- Gas generator speed
- Exhaust temperature
- Expected light-off
SailPlan connects to equipment that was never built to talk to anything. It fuses that telemetry with the manuals, service reports and history around it, and gives every application and AI tool one model to work from. Proven at sea.
reg 40211 = 0x0264PGN 61444 SPN 190 = 0x3840$GPRMC,…,A,…,12.4,047.0,…unit 2 · reg 40070 = 960A real operating question needs live data, documents, records and the people on site, and they have always lived in different places. The same edge, the same data model and the same interfaces answer it at sea, in a generator yard and across a busy port. Pick one.
Gas turbine 2 was slow to light off this morning. What happened, and what should we check?
2 earlier slow starts. Both cleared by igniter work.
Light-off on GT-2 came 6 seconds late on the last two starts. Its igniters were replaced 14 months ago, and the two earlier slow starts in its history were both cleared by igniter work. Check the igniters first, then run the Firing speed and light-off procedure.
Illustrative scenario, built the way the SailPlan demo works: live telemetry, equipment manuals and procedures, and written service reports answering one question together.
Why is Gen 2 running hot?
“Coolant temp on Gen 2 keeps creeping up under load since Saturday. Do we have coolant filters in stock?”
Coolant has been climbing under load since Saturday, matching the operator's report. Load is within the 2,000 kW rating, so the engine is not overworked. 4 coolant filters are in stock in the site store.
Illustrative scenario: one generator in a 15-unit yard on prime power. The same record works for standby generators.
What drove Tuesday morning's peak at the north gate, and what do we change?
Trucks queued at the north gate from 07:00, about 40 at the peak.
Two vessels berthed at the north terminal within 35 minutes, and about 40 trucks queued at the gate to meet them. The plume model places the peak on the terminal, not the highway. Staggering berth windows and gate appointments flattens it, and cuts the energy spent idling. The stakeholder report is drafted from the same data.
Illustrative scenario: sensors, a plume model, cameras and vessel traffic fused into one picture of how a port uses energy, and one source for the reports its stakeholders need. Aerial imagery: USDA NAIP via USGS The National Map.
Every OEM, controller and sensor has its own protocol, tags and units. The context that explains the numbers sits in manuals, logs and spreadsheets. SailPlan pays that translation cost once.
Edge software reads PLCs, engine controllers, analyzers and sensors directly: Modbus TCP and RTU, OPC UA, J1939/CAN, NMEA 0183 and 2000, 4–20 mA, EtherNet/IP, S7 and legacy serial. A new site is a configuration file, not a software project.
One data model normalizes every vendor, unit and tag, and catches dirty data on the way in. Telemetry, manuals, spare parts, service reports and crew emails all resolve to one equipment record.
A REST API and an MCP server put the whole model in reach of Claude, ChatGPT, Copilot or your own dashboards. It is not tied to any AI vendor. When a better model ships, your data is ready.
A ship crosses oceans on satellite and can lose every link for days. A generator yard sits behind a locked-down site firewall. The edge keeps reading either way.
Prime or standby power at a data center, a hospital, a water plant or any critical site. One SailPlan edge in the switchgear room polls every generator, keeps the data on site until the cloud has it, and gives operations full telemetry and observability.
A ship is a plant with decades-old machinery, bad connectivity and an inspector on board. Shore sites have the same problem with fewer constraints.
Government and commercial fleets. Main engines, gas turbines, generators and navigation, fleet-wide.
Air-quality sensors, plume models, gate cameras and AIS fused into one view of energy use, footprint and stakeholder reporting.
Tank pressure, boil-off gas, compressors and gas detection, on carriers, fuelling ships and terminals.
Prime and standby generators, switchgear and power chain. The LM2500 that drives a ship also runs a power plant.
Data centers, hospitals, water plants and telecom sites: the standby power and cooling that keep them running.
Barges, rail, trucking and pipelines: anything with a controller, a sensor or a manual.
Live condition of every asset, compared across sites and against each machine's own history. The failure signs your engineers already know become automatic alerts.
What does the procedure say for this alarm? The live reading, the manual page and the maintenance history in one answer. No more digging through binders.
True cost per operating hour. Purchase, energy, maintenance and downtime by asset, site or vendor.
Is tank pressure trending toward a limit? Pressure, boil-off and compressor load, read together.
How fast are these assets wearing? Failure rates by make, model and duty cycle.
Sentinel values, GPS dropouts to 0,0, flatlined probes and impossible states are flagged before they reach a report.
Root cause traced across equipment data, maintenance logs and service reports at once.
Coverage, claims and service history for every component, one query away.
See SailPlan connect your machines, manuals and records into one model.