An RTU in a pumping station or a substation is easy to look after when there is one of them. The difficulty arrives at the fortieth, spread across three counties, on four firmware versions, with nobody quite sure which settings were changed during last winter’s call-out. Odin’s Eye is Brodersen’s answer to that: one secure interface for monitoring, configuring and maintaining every RTU you have deployed. This guide covers what centralized RTU management actually involves, what Odin’s Eye does in each area, and how to work out which plan fits the fleet you are running.
Why fleets outgrow device-by-device management
Most RTU estates are not planned. They accumulate. A water utility adds a lift station, then another, then inherits a dozen more through a boundary change. Each one was commissioned by whoever was available, with the firmware that was current that month and the settings that suited that site.
Managed individually, that is workable for a while. The costs show up later, as questions nobody can answer quickly:
- Which devices are running which firmware version, right now?
- Did the configuration change at site 14, and who changed it?
- Is that alarm normal for this time of year, or is something about to fail?
- How long will it take to push a firmware update to everything?
Every one of those is answerable with a laptop, a drive and a day. The problem is that you need the answer before the drive, and you need it for the whole fleet rather than one device at a time.
The practical test. If a firmware issue were announced for your RTUs this afternoon, how many hours would pass before you knew which of your devices were affected? Centralized management turns that from a survey into a query.
What centralized RTU management means
The phrase covers four separate jobs that happen to be easier together than apart.
- Visibility. Knowing the current state of every device without visiting it, continuously rather than at the point you go looking.
- Change. Pushing firmware and configuration remotely, one device at a time when a site needs something specific, or across a group when a change applies to many.
- Warning. Being told that something has gone outside its limits while there is still time to act, rather than discovering it from the process going down.
- Control. Knowing who is allowed to do what, and having a record of it. In regulated environments this is not optional, and retrofitting it later is considerably harder than having it from the start.
What Odin’s Eye actually does
Real-time fleet monitoring
Continuous monitoring of every deployed RTU, including online and offline status, I/O status and power consumption, with a centralised dashboard for fleet-wide visibility. You can upload external HMI packages or build dashboards using the integrated web HMI designer.
Firmware management, per device or by group
Firmware can be upgraded on an individual device when one site needs a targeted fix, or across a whole group when a change applies more widely. The second is the one that changes how a maintenance window looks, because the work stops scaling with the number of devices.
Configuration templates
Settings can be modified on an individual RTU where a site genuinely differs. Where it does not, configuration templates apply the same settings across many devices at once. The value is less about speed than about standardisation: fewer one-off configurations means fewer sites whose behaviour nobody can predict.
Grouping and map view
Devices can be organised into groups and subgroups, which is what makes bulk actions safe and targeted. A map-based view through GeoLocation shows where the estate actually is, which matters when you are deciding what one engineer can reach in a day.
Alarms and event history
Odin’s Eye raises alarms and can notify by email as well as on the dashboard. Events can be watched in real time or exported as historical event logs, which is what turns a vague sense that a site misbehaves into evidence you can act on.
Security and access control
Access is through a browser over HTTPS, served via a reverse proxy. User, role and permission management limits what each operator can change, and role-based access is available on every plan including the free one. LDAP authentication, which lets the platform sit inside your existing directory rather than beside it as another credential set, is available from the Gold plan.
What you need to run it
This is worth being clear about before you plan a rollout, because it is not a sign-up-and-go cloud service. Odin’s Eye is installed on your own server: Windows Server 2022 or later, set up with an executable installer that configures the application services, a PostgreSQL database and the reverse proxy, with a licence key activated during setup.
On hardware, Odin’s Eye currently supports RTU32 series devices, specifically MP32A Rev. A to E modules of the RTU32M series. Those devices need to be running a recent enough image build: 3101 or later for Rev. A, B and C, and 3105 or later for Rev. D and E. It is worth checking your fleet against that before you plan anything, because an older image build will need updating first.
Choosing a plan
Plans are set by fleet size first, then by which control features you need. The free tier is a real tier rather than a trial: it does not expire.
Two things in that table are worth noticing, because they are easy to get wrong.
Role-based access is available from the free tier. You do not have to pay to separate what an operator may do from what an administrator may do. That is unusual, and it means even a three-device evaluation can be set up the way you would actually run it.
LDAP is the one that is held back. It arrives at Gold, not Silver. So if connecting the platform to your existing directory is a requirement, rather than a nice-to-have, that single feature decides your plan more than the device count does. It is worth checking that before you size on device numbers alone.
Where Odin’s Eye sits in a Brodersen system
Odin’s Eye manages RTUs rather than replacing what they do. A station keeps running its own control logic locally, whether that is a substation or a pumping station running a dedicated application such as NJORD-VAR. Odin’s Eye is the layer above: monitoring, diagnostics, configuration and management across many installations at once.
That separation matters in practice. Local control continues whether or not the management layer is reachable, which is the behaviour you want from infrastructure that has to keep running when the network does not.
Getting started
The sensible first step is small. Run three devices on the free plan, ideally three you already find awkward to reach, and live with it for a month. What you are testing is not the feature list. It is whether the questions at the top of this article become quicker to answer.
Visibility tells you something is wrong. Event history and access control tell you what changed and who changed it. Operating a fleet needs both, and neither gets easier to add once the estate is large.
Build your RTU in the online configurator → See Odin’s Eye →