Turnkey marine electrical project process map
A swimlane map of a full turnkey marine electrical project from customer requirements to closeout, across the Customer, Project Manager, Engineering, Procurement, Field Electrical and QA/Commissioning. Five decision gates run end to end — scope confirmation, design approval, incoming-equipment inspection, commissioning pass, and final customer acceptance.
Opens a copy in the editor and saves it in this browser. No account, nothing sent anywhere.
What is in this map
20 steps across 6 swimlanes and 6 phases, with 5 decision points.
- Swimlanes (who does the work)
- Customer, Project Manager, Engineering, Procurement, Field Electrical and QA / Commissioning
- Phases (left to right)
- Requirements & Planning, Engineering, Procurement, Installation, Testing & Commissioning and Closeout
Why map this process
This is the map for a customer who wants one contractor accountable from a requirement to a signed-off system, and it earns that promise by refusing to let any phase's approval stand in for another's. The design-approval decision's own comment draws the line precisely: it's a project milestone gate confirming design and bill of materials before procurement spends money, not the detailed design-review cycle — a customer who wants to iterate on the design itself in more depth is pointed to the standalone Electrical Engineering & Design Change SOP instead. Each gate answers one specific question and nothing more.
The commissioning-pass decision is deliberately NOT the same as the hard energization-approval gate inside the standalone commissioning SOP. Its comment is explicit: this is a project-level checkpoint on the phase run as part of the turnkey scope, and the harder gate governing when the system may actually be energized still lives in Electrical System Commissioning. Keeping that distinction on the page is what stops a project-management milestone from being mistaken for a safety sign-off.
Every step in the map
This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.
| # | Step | Shape | Swimlane | Phase | Goes to |
|---|---|---|---|---|---|
| 1 | Customer requirements received | Start | Customer | Requirements & Planning | 2 |
| 2 | Confirm scope, budget and schedule with customer | Process | Project Manager | Requirements & Planning | 3 |
| 3 | Scope, budget and schedule confirmed? | Decision | Project Manager | Requirements & Planning | 4 (Confirmed), 2 (Open items remain) |
| 4 | Develop project plan: milestones, resourcing, phase schedule | Process | Project Manager | Requirements & Planning | 5 |
| 5 | Prepare engineering design, schematics and wiring plans | Process | Engineering | Engineering | 6 |
| 6 | Customer **approves** engineering design and equipment list? | Decision | Engineering | Engineering | 8 (Approved), 7 (Revisions requested) |
| 7 | Revise design per customer feedback | Process | Engineering | Engineering | 6 |
| 8 | Procure equipment, cable and materials against approved design | Process | Procurement | Procurement | 9 |
| 9 | Incoming equipment matches *specification*? | Decision | Procurement | Procurement | 11 (Matches), 10 (Non-conforming) |
| 10 | Return *non-conforming* equipment and reorder | Process | Procurement | Procurement | 8 |
| 11 | Mobilize field crew, install cabling, panels and equipment | Process | Field Electrical | Installation | 12 |
| 12 | Complete *terminations* and installation checks | Process | Field Electrical | Installation | 13 |
| 13 | Perform functional and system testing | Process | QA / Commissioning | Testing & Commissioning | 14 |
| 14 | System passes *commissioning* tests? | Decision | QA / Commissioning | Testing & Commissioning | 16 (Pass), 15 (Fault found) |
| 15 | Diagnose and resolve fault, retest | Process | QA / Commissioning | Testing & Commissioning | 13 |
| 16 | Compile as-built documentation, test reports and O&M manuals | Process | Engineering | Closeout | 17 |
| 17 | Present deliverables to customer for acceptance | Process | Project Manager | Closeout | 18 |
| 18 | Customer **accepts** completed system? | Decision | Customer | Closeout | 19 (Accepted), 17 (Findings outstanding) |
| 19 | Hold project closeout meeting, transfer O&M documentation and warranty terms | Process | Project Manager | Closeout | 20 |
| 20 | Turnkey project closed out, customer system accepted | End | Customer | Closeout | End |
The decision points
Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.
-
3. Scope, budget and schedule confirmed?
Owned by Project Manager · Requirements & Planning
- Confirmed → step 4
- Open items remain → step 2
-
6. Customer **approves** engineering design and equipment list?
Owned by Engineering · Engineering
- Approved → step 8
- Revisions requested → step 7
-
9. Incoming equipment matches *specification*?
Owned by Procurement · Procurement
- Matches → step 11
- Non-conforming → step 10
-
14. System passes *commissioning* tests?
Owned by QA / Commissioning · Testing & Commissioning
- Pass → step 16
- Fault found → step 15
-
18. Customer **accepts** completed system?
Owned by Customer · Closeout
- Accepted → step 19
- Findings outstanding → step 17
Notes on specific steps
These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.
- 1. Customer requirements received
- Scope of work, vessel or site particulars, applicable classification-society rules and the customer's target in-service date are captured here. Every phase downstream, engineering, procurement, installation, commissioning, is scoped against what is recorded in this intake, so a gap here surfaces later as a design built to the wrong assumption rather than a documented requirement.
- 6. Customer **approves** engineering design and equipment list?
- This is a project milestone gate confirming the design and bill of materials before procurement commits spend, not the detailed design-review cycle itself. A customer wanting to iterate on the design in more depth before a turnkey commitment is better served starting from the standalone Electrical Engineering & Design Change SOP.
- 9. Incoming equipment matches *specification*?
- A mismatch here, wrong voltage rating, wrong IP rating, cable gauge that doesn't match the load calculation, is caught against the purchase order before a single item reaches the vessel or site, which is cheaper and faster than discovering it during installation.
- 14. System passes *commissioning* tests?
- This is a project-level pass/fail checkpoint on the commissioning phase Scanel runs as part of the turnkey scope, not a substitute for the hard energization-approval gate inside the Electrical System Commissioning SOP, which still governs when the system is actually allowed to be energized.
- 18. Customer **accepts** completed system?
- Acceptance is checked against the requirements captured at intake, so any gap between what was delivered and what was originally scoped surfaces here, before project closeout, rather than after the crew has demobilized.
Making it yours
Six phases (Requirements & Planning, Engineering, Procurement, Installation, Testing & Commissioning, Closeout) run Horizontal lane; six roles, including Procurement as its own lane, run Vertical lane. When adapting the incoming-equipment decision, keep its Notes naming the specific mismatches that matter to you (voltage rating, IP rating, cable gauge against the load calculation) — the row's own comment names these because catching them against the purchase order is cheaper than discovering them during installation.
What to watch out for
- Don't let 'scope, budget and schedule confirmed' become a formality that always says yes. The map draws its own loop back to re-confirm when open items remain, and a customer relationship this size is exactly where an unresolved scope gap compounds silently through every later phase if it isn't caught here.
- Keep the customer-acceptance decision distinct from the commissioning-pass decision. One is an internal QA checkpoint on the contractor's own commissioning work; the other checks delivered results against what the customer originally required at intake. Collapsing them removes the row where a technically-passing system that still doesn't match the original scope gets caught.
- Don't skip documenting non-conforming equipment returns. The map's own comment says catching a spec mismatch against the purchase order is cheaper before installation than after — but only if the return-and-reorder loop is actually used rather than quietly installing a close-enough substitute to hold the schedule.
Frequently asked questions
How is this different from just chaining together the other SOPs in this cluster?
It's largely the same underlying work, drawn as one accountable chart rather than five handoffs between separately-scoped engagements. The design-approval and commissioning-pass rows explicitly note where this map's gates are lighter than the standalone Design Change and Commissioning SOPs' own gates, because inside a turnkey project those deeper reviews still happen — they're referenced, not duplicated.
What happens if the customer rejects the completed system at final acceptance?
It loops back to 'present deliverables,' with the acceptance decision's own comment noting that any gap between what was delivered and what was scoped at intake surfaces here — before closeout, not after the crew has demobilized. Add a Notes entry recording what the specific gap was, so the reason for the loop is on record.
Do we need a project this size to use the full six-phase version?
If one contractor owns the project end to end — requirements through installation and commissioning — yes, because that's what makes the five gates meaningful as checkpoints on one accountable delivery. A customer who only wants a design produced, or only wants an existing installation serviced, is better matched to the narrower Electrical Engineering & Design Change or Generator & Motor Maintenance process maps.
Open the map and start editing
The editor loads this chart with the spreadsheet underneath it. Change a cell and the diagram redraws — no drawing, no signup.