Procurement and supplier selection
Need, purchase request, procedure, bids, evaluation and decision. The order and the contract use the commercial models.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseOPS
- Industry
- Cross-industry
- Tags
- EM-OPS-02W2subjectProcurementRequestSourcingEventSupplierBidBidEvaluationAwardDecision
What it is Filled
Need, purchase request, procedure, bids, evaluation and decision. The order and the contract use the commercial models.
Why it exists Filled
Need, purchase request, procedure, bids, evaluation and decision. The order and the contract use the commercial models.
Distinguishing features Derived, awaiting review
- Criteria have a version
- The decision references the considered bids
- Procurement approval does not mean a concluded contract
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: Winning a tender automatically creates a signed contract.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Операционный руководитель
Master systems
- BPM
- ERP
- WMS
- PLM
- EAM
Links to other meta-models Filled
neighbor
- EM-COM-01
- EM-FIN-03
- EM-OPS-05
references
- WM-ECO-019 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- ProcurementRequest
- SourcingEvent
- SupplierBid
- BidEvaluation
- AwardDecision
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- APQC/BPMN: process definitions and execution
- GS1 EPCIS/SCOR: traceability and supply chain
- IDTA AAS and PLM/EAM/WMS practice: product, instance and maintenance
Open 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?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-ops-02/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.