HOLOIN
Book a demo
Menu

live · Remote sites

For the operator who learns a site lost power when it goes silent.

Unmanned, not unknown.

Every generator, battery, fuel tank, door and sensor at every site, in one twin, on your own servers. The site tells you what the fuel is doing, and when its door opens with no work booked and no one checked in.

See it on a site like yours — 15 min →What you need
Varnholt Ridge Tower · VRT-044 · its twinlive
Grid
downsince 20:12:32
Battery autonomy
17min · from 2 outages
Generator
running20:12:35

RuleGrid fails and the generator hasn’t started: critical, with the controller’s own reason, and a work order. The line and the minutes are yours.

  • 20:12:32Grid down · reported by the site’s controller
  • 20:12:33Alarm: grid down, generator not started · about 17 min of battery left
  • 20:12:35Generator start completed · counted only when the controller reported it running
  • 20:12:35Alarm cleared · by the controller’s report, not by a person
What the twin holds: power · fuel · environment · access · alarms · jobs · historydemo run · the company’s own time
1The problems

What a site operator actually hears.

Four sentences from the people who run unmanned sites. Each one is answered below, with the screen that answers it.

the operator, at three in the morning
“We learn a site lost power when it goes silent.”
Answered by the grid alarm and the generator’s start ↓
the fuel manager, at month end
“Diesel goes missing and nobody can say where.”
Answered by the drop against the site’s own baseline ↓
the security lead
“The door opened and we don’t know why.”
Answered by the door against the work orders ↓
the network team, during an outage
“One site drops and the screen fills with alarms.”
Answered by one alarm, on the router ↓
2How HOLOIN answers each

Four problems, four screens.

Each answer below is something the product did in the demo run, shown on the screen where it did it.

Problem 1 · “We learn a site lost power when it goes silent.”

The grid fails. The site says whether the generator started.

If the generator hasn’t started, or the controller reports a failed start, a critical alarm with the controller’s own reason, and a work order. A start counts only when the controller reports the generator running; the battery’s minutes left come from the site’s own past outages.

Outcome A power cut reaches you as a work order, before the site goes silent.
Sites · alarms · grid
start failedCorvane Hill Tower“The generator didn't start: Fail to start.”20:09:20
work order#22opened by the rule, on the technician’s phoneopened
runningVarnholt Ridge Towergenerator start counted on the controller’s report20:12:35

From the demo run. At Corvane Hill Tower the controller reported a failed start: a critical alarm in its own words, and work order #22. At Varnholt Ridge Tower the generator was counted as started only when the controller reported it running.

Problem 2 · “Diesel goes missing.”

A drop the site can’t explain is an alarm.

A drop beyond the site’s own baseline for its state, with no run hours to explain it, raises an alarm — with the time and the site.

Outcome Missing diesel is an alarm with a time and a site.
Fuel · drop alarm
fuel drop118 L in 2 minbeyond the site’s own baseline · no run hours to explain it20:11:20

From the demo run. 118 litres in 2 minutes, against the site’s own baseline: an alarm at 20:11:20.

Problem 3 · “The door opened and we don’t know why.”

A door opened without work is an alarm.

No work order open, no technician marked on site: an alarm with the time and the site on the map. “I’m on site” from the phone is the exception.

Outcome Every opening is either work you know about, or an alarm.
Access · door
doorDoor opened at VRT-044no work order open · no one marked on site20:09:15

From the demo run. The door at VRT-044 opened at 20:09:15 with no work order open and no one marked on site.

Problem 4 · “The screen fills with alarms.”

One alarm, on the link that broke.

The router’s or gateway’s rhythm breaks: one alarm for the site, naming the probable cause, with when it was last heard. The twin records that path, so when the readings stop it can say which link broke instead of raising an alarm for every device.

Outcome One alarm names the router; the devices behind it wait under it.
Alarms · one list
root causeCellular router · OstrelaOstrela Pumping Station · silent20:09:34
held11 devices behind itlisted on the router’s alarm, none pagedheld

From the demo run. Ostrela Pumping Station went silent at 20:09:34. The twin named the router as the probable cause and held the eleven device alarms under it. The alarm on the router lists the devices held behind it.

And the rest of the day’s work

