Tenant Experience Apps & the ELV Backbone for Irish Buildings

In 2019, a tenant experience app was a novelty on Dublin commercial property — a few Dublin Docklands landlords had deployed early PropTech platforms as a differentiator to attract US tech sector tenants. By 2026, the calculus has inverted: in Dublin 2, Dublin 4 and the Docklands, a building without a tenant app and integrated digital services is increasingly the exception rather than the rule. For Irish ELV designers, the tenant experience app is no longer just a PropTech product decision — it is a design constraint that determines which access control platforms, which network infrastructure and which API-enabled building systems must be specified from the outset of the project.

This article explains how tenant experience apps integrate with the ELV backbone, which building systems must expose open APIs to support app connectivity, which PropTech platforms are active in the Irish market, and what GDPR obligations arise from collecting tenant location and behavioural data through these platforms. It is written from the ELV designer's perspective, not the PropTech vendor's — because the decisions made at RIAI Stage 2 about access control protocol, BMS openness and network architecture will determine whether the tenant app works well, works poorly, or cannot be connected at all.

What Tenant Apps Actually Need from the ELV Backbone

Tenant experience apps require integration touchpoints with multiple building systems. The criticality and achievability of each integration depends on the ELV specifications made at Stage 2. The following table summarises the key integration requirements:

Access Control: The Most Critical Integration

Mobile access credentials — replacing physical keycards with a smartphone app — are the most universally demanded tenant app feature on Irish commercial property. Implementation requires the access control system (ACS) to support a mobile credential standard and to expose a REST API for credential provisioning. The two dominant mobile credential standards in Irish deployments are HID Mobile Access (using Seos or OMNIKEY readers with BLE/NFC) and ASSA ABLOY Mobile Keys (using NFC and BLE on compatible hardware). Both require readers that are either replaced or upgraded from existing RFID-only readers.

The critical specification requirement for Irish ELV designers is that the access control platform must expose a documented, supported REST API with OAuth2 authentication that third-party tenant apps can use to provision and deprovision credentials without requiring manual intervention by the security team. Not all ACS platforms offer this — some have proprietary integration SDKs that require expensive custom development per PropTech vendor. The leading ACS platforms with published open REST APIs suitable for tenant app integration in the Irish market include Lenel OnGuard (REST API via Lenel S2 NetBox), Genetec Security Center (REST API via Genetec Web SDK), Software House C•CURE 9000 (REST API via CCURE Web Services), and Brivo (cloud-native, REST API first-party). Irish ELV designers should add "published REST API with OAuth2 credential provisioning" as a mandatory tender requirement for any ACS specified on a building targeting tenant app connectivity.

BMS Data: Environmental Comfort and Energy Transparency

Tenant apps that display real-time indoor environmental quality (IEQ) data — CO2 levels, temperature, humidity, particulate matter — require either a dedicated IoT sensor layer with cloud connectivity, or integration with the building BMS. BMS-sourced data is typically available via BACnet/IP polling from the BMS server, which requires an integration middleware layer (typically a cloud IoT gateway or an iPaaS platform such as MuleSoft, Boomi or Microsoft Azure Logic Apps) to translate BACnet/IP data to the REST/JSON format the tenant app consumes.

The alternative approach — deploying a dedicated IoT sensor layer (Disruptive Technologies, Pressac, SensorPush, Awair Element) connected directly to an IoT platform (AWS IoT Core, Microsoft Azure IoT Hub) — provides higher data granularity, faster refresh rates and easier GDPR-compliant data segmentation, but adds hardware cost of €60 to €120 per sensor node. For large Irish campuses with extensive BMS infrastructure, BMS-integrated data often provides the most cost-effective path to tenant app IEQ feeds. For buildings with limited BMS scope or new high-spec tenant-facing campuses, a dedicated IoT sensor layer delivers a better outcome.

PropTech Platforms Active in the Irish Market

The following platforms have active Irish deployments or local partnerships as of 2026:

• HqO — US-origin workplace experience platform with significant Dublin Docklands landlord client base (Kennedy Wilson, Hibernia, Iput). Includes mobile access via HID integration, room booking, events, food/coffee ordering and sustainability dashboard. Requires ACS REST API and tenant-level sub-metering for full feature deployment.
• Equiem — Australian-origin building community platform with growing Irish market. Strong on community features (events, notifications, local services), moderate on ELV integration depth.
• Planon Workplace — Enterprise-grade FM-integrated workplace platform. Used by large Irish corporates (insurance, financial services) for space management, FM ticketing and occupancy analytics. Deep BMS and access control integration capability via Planon open API.
• Microsoft Viva Insights + Workplace Analytics — Microsoft 365-integrated occupancy analytics based on Teams call data, Outlook calendar, and badge access correlations. Not a standalone building app, but increasingly used by large Irish enterprise tenants as the "de facto" occupancy analytics layer without deploying separate PropTech.
• Custom White-Label Apps — Several large Irish landlords (particularly those with 500,000+ sq ft portfolios) have commissioned custom white-label tenant apps on AWS Amplify or Azure Static Web Apps, integrating directly with their ACS, BMS and metering systems via in-house middleware. Provides full brand control and deeper ELV integration but requires ongoing development resource.

GDPR and Irish Data Protection Obligations

Tenant experience apps that collect location data, access event logs, desk booking history and environmental comfort preference data are processing personal data as defined by GDPR and the Irish Data Protection Act 2018. The Irish Data Protection Commission (DPC) is headquartered in Dublin and has demonstrated active enforcement, including multi-million euro fines under GDPR Article 83. Irish landlords deploying tenant apps must ensure:

• A comprehensive Privacy Notice is presented at app onboarding, covering what data is collected, how it is used, retention periods, and data subjects' rights under GDPR Articles 13/14
• Legal basis for each processing activity is documented — typically contract (for access control enabling building entry), legitimate interest (for occupancy analytics) or consent (for optional services like food ordering location tracking)
• Access log data retention is limited to the minimum necessary — DPC guidance suggests 30 days for non-security access events; 90 days for security-relevant events
• A Data Protection Impact Assessment (DPIA) is completed where the app tracks individual movement patterns across a building, as required under GDPR Article 35 for "systematic monitoring of a publicly accessible area" or high-risk employee monitoring
• Data Processing Agreements are in place with the PropTech vendor as data processor under GDPR Article 28

Specifying for Tenant App Readiness: ELV Design Checklist

Irish ELV designers should include the following requirements in Stage 3/4 ELV specifications for buildings targeting tenant app connectivity:

• Access Control: open REST API with OAuth2, mobile credential support (HID Seos or ASSA ABLOY Mobile Keys), documented credential provisioning endpoint
• BMS: BACnet/IP server mode with read/write access for authorised third-party integration clients; documented BACnet/IP device and object register
• Sub-Metering: tenant-level electricity metering (Modbus TCP or DLMS/COSEM) with 15-minute interval data exported to integration layer
• IoT Sensors: if deployed, MQTT or REST API with SSL/TLS, cloud platform gateway, documented data schema
• Network: dedicated VLAN for integration middleware with firewall rules allowing HTTPS outbound to PropTech platform cloud endpoints
• EV Charging: OCPP 1.6 or 2.0 compliant EVSE with booking API
• Digital Signage: CMS with REST API for event-driven content triggers from tenant app platform