Leak and water-risk devices
Water sensors, probes, local controllers, alarm relays, low-point locations, riser or mechanical-room context, and visible integration notes.
IoT / Sensors & Metering
Sensor and OT endpoint records for systems that are easy to forget until they fail.
Environmental sensors, leak detection, submeters, occupancy devices, gateways, and cloud-connected endpoints often fall outside the normal owner record.
Globin Engineering documents the installed IoT / Sensors & Metering environment so facilities, IT, security, energy teams, and vendors can see what exists, where it reports, who supports it, and what needs follow-up.
Endpoint mapSensors, rooms, areas, and monitored conditions
Meter inventoryElectric, water, gas, thermal, pulse, and panel notes
Gateway traceCloud, BAS, network, cellular, and dashboard paths
Alert routingRecipients, monitoring assumptions, and owner responsibilities
Support riskOffline, duplicate, battery, unsupported, and EOL conditions
Refresh baselineInput for leak audits, IAQ, energy, insurance, and updates
Scope
Map sensor endpoints before alerts, reports, and dashboards are trusted.
The record captures field-observable and stakeholder-supplied information: sensor types, locations, gateways, meter points, dashboard context, alert paths, support ownership, photos, and unresolved conditions.
It is not sensor design, calibration, alarm programming, IAQ certification, utility-grade meter validation, energy analysis, network configuration, commissioning, or live remediation unless those services are separately scoped.
Environmental and IAQ endpoints
Temperature, humidity, CO₂, IAQ, refrigerator/freezer, equipment-room, mechanical-room, and specialty monitoring devices.
Metering and energy points
Electric, water, gas, thermal, pulse, submeters, meter panels, labels, gateways, and visible communication paths.
Occupancy and lighting inputs
Occupancy sensors, room controllers, lighting-control endpoints, relay panels, zone notes, and space-use dependencies.
Gateways, dashboards, and alert paths
PoE devices, hubs, cloud gateways, cellular units, BAS links, dashboards, notification routes, and support responsibility.
Exceptions and lifecycle flags
Offline devices, dead batteries, unlabeled gateways, inaccessible endpoints, duplicate sensors, missing alerts, unsupported hardware, and likely EOL/EOS equipment.
Sensor record boundaries
What gets counted in an IoT / Sensors & Metering record?
Sensor records can range from a basic endpoint list to a deeper platform and alert-routing review. A standard owner record focuses on identifiable sensors, meters, gateways, dashboards, network dependencies, alert paths, ownership notes, photos, and exceptions.
Calibration, functional testing, alarm programming, measurement validation, IAQ certification, utility-grade verification, energy analysis, and live changes require separate scope.
| Record level | Normally included? | Examples |
|---|---|---|
| Sensor endpoint record | Yes | Leak, temperature, humidity, IAQ, occupancy, refrigerator/freezer, and specialty sensors |
| Metering record | Yes | Submeters, pulse inputs, utility meters, meter panels, gateways, and labels |
| Gateway / platform context | Where available | Hubs, PoE devices, cellular gateways, dashboards, cloud portals, BAS links |
| Alert-routing context | Where available | Notification paths, responsible parties, dashboard owners, monitoring assumptions |
| Testing / calibration | Separately scoped | Calibration, alarm testing, IAQ certification, meter validation, commissioning |
DeliverablesSensor floorplan overlaySensor locations, meter points, gateways, panels, dashboards, and support notes shown by floor or area. Sensor and meter inventoryDevice type, location, apparent vendor, visible model where available, platform, status, and exception flag. Gateway and platform summaryCloud gateways, hubs, BAS links, cellular units, PoE devices, dashboards, and ownership context. Alert and integration notesBMS / BAS / OT, LAN, cloud, cellular, relay, and notification paths separated into confirmed, provided, and unknown items. Lifecycle and exception reportOffline devices, dead batteries, missing alerts, unsupported gateways, abandoned sensors, unknown ownership, and replacement candidates. Owner handoff packageA usable baseline for leak audits, IAQ reviews, metering work, energy projects, insurance reviews, and annual updates.
IoT / Sensors & Metering deliverables built for alerts, operations, and refresh planning.
IoT / sensor / metering technical context
Sensor records should connect endpoints, gateways, platforms, alerts, ownership, and actionability.
Sensors only help when teams know what they monitor, where they are installed, how they communicate, which platform receives the data, who receives alerts, and who maintains the system. The owner record connects endpoints to operational context without replacing testing, programming, or engineering validation.
Major platforms and brands commonly encountered
- Distech Controls
- Johnson Controls
- Tridium / Niagara
- Legrand / Wattstopper
- Lutron
- EnOcean
- RLE Technologies
- AKCP
- Monnit
- Verkada Sensors
- Schneider Electric
- Siemens
- DENT
- Badger Meter
- Belimo
Brand lists are examples of environments the record may organize. They do not imply certification, authorization, partnership, or endorsement unless separately stated.
Technical fields the owner record can capture
- Leak, temperature, humidity, occupancy, IAQ, metering, utility, lighting-control, and environmental sensor records.
- Gateway, controller, BAS/OT, cloud platform, dashboard, alert-routing, network, power, and cellular context where available.
- Location, floor, room/area, sensor type, manufacturer/model, platform, confidence, visible status, and owner/vendor responsibility.
- Alarm path, notification recipient, dashboard owner, monitoring assumption, and escalation context where provided.
- Exceptions for dead batteries, offline sensors, missing alerts, unsupported gateways, abandoned devices, duplicate sensors, and unknown ownership.
Owner review questions this record helps answer
- Which sensors produce actionable alerts, and who receives them?
- Which devices are standalone, BAS-integrated, cloud-connected, cellular, tenant-managed, or vendor-managed?
- Which sensors are operational, abandoned, duplicated, offline, or missing from the owner record?
- Which dashboards, gateways, and notification paths are still supported?
- What should be refreshed before insurance, water-loss, IAQ, energy, or tenant-support reviews?
- What information should be redacted before vendor distribution?
Next Step
Start with leak detection, metering, environmental sensors, lighting inputs, or one OT closet.
A focused sensor survey can stand alone or become part of a broader building technology record. Start where the risk is clearest: water-loss exposure, IAQ complaints, energy reporting, missing alerts, unsupported gateways, or unclear ownership.