A.19.CPM:5.2 - Show (U.System) — comparing two supplier options without faking a total order
A program manager compares Supplier‑A vs Supplier‑B for a safety‑critical component. The team tracks a profile of measures (cost, lead time, defect rate, assurance, sustainability), but not all measures are strictly comparable across regions (different reporting regimes, different units).
-
The project has a declared
CN‑Spec(admission and comparability declarations) and a declaredCG‑Specthat lists admissible comparators inComparatorSetand evidence rules inMinimalEvidence. -
The comparator is
ParetoDominanceComparatorSpecRef@edition, declared inCG-Spec.ComparatorSet. -
The actual application binds the two supplier profiles; the claim scope
supplier options for the named component and procurement decision; its selected regulatory and reportingU.ContextSlicemembers under A.2.6;ComparisonPredicate = nonebecause Pareto dominance is supplied by the comparator; the stated procurement reference plane; and the explicit comparison interval. -
CPM runs
Compare(...); a changed component, scope member, comparator, plane, or interval is another comparison rather than an update to the same output.- If Supplier‑A is better in cost but worse in defect rate and incomparable on assurance due to missing evidence, CPM does not invent “A wins” or “A loses”.
CompareEligibilityreturnsdegradeorabstainunder the evidence policy. Onabstain, no comparison tokens are fabricated. When an explicitdegradepolicy permits a bounded partial comparison,ComparisonResultSlotcontains only the justified relation tokens and preserves incomparability.
-
The downstream
SelectorMechanismcan then return a selected set (e.g., keep both suppliers in the candidate set) rather than forcing a single winner by hidden tie‑break rules.