# data[].attributes.headline
5.0 Emergency / Contingency Arrangements

# data[].attributes.subject
5.0 Emergency / Contingency Arrangements

# data[].attributes.body
1. integration into Fire detection and fire suppression systems to be proven and implemented

2. Escape routes to align with Rig EES

# data[].attributes.body
Normally each Option would be considered within its own SCR or as an Annex to the Main Gate SCR. In this instances however, capture a summary of the options that you have discounted, and detail the safety aspects that prevented this option being considered. These safety aspects could be linked to physical hazards or an inability to meet the safety programme.

Option 2 - failed to be complaint against operating pressures and time to shutdown.

Option 1 - failed to be complaint with Noise regulations

# data[].attributes.body
Identify any systems that interface with the Oil SSTS, and identify any potential safety aspects that should be considered.

# data[].attributes.body
Identify any evidence e.g. past incidents, part experience, etc that could undermine the Oil SSTS SCR and describe the activities that have taken place to address these issues.

1. as this is to integrated into an existing system, changes to whole system operating instructions need to be updated.

2. Review of existing platform Hazard log to be undertaken to ensure integration of SSTS does not introduce any uncontrol new hazards

# data[].attributes.body
Capture any certificates that the Oil SSTS has or will have, and any associated restrictions/exemptions.

# data[].attributes.body
Capture any issues of particular sensitivity, e.g. use of restricted materials

# data[].attributes.body
posed by the Oil SSTS – Capture the residual risk anticipated to be posed by the Oil SSTS, this will make reference back to your hazard log and risk matrix.

# data[].attributes.body
Capture any risk management actions that are outstanding, and identify both the risk and the organisation responsible for its management.

# data[].attributes.body
This section would normally be populated, however for the purpose of this workshop please leave this section blank.

# data[].attributes.body
Residual risk, over filling of storage, and flooding of Separator, due to wellhead and storage filling valves failing open.

Additional operational requirements: regular monitoring of valve condition, monitoring of storage volume, and operation of separator.

Limit processing to 80% of storage volume, not start processing again until storage below 20% volume

# data[].attributes.body
Provide an argument why you think you ready for Initial Gate, and that the potential safety risks associated with the Oil SSTS are understood and that you have a strategy for controlling them.

SCR - MG

1. Initial design proposal is 80% complaint, with modifications and additional safe guards (See Hazard log) design can be made compliant.

# data[].attributes.body
Capture a summary of the key safety hazards and likely accidents related to the system. At initial gate, the safety hazards could be linked to the function of the system, as defined in the URD. Hazards will need to be mitigated using solutions captured in the System Requirements Document.

# data[].attributes.body
Capture the principle safety requirements identified for the system. These requirements will be developed and then incorporated into the System Requirement Document, to ensure safety is captured in the design.

# data[].attributes.body
Capture any areas of project risk, that could undermine your safety strategy and achieving the safety milestones. Each risk should be accompanied by a strategy how it will be mitigated

# data[].attributes.body
Capture how the project is progressing against the defined safety management plan

# data[].attributes.body
Capture any assumptions that underpin the safety case for main gate, this could include assumptions about the scope, safety requirements, operational profiles, time in service, operating environment etc. This list will be different from the Initial Gate SCR because you now have more technical information

# data[].attributes.body
Capture a brief description of your preferred solution, with sufficient details that the reader understands the boundary and the scope of the safety case (People, Equipment, Activity and Organisation), and interfaces with other safety cases.