Tagsight for process safety engineers.
The SIS scope on the P&IDs is supposed to match the SRS, the cause-and-effect matrix, and the SIL determination report. In practice, three of those four documents drifted in the last revision cycle and you only find out at the LOPA review when somebody points at a PSHH that nobody can trace back to a SIF.
What you do today.
- Highlight every SIS tag on the P&ID set, page by page
- Cross-walk those tags against the SRS, the SIF list, and the cause-and-effect matrix
- Find the inevitable mismatches, escalate to discipline leads, wait
- Re-issue the SIL determination after the next P&ID revision lands and start over
What changes with Tagsight.
- Filter the extracted instrument list to SIS-classified tags in one click
- Pull the cause-and-effect matrix from the same source drawing set into a sortable table
- Diff the SIS scope between two P&ID revisions for the SIL re-validation memo
- Surface PSH, PSHH, PSL, PSLL tags by trip-level so the LOPA reviewer can scope them in minutes
- Export the SIS subset as its own document set for the logic solver vendor
Where it fits in your week.
You are six weeks out from a LOPA workshop. Run the IFC P&IDs through Tagsight, filter for SIS tags, drop the result on the meeting room screen. The argument over what is in scope ends before it starts because everybody is reading the same list.
Auditor wants to see every SIF tag on the SRS traced back to a P&ID page. Tagsight carries the page reference on every extracted tag. The trace stops being a one-week spreadsheet exercise and becomes a filter operation.
Operations is asking which instruments have hardwired trips versus DCS interlocks. Pull the cause-and-effect matrix and the SIS subset from the same drawing set, show the split, hand the answer back the same day.
Common questions
Does Tagsight understand SIS, BPCS, and trip-class designations.
Can the cause-and-effect matrix be exported separately.
Put it to work.
The SIS scope on the P&IDs is supposed to match the SRS, the cause-and-effect matrix, and the SIL determination report. In practice, three of those four documents drifted in the last revision cycle and you only find out at the LOPA review when somebody points at a PSHH that nobody can trace back to a SIF.