SPEX MFV - Simultaneous Operations

• Document No.

• Audit Title

• Client / Site

• Conducted on

  Date

• Prepared by

• Location
  Address

• Personnel

Notes for Site Visits conducted as required by Project HSSE Plan Team Leader is responsible for report generation and submission Site Host is given direct feedback of visit outcomes before visiting team leaves the site MFV Leader agrees "SMART" actions with site host Host holds responsibility to follow up on agreed actions. Visit reports are recorded on site visit template only (this record) All completed site visit reports to be sent to the Project HSSE Coordinator for filing in Livelink - clearly handwritten reports are acceptable for submission. Visit record not marked as completed (Green) until visit report is submitted. Next MFV team uses past reports for part of their visit, following up on completions of previous actions.

• SIMOPS risks are identified and controls are set for all projects prior to mobilising multiple parties to the worksite and executing any works in a live environment.

  Yes

  No

  N/A

• All projects working under Shell HSE-MS or where Shell has ultimate responsibility must have a common Permit to Work system in place, led by one single authority, which controls all project organisations and activities and their interfaces

  Yes

  No

  N/A

• High risk interfaces are strictly controlled through the Permit to Work system.

  Yes

  No

  N/A

• Competent supervisors, identified in the Permit to Work, with authority on the involved organizations, are available in the field at all times to manage SIMOPS activities.

  Yes

  No

  N/A

• Formal communication sessions are agreed and are being implemented (such as interface meetings, tool box talks).

  Yes

  No

  N/A

• Plans are completed daily for the coming activities, identifying areas and systems affected, and then formally communicated to the Permit to Work Lead as a minimum the day before the activity start date.

  Yes

  No

  N/A

• SIMOPS activities are executed based on permit conditions defined by the Permit to Work Lead, ranging from temporary cancelation of the activity, to different timeframes or specific site controls.

  Yes

  No

  N/A

• Daily approved site activities by areas and systems are communicated and visible to relevant parties in established locations. (i.e. site permit office).<br>

  Yes

  No

  N/A

• Projects executed within other assets must be fully aligned and integrated with local SIMOPS procedures.

  Yes

  No

  N/A