LOOP is an AI assistant built for engine rooms, power plants, and industrial operations. Ask it anything about your machinery — it answers from your own rounds history and equipment manuals, even completely offline.
● Online · Vessel data loaded
LOOP isn't a generic chatbot. It's trained on your vessel's own rounds history, work orders, and equipment documentation — so its answers are specific, grounded, and useful.
LOOP can access and reason over your complete rounds history. Ask it about any reading, any trend, any period.
Upload equipment manuals and maintenance schedules. LOOP references them when answering — and tells you which section.
No internet required. LOOP runs locally on the vessel. Works in the middle of the Pacific the same as in port.
Answers are drawn from your own rounds history and manuals, with sources shown where they apply. Ask from a tablet and passages from the ship's library come back tagged with document and page, and the tag opens the scanned page. It is instructed rather than enforced, so check the page before you act on it.
Ask "when did we last see this?" and LOOP retrieves the exact record — without anyone having to dig through binders.
In the engine room, hands are busy. Ask LOOP a question by voice — it transcribes and responds immediately.
LOOP is field-tested on active vessels. Data stays on your ship — no uploads to external servers, no cloud dependencies, no latency.
Generic AI assistants give generic answers. LOOP gives answers grounded in your vessel's actual data.
LOOP is designed for the practical questions that come up during a watch — not abstract knowledge tests.
Describe a symptom and LOOP walks through the most likely causes in order of probability, cross-referenced with your vessel's maintenance history.
Ask LOOP to interpret what a trend in your rounds data means — whether it's normal variation or a developing issue worth investigating.
Find any maintenance record instantly without digging through binders. LOOP retrieves the exact job card, date, who did it, and what was found.
New crew can ask LOOP "what should I know about this engine room?" and get a summary of open items, current watch points, and recent exceptions.
Instead of hunting through PDF manuals, ask LOOP. It finds the relevant section and summarizes the procedure in plain language.
Asking questions is the smallest thing LOOP does. Most of the day it is moving worklists, logging completed jobs and sending the paperwork out — over the ship's own mail account, from a hub PC in the engine control room. Every item below was verified against the shipboard source before it was written here, and each carries what it depends on.
Mail the hub and it sends back every open item across the ship's worklists, each row numbered. Reply to that mail to complete, postpone, reactivate, delete, re-word, add or move items — edit the table rows in place, or type lines that quote the numbers. Items raised this way go through the same admin approval as items raised on a tablet.
Needs the hub PC running with email ingestion switched on and a mail account configured — it ships off by default — and your address on the hub's trusted-contact list.
Completed work is kept on the vessel as a table: the job, the worklist it came from, the machine, the name recorded by whoever closed it, when, and any note or photo. It replicates between the tablets and the hub, and you can ask for it by email and narrow it to one person or one machine, or group it by equipment. The print layout is built to not waste paper.
Same email prerequisites as above. A job closed from the wall display or by an email reply records that channel rather than a crew member's name.
Finish a round on the tablet and the hub builds the summary and mails it — every reading with its change since it was last taken, anything out of limits, the watchkeeper's notes and photos, and a trends chart. Give a round a recipient list once in the round builder and nobody has to remember again. Rounds set up for it also print a copy on completion.
The hub PC builds and sends it, not the tablet, so the hub has to be running. Sending needs the mail account configured; printing needs the printer reachable from the hub.
LOOP reproduces the vessel's own engine logbook sheet (Form 629) and fills it from readings the crew already entered. About 230 of its roughly 425 boxes are wired to an element in the duty round, the noon numbers or the daily soundings — 22 of those worked out from other readings rather than read directly. The rest, including the cylinder temperature bands, turbochargers and bearing temperatures, are not collected by the rounds and come out blank.
It is a view of your own data, not an official record and not offered as one. Check it against your entries before you lean on it.
A Raspberry Pi drives a TV showing a page the hub renders: worklists, alerts, round status, metrics, a crew notice board, a clock on ship's time rather than the PC's, and trend charts drawn from recorded readings with the alarm setpoint off the round template. The layout is arranged by an admin. You can put a question to LOOP from the display itself.
The Pi renders nothing on its own — it is a browser pointed at the hub, so the board is live only while the hub is up. Questions asked at the display do not reach the manual library; that path is the tablet.
LOOP is included in Pro ($999/mo) and Enterprise plans — or start with a 60-day pilot for a flat $2,500 with full access and no long-term commitment.