SubseaCore

From internal system to product

SubseaCore was not conceived as a product. It was the system the group’s oil and gas platform needed in order to run offshore crew, assets and contracts against real regulatory obligations, built by the group’s technology arm because nothing available made the right assumptions.

Because it was built for duty-holder responsibilities first, it carries assumptions general-market software does not: rotations rather than calendars, certifications that gate mobilisation, and travel routing that stitches two fare networks together when neither covers a journey end to end.

Nine connected modules

• Crew management — personnel, rotations and competence in one register.
• Rig and asset operations — the operating state of facilities and equipment.
• Offshore travel logistics — routing crews to hitches across fare networks.
• Projects and contracts — scope, milestones and commercial terms.
• Payroll and billing — rotation-aware pay and client invoicing from one record.
• Documents and compliance — controlled documents with evidence attached.
• Personnel on board — live POB, a safety artefact before a data point.
• Training and competence — validity tracked against the whole hitch.
• Reporting — drawn from the record rather than rebuilt beside it.

Why connected matters more than complete

The modules are useful individually and valuable together, because the failures they prevent are joins. A certification lapsing mid-hitch is only visible if competence, rotation and travel are the same record. A POB that disagrees with payroll is a reconciliation nobody should be performing.

Reach

The platform supports operations from the North Sea to Asia-Pacific, and its routing capability spans marine and general fare networks. You can read about it directly at subseacore.com.