Turnkey Marine Electrical Project SOP
A turnkey marine electrical project SOP for full-scope work: Scanel owns requirements, planning, engineering, procurement, installation, testing and commissioning through documentation, customer acceptance and closeout.
What the turnkey marine electrical project SOP process is
Most of Scanel's SOPs describe a single, already-scoped piece of work: install this system, commission this switchboard, service this EEx motor. This chart is different on purpose. A turnkey project is the case where the customer does not scope the individual pieces at all, they state what they need and Scanel takes it from "Customer requirements received" all the way to "Turnkey project closed out, customer system accepted", absorbing engineering, procurement, installation, testing and commissioning as phases of one project rather than as standalone jobs each requiring its own kickoff. That is why the chart puts "Confirm scope, budget and schedule with customer" and the "Scope, budget and schedule confirmed?" decision before a single drawing is started: on a turnkey job there is no separate customer-side scoping step to catch a wrong assumption later, so the project plan has to be built on a scope the customer has actually confirmed, not one Scanel inferred from the initial request.
The two mid-chart gates exist because a turnkey project multiplies the cost of a mistake that a narrower job would catch on its own. "Customer approves engineering design and equipment list?" is a project milestone, not a full design-iteration cycle, it confirms the design and bill of materials before procurement commits any spend; a customer who wants to go deeper on the design itself before committing to a turnkey build is better served starting from the standalone Electrical Engineering & Design Change SOP, and a customer who only wants a defined scope installed, with no engineering or procurement attached, should use the Marine Electrical Installation SOP instead. "Incoming equipment matches specification?" catches a wrong voltage rating, IP rating or cable gauge against the purchase order before it reaches the vessel or site, because on a turnkey job Scanel carries the procurement risk that a directly-ordering customer would otherwise carry themselves. "System passes commissioning tests?" is the same pattern applied to the commissioning phase Scanel runs as part of this scope, it is a project-level pass or fail on this chart, not a substitute for the hard energization-approval gate inside the standalone Electrical System Commissioning SOP, which still governs whether a system is safe to energize regardless of which chart brought it there.
The last lane is where the customer's original requirement gets checked against what was actually delivered, and "Customer accepts completed system?" is deliberately a real decision rather than a formality: findings outstanding routes back through "Present deliverables to customer for acceptance" rather than into closeout on an assumption that the customer will probably be satisfied. Every row also carries a named owner and an hours figure through the built-in People and Workload columns, so the workload BI panel can show, across a project running twelve or more weeks, whether Ida Marsh's project-management hours and Camille Ward's engineering hours actually track the phase the project is in, design-heavy early, installation-and-commissioning-heavy later, instead of just assuming the plan holds.
What this flowchart covers
In this template
- Intake and planning, from "Customer requirements received" through "Confirm scope, budget and schedule with customer" and the "Scope, budget and schedule confirmed?" decision to "Develop project plan: milestones, resourcing, phase schedule", so the plan is built on a confirmed scope rather than an assumed one
- Engineering and the design-approval gate: "Prepare engineering design, schematics and wiring plans" feeding the "Customer approves engineering design and equipment list?" decision, which routes a revision request to "Revise design per customer feedback" before procurement commits any spend
- Procurement and the equipment-verification gate: "Procure equipment, cable and materials against approved design" and the "Incoming equipment matches specification?" decision, which routes a mismatch to "Return non-conforming equipment and reorder" rather than letting it reach the installation crew
- Installation across the Field Electrical lane: "Mobilize field crew, install cabling, panels and equipment" and "Complete terminations and installation checks" before a single system is powered up for test
- Testing and the commissioning gate: "Perform functional and system testing" feeding the "System passes commissioning tests?" decision, which routes a fault to "Diagnose and resolve fault, retest" rather than into documentation on an assumption that it will pass
- Closeout: "Compile as-built documentation, test reports and O&M manuals", "Present deliverables to customer for acceptance", the "Customer accepts completed system?" decision, and "Hold project closeout meeting, transfer O&M documentation and warranty terms", plus named owners and hours on every row via the People and Workload columns so the BI panel can show Ida Marsh's project-management hours and Camille Ward's engineering hours across the full project timeline
When to use this template
- A customer wants Scanel to own an entire marine or offshore electrical project end to end, requirements through closeout, rather than coordinating engineering, procurement, installation and commissioning as separate jobs themselves
- You're scoping a new project and need to confirm it's actually turnkey before committing the schedule, rather than discovering halfway through that the customer expected to handle procurement or engineering approval on their own timeline
- A design or a procurement order needs a documented customer sign-off before spend commits, and there was no consistent point in the project where that approval was captured
- You're onboarding a new project manager or engineer and need a reference for how the phases hand off to each other on a turnkey job, rather than each phase lead assuming the previous one closed out cleanly
- A completed system failed customer acceptance and you want a record of what the finding was and how it routed back into the project, rather than an informal fix nobody documented before closeout
How it works
Replace the lanes with your actual project roles
This chart uses Customer, Project Manager, Engineering, Procurement, Field Electrical and QA / Commissioning. If your projects split procurement approval from procurement execution, or split QA sign-off from the commissioning engineer's own test, give that role its own lane rather than folding it into one column.
Put your own acceptance criteria on the confirmation and approval gates
"Scope, budget and schedule confirmed?" and "Customer approves engineering design and equipment list?" need a stated definition of "confirmed" and "approved", a signed scope document, an approved BOM revision, not just a verbal go-ahead. Write the actual sign-off mechanism into the row's comment field so the person running the gate isn't relying on memory of what counts.
Name who has the authority to reject non-conforming equipment
"Incoming equipment matches specification?" is the one gate in this chart where letting a marginal item through is expensive later, once it's fitted, a wrong-rated item is a rework job, not a return. Attach a named role, not just a title, so there's no ambiguity about who can send equipment back to the supplier instead of installing it under schedule pressure.
Set People and Workload on every row before you rely on the BI panel
The workload panel can only total hours for rows that carry them. Fill in People and Workload for each step as you adapt the chart, using realistic effort hours rather than elapsed time, so a project running several phases in parallel actually shows up as a busy stretch for the right people instead of looking evenly spread.
Decide what counts as an outstanding acceptance finding
"Customer accepts completed system?" is only useful if the project manager and the customer agree in advance on what routes to "Findings outstanding" versus what's a minor note handled after closeout. List examples directly in "Present deliverables to customer for acceptance" so the distinction isn't made differently project to project.
Frequently asked questions
What makes a project "turnkey" rather than a scoped installation job?
On this chart the customer states requirements once, at "Customer requirements received", and Scanel owns everything downstream: engineering, procurement, installation, testing and commissioning, as phases of one project. If the customer has already scoped a defined piece of electrical work and just needs it installed, the Marine Electrical Installation SOP is the right document instead.
What happens if incoming equipment doesn't match the specification?
The "Incoming equipment matches specification?" decision routes a mismatch to "Return non-conforming equipment and reorder" before it ever reaches the installation crew. Catching a wrong voltage rating, IP rating or cable gauge against the purchase order at this gate is deliberately earlier and cheaper than catching it once the item is already fitted.
Who approves the engineering design before procurement starts spending?
That's the "Customer approves engineering design and equipment list?" decision, and it's a project milestone confirming the design and bill of materials, not the detailed design-review cycle itself. A customer who wants to iterate on the design in more depth before committing to a turnkey build is better served starting from the standalone Electrical Engineering & Design Change SOP.
How does the commissioning gate on this chart relate to Scanel's dedicated commissioning SOP?
"System passes commissioning tests?" is a project-level pass or fail on the commissioning phase this chart runs as part of the turnkey scope. It is not a substitute for the hard energization-approval gate inside the Electrical System Commissioning SOP, which still governs whether the system is safe to energize regardless of which chart brought it to that point.
What happens if the customer doesn't accept the completed system?
The "Customer accepts completed system?" decision routes "Findings outstanding" back through "Present deliverables to customer for acceptance" rather than into "Hold project closeout meeting, transfer O&M documentation and warranty terms" on an assumption the customer will probably sign off. The project only closes out once acceptance is actually recorded.