That is a narrower and harder job than running a generic RFx. The sourcing team often has days, not months. Engineering may still be resolving the design. Suppliers return different quantities, tooling treatment, freight terms, validity and exceptions. The customer can revise the request while suppliers prepare their bids.
The software market includes strategic sourcing suites, direct-material sourcing systems, supplier collaboration tools and operational RFQ products. Industrial OEMs also need a link to the incoming customer request. The right system depends on whether the main problem is enterprise sourcing governance, BOM and part sourcing, supplier participation or customer-bid execution.
Separate the two RFQs
An OEM in a bid sits between two commercial requests. The customer asks the OEM for a configured product, project or service. The OEM asks suppliers for the material, equipment and subcontract work needed to fulfill it. The two packages share requirements, but they do not share ownership, disclosure or deadlines.
| Record | Issued by | Recipient | What it decides |
|---|---|---|---|
| Customer RFQ or RFP | Customer | Industrial OEM | Whether the OEM will offer a compliant solution, price and delivery promise |
| Supplier RFQ | Industrial OEM | Approved or prospective suppliers | Which external source, cost, lead time and terms support the OEM bid |
| Supplier clarification | Supplier or OEM | Named sourcing and engineering team | How the package, exception or commercial basis should read |
| Supplier award | Industrial OEM | Selected supplier | The chosen scope and commercial basis, subject to customer award and final purchase commitment |
Do not forward the full customer package by default. Build the supplier package from the requirements that supplier needs, remove restricted customer information and state which revision governs. The customer deadline drives the supplier calendar, but the supplier never owns the OEM’s customer promise.
Decide what needs a supplier quote
The first sourcing decision is scope. A customer RFQ can contain hundreds of lines, drawings and clauses. Some map to released parts and valid agreements. Some need a new quote. Some need engineering before a supplier can price them. Mark that status before launching an event.
| Scope status | Meaning | Action |
|---|---|---|
| Current source | Valid price, quantity, revision, supplier and term exist | Use the evidence and confirm validity against the bid schedule |
| Refresh price | Known part and supplier, but price or validity is stale | Run a focused RFQ or contract check |
| New source | The requirement has enough definition, but no approved commercial source exists | Select qualified candidates and launch an RFQ |
| Engineering needed | The supplier cannot price the current requirement without a decision | Resolve or issue a controlled assumption before RFQ |
| Make or buy open | The OEM has not chosen internal or external supply | Compare capacity, avoidable internal cost, supplier offers and risk |
| Allowance only | Deadline prevents a firm offer | Name the assumption, range, owner and expiry; keep it out of the award column |
A BOM-driven sourcing product can help when the scope already exists as parts and assemblies. A customer-bid workflow must also find new requirements in specifications, schedules, spreadsheets and email. Test both paths if the OEM sells configured and engineered equipment.
Build a package a supplier can actually quote
A short email with drawings attached is not a complete RFQ. Put the commercial and technical basis in a cover record, identify every file and define the response structure. A supplier should know what to price, what to exclude and how the OEM will compare the bid.
| Package block | Required content |
|---|---|
| Identity | RFQ number, package title, OEM contact and confidentiality basis |
| Technical scope | Part or work-package lines, descriptions, quantities, units and make/buy boundary |
| Controlled files | Drawing, model, BOM, specification and revision for each line |
| Quality and compliance | Inspection, certificates, codes, traceability, first article and record retention |
| Delivery | Need date, releases, destination, packaging and shipment terms |
| Commercial response | Currency, price breaks, tooling, NRE, freight, duty, payment, validity and escalation |
| Exceptions | Required deviation and assumption format with affected line and evidence |
| Calendar | Receipt confirmation, question deadline, answer date, bid deadline and expected decision |
When the customer request contains several revisions, create a manifest. The manifest should state which file is current, what changed and whether the change reopens supplier pricing. A filename such as “drawing-final-v3.pdf” is not revision control.
Choose suppliers by capability and bid context
| Selection factor | Evidence |
|---|---|
| Process and technical fit | Qualified processes, materials, equipment envelope and similar parts |
| Approval status | Approved supplier list, customer approvals, first-article or qualification status |
| Capacity and lead time | Available slot, material position, tooling and realistic release plan |
| Quality performance | Defect, escape, corrective-action and delivery history for comparable work |
| Commercial fit | Currency, region, Incoterm, payment, volume appetite and contract position |
| Risk | Single-source exposure, financial health, location, sub-tier and continuity plan |
| Participation | Named contact, portal access, response behavior and question discipline |
Invite enough suppliers to create a real choice without broadcasting sensitive work to firms that cannot perform it. A supplier-discovery network helps when the approved base lacks capability. An OEM still needs technical and quality approval before a low bid becomes usable.
Work backward from the customer deadline
The supplier bid deadline is not the customer bid deadline. Sourcing needs time to check completeness, resolve exceptions, normalize offers, negotiate and feed the chosen basis into costing and approval. Put those steps on the same plan.
| Milestone | Example for a 15-day customer response | Owner |
|---|---|---|
| Supplier package ready | Day 2 | Engineering and sourcing |
| Supplier receipt confirmed | Day 3 | Sourcing |
| Supplier questions due | Day 5 | Suppliers |
| OEM addendum issued | Day 7 | Engineering and sourcing |
| Supplier bids due | Day 10 | Suppliers |
| Commercial and technical normalization | Days 10–12 | Sourcing, engineering and quality |
| Supplier basis approved | Day 13 | Bid owner and approvers |
| Customer price and proposal approved | Days 14–15 | Commercial team |
A late customer addendum may compress or reset this plan. Show which supplier packages it affects and who accepted the resulting cost or schedule risk. Silent deadline changes create stale quotes that look current in the bid workbook.
Give every bidder the same answer
Supplier questions often expose missing dimensions, ambiguous test requirements or commercial conflicts. Answer through the RFQ record and issue the answer to every affected bidder. Private clarification can create bids on different scope.
| Question state | Required control |
|---|---|
| Received | Record supplier, date, package line and due date |
| Under review | Assign a technical or commercial owner; show whether the question blocks pricing |
| Answered | Approve the response and publish it to the affected bidder set |
| Changes scope | Issue an addendum, update the manifest and request bid confirmation or resubmission |
| Supplier-specific | Limit distribution only when the answer depends on that supplier’s proprietary method or exception |
| Open at deadline | Carry a named assumption or extend the event; do not treat a blank as compliance |
LevaData’s current documentation, for example, separates receipt confirmation, question, submission and award dates and records supplier messages inside the RFQ. Whether the OEM uses a portal or email, the same controls should exist.
Collect comparable supplier responses
| Response field | Why the OEM needs it |
|---|---|
| Unit price by quantity and release | Prevents a price at annual volume from standing in for a small first order |
| Tooling and NRE | Separates cash, ownership, life, maintenance and amortization |
| Material and escalation basis | Shows what price can move and when |
| Lead time and capacity | Tests the customer promise and identifies reservation conditions |
| Freight, duty and Incoterm | Creates a comparable landed cost |
| Currency and payment | Exposes exchange and working-capital effects |
| Validity | Shows whether the offer survives the customer decision schedule |
| Technical compliance | States accepted requirements, deviations and assumptions |
| Quality and certification | Confirms inspection, records and approval cost |
| Sub-tier and country of origin | Supports risk, trade and customer requirements |
Require a response at line level and package level. A supplier may comply with nine lines and take an exception on the one that controls delivery. A single total and a PDF attachment will push the comparison back into manual work.
Normalize before you rank
Supplier A may quote a lower unit price while excluding tooling, freight and testing. Supplier B may include those items and offer a shorter lead time. Compare the same scope, quantity, delivery and commercial basis before scoring or negotiating.
| Normalization step | Question |
|---|---|
| Scope | Did every supplier include the same lines, revision, quality and documentation? |
| Quantity | Do prices use the same order size, annual volume and release pattern? |
| Tooling and NRE | What cash is due, who owns the asset and how much sits in unit price? |
| Landed cost | Which freight, duty, packaging, currency and payment effects belong in the comparison? |
| Schedule | Can the supplier meet the required date without unpriced expedite or capacity risk? |
| Commercial terms | What validity, escalation, warranty and liability differ? |
| Risk and performance | What quality, delivery, concentration or qualification cost remains? |
The normalized view should preserve the supplier’s original response. Buyers need to see the submitted price, the OEM adjustment and the reason as separate values. Otherwise the comparison becomes an edited spreadsheet that no one can audit.
Follow one fabricated base through an RFQ
A customer asks an OEM for a process-pump package. The OEM must source the fabricated base, piping supports and protective coating. It sends one controlled package to three approved fabricators for an initial quantity of four and an expected annual volume of twelve.
| Bid element | Supplier A | Supplier B | Supplier C |
|---|---|---|---|
| Unit price at 4 | $28,400 | $29,100 | $27,600 |
| Tooling and fixture | $8,000 | Included | $12,000 |
| Coating | Included | Included | Excluded: $1,900/unit allowance |
| Freight | FOB supplier | Delivered | FOB supplier |
| Lead time | 14 weeks | 11 weeks | 16 weeks |
| Payment | 30% deposit, balance net 30 | Net 45 | 50% deposit, balance before ship |
| Technical position | Compliant | One approved weld-process alternative | Open exception on flatness inspection |
| Validity | 45 days | 60 days | 30 days |
Supplier C has the lowest headline unit price. After tooling, coating, freight and the four-unit quantity basis, its evaluated cost reaches $32,950 per unit before the inspection exception. Supplier A evaluates to $31,050. Supplier B remains $29,100 delivered, meets the needed date and offers the best payment and validity.
The OEM selects Supplier B for the bid basis and keeps A as the qualified alternate. It records the weld-process deviation and engineering approval with B’s quote. The customer cost model receives $116,400 for four bases, the 11-week lead time and the 60-day validity. The award remains conditional on the customer order.
Choose software by the sourcing problem
The category covers different jobs. Strategic sourcing suites govern enterprise RFx and awards. Direct-material products connect BOMs, item data, cost breakdowns and supplier decisions. Operational RFQ tools focus on buyer and supplier execution. Bourne connects those supplier events to a live customer bid.
| Product | Strongest fit | What to prove |
|---|---|---|
| SAP Ariba Strategic Sourcing and Product Sourcing | Large SAP-centered programs that need governed sourcing events, BOM/material sourcing, pricing history and ERP award integration | BOM and material-master mapping, supplier adoption, attachment/revision handling, award return and event setup time |
| Ivalua Direct Materials Sourcing | Direct-material programs that need BOM lifecycle, cost breakdown, RFx, supplier risk, quality and scenario analysis | Engineering and ERP integration, configuration effort, item-level revision control and use during short customer bids |
| JAGGAER One Sourcing | Enterprise sourcing with direct-material and BOM event support | Direct-material depth for your commodities, supplier workflow, analysis, approvals and integration |
| GEP Quantum Direct Sourcing | BOM-driven direct sourcing, supplier collaboration and award across a broader procurement platform | Current product depth, data model, explainability of agent actions and fit with existing source-to-pay systems |
| LevaData | Direct-material spend, part intelligence, benchmarks, risk and vendor RFQ collaboration | Coverage for custom and catalog parts, supplier-user adoption, BOM mapping, bid normalization and downstream award handoff |
| SourceDay RFQ | Operational buyer-supplier RFQ execution for direct-material teams | ERP and item-revision integration, project/package structure, response comparison and award transfer |
| Workday Strategic Sourcing | Collaborative RFx, intake, supplier evaluation, auction and source-to-contract governance | Manufacturing BOM and revision depth, direct-material cost structures and integration to the production stack |
| Bourne | Supplier RFQs created inside a customer-specific OEM bid with engineering, costing and deadline dependencies | Customer-RFQ extraction, package assembly, revision propagation, exception routing and transfer into cost and price approval |
Current product material supports these differences. SAP documents material and BOM sourcing plus RFQ and award integration. Ivalua links BOM roll-ups, cost breakdowns, should-cost, RFx and supplier risk. JAGGAER lists direct material and BOM sourcing in its sourcing product. GEP describes BOM-to-award execution in Direct Sourcing. LevaData documents part-level RFQ scope, calendars, messaging and vendor response. SourceDay publishes a buyer and supplier RFQ workflow with item revisions. Workday centers on RFx, pricing sheets, supplier evaluation, auctions and source-to-contract.
Check supplier effort as carefully as buyer features
A powerful buyer screen has little value when suppliers cannot open the package, understand the response format or submit before the deadline. Test the event with several real suppliers, including a small specialist with no full-time portal administrator.
| Supplier test | Pass condition |
|---|---|
| Access | The invited contact can authenticate and delegate without buyer support |
| Package review | The supplier can identify current files, lines, quantities and dates |
| Questions | The supplier can ask against a line or document and see published answers |
| Response | The supplier can enter or upload price breaks, tooling, dates, terms and exceptions |
| Revision | A changed package shows what moved and which answers need reconfirmation |
| Submission | The supplier receives a clear receipt and can revise before close under stated rules |
| Support | A real help path exists when access or upload fails near the deadline |
SAP Business Network, for example, gives suppliers a network account and sourcing workflow. LevaData requires active supplier users for in-platform messaging and bids. Workday supports supplier bid proposals online or through Excel. Each model shifts different work to the supplier; measure completion and support load during the pilot.
Protect drawings and customer information
| Control | Required behavior |
|---|---|
| Need-to-know package | Share only the files and customer facts required for the supplier scope |
| Confidentiality | Confirm agreement status before access to restricted files |
| Named access | Give each supplier contact individual access and remove it when the event ends |
| Download and audit | Record who viewed or downloaded controlled content when the requirement calls for it |
| Export and technical restrictions | Apply classification, geography and citizenship rules where required |
| Retention | Define how long suppliers and the OEM retain event records and withdrawn revisions |
| Sub-tier sharing | Require approval or declaration before the supplier shares the package downstream |
Security claims on a vendor website do not answer the event-design question. Run one package with the exact file types, supplier roles and regional restrictions the OEM uses. Confirm what suppliers can download, forward and retain.
Carry the selected basis into the customer cost model
The supplier event creates a bid input. It should update the correct line in the OEM cost model with the supplier, scope revision, evaluated cost, quantity, currency, validity, lead time and exceptions. Preserve alternate bids for negotiation and fallback.
| Change after supplier bid | Required action |
|---|---|
| Customer revises specification | Identify affected supplier packages and reopen only the exposed lines |
| Customer quantity changes | Request or apply the correct price break and review tooling amortization |
| Supplier validity expires | Refresh the bid or approve a visible, sourced escalation assumption |
| Engineering approves a supplier deviation | Update the offered product basis and store the approval with the supplier quote |
| Customer award arrives late | Reconfirm cost, capacity and lead time before order release |
| Supplier changes after award | Reopen cost, margin, delivery and technical handoff where the basis changes |
This connection prevents an estimator from typing one selected price into a workbook and losing the conditions that made it valid. Label each cost as contracted, firm, budgetary, modeled or allowed.
Run the proof on live packages
Use one repeat part package, one new engineered package and one event with a customer revision. Include suppliers of different sizes. Run the existing email or sourcing process in parallel long enough to compare the same work.
| Proof measure | What to record |
|---|---|
| Package preparation time | Receipt of usable customer scope to supplier issue |
| Supplier participation | Invited, confirmed, questioned, submitted and declined counts |
| On-time complete bids | Responses with all required technical and commercial fields by deadline |
| Clarification cycle | Questions, answer time, addenda and resubmissions |
| Normalization effort | Buyer hours from close to comparable bid table |
| Revision accuracy | Affected packages correctly reopened and supplier confirmations received |
| Cost handoff | Selected bid lines transferred with source, terms and exceptions intact |
| Customer-bid impact | Supplier evidence ready before cost and price approval |
Review failed participation one supplier at a time. A low response rate may come from access friction, an incomplete package, an unrealistic deadline, poor supplier fit or low award credibility. The remedy depends on the cause.
When Bourne is the best fit
Choose SAP Ariba, Ivalua, JAGGAER, GEP or Workday when the company needs an enterprise sourcing system to govern categories, events, suppliers, awards and contracts across broad spend. Choose LevaData when part intelligence, benchmarks and electronics or direct-material sourcing drive the program. Choose SourceDay when the operational RFQ and supplier workflow around ERP parts is the main need.
Bourne is best when supplier sourcing begins inside a customer RFQ and must move at the speed of the bid. It can read the customer package, identify bought-out and subcontract scope, assemble supplier packages from controlled files, route technical questions, compare returned bids and carry the selected evidence into product cost and price approval.
Bourne can also create or update an event in the sourcing platform the company already uses. The sourcing suite remains the supplier and award system of record. Bourne connects that event to the customer request and makes the engineering and deadline dependencies visible. See the supplier RFQ workflow for the application.
Arda Bulut
Arda Bulut is the co-founder and CTO of Bourne and HockeyStack. He leads engineering at Bourne, building the platform people use to create AI products, agents and automations.