Equivalency Table¶
Reference artifact — instantiates Acceptable Substitution Mapping
A lookup that, for each specified item, lists the alternates certified to satisfy the same requirement, with the validation basis recorded so a swap is settled by reference.
An Equivalency Table is a lookup register of already-settled one-for-one equivalences: for each specified item it names the alternates that have been certified to satisfy the same requirement, and — crucially — records the evidence that establishes each equivalence. Its defining move is that it treats interchangeability as a curated, validated fact you consult, not a judgment you re-litigate: a designer or buyer looks up the specified part and reads off the alternates that count as equal, with the basis for that equality attached. Because it stores a set of interchangeable equals rather than a graded menu, every entry answers the same requirement; the table's value and its danger both flow from that permanence, since an equivalence certified once will keep being handed back long after the world that certified it has changed.
Example¶
An electronics manufacturer maintains an equivalency table for the components in its products. A particular voltage regulator is specified across a dozen boards; the table lists three second-source alternates — parts from other vendors qualified to drop in for it — and against each one records the validation basis: matched parametric envelope (voltage, current, thermal), a passed qualification run, and a note on the one condition where the swap does not hold (a tighter dropout spec on a single board). When that regulator goes on allocation during a supply crunch, the sourcing engineer opens the table, sees which alternates are certified equal, reads the exception, and requalifies nothing — the equivalence was already established and recorded. Months later the original vendor revises the part's datasheet; the update trigger fires, the entry is flagged for revalidation, and until an engineer re-confirms it, the alternates are marked "review — spec changed" rather than silently trusted. The table's job is to hold a validated equivalence in a form the next person can rely on and audit.
How it works¶
What makes this the mechanism, rather than a casual cross-reference, is that it binds each equivalence to its evidence and to a decay signal:
- One requirement, many equals. Each row fixes a specified item; the listed alternates are those that all meet the same requirement, so they are interchangeable rather than graded.
- Evidence travels with the entry. No alternate is listed without the validation basis that earns its place — parametric match, test result, certification — so equivalence is a recorded claim, not an assertion.
- Conditions and exclusions are explicit. Where an equivalence holds only under a caveat, the caveat is recorded with it, so the lookup reproduces the full judgment.
- Entries carry a trigger to revalidate. Each equivalence is tied to the events (spec revision, obsolescence, evidence change) that force it back to review, so the register decays deliberately.
Tuning parameters¶
- Equivalence strictness — whether an entry must be a true drop-in or may be "acceptable with adjustment." Strict tables are safe and simple to use but list fewer options; looser ones cover more shortages but demand the reader honor every condition.
- Evidence bar per entry — how much validation an alternate needs before it's listed. A high bar makes every entry trustworthy but slow to add; a low bar fills the table fast and quietly admits weak equivalences.
- Coverage breadth — how many specified items get a row. Broad coverage is valuable under frequent substitution but multiplies the entries that can go stale.
- Revalidation cadence — how often and on what triggers entries are re-checked. Frequent revalidation keeps the table honest at real cost; rare revalidation is cheap until a lapsed equivalence fails in service.
When it helps, and when it misleads¶
Its strength is that it makes a settled equivalence fast, portable, and auditable: a swap that was proven once is available to everyone by lookup, with the basis attached so a reviewer can see why it holds — the artifact behind practices like second sourcing,[n1] where having qualified interchangeable parts is a deliberate resilience strategy.
Its signature failure is the frozen list: the table keeps affirming an equivalence after the requirement, the part, or the standard has moved, so a "certified equal" is trusted long past the point its evidence supports. A subtler version is an entry that matched on the measured parameters but diverges on one that was never in the table — a real equivalence on paper, a mismatch in service. The classic misuse is adding an alternate because it is convenient and back-filling no evidence, so the table silently degrades from a validated register into a wish list. The discipline is that no entry exists without its validation basis and a revalidation trigger — an equivalence that cannot show its evidence does not belong in the table.
How it implements the components¶
The table realizes the settled-equivalence record slice of the archetype — it curates and validates the set of equals, and does not adjudicate new cases or grade offerings:
acceptable_bundle_set— each row is a curated set of alternates deemed acceptable for one requirement, kept concrete and consultable.evidence_or_validation_criterion— every listed equivalence carries the recorded basis (parametric match, test, certification) that earns its place.update_trigger— entries are bound to the events that force revalidation, so the register is maintained rather than frozen.
It does not grade offerings into a tiered_acceptability_band for different needs — that is the Service Tier Mapping, its nearest artifact twin: the table lists equals that meet the same requirement, while tiers meet deliberately different levels. Nor does it run the live decision_boundary_and_review_rule and exception_and_appeal_path that adjudicate a newly proposed swap — that is the Procurement Equivalence Review, whose settled outcomes this table records.
Related¶
- Instantiates: Acceptable Substitution Mapping — it holds the validated equivalences a map relies on to authorize swaps by reference.
- Consumes: Procurement Equivalence Review — the review's approved substitutions become the table's settled entries.
- Sibling mechanisms: Service Tier Mapping · Design Tradeoff Curve · Indifference Map · Procurement Equivalence Review · Approved Alternative Catalog · Conjoint or Tradeoff Survey · Preference Elicitation Workshop · Substitution Matrix · Exception Review Workflow
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: The table establishes standing permissions that named alternatives satisfy the same requirement under recorded evidence, conditions, exclusions, and revalidation triggers.
Nearest alternative: Representation, Specification & Plan — A lookup surface presents the entries, but its operative force is certification that settles future substitutions by reference.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Logistics & Supply Chain Management
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Specialized
Rationale: Procurement and supply practice established approved-equal and second-source lists that let buyers substitute qualified products without reopening each selection.
Related originating lineages:
- Engineering & Design — Qualification engineering supplied functional requirements, test evidence, and revalidation triggers.
- Law & Governance — Procurement regulation supplied the governed meaning of acceptable brand-name-or-equal products.
Review resolution: The Federal Acquisition Regulation directly defines acceptable equal products by required functional and performance characteristics; the lookup's operational use is procurement, making logistics primary.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
The table and the Substitution Matrix look alike but do opposite work: the matrix scores candidates against attributes to reach a verdict, while the equivalency table records the verdicts already reached for quick lookup. A matrix is where an equivalence is decided; a table is where a decided equivalence lives.
[n1] Second sourcing is the practice of qualifying more than one supplier's part as interchangeable for a given function, so production is not hostage to a single vendor. An equivalency table is the artifact that records which parts are qualified equals and on what basis — turning a resilience goal into a consultable fact. ↩