NewDrawing Checker and CRS Builder · drawings back marked up, comments back as a finished CRS

ProductsCodeSyncDelivered

Code conflicts, found in a day, not a month.

CodeSync compares a client’s standard with the ASME, API and PIP codes it sits on: text, drawings and tables. Both clauses quoted, with clause number and page, and the action to take under the code that governs.

Client standard§6.3.2 · p. 41

Clause 6.3.2Nozzle necks NPS 2 and below: Sch 160 minimum.

Code it sits on§4.6 · p. 12

Clause 4.6Nozzle necks NPS 2 and below: Sch 80 minimum.
Stricter clauseSample · clause text shortened

Client standard §6.3.2 (p. 41) asks for more than the code, §4.6 (p. 12).

Action: the stricter clause governs. Specify Sch 160 for NPS 2 and below.

Sample comparison
1The case study
120 h → 8 h

to cross-check a client standard against PIP: four weeks down to one day.

6

critical conflicts, found across 200+ pages and 175+ requirements.

~$760K

estimated saving on a single project.

Case study: a client standard against the PIP STE/STF series; client name withheld. The 120-to-8-hour comparison and the ~$760K saving are from that case study; the saving is an estimate.

2How it sorts

Every requirement, in one of four piles.

Contradictions

The two documents say different things. Both clauses quoted, with the action to take.

Stricter clauses

The client asks for more than the code. You see which one governs.

Only in one

A requirement found in one document only, so it is not missed.

Needs an engineer

Items that need judgment are set aside for review, not decided.

3How it works

Weeks of reading, done in a day.

1

Upload

The client’s standard, and the codes it sits on.

2

Matched, clause by clause

Text, drawings and tables. Every requirement found and set against its counterpart.

3

Sorted and quoted

Four piles, both clauses quoted with clause number and page, and the action to take.

4Questions

What compliance leads ask first.

Which codes does it compare against?

The ASME, API and PIP codes a client standard sits on.

Only the text?

No: text, drawings and tables.

What does the output look like?

Every requirement sorted into contradictions, stricter clauses, requirements found in only one document, and items that need an engineer’s review. Each conflict quotes both clauses, with clause number and page, and the action to take under the code that governs.

Who decides what to do?

An engineer. CodeSync finds and quotes; items that need judgment are sorted out for review, not decided.

What happens to our standards?

Records sit in your own database, files are deleted when the run ends, and an administrator approves every account.

Next step

Send us a client standard.

We’ll set it against the codes it sits on and show you every conflict, both clauses quoted.