EM-OPS-02 · Subject model · W2
Procurement and supplier selection
Need, purchase request, procedure, bids, evaluation and decision. The order and the contract use the commercial models.
Partially published; research continues
Claude: complete-frozen-study-plus-one-audit-no-rerun; Grok: complete-exact-prompt-reconciled.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- ProcurementRequest
- SourcingEvent
- SupplierBid
- BidEvaluation
- AwardDecision
Deep research questions
- How to separate the evaluation of a bid from the evaluation of a supplier?
- How to explain a choice across several criteria?
- How to handle a sole supplier?
Verifiable invariants
- Criteria have a version
- The decision references the considered bids
- Procurement approval does not mean a concluded contract
End-to-end acceptance scenario
Three bids, a conflict of interest and a criterion change are recorded without deleting the decision history.
Negative case
Winning a tender automatically creates a signed contract.
Approaches to compare
- APQC/BPMN: process definitions and execution
- GS1 EPCIS/SCOR: traceability and supply chain
- IDTA AAS and PLM/EAM/WMS practice: product, instance and maintenance
Candidates in the live catalogue
- WM-ECO-019 · Purchase Order · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.