
How 42Hz gets from a reading to a finished job
42Hz reads your equipment, works out each unit’s normal, explains faults in plain English and plans the fix. It does not write to your equipment.

Technology partners

It finds the fault, gets it fixed and shows what it cost
Most platforms stop at the alarm. The cost comes after: who goes, with which part, and what the month ends up costing.
What it connects to, and what it guarantees.
Reads what exists
Works beside SCADA
Silence detection
Read-only always
Every site on one screen
The full record
SLA evidence
No new sensors
Built-in historian
Catch the fault while it is still a small job.
42Hz builds a baseline from each asset's own history. Two transformers under the same load behave differently, and both are fine. When one changes, that is the signal.

Most of the cost is in the response.
42Hz ranks the cases, phones the on-call until someone owns it, and sends the truck with the right part.

Every case has a price.
Penalty clocks run on screen, so month-end holds no surprises. Underperformance shows early enough to fix. Asset value comes from operating history, and well-kept equipment lasts longer.

For the technician
Plain English at the cabinet door.
A technician at a cabinet should not be decoding registers. 42Hz answers in plain English, on a desktop or a phone.
- Troubleshooting
- “What was the oil temperature trend on Transformer 1 during the last three load peaks?”
- Triage
- “Which three assets in the Southern District show setpoint drift this week?”
- Verification
- “Show me every breaker cycle count above 85 percent of rated life.”
From a single-line drawing to monitored sites in 90 days.
Your first stations are online in weeks, on equipment that is already there.

- 01
Tell us what you run
A drawing, a points list, or a photo of the panel door. We come back with what we can read at your sites, point by point, before anything is signed.
- 02
First sites come online
We use your network where you grant access, and a pre-configured cellular kit where you do not.
- 03
The baseline fills in
With a historian we start from your history. Without one, 42Hz keeps its own from day one, and useful signal appears in weeks.

It reads. It never writes.
Projects stall when software wants inbound access or touches control loops. 42Hz does neither. It does not write to your equipment and has no way to.
All traffic is encrypted and outbound, through a connection your security team owns. No listening ports. No remote control. No setting that enables writes.
For utilities, deployment sits within your existing CIP program.
“All connections with the OT environment should be initiated as outbound connections from within the OT environment.”
- Outbound-only, encrypted
- No inbound control channel
- No open listening ports
- No write path, at any permission level
