Overview

AUTO-FLEET-001, Determine Fleet Vehicle Replacement, ranks candidate fleet vehicles by lifecycle cost, operational availability risk, maintenance burden, utilization criticality, and safety rating.

Decision ID

AUTO-FLEET-001

Decision Name

Determine Fleet Vehicle Replacement

Description

Determine Fleet Vehicle Replacement using the relevant Fleet Vehicle Management business criteria, profile, and operating scenario.

Industry

Automotive

Sector

Fleet Vehicle Management (AUTO-FLEET)

Category

Vehicle Lifecycle (AUTO-FLEET-VEHICLE-LIFECYCLE)

Decision Preparation Model

fleet-vehicle-replacement version 1.0.0

Default Profile

balanced

Default Scenario

standard

Algorithm

TOPSIS

Weight Strategy

Expert (Manual) (API value Expert)

Catalog

DKR-AUTO-RUNTIME-001, version 13.9.3

Understanding This Decision

Determine Fleet Vehicle Replacement helps fleet operations teams decide which vehicle should be prioritized for replacement by balancing ownership cost, expected annual downtime, recurring maintenance burden, mission criticality, and safety condition.

Criteria

Use exact criterionId keys. Display names can change; canonical IDs drive validation, mapping, weighting, and execution.

Data Preparation Guide

Constraint Processing

This decision currently has no catalog-defined hard constraints. All validated candidates proceed to criteria-based ranking.

{
  "constraintSummary": {
    "definedConstraintCount": 0,
    "activeConstraintCount": 0,
    "eligibleOptionCount": 3,
    "excludedOptionCount": 0,
    "eligibleOptions": [
      "VEHICLE-001",
      "VEHICLE-002",
      "VEHICLE-003"
    ],
    "excludedOptions": []
  }
}

const constraints = decisionDetail.constraints || [];
if (constraints.length === 0) {
  // No catalog-defined hard constraints.
  // Submit all validated candidates for criteria-based ranking.
}

const summary = response.constraintSummary;
const excluded = response.decisionResult?.excludedOptions || [];

Excluded candidates do not participate in ranking because hard constraints are evaluated before scoring. For AUTO-FLEET-001, no candidates are excluded by catalog-defined constraints because Decision Catalog currently defines none for this decision.

Decision Preparation Model

The active decision preparation model reads fleet asset options from $.assets, option IDs from option.assetId, and display names from option.unitName. It prepares canonical values for AUTO-FLEET-001 before Decision Service applies decision validation and ranking.

Profile ID

fleet-vehicle-replacement

Version

1.0.0

Options Path

$.assets

Option ID Path

option.assetId

Display Name Path

option.unitName

{
  "fleetId": "FLEET-DEMO-001",
  "observationPeriodDays": 365,
  "assets": [
    {
      "assetId": "VEHICLE-001",
      "unitName": "Vehicle 001",
      "annualMaintenanceCost": 8200,
      "projectedRepairCost": 6200,
      "downtimeCost": 3600,
      "daysOutOfService": 9,
      "repairEventsLastYear": 6,
      "missionCriticality": "High",
      "safetyInspectionScore": 4.5
    }
  ]
}

{
  "optionId": "VEHICLE-001",
  "name": "Vehicle 001",
  "values": {
    "lifecycle_cost": 18000,
    "downtime_risk": 9,
    "maintenance_trend": 6,
    "utilization_criticality": 90,
    "safety_rating": 4.5
  }
}

Profiles and Scenarios

This example selects a Profile for evaluation emphasis and a Scenario for operating context. Discover both from the selected Decision Catalog definition.

Prepared Input

The active Decision Service Prepared Criteria Mode contract accepts decisionId, profileId, scenarioId, algorithm, weightStrategy, runSensitivity, requestContext, and options.

{
  "decisionId": "AUTO-FLEET-001",
  "profileId": "balanced",
  "scenarioId": null,
  "algorithm": "TOPSIS",
  "weightStrategy": "Expert",
  "runSensitivity": false,
  "requestContext": {
    "correlationId": "auto-fleet-001-demo-001"
  },
  "options": [
    {
      "optionId": "VEHICLE-001",
      "name": "Vehicle 001",
      "values": {
        "lifecycle_cost": 18000,
        "downtime_risk": 9,
        "maintenance_trend": 6,
        "utilization_criticality": 92,
        "safety_rating": 4.5
      }
    },
    {
      "optionId": "VEHICLE-002",
      "name": "Vehicle 002",
      "values": {
        "lifecycle_cost": 14500,
        "downtime_risk": 3,
        "maintenance_trend": 2,
        "utilization_criticality": 76,
        "safety_rating": 4
      }
    },
    {
      "optionId": "VEHICLE-003",
      "name": "Vehicle 003",
      "values": {
        "lifecycle_cost": 22500,
        "downtime_risk": 15,
        "maintenance_trend": 8,
        "utilization_criticality": 88,
        "safety_rating": 3.5
      }
    }
  ]
}

Execute

curl -X POST "https://dde.vinquery.com/api/v1/decide" \
  -H "Authorization: Bearer ${DECISIOQ_TOKEN}" \
  -H "Content-Type: application/json" \
  -H "X-Correlation-Id: auto-fleet-001-demo-001" \
  --data @auto-fleet-001-execute.json

Decision Service retrieves authoritative criteria, profiles, scenarios, and validation metadata from Decision Catalog, composes the engine-ready request, and executes the deterministic ranking.

Interpret the Result

Every successful response includes the deterministic decisionResult and a top-level explanation object. Use decisionResult.winner and decisionResult.ranking as the ranking; the explanation adds context but does not change it. Scores are useful within the same run, not across unrelated decisions or catalog versions.

{
  "service": "decisioq",
  "version": "7.6.3",
  "requestId": "0HNE...",
  "operation": "Decide",
  "success": true,
  "timestampUtc": "2026-07-19T00:00:00Z",
  "requestContext": {
    "correlationId": "auto-fleet-001-demo-001",
    "decision": {
      "id": "AUTO-FLEET-001",
      "name": "Prioritize Fleet Vehicle Replacement",
      "catalogVersion": "13.9.3"
    }
  },
  "configurationUsed": {
    "weightStrategy": { "value": "Expert", "source": "ExplicitRequest" },
    "rankingAlgorithm": { "value": "TOPSIS", "source": "ExplicitRequest" },
    "profile": { "value": "balanced", "source": "ExplicitRequest" },
    "scenario": { "value": "standard", "source": "ExplicitRequest" },
    "sensitivity": { "value": false, "source": "PlatformDefault" }
  },
  "decisionResult": {
    "winner": "VEHICLE-001",
    "confidence": 72.4,
    "ranking": [
      {
        "optionId": "VEHICLE-001",
        "score": 0.8421,
        "breakdown": {
          "lifecycle_cost": 0.25,
          "utilization_criticality": 0.20
        },
        "normalizationBreakdown": {}
      }
    ],
    "excludedOptions": []
  },
  "explanation": {
      "summary": "The selected vehicle has the strongest overall replacement priority.",
      "whyRecommended": "It combined high utilization criticality with acceptable safety evidence and manageable lifecycle cost.",
      "keyDrivers": [],
      "tradeoffs": [],
      "competitors": [],
      "sensitivitySummary": "Sensitivity analysis was not included in this response.",
      "scenarioSummary": "The standard operating scenario was selected.",
      "risks": [],
      "nextSteps": [],
      "assumptions": []
  },
  "constraintSummary": {
    "definedConstraintCount": 0,
    "activeConstraintCount": 0,
    "eligibleOptionCount": 3,
    "excludedOptionCount": 0,
    "eligibleOptions": [
    "VEHICLE-001",
    "VEHICLE-002",
    "VEHICLE-003"
    ],
    "excludedOptions": []
  },
  "warnings": []
}

Sensitivity Analysis

Use "runSensitivity": true when the client needs evidence about recommendation stability. DecisioQ varies criterion weights by controlled factors while keeping submitted options and values fixed.

{
  "runSensitivity": true,
  "sensitivityResult": {
    "stableWinner": true,
    "winner": "VEHICLE-001",
    "mostSensitiveCriterion": "lifecycle_cost",
    "confidence": 95,
    "criterionImpacts": {
      "lifecycle_cost": 0.1842
    },
    "winnerChangeCounts": {
      "lifecycle_cost": 0
    }
  }
}

Explanation of Decision Result

Every successful response includes a provider-neutral top-level explanation object. The Explanation Service receives the finalized deterministic result and a controlled evidence package; the object adds context but does not change the ranking.

{
  "explanation": {
      "summary": "The selected vehicle has the strongest overall replacement priority.",
      "whyRecommended": "It combined high utilization criticality with acceptable safety evidence and manageable lifecycle cost.",
      "keyDrivers": [],
      "tradeoffs": [],
      "competitors": [],
      "sensitivitySummary": "Sensitivity analysis was not included in this response.",
      "scenarioSummary": "The standard operating scenario was selected.",
      "risks": [],
      "nextSteps": [],
      "assumptions": []
  }
}

The Explanation of Decision Result must not receive raw private vehicle files or unrestricted notes. It explains the already-finalized result; it does not select, rerank, recalculate, or override it.

Tracing and Logs

Use request identifiers to connect client, Identity, Decision Catalog, and Decision Service activity. Authentication and identity-security activity belongs in IdentityAuditEvents. Catalog, mapping, decision execution, sensitivity, and explanation operations belong in decisioq_log.

X-Request-Id

Optional client-supplied request ID. If omitted, Decision Service or Decision Catalog generates one.

X-Correlation-Id

Optional client workflow ID propagated from Decision Service to Decision Catalog.

requestContext.correlationId

Payload value echoed by Decision Service and used for execution logging.

DecisionId

Recorded for decision-specific operations. General catalog and identity operations may not have a decision ID.

Code Examples

These examples authenticate, retrieve AUTO-FLEET-001 metadata, validate profile and scenario selections, execute the decision, pass a correlation ID, and print the deterministic result.

DECISIOQ_CLIENT_ID
DECISIOQ_CLIENT_SECRET

Optional:
DECISIOQ_IDENTITY_URL=https://identity.vinquery.com/connect/token
DECISIOQ_DKS_URL=https://dks.vinquery.com
DECISIOQ_DDE_URL=https://dde.vinquery.com

Troubleshooting

Production Checklist