Logistics Management System
One view of the movement, with clear ownership for every record.
LGMS governs logistics planning and execution across shipments, cargo, transport requests, routes, scenarios, fleet assets, marine movements and operational exceptions.
A transport request progresses through planning, allocation, routing and berth assessment
Planners, dispatchers, asset owners and port operators work from one governed movement record so each stage produces evidence required by the next.
Request. The transport request records what must move, origin, destination and required date, then follows a controlled decision workflow.
Missing control data does not constitute a pass
Where required berth-check information is missing, LGMS reports that the check cannot be completed. Missing control data is not interpreted as a pass.
LGMS has defined capability boundaries. It does not provide route optimisation, demand forecasting or pricing, and generative AI is not used to make operational decisions.
- Plan feasibility
- Constraints
- Scenarios
- Planning calendar
Infeasible constraints are surfaced before a logistics plan is committed.
- Resource allocation
- Fleet assets
- Operators
- Allocations
Database constraints prevent two plans from allocating the same controlled resource over the same period.
- Route restriction
- Versioned routes
- Corridor restrictions
- Movement check
The movement is checked against the route version in force, and the version is recorded with the check.
- Berth limit
- Port limits
- Berth finder
- Marine checks
Where a required port limit is unavailable, the result is reported as not checkable and the information gap remains visible.
Every governed master-data record has an accountable steward, quality measure and segregation-of-duties control
Quality is assessed across eight dimensions, with unmeasurable dimensions reported explicitly rather than scored optimistically. Submitters cannot approve their own records.
Published is distinct from effective. Released master-data records remain subject to their effective dates.
- Quality is assessed against a defined minimumEach domain records a quality score against its required threshold.
- Not measuredremains explicit. Integrity and conformity are reported as not measured where evidence is unavailable rather than assumed satisfactory.
- Versioned and effective-datedMaster-data records retain version and effective date so consuming processes can determine which revision applied at a given time.
Six implemented functional areas with defined scope
LGMS navigation covers transport, transport management, planning, fleet, marine and master-data functions.
Transport
Shipments, cargo, approvals and exceptions are governed as records so logistics status is derived from recorded work rather than entered as a separate declaration.
- Shipments
- Approvals
- Exceptions
Transport management
Transport requests and versioned routes retain corridor restrictions so movement feasibility is checked against governed route data.
- Transport requests
- Routes
Planning
Logistics plans include activities, scenario comparison, planning boards, calendars and constraints assessed before controlled commit.
- Logistics plans
- Scenarios
- Planning boards
- Planning calendar
- Constraints
Fleet and resources
Fleet assets and operators retain allocation, maintenance and inspection records, with database controls preventing conflicting assignments.
- Fleet assets
- Operators
- Allocations
- Maintenance
- Inspections
Marine and ports
Ports retain berth data and declared operating limits. Missing required limits are reported as not checkable rather than interpreted as acceptable.
- Ports
- Find a berth
Master data and knowledge
Governed master-data records retain named stewardship, measured quality and segregation-of-duties controls, with guidance shown alongside relevant records and sources identified.
- Governed records
- Domains
- Guidance
- Sources

Heavy-lift and offshore cargo planned against route and berth capability
Transport coordinators, planners, dispatchers, fleet managers, port administrators and project managers work from the same governed movement record and control resource conflicts and route constraints within it.
- Marine, heavy-lift and fleet roles with controlled external access
- Database controls prevent conflicting allocation of assets and operators
- Port limits are explicit, and the berth finder identifies missing required limits

Rejected data must be corrected before controlled commit
Select a dataset, download its template, upload and preview data, correct rejected rows, then confirm commit. Rejected rows return validation reasons and only accepted records are written.
- Twenty portable datasets across eight business domains
- Export-only datasets are distinguished from datasets that support controlled round-trip exchange
- Application-owned operational state is maintained separately from customer-managed master data
Conflicting resource allocation is prevented
Database controls prevent conflicting asset or operator allocation rather than relying on interface-only validation.
Missing limits do not constitute a pass
Where required port limits are missing, berth suitability is reported as not checkable rather than acceptable.
Master data has accountable ownership
Governed master-data records retain steward, source, submitter and approver, with segregation of duties preventing self-approval.
Guidance remains advisory
Guidance is advisory and does not approve, sign, close or otherwise alter governed records. Generative AI does not make operational decisions.
More of what the application covers
- Shipment lifecycle showing each shipment by current state
- Cargo retained against the shipment record that carries it
- Scenario comparison before a plan is committed
- Planning boards and a planning calendar
- Fleet maintenance and inspections
- Versioned routes with corridor restrictions
- Quality assessed across eight dimensions for each governed master-data record
- Hash-chained audit history behind governed changes
Logistics movement connected to the systems that create demand
- PMSPMS: Procurement Management SystemPMS creates procurement requirements, while LGMS plans and executes associated logistics movements.
- OPMSOPMS: Offshore Projects Management SystemOPMS governs offshore project execution, while LGMS governs supporting transport and marine-logistics activities.
- SPIRSPIR: Spare parts Interchangeability Record Management SystemSPIR governs spares and material records, while LGMS governs associated movement and delivery activities.
- CVMSCVMS: Contractor / Vendor Management SystemCVMS governs assurance for carriers, freight forwarders and other logistics suppliers.
Review LGMS using one of your heavy-lift movements.
Bring one movement with its cargo, route and berth. The demonstration will show the governed plan, resource-allocation controls and required checks before execution.

