Niagara and Reflow provide the supervisory experience. Facility Explorer and F4 controllers connect through BACnet/SC, BACnet/IP or MS/TP as the project requires; appropriate controller and gateway paths can preserve selected legacy N2 devices during phased work.
Reflow presents the site in one responsive, equipment-centered interface.
Open integration, trends, alarms and enterprise visibility.
IP backbone for current Facility Explorer and F4 designs.
IP and field-bus equipment control for airside systems.
Field controllers, expansion I/O and selected legacy devices.
Facility Explorer and Metasys are related Johnson Controls ecosystems but are not interchangeable. Exact integration and programming paths depend on model, firmware, database access and licensing.
No platform is best at everything. We match the system to the building, the people who will support it, and the owner's long-term plan.
JCI can be the right answer for a Facility Explorer estate, a phased N2 transition or a project that benefits from its equipment-controller breadth—as long as the long-term service path is designed up front.
Owners who want to retain an FX/Niagara investment while standardizing the graphics and operations layer.
Sites where selected legacy devices can stay temporarily while supervisory and equipment layers are modernized.
Database ownership, tools, licenses and native feature expectations must be documented before integration begins.
These links support the high-level architecture above. Final design depends on controller generation, software versions, licensing, cybersecurity standards and site conditions.
We can map the Facility Explorer, Metasys, BACnet and N2 layers and recommend a supportable Niagara end-state.
