Smart Building Software Development

Integration with existing BMS platforms and building automation systems without replacing the installed equipment: Siemens Desigo CC, Honeywell Experion and EBI, Johnson Controls Metasys, Schneider EcoStruxure Building Operation, and independent BACnet, LON, and KNX controllers. Protocol-level integration approach selected per system: BACnet/IP and BACnet MS/TP for HVAC and AHU controllers (the most common building automation protocol for post-2000 commercial buildings), KNX for European commercial lighting and HVAC systems (via KNXnet/IP), LON (LonWorks) for older building automation installations via LON-to-IP gateways, Modbus TCP and RTU for energy meters and industrial HVAC equipment, M-Bus for utility sub-meters (gas, water, thermal energy), DALI for digital lighting control, and MQTT over TLS for modern IoT-enabled sensors and smart devices. Protocol gateway devices (Anybus, Moxa, Kepware KEPServerEX) placed on-site to bridge legacy fieldbus protocols to IP and enable cloud connectivity without replacing legacy controllers. Edge processing via on-premises industrial PC or ruggedised edge server for buildings with data sovereignty requirements or unreliable internet connectivity -- data aggregated locally and synchronised to the cloud platform on connectivity recovery. Write-back control integration (setpoint changes, schedule overrides, relay triggers) for automated responses to defined conditions where the BMS vendor and building operator have agreed to enable remote control.

Sub-metering dashboards showing energy consumption by floor, zone, HVAC circuit, lighting circuit, and time period -- not just a building-level total pulled from a utility meter. Pulse-output energy meters connected via Modbus RTU or Modbus TCP feed kWh readings directly into the platform at 15-minute intervals; smart meters with DLMS/COSEM protocol are read via M-Bus gateway where a direct connection is available. Automated waste detection rules applied across the incoming data stream: HVAC air-handling units running on a weekend with occupancy sensors reporting zero people in the zone; lighting circuits active after the last access control exit event of the day; chiller plant draw that exceeds the expected load curve for the current outdoor temperature. Energy anomaly detection flags deviations from the rolling 4-week baseline for each circuit -- a 15% unexplained increase on a specific AHU triggers an alert before it appears on a utility bill. Demand response integration: during peak tariff periods (or when a demand response signal arrives via OpenADR 2.0), non-critical loads are shed automatically -- car park ventilation, perimeter lighting, non-essential HVAC zones -- based on a priority shedding schedule configured with the facilities team. Benchmarking views normalised by occupied floor area (kWh/m²) or occupancy count allow comparison across buildings, floors, or time periods without the distortion from size differences. Reports formatted for ASHRAE 90.1 compliance, LEED/BREEAM energy reporting, and ISO 50001 energy management system documentation so the sustainability team is not assembling the same data separately for each certification body.

Space utilisation analytics combining data from multiple sensor types and building systems, because no single sensor gives the complete picture: passive infrared (PIR) occupancy sensors report zone-level presence; camera-based people counters (Xovis, IRISYS, Axis) provide precise headcount at entrances and floor transitions; WiFi probe data from the network infrastructure gives a building-level device count without additional hardware; access control badging data records who entered which zone and when. Each source has different accuracy characteristics -- PIR sensors detect presence but not count; cameras count but require careful placement; WiFi underrepresents because not every person's device continuously probes. The analytics layer reconciles these sources into a single occupancy estimate per zone, flagging conflicts where sources disagree by more than a configured threshold. Desk booking system integration (Robin, Envoy, OfficeSpace, Condeco) adds the intended occupancy side of the equation: the system knows how many desks were booked versus how many were actually occupied, which is the metric that drives space planning decisions. Reports for real estate and workplace strategy teams show floor-level and zone-level utilisation rates over rolling 4-week, quarter, and year periods -- the data that justifies or challenges lease renewal decisions and desk-ratio changes. BLE beacon integration (Estimote, Tile, Kontakt.io) optionally extends zone-level precision to 3-5 metre resolution for conference room and hot-desk tracking without requiring named user tracking. Real-time occupancy dashboards for facilities management: cleaning teams deploy around actual building use rather than a fixed schedule, catering calibrates service to actual headcount, and security controls building-wide occupancy during emergencies.

