Skip to content
by Fairlead TechnologiesRequest a demo

Built by pilots

The operating system for maritime pilotage.

One connected platform for the entire operation. Dispatch, rotations, vessels, transportation, support operations and billing on a single operational record, shared with the people and organizations that keep waterways moving.

Request a demo
See the platform

The desk works in the browser. Pilots, agents, boat crew and drivers carry the same operation on iPhone and Android.

MERIDIAN PELAGIA · In Transit · Outer Bar → Windward Point LNG · Board 13:45 · MERCER · CALLAHAN

MERIDIAN PELAGIA · 2 PILOT · LNG · FW draft 38.6′

The job is bigger than the dispatch board.

The shape of the work

One movement, a dozen people who each hold part of it.

The agent who ordered it, the terminal expecting it, the tugs and linehandlers meeting it, the driver getting the pilot there, the crew putting him aboard. Each of them knows something the others need, and most of it still travels by phone through one desk. That coordination is real work, and it grows with the operation.

Today
PilotVessel masterAgentTerminalsTugsLinehandlersDriverHeloCoast GuardDispatchRecords

Information converges on one desk, and reaches everyone else one conversation at a time.

With NeriOS
PilotVessel masterAgentTerminalsTugsLinehandlersDriverHeloCoast GuardNeriOSDispatchPilotsTugsTerminalsTransportationBoat / HeloCoast GuardAccountingOperations

Information is entered once, by whoever holds it, and follows the work to everyone who needs it.

MERIDIAN PELAGIA · Tue · boarded 13:45 · all fast 16:20

The operational record

One movement. The entire record.

The facts captured to execute a movement carry forward into the service record and the billing workflow. Vessel details, assignments, times, and services stay connected without the same information being entered again.

  1. In Transit
  2. Tue · boarded 13:45 · all fast 16:20
  3. Service Record · Draft
  4. Components assembled from the movement
  5. Ready
  6. Invoice INV-2384
The movement
MERIDIAN PELAGIAOuter Bar → Windward Point LNGTue · Board 13:45
In Transit
  • PilotsMERCER · CALLAHAN
  • FW draft38.6 ft
  • Class2 PILOT LNG
  • TugBELLHAVEN CYPRESS
  • All fast16:20
Becomes the service record
Service Record · MERIDIAN PELAGIAOuter Bar → Windward Point LNGTue · boarded 13:45 · all fast 16:20 · LOA 951′ · Beam 149′ · FW draft 38.6′
Draft
  • Pilotage Servicefrom the vessel and the movement
  • Additional Pilotfrom the second assignment
  • Pilot Launchfrom the boarding at Outer Bar
  • Docking / Undockingfrom the arrival at the berth
Components assembled from the movement
No exceptions to review
Ready to invoice
Invoice INV-2384Meridian Chartering Ltd.
Ready
  • MERIDIAN PELAGIA · Outer Bar → Windward Point LNGcarried forward
  • MERIDIAN PELAGIA · Windward Point LNG → Outer Barcarried forward
Two service records · assembled for review

Billing starts from what actually happened. Charges are checked against the tariff that applies, missing information is flagged before an invoice is finalized, and staff review the record instead of re-entering it.

Recurring work

The same few outputs, rebuilt by hand every day.

These get done by hand in most operations, and not for want of effort: the pieces they need are spread across the day’s calls, notes and screens. Once the movements themselves are recorded in one place, the same outputs can be assembled from them.

  • Coast Guard clearance list

    Today

    Compiled by hand, every day

    With NeriOS

    Generated from the movements already recorded

  • Morning traffic summary

    Today

    Compiled and sent by hand, every morning

    With NeriOS

    Assembled and sent on schedule

  • Operating data for the business

    Today

    Exported, then put together for the question being asked

    With NeriOS

    Available in the platform, ready to read

Request a demo

MERIDIAN PELAGIA · Call 12:15 · crew log 13:44 · pickup 16:45

One app, seven portals

Everyone stays connected. Each role gets the view it needs.

Dispatchers work from the Control Console at the desk. Away from it, the same app opens on a different home for each role: pilots, agents, boat crew, drivers, trainees, helicopter operators, and dispatchers themselves. Tugs, VTS and accounting work from the browser. One movement, read by each of them in the shape their job needs.

Pilotthe watch, and the job in hand
Boat crewladder side, transfers, deck log
Agenttheir own ships, every stage
Driverduty status and ride offers

Orders start with the people who know the vessel.

Agents enter the vessel, the movement, and the services in their own NeriOS portal. Dispatch receives structured information it can work from directly, with fewer phone calls and less manual re-entry.

MERCER · CALLAHAN · Watch B · Rest after this job

  1. Dispatchthe working board, assignments, status
  2. Rotations & watcheswatch structure, availability, rest
  3. Ship ordersentered by agents, reviewed by dispatch
  4. Transportationrides and drivers for every assignment
  5. Boats & helicopterslaunch and helicopter operations
  6. Billingservice records and invoicing from operational data
  7. Trainingthe trainee matrix, training pilots, weekly evaluations
  8. Compliancecredential currency and every pilot's history, monitored
  9. Analyticsoperational data, processed and presented the way you need it
  10. Administrationpersonnel, permissions, and audit trails

