Damage Priority Queue Rank Scorer (significance x risk)
Rank caller damage significance×risk assessments with explicit stable ties, retaining products; score is triage policy, not calibrated expected harm or treatment priority authority.
Description
A triage score can multiply caller significance and risk assessments.
A triage score can multiply caller significance and risk assessments. Stable ties make the resulting ordering reproducible.
Rank caller damage significance×risk assessments with explicit stable ties, retaining products; score is triage policy, not calibrated expected harm or treatment priority authority.
When to use Damage Priority Queue Rank Scorer (significance x risk)
Use this tool to rank caller damage significance×risk assessments with explicit stable ties, retaining products; score is triage policy, not calibrated expected harm or treatment priority authority.
Prepare the collection, exposure, scheduling or financial records required for this calculation. Keep row order and the declared units consistent.
How to use Damage Priority Queue Rank Scorer (significance x risk) and understand its results
- Prepare the collection, exposure, scheduling or financial records required for this calculation. Keep row order and the declared units consistent.
- Enter callerSignificanceScores, callerRiskScores using the field table and calculation rules, then run the tool.
- Read priorityProducts, stablePriorityOrderIndices. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| callerSignificanceScores | Caller significance scores | list of number | Required |
| callerRiskScores | Caller risk scores | list of number | Required |
Align nonnegative scores and require finite products. Return products and zero-based indices sorted high to low, preserving source order for exact ties.1
Paired lists must be nonempty and have equal lengths.
priority = significance × risk; order by descending priority then original index Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| priorityProducts | Priority products | list of number |
| stablePriorityOrderIndices | Stable priority order indices | list of number |
{
"input": {
"callerSignificanceScores": [
2,
3,
3
],
"callerRiskScores": [
4,
2,
2
]
},
"output": {
"priorityProducts": [
8,
6,
6
],
"stablePriorityOrderIndices": [
0,
1,
2
]
}
}Limitations and assumptions
Products are policy scores, not calibrated harm estimates or treatment authority.
Numbers and computed results must be finite; overflow produces an error. Numeric lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Condition Change Delta Score Between Reports Calculator: Compare matched caller condition rubric components with explicit score direction, retaining offsetting improvements/deterioration; no objective damage scale or automatic diagnosis. For a complementary task, use Conservation Treatment Backlog Aging Days Calculator: Retain closed service time versus right-censored open backlog age with explicit status, rather than age every completed object to today; zero maximum means no open records.
References
Similar or alternative tools
- Condition Change Delta Score Between Reports Calculator
Compare matched caller condition rubric components with explicit score direction, retaining offsetting improvements/deterioration; no objective damage scale or automatic diagnosis.
- Conservation Treatment Backlog Aging Days Calculator
Retain closed service time versus right-censored open backlog age with explicit status, rather than age every completed object to today; zero maximum means no open records.