Offshore Projects Management System
Offshore projects, governed from the field up.
One controlled project environment for an offshore construction, commissioning and logistics department: schedule, engineering and supply, field execution, the marine spread, assurance and reporting; consolidated into a portfolio position management can act on.
- 0
- Operational modules
- 0
- Application screens
- 0
- Controlled reports
- 0
- Governed datasets
One governed record. Every figure recomputed, never retyped.
Offshore departments run on daily reports, spreadsheets and management packs that disagree with each other. OPMS replaces them with one project record that the deck, the project office and the centre all read.
The day is entered once
A field or site representative records crews, shifts, activities, constraints and photographs where the work is. That entry is the record; nothing is transcribed later.
Productivity is computed, not declared
Lost time is logged as non-productive-time events against a governed taxonomy. Productive time is a ratio of sums, carried with its numerator and denominator at every scope.
Management reads the portfolio
Each project issues a central export, ingestion validates it, and the portfolio position is recomputed from components before the management bulletin issues.
From portfolio scope to the management bulletin, on one record.
Six stages in three zones, each a group of pages in the application. The record enters once, is computed at the project and recomputed at the centre.
Projects, locations, work areas and the work breakdown are set up under administration; every role carries a protection tier and a project scope.
Six capability groups, one project record.
Nine operational modules grouped the way a department buys them. Every chip is a page of the application; the featured group moves on its own, or rest on a card to hold it.
Nine modules, and none of them keeps its own copy.
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
- One project
- QHSE
- Unrestricted
- Logistics / marine
- One project
- Commissioning
- Multi-project
- Central data custodian
- Unrestricted
- System administrator
- Unrestricted
Eight roles across three protection tiers. A field representative sees one project; the central data custodian sees the portfolio.
- Execution
- Supply chain
- Performance
- Project controls
- Vessel
- Readiness
- Commissioning
- Reporting
- Central exchange
- Recomputed, not carriedProductive time is a ratio of sums at every scope; a portfolio figure is never an average of project figures.
- Attention with an ageConstraints and exceptions carry a target date and an ageing measure as well as a status, so attention can be prioritised by both severity and time outstanding.
- Permission-gatedEight roles across three protection tiers, each with an explicit project scope.
The deck enters the day. The office reads the same record.
Crews, shifts, activities, constraints and photographs are entered once, on the deck. Opening a day is a statement that the day happened, and every figure the project office and the centre read afterwards is derived from it.
- One governed daily record per project, location, date and shift
- Amendments keep their history rather than replacing what was said
- Constraints and exceptions carry a target date and an age
Readiness is assessed from the records, not declared in a meeting.
A system is ready when its own evidence says so. Where a criterion cannot be determined, that is shown as its own state rather than being reported as failure.
- Systemisation
- Tag register
- Systems register
- Subsystem boundaries
Scope is established before completion is counted against it.
- Mechanical completion
- Inspection & test plans
- Inspection requests
- Punch list A / B
Completion share is derived from the check sheets, never typed in.
- Pre-commissioning
- Test packs
- Certificates
- Preservation
Preservation due dates are carried with the system they belong to.
- Turnover
- Turnover packages
- Dossiers & closeout
- Handover state
Handover is a record with evidence behind it, not a date in a plan.
Governed data is not editable master data.
Users, roles, projects, locations and the work breakdown, contractors, and the vocabularies every register selects from change only through their own approval path. The audit log is append-only.
Report and issue
A report catalogue, generation with readiness validation, the management bulletin and the archive, with document control, transmittals, exceptions and actions beside them.
Consolidate the portfolio
Each project issues a central export; ingestion validates it; a submission tracker shows compliance; the portfolio position is recomputed from components rather than carried up.
Keep the registers governed
Actions, decisions, interfaces, risks and opportunities, the change register and data quality, behind an append-only audit log.
Governed data, not editable master data
Users, roles, projects, locations, the work breakdown, contractors and the vocabularies every register selects from change only through their own approval path.
More of what the application covers.
- Governed import, template, 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 tracker and central exchange ingestion
- Interfaces, risks and opportunities registers
- Data quality rules with an owner for each
- Append-only audit log behind every controlled change
Two places, one project record.
Crews, shifts, activities, constraints and photographs recorded where the work is, with a tablet variant for daily field input.
The same day read back as productive time, lost person-hours, reporting compliance and the constraints past their date.
Where OPMS stops and the next application starts.
- OPEPOPEP: Offshore Projects Execution PlatformOPEP governs execution of a single offshore project; OPMS governs the wider portfolio and departmental reporting position.
- VMTVMT: Vessel Management TrackerVMT governs the fleet and vessel operational record; OPMS records how the marine spread supports each project.
- CCMSCCMS: Completion, Commissioning & Handover Management SystemCCMS governs system-level completion and tag records; OPMS consumes those positions for project-level reporting.
- EDMSEDMS: Enterprise Document Management SystemEDMS governs engineering deliverables and controlled documents; OPMS tracks the status of those deliverables against project work fronts.
See OPMS on one of your projects’ daily records.
Bring one project’s daily field records. We will show the productive-time figures, the portfolio position and the management bulletin OPMS produces from them.