Articles

The Missing Layer

FM Data Literacy as a Prerequisite for AI Success 

Part 1 of this series made the case that data quality is the structural barrier limiting AI adoption in facilities management. Clean, well-integrated, standards-compliant data is a prerequisite for AI systems to function reliably. But solving the data problem creates a second, equally important question: even when the data is ready, who is equipped to use what it produces?

The answer, according to emerging research from the International Facility Management Association (IFMA), is: not yet enough people. And the gap is growing wider faster than the profession is closing it.

The Rise of the FM Analyst

IFMA’s research report The Rise of the FM Analyst documents a fundamental shift in what facility management roles require. FM teams are building new data fluency capabilities in response to the analytical demands of modern building operations. Three competency areas are identified as most urgently needed: analytics proficiency, data governance literacy, and cross-stakeholder communication of data-driven insights.

From these demands, a new role archetype is emerging - the FM Analyst. This is a professional positioned at the intersection of building operations and data interpretation: someone who can extract meaning from the sensor streams, work order histories, occupancy patterns, and energy consumption data that modern buildings generate continuously, and translate that meaning into decisions that operators and executives can act on.

The emergence of the FM Analyst role reflects a structural recognition that AI tools and data platforms do not generate value autonomously. They require human judgment to function as intended - judgment that must be grounded in data literacy to be reliable.

What Data Literacy Means - and Does Not Mean

Data literacy is not the same as data science. The distinction matters practically and professionally. Data science involves building models, writing algorithms, and architecting analytical infrastructure. Data literacy involves reading outputs, asking the right questions of data systems, recognizing anomalous results, and translating findings into operational decisions.

Consider a predictive maintenance dashboard that flags an HVAC unit as high risk of failure within 30 days. A data-literate FM professional can interrogate that output: Is the sensor reading for this model calibrated? Has this unit generated similar alerts that proved to be false positives? Does the maintenance history suggest a pattern that explains this spike, or is something genuinely unusual? Without that layer of professional judgment, the alert is either ignored because it is distrusted or acted on blindly because it carries the authority of a data system.

Think of it as the difference between a pilot who can operate an aircraft and one who can also interpret instrument alerts, cross-reference competing readings, and make sound judgment calls when automated systems conflict. The autopilot handles cruise; the pilot handles the edge cases. AI in FM works the same way: the system handles pattern detection at scale; the FM professional handles the judgment calls that scale cannot replace.

IFMA’s Rethinking Data in FM research reinforces this framing, identifying data-driven decision-making and the capacity to translate analytical outputs into operational action as the defining competency shift for the profession in this decade.

The Widening Skills Gap

IFMA’s 2026 Global FM Trends research and FMJ synthesis both point to a compounding dynamic. As FM roles grow more complex and data-intensive, the profession faces a demographic challenge that amplifies the skills gap: significant retirement attrition is projected over the next decade, and the institutional knowledge leaving with retiring professionals is not being replaced at the rate the profession requires.

The result is a double gap. Technical data skills are insufficient - too few FM professionals have been trained to work with modern analytics platforms, interpret AI-generated outputs critically, or apply data governance principles in practice. Simultaneously, the accumulated operational experience that provides the contextual judgment needed to evaluate data outputs intelligently is attriting faster than it is being built into incoming talent.

This creates organizational fragility. An FM team with strong data infrastructure but weak data literacy will see AI tools produce outputs that nobody fully trusts, leading to either the underuse of expensive systems or an overreliance on their recommendations in contexts where human judgment should override them. Neither outcome serves the building owner, the occupants, or the profession.

The AI-Literacy Loop

There is a circularity problem embedded in the current moment. AI tools are frequently positioned as solutions to FM workforce capacity constraints - they are supposed to reduce the cognitive burden on FM professionals by automating routine analysis and surfacing actionable insights. But AI tools only deliver on that promise when the professionals using them have sufficient data literacy to evaluate whether those insights are sound.

Without data literacy, AI in FM risks reproducing a pattern the industry already knows well: expensive technology that generates outputs nobody can confidently validate, quietly accumulating in dashboards that are checked less and less frequently. The tools do not fail technologically. They fail organizationally because the human layer required to make them useful is absent.

Closing this loop requires treating data literacy not as a credential to add to a job posting but as a core professional competency to be developed systematically - through training programs, certification pathways, role design, and organizational investment in the FM Analyst capability that IFMA’s research identifies as the structural response.

What Leaders and Professional Bodies Should Do

The response to the FM data literacy gap operates at two levels: organizational and professional.

At the organizational level, FM leaders should:

•    Treat data literacy as a core operational competency - not a bonus skill - and reflect that in hiring criteria, role design, and professional development planning.

