Skip to main content
Zemerc
OPEPDeliver · Offshore & Marine Operations

Offshore Projects Execution Platform

A number is counted, not typed.

One governed system for executing an offshore project from fabrication and load-out through installation, commissioning and final handover, with reported positions derived from the underlying operational records.

OPEP project-controls view showing the current schedule revision, overdue and slipped activities, links to execution evidence, blocked work in the look-ahead period, and differences between claimed and evidenced progress
0Lifecycle modules
0Report definitions
0Controlled documents
0Organisation registers
Yard to handover

One project across yard, marine and offshore execution zones

OPEP maintains fabrication, marine execution and completions within one governed project lifecycle so schedule positions can be reconciled against supporting evidence.

Onshore
Load-out
Installation
Completions
Commissioning
Handover
Yard
Offshore
Handover
Stage 1 of 6 · Yard
Onshore

Yard fabrication covers work packs, work fronts, materials, labour, manufacturing and vendor scope against the project record.

In the application: Onshore execution
Evidence and reporting basis

Every reported figure is supported by an underlying record

Management and field reporting use the same governed registers, with unsupported figures reported as not measurable rather than invented.

Claimed progress compared with evidenced progress

Schedule position is reconciled against execution evidence so claimed-but-not-evidenced and evidenced-but-not-scheduled work remain distinct, actionable conditions.

Unsupported measures are reported as not measurable

Where supporting evidence is insufficient, the application reports the measure as unavailable rather than presenting zero or a positive result.

One governed register per record type

Equipment, personnel, companies, vessels and portfolios are maintained as shared project master records across relevant modules.

Inside OPEP

A non-conformance blocks only the scope to which it applies.

Blocking readiness, overdue work, failed inspections and items awaiting verification are separate governed states. A blocking record prevents the affected scope from progressing until the required condition is resolved.

OPEP quality view showing inspection and test plans, inspections, surveillance and non-conformance records, including blocking work, failed or overdue inspections, readiness constraints, items awaiting verification and ageing of open non-conformances

Open non-conformances are reported by age band so long-running items remain visible rather than being obscured by averages.

  • A verdict, not a slip
    Inspection outcome is distinct from schedule performance. Failed inspections and overdue inspections are recorded separately.
  • A blocking non-conformance remains open until the responsible party resolves the underlying issue and the required verification is completed.
    Closure by the originator alone is not sufficient.
  • Oldest open non-conformance reported by age
    The oldest open non-conformance is reported by age from its original raised date so long-running items remain visible.
Readiness

'Cannot be determined' is a distinct readiness state

Readiness reporting must distinguish failed criteria from criteria that cannot yet be assessed. OPEP retains 'cannot be determined' as a separate state rather than collapsing both conditions into 'not ready'.

It matters most at load-out, where the difference between “we checked and it is not ready” and “nobody checked” is the difference between a delayed sailing and an expensive one.

  1. Load-out readiness
    • Work packs complete
    • Cargo manifested
    • Certificates issued

    Where required supporting evidence is absent, readiness is reported as 'cannot be determined' rather than 'not ready'.

  2. Campaign readiness
    • Vessel available
    • Weather window
    • Approved lift plan

    Readiness is derived from governing registers rather than declared without supporting evidence.

  3. Mechanical completion
    • Check sheets
    • Punch by category
    • Inspection and test plans

    Completion percentage is derived from check-sheet records and remains traceable to its components.

  4. Ready for start-up
    • Commissioning tests
    • Non-conformances cleared
    • Turnover package

    A blocking non-conformance stops the scope to which it applies.

Capability architecture

Nine lifecycle modules organised around project execution

OPEP navigation is organised by project lifecycle stage, reflecting the sequence of offshore execution from yard through handover.

  • Project controls

    Work breakdown, activities, milestones, progress, variance, look-ahead and schedule revisions are reconciled against execution evidence rather than reported separately from it.

    • Projects
    • WBS
    • Activities
    • Milestones
    • Progress
    • Variance
    • Look-ahead
    • Reconciliation
    • Schedule revisions
  • Onshore execution

    Work packs and work fronts, materials, labour and areas through the fabrication yard, with manufacturing and vendor scope tracked against the same project record.

    • Work packs
    • Work fronts
    • Materials
    • Labour
    • Areas
    • Manufacturing
    • Vendors
  • Marine and logistics

    Cargo, load lists, manifests, warehouse movements and persons-on-board records support the operational readiness position for offshore campaigns.

    • Cargo
    • Load lists
    • Manifests
    • Warehouse
    • POB
    • Marine spreads
    • Vessels
  • Offshore installation

    Campaigns, lifts and installation sequence are governed with subsea scope, weather windows and vessel availability in the same project context.

    • Campaigns
    • Lifts
    • Sequence
    • Subsea
  • Completions and commissioning

    Systems, subsystems, tags, check sheets, punch items, certificates, turnover and readiness records continue through commissioning tests, packs, activities and start-up.

    • Systems
    • Subsystems
    • Tags
    • Check sheets
    • Punch
    • Certificates
    • Turnover
    • Readiness
    • Tests
    • Start-up
  • Daily execution and assurance

    Daily reports, diary, weather, constraints, actions and shift handover sit alongside incidents, observations, permits, inspections, investigations and environmental records.

    • Daily reports
    • Diary
    • Weather
    • Constraints
    • Actions
    • Handover
    • Incidents
    • Permits
    • Investigations
Where it runs

Yard, vessel and platform governed through one project record

OPEP supports offshore projects across oil and gas, LNG, offshore wind, power, subsea infrastructure, marine construction, offshore utilities and carbon-capture contexts where execution depends on weather, vessel availability and verified readiness.

  • Persons on board and crew rotation held with the campaign
  • Weather windows read against the lift plan
  • Daily reports, diary and shift handover retained as governed records
Governed data

Six organisation registers with defined identifiers and validation rules

Companies, equipment, personnel, portfolios, reference values and vessels each have defined identifiers, required fields and validation rules, with reference data configured to the organisation.

01Import reviewed

Imports remain uncommitted until reviewed and approved

Controlled data imports are previewed before approval and commit, while portable exports support full organisation-level extraction.

  • Progress counted from records rather than typed manually

    Every reported figure is derived from underlying records. Progress values exist because supporting check-sheet and execution records exist.

  • Not measurable is distinct from zero

    Where a figure cannot be derived, it is reported as not measurable rather than zero or a satisfactory result.

  • One governed register per record type

    Equipment, personnel, companies, vessels and portfolios are maintained in shared governed registers across relevant modules.

  • Claimed progress compared with evidenced progress

    Schedule position is reconciled against execution evidence so claimed-but-not-evidenced and evidenced-but-not-scheduled work remain distinct reportable conditions.

Also in OPEP

More of what the application covers

  • Schedule reconciliation against execution evidence
  • Look-ahead reporting showing blocked work within the next fourteen days
  • Weather windows held against the campaign
  • Persons on board and crew rotation
  • Shift handover as a governed record
  • Execution status covering attention, bottlenecks and readiness
  • Signed certificates among the controlled documents
  • Portable data extract covering the full organisation scope
OPEP

Review OPEP using one of your offshore campaigns.

Bring one campaign with work packs, load lists and check sheets. The demonstration will show schedule reconciliation against supporting evidence and the readiness position derived from the records.