Generator overlapPast the changeover allowance, the minutes count. The month ranks sites by overlap: the diesel nobody sees.
Fuel dueA recommendation on the Fuel page, never an order. The route is yours.
The month’s numbersGrid availability, generator hours, overlap minutes, fuel used, fuel per run hour, uptime: computed from the twin, not typed into a spreadsheet.
Generator controlWhere the controller allows it, a rule a person wrote can start or stop the generator, and the command completes only on the controller’s own evidence that it did. A stop is never refused by a HOLOIN rule.
Every site on one mapColoured by status, sorted by severity; filters for silent, on generator, needs fuel. Map tiles come from a server inside your own network, or the sites are drawn on a plain map with no streets; nothing is fetched from the internet to draw it.
DirectionsDirections on the site page, and Navigate on the technician’s work order, open the phone’s maps app.
DeliveriesEntered by hand, or arriving by the HTTP source.
Ready-made definitionsAn air sensor verified with a simulated device; a fuel level sensor and a power system monitor built from the vendor’s published register map.
3The twin of a site

The site is the record. Everything attaches to it.

A site is a generator controller, a battery system, a fuel sensor, a door contact and a shelter sensor, read by a Field Agent at the site over Modbus and by LoRaWAN sensors through the bundled radio server.

Power
Grid, generator, battery autonomy

From the controller, as it reports them.

Fuel
Level and baseline

Level against the site’s own baseline, deliveries and run hours.

Environment
The shelter

Shelter temperature, humidity, flood, smoke.

Access
The door

The door, against open work orders and who is on site.

Lines
Alarms and jobs

Rules you can read; work orders on the technician’s phone.

Then
History

The month’s numbers per site, exportable.

4What the twin changes in the day’s work

Fewer night calls. Fewer surprises at month end.

Stated as changes, not as numbers: your numbers are yours to measure, and Why it pays gives you the arithmetic.

Before
  • A site that lost power is found when it goes silent.
  • A generator “started” because someone sent the command.
  • Missing diesel shows up in the month’s invoice.
  • A door opening is a line in a log nobody reads.
  • One router drops and every device behind it alarms.
  • The month’s numbers are typed into a spreadsheet.
With the twin
  • Grid down with no generator start is a critical alarm, in the controller’s words.
  • A start counts when the controller reports it running.
  • A drop the site can’t explain is an alarm the day it happens.
  • An opening without a work order is an alarm.
  • One alarm on the router; the rest held under it.
  • Computed per site, per day, from the twin.
5OT and IT

OT and IT, in one twin.

The controller is OT. The router that carries its readings is IT. The site’s twin holds both, and the path between them.

A site is a generator controller, a battery system, a fuel sensor, a door contact and a shelter sensor, read by a Field Agent at the site over Modbus and by LoRaWAN sensors through the bundled radio server. All of it reaches HOLOIN through one cellular router. The twin records that path, so when the readings stop it can say which link broke instead of raising an alarm for every device.

OT · what the site is made of

Read in their own protocols, never written to unless a person switched that on.

  • Generator controller, battery system, fuel sensor over Modbus
  • Shelter temperature, humidity, flood, smoke over LoRaWAN
  • Door contact; deliveries entered or pushed

IT · what keeps it reporting

The Field Agent connects outbound only; the router and the gateway are devices in the twin too.

  • The cellular router, with the devices behind it recorded
  • The LoRaWAN gateway: heard, silent, never seen
  • The path from any reading back to the server, hop by hop
Ostrela Pumping Station · OPS-019 · silent
Cellular router · Ostrela · silentroot cause
11 devices behind it
Generator controllerheld
Battery systemheld
Fuel sensorheld
… and 8 more, each held under the router
Upstream cause: the cellular router. 11 devices silent behind it; one alarm, at 20:09:34. Without the path, the same minute would have raised eleven.

From the demo run. Ostrela Pumping Station went silent at 20:09:34. The twin named the router as the probable cause and held the eleven device alarms under it. The alarm on the router lists the devices held behind it.

6How it’s deployed

Buy the devices. Everything else comes inside.

One install bundle carries the servers a site needs. A Field Agent box on the controllers’ network connects out to your server; the site appears.