•    Create or designate FM Analyst roles that formally bridge building operations and data interpretation, rather than expecting existing staff to absorb these responsibilities without structural support.

•    Invest in practical data literacy training tied to the specific platforms and data systems in use - generic analytics training is significantly less effective than training anchored in operational context.

•    Design AI tool deployments to include explicit protocols for human review, flagging, and override - building in the judgment layer rather than assuming it.

At the professional development level, industry bodies have a parallel responsibility:

•    Integrate data fluency modules into existing FM certification pathways - the CFM and SFP credentials administered by IFMA are natural vehicles for embedding data literacy standards alongside traditional FM competencies.

•    Develop case-based learning resources that ground data literacy in building operations contexts, making the connection between data skills and FM practice concrete for practitioners at all career stages.

•    Create peer networks and communities of practice for FM Analysts, providing the professional recognition and knowledge-sharing infrastructure that accelerates competency development across the field.

What’s on the Horizon - Lifecycle Interoperability In 2026–2027

When standards-defined data integration and interoperability spans the building lifecycle (2026–2027)

Commercial real estate (CRE) has spent the last decade investing in digital representations of buildings—models, asset registers, automation systems, analytics platforms—yet too many portfolios still operate like a relay race where each runner drops the baton. Information created during design and construction often arrives in operations incomplete, inconsistent, or trapped inside a tool’s preferred format. The operational team then recreates what already existed, and the cycle repeats at every renovation, tenant change, or capital project.

The next two years show credible signs of a shift. Several major standards and frameworks are evolving to enable information to be specified, validated, exchanged, and reused with less manual translation. The emerging picture is not a single “magic standard” but an interoperable system—more like a modern shipping network where containers, customs rules, tracking codes, and port infrastructure all align to move goods predictably at scale.

The central thesis is straightforward:

Standards-defined lifecycle interoperability becomes real when governance, exchange schemas, machine-checkable requirements, operational handover structures, service-life planning, semantics, and CRE business data models align—so building information can travel across the lifecycle without losing its meaning.

This article synthesizes the current status and 2026–2027 horizon for:

·       ISO 19650 (information management processes)

·       ISO 15686 (service-life planning)

·       ASHRAE 223P (semantic data model for analytics and automation)

·       buildingSMART / ISO Industry Foundation Classes (IFC) (open schema for built assets)

·       buildingSMART Information Delivery Specification (IDS) (machine-readable information requirements and validation)

·       COBie (construction-to-operations building information exchange)

·       OSCRE (real estate industry data model)

The framing is consistent with the Building Lifecycle Management Initiative (BLMI): lifecycle value scales when information stays coherent from planning and delivery into operations, renewal, and portfolio decision-making.

Executive outlook: why 2026–2027 matters

CRE is approaching a convergence window where:

·       ISO 19650 governance language is being modernized so lifecycle information management is less segmented between “project” and “operations.”

·       IFC 4.3 is stable and widely referenced as the openBIM exchange baseline, while IFC 5 development focuses on long-term architecture improvements.

·       IDS is already finalized as a buildingSMART standard and is becoming the practical method for turning requirements into automated quality checks.

·       COBie is being delivered in more modern formats (including JSON and IFC-aligned templates) that support automation beyond spreadsheets.

·       ISO 15686 service-life planning is being refreshed to better support lifecycle strategies.

·       ASHRAE 223P advances semantic interoperability for operational analytics and automation.

·       OSCRE connects building and operational truth to portfolio/business truth (leases, reporting, ESG, capital planning).

The result is a clearer pathway to a standards-defined “digital thread” that CRE organizations can scale across portfolios.

The lifecycle interoperability stack: how the standards fit together

A helpful way to visualize interdependence is to map each standard to a role in a lifecycle information supply chain:

·       ISO 19650: the governance and process rules (who requests what, when, and how it is managed)

·       IFC (ISO 16739-1): the open schema “container” for built asset information

·       IDS: the machine-readable checklist that validates the required information is actually present

·       COBie: the operational handover manifest—what operators need to run and maintain the asset

·       ISO 15686: the service-life compass for maintenance and replacement planning

·       ASHRAE 223P: the semantic layer that makes operational data consistently meaningful

·       OSCRE: the business-domain model that links asset and operations data to CRE workflows and reporting

If any one layer is missing, organizations fall back to manual interpretation, custom mapping, and costly rework.

ISO 19650: lifecycle information governance that turns “data” into a deliverable

Current status ISO 19650 is widely adopted as the international foundation for managing information across the lifecycle of built assets, including defining information requirements, exchange points, roles, responsibilities, and common data environment expectations.

2026–2027 horizon ISO 19650 Parts 1–3 are in revision, including development-stage drafts (DIS/CD) that reflect ongoing modernization.

