Technical bid evaluations in hours instead of days.
A bid evaluation, a vendor document review, an inter-discipline check: most project document work is engineers reading the same requirements again and again. Raven's agents do the reading. The specification compared against every offer, vendor datasheets against the requisition, deliverables against each other, and every flag cites the pages that disagree. The work starts from the document set itself, so a single live package is enough to begin.
The bid tabulation, built by agents that read every offer.
A technical bid evaluation is days of reading: the specification, the datasheets, every vendor's offer, clause by clause. Raven's agents do the reading and build the tabulation: deviations flagged with the page they sit on, unclear items drafted as technical queries. We've tested this on a real pump bid evaluation with an international EPC.
| Requirement | Offer A | Offer B | Offer C |
|---|---|---|---|
| Flow & head · clause 4.2 | complies | complies | complies |
| Seal plan · 53B | complies | offers Plan 52 | complies |
| NPSH margin · 1 m | 1.4 m | 1.2 m | 0.6 m · p.14 |
| Casing material · SS316 | complies | TQ drafted | complies |
Vendor datasheets, checked value by value.
After the order, every vendor datasheet revision gets reviewed against the requisition, and the differences hide in the values. Raven's agents read each parameter off the vendor sheet and compare it against your requisition and process data, with every difference citing both pages.
| Parameter | Vendor B | Finding |
|---|---|---|
| Rated head | 82 m | meets clause 4.2 |
| NPSH margin | 0.6 m | below requisition · p.3 |
| Casing material | CS offered | requisition says SS316 |
| Test scope | per spec | cited · vendor p.7 |
The same value, checked across every deliverable.
Before an issue, deliverables get checked against each other by hand: the inter-discipline check that everyone runs out of time for. Raven's agents trace each shared value across the PFD, HMB, P&IDs, line list, isometrics, and datasheets, and flag where two documents disagree, showing both.
| Value | Documents | Finding |
|---|---|---|
| PFD flow vs HMB case 2 | PFD · HMB | consistent |
| Line 6"-CS-1204 size | line list · isometric | 6″ vs 4″ |
| PSV-201 set pressure | 3 documents | consistent |
| Nozzle N3 rating | vendor GA · datasheet | GA differs |
Datasheets drafted from the design data, in your templates.
Datasheet preparation is copying values out of the HMB, line list, and design basis into a template, tag after tag. Raven's agents fill your template with each value cited to its source, and list the inputs the documents don't contain instead of guessing them.
| Field | Value | Source |
|---|---|---|
| Rated flow | 220 m³/h | HMB case 2 |
| Design temp | 180 °C | HMB Rev C |
| Design pressure | 19.0 barg | design basis §3 |
| Minimum flow | not in the documents · needs input |
Package work from bid to handover, on the same documents.
TQ registers kept current
Each technical query linked to its clause, the vendor's answer, and the revision that closed it.
Vendor revisions re-checked
Each vendor document revision checked against the requisition as it arrives; values that moved backwards flagged.
The document list accounted for
Every document on the vendor document requirements list tracked, revision by revision, gaps chased before close-out.
Concessions with evidence
Concession and deviation requests assembled with the clauses and pages behind them.
Revisions propagated
A revised HMB case re-checked against every datasheet and deliverable that cites it.
Handover sets checked
Handover document sets checked for completeness and internal consistency before they reach the owner.
How a job starts here.
Most project teams start with one live package. Send the specification and the vendor offers from a bid on your desk; the comparison comes back with the deviations flagged, the technical queries drafted, and every flag citing its page.
Raven prepares and flags; it doesn't approve. Your engineers decide what stands, and nothing is issued without their sign-off.
What to send: The purchaser specification and datasheet, and each vendor's technical offer, for one package you are evaluating now. PDFs as received.
See Raven on your plant
A demo walks you through the jobs on this page, on your own documents. Or send one bid package: the specification and the offers, and the evaluation comes back with the deviations flagged.
