P-101A · purchaser specification
Pump requirements
| Parameter | Required |
|---|---|
| Rated flow | 220 m³/h |
| Seal plan | Plan 53B |
| Wetted parts | SS316 |
Technical bid evaluation
Complete technical bid evaluations in hours.
Raven compares vendor offers with your specification and prepares the evaluation, deviations and technical questions.
The problem
Every offer needs checking against the same requirements.
Vendors organize their offers differently. A requirement may be answered in a datasheet, qualified in a note or left unanswered. Building the comparison means finding those responses and checking them against the purchaser’s specification.
- Different formats make offers difficult to compare
- Deviations and missing answers need technical questions
- Revised offers need checking against the earlier findings
The solutionTechnical bid evaluation · Illustrative example MR-P101 · Rev 3
Offer B · Rev 0
One comparison, from the requirement to the vendor’s answer.
Raven aligns the offers with the specification, identifies deviations and omissions, and prepares the technical questions. Select a requirement below to compare the source documents and see the technical question it produces.
Seal plan: Plan 52 offered against Plan 53B.
Vendor B · technical offer
Seal support system
Seal planPlan 52
Offered: Plan 52 · Required: Plan 53B
Raven’s finding
Technical question · Seal plan
Confirm compliance with Plan 53B, or explain the proposed deviation.
Piloted on a pump case with an international EPC.The evaluation covered the purchaser requirements and multiple vendor offers.
How it works
- 01
Read the requirements and offers
Start with the purchaser specification, datasheets and vendor offers as received. Raven extracts the requirements and finds each vendor’s response, including qualifications and exclusions.
- 02
Build the evaluation and technical questions
Align the responses requirement by requirement. Record deviations and omissions, link the supporting pages and prepare the questions needed to resolve them.
- 03
Return the comparison for engineering review
Receive the evaluation, technical questions and open decisions in the format your team uses. Each finding links to its specification clause and vendor page. Your engineer makes the final technical decision.
Value for your team.
Less time assembling the evaluation.
Start with the requirements, vendor responses and open questions together instead of building the comparison row by row.
A clearer basis for the engineering decision.
See where an offer differs, what remains unanswered and which source supports each finding.
Check a revised offer
Keep vendor revisions in the same case and check the new response against the open questions.
Evaluate the next equipment purchase
Apply the same requirements-to-response comparison to the next set of specifications and offers.
Extend across the project
Have Raven prepare further evaluations, or let your team run the work in Raven as bids arrive.
See what a completed evaluation contains.
Walk through the vendor comparison, deviations and technical questions from a real TBE case. Then start with one equipment purchase your team is evaluating.
See a completed evaluation
