HAZOP and LOPA preparation from the P&IDs.
Before the HAZOP, somebody lists every node's equipment, instruments and valves by hand from marked-up P&IDs. Before the LOPA, the SIS scope on the drawings is supposed to match the SRS, the cause-and-effect matrix and the SIL determination report, and one of them always drifted in the last revision. You find out in the workshop, when nobody can trace a trip back to a SIF.
Three drawings included on a new account.
What you do today.
- Mark up the P&IDs into nodes and list the equipment, instruments and valves in each by hand
- 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
- Start over when the next P&ID revision lands
What changes with Tagsight.
- Get the equipment, instrument, valve and line registers off the P&ID set, with the sheet on every row, so each node's list starts filled
- Filter the instrument register to SIS-classified tags in one click
- Pull an existing cause-and-effect matrix into a sortable table
- Diff the SIS scope between two P&ID revisions for the revalidation memo
- Export the SIS subset as its own document set for the logic solver vendor
Where it fits in your week.
Two weeks before the HAZOP, the facilitator asks for every node's equipment, instruments and valves. Run the IFC P&IDs and every register row carries the drawing it came from, so each node's list is a filter on the drawings it covers instead of a day with a highlighter.
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.
Common questions
Does Tagsight run the HAZOP or the LOPA.
Does Tagsight understand SIS, BPCS, and trip-class designations.
Can the cause-and-effect matrix be exported separately.
Put it to work.
Before the HAZOP, somebody lists every node's equipment, instruments and valves by hand from marked-up P&IDs. Before the LOPA, the SIS scope on the drawings is supposed to match the SRS, the cause-and-effect matrix and the SIL determination report, and one of them always drifted in the last revision. You find out in the workshop, when nobody can trace a trip back to a SIF.
Three drawings included on a new account.