labs@atheron:~/industries/ports-marine/integrations$ connect --systems --automate

Terminal systems

Your terminal, gate, billing and port systems kept in step.

Most terminals run four or five systems from different vendors, and staff copy vessel and container data between them. An integration hub joins them through one API, so a change in one system reaches the others once, with nothing lost and nothing doubled.

Start a project See the example projects

// what matters here

What is different in this industry.

Built on published APIs

Each connector uses the system's published API or file exchange. We check yours before we quote.

Nothing lost, nothing doubled

Every message is retried when a system is down and checked so it is never applied twice.

A log you can search

Every message between systems is logged, so a missing invoice or call can be traced in minutes.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectAPI

Terminal systems hub

Hypothetical. Not a client, not a result.

// The problem

A terminal runs a terminal operating system, a gate system, billing and a port community system that do not talk to each other, so staff copy vessel and container data between them all day.

// What we would build

An integration hub that keeps the terminal operating system, the gate system, billing and the port community system in step through one internal API, with webhooks for changes, retries when a system is down, and a log of every message. Built on each system's published API; we check yours before we quote.

// What is in it

One internal API for vessels, calls, containers and invoices
Connectors to four systems, each with its own limits handled
Webhooks when a call or a container changes
Retries and a dead-letter queue, so nothing is lost or doubled
Monitoring and a searchable log of every message

// Stack

Node.js
PostgreSQL
OpenAPI
Message queue
DigitalOcean

// estimate

Build: ≈ US$71,800 to US$110,000, delivered within 17 weeksCAD 102,300 to 156,400
Hosting: ≈ US$344 a monthCAD 490 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

API contract agreed: 2.9 to 3.9 weeks
Slot rules agreed with your operations team: 1.4 to 1.9 weeks
Core resources built: 3.4 to 5.4 weeks
Security, gateway and connections: 1.9 to 3.4 weeks
Docs, SDKs and load tests: 1.4 to 1.9 weeks
Launch and first callers: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

AIS data provider account: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 20,460 to 31,280
API contract agreed 7.6%: CAD 7,774.80 to 11,886.40
Slot rules agreed with your operations team 8.7%: CAD 8,900.10 to 13,606.80
Core resources built 22.9%: CAD 23,426.70 to 35,815.60
Security, gateway and connections 15.3%: CAD 15,651.90 to 23,929.20
Docs, SDKs and load tests 7.6%: CAD 7,774.80 to 11,886.40
Launch and first callers 7.9%: CAD 8,081.70 to 12,355.60
Holdback, 30 days after launch (10%): CAD 10,230 to 15,640

Start from this example

// questions

Questions we get about this.

Can it connect to our port community system?

If it offers an API or a file exchange, yes. Each system joined is priced as its own connector.

What happens when the terminal system is down?

Messages wait in a queue and are sent when it is back, in order, with nothing doubled.

Could an off-the-shelf connector do this for a terminal?

If one does what you need, use it, and we will say so. Custom work pays off when your rules and systems are more than a connector can handle.

Back to the industry: Ports, shipping and marine About the service: Integrations and automation

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call