# Portepoch

*/Startups/Portepoch*

## Startup Overview

This terminal operations platform optimizes berth scheduling by ingesting real-time crane telemetry. Port authorities and terminal managers face constant dock congestion when ships arrive off-schedule or loading times fluctuate. By replacing static planning with dynamic execution, the system actively reallocates dock space and equipment as conditions change on the water and in the yard.

Traditional terminal operating systems like Navis N4 and Tideworks TOS, along with manual spreadsheet schedules, rely on delayed reporting and siloed planning modules. This solution bypasses manual entry through native integration with existing terminal sensors. It reads live equipment statuses and physical movement data to build accurate, minute-by-minute schedules for ship placement and crane assignment.

The platform discards rigid enterprise licensing in favor of outcome-based pricing. Operators pay strictly per container moved, directly aligning the cost of the software with the terminal throughput and operational capacity it delivers.

## Startup Founding Hypothesis

**Approach**: that optimizes berth scheduling using real-time crane telemetry
**Competitors**:
- [Navis N4](/Competitors/Navis_N4)
- [Tideworks TOS](/Competitors/Tideworks_TOS)
- [Spreadsheet-based scheduling](/Competitors/Spreadsheet-based_scheduling)
**Differentiator2x2**: outcome-priced per container and natively integrated with terminal sensors

## Startup Solution Coordinate

**Solution**: [Berth Telemetry Director](/Services/Berth_Telemetry_Director)

## Startup Position2x2

```mermaid
quadrantChart
    title Portepoch Competitive Landscape
    x-axis "Fixed Software Licensing" --> "Outcome-Priced Per Container"
    y-axis "Manual / Siloed Data" --> "Native Sensor Integration"
    quadrant-1 "Real-Time Optimization"
    quadrant-2 "Legacy Enterprise TOS"
    quadrant-3 "Manual Operations"
    quadrant-4 "Cost-Efficient but Siloed"
    "Navis N4": [0.15, 0.80]
    "Tideworks TOS": [0.25, 0.65]
    "Spreadsheet-based scheduling": [0.10, 0.15]
    "Portepoch": [0.90, 0.90]
```

## Startup Offer

**Proof**:
- Targeting a 10-15% reduction in vessel idle time for regional terminal operators.
- Aims to process live telemetry from 50+ cranes simultaneously with sub-second schedule recalculation.
- Designed to increase overall quay crane utilization rates without requiring new hardware.
**Tiers**:
- Name: Single Berth Pilot · Price: ~$0.15–$0.30 per TEU (Twenty-foot Equivalent Unit) · Inclusions: Real-time telemetry ingestion and dynamic scheduling for one active berth, capped at 25,000 TEUs per month.
- Name: Terminal Fleet · Price: ~$0.08–$0.18 per TEU · Inclusions: Multi-berth schedule optimization, automated Terminal Operating System (TOS) sync, and predictive delay alerts for up to 150,000 TEUs per month.
- Name: Port Network · Price: Custom rate based on annual container volume · Inclusions: Unlimited berths across multiple terminal facilities, bespoke hardware sensor mapping, and on-premises edge deployment options.
**Guarantee**: Guarantees a measurable reduction in average vessel turnaround time during the first 90 days; if baseline benchmarks are not improved, the container usage fees for that quarter are fully refunded.
**Business Function**: ProvideService
**Objection Handlers**:
- Objection: We already use Navis N4 for our terminal operations. Rebuttal: Portepoch is designed to integrate alongside your existing TOS, reading live crane data and pushing optimized schedule adjustments back to N4.
- Objection: Our crane sensors are legacy and do not offer modern APIs. Rebuttal: The platform intends to support raw industrial protocols (like OPC UA and Modbus) to standardize telemetry locally before cloud ingestion.
- Objection: Outcome pricing per container makes our software budget unpredictable. Rebuttal: Usage billing includes pre-negotiated monthly caps to eliminate budget overrun risk during unexpected peak surge windows.
- Objection: A cloud-based scheduler poses a risk if terminal internet goes down. Rebuttal: The scheduling engine is designed to fall back to a local edge appliance, maintaining continuous operations offline.
**Pricing Architecture**: UsageMeter

## Startup Brand

