01
Establish the duty
UI recovers the duty, interfaces, constraints and acceptance result from the evidence and working sessions.
Decision-ready outputControlled technical requirement and scope boundary
S09 · Technical Definition & RFQ Pack
Make the requirement quotable.
You know the duty or business outcome, but interfaces, scope, standards, evidence and acceptance criteria must be made quotable before supplier outreach.
Selected contextOil, Gas & Petrochemicals · Original situation: Обоснуйте реальное решение по импорту.
- Timing
- 5–15 working days after evidence review
- Commercial basis
- Fixed fee after evidence and complexity review
- Engagement model
- Fixed-fee technical-definition pack
- Begin with
- Duty or required outcome, operating context, available drawings/data, interfaces, constraints, quantities and decision deadline.
- Finish with
- RFQ pack with clarification and acceptance route
Decision file
What you receive for the decision
Preview the decision file before you commission the work.
01
Controlled technical requirement and scope boundary
02
Interface, data-gap and responsibility registers
03
Supplier response template and commercial return format
04
RFQ pack with clarification and acceptance route
Four controlled decisions
Move only when the evidence supports the next decision.
Structured RFQ inputs and supplier return fields before quotation.
02
Define scope and interfaces
We separate required scope, client inputs, supplier responsibilities, options and exclusions.
Decision-ready outputInterface, data-gap and responsibility registers
03
Structure the supplier return
You receive one issue-ready RFQ pack and a structured return format that makes supplier responses comparable.
Decision-ready outputSupplier response template and commercial return format
04
Set the acceptance route
Issue the RFQ internally, commission supplier discovery, or stop until the missing evidence is available.
Decision-ready outputRFQ pack with clarification and acceptance route
Minimum useful evidence
Send what already exists.
A complete technical or commercial file is not required. Missing evidence becomes an explicit part of the first review.
01Required duty or outcome
What to include+
What must work or be accepted?
02Operating site
What to include+
City / country and indoor, outdoor or hazardous-area conditions
03Evidence already available
What to include+
Describe drawings, tags, offers or reports—do not paste sensitive data.
04Known interfaces and constraints
What to include+
Mechanical, electrical, process, site or documentation interfaces
05Quantity / lots
What to include+
Quantity, lots and annual volume
06RFQ / award deadline
What to include+
Date or decision window
Execution boundary
Keep responsibility visible.
The pack controls interfaces, responsibility and acceptance—not only a list of technical attributes.
01
UI structures the requirement; specialist design authority, conformity decisions and client approvals remain explicitly assigned.
02
No technical, commercial or delivery conclusion is presented as confirmed without traceable evidence.
03
The client retains approval of scope, supplier commitment, regulated decisions and final acceptance.
Start with the decision in front of you
Make this requirement quotable.
The assistant preserves this service context, identifies missing evidence and prepares the preliminary brief.