Case studies

What it has actually done

Real operating data from working terminals, with the counts stated plainly and the limits stated just as plainly. No client is named, and nothing here is a projection.

European operatorRead →
Eleven years of records, one governed timeline

27,338 maintenance work orders, 236 HSSE events and 75 commercial contracts moved out of four disconnected systems into one reviewable operational record, plus a daily automated tank feed. What the joined record answered that the separate systems could not.

Why there is only one

Because there has been one, and publishing a second would mean inventing it.

Most vendor case-study pages in this industry carry four or five logos by the time the company is a year old. Some of those engagements are real. Many are a pilot conversation, a trial licence, or a name obtained with permission and stretched. We would rather show a single deployment with real counts against it and tell you exactly where it ended.

The second one will appear here when a second operator has run the layer against their own data and agreed to let the shape of it be described. Not before.

What we will not do with your operation

No named logos

Your name does not appear on this page, in a deck, or in a conversation with another operator, unless you have asked for it in writing.

No screenshots

Your screens describe how your business runs. The platform is shown to prospects on representative data only.

No operational numbers

Volumes, incident rates and counterparty structure stay yours. Any counts published are agreed first, in writing, or they are not published.

This is not a courtesy, it is the arrangement. In an industry that runs on relationships and discretion, a vendor who publicises one client's operation has told every other client what to expect.

Test it on your own records

Thirty days, historical exports only, nothing touching production. You keep the findings whether or not you go further.