Home / Case Studies / Résidence Aïcha 2

Case Study · Infrastructure Blueprint

Intelligence built into Résidence Aïcha 2 before the concrete cured

Immobilière de l'Archipel asked the right question early: instead of retrofitting smarts later, what if the open automation layer was designed into the building from day one? We drew the blueprint.

Sector Residential development Region Tunisia Service Infrastructure Blueprint (P3) Stage New build, design phase

Most building intelligence work is rescue work. Systems are already installed, already incompatible, already fighting each other, and someone calls us to make them readable after the fact. Résidence Aïcha 2 was different. Immobilière de l'Archipel, a Tunisian real-estate developer, came to us while the project was still on the drawing board. Their question was the right one: why inherit a fragmented building when you can design an open one?

That is exactly what our Infrastructure Blueprint engagement is for. Where the Data Auditor unifies systems that already exist, the Blueprint defines the automation layer from scratch, before a single controller is specified. The goal was a residential development that ships with one readable, vendor-neutral data layer baked in, not bolted on years later at three times the cost.

A clean slate is only an advantage if you design it deliberately. Otherwise it is just the place where lock-in is quietly born.

The challenge

New construction looks like freedom. It is where lock-in begins.

Each trade arrives with its own proprietary kit and its own closed protocol. The HVAC contractor, the access-control vendor, the metering supplier. Specify them one by one and you end up exactly where every retrofit starts: five vendors, five islands, nothing talking to each other. The developer would own the building but not its data.

What Archipel wanted instead

  • Heating, ventilation, access, lighting and metering reporting into one common layer, not five vendor dashboards.
  • Open protocols specified in the tender, so no supplier could trap the building behind a closed gateway.
  • A handover-ready map of every data point, owned by the developer and the residents association, not an integrator.
  • A foundation ready for later AI optimization, without a rebuild, the day the building is occupied.

The approach

From architecture drawings to an open automation layer

None of this happens by accident. It has to be written into the specification before procurement starts. That is the work.

STEP 01

Map the intent

We worked from the architectural and MEP drawings to list every system the building would need and every data point worth capturing, from boiler flow temperatures to door-access events and per-unit energy meters.

STEP 02

Specify open by default

We translated that intent into vendor-neutral procurement language. Open protocols, standard interfaces and an on-premises integration point became hard requirements in the tender, not nice-to-haves.

STEP 03

Design the data layer

We defined the single readable layer all systems report into, with a naming convention and topology that stay legible whether the building runs three vendors today or six in ten years.

STEP 04

Hand over the map

The engagement closes with the Documented Data Map: the complete, vendor-neutral record of points, protocols and integration logic. The developer owns it outright.

STEP 05

Leave the AI door open

The layer is structured so AI Optimization can be subscribed later as pure software, with benchmarking and forecasting, without re-wiring anything physical.

STEP 06

Stay hardware-light

No proprietary boxes on the developer's balance sheet. The intelligence lives in software and specification, which is where German engineering rigor pays off long after move-in.

The deliverable

What the developer walks away with

Not a slide deck. A procurement-ready specification and a living map that survives the construction phase, the handover, and every contractor who touches the building afterwards. Because the openness is written into the tender, it is enforceable. Suppliers either meet the open-protocol requirement or they do not win the work. The building stays the developer's asset, in every sense.

Included in the Blueprint

  • The Documented Data Map for the full development
  • Vendor-neutral, open-protocol tender language
  • On-premises integration point, no cloud dependency
  • Naming and topology standard for every data point
  • AI-optimization-ready data structure
  • No proprietary hardware lock-in

The outcome

Designed open, indicative early figures

0

Readable layer specified across all building systems

0

Vendor-neutral, no proprietary lock-in

0

Indicative lifecycle energy headroom designed in

The figures are indicative and reflect the design intent of an open, monitored building of this type rather than a settled meter reading. What is concrete is the structure: Résidence Aïcha 2 enters construction with one common data layer specified, open protocols mandated in procurement, and a Documented Data Map that the developer owns from the first day of operation. The harder result is the one that does not show on a chart. The developer never has to pay to undo a fragmented building, because the fragmentation was never allowed to happen.

We did not want to discover, two years after handover, that our own building was locked to a supplier we had stopped trusting. Specifying the open layer up front cost us a fraction of what an audit would have, and the asset stays ours.

Immobilière de l'Archipel
Immobilière de l'Archipel
Development lead, Résidence Aïcha 2

More work

Related projects and reading

Planning a new build or a deep retrofit?

Bring us in at the drawing board. We will design the open automation layer into your project before procurement locks anything in.

العربية