SIS Master Register
SIS Master Register
Please share your best practices to keep an SIS master register, and its use during operation, incident management, and other areas.
Re: SIS Master Register
Maintaining this register isn't just a documentation task; it is a critical requirement for compliance with standards like IEC 61511, to say the least.
In my opinion, a master register should be dynamic (reviewed & updated at a fixed frequency + linked with MOC update when needed), accessible, and rigorously controlled.
I would emphasize on the following as the best practices to maintain one.
Centralized Ownership: Assign a "Data Custodian" (usually a Lead IC or Process Safety Engineer). Unauthorized edits should be impossible.
Comprehensive Data Fields: At a minimum, each entry should include:
Digital Integration: Ideally, the register should be linked to your Asset Management System (AMS) or CMMS (like SAP or Maximo) to ensure maintenance triggers match the design intent.
In my opinion, a master register should be dynamic (reviewed & updated at a fixed frequency + linked with MOC update when needed), accessible, and rigorously controlled.
I would emphasize on the following as the best practices to maintain one.
Centralized Ownership: Assign a "Data Custodian" (usually a Lead IC or Process Safety Engineer). Unauthorized edits should be impossible.
Comprehensive Data Fields: At a minimum, each entry should include:
- SIF ID & Description: What is the specific hazard being mitigated?
- SIL Rating: The required Safety Integrity Level (SIL 1, 2, or 3).
- Logic Description: Detailed "Cause and Effect" relationships.
- Device Tags: All sensors, logic solvers, and final elements (valves/breakers).
- Trip Setpoints: The exact process values that trigger the SIF.
- Proof Test Intervals: How often the system must be manually tested to maintain its SIL.
Digital Integration: Ideally, the register should be linked to your Asset Management System (AMS) or CMMS (like SAP or Maximo) to ensure maintenance triggers match the design intent.
Re: SIS Master Register
There is no doubt about the criticality of having SIL in place and all valid. The issues normally fall the file gets outdated after MOC, having and excel with no control, missing bypass tracking, no link to SRS, wrong SIL values (VERY dangerous) and eventually no ownership.
Re: SIS Master Register
The interesting part here is that IEC 61511 doesn’t say to actually create an SIS Master Register.
What is does say is to track all SIFs, maintain lifecycle data, control changes, monitor performance, manage bypasses. And that all one cannot do without having a register in place.
What is does say is to track all SIFs, maintain lifecycle data, control changes, monitor performance, manage bypasses. And that all one cannot do without having a register in place.