**Voice**: Authoritative and precise, grounded in heavy maritime logistics.
**Tagline**: Turn crane telemetry into optimized terminal berth schedules.
**Icon Concept**: Container
**Palette Intent**: industrial-safety
**Visual Identity**: The visual identity contrasts hi-vis safety yellow and heavy steel gray with utilitarian, monospaced typography suited for harsh maritime environments.
**Archetype Reference**: the-ruler

## Startup Buyer Chain

**Chain**: Portepoch → Terminal Operators → Shipping Lines
**Gtm Motion**: Acquires terminal operators via limited-scope pilots on a single high-traffic berth, leveraging existing crane sensor data to prove scheduling efficiency without replacing the core TOS. Expands across the port authority's full footprint through an outcome-based pricing model that scales incrementally per additional container handled.
**Agent Channel**: Designed to publish berth availability schedules and predictive turnaround telemetry into a structured API registry, intended for discovery by autonomous freight-routing agents and global supply chain orchestration bots.
**Primary Channel**: Targeted outbound to Terminal Operations Directors and Harbor Masters, paired with technical capability demonstrations at maritime logistics conferences like TOC Americas and port infrastructure forums.

## Startup Customer Journey

```mermaid
flowchart LR\nA[Maritime Conference Demo] --> B[Single Berth Pilot]\nB --> C[Crane Telemetry API]\nC --> D[Navis N4 Interface]\nD --> E[Terminal Fleet Tier]\nE --> F[Port Network Tier]\nF --> G[Autonomous Freight Agent]
```

## Startup Proof Points

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Pilot Goals**:
- 90-day Single Berth Pilot (capped at 25,000 TEUs per month): Establish baseline vessel turnaround times and validate a measurable reduction in average idle time to trigger the performance guarantee.
- 60-day Offline Resilience Pilot: Simulate intermittent terminal internet outages to prove the scheduling engine seamlessly falls back to the local edge appliance and maintains operations.
**Target Metrics**:
- Target: 10-15% reduction in average vessel turnaround time within the first 90 days.
- Aim: Sub-second schedule recalculation speeds while concurrently processing live telemetry from 50+ active cranes.
- Target: 0 dropped operations during cloud-to-edge fallback transitions in the event of terminal network loss.
- Aim: 100% automated synchronization of multi-berth schedule adjustments into existing Terminal Operating Systems.
**Target Case Studies**:
- Regional terminal operator handling up to 150,000 TEUs per month: Prove a reduction in vessel idle time by seamlessly pushing dynamic schedule adjustments back to their existing Navis N4 system.
- Large multi-berth port facility: Validate the ability to ingest raw telemetry from legacy sensors via Modbus and OPC UA, increasing overall quay crane utilization without requiring new hardware installs.
- High-volume maritime logistics hub: Demonstrate continuous scheduling operations during internet connectivity outages by utilizing the local edge appliance fallback.
**Testimonial Targets**:
- Terminal Operations Director: Relief that Portepoch automatically adjusts scheduling in real-time, reducing crane idle time without requiring staff to abandon their existing TOS.
- Port IT Infrastructure Manager: Satisfaction with the immediate ingestion of legacy crane telemetry via raw industrial protocols, eliminating the need for expensive API retrofits.
- Maritime Facility CFO: Confidence in the usage-metered pricing model, explicitly praising the pre-negotiated monthly TEU caps that prevent budget overruns during unexpected cargo surges.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Port labor unions block the deployment of crane telemetry sensors over concerns regarding automated worker tracking and job displacement. · Mitigation Status: unmitigated
- Severity: high · Description: Legacy Terminal Operating System incumbents like Navis N4 restrict API access to prevent Portepoch from reading live terminal data. · Mitigation Status: in-progress
- Severity: high · Description: Terminal operators dispute outcome-based pricing invoices by attributing berth efficiency gains to external factors like weather or vessel delays. · Mitigation Status: unmitigated
- Severity: moderate · Description: Harsh marine environments degrade physical telemetry sensors on cranes, leading to data dropouts that break the real-time scheduling algorithm. · Mitigation Status: in-progress

## Startup Competitors

