Verify SIS scope and SIL allocation against P&IDs.
Functional safety auditors do not trust spreadsheets. They want to walk a P&ID, find a SIL-classified tag, and trace it through the SRS, the proof-test record, and the as-built loop folder without the trail going stale between drawings.
Workflow.
- 01
Extract the full instrument scope
Run the P&ID set through Tagsight as you would for any I/O list extraction. The extraction does not pre-judge SIS scope. That comes next.
- 02
Filter the SIS subset
Tag prefixes, PSHH, PSLL, FSLL, TSHH, TAHH, LSLL flag SIS scope per the drawing convention. Filter the extracted set on those prefixes. The result is the SIS instrument inventory ready for SIL allocation review.
- 03
Reconcile against the SRS and proof-test register
Cross-reference the SIS instrument inventory against the safety requirement specification and the proof-test schedule. Surface tags that have a SIL allocation but no proof-test entry, or proof-test entries pointing at tags that no longer exist.
What you get.
- Filtered SIS instrument inventory with SIL allocations carried through
- Proof-test reconciliation report, allocations without tests, tests without allocations
- SRS-referenced loop folder data per SIS function
- Audit trail per tag. Source P&ID page, source region, review decisions
FAQ.
01Does Tagsight assign SIL.
No. SIL assignment is a process safety responsibility per IEC 61511, ISA 84, owned by the operating company. Tagsight extracts the tag and the SIS-prefix metadata. The SIL allocation comes from the SRS.02Can the SIS dataset be exported separately from the BPCS dataset.
Yes. Filter on the SIS-prefix tag set, export to a separate Excel workbook with its own audit trail. Keeps the scope boundary that 61511 requires in the controls architecture visible in the documentation.