Saudi Aramco.

An Aramco gas plant runs hundreds of P&ID sheets across BPCS, SIS, and FGS scopes that have to stay independent through every audit trail. SAES-J fixes the column shape. The input set fixes the workload.

Start a workspace See industries served

P&ID extraction for Aramco SAES projects.

Saudi Aramco projects run against SAES. Tagsight extracts I/O lists and instrument indexes with BPCS, SIS, and FGS separation per SAES-J family conventions.

Primary standard: Aramco SAES

Documentation expectations.

Instrument tags consistent with SAES-J-001, J-100 family conventions. Area code, unit code, loop number, function letters
I/O list segmented by signal class with explicit BPCS, SIS, FGS separation
Instrument index covering the full unit drawing set with tag uniqueness enforced
Equipment list keyed to vessels, pumps, compressors, and packaged skids per SAES equipment-tagging conventions
Line list with size, pipe spec, service, metallurgy, and insulation per SAES-L-150 line-numbering family
SIS instrument register filtered for IEC 61511 audit and SAES-J-601 SIS scope
FGS, fire and gas instrument register kept distinct from BPCS and SIS

Where Tagsight fits.

SAES-shaped tag conventions come through alongside ISA 5.1
BPCS, SIS, FGS scope segments cleanly onto separate Excel sheets for distinct sign-off paths
Off-page connector matching across multi-page Aramco drawing sets keeps cross-unit interlocks intact
Revision comparison produces the diff records SAEP MOC procedure expects
Image-based ingestion covers scanned legacy P&IDs from older Aramco asset documentation
Direct export to TIA Portal, Studio 5000, PLCCreator, DEXPI bypasses intermediate reformatting

Common questions

Does Tagsight handle Aramco SAES tag conventions.

Yes. SAES-shaped tags come through alongside ISA 5.1. The original tag string is preserved. Signal classification is driven by the second-letter function regardless of the area, unit, loop hierarchy in front of it.

Is Tagsight an Aramco-approved or registered vendor.

Tagsight is independent. This page describes how Tagsight outputs line up with the documentation Aramco SAES expects on contractor and in-house projects. It does not represent a partnership or vendor-approval status.

How is FGS scope handled distinctly from BPCS and SIS.

Tags flagged as FGS by prefix or annotation segment onto a separate sheet on Excel export. Filter by FGS-prefix conventions used at the facility, FG, GD, FT-FG, etc. And the SAES-J-601 audit register exports independently.

Can large multi-unit Aramco drawing sets process as a single workspace.

Yes. Multi-hundred-page drawing sets process page-by-page so review can begin on early pages while later pages are still working. Off-page connector matching keeps cross-unit signals tied together.

What about Arabic-language annotations on legacy drawings.

Most Aramco engineering drawings are produced in English per SAES practice. Tags, line numbers, and equipment labels come through from the English text on the drawing. Free-text Arabic annotations are among the rows you confirm in the review canvas.

Run it on your Saudi Aramco projects.

Upload the relevant P&IDs and export the Saudi Aramco-shaped instrument index and I/O list.

Start a workspace Pricing

Aramco SAES is referenced descriptively. Tagsight has no affiliation with Saudi Arabian Oil Company.

Documentation expectations.

Instrument tags consistent with SAES-J-001, J-100 family conventions. Area code, unit code, loop number, function letters

I/O list segmented by signal class with explicit BPCS, SIS, FGS separation

Instrument index covering the full unit drawing set with tag uniqueness enforced

Equipment list keyed to vessels, pumps, compressors, and packaged skids per SAES equipment-tagging conventions

Line list with size, pipe spec, service, metallurgy, and insulation per SAES-L-150 line-numbering family

SIS instrument register filtered for IEC 61511 audit and SAES-J-601 SIS scope

FGS, fire and gas instrument register kept distinct from BPCS and SIS

Where Tagsight fits.

SAES-shaped tag conventions come through alongside ISA 5.1

BPCS, SIS, FGS scope segments cleanly onto separate Excel sheets for distinct sign-off paths

Off-page connector matching across multi-page Aramco drawing sets keeps cross-unit interlocks intact

Revision comparison produces the diff records SAEP MOC procedure expects

Image-based ingestion covers scanned legacy P&IDs from older Aramco asset documentation

Direct export to TIA Portal, Studio 5000, PLCCreator, DEXPI bypasses intermediate reformatting