Petroleum Development Oman L. L. C. Document Title: Specification for hse cases



Download 1.14 Mb.
Page9/26
Date20.10.2016
Size1.14 Mb.
#5176
1   ...   5   6   7   8   9   10   11   12   ...   26

11.3Performance Standards


A Performance Standard is a statement, which can be expressed in qualitative or quantitative terms, of the functional performance required of a SCE, and which is used as the basis for managing the risk from the Major Hazards. Defining and ensuring compliance with suitable Performance Standards provides assurance that the SCE is and will remain a barrier to the identified MAH.

Generally, the SCEs and Performance Standards follow a one-to-one relationship where each SCE has its own Performance Standard.

Performance Standards are used as the basis for design and technical (operational) integrity verification and are expressed in terms of functionality, availability, reliability, survivability and dependencies/interactions with other SCEs.

Functionality

Functionality is an expression used to define what the system or equipment is required to achieve in order to ensure design integrity.



Reliability and Availability

Reliability is defined as the required probability that the system or equipment will operate on demand, when required.

Availability is defined as the extent to which the system or equipment is required in order to retain its functional integrity.

Survivability

Survivability defines the external loading events such as fires, explosions or extreme weather, associated with the various MAHs against which the system or equipment is required to retain its functional integrity.



Dependencies and Interactions

This is used to identify other systems or equipment that are critical to the functionality of the primary system or equipment. By identifying these dependencies and interactions it is ensured that all interfaces have been covered.

There are two types of Performance standards;


  • Design Performance Standards. Design Performance Standards must be developed during the Define phase. They shall provide a list of key functional criteria to which the SCE must comply with during the design. In practice the content of the performance standards will be largely taken from the design and engineering standards that apply to the item or SCE. However, other information may be taken from the basis for design, the design philosophies, or the results of workshops and HEMP Studies such as HAZID/HAZOP, Design Review, Layout Reviews, Fire & Explosion Analysis, QRA, IPF, SAFOP, etc.

The Design Performance Standards will mature further during the execute phase and will check that the SCEs have been constructed as designed. The existing QA/QC procedures and practices should be used to support the Design Performance Standards. The design must take into account operational demands so that suitability can be ensured into the operate phase.

The Design Performance Standards will evolve into Operate phase Performance Standards at the end of the execute phase before handover.



  • Operations Performance Standards. The Operate phase Performance Standards for SCE’s should evolve from the Design Performance Standards. These Performance Standards are formatted to comply with the requirements of SAP-PM and SAP-QM in terms of minimum assurance tasks, assurance measures, assurance value and units of measure for the correct allocation to the appropriate level in the asset hierarchy.

Examples of the two types of Performance Standard are provided in 27 and 28, respectively.

11.3.1Performance Standard Approval


Each performance standard is allocated an ‘owner’. The owner is responsible for ensuring that the content of the performance standard is appropriate and achievable. The performance standard owner is normally the CFDH for the items covered by the SCE. However, the CFDH may delegate the review and approval of their performance standards to the relevant TA2.

12HSE CRITICAL TASKS


An HSE Critical Tasks is one that is in place to develop, implement or maintain the effectiveness and integrity of a Barrier, Escalation Factor Control or Recovery Measure Control in the MAH bow-ties.

An HSE Critical Position are those that execute HSE critical tasks.

The minimum information required for a HSE critical task shall be:


  • The description and purpose of the HSE critical task required

  • The person (position and reference indicator) responsible for performing each task

  • Reference to supporting documentation, e.g. work instructions, SAP, procedure, etc

  • The method and criteria to verify that the task is performed as required to maintain barrier effectiveness.

HSE critical tasks should be developed to the level of the party responsible for ensuring that tasks are completed on time and to the required standard, e.g. Managers, Supervisors and Specialists – the position responsible for ensuring that the task is done and not the person who is actually undertaking the work.

Bow-tie XP software enables the HSE critical tasks to be linked to the relevant barriers.

Inspections and preventative maintenance activities for hardware SCEs are implemented via the Maintenance Management System, i.e. SAP. The task information is contained within the task description in SAP for all SCE barriers and is NOT listed as an HSE critical task, and is considered part of the hardware barrier itself. This applies to for example maintenance and calibration of a gas detector.

Implementation tables shall be developed for each HSE Critical Position. The implementation tables describe each HSE Critical Task, its supporting business controls and the business records required to verify that the task is being adequately executed. The implementation tables also provide a link to relevant barriers (HSE Critical Activities) and hazards on the Bow-Tie diagrams.

See 29 for an example extract from an Implementation table. Communication of HSE Critical tasks to affected people in affected position is the responsibility of the HSE Case Custodian.



Download 1.14 Mb.

Share with your friends:
1   ...   5   6   7   8   9   10   11   12   ...   26




The database is protected by copyright ©ininet.org 2024
send message

    Main page