A BAS integration project rarely fails because BACnet doesn't work. It fails because each major platform has its own quirks layered on top of the standard, from how points get exposed to how a supervisor handles third-party driver licensing. A team that plans an integration assuming every BAS behaves identically ends up surprised mid-project, after the contract is signed and the timeline is set. Knowing the common quirks ahead of time, by platform, is what keeps an integration on schedule, and teams can walk through their specific BAS mix in a short session.
Three Major BAS Platforms, Three Different Integration Realities
iFactory connects cleanly to Niagara, Metasys and Desigo environments, working around each platform's own quirks instead of assuming one approach fits all three.
Why Platform-Specific Planning Matters
All three platforms generally support BACnet, which makes them look interchangeable on paper. In practice, point naming conventions, supervisor licensing, and legacy protocol support differ enough to change how long an integration actually takes.
| Platform | Common Quirk | Typical Workaround |
|---|---|---|
| Niagara | Station licensing can limit third-party driver connections | Confirm licensing tier before scoping point count |
| Metasys | Older sites often still run legacy N2 alongside BACnet | Plan for a protocol gateway on mixed-generation sites |
| Desigo | Point naming conventions vary significantly by installer | Build a point-mapping pass into the project plan upfront |
Get Your BAS Mix Reviewed Before You Scope the Project
Book a 30-minute session and iFactory will review your specific BAS platforms and versions for integration planning.
Niagara: Licensing and Station Architecture
Niagara's supervisor-and-station architecture is flexible, but third-party integrations depend heavily on how the existing station is licensed and how many point connections it already supports.
Check Licensing Tier First
Confirm whether the existing Niagara license supports the additional point connections an integration will add.
Map the Station Hierarchy
Multi-station deployments need a clear map of which station owns which points before integration begins.
Metasys: Mixed-Generation Protocol Support
Metasys deployments that have grown over many years often carry legacy N2 devices alongside newer BACnet ones, and an integration plan needs to account for both.
Audit for Legacy N2 Devices
Identify which field controllers still run N2 before assuming a pure BACnet integration path.
Plan Gateway Requirements Early
Where N2 devices remain, a protocol gateway becomes part of the integration scope, not an afterthought.
Desigo: Point Naming Consistency
Because Desigo installations often reflect each installer's own naming habits, point mapping tends to be the single biggest time sink on an integration project.
Budget Time for Point Mapping
A dedicated mapping pass against the actual point list avoids surprises once live data starts flowing.
Standardize Naming Going Forward
New points added after integration should follow an agreed naming convention to avoid repeating the same cleanup later.
Signals Your Current Integration Plan Has a Gap
Where iFactory Fits
iFactory integrates with all three platforms using drivers and mapping approaches suited to each one's specific quirks.
Platform-Aware Drivers
Connection methods account for licensing, protocol generation and naming differences by platform, not a one-size-fits-all driver.
Point-Mapping Tooling
A structured mapping pass normalizes inconsistent point names before data starts flowing into reports.
Legacy Protocol Gateways
Older N2 or other legacy devices are bridged in rather than requiring hardware replacement.
Mixed-Platform Portfolios
A portfolio running different BAS platforms across buildings still rolls up into one consistent view.
Reviewed by iFactory's BAS Integration team for accuracy against current platform behavior. Specific licensing terms, protocol support and naming conventions can vary by installation and version, so confirm current specifics with each platform's documentation or vendor before finalizing a project scope.
Frequently Asked Questions
Does a mixed-platform portfolio need separate reporting per platform?
No, data from all three platforms can roll up into one consistent portfolio view once the integration is in place, even though each platform is connected through its own appropriate method. Support can show a unified view across mixed platforms.
How long does point mapping typically add to a project timeline?
It varies by how consistent the existing naming already is, but a dedicated mapping pass is worth budgeting as its own project phase rather than assuming it happens automatically during connection.
What if we don't know our current Niagara licensing tier?
This is common, and confirming it is one of the first steps in a proper integration assessment rather than something to guess at. See how licensing gets confirmed during planning in a short session.
Can legacy N2 devices be fully replaced instead of bridged?
Replacement is an option but usually costs significantly more and takes longer than bridging through a gateway, so most projects bridge first and plan replacement on a separate equipment lifecycle timeline.
Does platform version matter for integration compatibility?
Yes, older platform versions can have different capabilities than current releases, which is why confirming version alongside platform type is part of a thorough assessment. Ask support how version affects your specific integration path.
Integrate With the BAS Platforms You Actually Have
iFactory connects cleanly to Niagara, Metasys and Desigo, quirks included. Book a walkthrough on your own platform mix.
