Offshore Personnel and Marine Logistics Software: Keeping Bed Bookings, Certification, Helicopter Manifests and the Muster Record in Agreement

The muster record is the product, everything else is scheduling

Offshore logistics looks like a movement planning problem. It is really an assurance problem wearing a scheduling costume. At any given minute you must be able to state exactly who is on each installation and vessel, that each of those people was eligible to be there, and that the record would survive scrutiny after an incident. Every feature in the system exists to keep that statement true.

The reason it is hard is that eligibility is compound and time bound. A person needs current offshore survival training, a valid offshore medical, the right competency for the role they are travelling to perform, current travel documentation, and sometimes site specific inductions or a current drug and alcohol test. Each of those expires on its own date. A crew change plan built three weeks ago against certifications valid at the time can contain a person whose medical lapses the day before the flight.

Then the constraints stack. There has to be a bed on the installation for the duration of the trip, which competes with campaign work and shutdown crews. There has to be a seat on an aircraft, and aircraft capacity is limited by weight, not only by seat count, so a heavier crew and a full baggage load can mean the same aircraft carries fewer people. And whatever finally flies must land in the personnel on board record on arrival, not in an email.

Why spreadsheets and generic tools fail at this specific job

Any spreadsheet can hold a list of people and dates. What it cannot do is hold the join. The competency matrix lives with the training team, the medical validity lives with occupational health or the contractor's own records, the bed plan lives with the installation, the flight manifest lives with the aviation provider in their format, and the personnel on board board is often a physical card system on the installation itself. Each is maintained by someone competent. The failure is always the seam.

Generic workforce management software does not help because it models employment, not eligibility to be at a location. It has no concept of a bed on an asset, no concept of aircraft weight, no concept of contractor personnel who are not your employees but whose certification you are nonetheless accountable for. That last point matters: most people flying offshore work for a contractor, and their training records sit in the contractor's system.

The consequence is a coordinator who spends the working day cross checking lists, and an offshore installation manager who trusts the physical board over any system, correctly, because the board is the one thing updated by the person watching people walk through the door.

Where Sword Vantage stops

Sword Vantage is the established product in this space and it is a serious system for personnel logistics and competence tracking. Operators running it are usually better off than operators running spreadsheets, and if your requirement is close to the standard offshore model it will serve you.

The limits are the ones any packaged product hits in a domain where every operator has its own regime. Your competency and medical matrix is yours, negotiated with your own safety function and often differing per asset and per role. Your bed allocation rules across installations and flotels reflect your own priorities during campaigns. Your aviation partners have their own manifest and weight formats and change them without asking you. Your lifting equipment certification regime for cargo carrying units follows your own inspection scheme. And your emergency response procedure defines exactly what the muster record must show and how fast. Where those differ from the packaged assumption, the work returns to spreadsheets and to email between the logistics coordinator and the aviation provider, which is precisely the seam that fails.

What a custom build has to include

A person record that is eligibility centred rather than employment centred. Every certification, medical, induction and competency held with an expiry date and a source, including for contractor personnel, with an ingestion path from contractor systems rather than an assumption that someone will type them in. Eligibility is then a computed state at a future date, which is the only version of the question that helps planning.

Trip planning that checks all constraints at once. Bed availability on the destination for the full duration, eligibility on the travel date and throughout the stay, aviation capacity by seat and by weight, and any site specific requirement. A plan that passes today and fails on the travel date because a certificate expired in between is the failure to design out.

Weight aware manifesting. Passenger weights and baggage captured at check in, seat allocation, and the manifest produced in the format the aviation partner requires. Late changes have to reflow the manifest, since a person removed at the heliport changes both the weight and who is expected on the other end.

Personnel on board reconciliation as a hard, physical process. Arrival and departure scanned or confirmed at the point of movement, with the offshore installation manager able to see and correct the position from the installation, working offline when the link drops. If the record can only be updated from shore, the installation will keep its own board and yours becomes decorative.

Cargo movements with certification enforcement. Cargo carrying units with their lifting certification and inspection dates, contents and dangerous goods declarations, waybills, and a hard block on shipping a unit whose certification has lapsed. Backloads matter as much as outbound, because units accumulate offshore and clog deck space when nobody is tracking the return.

Vessel and aviation scheduling against the movement demand. Which vessel calls at which installation on which run, deck space, and how personnel and cargo demand maps onto planned voyages and flights. The commercial value here is utilisation: seats and deck space are expensive and the default state is running them partly empty because nobody consolidated.

An emergency response view. Given an installation, who is on it right now, their next of kin details, their location if you track mustering, and an export that emergency response can use without training. Build this early rather than late, because it is the reason the system exists.

What it costs and how long it takes

A first release covering the eligibility centred person record, trip planning with constraint checking, and personnel on board reconciliation runs $95,000 to $190,000 and ships in 14 to 20 weeks. A full platform adding weight aware manifesting with aviation partner formats, cargo carrying unit certification and backload management, vessel and flight scheduling, contractor certification ingestion and the emergency response view runs $260,000 to $600,000 phased over 8 to 14 months.

What drives cost: the number of contractor organisations whose certification data you need, since each is a separate relationship and a separate format. The number of aviation providers and their manifest requirements. Offline capability offshore, which is mandatory and is real engineering. And integration with existing competence management or human resources (HR) systems, which is usually necessary and usually slower than anyone estimates because ownership of the data is contested internally.

What keeps cost down: start with one asset and its supporting flights. A single installation with correct eligibility, correct beds and a trustworthy personnel on board count proves the model, and the second asset costs a fraction of the first.

When buying is the right call

Buy if you support one installation with a stable crew, one aviation provider and a simple certification set. A packaged product or even a disciplined manual process is proportionate, and the money is better spent on the logistics coordinator.

Build when your personnel on board count differs between the installation and the shore system often enough that people have stopped being surprised, when a person has arrived at the heliport and been turned back for an expired certificate more than once, when bed allocation across assets is negotiated by phone during campaigns, or when your emergency response drill exposed how long it takes to produce an accurate list. That last one usually settles the argument internally without any help from us.

How to choose a developer for offshore logistics software

Ask how eligibility is evaluated for a date in the future. If their model only answers whether a certificate is valid today, crew change planning will keep failing at the heliport.

Ask how contractor certification data gets in. A developer proposing a portal where contractors upload documents has thought about it. One assuming your team will key it has never seen the volume.

Ask what happens to the personnel on board record when the satellite link to the installation drops. Offline capability with reconciliation is the only acceptable answer, and it should come from them rather than from you.

Ask how aircraft weight is handled. Seat counting alone is a sign they have modelled this as a booking system rather than as aviation logistics.

Ask who owns the code and settle it in writing before kickoff. You should hold the repository, the cloud accounts and the right to hire any other firm. At Digital Heroes the client owns the code from the first commit, which is not a preference when the system holds the muster record you would rely on during an emergency.