Chapter 1
Build the event
Daniel Reeves turns the approved line-expansion need into an RFQ draft. He defines the equipment scope, delivery location, response schedule, commercial fields, technical requirements, and evaluation weights. Three fictional qualified suppliers are selected. The event remains a draft until the configured review is complete. The illustration does not imply that a template replaces category judgment or technical input.
- Evidence visible
- Approved scope · Lots · Requirements · Evaluation criteria and weights · Response schedule · Invited suppliers
- Human action
- Daniel reviews the event and routes it for approval to publish.
- Policy or system boundary
- The RFQ uses customer-specific templates, policy, and review.
- Accessible alternative
- Chapter 1 shows Daniel creating an RFQ draft with scope, lots, response dates, commercial fields, technical requirements, evaluation weights, and three fictional qualified suppliers.
Read the complete walkthrough
Build the event
Daniel Reeves turns the approved line-expansion need into an RFQ draft. He defines the equipment scope, delivery location, response schedule, commercial fields, technical requirements, and evaluation weights. Three fictional qualified suppliers are selected. The event remains a draft until the configured review is complete. The illustration does not imply that a template replaces category judgment or technical input.
Publish a controlled RFQ
After approval, the RFQ opens to the invited suppliers through the illustrated supplier response path. Daniel can see which suppliers acknowledged receipt and the shared clarification deadline. Commercial responses remain unavailable to evaluators until the configured event stage permits access. This is a process-control illustration, not a universal statement about every customer policy.
Resolve supplier clarifications
One supplier asks whether an environmental rating applies to every drive or only units in the washdown area. Daniel routes the question to the technical evaluator. The approved answer clarifies the lot-level requirement and is issued to the appropriate audience. The event records the question, response, owner, version, and time. No supplier receives another supplier's confidential response.
Compare technical and commercial evidence
When the response stage closes, technical evaluators assess compliance against the published criteria. Daniel then reviews normalized commercial responses in a separate view. The comparison shows source values, units, adjustments, evaluator notes, and missing information. A highlighted difference is a prompt for review, not an automatic recommendation. Evaluation weights and treatment of nonconforming responses follow the approved Northstar Industrial Systems policy.
Model an award scenario
Daniel creates an award scenario that balances technical acceptability, evaluated cost, delivery commitments, and concentration. The model shows what changes when volume is split between two suppliers. Assumptions are editable and visible. Daniel documents why the proposed scenario fits the event criteria. The scenario is not an executed award and does not present modeled savings as realized value.
Approve and preserve the decision
Authorized sourcing and finance reviewers inspect the proposed allocation, evidence, and rationale. They can approve, return, or reject it. Once approved, Daniel releases the award outcome according to the configured process. The final trace links the approved scope, RFQ version, clarifications, source responses, evaluations, scenario, and reviewer decisions. This fictional outcome is not customer proof or a guaranteed sourcing result.