# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-08-24T11:11:00Z", "synthesisSha256": "eb84b9b28e267dbc460cba2943f4a9fa372da38cc9223addbbe77df8724a4213", "providerMode": "dual-provider", "providers": [ "Claude", "Grok" ], "waivedProviders": [] }, "metaModel": { "id": "WM-BLT-006", "registryId": "vr.wm-blt-006", "name": "Facility", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.BLT.FAC" ], "tags": [ "facility", "phy.blt.fac" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-blt-006-facility/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-006", "model": { "registry_id": "vr.wm-blt-006", "model_id": "WM-BLT-006", "name": "Facility", "entry_kind": "aggregate", "purpose": "Provide the governed, format-neutral context an agent needs to identify, classify, compose, operate, evidence and hand over a built facility as a managed aggregation of buildings, structures, systems and grounds.", "scope_statement": "A Facility is a bounded, operationally managed built entity that is planned, constructed, operated, maintained and eventually decommissioned as a unit under identified custody, and that aggregates one or more buildings, structures, engineered systems and associated grounds. The model covers the facility as (a) an identifiable real-world entity with registry standing, (b) an aggregation root over contained buildings and systems, and (c) an object of regulatory, financial, security and information governance. It deliberately excludes the internals of contained models (Building, Space, Equipment) and the land-tenure semantics of the containing Site.", "in_scope": [ "Facility identity, naming, reference designation and cross-registry keys", "Functional, occupancy and code classification of the facility as an operating whole", "Geospatial extent, georeference and jurisdictional location of the facility boundary", "Containment by Site and decomposition into facility parts, buildings and structures", "Facility-level engineered systems and linkage to the component asset register", "Lifecycle phase, operational status, milestone events and record versioning", "Condition, service life, deferred maintenance and criticality at facility level", "Ownership, custody, legal interest, operator and facility-management accountability", "Regulatory programme interests, permits, statutory inspections and nonconformities", "Security level, protective posture and information disclosure constraints", "Capacity, occupancy, utilisation and resource performance benchmarking", "Asset information requirements, provenance, retention and standards alignment" ], "out_of_scope": [ "Land parcel tenure, cadastral boundaries and site acquisition (Site model WM-BLT-008)", "Internal building fabric, storeys, structural systems and envelope (Building model WM-BLT-001)", "Room and space geometry, occupancy assignment and wayfinding (Space model)", "Component-level equipment records, serial numbers, warranties and spares (Equipment/Asset-item model)", "Legal-entity attributes of owners, operators and regulators (Organization/Party model)", "The permit or licence instrument itself, including its issuance workflow (Authorization model)", "Postal address normalisation and address-point registry semantics (Address model)", "Work-order execution, labour, scheduling and cost postings (Work Management model)", "Financial valuation, depreciation and capital accounting (Financial Asset model)", "Linear network topology of utilities and transport corridors beyond the facility boundary (Network/Utility model)", "Individual person records, credentials and access-card issuance (Identity/Access model)", "Construction project delivery, contracts and programme management (Project model)" ], "boundary_notes": [ { "neighbor": "Site (WM-BLT-008)", "distinction": "Site is the georeferenced land locus with tenure and parcel semantics; Facility is the operating unit placed on or spanning one or more sites. IFC keeps IfcSite and IfcFacility as distinct spatial structure elements and allows IfcFacility to be aggregated directly to IfcProject when no site information exists, so Site containment is normal but not universal.", "source_refs": [ "SRC-001", "SRC-018" ] }, { "neighbor": "Building (WM-BLT-001)", "distinction": "Facility aggregates buildings and structures; Building holds fabric, storeys and envelope. This inverts the IFC type hierarchy, where IfcBuilding is a subtype of IfcFacility rather than its part. The registry CONTAINS relation is retained as an operational aggregation, and IFC subtyping is recorded as an alignment conflict rather than a conformance claim.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "Space / Room model", "distinction": "Facility stops at facility parts and building membership; interior spatial subdivision (IfcSpace, COBie Space and Zone, CityGML rooms) belongs to the Space model. Facility records only aggregate space counts and area totals.", "source_refs": [ "SRC-002", "SRC-016", "SRC-010" ] }, { "neighbor": "Equipment / Asset-item model", "distinction": "Facility records facility-level systems and a pointer to the asset register with coverage and completeness measures; individual component identity, type data and maintenance history belong to the Equipment model (COBie Type and Component).", "source_refs": [ "SRC-016", "SRC-011" ] }, { "neighbor": "Organization / Party model", "distinction": "Facility references owner, custodian, demand organisation and service provider by identifier and role, with validity dates; it does not model legal-entity registration, corporate hierarchy or contracting capacity.", "source_refs": [ "SRC-012", "SRC-006" ] }, { "neighbor": "Authorization / Permit model", "distinction": "Facility carries regulatory programme interests, programme identifiers and permit references with validity windows; the permit instrument, its conditions text and issuance workflow belong to the Authorization model. EPA FRS models this as environmental interest types linked to a facility Registry ID.", "source_refs": [ "SRC-005", "SRC-004" ] }, { "neighbor": "Address / Location model", "distinction": "Facility holds address references and administrative unit codes needed for reporting and emergency response; address parsing, normalisation and address-point authority belong to the Address model.", "source_refs": [ "SRC-004", "SRC-003" ] }, { "neighbor": "Facility Management service model (ISO 41001)", "distinction": "Facility is the object of management, not the management system. FM policy, objectives, competence and audit of the FM management system belong to a separate management-system model; Facility retains only the accountability links and service scope.", "source_refs": [ "SRC-012" ] } ] }, "sources": [ { "id": "SRC-001", "title": "5.4.3.25 IfcFacility — IFC 4.3.2 Documentation", "organization": "buildingSMART International", "url": "https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcFacility.htm", "version_or_date": "IFC 4.3.2.20260821 (IFC4X3_ADD2) documentation build", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:05:00Z", "relevance": "Normative definition of a built facility as a spatial structure element, its subtypes (IfcBridge, IfcBuilding, IfcMarineFacility, IfcRailway, IfcRoad), CompositionType, and aggregation rules to IfcProject, IfcSite and parent facilities." }, { "id": "SRC-002", "title": "IfcFacilityPart — IFC 4.3.2 Documentation", "organization": "buildingSMART International", "url": "https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcFacilityPart.htm", "version_or_date": "IFC 4.3.2.20260821 (IFC4X3_ADD2) documentation build", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:06:00Z", "relevance": "Normative decomposition of facilities: mandatory UsageType conveying the subdivision convention, optional CompositionType, subtypes and placement/containment rules." }, { "id": "SRC-003", "title": "D2.8.III.2 INSPIRE Data Specification on Buildings — Technical Guidelines", "organization": "European Commission, INSPIRE Maintenance and Implementation Framework", "url": "https://inspire-mif.github.io/technical-guidelines/data/bu/dataspecification_bu.html", "version_or_date": "v3.1.0, 2024-01-31", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:10:00Z", "relevance": "Persistent identifier rules (inspireId, externalReference), lifespan versioning (beginLifespanVersion/endLifespanVersion with time zone), conditionOfConstruction, currentUse, dateOfConstruction/Demolition and the DateOfEvent partial-date pattern." }, { "id": "SRC-004", "title": "Facility Site Identification Data Standard, Standard No. EX000020.2", "organization": "U.S. Environmental Protection Agency / Exchange Network Leadership Council", "url": "https://www.epa.gov/sites/default/files/2015-06/documents/facilitysite-v2a_10012014.pdf", "version_or_date": "Version 2, 2014-10-01", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:14:00Z", "relevance": "Consensus data standard for uniquely identifying a facility of environmental interest across federal, state and tribal systems: facility site identifier, name, location address, geographic coordinates and interest typing." }, { "id": "SRC-005", "title": "FRS Description — Facility Registry Service", "organization": "U.S. Environmental Protection Agency", "url": "https://www.epa.gov/frs/frs-description", "version_or_date": "Accessed 2026-08-24", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:12:00Z", "relevance": "Operating registry that assigns a 12-digit FRS Registry ID, integrates program records from multiple source systems, performs record matching and a weekly best-pick coordinate selection — the reference pattern for facility identity resolution and provenance." }, { "id": "SRC-006", "title": "Federal Real Property Public Data Set", "organization": "U.S. General Services Administration", "url": "https://www.gsa.gov/policy-regulations/policy/real-property-policy-division-overview/asset-management/federal-real-property-profile/federal-real-property-public-data-set", "version_or_date": "FY2024 inventory; page last updated 2025-07-14", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:20:00Z", "relevance": "Statutory real-property inventory reporting under FASTA and FRPC guidance, and the explicit authority to exclude assets from publication for national-security and FOIA-exemption reasons — the basis for disclosure-control findings." }, { "id": "SRC-007", "title": "Federal Real Property Council 2026 Guidance for Real Property Inventory Reporting — FRPP Data Dictionary", "organization": "U.S. General Services Administration / Federal Real Property Council", "url": "https://www.gsa.gov/system/files/FY%202026%20FRPP%20DATA%20DICTIONARY%20(1).pdf", "version_or_date": "FY 2026 edition", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:22:00Z", "relevance": "Normative definition of the data elements and technical requirements for reporting real property assets (unique identifier, asset type, legal interest, status, size, condition, mission dependency, utilisation and disposition) to the FRPP management system." }, { "id": "SRC-008", "title": "General Records Schedule 5.4: Facility, Equipment, Vehicle, Property, and Supply Records", "organization": "U.S. National Archives and Records Administration", "url": "https://www.archives.gov/files/records-mgmt/grs/grs05-4.pdf", "version_or_date": "Transmittal No. 35, May 2024", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:24:00Z", "relevance": "Government-wide disposition authority for facility management, operation and maintenance records: temporary status, destroy when 3 years old or 3 years after superseded, with pre-1921 records offered to NARA before disposition." }, { "id": "SRC-009", "title": "The Risk Management Process for Federal Facilities: An Interagency Security Committee Standard, 2021 Edition", "organization": "Cybersecurity and Infrastructure Security Agency / Interagency Security Committee", "url": "https://www.cisa.gov/sites/default/files/publications/The%20Risk%20Management%20Process%20-%202021%20Edition.pdf", "version_or_date": "2021 Edition", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:26:00Z", "relevance": "Normative determination of Facility Security Level from mission criticality, symbolism, facility population, facility size and threat to tenant agencies, with five levels and associated baseline countermeasures." }, { "id": "SRC-010", "title": "OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/20-010/20-010.html", "version_or_date": "Version 3.0.0, OGC 20-010, approved 2021-09-13", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:30:00Z", "relevance": "Technology-independent semantic model for 3D urban objects with Levels of Detail, space and space-boundary concepts, city object grouping and a versioning module — grounds geometry, LoD and format-neutrality findings." }, { "id": "SRC-011", "title": "ISO 55001:2024 Asset management — Asset management system — Requirements", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/83054.html", "version_or_date": "Second edition, 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:32:00Z", "relevance": "Requirements for asset registers, asset criticality and risk, life-cycle decision-making, information requirements and documented information governing facilities as managed assets." }, { "id": "SRC-012", "title": "ISO 41011:2024 Facility management — Vocabulary", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/82405.html", "version_or_date": "Second edition, February 2024 (ISO/TC 267)", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:34:00Z", "relevance": "Controlled facility-management vocabulary, including the demand-organisation and service-provider distinction used for operator accountability; also the authority for treating 'facility' more broadly than the built-asset scope adopted here." }, { "id": "SRC-013", "title": "ISO 19650-3:2020 Information management using building information modelling — Part 3: Operational phase of the assets", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/75109.html", "version_or_date": "First edition, 2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:36:00Z", "relevance": "Operational-phase information management process: organizational, asset and exchange information requirements, trigger events, the asset information model and information acceptance." }, { "id": "SRC-014", "title": "ISO 81346-12:2018 Structuring principles and reference designations — Part 12: Construction works and building services", "organization": "International Organization for Standardization / International Electrotechnical Commission", "url": "https://www.iso.org/standard/63886.html", "version_or_date": "First edition 2018, confirmed 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:38:00Z", "relevance": "Rules for structuring systems and formulating reference designations for construction works and building services, with object classes and letter codes; explicitly excludes serial/inventory numbers, which bounds its use for identity." }, { "id": "SRC-015", "title": "ISO 15686-1:2011 Buildings and constructed assets — Service life planning — Part 1: General principles and framework", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/45798.html", "version_or_date": "Second edition, 2011", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:40:00Z", "relevance": "Life-cycle framework from initiation, project definition, design, construction, commissioning, operation, maintenance, refurbishment and replacement to deconstruction and disposal; basis for lifecycle phase and service-life findings." }, { "id": "SRC-016", "title": "Construction to Operations Building information exchange (COBie) V3 — NBIMS-US", "organization": "National Institute of Building Sciences", "url": "https://nibs.org/nbims/v3/cobie", "version_or_date": "COBie V3, part of NBIMS-US V4 (2023)", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:44:00Z", "relevance": "Handover data schema with an explicit Facility table plus Level, SpaceType, Space, Zone, Type, Component, System, Resource, Job, Event, Package, Document, Attribute and Risk tables; format-agnostic across spreadsheet, IFC and JSON." }, { "id": "SRC-017", "title": "SAREF4BLDG: an extension of SAREF for the building domain", "organization": "ETSI", "url": "https://saref.etsi.org/saref4bldg/v1.1.2/", "version_or_date": "v1.1.2, published 2020-04-13, last modified 2020-06-05", "source_type": "ontology", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:46:00Z", "relevance": "Standards-body ontology derived from IFC4 Add1 covering Building, BuildingSpace, PhysicalObject, BuildingObject and BuildingDevice; used as an alignment target, not a conformance claim." }, { "id": "SRC-018", "title": "Building Topology Ontology (BOT)", "organization": "W3C Linked Building Data Community Group", "url": "https://w3c-lbd-cg.github.io/bot/", "version_or_date": "v0.3.2 public draft; namespace https://w3id.org/bot#", "source_type": "ontology", "primary_source": true, "authority_tier": 3, "accessed_at": "2026-08-24T09:48:00Z", "relevance": "Minimal topology vocabulary (Zone, Site, Building, Storey, Space, Element; hasBuilding, hasStorey, hasSpace, containsZone, adjacentZone, hasElement). Notably has no Facility class between Site and Building — a documented alignment gap." }, { "id": "SRC-019", "title": "Property Types in Portfolio Manager", "organization": "U.S. Environmental Protection Agency, ENERGY STAR", "url": "https://www.energystar.gov/buildings/benchmark/understand-metrics/property-types", "version_or_date": "Accessed 2026-08-24", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:50:00Z", "relevance": "Operational property typology (18 broad categories, 80+ types) and the property / property-use / gross-floor-area benchmarking model, including multi-building campus properties benchmarked as a parent with child buildings." }, { "id": "SRC-020", "title": "2024 International Building Code, Chapter 3: Occupancy Classification and Use", "organization": "International Code Council", "url": "https://shop.iccsafe.org/media/wysiwyg/material/3000S24-Sample.pdf", "version_or_date": "2024 edition", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:52:00Z", "relevance": "Code occupancy groups A, B, E, F, H, I, M, R, S and U and their subgroups, which drive construction type, egress, fire protection and mixed-occupancy separation for facilities." }, { "id": "SRC-021", "title": "Uniclass — unified classification for the built environment", "organization": "NBS (Hubexo North UK Ltd)", "url": "https://www.thenbs.com/our-tools/uniclass", "version_or_date": "Suite of 12 tables, accessed 2026-08-24", "source_type": "classifier", "primary_source": true, "authority_tier": 3, "accessed_at": "2026-08-24T09:54:00Z", "relevance": "Classification tables including Complexes (Co) and Entities (En), where a complex is a project or estate as a whole and an entity is a constituent part such as a building, bridge or tunnel — a direct classifier for facility-level granularity choices." }, { "id": "SRC-022", "title": "ISO 41011:2024 Facility management — Vocabulary", "organization": "International Organization for Standardization", "url": "https://www.iso.org/obp/ui/en/?_escaped_fragment_=iso:std:82405:en", "version_or_date": "2024-02, Edition 2", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:30:00Z", "relevance": "Normative definition of facility as a collection of assets constructed, installed or established to serve an entity's needs; also demand organization, FM organization, facility service, facility life cycle, service life, facility plan, post-occupancy evaluation, end-of-life and related FM vocabulary." }, { "id": "SRC-023", "title": "ISO 6707-4:2021 Buildings and civil engineering works — Vocabulary — Part 4: Facility management terms", "organization": "International Organization for Standardization", "url": "https://www.iso.org/obp/ui/en/?_escaped_fragment_=iso:std:78714:en", "version_or_date": "2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:05:00Z", "relevance": "Construction-industry vocabulary for facility, facility-in-service, real estate, infrastructure, workplace, security zone and related FM terms complementary to ISO 41011." }, { "id": "SRC-024", "title": "IfcFacility — IFC 4.3.2.0 Documentation", "organization": "buildingSMART International", "url": "https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcFacility.htm", "version_or_date": "IFC 4.3.2.0 (IFC4X3_ADD2), corresponding to ISO 16739-1:2024", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:20:00Z", "relevance": "Open BIM spatial-structure entity for a facility that may be a building, bridge, railway, road or marine facility; composition, placement, containment, GlobalId, OwnerHistory and occupancy, agreement, risk and fire-safety property sets." }, { "id": "SRC-025", "title": "ISO 19650-3:2020 Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) — Information management using building information modelling — Part 3: Operational phase of the assets", "organization": "International Organization for Standardization", "url": "https://www.iso.org/obp/ui/en/?_escaped_fragment_=iso:std:75109:en", "version_or_date": "2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:25:00Z", "relevance": "Operational-phase information management, asset information model, trigger events, PIM-to-AIM handover, transfer of information on ownership change, and the relationship of facility management to asset management." }, { "id": "SRC-026", "title": "HL7 FHIR Release 4 — Resource Location", "organization": "Health Level Seven International", "url": "https://hl7.org/fhir/R4/location.html", "version_or_date": "FHIR v4.0.1", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:28:00Z", "relevance": "Healthcare and service-location identity, status, type, address, WGS84 position, managing organization, part-of hierarchy, hours of operation and the distinction between physical Location and Organization." }, { "id": "SRC-027", "title": "ISO/TR 41013:2017 Facility management — Scope, key concepts and benefits", "organization": "International Organization for Standardization", "url": "https://cdn.standards.iteh.ai/samples/71235/d35885a21e884ceaa03403913bc69d74/ISO-TR-41013-2017.pdf", "version_or_date": "2017-07, First edition", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:12:00Z", "relevance": "Scope of FM and explicit exclusion that a single asset is not a facility and that something not built, such as a nature preserve, is not a facility even if it is an asset." }, { "id": "SRC-028", "title": "2021 International Building Code (IBC) — Section 111.1 Change of occupancy", "organization": "International Code Council", "url": "https://codes.iccsafe.org/s/IBC2021P1/chapter-1-scope-and-administration/IBC2021P1-Ch01-Sec111.1", "version_or_date": "2021 IBC", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T18:22:00Z", "relevance": "Model building-code rule that a building or structure shall not be used or occupied, and that a change of occupancy shall not be made, until the building official has issued a certificate of occupancy." }, { "id": "SRC-029", "title": "IfcSite — IFC 4.3.2.0 Documentation", "organization": "buildingSMART International", "url": "https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcSite.htm", "version_or_date": "IFC 4.3.2.0 (IFC4X3_ADD2)", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:32:00Z", "relevance": "Site as defined land area and optional parent of IfcFacility; WGS84 latitude, longitude and elevation; land title number; postal address; and the spatial hierarchy against which Facility is placed." }, { "id": "SRC-030", "title": "Detailed Facility Report Data Dictionary", "organization": "United States Environmental Protection Agency", "url": "https://echo.epa.gov/help/reports/dfr-data-dictionary", "version_or_date": "ECHO Detailed Facility Report, accessed 2026-08-24", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T18:35:00Z", "relevance": "Operating data elements for a regulated facility: FRS ID, name, address, coordinates and datum, NAICS/SIC, Indian country, program identifiers, compliance status and inactive-facility indication." }, { "id": "SRC-031", "title": "Industry Foundation Classes (IFC) — buildingSMART International", "organization": "buildingSMART International", "url": "https://www.buildingsmart.org/standards/bsi-standards/industry-foundation-classes/", "version_or_date": "IFC 4.3.2.0 / ISO 16739-1:2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:21:00Z", "relevance": "States that IFC 4.3.2.0 is the latest official IFC and is published by ISO as ISO 16739-1:2024 for data sharing in construction and facility management, including infrastructure facilities." } ], "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity and Classification", "description": "What fixes which facility is meant, how it is named and designated, and how it is typed for operational, code and reporting purposes.", "rationale": "Facility data is federated across construction, real-property, regulatory and energy systems, each issuing its own key and its own typology. Identity resolution and classification precedence must be settled before any other context is trustworthy.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-014", "SRC-019", "SRC-020", "SRC-021" ], "layers": [ { "id": "identity-and-naming", "name": "Identity and Naming", "description": "Authoritative keys, cross-registry references, human-readable names and structured reference designations for the facility.", "source_refs": [ "SRC-004", "SRC-005", "SRC-003", "SRC-014" ], "findings": [ { "id": "facility-identifier-set", "name": "Facility identifier set and resolution rules", "description": "The identifiers that pin a facility to a single real-world referent: the master-system key, governed registry identifiers issued by external authorities, and the rules for uniqueness, non-reuse, merge and split. EPA FRS demonstrates the pattern of assigning a registry identifier and then matching incoming program records to it.", "source_refs": [ "SRC-004", "SRC-005", "SRC-003", "SRC-007" ], "questions": [ { "id": "q-master-key", "text": "Which identifier is the authoritative master-system key for this facility, which system issues it, and over what population is it unique?", "kind": "identity", "answer_data": [ "master system name", "identifier value", "issuing authority reference", "uniqueness scope statement" ] }, { "id": "q-external-keys", "text": "Which governed external registry identifiers resolve to this facility, and what is their precedence for cross-system reconciliation?", "kind": "interoperability", "answer_data": [ "external identifier value", "identifier scheme code", "issuing registry reference", "precedence rank" ] }, { "id": "q-nonreuse", "text": "Is the identifier persistent and never reused after the facility is decommissioned, merged into another facility or split?", "kind": "constraint", "answer_data": [ "reuse policy code", "merge or split event reference", "successor identifier", "policy source citation" ] }, { "id": "q-dedup", "text": "What deduplication and match-confidence rule applies when two source systems report what may be the same physical facility?", "kind": "validation", "answer_data": [ "match rule identifier", "match confidence value", "adjudication decision code", "adjudicated by reference" ] } ], "data_elements": [ { "id": "facility-id", "name": "Facility identifier", "description": "Authoritative master-system key for the facility instance.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005" ] }, { "id": "identifier-scheme", "name": "Identifier scheme", "description": "Code naming the scheme that governs the identifier's syntax and issuance.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-004" ] }, { "id": "external-identifier-set", "name": "External identifier set", "description": "Governed identifiers from other registries that denote the same facility, each with scheme, authority and precedence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-003" ] }, { "id": "identifier-assigned-at", "name": "Identifier assigned at", "description": "RFC 3339 timestamp at which the master identifier was assigned.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "identity-match-confidence", "name": "Identity match confidence", "description": "Confidence score for identity resolution when the record was matched rather than directly asserted.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] } ], "artifacts": [ { "id": "facility-identifier-register", "name": "Facility identifier register", "description": "Register of the master key and all cross-registry identifiers with issuing authority, scheme, precedence, assignment time and match evidence.", "media_or_form": [ "structured record set", "tabular register export" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus identifier scheme; register revisions are versioned, not renumbered.", "source_refs": [ "SRC-005", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "facility-naming-and-designation", "name": "Facility naming and structured designation", "description": "Human-readable names, aliases and signage names alongside structured reference designations formed under ISO 81346-12. Names are mutable and non-unique and must never be used as identity, while reference designations encode a position in a functional, product or location aspect structure.", "source_refs": [ "SRC-014", "SRC-001", "SRC-004" ], "questions": [ { "id": "q-preferred-name", "text": "What is the preferred facility name, in which language and script, and which authority may change it?", "kind": "definition", "answer_data": [ "preferred name text", "language tag", "naming authority reference", "effective from date" ] }, { "id": "q-alias-history", "text": "Which alternate, historical, legal and signage names apply, and over what validity periods?", "kind": "temporal", "answer_data": [ "alias name text", "alias role code", "valid from date", "valid to date" ] }, { "id": "q-rds", "text": "What reference designation is assigned to the facility, and in which aspect structure is it expressed?", "kind": "classification", "answer_data": [ "reference designation string", "aspect code", "designation standard reference", "designating organisation" ] }, { "id": "q-name-vs-id", "text": "Where a downstream system keys on name rather than identifier, what compensating control prevents mis-resolution?", "kind": "validation", "answer_data": [ "affected system reference", "control description", "residual risk rating" ] } ], "data_elements": [ { "id": "primary-name", "name": "Primary facility name", "description": "Preferred human-readable name for the facility.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001" ] }, { "id": "name-language", "name": "Name language tag", "description": "BCP 47 style language tag qualifying the name.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "alternate-names", "name": "Alternate names", "description": "Aliases, legal names, trading names and historic names with role and validity window.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "reference-designation", "name": "Reference designation", "description": "Structured designation string formed under ISO 81346-12 rules.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "rds-aspect", "name": "Reference designation aspect", "description": "Aspect (function, product or location) in which the designation is expressed.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-014" ] } ], "artifacts": [ { "id": "naming-and-designation-record", "name": "Naming and designation decision record", "description": "Record of the authoritative name, alias set with validity, the reference designation string and the aspect structure it belongs to, plus the approving authority.", "media_or_form": [ "decision record", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus decision sequence; superseded records retained with end-of-validity timestamps.", "source_refs": [ "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "classification-and-typology", "name": "Classification and Typology", "description": "Functional, industrial and regulatory typing of the facility, including building-code occupancy classification and its consequences.", "source_refs": [ "SRC-019", "SRC-020", "SRC-021", "SRC-001", "SRC-004" ], "findings": [ { "id": "facility-functional-classification", "name": "Functional and reporting classification", "description": "The facility's primary function and any secondary uses, expressed in one or more governed schemes (IFC facility subtype, Uniclass Complexes/Entities, ENERGY STAR property type, industrial activity codes used for regulatory reporting), with an explicit precedence for each downstream purpose.", "source_refs": [ "SRC-001", "SRC-019", "SRC-021", "SRC-004" ], "questions": [ { "id": "q-primary-function", "text": "What is the facility's primary function code, in which classification scheme and version, and as of what date?", "kind": "classification", "answer_data": [ "function code", "scheme identifier", "scheme version", "effective from date" ] }, { "id": "q-mixed-use", "text": "Which secondary uses coexist at this facility and what share of floor area or activity does each represent?", "kind": "composition", "answer_data": [ "secondary use code", "share value", "share basis code", "measured as of date" ] }, { "id": "q-scheme-precedence", "text": "Which classification is authoritative for regulatory reporting, and which is authoritative for benchmarking and portfolio analysis?", "kind": "authority", "answer_data": [ "purpose code", "authoritative scheme identifier", "governing rule reference" ] }, { "id": "q-reclassification", "text": "What change of use triggers reclassification, and what revaluation, permitting or benchmarking consequences follow?", "kind": "lifecycle", "answer_data": [ "trigger condition text", "downstream process reference", "notification obligation" ] } ], "data_elements": [ { "id": "primary-function-code", "name": "Primary function code", "description": "Code for the facility's dominant function within a named scheme.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-019", "SRC-021" ] }, { "id": "classification-scheme", "name": "Classification scheme and version", "description": "Identifier and version of the scheme in which a function code is expressed.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-021" ] }, { "id": "secondary-use-set", "name": "Secondary use set", "description": "Additional concurrent uses with apportionment shares.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-019" ] }, { "id": "ifc-facility-type", "name": "IFC facility type", "description": "IFC 4.3 facility subtype or predefined type applicable to the facility.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "classification-effective-from", "name": "Classification effective from", "description": "Date from which the classification assignment holds in the real world.", "value_kind": "date", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "classification-crosswalk-table", "name": "Facility classification crosswalk table", "description": "Table binding the facility to codes in each adopted scheme, with scheme version, precedence per purpose, mapping confidence and unmapped residue.", "media_or_form": [ "crosswalk table", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus scheme identifier and scheme version.", "source_refs": [ "SRC-021", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "occupancy-and-code-classification", "name": "Building-code occupancy and hazard classification", "description": "The regulatory occupancy groups assigned under the applicable building code edition, construction type, mixed-occupancy treatment and the highest hazard class present. This classification is legally consequential and is asserted by an authority having jurisdiction, unlike operational typologies.", "source_refs": [ "SRC-020", "SRC-001" ], "questions": [ { "id": "q-occupancy-group", "text": "Which code occupancy group or groups apply, under which code edition adopted by which jurisdiction?", "kind": "classification", "answer_data": [ "occupancy group code", "code edition text", "adopting jurisdiction reference", "determination date" ] }, { "id": "q-mixed-occupancy", "text": "Where multiple occupancies coexist, is the facility treated as separated, non-separated or accessory, and where are the separation boundaries?", "kind": "constraint", "answer_data": [ "mixed occupancy approach code", "separation rating", "boundary location reference" ] }, { "id": "q-hazard-class", "text": "What is the highest hazard classification present, and which stored or processed materials drive it?", "kind": "classification", "answer_data": [ "hazard group code", "material class", "quantity threshold basis" ] }, { "id": "q-ahj", "text": "Which authority having jurisdiction issued the occupancy determination and what evidence records it?", "kind": "authority", "answer_data": [ "authority reference", "determination document reference", "issue date" ] } ], "data_elements": [ { "id": "occupancy-group", "name": "Occupancy group", "description": "Code occupancy group or groups assigned to the facility or its parts.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-020" ] }, { "id": "code-edition", "name": "Applicable code edition", "description": "Building code and edition adopted by the jurisdiction at determination time.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-020" ] }, { "id": "construction-type", "name": "Construction type", "description": "Code-defined construction type governing fire resistance requirements.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-020" ] }, { "id": "hazard-classification", "name": "Hazard classification", "description": "Highest hazard group present and its material basis.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-020" ] }, { "id": "ahj-reference", "name": "Authority having jurisdiction", "description": "Reference to the authority that made or accepted the determination.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-020" ] } ], "artifacts": [ { "id": "occupancy-determination-record", "name": "Code occupancy determination record", "description": "Evidence of the occupancy and construction-type determination, mixed-occupancy approach and hazard classification, attributable to a named authority and code edition.", "media_or_form": [ "determination document", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus code edition and determination date; supersession recorded explicitly.", "source_refs": [ "SRC-020" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "spatial-extent-and-composition", "name": "Spatial Extent and Composition", "description": "Where the facility is, what boundary defines it, what contains it and what it is made of.", "rationale": "Facility boundaries are the single most contested aspect of the model: they determine metering scope, regulatory scope, security perimeter and cost allocation. IFC, CityGML and INSPIRE each supply normative but differing spatial constructs that must be reconciled once, here.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010", "SRC-016", "SRC-018", "SRC-014" ], "layers": [ { "id": "geospatial-extent-and-addressing", "name": "Geospatial Extent and Addressing", "description": "Georeferenced geometry, coordinate reference and accuracy, together with addressing and the administrative jurisdictions the facility falls within.", "source_refs": [ "SRC-003", "SRC-004", "SRC-010", "SRC-001" ], "findings": [ { "id": "facility-geometry-and-georeference", "name": "Facility geometry, georeference and level of detail", "description": "The representative point and boundary geometry of the facility, the coordinate reference system and vertical datum, positional accuracy, and the level of detail at which geometry is held. CityGML supplies LoD semantics, INSPIRE supplies accuracy and elevation reference expectations, and IFC supplies relative placement against site or parent facility.", "source_refs": [ "SRC-010", "SRC-003", "SRC-001", "SRC-004" ], "questions": [ { "id": "q-geometry-forms", "text": "Which geometric representations exist for the facility, and which one is authoritative for regulatory and emergency use?", "kind": "spatial", "answer_data": [ "geometry role code", "geometry value", "authoritative flag", "purpose code" ] }, { "id": "q-crs-accuracy", "text": "In which coordinate reference system and vertical datum is the geometry expressed, and what is its stated horizontal and vertical accuracy?", "kind": "measurement", "answer_data": [ "CRS code", "vertical datum code", "horizontal accuracy quantity", "accuracy method code" ] }, { "id": "q-lod", "text": "At what level of detail is the geometry held, and what was the capture method and capture date?", "kind": "provenance", "answer_data": [ "level of detail code", "capture method code", "captured at timestamp", "capture organisation reference" ] }, { "id": "q-placement", "text": "Is the facility placed absolutely or relatively to a site or parent facility, and what happens to the placement if the parent moves or is re-surveyed?", "kind": "relationship", "answer_data": [ "placement mode code", "placement parent reference", "re-survey propagation rule" ] } ], "data_elements": [ { "id": "representative-point", "name": "Representative point", "description": "Single georeferenced point standing for the facility, typically an entrance or centroid.", "value_kind": "geometry", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-003" ] }, { "id": "extent-geometry", "name": "Facility extent geometry", "description": "Boundary or footprint geometry delimiting the facility, in 2D, 2.5D or 3D.", "value_kind": "geometry", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010", "SRC-003" ] }, { "id": "crs-code", "name": "Coordinate reference system", "description": "Governed CRS identifier for all coordinate values in the record.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-010", "SRC-004" ] }, { "id": "horizontal-accuracy", "name": "Horizontal accuracy", "description": "Stated positional accuracy of coordinates, with unit.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "level-of-detail", "name": "Level of detail", "description": "LoD at which the geometry is modelled.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "geometry-observed-at", "name": "Geometry observation time", "description": "RFC 3339 time at which the geometry was surveyed or derived, distinct from record ingestion time.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "facility-boundary-geometry-set", "name": "Facility boundary geometry set", "description": "Set of georeferenced geometries for the facility with CRS, datum, accuracy, LoD and capture provenance, held independently of any serialisation format.", "media_or_form": [ "vector geometry set", "3D city model fragment", "BIM spatial placement" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus geometry role and level of detail; each version carries its own observation timestamp.", "source_refs": [ "SRC-010", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "facility-addressing-and-jurisdiction", "name": "Addressing and jurisdictional placement", "description": "Addresses used for postal, service, regulatory and emergency purposes, plus the administrative and jurisdictional units the facility falls within, including cases where it straddles a boundary. Address values are references into a sibling Address model; only role, authority and jurisdiction assignment are held here.", "source_refs": [ "SRC-004", "SRC-003", "SRC-006" ], "questions": [ { "id": "q-address-roles", "text": "Which addresses are recorded for the facility and what role does each play (postal, regulatory reporting, emergency response, service delivery)?", "kind": "identity", "answer_data": [ "address reference", "address role code", "authoritative for purpose code" ] }, { "id": "q-admin-units", "text": "Which administrative and jurisdictional units contain the facility, at which levels, and on what date were they determined?", "kind": "spatial", "answer_data": [ "administrative unit code", "unit level code", "determination date", "determination method" ] }, { "id": "q-straddling", "text": "Does the facility straddle any jurisdictional, tribal, utility or emergency-response boundary, and how is the split resolved for reporting?", "kind": "exception", "answer_data": [ "straddled boundary type", "apportionment rule", "primary jurisdiction reference" ] } ], "data_elements": [ { "id": "address-reference", "name": "Address reference", "description": "Reference to an address record with its role for this facility.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "admin-unit-code", "name": "Administrative unit code", "description": "Governed code for a containing administrative unit at a stated level.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-003" ] }, { "id": "country-code", "name": "Country code", "description": "Country in which the facility is located.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-004" ] }, { "id": "special-jurisdiction-indicator", "name": "Special jurisdiction indicator", "description": "Flag and type for tribal, federal enclave or other special jurisdictional status affecting applicable law.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "jurisdiction-determined-at", "name": "Jurisdiction determined at", "description": "Time at which jurisdictional placement was determined or last verified.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "address-and-jurisdiction-record", "name": "Address and jurisdiction record set", "description": "Role-tagged address references and the resolved set of containing administrative units, with determination method, date and straddling exceptions.", "media_or_form": [ "structured record set", "tabular export" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus address role and administrative unit level.", "source_refs": [ "SRC-004", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "composition-systems-and-asset-breakdown", "name": "Composition, Systems and Asset Breakdown", "description": "How the facility sits inside a site, decomposes into parts and buildings, and relates to its engineered systems and component asset register.", "source_refs": [ "SRC-001", "SRC-002", "SRC-016", "SRC-018", "SRC-014", "SRC-011" ], "findings": [ { "id": "site-to-facility-containment", "name": "Site containment and boundary exclusivity", "description": "The typed edge from the containing Site to this Facility, whether that containment is exclusive, whether the facility spans multiple sites or parcels, and how facility identity survives site subdivision or amalgamation. IFC permits a facility with no site at all, so containment must be modelled as conditional.", "source_refs": [ "SRC-001", "SRC-018", "SRC-006" ], "questions": [ { "id": "q-container", "text": "Which site or sites contain this facility, and is the containment exclusive for the period asserted?", "kind": "relationship", "answer_data": [ "site reference", "containment exclusivity flag", "valid from date", "valid to date" ] }, { "id": "q-no-site", "text": "If no site is recorded, what justifies treating the facility as the outermost spatial container, and what supplies its georeference?", "kind": "exception", "answer_data": [ "justification text", "georeference source reference", "approving role" ] }, { "id": "q-site-change", "text": "When the containing site is subdivided, merged or re-tenured, does the facility identifier persist and what event records the change?", "kind": "lifecycle", "answer_data": [ "event type code", "event time", "identifier continuity decision", "successor site reference" ] } ], "data_elements": [ { "id": "parent-site-reference", "name": "Parent site reference", "description": "Reference to the containing Site model instance, with validity window.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-018", "SRC-001" ] }, { "id": "containment-exclusivity", "name": "Containment exclusivity", "description": "Whether the facility belongs to exactly one site for the asserted period.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "containment-valid-from", "name": "Containment valid from", "description": "Date from which the site-facility containment holds.", "value_kind": "date", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "outermost-container-flag", "name": "Outermost container flag", "description": "True where the facility is modelled without a containing site, as IFC permits.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [], "inline_only_rationale": "Site containment is a typed edge between two independently governed models. The assertion carries only references, validity dates and an exclusivity flag; the documents of record (site plan, deed, survey) are artifacts of the Site model, and duplicating them here would create two conflicting masters for the same evidence." }, { "id": "facility-part-decomposition", "name": "Facility part decomposition and building membership", "description": "How the facility breaks down into parts and which buildings or structures are members over which periods. IFC requires an explicit usage convention for each facility part, and permits a facility to be part of a facility part, which allows longitudinal or regional division of larger facilities.", "source_refs": [ "SRC-002", "SRC-001", "SRC-016", "SRC-018" ], "questions": [ { "id": "q-decomposition-convention", "text": "Which decomposition convention governs the facility breakdown, and why was it chosen over the alternatives?", "kind": "composition", "answer_data": [ "usage type code", "convention rationale text", "approving role", "effective from date" ] }, { "id": "q-building-membership", "text": "Which buildings and structures are members of this facility, and over what validity period is each membership asserted?", "kind": "relationship", "answer_data": [ "building reference", "membership role code", "valid from date", "valid to date" ] }, { "id": "q-shared-parts", "text": "How are shared, common or jointly used parts handled where membership is not exclusive?", "kind": "exception", "answer_data": [ "shared part reference", "apportionment basis", "co-owning facility reference" ] }, { "id": "q-depth", "text": "How deep does the facility breakdown go before responsibility passes to the Building or Space model?", "kind": "constraint", "answer_data": [ "terminal level code", "handover rule text", "owning model identifier" ] } ], "data_elements": [ { "id": "decomposition-convention", "name": "Decomposition convention", "description": "Convention used to subdivide the facility, equivalent to the IFC facility part usage type.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "facility-part-reference", "name": "Facility part reference", "description": "Reference to a constituent facility part.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "building-member-reference", "name": "Building member reference", "description": "Reference to a contained Building model instance with membership validity.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-018", "SRC-016" ] }, { "id": "membership-exclusive", "name": "Membership exclusivity", "description": "Whether a member building or structure belongs to this facility alone.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "member-count", "name": "Member count", "description": "Count of member buildings or structures at the stated observation time.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-019" ] } ], "artifacts": [ { "id": "facility-breakdown-structure", "name": "Facility breakdown structure", "description": "Hierarchical breakdown of the facility into parts, buildings and structures, with the governing usage convention, membership validity windows and exclusivity flags.", "media_or_form": [ "hierarchical breakdown structure", "structured record set", "BIM spatial structure export" ], "serial": false, "identity_strategy": "Keyed by facility identifier; each node keyed by parent reference plus part identifier, with validity windows rather than renumbering.", "source_refs": [ "SRC-002", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "facility-systems-and-asset-register", "name": "Engineered systems and asset register linkage", "description": "Facility-level engineered systems (power, HVAC, water, drainage, fire protection, security, communications), their structured reference designations, the spaces or parts they serve, and the linkage from facility to the component asset register that holds individual equipment items.", "source_refs": [ "SRC-014", "SRC-016", "SRC-011", "SRC-017" ], "questions": [ { "id": "q-systems", "text": "Which engineered systems serve this facility, and what reference designation and aspect structure identifies each?", "kind": "composition", "answer_data": [ "system reference", "system type code", "reference designation string", "aspect code" ] }, { "id": "q-boundary-crossing", "text": "Which systems cross the facility boundary to a site-level or external utility, and where is the demarcation point?", "kind": "relationship", "answer_data": [ "system reference", "demarcation point description", "external provider reference", "metering point reference" ] }, { "id": "q-register-linkage", "text": "What key links facility records to the component asset register, and what proportion of installed assets is covered?", "kind": "interoperability", "answer_data": [ "linkage key", "asset register reference", "coverage proportion", "last inventory timestamp" ] }, { "id": "q-asset-transfer", "text": "How is an asset that is relocated between facilities recorded, and which record retains its maintenance history?", "kind": "process", "answer_data": [ "transfer event type", "event time", "source facility reference", "destination facility reference" ] } ], "data_elements": [ { "id": "system-reference", "name": "System reference", "description": "Reference to a facility-level engineered system.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-016", "SRC-014" ] }, { "id": "system-reference-designation", "name": "System reference designation", "description": "Structured designation for the system under ISO 81346-12.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "boundary-crossing-flag", "name": "Boundary crossing flag", "description": "Whether the system extends beyond the facility boundary to site or external infrastructure.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-016" ] }, { "id": "asset-register-reference", "name": "Asset register reference", "description": "Reference to the component asset register scoped to this facility.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "register-coverage-proportion", "name": "Register coverage proportion", "description": "Proportion of installed assets represented in the register, with basis.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "last-inventory-at", "name": "Last inventory time", "description": "RFC 3339 time of the most recent physical inventory verification.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] } ], "artifacts": [ { "id": "facility-system-and-asset-register-extract", "name": "Facility system and asset register extract", "description": "Register of facility-level systems with reference designations, served parts and boundary demarcations, plus a keyed extract linking to component asset records and coverage statistics.", "media_or_form": [ "system register", "handover data table set", "structured record set" ], "serial": false, "identity_strategy": "Systems keyed by reference designation within the facility; asset linkage keyed by the declared linkage key plus facility identifier.", "source_refs": [ "SRC-016", "SRC-014", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "non-building-and-mobile-facilities", "name": "Non-building, mobile and exclusion cases", "description": "ISO 16739-1:2024 / IFC 4.3 extends facility to bridges, roads, railways, waterways and port facilities. FHIR includes mobile clinics, ambulances and vehicles. EPA includes monitoring stations and waste sites that cannot be classified as single facilities. ISO/TR 41013 states that a single asset such as a car or air-handling unit is not a facility, and that something not built, such as a nature preserve, is not a facility. Mobile versus fixed and instance versus kind must be explicit. Kind-of-location classifiers are out of scope as instances.", "source_refs": [ "SRC-024", "SRC-031", "SRC-026", "SRC-027", "SRC-004" ], "questions": [ { "id": "non-building-and-mobile-facilities-q01", "text": "Is this a building-oriented facility, a civil or infrastructure facility, or a mixed campus, and which IFC or local subtype applies?", "kind": "classification", "answer_data": [ "domain_flag", "ifc_subtype", "campus_or_network_flag" ] }, { "id": "non-building-and-mobile-facilities-q02", "text": "Is the facility fixed, mobile or relocatable, and if mobile what is the current position versus the home base?", "kind": "state", "answer_data": [ "mobility_mode", "home_base_facility_id", "current_position" ] }, { "id": "non-building-and-mobile-facilities-q03", "text": "Does the candidate fail the facility test because it is a single asset, an unbuilt asset, a kind classifier, or a space or room?", "kind": "validation", "answer_data": [ "exclusion_reason", "recommended_sibling_model", "pass_fail" ] } ], "data_elements": [ { "id": "non-building-and-mobile-facilities-data01", "name": "Mobility mode", "description": "Fixed, mobile or relocatable operating mode.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-026" ] }, { "id": "non-building-and-mobile-facilities-data02", "name": "Instance or kind", "description": "Whether the record is a specific instance or a kind-of-facility classifier; kind is out of scope for this aggregate.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-026" ] }, { "id": "non-building-and-mobile-facilities-data03", "name": "Not-a-facility flag", "description": "Explicit exclusion when the candidate is a single asset or unbuilt asset.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-027" ] } ], "artifacts": [ { "id": "non-building-and-mobile-facilities-artifact01", "name": "Facility eligibility decision", "description": "Decision record that a candidate is or is not a facility under ISO 41011/41013 and this model.", "media_or_form": [ "decision-record" ], "serial": false, "identity_strategy": "Decision identifier assigned by the Dimension; cite the candidate's source identifier.", "source_refs": [ "SRC-027", "SRC-022" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-state-and-time", "name": "Lifecycle, State and Time", "description": "Where the facility is in its life, what condition it is in, and how record time is distinguished from real-world time.", "rationale": "Facility records are consumed long after they are written and are routinely corrected retroactively. Separating lifecycle phase, operational status, real-world validity and record versioning is required to make historic queries answerable and corrections auditable.", "source_refs": [ "SRC-015", "SRC-003", "SRC-010", "SRC-007", "SRC-013" ], "layers": [ { "id": "lifecycle-phase-and-events", "name": "Lifecycle Phase and Milestone Events", "description": "Phase and status of the facility across its service life, and the milestone events that move it between them.", "source_refs": [ "SRC-015", "SRC-003", "SRC-013", "SRC-007" ], "findings": [ { "id": "lifecycle-phase-status-and-milestones", "name": "Lifecycle phase, operational status and milestone events", "description": "The facility's position in the ISO 15686-1 life cycle (initiation, project definition, design, construction, commissioning, operation, maintenance, refurbishment, replacement, deconstruction and disposal), its current operational status, and the milestone events that changed either. INSPIRE supplies a construction-condition code list and ISO 19650-3 supplies operational trigger events that require an information exchange.", "source_refs": [ "SRC-015", "SRC-003", "SRC-013", "SRC-007" ], "questions": [ { "id": "q-phase", "text": "What is the facility's current lifecycle phase and operational status, on which code list, and since when?", "kind": "state", "answer_data": [ "lifecycle phase code", "operational status code", "code list reference", "status effective at timestamp" ] }, { "id": "q-milestones", "text": "Which milestone events have occurred, and what are the event time and the observation or recording time for each?", "kind": "event", "answer_data": [ "milestone event type", "event time", "recorded at time", "asserting party reference" ] }, { "id": "q-handover", "text": "What evidence closes construction handover and opens operation, and who accepts it?", "kind": "evidence", "answer_data": [ "acceptance evidence reference", "accepting role", "acceptance timestamp", "outstanding defect count" ] }, { "id": "q-terminal-states", "text": "Which terminal states exist (mothballed, disposed, demolished), and which obligations survive each of them?", "kind": "lifecycle", "answer_data": [ "terminal state code", "surviving obligation type", "obligation end condition", "responsible party reference" ] } ], "data_elements": [ { "id": "lifecycle-phase", "name": "Lifecycle phase", "description": "Current life-cycle phase of the facility.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-015" ] }, { "id": "operational-status", "name": "Operational status", "description": "Current operating state, such as in use, partially occupied, mothballed or disposed.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-003" ] }, { "id": "status-effective-at", "name": "Status effective at", "description": "RFC 3339 time from which the current status holds in the real world.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "milestone-event-set", "name": "Milestone event set", "description": "Ordered set of lifecycle milestone events with type, event time, recorded time and asserting party.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013", "SRC-015" ] }, { "id": "status-asserted-by", "name": "Status asserted by", "description": "Party or role authorised to assert the current status.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] } ], "artifacts": [ { "id": "facility-milestone-event-log", "name": "Facility milestone event log", "description": "Append-only log of lifecycle transitions and trigger events, each carrying event time, recording time, asserting party and supporting evidence reference.", "media_or_form": [ "append-only event log", "structured record set" ], "serial": true, "identity_strategy": "Keyed by facility identifier plus monotonically increasing event sequence number; entries are never edited, only superseded by correction entries that cite the corrected sequence.", "source_refs": [ "SRC-013", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "condition-service-life-and-versioning", "name": "Condition, Service Life and Record Versioning", "description": "Physical condition and remaining service life of the facility, and the versioning rules that govern its record over time.", "source_refs": [ "SRC-015", "SRC-007", "SRC-003", "SRC-010" ], "findings": [ { "id": "condition-and-service-life", "name": "Condition assessment, service life and deferred maintenance", "description": "Measured or estimated physical condition of the facility, the method and date of assessment, design and remaining service life, and the accumulated deferred maintenance liability. Federal real-property reporting requires condition and related measures alongside a reassessment cadence.", "source_refs": [ "SRC-015", "SRC-007", "SRC-011" ], "questions": [ { "id": "q-condition", "text": "What is the current condition measure, by which assessment method, and as of what assessment date?", "kind": "measurement", "answer_data": [ "condition index value", "condition method code", "assessment date", "assessing organisation reference" ] }, { "id": "q-service-life", "text": "What design service life was specified and what remaining service life is now estimated, on what basis?", "kind": "quality", "answer_data": [ "design service life duration", "remaining service life duration", "estimation basis code", "estimated at timestamp" ] }, { "id": "q-deferred-maintenance", "text": "What is the deferred maintenance and repair liability, in which currency and price base, and as of when?", "kind": "measurement", "answer_data": [ "liability amount", "currency code", "price base year", "as of date" ] }, { "id": "q-reassessment", "text": "How often must condition be reassessed, who is competent to do it, and what happens when the cadence is missed?", "kind": "process", "answer_data": [ "reassessment interval", "competency requirement", "overdue escalation rule" ] } ], "data_elements": [ { "id": "condition-index", "name": "Condition index", "description": "Numeric condition measure for the facility, on a declared scale.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "condition-method", "name": "Condition assessment method", "description": "Named method and version used to derive the condition measure.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "condition-assessed-at", "name": "Condition assessed at", "description": "RFC 3339 time of the condition assessment observation.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "design-service-life", "name": "Design service life", "description": "Service life specified at design, as a duration.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "remaining-service-life", "name": "Remaining service life", "description": "Estimated remaining service life, as a duration, with estimation basis.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "deferred-maintenance-value", "name": "Deferred maintenance value", "description": "Monetary liability for deferred maintenance and repair, with currency and price base.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "condition-assessment-report", "name": "Condition assessment report", "description": "Report recording the inspection scope, method, findings by system, condition score, remaining service life estimate and deferred maintenance itemisation, attributable to a named assessor.", "media_or_form": [ "assessment report", "structured record set", "evidence photograph set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus assessment date and method; each report is immutable once issued and is superseded rather than amended.", "source_refs": [ "SRC-015", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "temporal-versioning-and-validity", "name": "Record versioning, valid time and observation time", "description": "The bitemporal discipline for facility records: record version validity bounds, real-world validity, event time, observation time and ingestion time, and the rule separating a correction of a past error from a genuine real-world change. INSPIRE mandates lifespan version bounds with time-zone information; CityGML supplies a versioning module for city object states.", "source_refs": [ "SRC-003", "SRC-010", "SRC-005" ], "questions": [ { "id": "q-version-bounds", "text": "What are this record version's validity bounds, and how do they differ from the facility's real-world validity period?", "kind": "temporal", "answer_data": [ "version valid from timestamp", "version valid to timestamp", "real-world valid from date", "real-world valid to date" ] }, { "id": "q-time-separation", "text": "For each time-bearing attribute, are event time, observation time and ingestion time recorded separately with explicit offsets?", "kind": "temporal", "answer_data": [ "attribute name", "event time", "observed at time", "ingested at time" ] }, { "id": "q-correction-vs-change", "text": "How is a correction of an erroneous earlier value distinguished from a record of a real-world change?", "kind": "provenance", "answer_data": [ "change kind code", "corrected version reference", "correction reason text", "corrected by reference" ] }, { "id": "q-supersession", "text": "What rule resolves overlapping or conflicting versions of the same facility record?", "kind": "validation", "answer_data": [ "supersession rule identifier", "winning version reference", "conflict detection method" ] } ], "data_elements": [ { "id": "version-valid-from", "name": "Version valid from", "description": "RFC 3339 timestamp with explicit offset marking the start of this record version's validity.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "version-valid-to", "name": "Version valid to", "description": "RFC 3339 timestamp marking the end of this record version's validity; absent while current.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "real-world-valid-from", "name": "Real-world valid from", "description": "Date from which the described state holds in the real world, independent of record time.", "value_kind": "date", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "observed-at", "name": "Observation time", "description": "Time at which the state was observed or measured.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "recorded-at", "name": "Ingestion time", "description": "Time at which the value entered the governed record.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-005" ] }, { "id": "change-kind", "name": "Change kind", "description": "Whether a new version reflects a real-world change or a correction of a prior error.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "facility-version-history", "name": "Facility record version history", "description": "Chronological version history of the facility record with validity bounds, change kind, supersession links and the agent responsible for each version.", "media_or_form": [ "version history log", "structured record set" ], "serial": true, "identity_strategy": "Keyed by facility identifier plus zero-padded version sequence; versions are immutable and superseded, never overwritten.", "source_refs": [ "SRC-003", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "authority-tenure-and-compliance", "name": "Authority, Tenure and Compliance", "description": "Who owns, holds and operates the facility, what it is authorised to do, and what may be disclosed about it.", "rationale": "A facility is simultaneously a property interest, an operating responsibility and a regulated object. These three chains of authority are frequently held by different organisations, and conflating them is the most common cause of unactionable facility data.", "source_refs": [ "SRC-006", "SRC-007", "SRC-012", "SRC-005", "SRC-009", "SRC-020" ], "layers": [ { "id": "ownership-custody-and-tenure", "name": "Ownership, Custody and Operating Accountability", "description": "Legal interest in the facility, custodial control, and the demand-organisation to service-provider accountability chain.", "source_refs": [ "SRC-006", "SRC-007", "SRC-012", "SRC-011" ], "findings": [ { "id": "ownership-custody-and-legal-interest", "name": "Ownership, custody and legal interest", "description": "The legal interest held in the facility (owned, leased, licensed or otherwise managed), the party holding title, the organisation with custody and control where different, and the encumbrances, easements and lease terms that constrain use. Federal real-property reporting treats legal interest, ownership and custodial agency as distinct reportable facts.", "source_refs": [ "SRC-007", "SRC-006", "SRC-012" ], "questions": [ { "id": "q-legal-interest", "text": "What type of legal interest is held in the facility, by which party, and over what term?", "kind": "ownership", "answer_data": [ "legal interest type code", "holding party reference", "interest start date", "interest end date" ] }, { "id": "q-custody", "text": "Which organisation has custody and control of the facility for operational purposes, if different from the title holder?", "kind": "authority", "answer_data": [ "custodian organisation reference", "custody basis code", "custody effective from date" ] }, { "id": "q-encumbrances", "text": "Which encumbrances, easements, covenants or lease conditions constrain how the facility may be used or altered?", "kind": "constraint", "answer_data": [ "encumbrance type code", "constraint description", "instrument reference", "expiry date" ] }, { "id": "q-interest-change", "text": "What process records a change of ownership or interest, and what evidence must accompany it?", "kind": "process", "answer_data": [ "transfer event type", "effective date", "evidence reference", "approving authority reference" ] } ], "data_elements": [ { "id": "legal-interest-type", "name": "Legal interest type", "description": "Type of legal interest held in the facility.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "owner-organisation-reference", "name": "Owner organisation reference", "description": "Reference to the party holding the legal interest.", "value_kind": "reference", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "custodian-organisation-reference", "name": "Custodian organisation reference", "description": "Reference to the organisation with custody and control, where distinct from the owner.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "interest-term", "name": "Interest term", "description": "Start and end dates of the legal interest.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "encumbrance-set", "name": "Encumbrance set", "description": "Encumbrances, easements and covenants constraining use, with instrument references.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "tenure-and-interest-evidence-pack", "name": "Tenure and interest evidence pack", "description": "Compiled evidence of legal interest, custody assignment and encumbrances, with instrument references, effective dates and the authority that recorded each.", "media_or_form": [ "evidence document set", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus interest instrument reference; superseded packs retained with end dates.", "source_refs": [ "SRC-007", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "operator-and-service-accountability", "name": "Operator and facility-management accountability", "description": "The chain from demand organisation to facility-management service provider, the scope of services delegated, the governing agreement, and the named accountable person for statutory duties. ISO 41011 makes the demand-organisation and service-provider distinction the core of facility-management vocabulary.", "source_refs": [ "SRC-012", "SRC-011", "SRC-013" ], "questions": [ { "id": "q-demand-org", "text": "Which organisation is the demand organisation for this facility and which is the facility-management service provider?", "kind": "ownership", "answer_data": [ "demand organisation reference", "service provider reference", "relationship type code" ] }, { "id": "q-service-scope", "text": "What scope of services is delegated, under which agreement, and what is expressly retained by the demand organisation?", "kind": "authority", "answer_data": [ "service scope code", "agreement reference", "retained responsibility text", "scope effective from date" ] }, { "id": "q-accountable-person", "text": "Who is the named accountable person or role for statutory duties at this facility, and how is competence evidenced?", "kind": "authority", "answer_data": [ "accountable role name", "person or post reference", "competence evidence reference", "appointment date" ] }, { "id": "q-handover-of-responsibility", "text": "How is a change of operator or service provider recorded, and what information must transfer with it?", "kind": "process", "answer_data": [ "handover event type", "event time", "transferred information set reference", "acceptance confirmation" ] } ], "data_elements": [ { "id": "demand-organisation-reference", "name": "Demand organisation reference", "description": "Organisation whose objectives the facility serves and which specifies facility-management requirements.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-012" ] }, { "id": "service-provider-reference", "name": "Service provider reference", "description": "Organisation delivering facility-management services, internal or external.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "service-scope-code", "name": "Service scope code", "description": "Delegated service categories, such as maintenance, cleaning, security or energy management.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "management-agreement-reference", "name": "Management agreement reference", "description": "Reference to the governing agreement or appointment.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "accountable-role", "name": "Accountable role", "description": "Named role accountable for statutory duties at the facility.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "responsibility-effective-at", "name": "Responsibility effective at", "description": "RFC 3339 time from which the accountability assignment holds.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "facility-management-accountability-record", "name": "Facility management accountability record", "description": "Record of the demand organisation, service providers, delegated scope, governing agreement, named accountable roles and effective dates, with handover confirmations.", "media_or_form": [ "accountability record", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus agreement reference and effective-from timestamp.", "source_refs": [ "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "regulatory-standing-and-compliance", "name": "Regulatory Standing and Compliance Evidence", "description": "Regulatory programmes that apply to the facility, the authorisations it holds, and the inspection and certification evidence that demonstrates continuing compliance.", "source_refs": [ "SRC-005", "SRC-004", "SRC-020", "SRC-011" ], "findings": [ { "id": "regulatory-interests-permits-and-inspections", "name": "Regulatory programme interests, permits and statutory inspections", "description": "The regulatory programmes under which the facility is regulated or monitored, the programme identifiers issued by each regulator, the permits and authorisations in force with their validity and conditions, and the statutory inspection and certification regime with due dates, results and open nonconformities. EPA FRS models this as environmental interest types linking program records to a single facility registry identifier.", "source_refs": [ "SRC-005", "SRC-004", "SRC-020", "SRC-011" ], "questions": [ { "id": "q-programmes", "text": "Which regulatory programmes apply to this facility, which regulator is competent for each, and what programme identifier has each issued?", "kind": "authority", "answer_data": [ "programme code", "regulator organisation reference", "programme identifier value", "interest start date" ] }, { "id": "q-permits", "text": "Which permits and authorisations are currently in force, with what validity dates and what operating conditions?", "kind": "requirement", "answer_data": [ "permit reference", "valid from date", "valid to date", "condition summary text" ] }, { "id": "q-inspections", "text": "Which statutory inspections and certifications are required, and what are the last completion and next due dates for each?", "kind": "evidence", "answer_data": [ "inspection type code", "last completed at timestamp", "next due date", "result code" ] }, { "id": "q-nonconformity", "text": "Which nonconformities are open, what corrective action is committed, and by when must it complete?", "kind": "exception", "answer_data": [ "nonconformity reference", "severity code", "corrective action text", "due date" ] }, { "id": "q-reporting-obligations", "text": "What periodic reporting obligations follow from each programme interest, and at what cadence?", "kind": "requirement", "answer_data": [ "report type code", "cadence duration", "next submission due date", "responsible role" ] } ], "data_elements": [ { "id": "regulatory-programme-code", "name": "Regulatory programme code", "description": "Code identifying a programme under which the facility is regulated or monitored.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-004" ] }, { "id": "programme-identifier", "name": "Programme identifier", "description": "Identifier issued to the facility by a regulator within a specific programme.", "value_kind": "identifier", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "permit-reference", "name": "Permit reference", "description": "Reference to an authorisation instrument held in the Authorization model.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "permit-validity", "name": "Permit validity window", "description": "Valid-from and valid-to dates for an authorisation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "inspection-schedule", "name": "Inspection schedule", "description": "Statutory inspection types with last completion, next due date and result.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-020", "SRC-011" ] }, { "id": "open-nonconformity-set", "name": "Open nonconformity set", "description": "Open findings with severity, corrective action and due date.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011" ] } ], "artifacts": [ { "id": "regulatory-and-compliance-dossier", "name": "Regulatory and compliance dossier", "description": "Dossier binding programme interests, programme identifiers, permits with conditions, inspection certificates and open nonconformities to the facility identifier, with issuing authority and validity for each item.", "media_or_form": [ "compliance dossier", "certificate set", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus programme code and instrument reference; certificates carry their own issuing-authority identifiers and are never renumbered locally.", "source_refs": [ "SRC-005", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "occupancy-authorization-and-ahj", "name": "Occupancy authorization and authority having jurisdiction", "description": "Under IBC 111.1, a building or structure shall not be used or occupied, and a change of occupancy shall not be made, until the building official has issued a certificate of occupancy. Certificates that presume authority to violate the code are not valid. Work exempt from permit may be excepted. This rule is building-code-centric; roads, railways and some civil facilities are authorized by other AHJs. A CO authorizes occupancy under the building code; it does not by itself satisfy ongoing fire-code, elevator or environmental program duties. Phased projects may require occupancy authorization before occupying portions.", "source_refs": [ "SRC-028", "SRC-024", "SRC-025" ], "questions": [ { "id": "occupancy-authorization-and-ahj-q01", "text": "Has a certificate of occupancy or equivalent occupancy authorization been issued for this facility or a described portion, and by which AHJ?", "kind": "authority", "answer_data": [ "authorization_status", "certificate_identifier", "ahj_name", "portion_description" ] }, { "id": "occupancy-authorization-and-ahj-q02", "text": "What use, occupancy classification, construction type, code edition and design occupant load does the certificate authorize?", "kind": "authority", "answer_data": [ "authorized_use", "occupancy_classification", "construction_type", "code_edition", "design_occupant_load" ] }, { "id": "occupancy-authorization-and-ahj-q03", "text": "Is occupancy authorized in phases or for only a portion of the facility, and what is still prohibited?", "kind": "exception", "answer_data": [ "phased_flag", "authorized_portion", "remaining_restrictions" ] }, { "id": "occupancy-authorization-and-ahj-q04", "text": "When was the certificate issued or occupancy authorized, and when was that fact observed or ingested into this model?", "kind": "temporal", "answer_data": [ "issued_at", "observed_at", "ingested_at" ] } ], "data_elements": [ { "id": "occupancy-authorization-and-ahj-data01", "name": "Occupancy authorization status", "description": "Whether legal occupancy is authorized, prohibited, partial or not applicable because the facility is not a building or structure under the adopted code.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-028" ] }, { "id": "occupancy-authorization-and-ahj-data02", "name": "Certificate of occupancy identifier", "description": "Identifier assigned by the building official to the certificate.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-028" ] }, { "id": "occupancy-authorization-and-ahj-data03", "name": "Design occupant load", "description": "Design occupant load stated for the authorized occupancy.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-024", "SRC-028" ] }, { "id": "occupancy-authorization-and-ahj-data04", "name": "Building official or AHJ", "description": "Authority that inspects and issues occupancy authorization.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-028" ] } ], "artifacts": [ { "id": "occupancy-authorization-and-ahj-artifact01", "name": "Certificate of occupancy", "description": "Occupancy authorization issued by the building official for a building, structure or described portion.", "media_or_form": [ "certificate", "official-instrument" ], "serial": true, "identity_strategy": "Certificate number issued by the AHJ; bind to facility master identifier and portion.", "source_refs": [ "SRC-028" ] } ], "inline_only_rationale": null }, { "id": "compliance-monitoring-status", "name": "Compliance monitoring status", "description": "ECHO reports compliance monitoring activity counts, last monitoring date and statute-specific compliance status, including inactive facility. These determinations often reflect alleged rather than finally adjudicated violations. This finding is an alignment to US environmental operating data; it is not a universal compliance model and must not be treated as a court judgement.", "source_refs": [ "SRC-030" ], "questions": [ { "id": "compliance-monitoring-status-q01", "text": "What is the current reported compliance status by statute, and as of which refresh date?", "kind": "state", "answer_data": [ "statute", "compliance_status", "data_refresh_time" ] }, { "id": "compliance-monitoring-status-q02", "text": "When did the last compliance monitoring activity occur, of what type, and is the date an on-site inspection or an evaluation completion date?", "kind": "event", "answer_data": [ "last_monitoring_time", "activity_type", "on_site_flag" ] }, { "id": "compliance-monitoring-status-q03", "text": "Is the reported violation or noncompliance an alleged status used for tracking, or a final adjudication, and what caveats apply?", "kind": "quality", "answer_data": [ "adjudication_status", "caveat_text" ] } ], "data_elements": [ { "id": "compliance-monitoring-status-data01", "name": "Compliance status by statute", "description": "Most recent reported compliance status for each regulating statute.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-030" ] }, { "id": "compliance-monitoring-status-data02", "name": "Last compliance monitoring activity", "description": "Type and time of the most recent counted monitoring activity.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-030" ] } ], "artifacts": [ { "id": "compliance-monitoring-status-artifact01", "name": "Compliance status snapshot", "description": "Point-in-time extract of reported compliance and monitoring status.", "media_or_form": [ "report-extract" ], "serial": false, "identity_strategy": "Facility master identifier plus snapshot ingestion time.", "source_refs": [ "SRC-030" ] } ], "inline_only_rationale": null } ] }, { "id": "security-and-information-access", "name": "Security Posture and Information Access", "description": "The facility's assessed security level and protective measures, and the constraints on disclosing facility information.", "source_refs": [ "SRC-009", "SRC-006" ], "findings": [ { "id": "facility-security-level-and-protective-posture", "name": "Facility security level and protective posture", "description": "The assessed security level of the facility derived from mission criticality, symbolism, facility population, facility size and threat to tenants, the baseline countermeasures that follow, implemented versus required status, and any accepted deviations. The ISC standard defines five levels with associated requirements.", "source_refs": [ "SRC-009" ], "questions": [ { "id": "q-fsl", "text": "What security level has been assessed for this facility, and what score did each determination factor contribute?", "kind": "security", "answer_data": [ "security level code", "factor name", "factor score", "determination method reference" ] }, { "id": "q-countermeasures", "text": "Which protective measures are required at this level, which are implemented, and which deviations have been accepted by whom?", "kind": "security", "answer_data": [ "countermeasure code", "required flag", "implemented flag", "deviation approval reference" ] }, { "id": "q-critical-infrastructure", "text": "Is the facility designated critical infrastructure, under which sector and by which authority?", "kind": "classification", "answer_data": [ "sector code", "designating authority reference", "designation date" ] }, { "id": "facility-security-level-and-protective-posture-q-reassessment", "text": "When was the security assessment performed, when is reassessment due, and what event forces an early reassessment?", "kind": "temporal", "answer_data": [ "assessment date", "reassessment due date", "early trigger condition text" ] } ], "data_elements": [ { "id": "security-level", "name": "Facility security level", "description": "Assessed security level on a declared scale.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "security-factor-scores", "name": "Security determination factor scores", "description": "Scores for mission criticality, symbolism, population, size and threat.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "countermeasure-status-set", "name": "Countermeasure status set", "description": "Required versus implemented status per baseline countermeasure, with deviation approvals.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "critical-infrastructure-sector", "name": "Critical infrastructure sector", "description": "Sector designation where the facility is classified as critical infrastructure.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "security-assessment-date", "name": "Security assessment date", "description": "Date the security level determination was made.", "value_kind": "date", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "security-level-determination-record", "name": "Facility security level determination record", "description": "Determination record capturing factor scoring, resulting level, required countermeasure baseline, implementation status and accepted deviations, with the approving security authority.", "media_or_form": [ "determination record", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus determination date; the record itself is normally handled at a restricted sensitivity marking.", "source_refs": [ "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "information-disclosure-and-access-constraints", "name": "Information disclosure and access constraints", "description": "Which facility attributes may be published, which must be withheld or generalised, on what legal basis, who may grant exceptions, and what must be logged. Federal real-property publication law expressly authorises excluding assets for national-security reasons and under freedom-of-information exemptions, establishing that facility inventories are not uniformly public.", "source_refs": [ "SRC-006", "SRC-009" ], "questions": [ { "id": "q-withheld-attributes", "text": "Which attributes are withheld, generalised or precision-reduced in public releases, and on what legal basis is each?", "kind": "privacy", "answer_data": [ "attribute name", "treatment code", "legal basis reference", "review date" ] }, { "id": "q-sensitivity-marking", "text": "What sensitivity marking applies to each bundle, layer, finding and artifact of this facility record?", "kind": "access", "answer_data": [ "scope kind", "scope identifier", "sensitivity marking code", "marking authority" ] }, { "id": "q-exceptions", "text": "Who may grant an access exception, for what duration, and under what justification?", "kind": "exception", "answer_data": [ "granting role", "exception duration", "justification text", "expiry timestamp" ] }, { "id": "q-audit", "text": "What must be logged when restricted facility attributes are read, exported or shared with an external party?", "kind": "access", "answer_data": [ "log event type", "subject identity reference", "accessed scope reference", "access timestamp" ] } ], "data_elements": [ { "id": "sensitivity-marking", "name": "Sensitivity marking", "description": "Governed marking controlling disclosure of a scoped part of the facility record.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-009" ] }, { "id": "disclosure-basis", "name": "Disclosure or withholding basis", "description": "Legal or policy basis for publishing, generalising or withholding an attribute.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "redaction-rule-set", "name": "Redaction rule set", "description": "Rules for suppressing or generalising attributes, including geometry precision reduction, in public projections.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "access-exception-grant", "name": "Access exception grant", "description": "Time-bounded exception with granting role, justification and expiry.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "access-log-reference", "name": "Access log reference", "description": "Reference to the audit log recording reads and exports of restricted content.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "disclosure-control-record", "name": "Disclosure control record", "description": "Record of sensitivity markings per scope, redaction and generalisation rules, legal bases, exception grants and audit-logging obligations for the facility.", "media_or_form": [ "policy record", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus scope kind and scope identifier; each marking change is versioned with an effective timestamp.", "source_refs": [ "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "operations-performance-and-risk", "name": "Operations, Performance and Risk", "description": "How much the facility can do, how well it performs, how it is maintained and what threatens its continued operation.", "rationale": "Operating decisions and investment cases depend on capacity, utilisation, resource performance and criticality. Each of these is a measurement with a boundary, a method and an observation time, and is worthless without them.", "source_refs": [ "SRC-019", "SRC-009", "SRC-011", "SRC-016", "SRC-007" ], "layers": [ { "id": "capacity-utilisation-and-performance", "name": "Capacity, Utilisation and Resource Performance", "description": "Area and capacity measures, occupant population and operating schedule, and benchmarked resource and emissions performance with its measurement provenance.", "source_refs": [ "SRC-019", "SRC-009", "SRC-007" ], "findings": [ { "id": "capacity-occupancy-and-utilisation", "name": "Area, capacity, occupancy and utilisation", "description": "Area measures under a declared measurement standard, design capacity, occupant population by category, operating schedule and derived utilisation. Gross floor area and operating-hours style use details are the mandatory inputs to benchmarking, while facility population and size are two of the five security-level determination factors.", "source_refs": [ "SRC-019", "SRC-009", "SRC-007" ], "questions": [ { "id": "q-area-measures", "text": "Which area measures are recorded, under which measurement standard, and as of what date?", "kind": "measurement", "answer_data": [ "area measure type", "area quantity", "measurement standard reference", "measured as of date" ] }, { "id": "q-capacity-utilisation", "text": "What is the design capacity, what is actual utilisation, and by what formula is utilisation derived?", "kind": "measurement", "answer_data": [ "design capacity value", "utilisation value", "derivation formula text", "observation period" ] }, { "id": "q-population", "text": "What are the peak and typical occupant populations by category, how are they counted and how current is the count?", "kind": "measurement", "answer_data": [ "occupant category code", "peak count", "typical count", "counted as of date" ] }, { "id": "q-schedule", "text": "What is the operating schedule, including weekly operating hours and seasonal or shift variation?", "kind": "temporal", "answer_data": [ "weekly operating hours", "shift pattern code", "seasonal variation description", "schedule effective from date" ] }, { "id": "q-shared-area", "text": "How are shared and common areas apportioned across member buildings and tenants, and does the total reconcile?", "kind": "validation", "answer_data": [ "apportionment basis code", "reconciliation difference", "tolerance threshold" ] } ], "data_elements": [ { "id": "gross-floor-area", "name": "Gross floor area", "description": "Total enclosed floor area under a declared measurement standard, with unit.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-019" ] }, { "id": "area-measurement-standard", "name": "Area measurement standard", "description": "Standard and version under which area measures are taken.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-019" ] }, { "id": "design-capacity", "name": "Design capacity", "description": "Design capacity of the facility in units appropriate to its function.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "utilisation-rate", "name": "Utilisation rate", "description": "Derived utilisation over a stated observation period.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "occupant-population", "name": "Occupant population", "description": "Peak and typical occupant counts by category with counting method.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009", "SRC-019" ] }, { "id": "weekly-operating-hours", "name": "Weekly operating hours", "description": "Hours per week the facility is in operation, used for normalisation.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-019" ] } ], "artifacts": [ { "id": "capacity-and-utilisation-measurement-record", "name": "Capacity and utilisation measurement record", "description": "Measurement record holding area measures with standard and date, capacity, occupant population by category, operating schedule and derived utilisation with its formula.", "media_or_form": [ "measurement record", "tabular export", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus measure type and observation period; restatements create new records citing the superseded one.", "source_refs": [ "SRC-019", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "resource-performance-and-measurement-provenance", "name": "Energy, water and emissions performance with measurement provenance", "description": "Benchmarked resource and emissions performance for the facility over stated reporting periods, the normalisation and benchmark reference used, the metering boundary relative to the facility boundary, and the share of values that are metered rather than estimated. Multi-building facilities are benchmarked as a parent property aggregating child buildings, which makes the boundary declaration mandatory rather than optional.", "source_refs": [ "SRC-019", "SRC-011", "SRC-005" ], "questions": [ { "id": "q-metrics", "text": "Which energy, water and emissions metrics are tracked, over what reporting period, and in what units?", "kind": "measurement", "answer_data": [ "metric code", "metric value", "unit code", "reporting period start and end" ] }, { "id": "q-normalisation", "text": "Which normalisation and benchmark reference is applied, and against which comparison population?", "kind": "quality", "answer_data": [ "normalisation method code", "benchmark reference dataset", "comparison population description", "benchmark score" ] }, { "id": "q-metering-boundary", "text": "Does the metering boundary coincide with the facility boundary, and what is included or excluded?", "kind": "constraint", "answer_data": [ "boundary coincidence flag", "included scope description", "excluded scope description", "boundary diagram reference" ] }, { "id": "q-estimation", "text": "What share of reported consumption is metered versus estimated, and what estimation method was used?", "kind": "provenance", "answer_data": [ "metered share", "estimated share", "estimation method code", "meter reference set" ] }, { "id": "q-restatement", "text": "How are restatements of previously published performance figures identified, justified and propagated?", "kind": "process", "answer_data": [ "restated metric reference", "restatement reason text", "restated at timestamp", "downstream notification list" ] } ], "data_elements": [ { "id": "reporting-period", "name": "Reporting period", "description": "Start and end dates of the performance reporting period.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-019" ] }, { "id": "energy-use-intensity", "name": "Energy use intensity", "description": "Site or source energy use per unit floor area, with variant declared.", "value_kind": "quantity", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-019" ] }, { "id": "greenhouse-gas-emissions", "name": "Greenhouse gas emissions", "description": "Emissions attributable to the facility for the reporting period, with scope and factor set.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-019" ] }, { "id": "benchmark-score", "name": "Benchmark score", "description": "Comparative score against the declared benchmark population.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-019" ] }, { "id": "metering-boundary-note", "name": "Metering boundary declaration", "description": "Statement of what the metering boundary includes and excludes relative to the facility extent.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-019" ] }, { "id": "estimated-share", "name": "Estimated share", "description": "Proportion of reported consumption derived by estimation rather than metering.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "reading-observation-time", "name": "Reading observation time", "description": "Observation time of the underlying meter reading batch, recorded separately from ingestion time.", "value_kind": "timestamp", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] } ], "artifacts": [ { "id": "performance-benchmark-report", "name": "Resource performance and benchmark report", "description": "Report of energy, water and emissions metrics for a reporting period with normalisation method, benchmark reference, metering boundary declaration, metered versus estimated shares and restatement history.", "media_or_form": [ "benchmark report", "tabular export", "structured record set" ], "serial": true, "identity_strategy": "Keyed by facility identifier plus reporting period; successive periods are appended and restatements are issued as new versions citing the superseded report.", "source_refs": [ "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "performance-evaluation-and-service-life", "name": "Performance evaluation and service life", "description": "Service life is the period after installation during which a building or its parts meet performance requirements. Post-occupancy evaluation analyses how functional and comfortable a building is after users have occupied it. ISO 19650-3 includes post-occupancy or implementation evaluation as a point on the operational timeline. Key performance indicators and indoor environmental quality are measurement alignments; detailed energy-benchmarking schemes such as ENERGY STAR are known omissions unless later aligned.", "source_refs": [ "SRC-022", "SRC-025" ], "questions": [ { "id": "performance-evaluation-and-service-life-q01", "text": "What service-life period and performance requirements apply to the facility or its major parts?", "kind": "requirement", "answer_data": [ "service_life_period", "performance_requirements", "as_of_time" ] }, { "id": "performance-evaluation-and-service-life-q02", "text": "Has a post-occupancy or implementation evaluation been completed, when, and what outcomes were recorded?", "kind": "quality", "answer_data": [ "poe_status", "poe_time", "outcomes", "deficiencies" ] }, { "id": "performance-evaluation-and-service-life-q03", "text": "Which key performance indicators are governed at facility level, including any indoor environmental quality measures, and what is the current result?", "kind": "measurement", "answer_data": [ "kpi_id", "kpi_value", "measurement_time", "method" ] } ], "data_elements": [ { "id": "performance-evaluation-and-service-life-data01", "name": "Service life", "description": "Period after installation during which the facility or its parts meet performance requirements.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-022" ] }, { "id": "performance-evaluation-and-service-life-data02", "name": "Key performance indicators", "description": "Measures that provide essential information about performance at facility level.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-022" ] }, { "id": "performance-evaluation-and-service-life-data03", "name": "Post-occupancy evaluation status", "description": "Whether and when post-occupancy evaluation has been performed.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-022", "SRC-025" ] } ], "artifacts": [ { "id": "performance-evaluation-and-service-life-artifact01", "name": "Post-occupancy evaluation report", "description": "Analysis of function, comfort and performance after occupation.", "media_or_form": [ "report" ], "serial": true, "identity_strategy": "Report identifier assigned by the appointing or evaluating party; bind to facility master identifier.", "source_refs": [ "SRC-022", "SRC-025" ] } ], "inline_only_rationale": null } ] }, { "id": "maintenance-risk-and-continuity", "name": "Maintenance, Risk and Continuity", "description": "How the facility is maintained, how critical it is, what hazards it faces and how operation continues when it is impaired.", "source_refs": [ "SRC-011", "SRC-016", "SRC-007", "SRC-009", "SRC-015" ], "findings": [ { "id": "maintenance-regime-and-work-management", "name": "Maintenance strategy and work management linkage", "description": "The maintenance strategy applied per system, the planned maintenance tasks and their frequencies, the linkage from work orders back to facility, system and component, and the maintenance backlog with its ageing profile. Handover data schemas carry planned job, resource and event tables that seed this regime at commissioning.", "source_refs": [ "SRC-016", "SRC-011", "SRC-015" ], "questions": [ { "id": "q-strategy", "text": "Which maintenance strategy applies to each facility system, and what evidence justifies the choice?", "kind": "decision", "answer_data": [ "system reference", "strategy code", "justification text", "review date" ] }, { "id": "q-planned-tasks", "text": "Which planned maintenance tasks and frequencies are defined, and from which source were they derived?", "kind": "process", "answer_data": [ "task identifier", "frequency duration", "derivation source reference", "first due date" ] }, { "id": "q-work-order-linkage", "text": "How do work orders resolve back to facility, system and component, and what happens when the component is unknown?", "kind": "relationship", "answer_data": [ "work order reference", "resolution key", "fallback rule text", "unresolved count" ] }, { "id": "q-backlog", "text": "What is the maintenance backlog, how is it aged, and what threshold escalates it to a condition or risk finding?", "kind": "measurement", "answer_data": [ "backlog count", "backlog value", "ageing bucket distribution", "escalation threshold" ] } ], "data_elements": [ { "id": "maintenance-strategy", "name": "Maintenance strategy", "description": "Strategy per system, such as corrective, preventive, condition-based or predictive.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "planned-task-set", "name": "Planned task set", "description": "Planned maintenance tasks with frequency, first due date and derivation source.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-016" ] }, { "id": "work-order-reference", "name": "Work order reference", "description": "Reference into the Work Management model resolved to this facility.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-016" ] }, { "id": "backlog-count", "name": "Maintenance backlog count", "description": "Count of overdue or unexecuted maintenance items at the stated date.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "backlog-as-of", "name": "Backlog as-of date", "description": "Date at which backlog figures were computed.", "value_kind": "date", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "planned-maintenance-schedule", "name": "Planned maintenance schedule", "description": "Schedule of planned maintenance tasks by system with frequency, resource requirements, derivation source and current backlog position.", "media_or_form": [ "maintenance schedule", "handover data table set", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus system reference designation and task identifier; frequency changes are versioned with effective dates.", "source_refs": [ "SRC-016", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "criticality-hazard-and-continuity", "name": "Criticality, hazard exposure and operational continuity", "description": "The facility's criticality or mission-dependency rating and the method behind it, the natural and human-caused hazards it is exposed to, redundancy and alternate-facility arrangements, and when continuity plans were last exercised. Criticality drives both asset-management investment prioritisation and the mission-criticality factor in security-level determination.", "source_refs": [ "SRC-011", "SRC-009", "SRC-007" ], "questions": [ { "id": "q-criticality", "text": "What criticality or mission-dependency rating does the facility carry, derived by which method and reviewed when?", "kind": "classification", "answer_data": [ "criticality rating code", "method reference", "consequence dimensions considered", "review date" ] }, { "id": "q-hazards", "text": "Which natural and human-caused hazards is the facility exposed to, and on what likelihood and severity basis is each assessed?", "kind": "measurement", "answer_data": [ "hazard type code", "likelihood basis", "severity basis", "assessment source reference" ] }, { "id": "q-continuity", "text": "What redundancy, alternate-facility or degraded-mode arrangements exist if the facility becomes unavailable?", "kind": "process", "answer_data": [ "arrangement type code", "alternate facility reference", "recovery time objective", "dependency list" ] }, { "id": "q-exercise", "text": "When were the risk assessment and the continuity plan last reviewed and exercised, and what did the exercise find?", "kind": "evidence", "answer_data": [ "last review date", "last exercise date", "exercise outcome summary", "open action count" ] } ], "data_elements": [ { "id": "criticality-rating", "name": "Criticality rating", "description": "Facility criticality or mission-dependency rating on a declared scale.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011", "SRC-009" ] }, { "id": "criticality-method", "name": "Criticality method", "description": "Named method and version used to derive the criticality rating.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "hazard-exposure-set", "name": "Hazard exposure set", "description": "Hazards with likelihood and severity basis and source of the assessment.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "recovery-time-objective", "name": "Recovery time objective", "description": "Target duration within which facility function must be restored or relocated.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "continuity-plan-reference", "name": "Continuity plan reference", "description": "Reference to the continuity or emergency plan covering this facility.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "last-exercise-date", "name": "Last exercise date", "description": "Date the continuity arrangements were last exercised.", "value_kind": "date", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "risk-and-continuity-assessment", "name": "Facility risk and continuity assessment", "description": "Assessment recording criticality derivation, hazard exposure with likelihood and severity, redundancy and alternate-facility arrangements, recovery objectives and exercise outcomes.", "media_or_form": [ "assessment report", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus assessment date and method; assessments are immutable once approved and superseded by later assessments.", "source_refs": [ "SRC-011", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "fire-life-safety-and-risk", "name": "Fire, life safety and risk", "description": "IfcFacility may carry Pset_SpaceFireSafetyRequirements (fire risk factor, flammable storage, fire exit, sprinkler protection, air pressurization) and Pset_Risk (likelihood, consequence, mitigation). These are facility-scale assertions and do not replace storey- or space-level life-safety design. ISO 41011 emergency preparedness is the capability to mitigate emergency consequences. National fire-code inspection programs such as NFPA 25 or 72 are known omissions as primary sources.", "source_refs": [ "SRC-024", "SRC-022" ], "questions": [ { "id": "fire-life-safety-and-risk-q01", "text": "What fire-risk, sprinkler, exit and related life-safety assertions are made at facility scale, and where is detailed design held?", "kind": "constraint", "answer_data": [ "fire_risk_factor", "sprinkler_protection", "fire_exit_flag", "detailed_design_ref" ] }, { "id": "fire-life-safety-and-risk-q02", "text": "What named risks are assessed for the facility, with unmitigated and mitigated likelihood, consequence and significance?", "kind": "constraint", "answer_data": [ "risk_name", "risk_type", "unmitigated_significance", "mitigated_significance", "mitigation_planned" ] }, { "id": "fire-life-safety-and-risk-q03", "text": "What emergency-preparedness capability is asserted, and what evidence supports it?", "kind": "evidence", "answer_data": [ "preparedness_statement", "evidence_ref", "as_of_time" ] } ], "data_elements": [ { "id": "fire-life-safety-and-risk-data01", "name": "Fire safety requirements", "description": "Facility-scale fire-safety property assertions.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-024" ] }, { "id": "fire-life-safety-and-risk-data02", "name": "Facility risks", "description": "Assessed risks associated with the facility.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-024" ] }, { "id": "fire-life-safety-and-risk-data03", "name": "Emergency preparedness", "description": "Capability to take actions that will effectively mitigate the consequences of an emergency.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-022" ] } ], "artifacts": [ { "id": "fire-life-safety-and-risk-artifact01", "name": "Facility risk and life-safety file", "description": "Facility-scale fire, risk and emergency-preparedness assertions and evidence references.", "media_or_form": [ "risk-register", "safety-file" ], "serial": false, "identity_strategy": "Bind to facility master identifier; version by assessment time.", "source_refs": [ "SRC-024", "SRC-022" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "information-governance-and-interoperability", "name": "Information Governance and Interoperability", "description": "What information about the facility must exist, where it came from, how long it is kept, and how it moves between standards and systems.", "rationale": "Facility data outlives the systems that hold it and is exchanged across construction, operations, regulatory and geospatial domains. Requirements, provenance, retention and alignment must be governed explicitly or the model degrades into an unverifiable snapshot.", "source_refs": [ "SRC-013", "SRC-011", "SRC-008", "SRC-003", "SRC-010", "SRC-016", "SRC-017", "SRC-018" ], "layers": [ { "id": "information-requirements-and-quality", "name": "Information Requirements, Provenance and Quality", "description": "What information is required about the facility, where each value came from, and whether it can be trusted.", "source_refs": [ "SRC-013", "SRC-011", "SRC-005", "SRC-003" ], "findings": [ { "id": "asset-information-requirements-and-deliverables", "name": "Asset information requirements and accepted deliverables", "description": "The organisational, asset and exchange information requirements that apply to this facility, the trigger events during operation that require an information exchange, the asset information model held for the facility, and how information is accepted or rejected. ISO 19650-3 establishes asset information requirements at asset level and exchange information requirements per appointment and trigger event.", "source_refs": [ "SRC-013", "SRC-011", "SRC-016" ], "questions": [ { "id": "q-requirements", "text": "Which organisational and asset information requirements apply to this facility, and which appointment-level exchange requirements derive from them?", "kind": "requirement", "answer_data": [ "requirement reference", "requirement level code", "derived exchange requirement reference", "effective from date" ] }, { "id": "q-triggers", "text": "Which operational trigger events require an information exchange, to whom, and within what deadline?", "kind": "event", "answer_data": [ "trigger event code", "recipient reference", "deadline duration", "exchange format neutrality note" ] }, { "id": "q-aim", "text": "What constitutes the accepted asset information model for this facility, and where is its authoritative copy held?", "kind": "provenance", "answer_data": [ "asset information model reference", "authoritative repository reference", "acceptance timestamp", "accepting role" ] }, { "id": "q-acceptance", "text": "How are information acceptance and rejection recorded, and what happens to rejected deliverables?", "kind": "process", "answer_data": [ "acceptance status code", "rejection reason text", "resubmission deadline", "decision timestamp" ] } ], "data_elements": [ { "id": "information-requirement-reference", "name": "Information requirement reference", "description": "Reference to an organisational, asset or exchange information requirement applying to the facility.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "trigger-event-code", "name": "Trigger event code", "description": "Operational event that obliges an information exchange for this facility.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "asset-information-model-reference", "name": "Asset information model reference", "description": "Reference to the accepted asset information model for the facility.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "acceptance-status", "name": "Information acceptance status", "description": "Status of the most recent information deliverable against requirements.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "accepted-at", "name": "Accepted at", "description": "RFC 3339 time at which information was accepted into the asset information model.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] } ], "artifacts": [ { "id": "asset-information-requirements-specification", "name": "Asset information requirements specification", "description": "Specification of information requirements applying to the facility, mapped to trigger events, responsible appointments, acceptance criteria and the location of the authoritative asset information model.", "media_or_form": [ "requirements specification", "structured record set" ], "serial": false, "identity_strategy": "Keyed by facility identifier plus requirement level and version; supersession recorded with effective dates.", "source_refs": [ "SRC-013", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "provenance-lineage-and-data-quality", "name": "Attribute provenance, source precedence and validation", "description": "Per-attribute lineage to the supplying source system, the precedence rule when sources disagree, the validation rules a facility record must pass before publication, and the confidence attached to matched or derived values. Federated registries demonstrate the need: values are integrated from many program systems, matched, and periodically re-selected by an automated best-pick process.", "source_refs": [ "SRC-005", "SRC-003", "SRC-004", "SRC-011" ], "questions": [ { "id": "q-attribute-lineage", "text": "For each attribute, which source system supplied the value, when was it observed and when was it ingested?", "kind": "provenance", "answer_data": [ "attribute name", "source system reference", "observed at timestamp", "ingested at timestamp" ] }, { "id": "q-precedence", "text": "What precedence rule resolves conflicting values for the same attribute from different sources?", "kind": "decision", "answer_data": [ "precedence rule identifier", "ranked source list", "tie-break rule text", "last applied timestamp" ] }, { "id": "q-validation", "text": "Which validation rules must a facility record pass before publication, and which are blocking versus advisory?", "kind": "validation", "answer_data": [ "validation rule identifier", "severity code", "rule expression summary", "last evaluation timestamp" ] }, { "id": "q-confidence", "text": "What confidence or quality measure accompanies matched, derived or estimated values, and how is it computed?", "kind": "quality", "answer_data": [ "confidence value", "computation method", "applicable attribute list", "review date" ] } ], "data_elements": [ { "id": "attribute-source-system", "name": "Attribute source system", "description": "Source system that supplied a given attribute value.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "source-precedence-rank", "name": "Source precedence rank", "description": "Rank of a source system for a given attribute when values conflict.", "value_kind": "number", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "validation-rule-identifier", "name": "Validation rule identifier", "description": "Identifier of a rule the record must satisfy, with severity.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "validation-status", "name": "Validation status", "description": "Overall validation outcome for the current record version.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "value-confidence", "name": "Value confidence", "description": "Confidence or quality score for matched, derived or estimated values.", "value_kind": "number", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "conflict-note", "name": "Conflict note", "description": "Narrative of an unresolved or manually adjudicated source conflict.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] } ], "artifacts": [ { "id": "provenance-and-validation-report", "name": "Provenance and validation report", "description": "Per-attribute lineage with source system, observation and ingestion times, applied precedence rules, validation results by severity and open conflicts.", "media_or_form": [ "validation report", "lineage table", "structured record set" ], "serial": true, "identity_strategy": "Keyed by facility identifier plus record version and evaluation timestamp; reports are append-only evidence of the state at publication.", "source_refs": [ "SRC-005", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "alignment-retention-and-exchange", "name": "Standards Alignment, Retention and Exchange", "description": "How facility context maps to external standards, how long each record class is kept, and how the model is projected into any storage or interface technology.", "source_refs": [ "SRC-001", "SRC-010", "SRC-016", "SRC-017", "SRC-018", "SRC-008", "SRC-003" ], "findings": [ { "id": "standard-alignments-and-crosswalks", "name": "External standard alignments and crosswalk fidelity", "description": "The external schemas, ontologies and classifications this model is aligned to, at which versions, whether each mapping is lossless, which concepts have no faithful counterpart, and what evidence would be required before asserting conformance. Notably, the widely used building topology vocabulary has no facility class between site and building, and IFC subordinates buildings to facilities by type rather than by aggregation.", "source_refs": [ "SRC-001", "SRC-010", "SRC-016", "SRC-017", "SRC-018", "SRC-003", "SRC-021" ], "questions": [ { "id": "q-targets", "text": "Which external standards is this model aligned to, at what version, and in which direction does each mapping run?", "kind": "interoperability", "answer_data": [ "target standard identifier", "target version", "mapping direction code", "mapping owner reference" ] }, { "id": "q-lossiness", "text": "Which concepts cannot be expressed faithfully in a given target, and what is lost or approximated?", "kind": "interoperability", "answer_data": [ "unmapped concept name", "target standard identifier", "loss description", "workaround note" ] }, { "id": "q-conformance-evidence", "text": "What evidence would be required before claiming conformance rather than alignment to any target standard?", "kind": "evidence", "answer_data": [ "conformance test suite reference", "evidence artifact reference", "claim status code" ] }, { "id": "q-drift", "text": "How is alignment breakage detected when a target standard is revised, and who is accountable for repair?", "kind": "process", "answer_data": [ "monitoring method", "detection cadence", "accountable role", "repair deadline" ] } ], "data_elements": [ { "id": "target-standard-identifier", "name": "Target standard identifier", "description": "Identifier of an external standard, ontology or classification aligned to.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-010", "SRC-016" ] }, { "id": "target-standard-version", "name": "Target standard version", "description": "Exact version or edition of the aligned target.", "value_kind": "text", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-017" ] }, { "id": "mapping-lossy-flag", "name": "Mapping lossy flag", "description": "Whether the mapping to a given target loses or approximates meaning.", "value_kind": "boolean", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-018" ] }, { "id": "unmapped-concept-set", "name": "Unmapped concept set", "description": "Concepts with no faithful counterpart in a named target standard.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-018" ] }, { "id": "conformance-claim-status", "name": "Conformance claim status", "description": "Whether a relationship is asserted as alignment only or as evidenced conformance.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-010" ] } ], "artifacts": [ { "id": "facility-crosswalk-matrix", "name": "Facility crosswalk matrix", "description": "Matrix mapping model concepts to external standard constructs with version, direction, lossiness, unmapped residue and conformance claim status.", "media_or_form": [ "crosswalk matrix", "structured record set" ], "serial": false, "identity_strategy": "Keyed by model concept identifier plus target standard identifier and version; a new target version creates a new mapping row rather than editing the old one.", "source_refs": [ "SRC-001", "SRC-010", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "retention-disposition-and-archival", "name": "Retention, disposition and archival transfer", "description": "Which retention schedule governs each class of facility record, the disposition trigger and period, which records are permanent rather than temporary, and how destruction is evidenced. Government-wide scheduling treats routine facility operation and maintenance records as temporary with destruction three years after creation or supersession, while requiring the oldest records be offered for archival transfer before any disposition is applied.", "source_refs": [ "SRC-008", "SRC-006" ], "questions": [ { "id": "retention-disposition-and-archival-q-schedule", "text": "Which retention schedule and item governs each class of facility record, and what is the disposition trigger and period?", "kind": "retention", "answer_data": [ "record class code", "schedule item reference", "disposition trigger code", "retention period duration" ] }, { "id": "q-permanent", "text": "Which facility records are permanent or must be offered for archival transfer, and on what criterion?", "kind": "retention", "answer_data": [ "record class code", "permanence determination", "transfer criterion text", "transfer due date" ] }, { "id": "q-life-of-structure", "text": "Which records must be retained for the life of the structure plus a defined period, and how is that end date computed?", "kind": "retention", "answer_data": [ "record class code", "end-date computation rule", "dependent lifecycle event reference" ] }, { "id": "q-destruction-evidence", "text": "How is destruction authorised and evidenced, and what residual metadata survives it?", "kind": "evidence", "answer_data": [ "authorising role", "destruction certificate reference", "destruction timestamp", "surviving metadata list" ] } ], "data_elements": [ { "id": "record-class", "name": "Record class", "description": "Class of facility record for retention purposes.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-008" ] }, { "id": "retention-schedule-reference", "name": "Retention schedule reference", "description": "Reference to the governing schedule and item.", "value_kind": "reference", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-008" ] }, { "id": "disposition-trigger", "name": "Disposition trigger", "description": "Event that starts the retention clock, such as creation, supersession or facility disposal.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-008" ] }, { "id": "retention-period", "name": "Retention period", "description": "Duration for which the record class must be retained after the trigger.", "value_kind": "duration", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "disposition-action", "name": "Disposition action", "description": "Action at end of retention, such as destroy or transfer to archives.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-008" ] }, { "id": "destruction-evidence-reference", "name": "Destruction evidence reference", "description": "Reference to the certificate or log evidencing authorised destruction.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [ { "id": "records-disposition-register", "name": "Records disposition register", "description": "Register of facility record classes with governing schedule item, trigger, period, disposition action, executed dispositions and destruction evidence.", "media_or_form": [ "disposition register", "structured record set" ], "serial": true, "identity_strategy": "Keyed by facility identifier plus record class and disposition sequence; entries are append-only and destruction entries are never removed.", "source_refs": [ "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "exchange-packaging-and-interface-neutrality", "name": "Canonical payload, packaging and interface neutrality", "description": "The canonical logical payload of a facility record independent of any serialisation, how artifacts are packaged and integrity-checked, how partial updates are expressed and validated, and the bootstrap manifest that must accompany any store. Handover schemas that publish equivalent content as spreadsheet, model-file and JSON demonstrate that meaning must be defined before format.", "source_refs": [ "SRC-016", "SRC-010", "SRC-013" ], "questions": [ { "id": "q-canonical-payload", "text": "What is the canonical logical payload of a facility record, independent of document, graph, relational or document-database projection?", "kind": "interoperability", "answer_data": [ "canonical payload reference", "required element list", "projection-independent constraint list" ] }, { "id": "q-packaging", "text": "How are artifacts packaged, integrity-checked and referenced from the facility record?", "kind": "interoperability", "answer_data": [ "package structure description", "checksum algorithm", "artifact reference form", "package manifest reference" ] }, { "id": "q-patching", "text": "How are partial updates expressed, ordered and validated against the canonical payload?", "kind": "process", "answer_data": [ "patch operation set", "ordering rule", "validation gate reference", "conflict resolution rule" ] }, { "id": "q-bootstrap", "text": "What agent bootstrap contract must accompany any store or interface exposing this model?", "kind": "interoperability", "answer_data": [ "bootstrap manifest reference", "required field list", "read order list", "last verified timestamp" ] } ], "data_elements": [ { "id": "canonical-payload-reference", "name": "Canonical payload reference", "description": "Reference to the projection-independent logical payload definition for a facility record.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-010", "SRC-016" ] }, { "id": "projection-format", "name": "Projection format", "description": "A concrete storage or interface projection in use, declared as a projection rather than a semantic.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-016" ] }, { "id": "artifact-checksum", "name": "Artifact checksum", "description": "Integrity digest for a packaged artifact, with the algorithm named.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-016" ] }, { "id": "patch-operation-set", "name": "Patch operation set", "description": "Ordered set of additive, replacement or removal operations expressed against the canonical payload.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "bootstrap-manifest-reference", "name": "Bootstrap manifest reference", "description": "Reference to the AGENTS.md bootstrap contract for the store exposing this model.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-013" ] } ], "artifacts": [ { "id": "facility-exchange-package", "name": "Facility exchange package", "description": "Self-describing package containing the canonical facility payload, referenced artifacts with checksums, the applicable crosswalk rows and the bootstrap manifest, renderable into any chosen projection.", "media_or_form": [ "exchange package", "handover data table set", "structured record set", "graph serialisation" ], "serial": true, "identity_strategy": "Keyed by facility identifier plus package sequence and RFC 3339 creation timestamp; each package is immutable and integrity-verifiable by its manifest digest.", "source_refs": [ "SRC-016", "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-facility", "name": "Register facility", "description": "Create a governed facility record with an authoritative identifier, minimal classification, containment and initial lifecycle state.", "inputs": [ "candidate facility descriptor", "proposed identifier or issuing authority", "containing site reference where applicable", "asserting party and authority basis" ], "outputs": [ "facility record version 1", "assigned facility identifier", "identifier register entry", "creation event log entry" ], "preconditions": [ "Identity resolution has been run and no existing facility matches above the adjudication threshold", "An issuing authority for the identifier scheme is named", "Country and coordinate reference system are supplied" ], "effects": [ "A new persistent facility identifier is assigned and recorded as never-reusable", "An append-only creation event is written with event time and ingestion time", "Downstream registries are notified of the new identifier" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-003" ] }, { "id": "resolve-facility-identity", "name": "Resolve facility identity", "description": "Match an inbound facility assertion against existing records using name, address, coordinates and programme identifiers, returning a match, a candidate set or a no-match decision with confidence.", "inputs": [ "inbound facility assertion", "match rule set and thresholds", "reference registry snapshot" ], "outputs": [ "match decision code", "matched facility identifier or candidate set", "match confidence value", "adjudication record" ], "preconditions": [ "Inbound assertion carries at least one location or identifier attribute", "Match rules and thresholds are versioned and published" ], "effects": [ "An adjudication record is appended with the rule version and confidence", "Below-threshold matches are queued for human adjudication rather than auto-merged", "Merge or split decisions emit successor identifier links" ], "source_refs": [ "SRC-005", "SRC-004" ] }, { "id": "classify-facility", "name": "Classify facility", "description": "Assign functional, reporting and code occupancy classifications to the facility in each adopted scheme, with precedence per downstream purpose.", "inputs": [ "facility identifier", "scheme identifiers and versions", "use and area evidence", "authority having jurisdiction determination where applicable" ], "outputs": [ "classification assignment set", "crosswalk table rows", "classification effective-from date" ], "preconditions": [ "Primary function evidence is available", "Each scheme version in use is declared" ], "effects": [ "Classification changes trigger review of permits, benchmarking baseline and occupancy determination", "Prior classifications are retained with end dates rather than overwritten" ], "source_refs": [ "SRC-019", "SRC-021", "SRC-020", "SRC-001" ] }, { "id": "assemble-facility-composition", "name": "Assemble facility composition", "description": "Bind the facility to its containing site, its facility parts, its member buildings and structures, and its engineered systems, applying an explicit decomposition convention.", "inputs": [ "facility identifier", "site reference", "building and structure references", "decomposition convention", "system reference designations" ], "outputs": [ "facility breakdown structure", "membership assertions with validity windows", "system register entries" ], "preconditions": [ "A decomposition convention has been selected and justified", "Member references resolve to governed model instances" ], "effects": [ "Non-exclusive memberships are flagged and given an apportionment basis", "Breakdown depth beyond the declared terminal level is rejected and routed to the Building or Space model" ], "source_refs": [ "SRC-002", "SRC-001", "SRC-016", "SRC-018" ] }, { "id": "record-lifecycle-transition", "name": "Record lifecycle transition", "description": "Record a change of lifecycle phase or operational status as an event with separate event, observation and ingestion times, and the evidence and authority behind it.", "inputs": [ "facility identifier", "target phase and status codes", "event time", "supporting evidence reference", "asserting party" ], "outputs": [ "milestone event log entry", "updated status fields", "new record version" ], "preconditions": [ "The transition is permitted from the current state", "Event time carries an explicit offset or Z", "The asserting party holds authority for the transition" ], "effects": [ "Terminal transitions retain surviving regulatory and retention obligations", "Handover into operation triggers the applicable information exchange requirements" ], "source_refs": [ "SRC-015", "SRC-013", "SRC-003" ] }, { "id": "assess-condition-and-risk", "name": "Assess condition and risk", "description": "Record a condition assessment, service-life estimate, criticality rating and hazard exposure for the facility, attributable to a named method and assessor.", "inputs": [ "facility identifier", "assessment method and version", "inspection observations", "criticality method", "hazard source data" ], "outputs": [ "condition assessment report", "criticality rating", "hazard exposure set", "reassessment due date" ], "preconditions": [ "Assessor competence is evidenced", "Method version is declared and its scale is published" ], "effects": [ "Backlog above the escalation threshold raises a maintenance and investment finding", "Criticality changes propagate to the security-level mission-criticality factor" ], "source_refs": [ "SRC-015", "SRC-007", "SRC-011", "SRC-009" ] }, { "id": "verify-regulatory-standing", "name": "Verify regulatory standing", "description": "Check that programme interests, permits, statutory inspections and certificates are current for the facility and surface expiries and open nonconformities.", "inputs": [ "facility identifier", "programme interest set", "permit and certificate references", "evaluation date" ], "outputs": [ "regulatory standing summary", "expiry and overdue list", "open nonconformity list" ], "preconditions": [ "Programme interests are mapped to competent regulators", "Permit validity windows are populated" ], "effects": [ "Expired or missing authorisations block publication of an operational status of in-use without an explicit exception", "Overdue statutory inspections raise a compliance exception with an owner and deadline" ], "source_refs": [ "SRC-005", "SRC-011", "SRC-020" ] }, { "id": "publish-facility-performance", "name": "Publish facility performance", "description": "Compute and publish capacity, utilisation and resource performance for a reporting period with declared boundary, normalisation, metered share and provenance.", "inputs": [ "facility identifier", "reporting period", "meter and estimate inputs", "area and occupancy measures", "normalisation and benchmark reference" ], "outputs": [ "performance benchmark report", "benchmark score", "metering boundary declaration", "provenance and validation report" ], "preconditions": [ "Metering boundary is declared relative to the facility extent", "Gross floor area and operating hours are present and dated" ], "effects": [ "Restatements create a new report version citing the superseded one and notify downstream consumers", "Estimated shares above the declared threshold mark the figures as advisory" ], "source_refs": [ "SRC-019", "SRC-005", "SRC-011" ] }, { "id": "apply-disclosure-controls", "name": "Apply disclosure controls", "description": "Produce a release projection of the facility record with sensitivity markings applied, attributes withheld or generalised, exceptions honoured and access logged.", "inputs": [ "facility record version", "sensitivity markings by scope", "redaction and generalisation rules", "requesting identity and purpose" ], "outputs": [ "release projection", "redaction manifest", "access log entry" ], "preconditions": [ "Every scope carries a sensitivity marking", "The requesting identity is authenticated and its role is resolved" ], "effects": [ "Withheld attributes are recorded as withheld with a legal basis rather than silently omitted", "Geometry precision reduction is applied before any public release", "An access log entry is written for restricted content" ], "source_refs": [ "SRC-006", "SRC-009" ] }, { "id": "export-facility-exchange-package", "name": "Export facility exchange package", "description": "Render the canonical facility payload and its artifacts into a chosen projection with crosswalk rows, integrity digests and the required bootstrap manifest.", "inputs": [ "facility identifier and record version", "target projection", "crosswalk selection", "artifact set" ], "outputs": [ "facility exchange package", "package manifest with digests", "AGENTS.md bootstrap file", "conformance claim status statement" ], "preconditions": [ "Record version has passed blocking validation rules", "Target standard versions in the crosswalk are current" ], "effects": [ "Packages are immutable and integrity-verifiable", "Lossy mappings are declared in the manifest rather than silently applied", "No conformance is asserted without a cited evidence artifact" ], "source_refs": [ "SRC-016", "SRC-010", "SRC-013" ] }, { "id": "authorize-or-record-occupancy", "name": "Authorize or record occupancy", "description": "Record a certificate of occupancy or equivalent AHJ authorization, including occupancy classification, code edition, occupant load and authorized portion.", "inputs": [ "facility or portion identifier", "AHJ", "certificate contents", "issued time" ], "outputs": [ "occupancy authorization status", "certificate artifact" ], "preconditions": [ "The object is a building or structure, or another facility type with a defined occupancy AHJ.", "Change of occupancy is not asserted without a new authorization." ], "effects": [ "Legal occupancy state is updated.", "Unauthorized occupation remains prohibited in the model." ], "source_refs": [ "SRC-028", "SRC-024" ] }, { "id": "handover-to-operations", "name": "Handover to operations", "description": "Transfer relevant project information into the operational asset information model, mark the facility in-service after commissioning, and accept information containers in the CDE.", "inputs": [ "facility identifier", "PIM reference", "AIR and OIR", "commissioning evidence" ], "outputs": [ "AIM reference", "in-service flag", "acceptance status" ], "preconditions": [ "Appointing party has specified operational information requirements.", "Information containers have been checked against the level of information need." ], "effects": [ "Operational phase information management is active.", "Facility-in-service may be asserted if commissioning and handover are complete." ], "source_refs": [ "SRC-025", "SRC-023" ] }, { "id": "transfer-ownership-and-aim", "name": "Transfer ownership and AIM", "description": "Record a change of owner or operator, run due diligence, transfer the AIM, and keep identity stable across the transaction.", "inputs": [ "facility identifier", "new owner or operator", "due diligence package", "AIM containers" ], "outputs": [ "updated party roles", "AIM transfer status", "due diligence gaps" ], "preconditions": [ "Incoming party is identified.", "Security-minded handling is applied if required." ], "effects": [ "Party-role history gains a new interval.", "Information continuity is attempted; gaps are recorded rather than silently dropped." ], "source_refs": [ "SRC-025", "SRC-022", "SRC-004" ] } ], "composition": [ { "target": "WM-BLT-008 Site", "relation": "REFERENCE", "purpose": "Bind the facility to its containing site or sites for georeference, tenure context and portfolio rollup, while leaving parcel and land-tenure semantics in the Site model. Modelled as conditional because a facility may be the outermost spatial container.", "required": false, "source_refs": [ "SRC-001", "SRC-018" ] }, { "target": "WM-BLT-001 Building", "relation": "CHILD", "purpose": "Aggregate the buildings and structures that constitute the facility, with membership validity and exclusivity, delegating fabric, storeys and envelope to the Building model.", "required": false, "source_refs": [ "SRC-002", "SRC-018", "SRC-016" ] }, { "target": "Space / Room model", "relation": "REFERENCE", "purpose": "Reference interior spaces and zones for area totals, service relationships and occupancy without duplicating space geometry or assignment.", "required": false, "source_refs": [ "SRC-016", "SRC-010" ] }, { "target": "Equipment / Asset-item model", "relation": "REFERENCE", "purpose": "Link the facility to component-level asset records via a declared linkage key, with register coverage and inventory recency held here and item detail held there.", "required": false, "source_refs": [ "SRC-016", "SRC-011" ] }, { "target": "Organization / Party model", "relation": "REFERENCE", "purpose": "Resolve owner, custodian, demand organisation, service provider, regulator and assessor roles to governed party identifiers with validity windows.", "required": true, "source_refs": [ "SRC-012", "SRC-007" ] }, { "target": "Authorization / Permit model", "relation": "REFERENCE", "purpose": "Attach permits, licences and programme authorisations to the facility by reference, keeping instrument text, conditions and issuance workflow in the Authorization model.", "required": false, "source_refs": [ "SRC-005", "SRC-004" ] }, { "target": "Address / Location model", "relation": "REFERENCE", "purpose": "Resolve role-tagged addresses and administrative units without embedding address parsing or address-point authority.", "required": false, "source_refs": [ "SRC-004", "SRC-003" ] }, { "target": "Work Management model", "relation": "REFERENCE", "purpose": "Resolve work orders, jobs and resources back to facility and system so that maintenance backlog and history are computable without duplicating execution records.", "required": false, "source_refs": [ "SRC-016", "SRC-011" ] }, { "target": "Measurement / Observation mixin", "relation": "MIX-IN", "purpose": "Supply the common pattern of value, unit, method, observation time and ingestion time used by condition, area, occupancy and resource-performance findings.", "required": true, "source_refs": [ "SRC-019", "SRC-005", "SRC-003" ] }, { "target": "Bitemporal versioning mixin", "relation": "MIX-IN", "purpose": "Supply record validity bounds, real-world validity, change kind and supersession semantics applied uniformly across facility findings.", "required": true, "source_refs": [ "SRC-003", "SRC-010" ] }, { "target": "IFC 4.3 spatial structure (IfcFacility, IfcFacilityPart)", "relation": "ALIGN", "purpose": "Align facility identity, composition and placement with the IFC spatial structure. Alignment only: IFC subordinates IfcBuilding to IfcFacility by subtyping, whereas this model aggregates buildings under a facility.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "OGC CityGML 3.0 Conceptual Model", "relation": "ALIGN", "purpose": "Align geometry, level of detail and city-object versioning for geospatial exchange and digital-twin use, independent of GML or any other encoding.", "required": false, "source_refs": [ "SRC-010" ] }, { "target": "COBie V3 (NBIMS-US)", "relation": "ALIGN", "purpose": "Align facility handover content with the Facility, Level, Space, Zone, Type, Component, System, Job and Document tables so construction-to-operations exchange is lossless in the covered subset.", "required": false, "source_refs": [ "SRC-016" ] }, { "target": "INSPIRE Buildings data specification", "relation": "ALIGN", "purpose": "Align persistent identifiers, lifespan versioning and construction-condition semantics for European geospatial publication.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "ETSI SAREF4BLDG and W3C BOT", "relation": "ALIGN", "purpose": "Align to linked-data building vocabularies for graph projection. Recorded as partial: neither vocabulary offers a facility class between site and building, so facility identity must be carried by an extension term.", "required": false, "source_refs": [ "SRC-017", "SRC-018" ] }, { "target": "ISO 55001 asset management system", "relation": "ALIGN", "purpose": "Align the facility asset register, criticality, life-cycle decision-making and documented-information requirements with the asset management system that governs the portfolio.", "required": false, "source_refs": [ "SRC-011" ] }, { "target": "ISO 19650-3 operational information management", "relation": "ALIGN", "purpose": "Align information requirements, trigger events and asset information model acceptance with the operational-phase information management process.", "required": false, "source_refs": [ "SRC-013" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "A Dimension adopting WM-BLT-006 must name a single accountable facility or infrastructure owner-operator package and a named data steward role before any facility record is published.", "The owner package must declare its identifier scheme, issuing authority and non-reuse policy, and must state which external registry (for example an environmental facility registry or a real-property inventory) it treats as the authoritative master for identity.", "The owner package must publish its adopted code lists and versions for lifecycle phase, operational status, legal interest, classification schemes and sensitivity markings, and must version them independently of the model.", "The owner package must define the terminal decomposition level at which responsibility passes to the Building, Space and Equipment models, and must reject deeper structure at validation time.", "The owner package must nominate the retention schedule authority applicable in its jurisdiction and map every artifact class in this model to a schedule item." ], "namespace_guidance": "Use a stable, resolvable namespace under the adopting Dimension, segmented by record plane and model, for example {dimension-root}/world-model/wm-blt-006/{facility-identifier}. Node identifiers within the model are lower-kebab-case and stable for the life of the model; renaming a node requires a new identifier plus an explicit supersession link. External identifiers keep their issuing authority's namespace and are never rewritten into the local namespace. Where linked-data projection is used, mint facility IRIs in the Dimension namespace and relate them to external vocabularies by alignment properties rather than by asserting equivalence.", "registry_links": [ "vr.wm-blt-006 is the registry entry of record for this model; nav path NAV.PHY.BLT.FAC and domain tags PHY.BLT.FAC are the authoritative navigation keys.", "Relation edges to WM-BLT-008 (Site contains Facility) and WM-BLT-001 (Facility contains Building) are maintained in planning/VERCY-MODEL-RELATIONS.csv and must be updated in the same change as any composition change here.", "Sibling models referenced but not owned (Organization, Address, Authorization, Equipment, Space, Work Management) must be registered before a Dimension may assert the corresponding REFERENCE links as required." ] }, "canon_and_patch": { "canonicalization_rules": [ "The canonical form is the logical payload defined by this model, not any serialisation. JSON, YAML, Markdown, HTML, Git, MCP and MongoDB are projections and must round-trip the canonical payload without semantic loss.", "Property order is not semantic; canonical comparison sorts object members by identifier and orders collections by their declared natural key, falling back to identifier then observation time.", "All time values are RFC 3339 with seconds and an explicit numeric offset or Z; no local-time-without-offset values are canonical, and dates that are genuinely partial use the declared partial-date structure rather than a padded timestamp.", "Quantities are canonical only with an explicit unit and, where applicable, a measurement method and standard reference; bare numbers for area, energy and monetary values are rejected.", "Geometry is canonical only with an explicit coordinate reference system and, where vertical values are present, a vertical datum.", "Empty, null and absent are distinct: absent means not asserted, null means asserted as unknown, and a withheld marker means asserted but not disclosed." ], "patch_rules": [ "Patches are expressed as ordered operations against canonical paths and must declare whether each operation is a real-world change or a correction of a prior error.", "Every patch carries the base record version it applies to; a patch against a superseded version is rejected rather than rebased automatically.", "Patches never mutate append-only artifacts (event log, version history, provenance report, disposition register, exchange packages); corrections to those are appended as new entries citing the corrected sequence.", "Identifier fields are not patchable. Changing identity requires a merge or split event that emits successor links and preserves both prior identifiers as non-reusable.", "A patch that would change classification, occupancy group, legal interest, security level or sensitivity marking requires the authority named for that finding and is rejected without it.", "Patches must pass all blocking validation rules before commit; advisory rule failures are recorded on the resulting version rather than blocking it." ], "compatibility_rules": [ "Adding an optional finding, question, data element or artifact is a minor change. Removing one, tightening cardinality, making an element required, or narrowing a code list is a breaking change.", "Code list values may be added in a minor change; retiring a value requires deprecation with an end date and a documented successor value, and existing records retain the retired value with their original validity.", "External standard alignments are versioned independently of the model; a target standard revision creates a new crosswalk row and never edits an existing one.", "Consumers must ignore unknown members in a projection rather than fail, but must not infer meaning for members absent from the canonical payload.", "No conformance to an external standard is claimed at any version without a cited evidence artifact; alignment claims are the default and must be labelled as such." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier issued by the system of record for the facility, such as a real-property inventory unique identifier or an environmental facility registry identifier.", "Governed global identifier or IRI issued by a recognised registry or minted in the adopting Dimension's resolvable namespace under a published minting policy.", "UUID or ULID assigned by the adopting Dimension, used only when neither of the above exists, and recorded together with the reason no governed identifier was available.", "A date, a name, an address, a coordinate pair and a reference designation are never identifiers. Reference designations under ISO 81346-12 denote positions in an aspect structure and expressly exclude serial and inventory numbering." ], "timestamp_rule": "All timestamps are RFC 3339 with seconds precision and an explicit numeric UTC offset or Z. Event time, observation time and ingestion time are recorded as separate fields wherever they can differ, and a value asserted with only one of them must declare which one it is.", "serial_naming_rule": "Serial artifacts are named {facility-identifier}--{artifact-id}--{zero-padded-sequence}--{RFC-3339-creation-timestamp}. Sequences are monotonic per facility and artifact class, never reused, and gaps must be explained by a recorded void entry rather than silently closed.", "integrity_rule": "Every artifact carries a named digest algorithm and digest value in its package manifest. Immutable artifacts (event logs, version histories, assessments once approved, issued certificates, exchange packages) are verified on read and on export; a digest mismatch blocks use and raises a provenance exception rather than being repaired in place. Artifacts are referenced from records by identifier plus digest, never by mutable path alone." }, "policies": [ "Alignment is the default relationship to any external standard. Conformance is asserted only where a cited evidence artifact from a test suite or accredited assessment exists, and the claim carries the exact target version.", "Identity is never inferred from name, address or coordinates alone. Automated matching below the published adjudication threshold produces a candidate set for human decision, and every merge or split is an auditable event with successor links.", "No facility attribute is published without its provenance: source system, observation time and ingestion time. Values that are estimated, derived or matched carry a confidence measure and are labelled as such in every projection.", "Sensitivity marking is mandatory at bundle, layer, finding and artifact scope. Withheld attributes are disclosed as withheld with a legal basis; silent omission is prohibited because it is indistinguishable from absence of data.", "Retention is scheduled per record class against a named jurisdictional authority. Destruction requires authorisation and leaves an auditable destruction record; records eligible for archival transfer are offered before any disposition is applied.", "Boundary discipline is enforced: a change that would add parcel tenure, building fabric, room geometry, component detail or party registration data to this model is rejected and routed to the owning sibling model.", "Do not treat a certificate of occupancy as exhausting fire-code, environmental-program or information-security duties.", "Do not merge facility records solely on similar names or ZIP-centroid coordinates.", "Do not classify a single equipment asset or an unbuilt nature preserve as a facility.", "Apply security-minded handling to location, occupancy, risk and system fields of high-security facilities.", "Keep Site, Building, Asset, Party and Infrastructure in sibling models; reference them with typed edges." ], "crud": { "read": [ "Read is scoped by sensitivity marking at bundle, layer, finding and artifact level; a reader receives a projection with withheld markers rather than a silently reduced record.", "Historic reads are answerable as-of a record version time and as-of a real-world date, and the two must be requestable independently.", "Reads of restricted content are logged with subject identity, scope, purpose and RFC 3339 timestamp.", "Public projections apply geometry precision reduction and the published redaction rule set before release." ], "create": [ "Creation requires a resolved identity decision, a named issuing authority for the identifier, country and coordinate reference system, lifecycle phase, operational status and a sensitivity marking.", "Creation is refused where identity resolution returns a match above the adjudication threshold; the caller must instead amend the existing facility or raise a split decision.", "Creation writes version 1 plus a creation event carrying event time, ingestion time and the asserting party." ], "update": [ "Updates are versioned, never destructive. Each new version declares change kind (real-world change or correction) and cites the version it supersedes.", "Updates to classification, occupancy group, legal interest, security level or sensitivity marking require the authority named in the corresponding finding.", "Updates that fail a blocking validation rule are rejected with the failing rule identifiers; advisory failures are attached to the resulting version.", "Bulk updates from a source system are applied under the published precedence rules and never overwrite a higher-precedence value." ], "delete": [ "Facility records are not deleted while any retention obligation or surviving regulatory obligation is open; decommissioning is a lifecycle transition, not a deletion.", "Logical deletion sets an end of real-world validity and an end of record validity, retaining the identifier as permanently non-reusable.", "Physical destruction occurs only under an authorised disposition action, is evidenced by a destruction record, and retains the minimum tombstone metadata (identifier, record class, schedule item, disposition date, authorising role).", "Deletion requests that would break a referenced edge from a sibling model are refused until the referencing model has been updated." ] }, "roles": [ { "name": "Facility owner-operator (accountable owner)", "responsibilities": [ "Owns the model instance for a given facility and accepts accountability for its accuracy and completeness.", "Approves lifecycle transitions, legal interest changes and disposal decisions.", "Nominates the data steward and the named accountable persons for statutory duties." ] }, { "name": "Facility data steward", "responsibilities": [ "Maintains identifier assignment, cross-registry references and the deduplication adjudication queue.", "Publishes and versions code lists, validation rules, match thresholds and source precedence.", "Runs periodic reconciliation against external registries and records unresolved conflicts." ] }, { "name": "Information manager", "responsibilities": [ "Maintains organisational, asset and exchange information requirements and the trigger-event calendar.", "Accepts or rejects information deliverables into the asset information model and records the decision.", "Owns the canonical payload definition, crosswalk matrix and exchange packaging rules." ] }, { "name": "Compliance and records officer", "responsibilities": [ "Maintains programme interests, permits, statutory inspection schedules and open nonconformities.", "Maps every artifact class to a retention schedule item and executes authorised dispositions with evidence.", "Escalates expired authorisations and overdue statutory inspections to the accountable owner." ] }, { "name": "Security and disclosure authority", "responsibilities": [ "Determines and reviews the facility security level and required protective measures.", "Assigns sensitivity markings at bundle, layer, finding and artifact scope and approves redaction rules.", "Grants, time-bounds and reviews access exceptions, and reviews the access audit log." ] }, { "name": "Consuming agent (automated)", "responsibilities": [ "Reads AGENTS.md before any other file and follows the declared read order.", "Treats absent, null and withheld as distinct and never infers values for withheld or absent attributes.", "Refuses to assert conformance, identity matches or performance figures without the accompanying provenance and evidence references." ] } ], "access": { "default_rule": "Deny by default. Access is granted per scope (bundle, layer, finding, artifact) to an authenticated identity holding a role explicitly bound to that scope's sensitivity marking, for a declared purpose. Facility information is not presumed public: statutory real-property publication regimes expressly authorise excluding assets for national-security reasons and under freedom-of-information exemptions, so the model treats openness as a per-scope decision rather than a default.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency response: the emergency-response address, representative point, occupant population, hazard classification and utility demarcation points are released to a recognised emergency service on assertion of an incident, with post-hoc logging rather than prior approval.", "Statutory disclosure: regulatory programme interests, permit references and required environmental or energy disclosures are released to the competent regulator regardless of internal marking, limited to the attributes the obligation names.", "Security-restricted attributes: security level determination, countermeasure status, detailed floor geometry and critical-system demarcation are withheld from public projections and released only under a time-bounded exception granted by the security and disclosure authority.", "National-security and freedom-of-information exclusions: whole facilities may be excluded from public inventory publication, in which case the exclusion itself and its legal basis are recorded even though the record is not released.", "Research and benchmarking: aggregate or generalised projections (coarsened geometry, banded areas, banded occupancy) may be released where the release cannot re-identify a restricted facility, subject to a documented re-identification assessment.", "High-security and high-security-zone facilities may omit or coarsen address and coordinates.", "Personal contact data in affiliations is privacy-restricted.", "Alleged compliance status must be labelled as alleged where not adjudicated.", "Indian-country and similar jurisdictional flags are visible to authorized program roles and may be restricted in public projections." ], "audit_requirements": [ "Log every read, export and share of restricted-marked content with subject identity, scope reference, declared purpose, projection produced and RFC 3339 timestamp.", "Log every access-exception grant with granting role, justification, scope, expiry timestamp and the revocation or expiry event.", "Log every merge, split, identifier assignment and sensitivity-marking change as an immutable event with the asserting party.", "Log every disposition action with the schedule item, authorising role and destruction or transfer evidence reference.", "Retain audit logs at least as long as the longest retention obligation applying to the facility record classes they cover, and verify their integrity digests on read.", "Record who read or changed security-minded, identity-merge, occupancy-authorization and owner-transfer fields, with event time and ingestion time.", "Steward merge and split decisions are immutable audit artifacts." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Model ID and registry ID", "Canonical payload and canonicalization rules URL", "Sensitivity marking and access policy URL", "Retention schedule authority URL", "Crosswalk matrix URL and conformance claim status", "Contact or accountable owner reference", "Last verified RFC 3339 timestamp" ], "read_order": [ "AGENTS.md — read first and in full before any other artifact, including when the store is a database or an MCP server rather than a file tree.", "Specification URL — the model definition, bundle and layer structure, findings and required data elements.", "Storage type URL — how the canonical payload is projected into the actual store, and which projection-specific constraints apply.", "Interface URL — the read, create, update and delete operations exposed, their scopes and their authentication requirements.", "Processes URL — the governed functions, their preconditions and effects, and the approval authorities for restricted transitions.", "Sensitivity marking and access policy — before requesting or rendering any facility attribute.", "Crosswalk matrix and conformance claim status — before mapping content into or out of any external standard." ] } }, "coverage": { "claim": "Merged model covers the context an agent needs to identify, classify, compose, operate, evidence, govern and exchange a built facility as an operationally managed aggregate, using the Claude result as base (explicit in/out-of-scope lists keyed to named sibling models, eight sourced boundary notes, bitemporal and retention discipline) plus five Grok findings for facility eligibility and non-building/mobile cases, AHJ occupancy authorization, alleged-versus-adjudicated compliance status, facility-scale fire and life safety, and post-occupancy evaluation. Bounded to the facility aggregate only: Site, Building, Space, Equipment, Organization, Authorization, Address and Work Management remain sibling models. No claim of universal, cross-jurisdiction or metaphysical completeness is made; code lists remain Dimension-declared.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Master-system key, governed external registry identifiers, non-reuse, merge and split, and match confidence are grounded in the EPA Facility Site Identification Data Standard, the FRS registry pattern and INSPIRE persistent-identifier rules. Reference designations are explicitly excluded from identity because ISO 81346-12 excludes serial and inventory numbering from its scope." }, { "dimension": "lifecycle", "status": "covered", "notes": "Phase set from ISO 15686-1, operational status from real-property inventory and INSPIRE construction-condition semantics, handover and trigger events from ISO 19650-3, terminal states with surviving obligations. Gap: no primary source consulted supplies a single normative facility status code list, so the model requires the adopting Dimension to declare and version its own." }, { "dimension": "relationships", "status": "covered", "notes": "Site containment (conditional, because IFC allows a facility as outermost container), facility part decomposition with a mandatory usage convention, building membership with validity and exclusivity, system-to-space service edges, and typed references to seven sibling models." }, { "dimension": "temporal", "status": "covered", "notes": "Bitemporal discipline with record validity bounds, real-world validity, event time, observation time and ingestion time; RFC 3339 with explicit offset mandated; partial dates handled by a declared structure rather than padding; correction versus real-world change distinguished explicitly." }, { "dimension": "provenance", "status": "covered", "notes": "Per-attribute source system, precedence ranking, match confidence, estimated versus metered shares and restatement handling, modelled on the federated-registry integration and best-pick pattern and on benchmarking data-quality practice." }, { "dimension": "ownership", "status": "covered", "notes": "Legal interest, title holder, custodial control and encumbrances separated from operating accountability; the demand-organisation to service-provider distinction is taken from ISO 41011 facility-management vocabulary." }, { "dimension": "validation", "status": "covered", "notes": "Blocking versus advisory rules, publication gate, canonical-form constraints (unit required, CRS required, offset required), reconciliation tolerances for apportioned area, and deduplication adjudication thresholds." }, { "dimension": "access", "status": "covered", "notes": "Deny-by-default with per-scope sensitivity markings across bundle, layer, finding and artifact; five named exception classes including emergency response and statutory disclosure; audit obligations. Grounded in the statutory authority to exclude federal real property from publication for national-security and FOIA-exemption reasons, and in the ISC security-level standard." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Record classes mapped to schedule items with trigger, period and disposition action; decommissioning modelled as a lifecycle transition rather than deletion; tombstone metadata preserved; archival-offer obligation before disposition. Grounded in NARA GRS 5.4 (Transmittal 35, May 2024)." }, { "dimension": "interoperability", "status": "covered", "notes": "Alignments to IFC 4.3, CityGML 3.0, COBie V3, INSPIRE Buildings, SAREF4BLDG, BOT, ISO 55001 and ISO 19650-3, each versioned, direction-tagged and lossiness-flagged, with conformance withheld absent cited evidence." }, { "dimension": "classification", "status": "covered", "notes": "Functional and reporting classification with per-purpose precedence, plus legally consequential code occupancy classification asserted by an authority having jurisdiction. Uniclass Complexes versus Entities is recorded as a granularity decision rather than a fixed mapping." }, { "dimension": "spatial", "status": "covered", "notes": "Representative point, extent geometry, CRS and vertical datum, accuracy, level of detail, relative versus absolute placement, addressing roles and jurisdictional straddling." }, { "dimension": "measurement", "status": "covered", "notes": "Area under a declared measurement standard, capacity, occupancy, utilisation formula, resource metrics with normalisation and benchmark reference, metering boundary declaration and metered-versus-estimated share." }, { "dimension": "security", "status": "covered", "notes": "Security level determination factors, five-level scale, required versus implemented countermeasures with approved deviations, critical-infrastructure designation and reassessment cadence, from the ISC Risk Management Process 2021 Edition." }, { "dimension": "risk and criticality", "status": "covered", "notes": "Criticality and mission dependency with declared method, hazard exposure with likelihood and severity basis, redundancy and recovery objectives, exercise evidence. Gap: no consulted primary source defines a cross-sector criticality scale, so the method must be named by the adopting Dimension." }, { "dimension": "regulatory compliance", "status": "covered", "notes": "Programme interests with regulator and programme identifier, permits with validity and conditions, statutory inspections with due dates, open nonconformities with corrective actions and deadlines." }, { "dimension": "financial", "status": "not-applicable", "notes": "Valuation, depreciation, capital accounting and cost postings are routed to a Financial Asset model. Only deferred maintenance liability is retained here, because condition reporting requires it and real-property inventory guidance reports it alongside condition." }, { "dimension": "human occupancy and privacy", "status": "gap", "notes": "Occupant population is modelled only as aggregate counts by category. Person-level occupancy, access-credential records and workplace monitoring raise data-protection duties that no consulted source addresses at facility level; these are deferred to an Identity/Access model and flagged as an evidence gap rather than covered here." } ], "known_omissions": [ "ISO 55001:2024, ISO 41011:2024, ISO 19650-3:2020, ISO 81346-12:2018 and ISO 15686-1:2011 are paywalled. Their scope, structure and key distinctions were taken from the ISO catalogue records and committee material; exact normative clause text and full term definitions were not read, so no clause-level conformance is asserted anywhere in this model.", "The FY2026 FRPP Data Dictionary PDF could not be machine-parsed during research. It is cited for the existence and authority of the reporting data elements (identifier, asset type, legal interest, status, size, condition, mission dependency, utilisation, disposition), not for verbatim element names or code values.", "The EPA Facility Site Identification Data Standard PDF could not be machine-parsed. Its data groupings are cited at the level confirmed by EPA's own summary pages; individual element names and formats should be re-verified against the PDF before implementation.", "No consulted source provides a normative, cross-jurisdiction code list for facility operational status, criticality scale or maintenance strategy. These are marked as Dimension-declared code lists rather than presented as canonical.", "Sustainability and green-building certification (LEED, BREEAM, energy performance certificates under the EU Energy Performance of Buildings Directive) is not modelled as a separate finding; only benchmarked resource performance is covered. This was rejected as attractive but insufficiently grounded at facility rather than building level in the sources consulted.", "Insurance, valuation and loss-history context is absent. It is genuinely part of the facility decision surface but no primary source in the consulted set supports a defensible structure for it.", "Digital-twin runtime telemetry, building automation point naming (for example Brick or Project Haystack) and control-system topology are not modelled; only the static system register and reference designation are covered.", "Marine, rail, road and bridge facility specialisations are acknowledged through IFC subtypes but not elaborated. A facility with no buildings at all is supported structurally but its domain-specific context is out of scope.", "ENERGY STAR Portfolio Manager and other energy-benchmarking facility IDs were not fetched as primary sources.", "Uniclass, OmniClass, MasterFormat and similar construction classification tables are not included.", "CISA critical-infrastructure sector designations lack primary support here.", "NFPA 101/25/72, ASME A17.1 and equivalent ongoing inspection regimes are not specified beyond the note that a CO does not satisfy them.", "COBie as a distinct handover schema is not specified; ISO 19650 AIM is used instead.", "ISO 21542 / ADA accessibility beyond IFC HandicapAccessible is not specified.", "Climate-risk scoring, whole-life cost models and GHG inventories are vocabulary-aligned in ISO 41011 but not operationalized as findings.", "Temporary event facilities, underground mines, nuclear licensed sites and vessels as facilities are not developed.", "National facility registers outside the US EPA FRS (for example European PRTR or other cadastres) are not included.", "ISO 19650-5 is cited via ISO 19650-3 but was not fetched as a primary document." ], "conflicts": [ "IFC 4.3 makes IfcBuilding a subtype of IfcFacility, whereas the registry relation and this model make Facility an aggregate that contains Building (WM-BLT-001). These are incompatible readings of the same word: IFC says a building is a kind of facility, this model says a facility is a set of buildings. Recorded as an alignment conflict; the crosswalk must map a single-building facility to IfcBuilding directly rather than to IfcFacility plus a child.", "The W3C Building Topology Ontology exposes bot:Site with bot:hasBuilding and provides no class between site and building. Any BOT projection of a multi-building facility must introduce an extension term or collapse the facility, losing the aggregation. Alignment is therefore declared partial and lossy.", "EPA FRS models a 'facility site' scoped to regulatory interest. A regulated facility site can be co-extensive with, larger than, or smaller than a Vercy Facility, and can be co-extensive with a Site. The site-contains-facility containment therefore cannot be assumed when reconciling with environmental registries.", "ENERGY STAR treats a multi-building campus as a parent 'property' with child buildings, using property and property-use terminology that does not map cleanly onto site, facility and building. The parent property may correspond to a Facility or to a Site depending on how the portfolio was set up.", "Uniclass places Complexes (Co) above Entities (En), so a Vercy Facility may classify as a complex or as an entity depending on granularity. No rule in the consulted sources determines which, so the choice is left to the adopting Dimension and must be recorded.", "ISO 41011 facility-management vocabulary uses 'facility' more broadly than the built-asset scope adopted here, including service and non-built assets. This model narrows the term deliberately and records the narrowing rather than claiming vocabulary conformance.", "IFC allows a facility to be aggregated directly to a project with no site, contradicting any modelling that makes Site containment mandatory. The composition link to WM-BLT-008 is therefore marked not required.", "IFC 4.3 treats IfcBuilding as a subtype of IfcFacility; this model treats Facility as containing Building. Alignment only; no IFC conformance claim.", "EPA FIDS/FRS treats a facility as a distinct real-property facility-site and often conflates land and operations; ISO/IFC distinguish Site from Facility.", "FHIR Location ranges from bed and freezer to building and mobile clinic; using it as the Facility aggregate would over-cover spaces and kinds.", "ISO 19650-3 uses asset as a convenience term covering asset management and facility management; ISO 41011 keeps facility distinct from asset.", "IBC occupancy authorization applies to buildings and structures, not necessarily to roads, railways or other civil IfcFacility subtypes.", "Facility names and addresses routinely differ across EPA program systems after ownership change; name matching without steward review is unsafe.", "ECHO compliance status is often alleged tracking status, not adjudication." ], "regional_assumptions": [ "The FRPP data dictionary, FRS and the Facility Site Identification Data Standard, NARA GRS 5.4, the ISC Risk Management Process, the International Building Code and ENERGY STAR Portfolio Manager are United States instruments. Adopters elsewhere must substitute equivalent national real-property inventories, environmental registries, retention schedules, protective-security standards, building codes and benchmarking regimes; the structural findings are intended to survive that substitution but the code lists are not.", "The INSPIRE Buildings data specification and its identifier and lifespan rules are European Union instruments implementing Commission Regulation (EU) No 1089/2010 and apply only where INSPIRE publication obligations exist.", "Uniclass is a United Kingdom classification. Adopters in other regions will more likely use OmniClass, a national equivalent or an industry activity classification, and the crosswalk must record which.", "Coordinate reference systems, vertical datums, address structures and administrative unit hierarchies are region-specific. The model mandates that CRS and datum be declared but does not prescribe values.", "Data-protection duties over occupancy and access data vary substantially by jurisdiction. The model deliberately holds only aggregate occupancy and defers person-level data, but adopters in strict-regime jurisdictions should verify that even aggregate occupancy counts are lawful to retain and publish.", "Retention periods differ sharply between public-sector schedules and private-sector obligations. The three-year default reflected in the cited government-wide schedule must not be generalised; adopters must map to their own scheduling authority.", "EPA FRS, NAICS/SIC, Indian-country and federal-facility indicators are United States environmental-program constructs.", "IBC 2021 Section 111 is a US model code; adopting jurisdictions may use other editions or national building codes with different occupancy certificates.", "FHIR Location is healthcare-centric and is an optional alignment for hospitals and clinics, not a general facility register.", "IFC GlobalId is an exchange-world identifier, not a legal or environmental master ID.", "Best-pick NAD83 coordinates and ZIP-centroid approximations are US FRS/ECHO behaviours.", "Land-title numbers on IfcSite follow local cadastral practice and are references, not a world land register." ], "adversarial_checks": [ "Counterexample: a road, railway, bridge or marine facility that contains no buildings at all. IFC treats these as first-class facility subtypes. The model survives because building membership is optional and decomposition uses an explicit usage convention, but the registry's 'Facility contains buildings or structures' rationale is only conditionally true and is recorded as such.", "Counterexample: a single-building facility where Facility and Building are co-extensive. This risks duplicating WM-BLT-001. Resolved by requiring the terminal decomposition level to be declared and by mapping such cases directly to IfcBuilding in the crosswalk rather than creating a facility node plus a redundant child.", "Counterexample: leased floors inside a third-party multi-tenant building operated as a facility by a tenant. Here the facility is smaller than the building, inverting the containment. The model accommodates this through non-exclusive membership with an apportionment basis and a legal interest of leased, but the CONTAINS edge to WM-BLT-001 is semantically strained and is flagged for review.", "Counterexample: a facility spanning several parcels, two municipalities and two utility service territories. Tests exclusive site containment and single-jurisdiction assumptions; addressed by the straddling question, multi-site references and apportionment rules, but no consulted source prescribes an apportionment method, so this remains a Dimension decision.", "Counterexample: a mothballed or disposed facility that still carries environmental permits, monitoring obligations and long-lived record retention. Tests whether terminal lifecycle states terminate obligations; the model explicitly separates operational status from surviving obligations and blocks deletion while any obligation is open.", "Counterexample: a facility whose public record is lawfully withheld in its entirety for national-security reasons. Tests whether absence and withholding are distinguishable; the model requires the exclusion and its legal basis to be recorded even when the record is not released, so a consumer can tell 'withheld' from 'does not exist'.", "Rejected structure: a dedicated Address bundle. Rejected as duplicating a sibling Address model; only role-tagged references and jurisdictional placement are retained.", "Rejected structure: a Sustainability Certification bundle. Rejected because the consulted primary sources support benchmarking metrics at property level but do not support a defensible certification structure at facility level; folded into resource performance and recorded as a known omission.", "Rejected structure: an Occupant bundle holding person-level occupancy. Rejected on privacy grounds and for lack of primary support at facility level; deferred to an Identity/Access model and recorded as an explicit coverage gap rather than silently dropped.", "Could Facility collapse into Site? Only if EPA facility-site conflation is adopted; ISO 41011 and IFC IfcSite versus IfcFacility keep them distinct, so collapse is rejected and recorded as conflict.", "Could Facility collapse into Building? Only if IFC subtype is adopted; Vercy known relation and ISO 41011 collection-of-assets definition keep Building as a contained shelter object.", "Is a car, AHU or nature preserve a facility? ISO/TR 41013 says no; the eligibility function rejects those candidates.", "Can a facility exist with no site and no building? IFC allows direct assignment to project and non-building subtypes; the model allows it.", "Can one facility span many sites? Unresolved; agents must record multi-site as a boundary note rather than invent a universal rule.", "Does a certificate of occupancy end regulatory duty? No; IBC authorizes occupancy while environmental and fire-code programs may continue, including after operations cease.", "Is FM or ISO 41001 the same object as Facility? No; FM is the organizational function and management system; Facility is the asset collection those functions operate." ] }, "researchAdjudication": { "providerMode": "dual-provider", "activeProviders": [ "claude", "grok" ], "waivedProviders": [], "providerPolicy": {}, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "Both providers independently reached entry_kind=aggregate for vr.wm-blt-006, and both independently rejected the two collapse candidates: Facility into Site (rejected because ISO 41011 and IfcSite/IfcFacility keep land locus distinct from operating asset collection) and Facility into Building (rejected because IFC 4.3 subtyping is recorded as an alignment conflict, not adopted as the registry relation). The registry CONTAINS edge to WM-BLT-001 is retained as operational aggregation; Site containment is retained as conditional because IFC permits a facility aggregated directly to a project with no site. No split, reclassification or merge is warranted: the boundary between the Facility aggregate and the Facility Management management system (ISO 41001) is stated identically by both providers." }, "decisions": [ { "concept": "Base provider selection", "disposition": "Claude adopted as base", "rationale": "Claude states twelve in-scope and twelve out-of-scope items each keyed to a named sibling model, gives eight source-referenced boundary notes, and carries the governance spine the merged model needs (bitemporal versioning, retention and disposition, disclosure control, crosswalk lossiness). Grok's bundle set is wider but its boundaries repeat inside findings rather than being declared once; size was not the deciding factor." }, { "concept": "Entry kind", "disposition": "Accepted as aggregate", "rationale": "Independent agreement between providers, and both reached it by rejecting the same two collapse candidates (into Site and into Building) with the same primary evidence, which is stronger than mere agreement on a label." }, { "concept": "Facility CONTAINS Building versus IFC 4.3 IfcBuilding-as-subtype", "disposition": "Retained as recorded alignment conflict; registry CONTAINS relation kept", "rationale": "Both providers independently declined IFC conformance and recorded the inversion. Base additionally prescribes that a single-building facility maps directly to IfcBuilding in the crosswalk rather than to IfcFacility plus a redundant child, which resolves the practical case without changing the boundary." }, { "concept": "Site containment obligation", "disposition": "Conditional edge to WM-BLT-008, not mandatory", "rationale": "IFC permits a facility aggregated directly to a project with no site, and both providers reached this conclusion separately. The composition link must therefore be marked not-required rather than assumed." }, { "concept": "Facility eligibility and negative test", "disposition": "Accepted from grok", "rationale": "Base only carried this reasoning in adversarial checks; a registered agent needs a first-class test that rejects a single asset, an unbuilt asset, a kind-of-location classifier, or a room, and admits civil and mobile facilities." }, { "concept": "Certificate of occupancy as authorization gate", "disposition": "Accepted from grok, bounded to reference plus scope and validity", "rationale": "Distinct from occupancy classification, which the base already holds. The instrument's issuance workflow and conditions text stay in the Authorization sibling model per the base out-of-scope list, so the addition does not breach the declared boundary." }, { "concept": "Alleged versus adjudicated compliance status", "disposition": "Accepted from grok", "rationale": "Base tracks open nonconformities but not the legal weight of a reported determination or its refresh lag. Misreporting alleged as adjudicated is a concrete downstream harm and the ECHO data dictionary supports the distinction directly." }, { "concept": "Facility-scale fire and life safety", "disposition": "Accepted from grok", "rationale": "Base risk coverage is exposure and continuity plus protective security; fire risk, sprinkler and exit provisions and emergency preparedness were genuinely absent. Accepted with the source's own caveat that detailed life-safety design belongs to Building and Space models." }, { "concept": "Post-occupancy evaluation", "disposition": "Accepted from grok, service-life portion suppressed", "rationale": "POE is defined in ISO 41011 and placed on the ISO 19650-3 operational timeline and is missing from the base. Service life remains mastered by the base condition-and-service-life finding to avoid two masters for the same measure." }, { "concept": "Grok identifier, naming, address and coordinate findings", "disposition": "Rejected as duplicative", "rationale": "Base already covers master key and external registry precedence, non-reuse, merge and split, alias validity, address roles and jurisdiction, CRS, vertical datum, accuracy, level of detail and relative-versus-absolute placement. Adding these would create parallel structure without new decision surface." }, { "concept": "Grok identity-matching-and-data-quality (no silent merge without steward review)", "disposition": "Rejected as a finding; retained as a required answer under the base deduplication question", "rationale": "Base already asks what deduplication and match-confidence rule applies and what confidence accompanies matched values. The steward-adjudication control is the answer to those questions, not a separate structure, and duplicating it would split match governance across two layers." }, { "concept": "Grok facility-services-and-service-levels", "disposition": "Rejected as duplicative", "rationale": "Base operator-and-service-accountability already carries delegated service scope, governing agreement and what the demand organisation retains, and both providers put SLA commercial terms and the FM management system out of scope. Only mobilization state was novel, which is insufficient for a finding." }, { "concept": "FHIR Location alignment (grok-only source)", "disposition": "Deferred to the crosswalk matrix, not adopted as structure", "rationale": "FHIR Location spans beds, freezers, vehicles and buildings, so adopting it as the facility aggregate would over-cover spaces and kinds; grok itself records this as a conflict. It may be added as a versioned alignment row under the base crosswalk finding once a healthcare profile is validated." }, { "concept": "Grok parties-ownership-and-authority and safety-security-and-access bundles", "disposition": "Not adopted as bundles; accepted content routed into existing base layers", "rationale": "Base already places ownership, custody and operating accountability under authority-tenure-and-compliance and security posture under the same bundle. Creating parallel bundles would fragment authority semantics; the two accepted safety and authorization findings fit existing layers cleanly." } ], "publicationHolds": [ "Source and live-version verification is incomplete: the same EPA Facility Site Identification Data Standard PDF is dated 2014-10-01 Version 2 by claude (SRC-004) and 2006-01-06 Version 2.0 by grok (SRC-003), and the two providers assign it different authority tiers. Re-fetch and pin one date, version and tier before any citation is published.", "Pin a single IFC documentation reference: claude cites the ifc43-docs build 4.3.2.20260821 (IFC4X3_ADD2) while grok cites standards.buildingsmart.org IFC 4.3.2.0 mapped to ISO 16739-1:2024. Both URLs must be re-resolved live and one canonical citation chosen for IfcFacility, IfcFacilityPart and IfcSite.", "All ISO sources on both sides (41011, 6707-4, 19650-3, 55001, 81346-12, 15686-1) were taken from catalogue or Online Browsing Platform records, not normative clause text. Hold any clause-level or conformance wording; publish alignment language only, and state the non-reading explicitly in the draft.", "Claude records that the FY2026 FRPP Data Dictionary and the EPA FIDS PDF could not be machine-parsed, so element names, formats and code values are unverified. Publish these as existence-and-authority citations only; block implementation-level field naming until re-parsed.", "Multi-profile domain validation is not complete. The merged evidence is dominated by US federal instruments (FRS, FRPP, NARA GRS 5.4, ISC, IBC, ENERGY STAR, ECHO) plus EU INSPIRE and one healthcare alignment. Validate against at least one non-US built-asset profile and one non-building civil or infrastructure profile before presenting the model as domain-general.", "The five accepted grok findings each rest on a narrower evidence base than the base findings around them (IFC property sets for life safety, a single ECHO dictionary for compliance status, one IBC section for occupancy authorization). Mark them as provisionally sourced in the draft and re-verify before they carry any normative weight." ], "deferredResearch": [ "Whether one operational facility may span multiple sites, and by what method area, population and reporting are apportioned when a facility straddles parcels, municipalities, tribal land or utility service territories. Claude allows multi-site with apportionment but states no consulted source prescribes a method; grok records the question as unresolved. Neither position is evidenced, so it must be recorded as an open Dimension decision.", "Accessibility designation at facility aggregate level (ISO 21542, ADA and national equivalents). Grok carries only the IFC HandicapAccessible flag and lists ISO 21542/ADA as an omission; claude does not address accessibility at all. Needs a primary source before any finding is created.", "Ongoing statutory inspection regimes referenced but not sourced: NFPA 101, 25 and 72, ASME A17.1 and non-US equivalents. Required to give the accepted fire-life-safety finding a defensible inspection cadence rather than a static assertion.", "Facility registers outside the US EPA FRS (European PRTR, national real-property inventories and cadastres) to test whether the identifier resolution, programme-interest and regulatory-standing structures survive substitution of the US instruments they were derived from.", "Sustainability and green-building certification at facility rather than building level (LEED, BREEAM, EPBD energy performance certificates). Claude rejected it as attractive but insufficiently grounded; grok lists ENERGY STAR as unfetched. Decide only after a facility-level primary source is obtained.", "Person-level occupancy, access credentials and workplace monitoring. Claude marks this an explicit coverage gap and holds only aggregate counts; verify whether even aggregate occupancy retention and publication are lawful in strict data-protection jurisdictions before the model is adopted there.", "Insurance, valuation and loss-history context, and digital-twin runtime telemetry with control-point naming (Brick, Project Haystack). Both are acknowledged parts of the facility decision surface but neither provider found primary support for a defensible structure." ] }, "statistics": { "sources": 31, "bundles": 6, "layers": 13, "findings": 31, "questions": 121, "artifacts": 30, "functions": 13 } }