Decision Summary

Business question: Which parking option should be recommended for prioritize enforcement patrol in the selected Parking Lot Management context?

Outcome: a ranked recommendation that supports, but does not replace, accountable business judgment.

5-Minute Quick Path

First working request →

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 Data Mode

This complete illustrative request comes from certification case valid-generated-business-payload. It demonstrates shape and mapping, not production data.

{
  "decisionId": "AUTO-PARK-032",
  "mappingProfileId": "parking-lot-manageme-prioritize-enforcement-patrol-auto-park-032",
  "businessData": {
    "requestContext": {
      "sourceSystem": "automotive-profile-factory",
      "correlationId": "factory-auto-park-032"
    },
    "parkingOperations": [
      {
        "optionId": "PARKING-032-01",
        "name": "Prioritize Enforcement Patrol Option 1",
        "enforcement": {
          "and": {
            "compliance": {
              "violationSeverity": 1.72,
              "customerDisruption": 2.88
            }
          }
        },
        "risk": {
          "safetyRisk": 2.92,
          "complianceNecessity": 3.28
        },
        "assessment": {
          "evidenceQuality": 1.64
        }
      },
      {
        "optionId": "PARKING-032-02",
        "name": "Prioritize Enforcement Patrol Option 2",
        "enforcement": {
          "and": {
            "compliance": {
              "violationSeverity": 2.92,
              "customerDisruption": 4.04
            }
          }
        },
        "risk": {
          "safetyRisk": 3.04,
          "complianceNecessity": 3.92
        },
        "assessment": {
          "evidenceQuality": 2.36
        }
      }
    ]
  }
}

Download Business Data request

Prepared Criteria Mode

This complete request is the published expected-canonical artifact. Values and names remain illustrative.

{
  "decisionId": "AUTO-PARK-032",
  "mappingProfileId": "parking-lot-manageme-prioritize-enforcement-patrol-auto-park-032",
  "mappingProfileVersion": "1.0.0",
  "profileId": "balanced",
  "scenarioId": "standard",
  "algorithm": "TOPSIS",
  "weightStrategy": "Expert",
  "runSensitivity": false,
  "requestContext": {
    "correlationId": "factory-auto-park-032"
  },
  "options": [
    {
      "optionId": "PARKING-032-01",
      "name": "Prioritize Enforcement Patrol Option 1",
      "values": {
        "violation_severity": 1.72,
        "safety_risk": 2.92,
        "evidence_quality": 1.64,
        "customer_disruption": 2.88,
        "compliance_necessity": 3.28
      }
    },
    {
      "optionId": "PARKING-032-02",
      "name": "Prioritize Enforcement Patrol Option 2",
      "values": {
        "violation_severity": 2.92,
        "safety_risk": 3.04,
        "evidence_quality": 2.36,
        "customer_disruption": 4.04,
        "compliance_necessity": 3.92
      }
    }
  ]
}

Download Prepared Criteria request

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.

Winner: PARKING-032-01. Download verified local result

Profiles and Scenarios

Profiles: balanced, customer_first, revenue_optimized, safety_compliance

Scenarios: standard, peak_event, system_disruption

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, peak_event, system_disruption. 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.