Johnson Controls Metasys is one of the most widely installed building automation systems in commercial real estate. If you own or manage a building with Metasys, you're in good company — but you may also be facing some familiar challenges.
Understanding Your Metasys System
Metasys N2 (1980s-1990s)
Original generation using proprietary N2 bus protocol. Controllers include NCM, DX-9100, and application-specific controllers.
Metasys Extended Architecture (Early 2000s)
Added BACnet capability alongside N2, introduced NAE controllers.
Metasys ADS/ADX Plus (2010s)
Current generation with web-based interface, enhanced analytics, and cloud connectivity options.
Common Metasys Challenges
Hardware Obsolescence: Older NCM and early NAE models are increasingly difficult to source.
Software Support: Legacy software runs on outdated OS (Windows XP/7) with security vulnerabilities.
Protocol Limitations: Pure N2 systems can't communicate with modern BACnet equipment without gateways.
Service Availability: Pool of qualified technicians for legacy N2 systems is smaller.
Option 1: Upgrade Within Metasys
- ✓ Manufacturer-supported migration
- ✓ Proven, mature platform
- ✓ Training familiarity for team
- ✓ Single vendor relationship
- ⚠ Premium pricing
- ⚠ Continued vendor lock-in
- ✓ Lower initial cost
- ✓ Vendor independence
- ✓ Open protocols (BACnet)
- ✓ Gradual migration path
- ⚠ Running two platforms initially
- ⚠ N2 expertise still needed
Option 3: Hybrid Approach
Many buildings end up with a hybrid strategy combining elements of both:
- Add an open supervisory platform (Niagara) immediately for modern interface
- Keep functional Metasys controllers where they work well
- Replace failing controllers with open BACnet devices
- Upgrade critical areas while maintaining legacy in less critical zones
"This pragmatic approach balances cost, risk, and capability improvement. It's often the most sensible path for buildings that can't justify a complete system replacement but need modernization."
Decision Factors
Consider These Factors
- Current System Condition: If controllers are functional, integration may be efficient. If failing throughout, more replacement needed.
- Scale: Larger buildings with hundreds of controllers benefit more from phased approaches.
- Service Relationship: If JCI service has been problematic, an open platform enables competitive bidding.
- Long-Term Plans: Major renovation planned? Coordinate with BMS decisions.
- Regulatory Requirements: Local Law 97 may require capabilities your current system lacks.
The N2 Protocol Question
For buildings still running N2 protocol, plan for migration. N2 is a frozen standard with:
- Limited pool of expertise
- No new development
- Integration complexity increasing
This doesn't mean immediate replacement, but you should be moving toward BACnet as the primary protocol.
Making the Transition: Practical Steps
Step 1: Complete system inventory — controllers, software, network, known issues
Step 2: Define requirements — what must the future system do?
Step 3: Get multiple perspectives — JCI and independent integrators
Step 4: Plan for transition — phase work to minimize disruption
Step 5: Budget for training and documentation
Working with Controls NYC
At Controls NYC, we have extensive experience with Metasys systems across all generations. We're not a Johnson Controls dealer, which means we can provide objective advice about your options — including when staying with Metasys makes sense.
Contact Controls NYC for a straightforward assessment of your Metasys system and honest advice about your path forward.
Sources & References
- Johnson Controls Building Automation - Official Product Information
- Tridium Niagara Framework Documentation
- BACnet International - Open Protocol Standards
Ready to Discuss Your Building?
Whether you're evaluating an upgrade, dealing with a failing system, or just want a second opinion — we're happy to talk through your options.
Schedule a Free Consultation