Why it matters: For CRE, ISO 19650 is the difference between “hoping” information arrives and making information delivery enforceable. Without governance, a portfolio’s information behaves like an unlabeled set of moving boxes: items may exist somewhere, but no one can reliably find the right box, confirm what’s inside, or trust it’s complete.

With the ISO 19650 discipline, owners and operators can define Owner/Asset/Exchange Information Requirements in a way that procurement teams can contract, project teams can deliver, and acceptance teams can audit. In practical terms, it supports fewer disputes at handover, clearer accountability, and more consistent lifecycle continuity—especially when combined with IDS for machine validation.

IFC (ISO 16739-1): the open schema that keeps building data portable

Current status: IFC is the principal open, vendor-neutral schema for representing built assets and infrastructure works over their lifecycle. buildingSMART identifies IFC 4.3.2.0 (IFC 4.3) as the latest official release, also published as ISO 16739-1.

2026–2027 horizon IFC 4.3 remains the practical baseline for exchange, while IFC 5 development focuses on longer-term architecture improvements. For CRE stakeholders, the near-term story is stability and improved interoperability through consistent implementation and certification—not constant schema churn.

Why it matters: CRE portfolios rarely live within a single software ecosystem. A building’s digital life touches architects, engineers, contractors, commissioning agents, FM teams, CAFM/CMMS/EAM platforms, analytics vendors, and capital planning tools—often across decades. IFC functions like a standardized shipping container: it does not guarantee that the contents are perfect, but it makes it far more likely that the contents can be moved and reused without being rebuilt from scratch.

When IFC is used consistently, owners gain leverage. Data exchange becomes less dependent on a vendor relationship and more dependent on compliance with a shared, open structure.

IDS: turning information requirements into automated quality control

Current status Information Delivery Specification (IDS) is a buildingSMART standard that defines information requirements in a computer-interpretable form and supports automated compliance checking of IFC models.

2026–2027 horizon: IDS is expected to mature through enhanced tooling, broader procurement adoption, and iterative refinements as the ecosystem evolves.

Why it matters: IDS is the missing “inspection mechanism” that CRE has long needed. Many owner requirements exist as narrative documents and spreadsheets—useful for humans, but inconsistent for software and hard to enforce. IDS converts the requirements into a form that can be checked, much like a barcode scanner validates a shipment.

That changes the economics of handover and model quality. Instead of discovering missing asset tags, classifications, or properties at the end—when fixes are expensive—IDS supports earlier detection and correction. It also reduces the burden on FM teams, who otherwise inherit the cost of incomplete information.

COBie: the handover manifest—modernizing how operations get what they need

Current status: COBie (Construction to Building Operations information exchange) is a structured dataset intended to support O&M handover: asset registers, spaces, systems, warranties, maintenance information, and more. It is commonly delivered in spreadsheet form, but NBIMS-US v4 resources include modern templates such as JSON schema and IFC schema representations.

2026–2027 horizon: The practical direction is modernization: COBie outcomes delivered in more automation-friendly formats and better alignment with model-based exchange.

Why it matters: Operations teams do not manage “models”—they manage assets. COBie is valuable because it focuses on the minimum viable dataset needed to run the building on day one. The relatable reality for CRE is that handover is often a messy kitchen move-in: the appliances arrive, but the manuals, warranty cards, and service schedules are scattered across boxes.

Modern COBie delivery formats support a shift from “spreadsheet as final product” to “structured data as a reusable asset.” When integrated with IFC and validated via IDS, COBie becomes less of a painful one-time deliverable and more of a repeatable lifecycle baseline.

ISO 15686: service-life planning as a portfolio maintenance compass

Current status ISO 15686 provides methods and structure for service-life planning, supporting long-term performance, maintenance, replacement, and lifecycle cost strategies.

2026–2027 horizon The series is undergoing modernization, including development of ISO/DIS 15686-1.2.

Why it matters: CRE value is won or lost over decades, not at substantial completion. Service-life planning is what turns asset data into a capital strategy. Without it, portfolios behave as cars run without a maintenance schedule: things still work—until they fail at the least convenient time.

ISO 15686 becomes far more powerful when paired with interoperability for lifecycle data. If service-life assumptions can be captured at handover (COBie/IFC), validated as complete (IDS), governed over time (ISO 19650), and linked to portfolio planning systems (OSCRE), then capital planning shifts from reactive to predictive.

ASHRAE 223P: semantics that let operational analytics scale across buildings

Current status: ASHRAE Proposed Standard 223P aims to define interoperable, machine-readable semantic models representing building system information for analytics, automation, and control.

2026–2027 horizon: The work is positioned toward publication in the 223-202x timeframe and is advancing through formal standards development processes.

