A technology checklist for the next stage.

Require IFC 4.3 deliverables with model-view and property validation

Open exchange of BIM lifecycle data across authoring and FM tools

Limit · Valid IFC may still omit operational properties or lose relationships

Attach IDS to every design procurement construction and handover gate

Machine-readable information requirements and automated IFC validation

Limit · Validates declared model content not physical truth; poor requirements remain valid

Make issues first-class records linked to IFC GUIDs and evidence

Portable model issue and clash coordination without proprietary model files

Limit · Issue layer is not full document/change control; test API versus file support

Use URIs and versioned API mappings plus JCX Bangladesh extension

Stable multilingual classes properties values and relations for built environment terms

Limit · Content/API versions change; cache terms and never rely on unversioned identifier URLs

Require API export/import and document/issue archive from CDE vendors

Cross-platform document issue and data-environment exchange

Limit · Vendor CDE may claim compatibility without full round-trip semantics

Create OIR AIR PIR EIR BEP CDE status and responsibility matrix

Defines information requirements roles workflows approvals status and security across asset lifecycle

Limit · Certification can become paperwork unless linked to decisions and tests

Classify and restrict security drawings tenant data and critical-system information

Sensitivity triage and security-minded management of sensitive information

Limit · Does not replace ISO 27001/OT controls or local law

Run a JCX dictionary commission with definitions units mappings and versions

Rules roles and governance for properties in interconnected data dictionaries

Limit · Defines method not content; governance effort remains with JCX

Template equipment products spaces handover and environmental data

Machine-interpretable object data templates across asset lifecycle

Limit · Templates require actual domain content and product data adoption

Map leases units parties investments procurement and portfolio data to OSCRE

Common enterprise real-estate investment occupier lease vocabulary and schemas

Limit · Do not force enterprise model into IFC geometry; access and version terms apply

Connect asset condition risk lifecycle cost service level and sustainability to decisions

Value-aligned lifecycle asset-management vocabulary principles outcomes and maturity

Limit · Framework does not itself provide a software schema

Use as governance target for lifecycle maintenance and capital planning

Requirements for an asset-management system and continual improvement

Limit · Certification costs and process overhead; not a digital-twin model

Link work orders services SLAs occupants and asset outcomes

FM management-system requirements and service alignment

Limit · Management system not a point/telemetry ontology

Evaluate as canonical operations graph for cross-building analytics

Semantic graph of building assets systems spaces equipment points and relationships

Limit · Modeling effort and ontology crosswalks required; not enterprise lease/BIM model

Ingest Haystack and normalize to JCX with tag/profile validation

Pragmatic tags file types ontology and HTTP API for building IoT data

Limit · Tag ambiguity and vendor profiles can impair automated reasoning

Use as candidate crosswalk between property and operations concepts

Modular ontology for property ownership inhabitants technical systems sensors and events

Limit · Pin version and test implementations; avoid mixing REC versions

Use as a projection with neutral JSON-LD/JSON Schema/RDF export

JSON-LD model language for twin interfaces properties components and relations

Limit · Cloud/runtime lock-in and version migration; not neutral property system

Require BACnet/IP or BACnet/SC gateway and BTL evidence where practical

Vendor-independent building automation communication for HVAC lighting access elevators security and fire

Limit · Protocol interoperability does not guarantee semantic point mapping or cyber safety

Use segmented read-only gateway and persist register maps scaling units and quality

Simple device/register communication and TLS/X509 security option

Limit · No native semantics; legacy serial and unsafe internet exposure are risks

Use selectively for resident devices with commissioning and offboarding

IPv6 application-layer interoperability for smart-home devices

Limit · Version/device-category support and consumer lifecycle; not HVAC/fire/elevator standard

Use for spatial search/query and partner exchange preserving CRS

Feature-level REST/OpenAPI access to parcels buildings roads permits and amenities

Limit · Core read scope and implementation parts differ; test CRS/filter/write behavior

Expose interoperable sensor observations when useful and preserve quality/time

Unified geospatial Web API for sensor observations metadata and tasking

Limit · High-volume time series and control authorization need separate architecture

Link district context and parcels to IFC building/project IDs

3D city-model exchange for planning BIM navigation disaster energy and urban twins

Limit · 3D geometry complexity and version/encoding conversion can lose semantics

Store activity data factor source period boundary estimation and assurance

Boundaries and categories for corporate/value-chain GHG inventories

Limit · Scope boundary choices can double count; not a property data model

Link BIM quantities EPDs procurement operations maintenance and end-of-life

Consistent embodied operational and user carbon assessment and deviation reporting

Limit · Area basis boundaries factors and deviations must be aligned before comparing

Version pathway factors occupancy area and assumptions in every result

Country/property pathways for energy/carbon intensity and misalignment year

Limit · Pathways update; primarily operational/in-use and not embodied carbon

Store raw evidence and project GRESB as reporting projection

Investor-driven benchmark for management performance development and sustainability evidence

Limit · Score is not canonical data or proof of technical performance; weights evolve

Store certificate scheme version scope date evidence and expiry

External certification of digital connectivity and smart-building capability

Limit · Certification not network topology, data quality or cyber assurance

Connect environmental objectives evidence corrective actions and operational data

Environmental management system and continual improvement

Limit · EMS certification is not a carbon calculation or building-performance guarantee

Use for corporate/CDE/cloud supplier controls and audit evidence

Confidentiality integrity availability risk management and ISMS controls

Limit · Certification does not guarantee OT safety or correct implementation

Create current/target profiles for IT CDE BMS/OT and vendors

Govern Identify Protect Detect Respond Recover governance and risk profiles

Limit · Framework is outcome-oriented; map controls to actual implementation

Use for BMS/PLC gateway segmentation and vendor responsibilities

OT zones systems components and supplier security requirements

Limit · Choose exact parts and security levels; do not claim compliance generically

Create AI inventory risk classification impact assessment logs and human oversight

Organization-wide AI policies risk transparency accountability and continual improvement

Limit · Management certification is not model accuracy or fairness proof

Use for tenant screening maintenance analytics worker/camera and GenAI release gates

Voluntary trustworthy AI risk management across design/deploy/use/evaluation

Limit · Current framework revision means pin version and record mappings

Use as a high-bar reference for EU customers/data and sensitive decisions

Risk-based legal obligations for AI placed on/used in EU market

Limit · Legal applicability is fact-specific; obtain counsel and track implementing rules

Minimize identity data separate marketing/tenant/visitor/CCTV and define retention/access

National privacy/data-protection obligations and rights

Limit · Legal status and implementing rules can change; do not treat summary as legal advice

Use data inventory provenance classification stewardship and interoperable exports

National data governance interoperability lifecycle transparency and accountability

Limit · Confirm applicability/authority and amendments before implementation

Support Unicode Bangla/English OGC GIS and practical DB/API exports

Guidance for data architecture Unicode DBMS GIS GML catalogue and KML

Limit · Public-sector requirements may not map directly to private developer; verify latest edition

Attach source document hash extraction method reviewer and supersession to every claim/measure

Interoperable model for entities activities agents and derivation of data

Limit · Provenance does not prove truth; capture evidence and validation separately