More than dispatch

The whole operation lives here.

The Control Console is the front of a much larger system. The same platform manages rotation, receives agent orders, coordinates transportation, and carries completed movement data into billing.

Rotation

See the impact before you make the assignment.

Who is up, who is resting, who covered last night and what it cost them: the rotation is a running calculation that has to stay right while the day changes around it. NeriOS keeps the order, the rest clock and the reason for every call in one place, so the roster builds itself as the work happens.

  1. Cover a job, keep your placeTaking a movement out of turn does not cost a pilot their position in the rotation.
  2. The rest clock runs itselfRest follows the rule automatically once a movement completes, instead of being tracked on the side.
  3. Off-watch calls are on the recordWho was called, when, and why, so the answer exists later without anyone having to remember it.
  4. See the rotation at any point in timeThe order as it stood this morning, as it stands now, and as it is expected to stand tonight.

The people, not just the movements

Training and compliance live on the same record.

A trainee's year runs on a living training matrix — required maneuvers with counts, training pilots steering the week's assignments, an evaluation filed every week. And because every movement is attributable, any single pilot's history — credentials, currency, rest — is one screen, not a filing cabinet.

Last 90 days · 812 completed movements

Over time

Every day of operations builds a complete operational dataset.

Because movements are recorded once and carried through dispatch, transportation, and billing, the data stays consistent. Questions that used to be answered from memory can be answered from the record.

Movements per weekUp 31% over eight weeks, concentrated in tanker inbounds

MOCai

Understand what happened, why, and what to expect next.

MOCai is the intelligence layer on top of the NeriOS operational record. It is designed to analyze what happened, explain why, surface patterns, and support planning, with the evidence attached to every answer. The operational decision stays with the professionals responsible for making it.

It advises. Your organization decides.

Operational authority stays with the licensed professionals who hold it. That is a permanent design commitment, not a current limitation.

What the board is likely to look like next.

Alongside the movements already assigned, the rotation engine projects who each upcoming job is expected to reach. It is presented as a forecast and labeled as one, with the confidence attached. A dispatcher’s assignment always replaces it.

  • Projected pilot

    Who the rotation is expected to reach, in italic, with a confidence figure. It is a forecast, never a staged assignment. A dispatcher’s assignment always wins and replaces it.

  • Trainee ride request

    A starred name is a trainee who asked for that ride from their phone. Asking is not being assigned. The whole board sees the request, and the dispatcher still decides.

Being built toward

Using the operating history to answer bigger questions.

  • When is the soonest a given ship can sail?
  • How many pilots are needed today?
  • How many will be needed in twelve, twenty-four, thirty-six months?
  • Can a dispatch rule that protects more rest be tested before it is adopted?

The forecasting layer is not shipped. It is named here as direction rather than as a feature, because what it depends on is the clean operational record NeriOS is building now.

As the operation grows

More activity, not more work.

More movements mean more calls, more updates, more to enter and more people asking dispatch where things stand. That increase lands somewhere. It should land on the software.

  • More movementsEntered at the source, by the people closest to them
  • More calls and updatesUpdates follow the movement to everyone on it
  • More information to enterEntered once, then carried forward
  • More recurring tasksRoutine work runs on its own
  • More questions for dispatchEach role can already see the answer

Trust & confidentiality

Your operation stays yours.

NeriOS connects the people and workflows that need to work together without making everything visible to everyone. Connected does not mean exposed.

  • Built around organizational boundaries

    NeriOS is multi-tenant, and multi-tenant must not mean casually shared. The platform is designed around organization-level boundaries in the data model, database security policies, and application access controls. Access is scoped by organization and role, so one organization’s information is not another organization’s information.

  • Access follows responsibility

    A dispatcher, a pilot, a driver, an agent and a billing user each see the surface appropriate to their role and their organization. Privileged platform administration is separated from ordinary organizational access.

  • Designed for accountability

    Operational changes leave a trail. Records carry who entered them, when, and what changed, and critical actions write to an audit log the organization can review.

Fairlead does not treat customer operational information as marketing material. The product interfaces on this page are shown with synthetic demonstration data.

Fairlead Technologies

Built by pilots.

NeriOS is developed by Fairlead Technologies, LLC. Led by working pilots, our development team understands firsthand the challenges common to pilotage operations and built an integrated platform to solve them.

  • Support continues after go-liveImplementation is the start of the relationship, not the end of it.
  • Routine changes are includedAn operation changes. Keeping the software matched to it is part of the arrangement, not a fresh negotiation each time.
  • A manual for every roleWritten for the work that role actually does, and kept current as the product moves.
Request a demoA short note about your organization is plenty. We’ll take it from there.