- [Navis N4](/Competitors/Navis_N4) — Incumbent TOS
- [Tideworks TOS](/Competitors/Tideworks_TOS) — Incumbent TOS
- [Spreadsheet-Based Scheduling](/Competitors/Spreadsheet-Based_Scheduling) — Status Quo
- [Portchain Berth Optimization](/Competitors/Portchain_Berth_Optimization) — Point Solution
- [CyberLogitec OPUS](/Competitors/CyberLogitec_OPUS) — Legacy TOS
- [Kaleris Execution System](/Competitors/Kaleris_Execution_System) — Enterprise Suite

## Startup Solution Stack

- [Berth Scheduling Service](/Services/Berth_Scheduling_Service) — Service-as-Software
- [Berth Allocation Agent](/Agents/Berth_Allocation_Agent) — Agent
- [Crane Telemetry Worker](/Agents/Crane_Telemetry_Worker) — Agent
- [Sensor Ingestion API](/Software/Sensor_Ingestion_API) — Software
- [Container Pricing Engine](/Software/Container_Pricing_Engine) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the port's technical architect of flow, not a dispatcher fighting delays
- **Want**: to maximize quay crane utilization and minimize vessel idle time
- **Identity**: the operations director at a regional container terminal
**Plan**:
- Step: Input parameters · Detail: Define your vessel arrival windows and crane availability within the optimization dashboard.
- Step: Validate throughput · Detail: Review the live telemetry-driven schedule to verify crane cycle times against actual sensor data.
- Step: Sync operations · Detail: Push the optimized berth sequence directly into your existing Tideworks or Navis N4 system.
**Guide**:
- **Empathy**: Does your berth scheduling still cause vessel bunching because crane performance varies?
**Problem**:
- **Villain**: uncoordinated telemetry
- **External**: Scheduling in Navis N4 relies on static estimates while live quay crane telemetry remains trapped in isolated industrial protocols.
- **Internal**: You feel like you are flying blind while million-dollar assets sit idle during peak surge.
- **Philosophical**: Every terminal operator deserves precise vessel windows based on real machine performance — not spreadsheet guesses.
**Success**: Berth schedules stay synchronized with real-time crane performance, cutting idle time and stabilizing terminal throughput.
**One Liner**: Disconnected crane telemetry costs terminal operators vessel idle time. Portepoch optimizes berth schedules using real-time sensor data so throughput increases without adding new hardware.
**Positioning**:
- **So That**: turnaround times drop using real-time crane telemetry data
- **Unlike**: spreadsheet-based scheduling and static TOS modules
- **For Whom**: regional container terminal operations directors
- **Category**: AI-driven berth optimization software
**Call To Action**:
- **Direct**: Schedule a berth pilot
- **Transitional**: View telemetry schema
**Failure Stakes**:
- Increasing vessel turnaround times
- Unpredictable quay crane idle costs
- Missed berth productivity benchmarks
**Transformation**:
- **To**: the maritime terminal's efficiency authority
- **From**: a terminal lead managing Navis N4 through manual workarounds
**Controlling Idea**: Real-time crane telemetry must drive the berth schedule to eliminate port congestion.

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Disconnected crane telemetry costs terminal operators vessel idle time. Portepoch optimizes berth schedules using real-time sensor data so throughput increases without adding new hardware.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 109c1172a2dcd43b

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: AI-driven berth optimization software for regional container terminal operations directors. Unlike spreadsheet-based scheduling and static TOS modules — turnaround times drop using real-time crane telemetry data.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: f82353052d05e2d2

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Scheduling in Navis N4 relies on static estimates while live quay crane telemetry remains trapped in isolated industrial protocols.
Solution: Disconnected crane telemetry costs terminal operators vessel idle time. Portepoch optimizes berth schedules using real-time sensor data so throughput increases without adding new hardware.
Customer: regional container terminal operations directors
Unlike: spreadsheet-based scheduling and static TOS modules
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: c14ff7b02aa5f9db

## Startup Token M E D D P I C C

