Application Scenarios
The job always arrives at the worst possible moment. A 3500/42M in a compressor skid has been running for eleven years on a 0–5 mils pp radial scale, and the asset team has just swapped the probes for a 200 mV/mil XL pair during a probe-fail incident. The Danger LED is lit, the historian is flat-lining, and the operations manager is standing behind the technician. Opening the 3500/01-01 on a rugged laptop, the engineer drags the new transducer type onto the slot, re-enters the sensitivity, re-runs the gap calculation, downloads, and watches the CONFIG OK LED go dark. Fifteen minutes, no trip, no new rack file guessed from memory.
The second scene is quieter and more common. Turnaround is six weeks away, the DCS is being migrated, and nobody can find the original rack build documentation. The 3500/01-01 is used offline: a virtual rack is built slot by slot from the latest physical survey, point names are standardised, Alert and Danger setpoints are entered from the mechanical protection philosophy, and the file is saved as a controlled revision before anyone connects a cable. When commissioning week arrives, the download is a verification step rather than a field improvisation — and the paperless audit trail is already in the document system.
Parameter
| Main Parameter | Value / Description |
|---|---|
| Product Model | 3500/01-01 — Rack Configuration Software and Configuration Manual, Bently Nevada 3500 ordering family |
| Manufacturer | Bently Nevada (a Baker Hughes business); legacy GE/Bently Nevada media and documentation common in the installed base |
| Product Category | Engineering configuration software (offline design + online download/verify tool), supplied on removable media |
| System Target | All 3500 Series racks and module generations, including M-Series monitors, 3500/20 RIM and 3500/22M TDI architectures |
| Build Method | Graphical slot-map workspace. Left-click an empty slot to place a monitor; right-click an occupied slot for its context menu, setpoints and point-name editor |
| Configuration Objects | Channel enable/disable, transducer family and sensitivity, full-scale range and engineering units, gap and clamp values, Timed OK / Channel Defeat, Alert and Danger thresholds with independent delays, relay voting logic, point names, rack type and slot addressing |
| Output / Persistence | Rack configuration file (the compiled .cmd/rack file written to the RIM or TDI). Save, reload, compare and re-download — this is the recoverable artefact that replaces the handwritten commissioning sheet |
| Connection Paths | Front-panel RS232 on the RIM/TDI; USB-to-serial (USB-B on 3500/22M, adapter on earlier hardware); rear serial for permanent workstation or modem tie-in; Ethernet/TCP-IP for network-resident racks. Cables are ordered separately — the media kit is not a cable |
| Security Model | Two-tier software password protection plus the keylock switch on the RIM/TDI front panel. Key in RUN = no edits; PROGRAM = writes allowed. The intent is deliberate: you cannot “accidentally” move a Danger setpoint during a log review |
| Verification & Diagnostics | Download verification against the physical backplane, CONFIG OK LED semantics, module mismatch detection, alarm/event and system-event export, rack-info export for remote support sessions — all without disturbing live protection |
| Firmware Path | Module firmware is staged and updated through the same tool. Version matching between software, RIM/TDI firmware and module revision is mandatory before a swap, not a suggestion |
| Supported OS (published baseline) | English-language Microsoft Windows 7 or Windows Server 2012 and later; the tool pre-dates Windows 11 and has historically run acceptably under compatibility shims, but test on a non-production seat first |
| Published Hardware Floor | Intel Pentium-class or better; 800 × 600 SVGA minimum; 128 MB RAM recommended; ~35 MB free disk; CD-ROM for media extraction; RS232 port, USB-to-serial adapter, modem or network path to the rack |
| Language | English UI in the baseline release. The configuration manual is the primary reference; keep a locally archived PDF copy beside the media |
| Media / Package | CD-ROM or equivalent installation media plus printed/bound Configuration Manual. Package shipping dimensions commonly cited around 24.1 × 10.3 × 2.4 cm, mass ~0.2 kg — media, not a rack-mounted module |
| Support Vehicle | 3500/18-A-XX software support plan, sold separately and tiered by duration and single- versus multi-software coverage (01 = 1-year single, 02 = 1-year multi, through 09/10 = 5-year). A support plan, not the media, is what buys version updates |
| Recommended Accessory | 100M2833 — 10-foot USB A-to-B cable, the shortest and most reliable local link to a 3500/22M front-panel port |
Technical Principles and Innovative Values
Innovation Point 1 — Configuration is a file, not a panel of trim pots. The 3500’s architectural move was to take everything that used to be a jumper, dip-switch and scaling resistor and turn it into a downloadable data set. The 3500/01-01 is the editor for that data set. Because the rack file is portable, a four-rack train can be built once, replicated, checksum-compared and restored in minutes. More importantly, a destroyed RIM no longer means a re-commissioning exercise — it means copy the file, download, verify.
Innovation Point 2 — The safety path was deliberately left outside the software’s reach. This is the feature nobody advertises loudly enough. The RIM/TDI is explicitly not part of the critical monitoring path: a crashed PC, a pulled USB cable or a corrupted download does not silence a 3500/42M channel or release a Danger relay. The 3500/01-01 can go offline mid-job and the turbine protection keeps running exactly as it was. That separation is why the tool is trusted in SIL-relevant environments — it changes configuration, not physics.
Innovation Point 3 — Compile-time sanity checks beat field surprises. The slot-map editor refuses what the backplane would refuse: a module in the wrong slot, a channel count that exceeds the relay, a transducer sensitivity that does not match the monitor type, a gap limit set outside the probe’s linear range. Catching those on a laptop at a desk — rather than at 03:00 with a permit and a two-hour window — is the difference between a commissioning milestone and a punch-list item.
Innovation Point 4 — Online readback without online risk. Later software builds (V3.90 and beyond) added the rack-info button: export the Alarm Event List, System Event List, Asset Information and the live Rack File while connected, with no effect on rack operation. Send the bundle to a remote specialist instead of flying one in. For a platform where the nearest Bently-literate engineer may be three time zones away, that is a genuine availability lever.
Innovation Point 5 — Version discipline disguised as a menu item. Each release quietly adds hardware support and closes specific defects — the 22M with front-panel USB, the 3500/53M overspeed monitor, the 3500/32M relay module, and fixes for exactly the sort of UI crash that used to happen when a relay with more than three channels was verified. Running a current-ish 3500/01-01 build against an old module is usually fine; running an old build against a new module is the failure mode that leaves you downloading the installer from a forum at 2 a.m. Keep the media version and the support plan aligned.
