Solutions
Asset monitoring
Hundreds of pieces of equipment watched at once, each with its health in a single number and its full history.
What it solves
A plant has hundreds of critical machines and one thermographic round each quarter. Between one round and the next nobody knows anything, and failure does not wait for the calendar. By the time it shows up in the October photograph it has been warning since August, and the discussion is no longer how to avoid it but how many shifts it cost.
What gets measured here
Every signal, with the standard behind it
0–100
Four weighted signals · seven bands
Asset health
The index weighs absolute temperature, ΔT over the reference, trend and irregularity into a number from 0 to 100 across seven bands. Every default threshold cites the standard it comes from, and can be opened from the screen itself.
IEC 60034 · NETA MTS 100.18 · ISO 18434-1> 35 K
Over the asset's own reference · 10–35 alert · 1–10 preventive
Thermal anomaly class
The ΔT over the baseline classifies the finding and sets its urgency. Above 35 °C over the reference it stops being monitoring and becomes immediate intervention.
NETA MTS 100.18P → F
From detectable to failure, measured in days
P-F interval
The time between the failure becoming detectable and the failure occurring. Remaining useful life and the window to act without stopping the line come from there, not from a fixed calendar date.
ISO 13381-1 · ISO 173593 levels
Asset · system · sub-asset
Failure taxonomy
The fault is recorded at the level where it actually happened, which is the only way the history is any use for comparing equipment across plants.
ISO 1422419.6 %
Of volume at a quarter of the height, in a horizontal cylinder
Level and volume in vessels
The thermal line marks the surface of the product; the vessel's strapping table turns that height into litres. Percentage of height is not percentage of volume: at a quarter of its height, a horizontal tank holds 19.6 % of its capacity, not 25 %.
API MPMS Ch. 3
The full catalogue is 311 standards across fourteen domains, and it lives inside the platform — next to the field where the number goes — not in an appendix to the manual.
What comes out of it
The report carries two logos, not ours
The end customer's at the top and, where an integrator did the installation, theirs beside it. SEPTEM's name has no business appearing on anyone else's deliverable. Every report carries its reference number and the measurement behind it.
The finding becomes a work order
Maintenance management lives inside, not in another program: the order is born from the asset that needs it, carries its steps, its spare part and its cost, and its SLA runs by severity. On closing, the sensor confirms the temperature came down — or the order does not close.
The alert arrives where the person will see it
Email, WhatsApp, SMS, voice, Slack or a webhook into the system they already use. With escalation: if nobody responds within the deadline, it goes up. An alert that lands on a dashboard nobody watches is not an alert.
What it uses
A hot spot is not a temperature
A motor at 68 °C in January and at 68 °C in July do not mean the same thing. What decides is the ΔT against its reference —the twin machine beside it, or itself a month ago— and that is why the index weighs four signals instead of one. The worst component governs: a single point below 50 pulls the whole down, because a transformer does not fail on average.