27 applications. Start with the industrial record or workflow you need to govern.
Zemerc is a portfolio of independently operable applications. Each one governs a defined class of industrial record and can be adopted on its own. Start with the record or workflow that needs control, then add other applications only where the operation requires them.
Capital projects: controls, supply, completions and offshore execution.
Producing assets: integrity, maintenance, flow and hydrocarbon accounting.
People and major-hazard risk across design and operation.
Management systems, sustainability reporting, documents and knowledge.
A portfolio of independently operable applications not dependent modules within a single platform.
This distinction matters commercially and operationally. Clients may purchase and operate one application without buying the wider portfolio or depending on another Zemerc product.
Every application operates independently
Each application has its own users, data, controls and release lifecycle. It remains fully operable as a standalone product.
Adopt one application independently
A client may adopt one application for one team without any requirement to purchase another. Expanding the portfolio remains a separate decision, not a dependency.
Connected only where records genuinely relate
Applications exchange defined records only where the underlying work crosses a genuine operational boundary.
Narrow the portfolio to the application that matches your requirement.
Filter by operating stage and operating area, or search using the record or workflow you manage, such as a punch list, sealed tender, barrier or meter reading.
Search matches application names, governed records and lifecycle stages.
27 applications in the portfolio
- PDMSProjects
PDMS: Project Delivery Management System
Portfolio governance, project workspaces and stage-gate evidence.
Portfolio → Project workspace → Stage gate → Delivery governanceSee the application - BCMSProjects
BCMS: Budget & Cost Management System
Estimate, budget, commitment, actual and forecast maintained within one financial chain.
Estimate → Budget → Commitment → Actual → ForecastSee the application - IFMSProjects
IFMS: Interface Management System
Governed interfaces between parties on capital projects.
Interface identified → Agreed → Decision recorded → ClosedSee the application - CVMSSupply chain
CVMS: Contractor / Vendor Management System
Supplier and contractor assurance with evidence-derived compliance and a supplier portal.
Qualification → Computed compliance → Supplier portal → ScorecardSee the application - PMSSupply chain
PMS: Procurement Management System
Source-to-pay procurement with sealed tenders and supplier access.
Requisition → Sealed tender → Award → Purchase order → ReceiptSee the application - CMSSupply chain
CMS: Contracts Management System
The contract lifecycle through obligations, claims and payment certification.
Contract → Obligation → Claim → Payment certificationSee the application - LGMSSupply chain
LGMS: Logistics Management System
Movement planning, scenario comparison and marine or berth checks.
Movement plan → Scenario comparison → Comparison → Marine and → ExecutionSee the application - CCMSCompletions
CCMS: Completion, Commissioning & Handover Management System
Inspection and test records, punch lists, certificate sequence and turnover packages.
ITR → Punch list → Certificate chain → Turnover packageSee the application - QMSCompletions
QMS: Quality Management System
Inspection and test plans, inspections, non-conformance, corrective action, traceability and quality dossiers.
ITP → Inspection → Non-conformance and corrective action → Quality dossierSee the application - SPIRCompletions
SPIR: Spare parts Interchangeability Record Management System
Spares, transmittals, vendor portal and digital handover records.
Vendor data → SPIR register → Transmittal → Digital handoverSee the application - OPEPOffshore
OPEP: Offshore Projects Execution Platform
Offshore-project execution from fabrication through commissioning and handover, with status derived from governed records.
Project record → Readiness gate → Offshore execution → Field updateSee the application - OPMSOffshore
OPMS: Offshore Projects Management System
Daily field input to productivity analysis and portfolio consolidation.
Daily field input → Productive and non-productive time → Portfolio consolidation → Management bulletinSee the application - VMTOffshore
VMT: Vessel Management Tracker
Fleet, charters, campaigns, daily operations, downtime and off-hire.
Vessel & charter → Campaign → Daily operations → Downtime & off-hireSee the application - AIRMSAssets
AIRMS: Asset Integrity & Reliability Management System
Integrity, inspection, corrosion and barrier records with an Asset 360 view.
Asset 360 → Inspection → Integrity record → Barrier assuranceSee the application - RAMSAssets
RAMS: Reliability, Availability & Maintainability Management System
Quantitative reliability analysis for operating assets.
Reliability model → Analysis → Availability → MaintainabilitySee the application - EAMSAssets
EAMS: Enterprise Asset Management System
Maintenance execution: work orders, preventive maintenance, inventory and calibration.
Asset → Condition → Work order → Preventive maintenanceSee the application - OMSAssets
OMS: Obsolescence Management System
Lifecycle supportability risk and lifetime-buy decisions.
Lifecycle risk → Where-used impact → Mitigation case → Lifetime buySee the application - FAMSProduction
FAMS: Flow Assurance Management System
Network hydraulics, thermal behaviour, envelopes and pigging.
Network → Hydraulic and thermal analysis → Envelope evaluation → PiggingSee the application - HAMSProduction
HAMS: Hydrocarbon Accounting Management System
Meter readings governed through validation, allocation, reconciliation, period close and reporting.
Metered → Validated → Allocated → Reconciled → Closed → ReportedSee the application - HSESafety & Risk
HSE: Health, Safety & Environment Management System
Occupational and operational safety, field reporting, permits and emergencies.
Permit → Field report → Incident → Emergency responseSee the application - PSMSafety & Risk
PSM: Process Safety Management System
Operational process safety covering hazards, barriers, change and proof testing.
PHA → Barrier and safety instrumented function → Management of change → Proof testSee the application - TSMSafety & Risk
TSM: Technical Safety Management System
Technical safety in design: safety case, hazard register and safety-critical elements.
Hazard register → ALARP → Safety case → Safety-critical-element assuranceSee the application - RMSSafety & Risk
RMS: Risk Management System
One enterprise risk register with facilitated workshops, bow-tie analysis and control-effectiveness records.
Risk register → Workshop → Bow-tie analysis → Control effectivenessSee the application - IMSGovernance
IMS: Integrated Management System
Multi-standard management-system capability: understand, build and operate.
Understand → Build → OperateSee the application - ESGGovernance
ESG: Environmental, Social & Governance Management System
Carbon, disclosure frameworks, materiality and reporting.
Data → Materiality assessment → Framework → ReportSee the application - EDMSGovernance
EDMS: Enterprise Document Management System
Controlled documents, revisions, transmittals and records.
Registered → Revised → Reviewed and approved → Published and distributedSee the application - LLMSGovernance
LLMS: Lessons Learned Management System
Lessons learned and the knowledge chain from capture to reuse.
Captured → Reviewed → Approved → Retained and reusedSee the application
PDMS: Project Delivery Management System
Portfolio governance, project workspaces and stage-gate evidence.
Portfolio, programme and project records are governed within one structure, with stage gates derived from workspace registers rather than manually entered status. Where the available history does not support a completion forecast, no forecast is produced.
- 0
- Applications in the portfolio
- 0
- Operating areas
- 0
- Stages of the operation
Barrier assurance depends on activity that was performed, not on policy statements alone.
Performance standards carry their governing standard and assurance frequency. Each assurance activity records what was performed and what was found, and degradations are tracked through to restoration.
- No integrity score, health index or readiness score is calculated unless a defined and supportable method exists
- Thickness readings and approved assessment revisions are retained as immutable governed records
- A defect cannot close until the required supporting evidence is complete


