OdysseyGPT

Case study

Case study: a 113-field valve data sheet checked against a 7-document customer package

An engineered-valve manufacturer that makes severe-service isolation valves ran one equipment data sheet against a customer package with OdysseyGPT. The customer is not named.

By Ademola Afolabi, Founder, New Odyssey Ltd · Last reviewed:

The short answer

An engineered-valve manufacturer checked a 113-field equipment data sheet against a 7-document customer package. OdysseyGPT ran 1,974 requirement checks in about 10.5 minutes, read every page in both directions, and cited every verdict to a document and page, for engineers to review.

Key Takeaways

  • 113 data sheet fields, 7 customer documents, 1,974 requirement checks.
  • About 10.5 minutes from start to finished checks.
  • Every page read in both directions: the customer's requirements against the data sheet, and the data sheet against the package.
  • Every verdict cited to a document and page, so an engineer can open the source.

The customer and the job

The customer makes engineered, severe-service isolation valves. The job was a common one: check one equipment data sheet, with 113 fields, against a customer package of 7 documents before answering.

What was run

Result
Data sheet fields113
Customer documents7
Requirement checks1,974
TimeAbout 10.5 minutes
DirectionEvery page, both directions
CitationsEvery verdict cited to a document and page

Examples of what it found

Five checks from the run, anonymised. Each verdict came with the document and page it was read from.

CheckWhat was comparedVerdict
Design pressure and temperatureDesign 10.75 barg at 191 °C against a MAWP of 12.47 barg at 196 °CExceeds
Minimum design metal temperature−15 °C against 5 °F (−15 °C), read across unitsMeets
Noise85 dB(A) meets a "max 85 dB(A)" requirement but falls short of a "lower than 85 dB(A)" oneMeets one wording, falls short of the other
CE markingA declaration of conformity to 2014/29/EU against "PED (CE)"Falls short
Hazardous areaZone 2 IIC T4 against "Other (see notes)"Falls short

The noise row is the kind a tired reader misses: the same number passes one clause and fails another, because the wording differs. The CE and hazardous-area rows are gaps an engineer then has to resolve with the customer.

What happens to the findings

The verdicts are a draft. An engineer opens the cited page, decides each open item and writes the deviations and clarifications. OdysseyGPT sends nothing to the customer.

For the method, see the technical deviation list guide and OdysseyGPT for manufacturing. The tool used was Document Review. OdysseyGPT Managed is from $999/month (USD), with onboarding included.

Try it on your own documents

Free sample: a cited compliance matrix

Send one spec package and your datasheets. Get a cited compliance matrix within 48 hours.

Get the free result

Frequently asked questions

How long did the review take?

About 10.5 minutes for 1,974 requirement checks across a 113-field data sheet and a 7-document customer package. The verdicts are a draft for engineers to review.

Who was the customer?

An engineered-valve manufacturer that makes severe-service isolation valves. The case study is anonymised.

Did OdysseyGPT decide the deviations?

No. It drafts a cited verdict for each check. Engineers decide each open item and write what goes to the customer.

Related Pages