IOGP-690 §25C manning: the workload case that wins the extra engineer
Ask any offshore maintenance manager what the hardest part of the job is and you won't hear "the weather" — you'll hear "getting one more engineer approved." Headcount on an installation is a commercial decision made by people who don't sign task cards. The only argument that survives that meeting is a documented workload case, and IOGP-690 §25C is the hook that makes it mandatory rather than optional. Here is how to build the case so it approves itself.
01What §25C actually demands
Section 25C of IOGP-690 (the offshore helicopter operations guidelines) doesn't hand you a headcount table. It does something better: it requires that maintenance manning be adequate for the maintenance programme actually being flown, considering duty-time limits, concurrent aircraft operations and the roster pattern. "Two engineers because we always had two" is not a compliance position — it's an anecdote. The section pushes you toward a documented justification, which is exactly the document you wave in the budget meeting.
02The workload case in five numbers
Worked example: a North Sea installation operating 2 × AW189, each averaging 18 flight hours per week, with two engineers on duty per 12-hour shift, seven days a week:
| # | Input | Value |
|---|---|---|
| 1 | Fleet demand (2 × 18 FH × 1.4 MH/FH blended rate) | 50 MH/week |
| 2 | Unscheduled defect allowance (+30% historical findings) | +15 MH/week |
| 3 | Total weekly demand | 65 MH/week |
| 4 | Productive hours available (2 eng × 12 h × 7 d × 55% wrench-time) | 92 MH/week |
| 5 | Peak week: 50 FH inspection on A/C1 + AOG rectification on A/C2 | ~120 MH/week |
The average week shows a 42% headroom — the number the asset manager will quote back at you. The peak week is 30% short, and peak weeks are not edge cases offshore: they are the weeks with a calendar inspection due, a deck strike finding, or a salt-ingestion rinse inspection stacked on a snag. Miss the peak and the aircraft goes AOG on the installation, which costs more per day than an engineer costs per year.
roster multiplier = duty requirement × rotation factor (e.g. 3 shifts cover 2 posts)
03Why manning cases get rejected
- They argue averages. Average demand always fits. If your case doesn't contain a peak-week scenario, the reviewer will assume — correctly — that you haven't modelled the risk.
- No findings allowance. Scheduled task cards are the visible tip; defect rectification typically adds 25–40%. A case without a historical findings ratio reads as optimistic.
- Duty time treated as productive time. Twelve hours on shift is not twelve hours of spanner work. Helideck ops, refuelling supervision, briefings, tooling and admin consume 40–50% offshore. Use an honest wrench-time ratio.
- Rotation forgotten. Two posts covered by 2-on/2-off equal-time rotation means four engineers on the roster, not two — and training, leave and type-recurrent time push the real figure higher.
04Turning it into a document that survives audit
The case that gets approved — and that a surveyor or customer audit accepts under §25C — has four sections: the demand model (numbers 1–3 above), the availability model (number 4, with the wrench-time ratio stated), the peak-week stress test (number 5), and the roster map showing how duty posts become rostered heads. Keep it to one page plus an annex. Re-run it quarterly, because utilisation offshore drifts with the drilling programme, and a manning case built on last year's flying is exactly what an auditor will check first. Pair it with the IOGP-690 §25C offshore manning guide for the clause-by-clause mapping.
Build the workload case in minutes: enter your aircraft, utilisation and roster, stress the peak week, and export an auditor-ready PDF for the budget meeting.
Run the manning case →