Sour service, API, ASME read before you price
From package to work product
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 of the inquiry and lays it out tag by tag: bore, pressure class, end connection, body material, trim, fire-safe test and sour-service duty. NACE MR0175 sits beside API 607 and the ASME flange standard, and every value carries the page it came from. Where the datasheet says ANSI900 and the line list says ANSI600, the conflict is on the row, not buried on page 14.
Technical deviations
Seventy-one line items become twenty-three decisions.
Loonar groups the extracted values against your qualified range, so sour service is one row covering forty-one items rather than forty-one repeated checks. MR0103 against MR0175, duplex forgings you do not stock, an ANSI900 trunnion above your range: each one is a partial or full deviation with the items it affects and the register that proves it. Fugitive emissions the RFQ never mentions is 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 assessed against your standard positions, with the page behind it. Uncapped production loss, a forty-eight month warranty tail on sour-service valves, a fifteen per cent delay cap on a turnaround-driven schedule: the four clauses that carry real exposure surface above the twenty-six that are 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.