Safety Critical Element Management Manual

35
Restricted
EP 2009-9009
Appendix 2 - SAP specific requirements
SAP specific requirements (continued)
In Notification
Condition after Malfunction code Wells and some OpCos only
CMPT Priority
CMPT should be switched on for all Facilities Functional Locations
CMPT Likelihood
CMPT Consequence Severity
Used to determine task criticality of work order
Required End Date
Output of CMPT, used to populate LAFD of work order
Status
To be kept up to date on timely basis
In Work Order
Work Order Type
Use 72 FP; 72 FC; 72 WC 72 WP only
LAFD
Date used for compliance reporting, can be updated to deviation expiry date if the deviation approved
OLAFD
Original LAFD, cannot be changed
Status
To be kept up to date on timely basis

Safety Critical Element Management Manual
Appendix 3 - Guidance on SCE groups and minimum performance assurance levels This Appendix gives guidance for the correct allocation of
SCEs, identified in the HSE case as part of the HEMP, to SCE
groups. It also specifies, for each SCE group, the minimum level at which there shall be performance standards and acceptance criteria defined.
The performance standard templates contain two type of responses for the Assurance Value Yes/No: which is the least detailed approach, in which
“yes” = performance standard has been met and no performance standard has not been met, referenced against an explicit performance assurance measure such as Fire pump starts on demand Characteristic a quantitative measured result which is compared with the target value to automatically determine whether the acceptance criteria has been met.
For a few performance standards, it is acceptable to record the detailed results of the Assurance Tasks in an alternate system such as PACER or eWIMS, in which case it is mandatory to also record at least the high level results in SAP eg “Within
Specification”. These cases are clearly indicated as footnotes within each performance standard template, and this approach is not acceptable in any other cases.
Notes.
1. This is not intended as a pick list of SCEs, although it does provide typical equipment type examples by SCE group.
SCEs are only classed as such if their failure to perform could lead to the release of, or fail to limit the consequence of, a Major Hazard as defined in the bow-tie model as part of the HEMP. These examples are not intended to be exhaustive and are provided for illustration purposes only. Minimum Level means the least detailed position in the
Asset hierarchy application at a more detailed level would give additional granularity in the SCE Management but would take more effort to put in place and operate. In order to allow for continuous quality improvement, change control for this Appendix will follow the same process as for
SCE groups and performance standards (MIE2012.03
Management of Change for Identification of SCEs and
PS.doc).
EP 2009-9009
Restricted
36

Download 494.83 Kb.

Share with your friends: