Founding operator story · Pig-Tainer
From whiteboard and terminal tabs to one operating board
Pig-Tainer is the founding operator Conterminal was built inside. Not an arm's-length reference account. Its internal yard board became the multi-tenant platform Pig-Tainer now runs on as one tenant, on live work.
- Founding
- Operator and product proving ground
- Live
- Container, vessel, driver and dispatch work
- Reviewable
- Document and credential intake
- Building
- Billing and driver settlement
The company
The working drayage carrier Conterminal was built inside. Now it runs as a tenant.
Pig-Tainer is a working drayage carrier. It is where Conterminal's operating model first met real containers, drivers, deadlines, and terminal sources. We do not present it as an independent customer endorsement.
Conterminal began as the board Pig-Tainer's dispatchers worked from. Rebuilding that internal system as a multi-tenant platform forced the product to separate one carrier's habits from the durable container record every operator needs.
The challenge
Before Conterminal.
The information existed. It just arrived late and lived in different tools. The daily job wasn't missing data. It was rebuilding context from whiteboards, calls, spreadsheets, and terminal tabs.
Status scattered across provider sites
Container and vessel milestones lived across terminal, rail, and steamship-line sources. Someone checked each one, then copied it back into the carrier's own working view.
Dispatch and driver readiness were separate
The shift board, driver credentials, equipment status, and return deadlines never shared one operating record. So the desk reconnected them by hand.
The update often arrived after the decision
A schedule change, hold, credential lapse, or return-document gap went urgent only after someone called, a driver waited, or a cost clock kept running.
The approach
What they run now.
Pig-Tainer's current operating view pulls container and vessel status, driver readiness, at-risk return work, and the dispatch plan onto one board. It leads with what changed and what needs a decision, then opens into the source and workflow behind it.
External status enters the record through connected provider sources. Arrival conflicts get reconciled by source precedence. Return risk stays visible until the physical gate event and the required paperwork agree. Billing and driver settlement remain in development. We do not present them as finished scope.
Operational evidence
Running on real freight.
Credential intake with a reviewer
Driver documents can extract into suggested fields while the source stays visible. A reviewer confirms the result before it updates the driver record.
Driver context beside the shift
The driver roster, credential expirations, and supported Motive ELD context sit beside dispatch work. No rebuilding from separate systems.
Return risk requires two facts
A termination return stays at risk until both the physical gate-in and the required interchange receipt exist. The board names which side of that proof is still missing.
Conflicting arrival data stays visible
On-water tracking records the competing sources, applies documented precedence, and rejects implausible arrival signals. It does not make the dispatcher choose between unexplained dates.
What the story proves
Pig-Tainer remains the founding operator behind Conterminal. A live environment for container, vessel, driver, and dispatch work. The evidence is operational depth, not an independent testimonial. And the unfinished billing and settlement work stays labeled as unfinished.
Explore the operating layers
Get started
See the platform behind the operator story.
Bring your own containers and operating questions. We'll show you the same working system on your freight.