Why it matters: A portfolio can have excellent BIM and handover data and still struggle to scale analytics—because operational data often lacks consistent meaning. One building’s “SAT” might be another building’s “SupplyTemp,” with different units, relationships, and contexts. That forces organizations to rebuild integrations, building by building.

ASHRAE 223P matters because it targets the “meaning layer.” It helps software understand not only that a point exists, but what it represents and how it relates to equipment and system topology. The relatable outcome is that analytics become more like a reusable app store—deployable across many buildings—rather than like custom cabinetry built separately for every project.

OSCRE: connecting building and operations data to CRE business outcomes

Current status: OSCRE provides a comprehensive Industry Data Model (IDM) to support standardized data exchange across real estate use cases.

2026–2027 horizon OSCRE’s continued development and adoption trajectories are increasingly relevant as CRE teams align operational building data with portfolio reporting, ESG metrics, and enterprise systems.

Why it matters: Interoperability fails if it stops at the mechanical room. CRE leaders ultimately need to build facts to connect to business decisions: lease obligations, tenant experience, operating expenses, procurement, capital planning, risk, and sustainability reporting.

OSCRE serves as the “accounting chart of accounts” for real estate data—providing structured definitions so the organization is not constantly translating between operational and portfolio systems. When OSCRE is used alongside building data standards, the portfolio can stop treating building information as a technical side project and start treating it as a core operating asset.

Where the gears mesh: how lifecycle interoperability becomes achievable

Interoperability becomes practical when these standards are used together:

·       ISO 19650 defines the lifecycle information management process.

·       Owners express requirements that can be formalized as IDS.

·       Project teams deliver IFC-based exchanges.

·       IDS validates the delivery automatically.

·       COBie captures operations-ready baseline data.

·       ISO 15686 informs service-life planning and long-term strategy.

·       ASHRAE 223P makes operational telemetry consistently meaningful.

·       OSCRE connects technical truths to portfolio truths.

In an analogy: ISO 19650 is the “rules of shipping,” IFC is the standardized container, IDS is the scanner that confirms the shipment meets contract, COBie is the packing slip operators rely on, ISO 15686 is the long-term maintenance schedule, 223P is the shared language for sensor meaning, and OSCRE is the enterprise ledger where real estate decisions get made.

Click the image to view the interactive infographic

When CRE will feel it: four visible shifts in 2026–2027

From policy to proof: enforceable information requirements

As ISO 19650 revisions progress and IDS adoption expands, owners can increasingly specify requirements in a way that can be automatically verified. This is the transition from “requirements as interpretation” to “requirements as measurable acceptance.”

From handover scramble to operations-ready baselines

With modern COBie delivery formats and better alignment with model-based data, handover becomes less of a frantic end-of-project event and more of a repeatable data product that feeds CMMS/EAM systems cleanly.

From points to performance: semantic operations at scale

As semantic approaches mature, analytics and automation deployments can become repeatable across buildings. The integration burden drops, and portfolio-wide optimization becomes more feasible without bespoke engineering in every building.

From building data to portfolio decisions: aligning technical truth with business truth

With OSCRE and related enterprise models, the industry gains a clearer path to connecting asset/ops data to the systems that govern value: finance, leasing, ESG reporting, and portfolio planning.

Where CRE professionals should build awareness and knowledge

·       Owner-side information requirements (OIR/AIR/EIR literacy): The skill to define what data is needed, not only what documents are needed.

·       IFC + IDS paired capability: Exchange without validation is fragile; validation without exchange is isolated. CRE teams should understand how they work together in procurement and acceptance.

·       Handover modernization: Move beyond “spreadsheet compliance” toward structured, system-ready datasets.

·       Service-life planning as a data discipline: Connect ISO 15686 thinking to digital asset records so capital planning is data-driven and defensible.

·       Operational semantics readiness: Prepare for semantic standards by building internal awareness of point meaning, topology, and system relationships.

·       Enterprise integration: Align building and operational data initiatives with OSCRE-style business models to reduce translation between technical and financial realities.

Closing: the horizon is convergence—governance + schema + validation + semantics + business context

The building industry is moving toward a practical tipping point. Governance (ISO 19650), open schema (IFC), computable requirements (IDS), operational handover structure (COBie), service-life planning (ISO 15686), operational semantics (ASHRAE 223P), and CRE business-domain modeling (OSCRE) are increasingly complementary.

Together they point to a future where lifecycle interoperability is less about custom integrations and more about predictable, standards-defined connections—like the internet, where shared protocols make exchange reliable even when systems differ.

For CRE professionals, the horizon is not merely new standards documents. It is a path toward buildings and portfolios that preserve their digital memory—so every lifecycle decision starts with trusted information rather than costly rediscovery.

Sources