Skip to main content
Zemerc
Deliver · Offshore & Marine Operations

From yard to offshore execution, through one governed record.

Offshore projects, vessel fleets and campaigns operate from daily records shared by office and field teams.

3
Applications
5
Stages in the flow
Why this area

Counted separately, never blended

Offshore projects, vessel fleets and campaigns operate from daily records shared by office and field teams.

  • Counted separately, never blended

    Outstanding work is counted per register and per age; a gate is ready, not ready, or cannot be determined.

  • Weather hold remains distinct from other delay

    Lost hours are recorded by activity and cause because commercial and operational analysis depends on the distinction.

  • Field entry and office view

    Daily data is entered on a mobile device against the vessel and reporting period, into the same record used by the office.

How the work moves

5 stages, each owned by an application.

Each stage shown here is supported by a Zemerc application, and every application remains independently operable. Operating areas are a way to understand related work, not a mandatory commercial bundle.

Office
Field
Project record
Readiness gate
Offshore execution
Fleet & campaign
Portfolio view
Stage 1 of 5OPEP
Project record

Fabrication through commissioning in one governed record.

Inside the application

OPEP: Offshore Projects Execution Platform

Offshore-project execution from fabrication through commissioning and handover, with status derived from governed 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

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

  • Progress counted from records rather than typed manually
    Every reported figure is derived from supporting records, and unsupported measures are reported as not measurable rather than zero.
  • One master record per
    entity. Equipment, personnel, companies and vessels are maintained once and reused across relevant modules, ensuring consistent identification.
  • Identify blocked work fourteen days ahead
    The look-ahead identifies blocked work within the next fourteen days so intervention can occur before the execution window closes.
How the record moves

Yard, vessel and platform governed through one project record.

Offshore projects may use separate systems for fabrication, marine execution and completions. The handovers between them create material schedule, cost and readiness risk.

  1. Onshore execution
    Marine and logistics

    Work packs and cargo form a controlled load list against the planned sailing date

  2. Marine and logistics
    Offshore installation

    A campaign is read against weather windows and vessel availability

  3. Offshore installation
    Commissioning

    Systems, check sheets and certificates carry through to start-up

Offshore · daily operational record

Bring one campaign or one vessel-month record.

The operational day is recorded once at the point of work. Project-office and portfolio views are derived from that record rather than recreated through transcription.

  • Execution status derived from governed records; Seven governed registers summarised in one view, with ageing and gate readiness shown alongside them.
  • Separate applications, one area; OPEP, OPMS and VMT are distinct applications; none replaces another.
  • Offline field capture; VMT records daily operations as a PWA when network connectivity is unavailable.
Offshore assurance

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

Blocking readiness, overdue work, failed inspections and verification outstanding are separate governed states derived from the underlying registers. A failed inspection represents a technical outcome; a late inspection represents a schedule condition, and the application keeps those positions distinct.

  • Open non-conformances reported by age band rather than averaged
  • A blocking record is resolved by the responsible party rather than closed by its originator.
  • Readiness assessed from records, with 'cannot be determined' kept distinct from 'not ready'
Marine · supporting spread

Where this operating area is managed in practice

Vessels, charters, crew and persons on board are governed within the project record, allowing weather windows and lift plans to be assessed together.

  • Evidence-based overrides; A gate override is recorded against the evidence it overrides.
Questions we are asked

Before the first working session

  • Which applications belong here?

    OPEP (offshore project execution), OPMS (portfolio consolidation), VMT (fleet).

  • Are OPEP and VMT the same application?

    No. OPEP is project-rooted and VMT is vessel-rooted. Each application is independently operable and adopted separately.

  • What does the field team use?

    Mobile daily data entry uses the same governed record viewed by the office.

  • Execution status derived from governed records

    Seven governed registers summarised in one view, with ageing and gate readiness shown alongside them.

  • Separate applications, one area

    OPEP, OPMS and VMT are distinct applications; none replaces another.

  • Offline field capture

    VMT records daily operations as a PWA when network connectivity is unavailable.

  • Evidence-based overrides

    A gate override is recorded against the evidence it overrides.

OPEP

Bring one campaign or one vessel-month record

The demonstration will show the governed execution record from field entry through office reporting.