THE BUSINESS OF THE WORKING WATERFRONT
Field guidesAbout the brief ↗
THEWaterfront Brief.
MARITIME BUSINESS.
WATERFRONT DEVELOPMENT.
TECHNOLOGY THAT CONNECTS THEM.

Marine Electrification / Infrastructure guide

Shore power planning: vessel, berth & utility interfaces

Scope a shore power project by clarifying onboard loads, berth arrangements, utility requirements, operating windows, and ownership.

THE TAKEAWAY

Name the loads and the operating window before choosing equipment.

Say what the power connection is for

“Shore power” can mean supplying onboard loads at berth. A battery-electric or hybrid ferry project may additionally need propulsion charging within a service schedule. State both the intended function and the operating conditions in the brief so the project team can establish the appropriate technical scope.

Document vessel types, berth locations, typical and exceptional stays, access, and planned changes to the operation. Qualified electrical, vessel, terminal, and utility teams need a shared set of assumptions.

Define the project interfaces

Define the project interfaces
InterfaceQuestions to resolve
Onboard loadsWhat must be supplied, under what conditions, and who verifies the data?
Berth arrangementWhere will the vessel connect and how does that affect access?
Utility connectionWhat is the connection process and what evidence is needed?
OperationWho connects, monitors, maintains, and responds to faults?
Future changeWhich additional vessels or service patterns should be considered?

Keep the utility conversation inside the program

Do not treat the utility interface as a final administrative step after equipment selection. Establish the information the utility needs, its process, and the responsibilities for any connection works. Separate confirmed information from assumptions and give unresolved items an owner.

For fleet charging context, WSDOT’s public ferry electrification program describes terminal and vessel charging work as part of one system effort. That illustrates why the shore and vessel programs need coordination; another project still needs its own technical evaluation.

Ask for an interface register at handover

A practical register records the requirement, its evidence source, the team responsible, the decision date, and the dependency if it changes. Use it alongside technical deliverables and the operating plan.

The result should help the owner see which decisions are ready, which depend on specialist work, and which assumptions could affect the sequence. Equipment ratings and engineering acceptance need project-specific professional analysis.

Sources & research notes

Company capabilities are based on the primary sources below. Scenario calculations, scope checklists, and fit assessments are our editorial analysis.

A practical starting point for the next project conversation. How we research and compare ↗