BACnet Device Integration
Connect BACnet device data with the applications your building depends on. Put communication, equipment context and application requirements in the same conversation.
Explore BACnet Device IntegrationCommunication serversMake the connection.
Make the connection.
Use the information.
Connect devices, networks and web-service data to the application interfaces your project needs.
Choose your building blocksStart with the work
Start with the work
you need to do.
Each product has a distinct role. Follow the path that fits your source systems and engineering requirements.
SNMP Device Integration
Bring information from network-connected equipment into your operational view. Connect the namespaces your devices expose to the data your application needs.
Explore SNMP Device IntegrationCXS JSON Server
Bring JSON data from devices and services into OPC-compatible applications. Connect useful information to the systems your team already works with.
Explore CXS JSON ServerDefine the fitThree questions.
Three questions.
A useful starting point.
What is the source?
Identify devices, protocols, services and the access available to the project.
Where will it be used?
Confirm the application platform, client interface and deployment boundaries.
What needs engineering?
Separate runtime communication from discovery, configuration and application design.
BACnet+ for IgnitionBuilding data.
Building data.
Alarms. History. Schedules.
Choose BACnet/IP or BACnet Secure Connect for the network your application needs.
Connectivity / Ignition
BACnet+ IP
BACnet/IP connectivity with native alarms, history and scheduling in Ignition.
Discuss BACnet+ IPExplore the module
Connectivity / Ignition
BACnet+ SC
BACnet Secure Connect with encrypted, certificate-based communication and native Ignition integration.
Discuss BACnet+ SCExplore the moduleBuilt for builders
Bring us the application.
Tell us what you are connecting, the platform you use and the work you need to do.
Discuss your project