The My Building software system architecture is that of a series of microservices running in a containerized environment, each executing their own specific role and function and interacting between each other and with the outside world following a defined set of rules. This architecture allows for a high degree of flexibility in deployment options as well as scalability. In addition to the microservices that make up the My Building application, there are a series of external applications which also may be containerized or may run stand alone. In all cases, care should be given to ensure that:
A multi-building network is the same as a single building network except for the following:
- Persistent data store is outside the container
- Processes for backup and restoration of data is well defined, monitored, and executed.
- Tools are implemented for monitoring the installation and alerting the appropriate individuals when there are problems.
Related Articles:
The Leviton Lighting Control Systems & "The network"
Before we discuss further about My Building system architecture, it's helpful to understand the basic layout of the lighting control network. First, looking at a single building deployment:- Lighting control Devices, like relays, dimmer, sensors, switches, keypads and the like, are located inside the room. They all communicate with each other on a local in-room network which can be either be "wired" using a proprietary protocol we all LumaCAN, or, "Wireless" using a protocol similar to Zigbee. All of the in-room devices managed by a Room Controller.
- All Room Controllers (RC), typically located one per room, communicate through a Wi-Fi network using MQTT/IP. The Wi-fi access points can be provided by Leviton or the customer. The customer is the preference.
- Clients using a web browser from their computer, or, the My Building app on their phone, communicate to the My Building software.
- Note: in some cases, the app will make a direct TCP/IP connection to the Room Controllers
- The BACnet point of presence, ASCII interface for A/V, et all, if provided, is local to the building network and at the location of the Building Management or Building Automation Server. These device that exposes bacnet to the network is one of the My Building microservices and often runs on a constrained Linux device provided by Leviton, but also be virtualized.
- My Building uses email for some notification, a SMTP server is required and should be provided by the local site IT team
A multi-building network is the same as a single building network except for the following:
- An MQTT broker must be located in (or available to) every building. This broker is used to keep communication necessary within the building...in the building. This broker will be setup as a bridge broker to the main MQTT broker
More Questions?
Please leave reply below or email LCTechSupport@Leviton.com
Last edited:
