Financial Planning for a
Port Operator That Doesn't Pause
A major port and terminal operator on the West Coast needed a planning environment that could move at the speed of the business — across terminals, entities, and operational lines that don't stop for budget season. We were honored to help.
Planning for a Business That Runs Around the Clock
A major port and terminal operator on the West Coast was running its financial planning across a complex structure of operating entities, terminals, and service lines — each with its own cost dynamics, its own labor model, and its own revenue patterns. Vessel calls, container volumes, equipment utilization, and labor costs shifted by the day, and the planning environment was struggling to keep up.
Existing planning was fragmented. Some entities planned in spreadsheets. Others used disconnected tools. Consolidation was slow, version control was inconsistent, and Finance leadership had no single, trusted view of how the business was actually trending against plan. The work to fix it had to happen without disrupting daily operations — because at a port, operations never pause.
"The business doesn't stop. Vessels arrive. Containers move. Labor shifts. The planning system had to live in that reality — not pretend it didn't exist."
Understand the Operation First. Build the Planning System Around It.
Before any architecture decisions were made, the work started where it always does — listening. Sitting with Finance, with terminal operations leaders, with the people responsible for forecasting labor, equipment, and revenue across the port's lines of business. The goal wasn't to bring a generic planning template and force the operation into it. The goal was to understand the operation deeply enough to build planning around the way it actually runs.
The chosen path: a unified Oracle EPM Cloud environment built to support multi-terminal, multi-entity planning — with driver-based logic that reflected how vessels, volumes, and labor actually shape financial outcomes, and a consolidation model that respected the operational structure beneath it.
- Mapped each terminal's planning patterns and operational drivers before building the architecture
- Designed a unified Oracle EPM Cloud environment supporting multi-terminal, multi-entity consolidation
- Built driver-based planning that reflected vessel calls, container volumes, equipment utilization, and labor patterns
- Partnered closely with Finance leadership on chart of accounts alignment across operating entities
- Designed the planning workflow to integrate with the operational rhythm — not impose a finance rhythm on operations
Every architectural decision was made against a single test: does this help the team plan more accurately, more quickly, and with more confidence? When the answer was yes, the decision moved forward. When it wasn't, the design kept evolving.
A Planning Environment That Moves at the Speed of Operations
From Fragmented Planning to a Unified Architecture
A Planning Environment Built Around the Operation.
When Finance opened the planning environment, what they saw wasn't a generic budgeting system trying to fit a port. It was their port — terminals, entities, vessel patterns, labor structures — modeled in a way that matched how the business actually runs. Plans could be built faster. Variances had context. Conversations across Finance and Operations had a shared frame of reference for the first time.
"The best financial planning systems don't ask the business to slow down. They keep pace with the operation — and help leadership see further ahead because of it."
The architecture was finished. The Finance team carried it forward. And the planning conversations across terminals, operations, and headquarters started to sound different — more grounded, more specific, more useful.
We're grateful for the trust the team placed in us — and for the chance to help build something that respected the realities of a port that never stops.