Digitize ISA-20 instrument datasheets for procurement and asset records.

ISA-20 datasheets carry the instrument-by-instrument specification procurement sends to vendors for quote. On any reasonably-sized project there are hundreds, and re-typing them into a spec database is three weeks of junior-engineer time with typos in the materials-of-construction column.

Start a workspace See pricing

Workflow.

01
Upload the datasheet set
Single sheet, batched workbook, or a folder of mixed PDF spec sheets. Each page routes to the right extractor by document type. Non-datasheet pages route to their own extractors so a mixed handover package processes as one upload.
02
Sectional extraction
Each datasheet decomposes into ISA-20 sections. Identification, process conditions, performance, materials of construction, certifications, accessories, vendor fill. Vendor-fill cells stay flagged on the structured output so procurement can see what the vendor still has to provide.
03
Export to the procurement format
Excel workbook in the canonical ISA-20 layout, with vendor-fill cells highlighted and identifying metadata at the top. CSV for material-master imports. JSON for vendor-portal integrations.

What you get.

Structured records per instrument. Identification, process, performance, materials, certifications
Vendor-fill column highlighted on output for procurement inquiry
Materials-of-construction roll-up across the datasheet set for spec-class consistency review
ATEX, IECEx, FM, CSA, SIL, and IP-rating summary across the instrument set

FAQ.

01Do legacy non-ISA-20 datasheet formats work.
Yes. Datasheet conventions beyond ISA-20 are supported, and unrecognised columns ingest as free-form fields preserved on output. The structured spine of the record stays consistent across formats so spec-class roll-ups still work.
02Some sheets have hand-written vendor data filled in after award. Does that affect extraction.
Hand-written vendor entries read with reduced confidence and surface as flagged cells for human review on the workbook output. They never silently overwrite typed values from the original spec.

Related

AudienceFor Controls Engineers TemplateISA 5.1 Cheat Sheet, PDF ConvertP&ID to instrument index

Digitize ISA-20 instrument datasheets for procurement and asset records.

Workflow.

Upload the datasheet set

Single sheet, batched workbook, or a folder of mixed PDF spec sheets. Each page routes to the right extractor by document type. Non-datasheet pages route to their own extractors so a mixed handover package processes as one upload.

Sectional extraction

Each datasheet decomposes into ISA-20 sections. Identification, process conditions, performance, materials of construction, certifications, accessories, vendor fill. Vendor-fill cells stay flagged on the structured output so procurement can see what the vendor still has to provide.

Export to the procurement format

Excel workbook in the canonical ISA-20 layout, with vendor-fill cells highlighted and identifying metadata at the top. CSV for material-master imports. JSON for vendor-portal integrations.

What you get.

Structured records per instrument. Identification, process, performance, materials, certifications

Vendor-fill column highlighted on output for procurement inquiry

Materials-of-construction roll-up across the datasheet set for spec-class consistency review

ATEX, IECEx, FM, CSA, SIL, and IP-rating summary across the instrument set

FAQ.

01Do legacy non-ISA-20 datasheet formats work.

Yes. Datasheet conventions beyond ISA-20 are supported, and unrecognised columns ingest as free-form fields preserved on output. The structured spine of the record stays consistent across formats so spec-class roll-ups still work.

02Some sheets have hand-written vendor data filled in after award. Does that affect extraction.

Hand-written vendor entries read with reduced confidence and surface as flagged cells for human review on the workbook output. They never silently overwrite typed values from the original spec.