Every spec, every standard read before you price
From thousands of pages to structured data
A standard in one document, a service note contradicting it in another. Any one can be caught. Catching all of them, every time, is the problem.
Sour service parameters
Every valve tag, read against API, ASME and NACE.
Loonar pulls the trunnion ball, gate, check and globe scope out tag by tag, bore, pressure class, end connection, material, trim, fire-safe test and sour-service duty, with NACE MR0175, API 607 and the ASME flange standard cited to the page they came from. When the datasheet says ANSI900 and the line list says ANSI600, the conflict shows on the row instead of hiding on page 14.
Technical deviations
Every deviation identified, ready for your decision.
Loonar groups values against your qualified range, so sour service is one row covering forty-one items instead of forty-one checks: MR0103 against MR0175, duplex forgings you don't stock, an ANSI900 trunnion above range, each flagged as a deviation with its items and proof. Fugitive emissions the RFQ never mentions gets flagged as missing before it becomes an assumption.
The clause register
The terms read the same way as the specification.
Every clause in the operator's conditions is classified, risk rated and checked against your standard positions, page cited. Uncapped production loss, a forty-eight-month warranty tail on sour-service valves, a fifteen per cent delay cap on a turnaround schedule: the four clauses carrying real exposure surface above the twenty-six already aligned.
Explore solutions
The rest of the range.
See what Loonar reads in your package.
Book 30 minutes and bring a real oil and gas inquiry. We run your own package through Loonar and show you the requirement list it builds, every value carrying its page and the standard behind it.