Integration with existing access control systems via REST API, manufacturer SDK, or OSDP (Open Supervised Device Protocol) to surface access event data in the unified building platform without replacing installed hardware. Systems connected include Lenel (part of Carrier Global), Genetec Security Center (via SDK), Avigilon (via RESTful API), Software House C-CURE 9000 (via EventTracker API), Honeywell Pro-Watch (via database-level integration), and cloud-native platforms such as Brivo and Kisi via documented REST APIs. Badge holder management: the building platform consumes the cardholder and access group data from the access control system rather than maintaining a separate directory -- changes made in the access control system propagate to the building platform view in near real time. Door event stream: every access event (granted, denied, forced, held open, door ajar alarm) is ingested, timestamped, and logged to the building platform audit database. The audit trail combines access control events with energy metering, HVAC, and occupancy data against a common timeline -- enabling investigation workflows where a security team can correlate an energy spike with an unexpected access event in an unoccupied zone. Visitor management workflows integrated with building access: pre-registration through the tenant portal or a web form generates a time-limited access credential issued automatically to the visitor before arrival, eliminating the reception queue. Integration with visitor management platforms (Envoy, Proxyclick, Traction Guest) via API where those platforms are already deployed. CCTV event integration: camera systems with analytics output (motion events, person detection alerts) can trigger dashboard notifications in the building management interface for security teams -- the integration is event-based rather than video streaming, keeping bandwidth requirements and privacy risk low. Unified compliance reporting: zone access logs combined with visitor records produce the audit report required for ISO 27001 physical access controls, financial services regulatory requirements, and data centre access logging standards.

Web and mobile tenant portals built as a React/Next.js progressive web app (installable on iOS and Android via PWA without requiring App Store distribution) or as a native mobile app where push notification reliability and biometric login are priorities. Tenant onboarding tied to the building's access control system: when a new tenancy is configured in the access control system, a portal invite is automatically generated and sent to the primary tenant contact with role-based access for up to N named users per tenancy. Comfort and environment requests: tenants submit temperature, lighting, and ventilation complaints through the portal, which creates a timestamped record in the facilities management queue and optionally triggers an automatic HVAC setpoint adjustment if write-back integration is in scope. Service request submission and tracking: maintenance requests, cleaning escalations, and reactive works move through a visible workflow -- submitted, acknowledged, in progress, resolved -- with push notification delivery at each stage via FCM (Firebase Cloud Messaging) for Android and APNs for iOS. Visitor pre-registration: the tenant creates a visitor record in the portal (name, company, date, time, host) which generates a time-limited access credential delivered to the visitor by SMS or email before arrival, eliminating reception queuing. Meeting room booking integrated with the building's space inventory and the tenant's Microsoft 365 or Google Workspace calendar via Graph API and Google Calendar API respectively -- room availability reflects real-time status from both the booking system and the occupancy sensor layer. Per-tenancy data isolation enforced at the database level using row-level security: tenant A cannot see tenant B's service requests, visitor records, or usage data under any application condition. For multi-tenant buildings with different operators per tenancy, white-labelled portal options with per-tenancy logo, colour scheme, and domain. Service billing via Stripe Connect: building services consumed beyond the base lease (meeting room overtime, event space hire, car park, fitness facilities) billed directly to the tenant's stored payment method with itemised receipts.

Automated fault detection combining rule-based and statistical methods against the continuous stream of data from BMS, energy meters, and sensors -- because the threshold rules that catch the obvious failures miss the gradual degradation patterns that show up first in the data. Rule-based fault detection follows ASHRAE Guideline 36 sequences for air-handling units and variable air volume boxes: supply air temperature deviations from setpoint beyond tolerance for more than a configurable duration, simultaneous heating and cooling valve activity (a common energy waste fault), economiser controls not responding to outdoor air conditions. Statistical fault detection applies building-specific baselines: a rolling 4-week regression model of expected chiller power draw against outdoor wet-bulb temperature flags a 12% unexplained increase in plant power consumption as a potential refrigerant leak or condenser fouling -- faults that don't violate any single BMS alarm threshold but show up clearly in statistical deviation from the expected curve. Fault prioritisation: each detected fault is scored by estimated energy waste per day, estimated maintenance cost if left unattended (based on equipment type and fault pattern), and whether the fault directly affects tenant comfort. The maintenance team sees a ranked queue rather than a noise floor of undifferentiated alarms. CMMS integration for automatic work order creation: faults that breach configured thresholds create work orders in IBM Maximo (via REST API), Planon, ServiceChannel, or Corrigo CMMS without requiring a facilities manager to manually transcribe the fault description, timestamps, and sensor readings. Work order fields pre-populated with the affected equipment, fault type, sensor data at time of fault, and the recommended corrective action from the fault library -- reducing the diagnostic time for the responding technician. MTBF (mean time between failure) tracking per equipment class: the platform records fault history per asset, enabling proactive maintenance decisions before the next failure cycle based on observed failure frequency rather than manufacturer-recommended intervals that don't account for actual run hours and operating conditions.