You supply
  • One Linux server with Dockeryours, or one we run for you in the country you choose
  • The devicesany model listed, or your own with a published map
  • The ports your IT opensthe install guide lists them
Inside the install
  • The Field Agent at the sitereads the controllers over Modbus, and connects outbound only
  • The LoRaWAN network serverfor the shelter sensors, through your own gateway
  • The database, the backups, the web entryone compose file, one address
Kept running by the install itself
  • One scriptready in 2 min 42 s on the acceptance box (run 39194860273)
  • Nightly backup, monthly restore drilla failed one is an alarm in the product
  • Upgrade in placesame volumes, registrations and readings intact, proven on every release
  • No telemetrythe bundled servers’ phone-home is off; CI fails if any container reaches out

The servers this kind of asset uses, each shown only when its acceptance run passed; statuses from the facts file.

7Without HOLOIN

Five systems, or one.

The same sites, run the usual way. No names: the categories are what matters.

Bought separately
  • A controller portal per make — one login each, alarms in each one’s words.
  • A fuel-monitoring service — a level graph, and the arithmetic left to you.
  • An access-control system — door events in their own log.
  • A network monitor for the routers — a page for every silent device.
  • A spreadsheet for the month — kept by whoever remembers.
Five contracts, five logins, no path from one to the other. When a site goes quiet, nobody can say why.
In HOLOIN
  • The controllers read in their own protocols — one board, the controller’s reason kept.
  • Fuel against the site’s baseline — a drop the site can’t explain is an alarm.
  • The door against the work orders — an opening without work is an alarm.
  • The router is a device in the twin — one alarm names the link.
  • The month’s numbers — computed per site, per day.
One installation, one database you own, one price counted in devices.
8What it costs

Counted in devices. Never in people.

One licence per installation, per year, by device tier. A controller or a sensor is a device; an operator’s login and a technician’s phone are not. Add operators and technicians without a change to the bill.

The whole grid, every tier and every pack, is on Pricing — published, with what counts as a device and what is included.

US$4,000a year
Eight sites, about a dozen devices each: the controller, battery system, fuel sensor, door, shelter sensors and the router — the 100-device tier, from the published grid.
  • The platformUS$2,500
  • The Remote sites packUS$1,500
  • Operators and techniciansincluded
  • The LoRaWAN network server, the phone appincluded
9Secure, and kept running

Your server. Your sites’ data. Nothing phones home.

Not a policy page: each of these is a property of the software you can check on your own server.

One installation, yours

Installed from a bundle that carries everything it needs. Never a shared cloud: one installation per customer, or one your integrator runs for you, each client a company of its own.

PostgreSQL you own

Every reading, alarm and record in a database you administer. A nightly backup you can restore anywhere, drilled monthly.

Read-only unless a person switched it on

The site is read, never written to, until an administrator turns on control for that site with a written reason; every command is logged.

Nothing phones home

No telemetry in the product, none in the bundled servers. Proved with the network sealed on every release.

Your rules stay yours

Lines, rules, schedules and what the twin learned are text and arithmetic in your database; they leave with you.

An audit log that can’t be edited

Every change, by whom, from where — append-only in the database itself, for seven years, even for the database’s own administrator.

10The four questions

What you actually want to know.

Do I have to install anything?

No. We run HOLOIN for you on a dedicated server in the country you choose, never shared with another company, and you can take it with you. If you have your own servers, install it there instead; same product.

What do I need?

A Field Agent box at each site on the controllers’ network (it only connects outbound), a cellular router or any path back to your server, and the ready-made definitions above. The install guide lists the ports.

What does it cost?

Per installation, per year, by device tier: from US$4,000 a year for the platform and Remote sites, up to 100 devices. The whole grid is on Pricing. No per-seat fees; every operator and technician is included.

Who do I call?

Hours, channel and response time: on request. Every installation can produce a support bundle on demand, a readable archive with no personal data or secrets, which your IT team can check before it goes to us.

11The way in

See it running on your sites.

I run the sites

Fifteen minutes on three unmanned sites: the grid fails, the fuel drops, the door opens, a site goes silent. Your controllers, if you bring their register maps.

See it on a site like yours — 15 min →Get demo access →

I install systems for operators

One installation per client. The Field Agent at the site, the radio server inside, the ports in the install guide.

Start a partner conversation →