What can IT-Label learn from HIB 3.0?

The Dutch Central Government Real Estate Agency works with an extensive technical guideline for the digital infrastructure of its buildings: the Handbook for ICT Housing and Cabling, in the version known as HIB 3.0. The document describes how ICT rooms, cabling, connection points, redundancy and management should be designed and realised in government buildings. It is written for technicians and project managers, not for investors or brokers.

Still, HIB 3.0 is interesting for anyone involved in the digital quality of real estate. Not because commercial property should meet the same level as a government office, but because the handbook illustrates a principle: digital infrastructure can be designed, standardised, documented and future-proofed in advance. That is exactly the kind of thinking that is often missing in the commercial market.

The central question of this article is therefore not whether IT-Label can replace HIB 3.0. It cannot, and that is not the intention either. The question is: what can an IT-Label audit learn from the way HIB 3.0 looks at infrastructure, and how do you translate that knowledge into a delivery level that an owner, tenant or advisor understands immediately?

What HIB 3.0 does and does not cover

HIB 3.0 focuses on the passive, building-bound digital infrastructure. Think of the requirements for ICT rooms and ICT cabinets, copper and fibre-optic cabling, connection points and patch facilities, the electrical provisions and climate conditions an ICT room needs, and physical security. Topics such as Power over Ethernet, coding and labelling, documentation and scalability are also addressed.

What matters is what does not automatically fall within scope. HIB 3.0 covers housing and cabling, not the active ICT equipment an organisation installs itself, nor full-scale data centres. This distinction between the fixed base in the building and the equipment and services of the user is essential, and it recurs in nearly every conversation about who is responsible for IT investments in a space.

Anyone reading HIB 3.0 will notice how systematically responsibilities and boundaries are recorded. That makes the handbook not just a collection of technical requirements, but also an example of how to organise scope and transferability. That last point in particular is valuable for an audit that ultimately needs to be readable for a broad audience.

From technical requirement to audit point

The temptation is great to shorten the hundreds of requirements in HIB 3.0 into a checklist and simply tick them off during an inspection. That would be a mistake. The result would be a technical exam that a tenant or investor cannot read. The task for an IT-Label audit is different: recognise relevant principles, check them, and then translate them back into understandable language.

A useful approach is to ask three questions for each relevant component. What is technically relevant and why? What can an auditor objectively establish during a building inspection? And what does that ultimately mean for the user? Two examples make this concrete.

• Fibre-optic backbone and redundant routes. Technically, this concerns the number of connections and their physical separation. The auditor can check how many connections are present, how they enter the building and what expansion space is available. For the user, this translates into: how dependent am I on a single connection, and what happens in the event of a fault?
• Structured data cabling. Technically, this revolves around category, age, connection points and patch facilities. The auditor assesses type, condition, coverage and documentation. For the user, this becomes: can I connect my workstations immediately, or do I first need to invest in new cabling?

That common thread, from technical requirement to audit point to delivery level to meaning for the user, is where the translation happens. It is also what distinguishes IT-Label from a technical standard: not inventing new requirements, but making existing technology readable.

A user does not want to read a handbook of hundreds of requirements. They want to know what the building can handle digitally and what that costs.

A possible audit matrix

To make the principles from HIB 3.0 workable, an audit can group relevant checkpoints into categories. What follows below is a proposal for further development, not an established methodology. The goal is structure, not completeness.

Connectivity and internal infrastructure

The first question is what enters the building: fibre optics, other fixed connections, the number of available providers, capacity and the physical entry points. The second question is how data is subsequently carried through the building and the rented space, via backbone, copper and fibre-optic cabling, patch facilities and connection points. In both cases, what matters is not only what is present, but also the technical condition and the room for expansion.

ICT rooms, redundancy and smart readiness

ICT rooms require attention to location, accessibility, physical security, available space, power supply and climate. Redundancy and continuity revolve around dual connections, separated routes and identifying single points of failure, a topic we covered extensively earlier in redundancy explained. For smart readiness, one distinction is crucial: can the infrastructure support sensors, access control, PoE and building management systems, or is the application actually present? These are two different things.

Documentation and management

This component deserves extra attention. As-built drawings, cable registration, labelling, maintenance documentation and recorded responsibilities determine whether infrastructure is transferable. A technically excellent installation that is documented nowhere can still be a black box for a new user. HIB 3.0 shows how seriously professional parties take this, and that is a lesson commercial real estate can benefit from.

From hundreds of requirements to a few understandable performances

To keep the audit readable, technical checkpoints can be brought together under a limited number of performance categories. This too is a possible direction, to be critically tested against both HIB 3.0 and the existing IT-Label methodology, and is not presented as a definitive new methodology.

• CONNECT. How well is the building connected externally?
• DISTRIBUTE. How well can data be distributed internally?
• CONTINUE. How robust and redundant is the infrastructure?
• SECURE. What physical and digital security provisions are present?
• SCALE. How easily can the infrastructure grow along with demand?
• SMART. To what extent is the building prepared for smart-building technology?
• MANAGE. How well are infrastructure, documentation and responsibilities organised?

The advantage of such performance categories is that they bridge the technical depth of HIB 3.0 and the simplicity a real estate professional needs. They translate dozens of checkpoints into a handful of questions everyone can follow.

The translation table

The following table shows how a technical world, an audit point and a real estate translation come together. Each row ends with the question the user actually asks.

From audit to classification

The outcomes of an audit can ultimately contribute to the existing classifications. Importantly: an IT1+ PREMIUM does not simply mean that a building meets all HIB 3.0 requirements. IT-Label assesses a different question, namely the actual digital delivery level for the user. Broadly, this can be outlined as follows.

• IT1+ PREMIUM and IT1 HIGH PERFORMANCE. A very complete, respectively high-quality digital ecosystem, with strong continuity, scalability and manageability. With IT1 HIGH PERFORMANCE, only limited user-specific optimisations are needed.
• IT2 PLUG & PLAY and IT3 READY. A strong foundation that allows a user to become operational quickly, or a situation in which the essential provisions are present but a substantial part of the fit-out still rests with the tenant.
• IT4 CORE and IT5 SHELL. Mainly basic connections present, with the user realising a large part themselves, or a digital shell-and-core situation. We explained what that means in concrete terms in what IT4 CORE or IT5 SHELL means for your building.

This creates a logical and traceable chain: from technical standard to audit, from findings to label, and from label to a delivery level that a user understands.

The demarcation list as the final piece

One of the strongest lessons from professional technical projects is careful demarcation. An audit should ideally not only state what is present, but also provide insight into who is responsible for what. That requires distinguishing between building-bound infrastructure, infrastructure within the leased space, active equipment, services and providers, management, maintenance, upgrades and user-specific IT.

The classification does not automatically determine who is legally or contractually responsible. That is recorded in a demarcation list, which aligns with the agreements between tenant and landlord and with the question of who is responsible for IT in the lease agreement. The label makes the situation transparent; the demarcation list makes the agreements binding.

Your next step

IT-Label does not need to reinvent the technical world. An enormous amount of knowledge already exists on how professional digital infrastructure should be designed, realised and documented, and HIB 3.0 is an interesting example of that. The challenge lies elsewhere: checking, structuring and translating that technology into a language that owner, broker and tenant alike understand.

From technical requirement to audit point, from audit point to delivery level, from delivery level to IT1+ through IT5. Because ultimately, a user does not want to read a handbook of hundreds of requirements. They want one question answered: what can this building handle digitally, and what does that mean for my organisation? If you would like to know how an audit works for your property, read more about how the IT-Label works or get in touch to discuss the possibilities.