Hassantuk Integration Platform for Multi-Building Operators across the UAE

Six connected workflows: (1) Portfolio-wide telemetry aggregation — fire alarms, equipment trouble, power interruptions, water reservoir levels, pump status, gas leakage signals from every Hassantuk-connected site. (2) Proactive maintenance routing — telemetry signals auto-route to maintenance with severity, location, SLA. (3) Building owner / FM client portal — portfolio status visibility for landlords and FM operators. (4) Approved installer operational dashboard — for Naffco, Firex, Ateis tier installers managing thousands of installations. (5) False-alarm pattern analysis — Bukhoor mode events, cooking false-alarms, building-specific patterns. (6) AMC alignment with Hassantuk monitoring — equipment triggering troubles auto-prioritised for AMC inspection.

Around those six, most operators also want: Hassantuk Command Centre coordination logs for incidents requiring Civil Defence dispatch, Bukhoor mode usage analytics across the portfolio, installation quality patterns per panel manufacturer, and leadership dashboards showing portfolio compliance health and Hassantuk monitoring effectiveness.

Hassantuk telemetry API access typically requires approved installer status. Naffco, Firex, Ateis (per Dubai Civil Defence) are the major approved installers; others exist. Approved installer status comes with API access to the panel telemetry from sites the installer commissioned and maintains.

For multi-building owners and facility management companies who aren't approved installers themselves, integration approaches vary: (1) partner with an approved installer who shares telemetry via the platform; (2) for sites where the operator is the responsible AMC contractor, API access can typically be arranged; (3) for purely owned-portfolio operators, manual signal verification workflows keep Hassantuk-connected sites in the operational view alongside any direct API integration.

The platform supports all three patterns — full API integration where access exists, partner-installer data sharing where access is brokered, and manual verification workflows where direct integration isn't yet possible. The integration approach is scoped during discovery based on operator status and portfolio composition.

Hassantuk continuously monitors fire alarm panels, smoke/heat detectors, fire pumps, sprinkler systems, equipment trouble signals, power interruptions, water reservoir levels, and gas leakage. Each signal carries operational meaning beyond fire alert — a low alarm panel battery flagged today is a maintenance issue resolvable in 30 days; ignored, it becomes an emergency in 90 days.

The platform routes telemetry signals to maintenance workflows with severity, location, and resolution SLA. Equipment trouble auto-creates a maintenance task. Disconnections detected and resolved before building owners notice the panel is offline. Pump room status anomalies trigger inspections before they compound.

For approved installers managing thousands of sites, this approach is designed to reduce emergency dispatch incidents by 40-60% and lift AMC contract compliance scores. For multi-building owners, it returns control over building maintenance to the owner rather than waiting for the AMC contractor's quarterly visit cycle.

Hassantuk's Bukhoor mode is a UAE-specific feature allowing traditional incense burning without triggering false fire alarms. Adoption varies by building type and demographic. False-alarm events from cooking, smoking, steam, and other non-fire causes also generate operationally important data.

The platform aggregates Bukhoor mode events and false-alarm patterns across the portfolio. Building-specific patterns surface — high false-alarm rates from kitchen-area sensors suggest sensor placement review; recurring Bukhoor mode usage suggests resident education opportunities or sensor sensitivity tuning.

For FM operators and large landlords, this analysis directly reduces false-alarm dispatch costs and improves resident satisfaction. For approved installers, false-alarm patterns inform sensor model selection and placement strategy for future installations.

Concept Evolution, IBM Maximo, Planon, Archibus are mature CAFM platforms widely used by UAE FM companies (EFS, Imdaad, Khidmah, Farnek, Emrill). They handle integrated facilities management well, with fire safety as one workstream among many.

The challenge: these CAFM platforms don't natively integrate with Hassantuk. Fire safety as a workstream within CAFM is treated generically — same as HVAC, plumbing, electrical. The UAE-specific Hassantuk telemetry layer requires custom integration.

For most FM companies, the right answer is to keep Concept Evolution or Maximo for the broader CAFM workflow and add the Hassantuk integration layer via custom build — the platforms exchanging fire safety job data, telemetry events, and AMC compliance status. The decision is made during discovery based on existing tooling and Hassantuk-connected site count.

Here's where the platform typically sits in a wider stack.

Field service and dispatch platforms — we sit alongside or replace platforms like Simpro, ServiceTitan, Loc8, and Fieldpoint depending on what's already working.

Fire-specific tools — we integrate with or replace Inspect Point, BuildingReports, ServiceTrade, and Uptick.

CAFM platforms — we sit alongside Concept Evolution, IBM Maximo, and Planon, adding the fire-specific layer they don't natively cover.

Mandatory UAE government channels — we interface with DCD e-services, Hassantuk, ADCDA portal, and Sharjah Civil Defence Aman platform as required.

Integration approach is scoped during discovery. We don't ask you to rip and replace anything that works.

Discovery takes three to four weeks (slightly longer than typical due to Hassantuk API access scoping). Working with your operations leadership, fire safety operations team, and (if applicable) approved installer relationship managers, we map your portfolio composition — Hassantuk-connected site count, AMC contractor status, approved installer relationships, current visibility tooling. Output is a detailed report covering: current-state map, recommended platform architecture, Hassantuk API access strategy, integration scope, phased implementation plan, and fixed-price build proposal.

Build for a core Hassantuk integration platform (telemetry aggregation, proactive maintenance routing, client portal, false-alarm pattern analysis, AMC alignment) takes twelve to sixteen weeks from discovery completion. API access negotiation with Hassantuk approved installers (where applicable) and CAFM platform integration may extend by 3-5 weeks.

We don't publish a price bracket because what's useful varies massively — an FM operator with 50 Hassantuk-connected sites needs something fundamentally different from an approved installer managing 5,000+ installations. Discovery produces a fixed-price proposal with no obligation to proceed.