Operations Answer the question that orders a facility's operation — how much water comes in, how much goes out and how much stays — and see the pipelines that carry tailings and water: where they run, what equipment they have and what their instruments say.

The data layer is designed for it: the interface consumes a contract — sensor readings, summary, water balance, topology — and does not know where the data comes from. Behind it are swappable adapters chosen by configuration, and three implementations exist. Plugging in a client's historian does not require rewriting a single screen.

But each concrete connection is an integration project, not a checkbox. We do not promise it as immediate. And there is no write path to the control system: the platform reads and presents, it does not act on pumps or valves. That is also its most valuable safety property.

The historian has the series. What it does not have is the band, the task or the document that justifies the band; that is what the platform adds.

No. The screen draws each pipeline's real route — it comes from the survey — orders its equipment and shows its instruments' readings coloured by threshold band. It does not model flow, compute head losses, detect leaks or blockages, or control pumps and valves.

The process schematic is in order, not to scale, and the screen says so; what is real is the length of each reach, which is labelled. It is not an engineering drawing. What it adds is something else: a twenty-kilometre line that reads at a glance, with the out-of-band instrument marked at its chainage rather than in a list.

Twin Mining TMS's data layer uses interchangeable adapters per source: the screen consumes a contract and the source — geotechnical and geochemical instrumentation, sensors, corporate systems — is swapped by configuration without touching the interface. There is also an API for integration; there is no write path towards control systems.

Each integration is a piece of work, not a checkbox: source, frequency and units have to be agreed with the operator. We say so up front so nobody arrives at the first meeting expecting an automatic connection.

Integrations are implemented incrementally, source by source, without stopping what already works.

TARP stands for Trigger Action Response Plan. It is the set of threshold bands for an instrument — green, amber, red — together with the response defined for each: which actions are mandatory, who must approve them, and who must be notified.

Explained to someone outside the sector: it is a sensor's traffic light, plus what has to happen when it changes colour.

In Twin Mining TMS the threshold, the response, and the document backing it live on the same screen, and changing a threshold goes through a formal management-of-change record. That last link is what separates a TMS from a monitoring system.