← Back to catalogue
Published

Procurement and supplier selection

EM-OPS-02 · em-ops-02

Need, purchase request, procedure, bids, evaluation and decision. The order and the contract use the commercial models.

Enterprise profiles Enterprise subject EnterpriseOPS

Bundle → Layer → Finding → Questions Filled

2 bundles · 2 layers · 4 findings · 9 questions

Need and procedure From a need to a sourcing event with stated criteria.

Request and criteria

The purchase request and the versioned evaluation criteria.

Purchase request

The need, its owner and the chosen procedure.

  1. Which need does this request cover, and who raised it?
  2. Which procedure was chosen, and why, including a sole supplier case?

Criteria version

Evaluation criteria with versions and changes.

  1. Which version of the criteria applied to this event?
  2. Was a criterion changed during the event, and with what justification?
Bids and decision Bids received, their evaluation and the award.

Evaluation

Bid evaluation kept apart from supplier evaluation.

Bid scoring

Scores per bid and criterion.

  1. How did each bid score against each criterion?
  2. Is this an evaluation of the bid or of the supplier?

Award and conflicts

The decision, the bids it considered and any conflict of interest.

  1. Which bids did the award decision consider?
  2. Was a conflict of interest declared, and how was it handled?
  3. Has a contract been concluded, or only the award approved?

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 Filled

  • A bid is evaluated against its own criteria; the supplier's general standing is a separate assessment.
  • Criteria carry a version so that a decision can be explained against the criteria in force.
  • Approval of an award is not a concluded contract.
  • Distinct from the order and contract contours, which take over once a supplier is chosen.

What robots and AI may and may not do Filled

Must not

  • Create a signed contract automatically from a winning bid.
  • Apply a changed criterion to bids without recording the change.
  • Delete or overwrite earlier decisions in the history.
  • Share one bidder's prices or terms with another bidder.

Only with a human decision

  • Making the award decision.
  • Approving a sole supplier procedure.
  • Handling a declared conflict of interest.

May

  • Score bids against the criteria version in force and show the result per criterion.
  • Flag criteria changes and declared conflicts of interest.
  • Prepare a summary explaining an award across several criteria.

Moral aspects Filled

  • Fair treatment of bidders depends on stable criteria and confidential bids.
  • Undeclared conflicts of interest can misuse public or company funds.

Who is affected

  • Bidding suppliers
  • Requesters and buyers
  • Funders or the public in public procurement

Owners Filled

Steward

The head of operations or procurement who answers for fair and documented supplier selection.

Master systems

  • Business process management suite
  • ERP
  • Warehouse management system
  • Product lifecycle management system
  • Enterprise asset management system

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 Filled

Identity and identifiers required Filled

  • Identified by a sourcing event identifier; bids by bid identifier and bidder, the award by decision identifier.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A record of a sourcing event with bids, scores and an award decision.
  • Often confused with a purchase order or a supplier contract.

Capabilities and actions required Filled

  • Award decisions can be explained against the criteria version in force.
  • Criteria changes and conflicts of interest can be audited.

Hazards and failure modes required Filled

  • Bid rigging or favouritism hidden by changed criteria.
  • Leakage of confidential bid content.

Standards and interfaces required Filled

  • Open Contracting Data Standard from the Open Contracting Partnership for procurement data.
  • Common Procurement Vocabulary of the European Union for classifying purchases.
  • GLEIF LEI for identifying supplier legal entities.

Context of use required Filled

  • Used in corporate purchasing and public procurement.
  • Public procurement is subject to procurement law with its own procedures and records.

Sources Filled

  1. APQC/BPMN: process definitions and execution
  2. GS1 EPCIS/SCOR: traceability and supply chain
  3. IDTA AAS and PLM/EAM/WMS practice: product, instance and maintenance
  4. OMG Business Process Model and Notation 2.0.2 - Checked live (HTTP 200) on 2026-10-07.
  5. OASIS Universal Business Language 2.3 - Checked live (HTTP 200) on 2026-10-07.

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, ver-cy/world-models/card-supplements/em-ops-02.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.