The Skills Gap Is a Process Safety Problem
A control room operator misreads a high-pressure alarm because nobody explained what the underlying transmitter is actually measuring. A maintenance technician reinstalls a valve with the packing gland finger-tight because the written procedure assumed he already knew the torque sequence. A newly promoted instrument engineer signs off a safety instrumented function proof test without understanding the demand mode assumptions behind the target risk reduction. Each scenario is illustrative, but every experienced engineer reading this has seen a close equivalent. The skills gap in oil and gas is not an HR abstraction — it is a direct contributor to spurious trips, unplanned shutdowns, near-misses, and, at the far end of the consequence scale, loss of containment events.
The workforce problem has a structural cause. The result is a competency distribution with a hollowed-out middle: a shrinking group of senior practitioners and a growing group of junior staff with limited mentored exposure to real plant conditions.
This article sets out where the gap bites hardest, what standards already require in terms of competency, and what a maintenance lead or engineering manager can do about it without waiting for an industry-wide solution.
Where the Gap Creates the Most Risk
Process Safety and Functional Safety Roles
IEC 61511 — Functional Safety: Safety Instrumented Systems for the Process Industry Sector — explicitly requires that persons carrying out activities in the safety lifecycle possess the necessary education, training, knowledge, and experience. This is not a soft recommendation. The standard places competency as a lifecycle obligation alongside hardware integrity and software verification. An organisation that cannot demonstrate the competency of its SIS engineers and technicians is non-compliant, regardless of how well the hardware is specified.
The practical consequence is that proof testing of safety instrumented functions — pressure safety valves, emergency shutdown valves, high-integrity pressure protection systems — must be performed by technicians who understand what a partial stroke test does and does not prove, how a bypass affects the SIL claim, and when a revealed failure requires a formal management of change review. These are not instinctive skills; they are learned through structured exposure and mentoring.
Rotating Equipment Maintenance
API 610 — Centrifugal Pumps for Petroleum, Petrochemical and Natural Gas Industries — and API 682 — Pumps — Shaft Sealing Systems for Centrifugal and Rotary Pumps — together define the design and maintenance envelope for the most common rotating equipment on a process plant. Replace with: 'A technician who does not understand how seal flush plan selection relates to sealed fluid properties and operating conditions, or who does not recognise the significance of a change in seal pot pressure trend, will not catch a developing seal failure before it becomes a hydrocarbon release.'
The gap here is partly generational and partly structural. Older technicians learned pump behaviour by working alongside experienced machinists over years. The current environment often places a junior technician in front of a computerised maintenance management system work order with a procedure that was written for someone who already understands the equipment.
Replace with: 'ISA/IEC 61511-1 — Functional Safety: Safety Instrumented Systems for the Process Industry Sector — Part 1: Framework, Definitions, System, Hardware and Software Requirements — requires that calibration and loop testing maintain the integrity of safety functions. A technician who calibrates a transmitter incorrectly, or who does not understand loop testing versus functional testing, can invalidate an SIL claim without generating any paperwork that flags the problem.' A technician who calibrates a transmitter incorrectly, or who does not understand loop testing versus functional testing, can invalidate an SIL claim without generating any paperwork that flags the problem.
Structural Approaches to Closing the Gap
Competency Frameworks vs. Training Courses
There is a meaningful difference between sending someone on a course and verifying that they are competent to perform a task unsupervised. A competency framework defines the knowledge, skills, and behaviours required for a specific role, then provides evidence criteria — typically a combination of written assessment, observed performance, and supervisor sign-off — that allow the organisation to make a defensible statement about individual capability.
| Approach | What it produces | What it does not produce |
|---|---|---|
| Training course attendance | Awareness of a topic | Demonstrated field competency |
| Competency framework with assessment | Documented, role-specific capability | Guaranteed performance under stress |
| Mentored shadowing alone | Tacit knowledge transfer | Formal evidence trail |
| Combined framework + mentoring + assessment | Both evidence and embedded knowledge | — |
The combined approach is more resource-intensive but is the only one that satisfies both the regulatory intent of IEC 61511 and the practical need to retain tacit knowledge before it walks out the door.
Knowledge Capture Before Retirement
When a senior engineer or technician retires, the organisation loses not just their skills but their contextual knowledge: why a particular bypass valve was installed, what the original design intent of a control loop was, which relief valve has a history of chattering under specific conditions. This knowledge rarely appears in drawings or procedures.
Structured knowledge capture should begin well before a planned departure. Useful methods include:
- Annotated P&ID reviews where the departing engineer walks a junior colleague through non-obvious design decisions
- Recorded troubleshooting sessions on actual plant problems
- Procedure revision workshops where the senior technician identifies every step that assumes knowledge not written in the document
The output is not a video library — it is updated procedures, revised training materials, and a junior engineer who has been forced to ask the right questions while there was still someone to answer them.
Simulator and Digital Twin Training
High-fidelity process simulators have been used for operator training in LNG and refining for decades. The same principle applies to maintenance and instrument technicians, though the tooling is different. A digital twin of a safety instrumented system — even a simplified one — allows a technician to practice a proof test procedure, observe what a failed-safe versus failed-dangerous fault looks like in the diagnostic display, and understand the bypass management sequence without touching live plant.
This is not a replacement for supervised field experience, but it substantially compresses the time required to reach a baseline competency level before a trainee is paired with a senior technician on real equipment.
Illustrative Scenario: SIS Proof Test Competency Gap
The following is illustrative and does not represent a specific incident or organisation.
An offshore platform schedules its annual proof test campaign for the emergency shutdown valves on the high-pressure separator. The assigned technician has completed the company's one-day SIS awareness course and has the relevant work order. The procedure requires him to verify full closure of the ESV and confirm the valve position feedback signal at the logic solver.
What the procedure does not explain — and what the technician does not know — is that the platform's SIL claim for this function is based on a partial stroke test being performed quarterly, with the annual full-stroke test as a supplementary check. The technician has never seen a partial stroke test performed.
He completes the full-stroke test correctly, signs off the work order, and the function is returned to service. The paperwork is clean. The SIL claim is not.
The gap here is not procedural non-compliance — the technician followed the procedure. The gap is the absence of system-level understanding that would have prompted him to query the test history before signing off.
Competency Gap Assessment Checklist
Use this checklist at the team or site level to identify priority areas for intervention.
Process Safety and SIS
- [ ] Can each technician assigned to SIS maintenance explain the difference between a proof test and a functional test?
- [ ] Does the organisation have a documented competency standard for SIS work, with evidence records per individual?
- [ ] Are bypass management procedures understood and followed, with appropriate compensatory measures in place?
Rotating Equipment
- [ ] Can maintenance technicians explain the purpose of the seal flush plan fitted to each critical pump?
- [ ] Are vibration and seal pot pressure trends reviewed by someone who understands the failure modes, not just the alarm limits?
- [ ] Are API 610 and API 682 requirements referenced in maintenance procedures, not just in the original design documentation?
Instrument and Calibration
- [ ] Are calibration procedures written to the level of detail that a technician with no prior experience of the instrument type could follow correctly?
- [ ] Is there a process to verify that calibration results are reviewed for outliers before the instrument is returned to service?
Knowledge Retention
- [ ] Has the organisation identified which roles have a single point of knowledge failure — one person who holds critical tacit knowledge?
- [ ] Is there an active plan to transfer that knowledge before the individual leaves?
Training Effectiveness
- [ ] Are training records linked to demonstrated competency, or only to course attendance?
- [ ] Is there a mechanism for a technician to flag that a procedure assumes knowledge they do not have?
Conclusion
The skills gap does not resolve itself through recruitment alone. Hiring junior engineers and technicians into an environment where mentoring is thin, procedures assume competency that does not exist, and knowledge capture is unstructured will reproduce the same gap one cycle later.
The immediate next steps for a maintenance lead or engineering manager are straightforward: identify the roles where a competency failure creates a process safety or major equipment risk, assess the current evidence of competency for each individual in those roles, and close the gap between course attendance records and demonstrated field capability. IEC 61511 gives you the regulatory framework to justify the investment. The cost of an unplanned shutdown or a loss of containment event gives you the business case.
Start with the roles that touch safety instrumented functions and high-consequence rotating equipment. Build the competency framework before the next proof test campaign, not after.
