BP.

BP RP and GP treat BPCS, SIS, and FGS as three distinct document sets, each with its own sheet, sign-off path, and instrument index subset. IEC 61511 lifecycle discipline sits inside the RP family rather than alongside it.

Start a workspace See industries served

P&ID extraction for BP RP and GP projects.

BP projects run against RP and GP. Tagsight extracts I/O lists, instrument indexes, equipment lists, and line lists with BPCS, SIS, and FGS separation.

Primary standard: BP RP, GP

Documentation expectations.

Instrument tag conventions consistent with BP RP, GP instrumentation family
I/O list with BPCS, SIS, FGS scope explicitly separated
Instrument index across the full drawing set with tag uniqueness enforced
Equipment list keyed to vessels, pumps, compressors, packaged skids
Line list with size, pipe class, service, metallurgy
SIS register filtered per IEC 61511, BP heavily references
FGS register kept distinct

Where Tagsight fits.

BP RP, GP-shaped tag conventions come through alongside ISA 5.1
BPCS, SIS, FGS segmentation onto separate Excel sheets
Off-page connector matching across multi-page upstream and refining drawing sets
Revision comparison feeds MOC change records under PSM and BP MOC procedure
Direct exports to TIA Portal, Studio 5000, PLCCreator, DEXPI
Image-based ingestion covers scanned legacy drawings from older BP-operated assets

Common questions

Does Tagsight handle BP RP, GP tag conventions.

Yes. BP RP, GP-shaped tags come through alongside ISA 5.1. The original tag string is kept verbatim.

Is Tagsight a BP-approved vendor.

Tagsight is independent. This page describes how Tagsight outputs line up with BP documentation expectations. It does not represent an approval, partnership, or registration.

How does Tagsight handle BP's renewables portfolio drawings, hydrogen, solar, wind.

ISA 5.1 and dialect-permissive variants come through regardless of sector. Renewables and hydrogen drawings produce the same structured output as oil and gas drawings.

Can the export support OSHA PSM MOC documentation.

Yes. Revision comparison produces an added, removed, modified diff suitable as supporting evidence in a PSM MOC package.

Run it on your BP projects.

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

Start a workspace Pricing

BP RP and GP are referenced descriptively. Tagsight has no affiliation with BP plc.

Documentation expectations.

Instrument tag conventions consistent with BP RP, GP instrumentation family

I/O list with BPCS, SIS, FGS scope explicitly separated

Instrument index across the full drawing set with tag uniqueness enforced

Equipment list keyed to vessels, pumps, compressors, packaged skids

Line list with size, pipe class, service, metallurgy

SIS register filtered per IEC 61511, BP heavily references

FGS register kept distinct

Where Tagsight fits.

BP RP, GP-shaped tag conventions come through alongside ISA 5.1

BPCS, SIS, FGS segmentation onto separate Excel sheets

Off-page connector matching across multi-page upstream and refining drawing sets

Revision comparison feeds MOC change records under PSM and BP MOC procedure

Direct exports to TIA Portal, Studio 5000, PLCCreator, DEXPI

Image-based ingestion covers scanned legacy drawings from older BP-operated assets