Skip to main content
Zemerc
OPMSDeliver · Offshore & Marine Operations

Offshore Projects Management System

Offshore projects, governed from field records through portfolio reporting.

A governed project environment for offshore construction, commissioning and logistics, covering schedule, engineering and supply, field execution, marine spread, assurance and reporting, consolidated into a portfolio position.

0
Operational modules
0
Application screens
0
Controlled reports
0
Governed datasets
Why OPMS is used

One governed record with every figure recomputed from source data

Offshore departments often operate across separate daily reports, spreadsheets and management packs. OPMS provides one governed project record used by field, project-office and central reporting teams.

Daily operational data is recorded once at the point of work

Field and site representatives record crews, shifts, activities, constraints and photographs where work occurs. That daily entry becomes the governed operational record used by downstream reporting.

Productivity is calculated from governed records

Lost time is recorded as non-productive-time events against an approved taxonomy. Productive time is calculated as a ratio of sums and retains its numerator and denominator at each reporting scope.

Management reads the consolidated portfolio position

Each project issues a controlled central export. Ingestion validates the submission before the portfolio position is recomputed and management reporting is issued.

Controlled project flow

From portfolio scope to management reporting through one governed project record

Six stages across three operating zones. Records are captured once, calculated at project level and recomputed for portfolio reporting.

Portfolio scope
Schedule and plan
Engineering and supply
Field execution
Performance and assurance
Report and consolidate
Plan
Execute
Prove
Stage 1 of 6 · Plan
Portfolio scope

Projects, locations, work areas and work-breakdown structures are configured under administration, with role-based protection tiers and project scope.

In the application: Administration · Home
OPMS scope

Six capability groups supported by one governed project record

Nine operational modules are organised around offshore-project workflows and functional ownership.

One record, many readers

Nine modules operating from one governed project record

All modules read and write the same governed project record, so a productive-time figure shown in the executive view is derived from the same underlying records used in the daily operational view.

Construction management
Unrestricted
Reporting coordinator
Multi-project
Field / site representative
Single-project scope
QHSE
Unrestricted
Logistics and marine
One project
Commissioning
Multi-project
Central data custodian
Unrestricted
System administrator
Unrestricted

Eight roles across three access-protection tiers, with project scope defined for each role.

Project record
  • Execution
  • Supply chain
  • Performance
  • Project controls
  • Vessel
  • Readiness
  • Commissioning
  • Reporting
  • Central exchange
  • Recomputed, not carried
    Productive time is calculated as a ratio of sums at each scope; a portfolio value is not produced by averaging project percentages.
  • Attention includes age
    Constraints and exceptions retain target dates and ageing measures so priority reflects both significance and time outstanding.
  • Permission-gated
    Eight roles across three protection tiers, each with an explicit project scope.
Source of the governed record

Field teams record the day once; office teams use the same governed record

Crews, shifts, activities, constraints and photographs are recorded once at the work location. Project-office and portfolio figures are subsequently derived from the same governed daily records.

  • One governed daily record per project, location, date and shift
  • Amendments retain their history rather than replacing the earlier position
  • Constraints and exceptions retain target dates and ageing information
Readiness and commissioning

Readiness is assessed from governed records rather than declared without supporting evidence

System readiness is derived from supporting evidence. Where required criteria cannot be assessed, the result is reported as 'cannot be determined' rather than failed.

  1. Systemisation
    • Tag register
    • Systems register
    • Subsystem boundaries

    Scope is established before completion is measured against it.

  2. Mechanical completion
    • Inspection & test plans
    • Inspection requests
    • Punch list by category A and B

    Completion percentage is derived from check-sheet records rather than entered manually.

  3. Pre-commissioning
    • Test packs
    • Certificates
    • Preservation

    Preservation due dates are carried with the system they belong to.

  4. Turnover
    • Turnover packages
    • Dossiers and close-out
    • Handover state

    Handover is governed as an evidence-backed record rather than represented only by a planned date.

Governance and audit

Governed operational data is distinct from editable master data

Users, roles, projects, locations, work-breakdown structures, contractors and reference vocabularies change through governed approval paths, with append-only audit history.

  • Report and issue

    Controlled reports, management bulletins, archives, document control, transmittals, exceptions and actions are managed through governed reporting workflows.

  • Consolidate the portfolio

    Each project issues a controlled central export, ingestion validates it, submission compliance is tracked, and portfolio figures are recomputed from project-level components.

  • Keep the registers governed

    Actions, decisions, interfaces, risks, opportunities, change and data-quality records are retained with append-only audit history.

  • Governed operational data distinct from editable master data

    Users, roles, projects, locations, work-breakdown structures, contractors and reference vocabularies change through governed approval paths.

Also in OPMS

More of what the application covers

  • Governed import, templates, export, bulk update and historical migration
  • Tag register, systems register and completions
  • Certificates, test packs, turnover and closeout dossiers
  • Readiness assurance assessed from records
  • Submission tracking and central-exchange ingestion
  • Interfaces, risks and opportunities registers
  • Data-quality rules with accountable ownership
  • Append-only audit history behind controlled changes
Field and office

Field and office teams operate from one project record

Offshore · daily field input

Crews, shifts, activities, constraints and photographs recorded where the work is, with a tablet variant for daily field input.

Onshore · project and portfolio

The same daily record supports productive-time, lost-person-hour, reporting-compliance and overdue-constraint measures.

OPMS

Review OPMS using one of your project’s daily records

Bring one project’s daily field records. The demonstration will show productive-time measures, the consolidated portfolio position and the management bulletin derived from them.