**Pain**: Scheduling in Navis N4 relies on static estimates while live quay crane telemetry remains trapped in isolated industrial protocols.
**Metrics**: Target: Berth schedules stay synchronized with real-time crane performance, cutting idle time and stabilizing terminal throughput.
**Rendered**: Pain: Scheduling in Navis N4 relies on static estimates while live quay crane telemetry remains trapped in isolated industrial protocols.
Economic buyer: Terminal Operators
Metrics: Target: Berth schedules stay synchronized with real-time crane performance, cutting idle time and stabilizing terminal throughput.
Competition: spreadsheet-based scheduling and static TOS modules
**Mechanism**: spine-derived-v1
**Competition**: spreadsheet-based scheduling and static TOS modules
**Economic Buyer**: Terminal Operators
**Vocab Fingerprint**: 9a50c5c335258d2c

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: AI-driven berth optimization software for regional container terminal operations directors

regional container terminal operations directors — Scheduling in Navis N4 relies on static estimates while live quay crane telemetry remains trapped in isolated industrial protocols. Disconnected crane telemetry costs terminal operators vessel idle time. Portepoch optimizes berth schedules using real-time sensor data so throughput increases without adding new hardware.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 85b54c7dbc0cc6c3

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: AI-driven berth optimization software. Disconnected crane telemetry costs terminal operators vessel idle time. Portepoch optimizes berth schedules using real-time sensor data so throughput increases without adding new hardware. Serves regional container terminal operations directors.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: 73aa7d4dee0a4571

## Neighborhood

### Candidate solutions

- [Demonstrate Virtual CFO Value](/Problems/Demonstrate_Virtual_CFO_Value) — candidate solution for · Problems

### What it offers

- [Berth Telemetry Director](/Services/Berth_Telemetry_Director) — offers · Services

### Composed of

- [Berth Allocation Agent](/Agents/Berth_Allocation_Agent) — composes · Agents
- [Berth Scheduling Service](/Services/Berth_Scheduling_Service) — composes · Services
- [Crane Telemetry Worker](/Agents/Crane_Telemetry_Worker) — composes · Agents
- [Sensor Ingestion API](/Software/Sensor_Ingestion_API) — composes · Software
- [Container Pricing Engine](/Software/Container_Pricing_Engine) — composes · Software

### Embodies

- [Service-as-Software](/Theses/Service-as-Software) — embodies · Theses

### Competitors

- [Navis N4](/Competitors/Navis_N4) — competes with · Competitors
- [Portchain Berth Optimization](/Competitors/Portchain_Berth_Optimization) — competes with · Competitors
- [CyberLogitec OPUS](/Competitors/CyberLogitec_OPUS) — competes with · Competitors
- [Spreadsheet-Based Scheduling](/Competitors/Spreadsheet-Based_Scheduling) — competes with · Competitors
- [Kaleris Execution System](/Competitors/Kaleris_Execution_System) — competes with · Competitors
- [Tideworks TOS](/Competitors/Tideworks_TOS) — competes with · Competitors

### Similar Startups

- [Managerquay](/Startups/Managerquay) — similar · Startups
- [Zerowharf](/Startups/Zerowharf) — similar · Startups
- [Baywharf](/Startups/Baywharf) — similar · Startups
- [Heavywharf](/Startups/Heavywharf) — similar · Startups
- [Autonomousquay](/Startups/Autonomousquay) — similar · Startups
- [Spotterquay](/Startups/Spotterquay) — similar · Startups
- [Jointoptimaquay](/Startups/Jointoptimaquay) — similar · Startups
- [Auroraquay](/Startups/Auroraquay) — similar · Startups
- [Acceleratedock](/Startups/Acceleratedock) — similar · Startups
- [Stridewharf](/Startups/Stridewharf) — similar · Startups
- [Autonomywharf](/Startups/Autonomywharf) — similar · Startups
- [Depotport](/Startups/Depotport) — similar · Startups
- [Crossyard](/Startups/Crossyard) — similar · Startups
- [Autopilotdock](/Startups/Autopilotdock) — similar · Startups
- [Cornerstonedock](/Startups/Cornerstonedock) — similar · Startups
- [Cadencevessel](/Startups/Cadencevessel) — similar · Startups
- [Cargofield](/Startups/Cargofield) — similar · Startups
- [Basisyard](/Startups/Basisyard) — similar · Startups
- [Truewharf](/Startups/Truewharf) — similar · Startups
- [Floorfuel](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Floorfuel) — similar · Startups