Device Configurator

It Works Offline, and That Matters More Than It Sounds

Most fleet software now assumes a connection. Device Configurator doesn’t.

It runs in a workplace with no internet connection, so the software is available whenever it’s needed, rather than whenever the network allows. For a remote site, an underground operation, or a plant where the gas detector store is nowhere near a reliable connection, that’s the difference between usable and not.

It also keeps the data local, which matters where an organisation has a policy about where instrument and worker data is allowed to sit.

One Application for BW and RAE

Honeywell’s portable range came from two histories, the BW instruments and the RAE Systems ones, and for years they needed different software. Fleet Manager II covered one, and ProRAE Studio II the other.

Device Configurator covers both, and supports data migration from either. For anyone running a mixed Honeywell fleet assembled over time, that brings two sets of records and two pieces of software into one.

Templates Are the Point

Configuring one instrument is straightforward. Configuring a hundred identically isn’t, and inconsistent alarm setpoints across a fleet are a real problem, not just an untidy one.

Templates are created, edited, stored and uploaded, so a configuration is defined once and applied across the instruments it should cover. That keeps alarm thresholds, settings and policy consistent, and turns a change across the fleet into a single action rather than a hundred.

What It Actually Does

The software downloads data logs and configuration settings from supported instruments, changes and uploads new configuration settings back to them, updates firmware, downloads reports, and creates, edits, stores and uploads templates.

Device History gives a comprehensive view of the data across an instrument’s life, including calibration and bump test records, which is what an audit asks for.

Security and Access

Two things here matter in an organisation, rather than on a single PC.

Data is encrypted, which minimises privacy concerns. Access is role based, with managed access control, so who can see and change what is set deliberately, rather than by whoever happens to have the software installed.

Investigating an Incident

Event reporting is centralised, which is the difference between knowing an instrument alarmed and understanding what happened.

Pulling alarm events across the fleet into one view lets a pattern be seen, where individual instrument logs show only isolated incidents. In an investigation, that’s usually the question being asked.

Connecting to Instruments

Instruments connect through a docking station or directly. IntelliDoX connects over the network, MicroDock II connects by USB, and AutoRAE 2 is also supported. Instruments can also connect directly by USB or Bluetooth.

Administrator privileges on the PC are needed to install it. They aren’t needed to run it afterwards.