Frequently Asked Questions

Yes. We specialize in retrofitting legacy Tridium, Honeywell, and JCI systems via edge gateways, avoiding the need for a "rip and replace" job.

We support all major industrial protocols including BACnet/IP, BACnet MSTP, Modbus TCP/RTU, KNX, and LonWorks.

Typically 2–6 weeks depending on scale. Since we work in parallel with existing controllers, downtime is minimal to non-existent.

Minimally. We tap into the communications bus passively at first. Active control is migrated gradually, ensuring business continuity.

Yes. Our Haystack-compatible tagging model normalizes data from disparate systems (e.g., a Daikin VRV and a Siemens Chiller) into a unified standard.

Yes. Our energy engineers follow IPMVP Option A and Option B protocols. Before retrofit you receive a detailed M&V Plan; after commissioning you receive quarterly M&V Reports comparing baseline energy consumption against post-retrofit actuals, adjusted for occupancy and weather variables. This is the documented evidence your sustainability reporting team needs for GRESB, EPC, or ESG commitments.

Yes. We support API and direct integration with Schneider EcoStruxure, Siemens Navigator, IBM Maximo, and custom Power BI dashboards via our Haystack-normalised data layer. We can also push live energy and equipment data to landlord reporting portals or your GRESB evidence pack. If your CAFM vendor provides an open API, we can typically connect within the project scope.

Our audit covers: full controller inventory and firmware capture; existing point schedule extraction via passive monitoring (no system cutover); energy baseline from meter data; review of HVAC sequences of operation; and identification of quick-win optimisations such as setpoint corrections and scheduling gaps. You receive a written report with prioritised recommendations and estimated payback periods within five business days of the site visit.

This is a core strength. We deploy a Niagara Framework or Priva top-level supervisor that normalises data from Siemens, Schneider, JCI, and legacy proprietary systems into a single dashboard. You get one reporting view, one alarm management interface, and one maintenance contract — regardless of the brand mix across floors or sites.

Yes. Our IoT sub-metering approach uses pulse-output or Modbus energy meters connected to LoRaWAN or RS-485 gateways, installed in one to two days per building without any control system changes. Sub-meter data feeds directly into our analytics dashboard and can be allocated by tenant, floor, or system type for recharging, utility budgeting, or sustainability reporting purposes.

We deploy industrial-grade LoRaWAN and MQTT sensors for occupancy, air quality (IAQ), temperature, humidity, and water leak detection.

We focus on long-range wireless (LoRaWAN) for minimal architectural impact, but also support PoE wired sensors for mission-critical zones.

Our LoRaWAN sensors typically feature a 5–10 year battery life depending on reporting frequency, drastically reducing maintenance overhead.

Extremely. Data is encrypted AES-128 from sensor to gateway to server. We can also deploy entirely on-premise LoRaNS servers to keep data off the cloud.

Yes. We use sensing cables and spot detectors to identify leaks instantly and can trigger automated shut-off valves via the BMS integration.

Yes — this is the closed-loop advantage of our BMS and IoT integration. Occupancy data from LoRaWAN sensors triggers HVAC zone activation and lighting scene changes through the BMS, removing the need for manual scheduling. Air quality data — CO₂, VOC, particulates — triggers demand-controlled ventilation, ramping fresh air only when and where it is needed, cutting unnecessary energy spend.

All sensors are factory-calibrated and we record baseline readings on commissioning. For critical IAQ sensors we schedule annual field calibration checks as part of PPM. Sensors reporting outside expected range are flagged automatically by our monitoring platform. We also run cross-sensor plausibility checks — if one sensor in a zone reads anomalously versus its neighbours, it is flagged for inspection.

Yes. We deploy CO₂, TVOC, PM2.5, and PM10 sensors mapped to the specific requirements of WELL Building Standard v2, LEED v4 EQ credits, and Fitwel. Our platform generates automated compliance reports showing average and peak readings per zone against the relevant benchmark thresholds, exportable in the format typically required by certification assessors.

We treat fire and life safety systems as separate from our IoT infrastructure to protect system integrity — they remain under their own certified controls. However, our BMS integration can receive output signals from the fire panel to trigger HVAC shutdown modes, pressurisation, or elevator recall via volt-free contacts. We do not modify certified fire safety systems under any circumstances.

LoRaWAN sensors buffer data in the gateway locally and transmit missed readings on reconnection — typically with no data loss for outages under 24 hours. For MQTT-based sensors in more critical applications, we deploy local edge servers that continue to receive and process sensor data independently and sync to the cloud on reconnection, ensuring continuity of alarm monitoring.

For high-security clients, we offer fully air-gapped on-premise deployments. No data ever leaves your physical network or touches the internet.

Yes, we can bring ONVIF, RTSP, and major VMS feeds into the central dashboard for a unified view, correlating video with access events.

We integrate with leading biometric readers (fingerprint, facial recognition, iris) and map those credentials to user profiles in the system.

You retain full control. Footage is stored on your local NVRs or SANs. We do not aggregate video data to our servers unless specifically requested for cloud backup.

We follow strict OT cybersecurity practices (IEC 62443), employing network segmentation, strict firewall rules, and regular vulnerability scanning.

Yes. We integrate with Microsoft Active Directory / Entra ID, SAP HR, and leading HRMS platforms to enable automated joiner-mover-leaver workflows. When a staff member is added to HR, access credentials are provisioned automatically. When they leave, credentials are revoked across all controlled doors simultaneously — closing the administrative gap that creates most insider-threat vulnerabilities.

We deploy Genetec Security Center analytics for crowd density monitoring, loitering detection, perimeter intrusion, licence plate recognition (ANPR), and direction-of-travel rules. For hospitality and retail clients we can add people-counting, queue length analytics, and heat-mapping. All analytics run on-premise on the VMS server — footage is not uploaded to cloud AI services.

Default retention is 30 days for continuous recording. For compliance-sensitive environments we extend to 90 days or more. Storage is sized at design stage using camera resolution, frame rate, H.265 compression, and site-specific motion density estimates. We specify enterprise RAID storage with N+1 redundancy and automated disk health monitoring as standard on all projects.

Yes. Genetec Security Center Federation and Omnicast allow a central SOC to view live and recorded video, manage access events, and respond to alarms across unlimited remote sites from one console. Each site retains its own local recording server for resilience — the federation layer provides central oversight without creating a single point of failure.

Yes. We integrate with Genetec Visitor Management and compatible platforms such as Envoy to allow hosts to pre-register visitors, generate time-limited QR or PIN credentials, and automatically revoke access at visit end. Reception desks receive arrival alerts and can print badges or issue mobile credentials. All visitor events are logged in the access control audit trail for compliance.