If Your Old DAS Alarm Has Reached Its Limit, What Should Come Next?

There’s still a DAS keypad on the wall, or a NetworX-lineage panel doing its job somewhere in a cupboard. It might still arm and disarm without complaint. It might already be showing its age — a fault here, a limited option there. Either way, the real question isn’t how old the name “DAS” sounds. It’s whether this particular generation is still worth investing in, and what actually comes next if it isn’t.

Has a DAS-Era Alarm Really Reached the End of the Road?

“End of the road” isn’t a status any manufacturer has declared for every DAS system out there — it’s the question this article actually answers, not a conclusion it starts from. Age by itself doesn’t prove a working panel needs to go.

What’s actually documented is narrower and more useful: Aritech’s current Reliance XR series is officially described as the natural successor to NetworX. That doesn’t by itself tell you whether a particular old DAS installation should be replaced. Its condition, configuration and what the property now requires still matter — and those are the questions worth answering before anything else.

What Does the Current Reliance XR Path Actually Offer?

For installations where the existing equipment is confirmed as part of the compatible NetworX architecture, Aritech documents a current migration path through Reliance XR. The manufacturer describes XR as the natural successor to NetworX and supports both new installations and upgrades from existing NetworX systems.

Age Alone Doesn’t Settle the Question

A functioning old panel isn’t automatically a reason to keep investing in it indefinitely — but its age alone isn’t a reason to replace it either. What actually matters is the specific fault (if there is one), the condition of the existing installation, whether the current configuration still suits the property, and whether a practical migration path exists. Those are the questions worth answering before deciding anything, not the number of years the panel has been on the wall.

If Replacement Is Justified, What Are You Actually Choosing Between?

Once an assessment shows that continuing with the existing installation no longer makes sense, the decision isn’t a single obvious choice. For this article, two materially different approaches are worth comparing, because they lead to genuinely different outcomes for the installation — not because they’re the only two replacement options that exist anywhere.

Path One: Move Compatible Equipment to Aritech Reliance XR

Where the existing installation is confirmed as compatible NetworX equipment, this isn’t just “another new alarm” — it’s the manufacturer’s own documented upgrade path. Aritech’s current Reliance XR boards use the same form factor as the original NetworX boards and include a dual-bus design (NetworX bus plus RS-485), which the manufacturer states makes them backward compatible with almost all NetworX auxiliary equipment, including keypads and zone expanders.

That’s a meaningful, documented migration path — but “almost all” is doing real work in that sentence. It means compatible existing NetworX keypads and auxiliary modules may be retained, not that every installed component automatically will be. The exact configuration on the wall still needs to be checked against current Reliance XR compatibility before assuming anything carries over.

Path Two: Redesign Around Ajax

This is a different kind of decision — not an upgrade within the same lineage, but moving the property onto a wireless-first platform and rebuilding the alarm architecture around what it needs today. Unlike the Reliance XR path, this isn’t about continuity with the existing control system at all: the old panel itself isn’t part of the new architecture. It’s replaced, not migrated.

That doesn’t mean everything physically connected to the old panel loses its value automatically. There’s a real distinction between the control panel and the individual wired detectors that were connected to it. Ajax’s MultiTransmitter is an official integration module for connecting compatible third-party wired detectors and devices to an Ajax system, with 18 wired zones supporting common contact types (NC, NO, EOL and others). That’s a genuine path for retaining suitable existing hardware — door and window contacts, certain motion detectors, and similar wired devices, provided their wiring and contact type are compatible.

What determines whether a specific device is worth keeping isn’t simply “it’s wired” — it’s the device’s type, its condition, and whether its wiring and contact configuration match what MultiTransmitter supports. That’s evaluated device by device, not assumed for the installation as a whole, and it never extends to the old control panel itself, which this path doesn’t retain in any form.

What Can Stay and What Usually Needs Reconsidering?

Which Direction Fits the Property?

Neither path is a default answer. The right direction depends on:

In practice, these tend to point in different directions depending on what’s actually valuable in the existing installation. If the existing equipment is confirmed compatible NetworX architecture, with keypads and modules still in good condition, the Reliance XR migration path is worth closer consideration — it preserves more of what’s already there. If the goal is more of a broader redesign, and what’s actually worth keeping is mainly a handful of individual wired detectors rather than the control architecture itself, a platform change is the more relevant conversation, with those specific devices assessed for MultiTransmitter compatibility rather than the whole system evaluated as one unit.

Neither conclusion follows from the DAS name alone — both depend on what’s actually installed and what the property needs next.

FAQ