Decision Summary
Business question: Which tire option should be recommended for recommend tire replacement in the selected Tire Retail & Service context?
Outcome: a ranked recommendation that supports, but does not replace, accountable business judgment.
| Criterion ID | Meaning | Direction | Weight | Unit |
|---|---|---|---|---|
repairability_score | Repairability Score | maximize | 25% | Rating |
safety_risk | Safety Risk | minimize | 25% | Rating |
repair_cost | Repair Cost | minimize | 15% | Currency |
remaining_tire_life | Remaining Tire Life | maximize | 20% | Percentage |
customer_urgency | Customer Urgency | maximize | 15% | Rating |
5-Minute Quick Path
Goal
Run Recommend Tire Replacement with a complete candidate set.
Recommended mode
Business Data Mode when you have ordinary operational records.
You provide
Candidate business records matching the published input schema.
DecisioQ returns
A ranked recommendation with score evidence.
Data Preparation Guide
Business Data uses domain-shaped records and the published mapping profile. Prepared Criteria bypasses mapping and supplies canonical criterion IDs directly. Never send both modes in one request.
| Business source | Canonical target |
|---|---|
option.assessment.repairabilityScore | repairability_score |
option.risk.safetyRisk | safety_risk |
option.financial.repairCost | repair_cost |
option.tire.repair.remainingTireLife | remaining_tire_life |
option.tire.repair.customerUrgency | customer_urgency |
Business Data Mode
This complete illustrative request comes from certification case valid-generated-business-payload. It demonstrates shape and mapping, not production data.
{
"decisionId": "AUTO-TIRE-024",
"mappingProfileId": "tire-retail-and-serv-recommend-tire-replacement-auto-tire-024",
"businessData": {
"requestContext": {
"sourceSystem": "automotive-profile-factory",
"correlationId": "factory-auto-tire-024"
},
"repairOrders": [
{
"optionId": "REPAIR-024-01",
"name": "Recommend Tire Replacement Option 1",
"assessment": {
"repairabilityScore": 1.76
},
"risk": {
"safetyRisk": 1.84
},
"financial": {
"repairCost": 200.0
},
"tire": {
"repair": {
"remainingTireLife": 63.0,
"customerUrgency": 2.44
}
}
},
{
"optionId": "REPAIR-024-02",
"name": "Recommend Tire Replacement Option 2",
"assessment": {
"repairabilityScore": 2.12
},
"risk": {
"safetyRisk": 1.64
},
"financial": {
"repairCost": 375.0
},
"tire": {
"repair": {
"remainingTireLife": 16.0,
"customerUrgency": 2.28
}
}
}
]
}
}Prepared Criteria Mode
This complete request is the published expected-canonical artifact. Values and names remain illustrative.
{
"decisionId": "AUTO-TIRE-024",
"mappingProfileId": "tire-retail-and-serv-recommend-tire-replacement-auto-tire-024",
"mappingProfileVersion": "1.0.0",
"profileId": "balanced",
"scenarioId": "standard",
"algorithm": "TOPSIS",
"weightStrategy": "Expert",
"runSensitivity": false,
"requestContext": {
"correlationId": "factory-auto-tire-024"
},
"options": [
{
"optionId": "REPAIR-024-01",
"name": "Recommend Tire Replacement Option 1",
"values": {
"repairability_score": 1.76,
"safety_risk": 1.84,
"repair_cost": 200.0,
"remaining_tire_life": 63.0,
"customer_urgency": 2.44
}
},
{
"optionId": "REPAIR-024-02",
"name": "Recommend Tire Replacement Option 2",
"values": {
"repairability_score": 2.12,
"safety_risk": 1.64,
"repair_cost": 375.0,
"remaining_tire_life": 16.0,
"customer_urgency": 2.28
}
}
]
}Understanding the Result
The score is a relative TOPSIS closeness coefficient within this candidate set; it is not a probability. The winner below was computed by DecisioQ.DecisionEngine.Services.TopsisEngine in-process from the published canonical request.
| Rank | Option | ID | Score |
|---|---|---|---|
| 1 | Recommend Tire Replacement Option 2 | REPAIR-024-02 | 0.548059 |
| 2 | Recommend Tire Replacement Option 1 | REPAIR-024-01 | 0.451941 |
Winner: REPAIR-024-02. Download verified local result
Profiles and Scenarios
Profiles: balanced, cost_focused, customer_first, safety_quality
Scenarios: standard, seasonal_peak, limited_inventory, urgent_customer_need
Profiles change business priorities; scenarios represent operating context. Re-run the same candidate set and compare winner, score gap, and criterion contribution before adopting a change.
Sensitivity Analysis
Vary the highest-weight criteria in small increments and record whether the winner changes. A stable winner across reasonable weight changes is stronger evidence than a large score in one configuration.
Scenario Analysis
Use a published scenario only when it represents the intended operating context: standard, seasonal_peak, limited_inventory, urgent_customer_need. Compare the winner, ranking gap, and trade-offs with the baseline run.
Integration Examples and Next Steps
Use the API guide and client kit to transport either request mode. This example intentionally does not duplicate authentication, routing, Key Vault, usage accounting, or operational logging guidance.
Review the batch validation report, replace illustrative data with governed business data, and add domain acceptance thresholds before rollout.