Every quantity is traceable to the reading that produced it.
Readings are retained immutably with governed substitution. Each reading is classified by its validation state as valid, warning or suspect rather than being silently accepted.
- Effective-dated calculations rerun a historical period using the method that was in force at the time.
- Allocated quantities reconcile against counterparty statements
- Record lineage is retained through close-out, when traceability is most important.
22 operational problems and the applications designed to address them.
Most organisations start with a requirement rather than an application name. These examples link common operational problems to the applications designed to govern the relevant records or workflows.
- BCMS“Cost reports and commitments do not reconcile consistently”Estimate, budget, commitment, actual and forecast maintained within one governed financial chain
- IFMS“Ownership is unclear at the boundary between contractors.”Each interface is numbered, owned by both parties and measured against a required-by date.
- CVMS“We cannot demonstrate that a supplier was compliant when used.”Compliance is derived from the evidence held at the relevant time with suppliers maintaining their records through a controlled portal.
- PMS“A tender may be accessible before authorised opening”Tender submissions remain sealed without an administrative read path and are opened through a formal recorded action.
- CCMS“Certificates issued from percentage completion rather than verified deliverables”Controlled certificate sequence in which gate release depends on completed deliverables and percentage is derived afterwards
- QMS“Non-conformance closure lacks independent authority”Technical-authority disposition with effectiveness review and signed closure
- OPEP“Offshore progress is reported from records that do not reflect deck activity.”Reported figures are derived from underlying records, and unsupported measures are shown as not measurable rather than zero.
- LGMS“The same vessel is allocated to two movements”Database-level constraints prevent conflicting allocations rather than relying solely on interface validation.
- AIRMS“Our integrity position is a score nobody can reproduce.”Governed, revision-controlled assessment registers with evidence-gated closure, without relying on an unsupported health index.
- EAMS“Maintenance compliance includes work without independent verification”Work completion and independent verification are governed as separate actions.
- OMS“A critical spare is found to be obsolete when it is needed.”Verified manufacturer evidence supports lifecycle assessment and timely lifetime-buy decisions.
- RAMS“Reliability studies remain in reports that are not routinely rerun.”Versioned models use a deterministic engine over an immutable failure register coded to a standard taxonomy.
- FAMS“Flow-assurance work relies on a fluid definition that has not been formally agreed.”Governed engineering records prevent draft information from being used downstream and separate authorship from approval.
- HAMS“A corrected meter reading has overwritten the original source record”Immutable readings with governed substitution and effective-dated calculations that support historical reruns
- HSE“Incident reporting is delayed because field capture is not readily available”Authorised users can report from the field, including offline where supported, with each report receiving a permanent document number.
- PSM“We report a process-safety index that lacks a defensible engineering basis.”Where no certified engineering method exists, the application reports the underlying components individually rather than presenting an unsupported composite index.
- TSM“Safety-critical element definitions are recreated when the plant enters operation.”Barriers, safety-critical elements and performance standards are defined during design and published as governed requirements for operation.
- RMS“Separate risk registers prevent a coherent enterprise-risk view”One enterprise register supported by facilitated workshops, bow-tie analysis and control-effectiveness records
- IMS“The management system exists as static documentation rather than an operating control system”A multi-standard management system established as a working structure that can be operated and improved
- ESG“Sustainability figures are assembled manually each reporting cycle”Disclosure derived from governed operating records so sustainability and operating figures can share a common source
- LLMS“The same lesson recurs across projects”A governed knowledge chain from capture through review to reuse on subsequent work
- SPIR“Handover arrives as an unstructured collection that is difficult to audit”Spares, vendor data and transmittals retained as governed records, with handover completeness derived from supporting registers
Applications connect only where operational records genuinely intersect.
Applications do not share data merely because they are sold within one portfolio. Controlled interfaces exchange named records only where work genuinely passes from one team or process to another.
- PMSLGMS
Receipt: a received item can trigger the logistics activity required to move it
- LGMSCCMS
Delivered item: receipt and acceptance records support installation and testing readiness
- CCMSSPIR
Completed system: verified completion evidence becomes part of the handover record
- QMSCCMS
Inspection and test record: quality evidence can become completion evidence
- IFMSPDMS
Open interface: an unresolved boundary can become a delivery exposure
- TSMPSM
Safety-critical element: a design definition becomes an operational assurance obligation
- PSMAIRMS
Barrier assurance: an assurance obligation can become an inspection or integrity activity
- AIRMSEAMS
Defect: an integrity finding can generate maintenance work with a verification step

Choose the first application based on the team and record that need stronger control.
Application selection should begin with the team that owns the relevant record or workflow, rather than with a suite-level procurement decision. That team is best placed to test whether the application supports the work.
- Each application operates independently, so initial adoption creates no dependency on another Zemerc application.
- Cross-area relevance is shown explicitly, with one primary area and any additional areas served.
- Each application page presents the application’s own interface and screens rather than generic illustrations.
All 27 applications by operating stage and area
Every application in the portfolio, with its primary operating area and any additional areas it supports.
See the applications working with your own records
A working session built around one of your own registers, projects or assets, showing the application against representative records and controls.
