USE CASES · IOT
Building automation: sustaining services and responding in time
A water tank may start emptying long before a resident notices a supply interruption. A pump may operate outside its usual condition for several cycles. Building management needs to recognize those signals early enough to investigate and coordinate a response.
Building automation and IoT can extend that observation capability. Their value depends on turning measurements into information that maintenance staff, management and residents can use, with different roles and permissions.
Lighting and climate control in shared spaces
Schedules, daylight and the use of a zone help determine when equipment needs to operate. A lack of movement does not always mean that a room is empty; a meeting room with seated occupants needs a different criterion from a corridor.
Scheduling should retain manual control and appropriate equipment limits. The lighting and climate control case develops a zone-level trial that considers comfort and energy used. Lower consumption is valuable when the service people need is maintained.
Energy: relating consumption to services
Meters help investigate the demand of each service and when it changes. Interpreting differences requires knowing occupancy, weather, schedules and maintenance work. An aggregated record may need additional measurements to locate a cause.
Comparison should specify power or energy, units and intervals. Data acquisition and any circuit modifications require appropriate equipment and installation conditions. A dashboard supports investigation; electrical protection devices retain their specific role.
A first improvement may be correcting an operating schedule or inspecting equipment that consumes energy during waiting periods. Measurements before and after help evaluate the effect without promising a percentage saving.
Access: managing permissions and keeping useful records
Access control links a credential with a valid permission and a door. Visitors, residents and maintenance staff may need different scopes. The record should make it possible to review and revoke an authorization and identify which system confirmed its application.
Local entry and exit functions need to be considered when designing the integration. Connection to a management platform does not replace the installation’s requirements. Who can consult movement records and how long those records are kept also need to be defined.
Cameras can provide context for reviewing an event. Their location and access to images need an explicit purpose. Collecting more data without a clear question may add work and expose information without improving the service.
Maintenance: from an observed condition to an intervention
Pumps, climate control and other equipment can provide temperature, vibration, operating hours or status. Comparison needs equivalent conditions. A change in load may alter a signal without indicating a failure.
An alert should bring together evidence a technician can review. Inspection and its outcome are then recorded: intervene, keep observing or correct the measurement. Predictive maintenance needs additional evidence to demonstrate warning time, missed problems and unnecessary alerts.
Lifts and other systems with specific functions are integrated through the access methods and procedures appropriate to their maintenance. Additional monitoring must preserve that division of responsibilities.
Water: understanding level, replenishment and consumption
A level reading helps observe the reserve. Understanding its evolution requires relating it to inflows, consumption and pump operation. Sensor selection must consider the geometry, environment and actual tank conditions.
If the level drops, the response may be to check replenishment, inspect a pump or prepare a communication. The notification needs to state when the reading was taken and whether data is still arriving. An old reading cannot establish the current reserve.
Local pump controls must retain their operating limits and protections. A schedule intended to manage operating times cannot disregard water availability. The trial should include communication loss and sensor faults.
Leaks and persistent consumption can also be investigated through localized sensors or flow measurements. Green spaces require relating irrigation, moisture and use. An apparently unusual observation needs to be checked against the services that were expected.
Waste: observing condition to organize collection
In some buildings, knowing how full containers are and how often they are emptied may be useful. The shape of the waste and container affects a distance measurement; it needs to be checked against the actual condition.
The data may help organize a task within the hygiene and service conditions applicable to the building. Its usefulness should be compared with a simpler inspection or schedule. Connectivity makes sense when it improves a specific decision and justifies its maintenance.
Communication: informing the appropriate people
A technical event may require a staff inspection followed by a notification to affected residents. Those messages have different purposes. Communication should state what is known, what is being done and when an update can be expected, when that can be established.
Message delivery, acknowledgment and problem resolution need to remain distinct. A responsible person, confirmation of attention and an escalation path should be established for tasks that remain pending.
Notifications are reviewed for relevance and frequency. Informing the entire building about every reading may consume attention without supporting an action. Recipients and content are chosen according to the incident and permissions.
Integrating with explicit functions and limits
Node-RED can bring messages together and coordinate records and notifications. A local device can execute rules that need to remain available without Internet access; that continuity must be designed and tested. Installing a backup computer does not ensure it by itself.
A remote platform can facilitate consultation across buildings. When AWS IoT Core is used, message reception and routing are configured alongside processing, persistence and permissions. The dashboard displays data time and quality to make disconnection visible.
Node-RED security configuration, device credentials and user authorizations are part of maintenance. Each extension needs to preserve an understandable way to manage those permissions.
Testing a complete service workflow
We can start with water supply or one lighting zone. The trial records observations, notifications, decisions and results, including missing data and situations in which nobody responds.
We need to establish whether the building sustains the service, whether the responsible person receives better evidence and how much effort the solution requires. That result helps determine which other part of the operation is worth connecting.