Overview

AUTO-FLEET-001, Determine Fleet Vehicle Replacement, ranks candidate fleet vehicles by lifecycle cost, downtime risk, maintenance trend, 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)

Industry Profile

fleet-vehicle-replacement version 1.0.0

Default Profile

balanced

Default Scenario

standard

Algorithm

TOPSIS

Weight Strategy

Manual

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, operational downtime, maintenance trend, mission criticality, and safety condition.

Architecture

1. Request a token from https://identity.vinquery.com/connect/token.
2. Use the returned jwtToken as the bearer token.
3. Load https://dks.vinquery.com/decisioncatalog.
4. Load https://dks.vinquery.com/decisioncatalog/decisions/AUTO-FLEET-001.
5. Use the industry profile fleet-vehicle-replacement version 1.0.0.
6. Choose a valid profileId and scenarioId from the decision metadata.
7. Submit canonical option values to https://dde.vinquery.com/api/v1/decide.
8. Retain requestId and correlationId for tracing.

Authentication

Request a secure session token from Identity. Keep credentials server-side, cache tokens, renew before expiration, avoid duplicate concurrent token requests, and never log authorization headers.

POST https://identity.vinquery.com/connect/token
Content-Type: application/json

{
  "clientId": "{clientId}",
  "clientSecret": "{clientSecret}",
  "audience": "vinquery:api:decisioq"
}

{
  "requestId": "0HNE...",
  "jwtToken": "{jwtToken}",
  "tokenType": "Bearer",
  "expiresIn": 1800,
  "expiresUtc": "2026-07-19T00:30:00Z",
  "userId": 1166,
  "consumerName": "Example API Consumer",
  "apiConsumerId": "00000000-0000-0000-0000-000000000000"
}

Catalog Discovery

Retrieve current metadata instead of permanently hard-coding criteria or profiles. DKS is authoritative for version-aware decision knowledge.

GET https://dks.vinquery.com/decisioncatalog
Authorization: Bearer {jwtToken}

GET https://dks.vinquery.com/decisioncatalog/decisions/AUTO-FLEET-001
Authorization: Bearer {jwtToken}

Criteria

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

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 DKS currently defines none for this decision.

Industry Profile

The active industry profile 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 DDE 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",
  "assets": [
    {
      "assetId": "VEHICLE-001",
      "unitName": "Vehicle 001",
      "annualMaintenanceCost": 8200,
      "projectedRepairCost": 6200,
      "downtimeCost": 3600,
      "daysOutOfService": 0.4,
      "repairEventsLastYear": 6,
      "missionCriticality": 92,
      "safetyInspectionScore": 4.5
    }
  ]
}

{
  "optionId": "VEHICLE-001",
  "name": "Vehicle 001",
  "values": {
    "lifecycle_cost": 18000,
    "downtime_risk": 4,
    "maintenance_trend": 72,
    "utilization_criticality": 92,
    "safety_rating": 4.5
  }
}

Profiles and Scenarios

Profiles adjust weights. Scenarios describe operating context. Both are discovered from the DKS decision detail response.

Prepared Input

The active DDE catalog execution contract accepts decisionId, profileId, scenarioId, algorithm, weightStrategy, runSensitivity, requestContext, and options.

{
  "decisionId": "AUTO-FLEET-001",
  "profileId": "balanced",
  "scenarioId": "standard",
  "algorithm": "TOPSIS",
  "weightStrategy": "Manual",
  "runSensitivity": false,
  "requestContext": {
    "correlationId": "auto-fleet-001-demo-001"
  },
  "options": [
    {
      "optionId": "VEHICLE-001",
      "name": "Vehicle 001",
      "values": {
        "lifecycle_cost": 18000,
        "downtime_risk": 4,
        "maintenance_trend": 72,
        "utilization_criticality": 92,
        "safety_rating": 4.5
      }
    },
    {
      "optionId": "VEHICLE-002",
      "name": "Vehicle 002",
      "values": {
        "lifecycle_cost": 14500,
        "downtime_risk": 3,
        "maintenance_trend": 54,
        "utilization_criticality": 76,
        "safety_rating": 4
      }
    },
    {
      "optionId": "VEHICLE-003",
      "name": "Vehicle 003",
      "values": {
        "lifecycle_cost": 22500,
        "downtime_risk": 5,
        "maintenance_trend": 98,
        "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

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

Interpret the Result

Use decisionResult.winner and decisionResult.ranking as the deterministic result. Scores are useful within the same run; avoid comparing raw scores across unrelated decisions or catalog versions.

{
  "service": "decisioq",
  "version": "7.6.3",
  "requestId": "0HNE...",
  "operation": "Decide",
  "success": true,
  "decisionType": "AUTO-FLEET-001",
  "decisionVersion": "13.9.3",
  "timestampUtc": "2026-07-19T00:00:00Z",
  "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": "Vehicle 001 ranked highest based on the submitted criteria.",
      "strengths": [],
      "weaknesses": [],
      "exclusions": []
    }
  },
  "constraintSummary": {
    "definedConstraintCount": 0,
    "activeConstraintCount": 0,
    "eligibleOptionCount": 3,
    "excludedOptionCount": 0,
    "eligibleOptions": [
    "VEHICLE-001",
    "VEHICLE-002",
    "VEHICLE-003"
    ],
    "excludedOptions": []
  },
  "executionTrace": {
    "selectedProfileId": "balanced",
    "selectedScenarioId": "standard",
    "weightSource": "dksProfile:balanced",
    "effectiveWeights": {
      "lifecycle_cost": 25,
      "utilization_criticality": 20
    }
  },
  "warnings": [],
  "requestContext": {
    "correlationId": "auto-fleet-001-demo-001"
  }
}

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

The Explanation Service receives the finalized deterministic result and a controlled evidence package. It is synchronous in the current execution flow when configured and returns under the vendor-neutral ai block. If explanation generation fails silently, the deterministic result remains available.

{
  "ai": {
    "enabled": true,
    "generated": true,
    "schemaValidated": true,
    "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, DKS, and DDE 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, DDE or DKS generates one.

X-Correlation-Id

Optional client workflow ID propagated from DDE to DKS.

requestContext.correlationId

Payload value echoed by DDE 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