For isolation valve package QC
Audit valve packages faster — ITP, heats, and Data Book in one place.
Organize inspection requirements by component and trace BOM heat numbers against your project Data Book with cited evidence pages.
- API 6D
- /API 598
- /ASME B16.34
- /NACE MR0175
Coverage matrix
Project A-2241
| Component / Heat | Chem | Mech | NDE | Cert |
|---|---|---|---|---|
| BodyH-44219A | ||||
| BonnetH-44219B | ||||
| StemH-50112 | — | |||
| BallH-50488 | — | — | ||
| SeatH-50488 | — | — |
Bonnet H-44219B → NDE missing · expected MT report
01 · How it works
From Data Book upload to cited coverage — in one workspace.
- 01
Sign in & create a project
Spin up a project workspace for each valve package. Your files stay scoped to the project.
- 02
Upload the vendor Data Book
Drop in MTRs, NDE reports, certs, and test charts. Document AI indexes pages for citation.
- 03
Organize the ITP by component
Upload one or more ITPs. We group inspection requirements into Body, Bonnet, Stem, and more.
- 04
Run traceability & review coverage
Upload the BOM, match heat numbers to evidence pages, and see expected vs. found in one matrix.
02 · What you get
Audit-ready output, not AI guesswork.
Every coverage finding points back to a heat number and a specific page. Hold-points and gaps are explicit, not buried.
ITP organized by component
Inspection requirements grouped automatically — Body, Bonnet, Stem, Ball, Seat, trim, fasteners.
Heat-level traceability
Every BOM line resolved to its heat number and matched against MTRs in the Data Book.
Expected vs. missing reports
A coverage matrix shows chemical, mechanical, NDE, and certificate evidence per heat — at a glance.
Page-level evidence citations
Every confirmed report links to the exact page in the Data Book. No more hunting through PDFs.
Beta — scoped & private
Documents stay within your project workspace. No cross-project sharing.
Cited evidence, not guesses
Every match links to the source page in the Data Book.
Document AI under the hood
Parsing and extraction tuned for technical PDFs and MTRs.
03 · FAQ
Common questions
Quick answers about projects, documents, and how Package QC review fits your workflow.
What is Package QC review?
A single workspace per project where you organize ITP inspection rows by component (Body, Bonnet, Stem, and more), upload a BOM or part list, trace heat numbers through your Data Book, and review a coverage matrix of expected vs. found reports with page citations.
What do I need before I start?
An account, a project, and searchable PDFs for your vendor Data Book (text-based or OCR’d). You’ll also upload one or more ITP PDFs and a BOM/part list PDF for heat traceability. API keys for document parsing and AI are configured on the server by your administrator.
Where are my files stored?
Each project keeps its own Data Book, indexes, and caches under your user workspace on the server. Files are not shared across projects or other users.
How does heat traceability work?
The app extracts heat numbers from your BOM, splits batched strings when needed (e.g. combined heats on one line), searches indexed Data Book pages by keyword and vector similarity, and tags pages by report type (chemical, mechanical, NDE, certificates, and more). Results link to specific file names and page numbers.
Does the ITP matrix replace reading the ITP?
No. The organized ITP and coverage matrix are decision support. The ITP remains the master requirement; use cited Data Book pages to verify evidence before release or hold decisions.
Why does organize or traceability take a while?
First runs parse PDFs and may build a search index over the full Data Book. Re-running with the same files is faster when caches apply. Large Data Books and many unique heats increase processing time.
What standards does the tool reference?
The workflow is built for isolation valve packages and common QC practice (API 6D, API 598, ASME B16.34, NACE MR0175 / ISO 15156 where applicable). Your contract ITP and purchaser specs always govern.
Is this production-ready?
The app is in beta. Expect iterative improvements; always perform independent QC on critical hold points, pressure test records, and material traceability before shipment or final acceptance.
Where are my documents stored and who can access them?
Files for each project live on the application server under your user account (not in a public git repo). Only your signed-in account can access your projects via the API. Use project delete to remove on-disk Data Books, indexes, and caches for that project.
Are my PDFs sent to third-party AI services?
Yes, for parsing and organization. Uploaded ITPs and Data Book pages are processed using document AI services (LlamaCloud for parsing and Google Gemini for embeddings and ITP organization) configured on the server. See the Privacy page for details and operator responsibilities.
How do I delete my project data?
On the Projects screen, use Delete project to remove the project record and all files under that project workspace. This does not delete your user account.
04 · Get started
Run your first Package QC review today.
Create a project, upload your Data Book, and walk through ITP organization, BOM traceability, and coverage in one session.