# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-08-24T10:16:53Z", "synthesisSha256": "73fb48cfd24878d4d1ef374d7c4b3cc856de1cc91c7ccaccdae824fa3e6d1407", "providerMode": "dual-provider", "providers": [ "Claude", "Grok" ], "waivedProviders": [] }, "metaModel": { "id": "WM-BLT-008", "registryId": "vr.wm-blt-008", "name": "Site / Campus", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.BLT.SITE" ], "tags": [ "site", "campus", "phy.blt.site" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-blt-008-site-campus/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-008", "model": { "registry_id": "vr.wm-blt-008", "model_id": "WM-BLT-008", "name": "Site / Campus", "entry_kind": "entity", "purpose": "Provide the format-neutral context an agent needs to identify, describe, govern and operate a site or campus: a bounded area of land (with associated subsurface, surface water and airspace) held under coordinated management control, inside which facilities, infrastructure, circulation and open space are operated as one unit.", "scope_statement": "WM-BLT-008 models the managed physical container itself - its identity, classification, spatial extent, composition, control, lifecycle, operating conditions, measurement boundary and evidence - and stops at the interfaces with contained facilities (WM-BLT-006), the containing settlement or place (WM-PLC-005 / WM-PLC-002), the legal land unit, and the parties that own or operate it. Facilities, parcels, organisations, permits and individual assets are referenced by identifier, never re-modelled here. The model is projection-independent: IFC, CityGML, GeoJSON, Markdown, Git, MCP and MongoDB are encodings of these semantics, not the semantics.", "in_scope": [ "Site identity, naming, coding and identifier crosswalks across authoritative registries and internal systems", "Site typology and classification against governed schemes", "Declared managed extent: what is inside the site, including discontiguous parts and third-party enclaves", "Boundary geometry, coordinate reference system, elevation datum, vertical and subsurface extent", "References to the land parcels and tenure instruments the site rests on", "Containment of facilities (WM-BLT-006) and on-site infrastructure networks", "Ground surface, landscape, open space, parking and laydown areas", "Internal zones, precincts, development phases, circulation routes and control points", "Ownership, operatorship, duty-holder accountability and delegation", "Regulatory authorisations, permits and registry interests attached to the site", "Physical access control, perimeter and site information sensitivity", "Lifecycle states, boundary change events, split/merge and successor lineage", "Operating hours, site rules, permit-to-work regimes and service provision", "Natural hazard exposure, contamination and environmental constraints", "Emergency preparedness, evacuation and muster arrangements", "Site-level quantities, areas, occupancy and capacity", "Energy, water, waste and greenhouse-gas reporting boundary and meter coverage", "Site-scale monitoring platforms and observations", "Site records, evidence, provenance and retention", "Alignment and crosswalks to external schemas and operational systems" ], "out_of_scope": [ "Internal anatomy of a building or civil facility - storeys, spaces, rooms, systems and building elements (WM-BLT-006 and its children)", "Legal land title, deeds, rights, restrictions and responsibilities as first-class legal objects (land administration sibling model, aligned to ISO 19152-1)", "Settlement, administrative area and populated-place semantics (WM-PLC-005, WM-PLC-002)", "Legal entity, organisation and person records for owners, operators, staff, visitors and contractors", "Individual equipment and plant items, their maintenance history and work orders (asset register and maintenance sibling models)", "Construction and capital project delivery processes, programmes and contracts", "Lease, licence and other commercial agreement terms", "Address and geocoding conceptual model - addresses are referenced, not defined here", "Utility network topology, capacity modelling and operations beyond the site demarcation point", "Sensor and actuator device specifications - observations are referenced through SOSA/SSN patterns", "Environmental permit legal instruments as documents of record (authorisation sibling model)", "Financial valuation, depreciation and real-estate investment accounting" ], "boundary_notes": [ { "neighbor": "WM-BLT-006 Facility", "distinction": "IFC 4.3 keeps IfcSite and IfcFacility as separate spatial structure elements: a facility is aggregated by IfcProject, IfcSite or another IfcFacility, and decomposes into IfcFacilityPart and IfcSpace. WM-BLT-008 therefore records the containment edge, the facility identifier and the site-side demarcation point, and never re-states facility-internal structure.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "Land parcel / cadastral parcel (land administration sibling model)", "distinction": "A cadastral parcel is a legal spatial unit with homogeneous property rights, identified by nationalCadastralReference and inspireId, and used primarily as a locator. A site is a management construct: it may span many parcels, occupy part of a parcel, or include parcels held under different tenure. IFC 4.3 deprecated IfcSite.LandTitleNumber, reinforcing that title belongs elsewhere. WM-BLT-008 references parcels; it does not model rights, restrictions or responsibilities.", "source_refs": [ "SRC-001", "SRC-004", "SRC-010" ] }, { "neighbor": "WM-PLC-005 Settlement and WM-PLC-002 Place", "distinction": "A settlement is an administrative or populated-place concept; a site is an operational container under a single management regime. A site can straddle two settlements or lie wholly outside any populated place, so containment by settlement is a recorded relationship with its own evidence, not a derived truth.", "source_refs": [ "SRC-008", "SRC-004" ] }, { "neighbor": "Regulatory facility registry entries (e.g. EPA FRS facility site)", "distinction": "EPA FRS clusters program-system records under a 12-digit Registry ID and treats the originating programs as source of truth. A regulatory facility site is a reporting unit that frequently does not align one-to-one with the managed site: one site may carry several FRS interests, and one FRS record may cover only part of a site. The crosswalk must be recorded with match confidence rather than assumed.", "source_refs": [ "SRC-003" ] }, { "neighbor": "Reporting boundary constructs (ENERGY STAR property, GHG Protocol organizational boundary)", "distinction": "EPA Portfolio Manager models a campus as a parent property with child properties and does not support nested campuses; GHG Protocol sets organizational boundaries by equity share or control. Both are accounting boundaries that can diverge from the physical managed extent. WM-BLT-008 records each reporting boundary as a distinct, dated view over the site, never as the site's definition.", "source_refs": [ "SRC-011", "SRC-013" ] }, { "neighbor": "Utility network model", "distinction": "On-site distribution is in scope only up to the demarcation point where responsibility passes to an external network operator. Network topology, hydraulic or electrical modelling and upstream operations sit in the utility network sibling model.", "source_refs": [ "SRC-001", "SRC-009" ] }, { "neighbor": "Asset management system (ISO 55001) and asset information model (ISO 19650)", "distinction": "ISO 55001 governs the management system and ISO 19650 governs information containers and trigger events. WM-BLT-008 is neither: it is the subject those systems act upon. It records which management system and information requirements apply, and cites their identifiers, without absorbing their clauses.", "source_refs": [ "SRC-009", "SRC-012" ] } ] }, "sources": [ { "id": "SRC-001", "title": "IfcSite - IFC 4.3.2 Documentation", "organization": "buildingSMART International", "url": "https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcSite.htm", "version_or_date": "IFC 4.3.2 (IFC4X3_ADD2), documentation build 4.3.2.20260821", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:05:00Z", "relevance": "Normative definition of a site as a spatial structure element: RefLatitude, RefLongitude, RefElevation, CompositionType COMPLEX/ELEMENT/PARTIAL, aggregation of sites and facilities, and the deprecation of LandTitleNumber and SiteAddress as of IFC4.3.0.0." }, { "id": "SRC-002", "title": "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 (IFC4X3_ADD2), documentation build 4.3.2.20260821", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:07:00Z", "relevance": "Defines the site/facility boundary: subtypes IfcBuilding, IfcBridge, IfcRoad, IfcRailway, IfcMarineFacility; facilities are aggregated by IfcProject, IfcSite or another facility and decompose into IfcFacilityPart and IfcSpace." }, { "id": "SRC-003", "title": "FRS Description - Facility Registry Service", "organization": "United States Environmental Protection Agency", "url": "https://www.epa.gov/frs/frs-description", "version_or_date": "Page last updated 2025-09-05", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:12:00Z", "relevance": "Authoritative example of master-system site identification: a 12-digit FRS Registry ID clustering records from roughly 90 program systems, with program systems as source of truth, a weekly geospatial best-pick process and a data steward network." }, { "id": "SRC-004", "title": "D2.8.I.6 INSPIRE Data Specification on Cadastral Parcels - Technical Guidelines", "organization": "European Commission - INSPIRE Maintenance and Implementation Group", "url": "https://inspire-mif.github.io/technical-guidelines/data/cp/dataspecification_cp.html", "version_or_date": "v3.1.1, 2024-07-31", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:20:00Z", "relevance": "Normative attribute set for the land basis a site rests on: inspireId, geometry, nationalCadastralReference, label, areaValue, referencePoint, validFrom/validTo and beginLifespanVersion/endLifespanVersion, plus the statement that parcels serve mainly as locators for geo-information." }, { "id": "SRC-005", "title": "Semantic Sensor Network Ontology (SSN/SOSA)", "organization": "World Wide Web Consortium (W3C)", "url": "https://www.w3.org/TR/vocab-ssn/", "version_or_date": "W3C Recommendation, 19 October 2017", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:26:00Z", "relevance": "Supplies the observation pattern for site monitoring: Platform, Sensor, Observation, FeatureOfInterest, ObservableProperty, and the normative separation of resultTime (when the activity completed) from phenomenonTime (when the result applies to the feature of interest)." }, { "id": "SRC-006", "title": "29 CFR 1910.38 - Emergency action plans", "organization": "United States Department of Labor - Occupational Safety and Health Administration", "url": "https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.38", "version_or_date": "67 FR 67963, 7 November 2002; current text as published by OSHA", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:31:00Z", "relevance": "Normative minimum content for site emergency preparedness: written plan (oral permitted for 10 or fewer employees), reporting procedures, evacuation type and exit route assignments, critical-operations staff, post-evacuation employee accounting, rescue and medical duties, named contacts, a maintained employee alarm system, and defined review triggers." }, { "id": "SRC-007", "title": "NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations", "organization": "National Institute of Standards and Technology", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final", "version_or_date": "Revision 5, September 2020, updated 2020-12-10", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:36:00Z", "relevance": "Physical and Environmental Protection (PE) control family provides the normative pattern for site perimeter and access governance: physical access authorizations, enforcement at defined entry and exit points, access logging, visitor control and inventory of physical access devices." }, { "id": "SRC-008", "title": "OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard", "organization": "Open Geospatial Consortium", "url": "https://www.ogc.org/standard/citygml/", "version_or_date": "Version 3.0, OGC document 20-010", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:42:00Z", "relevance": "Semantic model for 3D urban objects with a Core module plus thematic modules including CityObjectGroup, LandUse, Relief, Transportation, Vegetation and WaterBody; supplies grouping, level-of-detail and land-cover concepts for site-scale representation and its encoding-independent conceptual layer." }, { "id": "SRC-009", "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:48:00Z", "relevance": "Requirements for scope of the asset management system, leadership and accountability, life-cycle planning and control of change, documented information, and performance evaluation - the governance frame within which a site is held and operated." }, { "id": "SRC-010", "title": "ISO 19152-1:2024 Geographic information - Land Administration Domain Model (LADM) - Part 1: Generic conceptual model", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/81263.html", "version_or_date": "First edition, 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:52:00Z", "relevance": "Defines party, basic administrative unit, rights/responsibilities/restrictions, spatial unit, source and versioned object - establishing that legal land units and tenure belong to a land administration model rather than to a managed-site model." }, { "id": "SRC-011", "title": "How to Benchmark a Campus in Portfolio Manager", "organization": "United States Environmental Protection Agency - ENERGY STAR", "url": "https://www.energystar.gov/buildings/tools-and-resources/how-benchmark-campus", "version_or_date": "Guide dated March 2024; landing page updated 2025-01-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:58:00Z", "relevance": "Public-authority rules for multi-building campus accounting: parent property and child property structure, absence of nested campuses, campus-serving meters recorded at the parent and single-building meters at the child, and a restricted list of property types eligible for campus-level certification." }, { "id": "SRC-012", "title": "ISO 19650-1:2018 Organization and digitization of information about buildings and civil engineering works, including building information modelling (BIM) - Information management using building information modelling - Part 1: Concepts and principles", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/68078.html", "version_or_date": "First edition, 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T10:03:00Z", "relevance": "Supplies asset information requirements, the asset information model, information containers and the common data environment as the agreed source of information, together with the trigger-event pattern that drives site information updates through the operational phase." }, { "id": "SRC-013", "title": "GHG Protocol Corporate Accounting and Reporting Standard", "organization": "World Resources Institute and World Business Council for Sustainable Development", "url": "https://ghgprotocol.org/corporate-standard", "version_or_date": "Revised edition, with 2015 Scope 2 Guidance", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T10:08:00Z", "relevance": "Defines organizational boundaries (equity share and control approaches) and operational boundaries (scope 1, 2 and 3) covering seven greenhouse gases - the basis for treating a site emissions inventory as a consolidation view distinct from the physical site." }, { "id": "SRC-014", "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, 2024", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T10:12:00Z", "relevance": "Governed vocabulary for facility management terms used in site operating models, service provision and demand organisation, superseding the 2017 first edition." }, { "id": "SRC-015", "title": "IfcSite — IFC 4.3.2.0 (IFC4X3_ADD2) official 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), ISO 16739-1:2024 family", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Normative spatial-structure class for a defined area of land, possibly covered with water; composition COMPLEX/ELEMENT/PARTIAL; georeference, containment of facilities and buildings, GlobalId, LandTitleNumber and SiteAddress (latter two deprecated in ADD2)." }, { "id": "SRC-016", "title": "ISO 6707-1:2020 Buildings and civil engineering works — Vocabulary — Part 1: General terms", "organization": "International Organization for Standardization", "url": "https://www.iso.org/obp/ui/es/?_escaped_fragment_=iso:std:77077:en", "version_or_date": "ISO 6707-1:2020 (sixth edition, 2020-08)", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Clause 3.1.1.5 defines site as an area of land or water where construction work or other development is undertaken; distinguishes building, civil engineering works, external works/sitework and land." }, { "id": "SRC-017", "title": "OPC UA Common Object Model: ISA-95 — ISA95EquipmentElementLevelEnum", "organization": "OPC Foundation", "url": "https://reference.opcfoundation.org/specs/OPC-10030/7.4", "version_or_date": "OPC 10030 ISA-95 companion specification, ISA95EquipmentElementLevelEnum", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Publishes the ISA-95/IEC 62264 role-based equipment hierarchy: enterprise contains sites; a site is a physical, geographical or logical grouping determined by the enterprise and may contain areas, production lines, process cells and production units." }, { "id": "SRC-018", "title": "INSPIRE Data Specification on Cadastral Parcels — Technical Guidelines", "organization": "European Commission INSPIRE Maintenance and Implementation Group", "url": "https://inspire-mif.github.io/technical-guidelines/data/cp/dataspecification_cp.pdf", "version_or_date": "D2.8.I.6 v3.1.1, published 2024-07-31", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Defines cadastral parcels as single areas of Earth surface under homogeneous real-property rights and unique ownership, with inspireId, nationalCadastralReference, geometry, label, area, reference point and beginLifespanVersion; compatibility with LADM; parcels are locators, not managed campuses." }, { "id": "SRC-019", "title": "OGC Land and Infrastructure Conceptual Model Standard (LandInfra)", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/15-111r1/15-111r1.html", "version_or_date": "OGC 15-111r1, version 1.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Clause 4.2.9 repeats ISO 6707-1 site; 4.2.7 defines facility as improvements of or on the land; land division covers administrative jurisdictions, land parcels, easements and condominiums; survey locates facilities on terrain in compliance with interests in land." }, { "id": "SRC-020", "title": "42 U.S. Code § 9601 — CERCLA definitions", "organization": "United States Congress", "url": "https://www.law.cornell.edu/uscode/text/42/9601", "version_or_date": "42 U.S.C. § 9601, current through accessed text 2026-08-24", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Section 101(9) defines facility as any building, structure, installation or any site or area where a hazardous substance has come to be located, excluding consumer products and vessels; this overlays environmental liability on physical holdings." }, { "id": "SRC-021", "title": "ISO 19152-2:2025 Geographic information — Land Administration Domain Model (LADM) — Part 2: Land registration", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/81264.html", "version_or_date": "ISO 19152-2:2025 (edition 1, published 2025-05)", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Abstract model of parties, basic administrative units, rights-responsibilities-restrictions, and spatial units including parcels, legal space of buildings, utilities and civil-engineering elements; SpatialUnitGroup can represent grouped land holdings; VersionedObject supports lifespan." }, { "id": "SRC-022", "title": "ISO 19650-3:2020 Information management using BIM — 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": "ISO 19650-3:2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Applies information management to assets of all sizes including portfolios of buildings, campuses, infrastructure networks and individual buildings; defines AIM, PIM-to-AIM transfer, trigger events, appointment, continuity of information on ownership transfer, and points to ISO 19650-5 security-minded approach, ISO 55000 and ISO 41011." }, { "id": "SRC-023", "title": "OGC CityGML 3.0 Conceptual Model Standard", "organization": "Open Geospatial Consortium", "url": "https://www.ogc.org/publications/standard/citygml/", "version_or_date": "CityGML 3.0 Part 1 Conceptual Model OGC 20-010, approved 2021-09", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Semantic 3D city objects, LandUse, CityObjectGroup and construction/building modules; no Site class; grouping and land-use are the urban-model counterparts of a managed campus, with BIM/IFC interoperability goals." }, { "id": "SRC-024", "title": "Pset_LandRegistration — IFC 4.3.2.0", "organization": "buildingSMART International", "url": "https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/Pset_LandRegistration.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:00:00Z", "relevance": "Property set applicable only to IfcSite: LandID and LandTitleID assigned by the statutory registration authority, plus IsPermanentID distinguishing temporary and permanent identities; replacement for deprecated IfcSite.LandTitleNumber." }, { "id": "SRC-025", "title": "IEC 62264-1:2013 Enterprise-control system integration — Part 1: Models and terminology", "organization": "International Electrotechnical Commission", "url": "https://standards.iteh.ai/catalog/standards/iso/db90faa8-7d04-4c7f-aeb0-627675ee5a1e/iec-62264-1-2013", "version_or_date": "IEC 62264-1:2013 (ISO/IEC dual logo, based on ANSI/ISA-95.00.01)", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Normative role-based equipment hierarchy clauses 5.3.2–5.3.4: Enterprise, Site and Area; site used for rough-cut planning and scheduling; dual physical-asset hierarchy distinct from role-based equipment." }, { "id": "SRC-026", "title": "Pset_SiteCommon — IFC 4.3.2.0", "organization": "buildingSMART International", "url": "https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/Pset_SiteCommon.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:00:00Z", "relevance": "Common site properties: Reference, BuildableArea, SiteCoverageRatio, FloorAreaRatio, BuildingHeightLimit and TotalArea; notes that perimeter, area and volume are quantities and classification is via IfcClassificationReference." }, { "id": "SRC-027", "title": "29 CFR 5.2 — Definitions, including site of the work", "organization": "United States Department of Labor", "url": "https://www.ecfr.gov/on/2024-10-07/title-29/section-5.2", "version_or_date": "29 CFR 5.2 as of 2024-10-07", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T18:00:00Z", "relevance": "Defines site of the work as primary construction site where the building or work will remain, secondary sites where a significant portion is constructed for specific use, and adjacent dedicated support sites; excludes general manufacturing of products for the public." } ], "structure": { "bundles": [ { "id": "identity-classification-and-extent", "name": "Identity, classification and managed extent", "description": "Establishes which site is being described, what kind of site it is, and the declared rule for what falls inside it.", "rationale": "Every downstream statement about a site is meaningless until the subject is pinned to a stable identifier and the inclusion rule for its managed extent is explicit. IFC gives the entity a formal spatial identity, EPA FRS shows the master-data reality of multiple competing site records, and EPA campus guidance shows that the inclusion rule is a deliberate decision rather than an observation.", "source_refs": [ "SRC-001", "SRC-003", "SRC-011" ], "layers": [ { "id": "identity-and-designation", "name": "Identity and designation", "description": "Identifier assignment, identifier priority, naming and the rules governing retirement or reuse.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "findings": [ { "id": "site-identity-and-designation", "name": "Site identity, identifier priority and designation", "description": "How a site instance is uniquely identified and named across authoritative registries and internal systems, which identifier is canonical, and how identifiers may be retired.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "questions": [ { "id": "q-authoritative-identifier", "text": "Which identifier is the authoritative master-system identifier for this site, and which system issues and maintains it?", "kind": "identity", "answer_data": [ "Issuing system or registry name", "Identifier value", "Identifier scheme reference", "Date and time of assignment (RFC 3339)", "Steward or issuing authority" ] }, { "id": "q-governed-global-identifiers", "text": "Which governed global identifiers or IRIs resolve to this site, and what persistence guarantee does each carry?", "kind": "interoperability", "answer_data": [ "Scheme name (for example EPA FRS Registry ID, national cadastral reference, IFC GlobalId)", "Identifier value", "Resolvable IRI where one exists", "Persistence and non-reallocation policy", "Match confidence for each crosswalked identifier" ] }, { "id": "q-surrogate-key", "text": "If no external authoritative identifier exists, what UUID or ULID has the adopting Dimension assigned, and when?", "kind": "identity", "answer_data": [ "UUID or ULID value", "Assigning Dimension", "Assignment timestamp (RFC 3339 with offset or Z)", "Justification that no higher-priority identifier was available" ] }, { "id": "q-names-and-languages", "text": "What official, legal, trading and wayfinding names does the site carry, in which languages, and which is canonical?", "kind": "definition", "answer_data": [ "Name string", "Name type (official, legal, trading, wayfinding, historical)", "Language tag", "Canonical flag", "Validity period" ] }, { "id": "q-identifier-retirement", "text": "Under what conditions may this identifier be retired, and may it ever be reassigned to a different site?", "kind": "constraint", "answer_data": [ "Retirement conditions", "Reassignment prohibition statement", "Quarantine period", "Successor or predecessor identifier references" ] } ], "data_elements": [ { "id": "site-primary-identifier", "name": "Primary site identifier", "description": "The single canonical identifier for the site, selected by the identity priority rule.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "site-identifier-scheme", "name": "Identifier scheme", "description": "Coded reference to the scheme that governs the identifier, including its issuing authority.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "site-alternate-identifier", "name": "Alternate site identifier", "description": "Any additional identifier by which the site is known in another system, with match confidence.", "value_kind": "identifier", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-001" ] }, { "id": "site-name", "name": "Site name", "description": "A name borne by the site, typed and language-tagged.", "value_kind": "text", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-004" ] }, { "id": "site-identifier-assigned-at", "name": "Identifier assignment time", "description": "RFC 3339 timestamp at which the primary identifier was assigned by its issuing authority.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "site-identifier-status", "name": "Identifier status", "description": "Whether the identifier is active, superseded or retired.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "site-registration-record", "name": "Site registration record", "description": "The authoritative register entry that establishes the site identifier, its issuing authority and assignment date.", "media_or_form": [ "registry entry", "structured record", "signed register extract" ], "serial": false, "identity_strategy": "Carries the primary site identifier as its subject key; the artifact itself is versioned by register transaction reference.", "source_refs": [ "SRC-003" ] }, { "id": "site-identifier-crosswalk", "name": "Site identifier crosswalk table", "description": "Mapping from the canonical site identifier to every known external identifier, with source system, match method, match confidence and reconciliation date.", "media_or_form": [ "tabular dataset", "mapping document" ], "serial": true, "identity_strategy": "Identified by canonical site identifier plus crosswalk revision number and reconciliation timestamp.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "classification-and-managed-extent", "name": "Classification and managed extent", "description": "The site's type against governed classification schemes and the explicit inclusion rule defining what falls within the managed container.", "source_refs": [ "SRC-001", "SRC-008", "SRC-011", "SRC-014" ], "findings": [ { "id": "site-typology-and-classification", "name": "Site typology and classification", "description": "Which governed classification schemes classify this site, what values apply, and when reclassification is required.", "source_refs": [ "SRC-001", "SRC-008", "SRC-014" ], "questions": [ { "id": "q-classification-schemes", "text": "Against which governed classification schemes is this site classified, and what is the scheme version for each assigned value?", "kind": "classification", "answer_data": [ "Scheme identifier and version", "Assigned class code and label", "Assignment date", "Assigning role" ] }, { "id": "q-multiple-classifications", "text": "Can the site hold more than one classification at the same time, and how are conflicting values reconciled?", "kind": "constraint", "answer_data": [ "Multi-classification permitted flag", "Precedence rule between schemes", "Recorded conflicts and resolution note" ] }, { "id": "q-composition-type", "text": "Is this record a site complex, a site, or a site section, and what does that imply for its parent and child records?", "kind": "composition", "answer_data": [ "Composition type value (complex, element, partial)", "Parent record identifier", "Constraint that parent composition type must differ" ] }, { "id": "q-reclassification-trigger", "text": "What events oblige the site to be reclassified, and who may authorise the change?", "kind": "lifecycle", "answer_data": [ "Trigger event types", "Authorising role", "Effective date of new classification", "Prior classification retained as history" ] } ], "data_elements": [ { "id": "site-class-assignment", "name": "Site class assignment", "description": "A coded classification value drawn from a named, versioned scheme.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-008", "SRC-014" ] }, { "id": "site-composition-type", "name": "Site composition type", "description": "Whether the record represents a site complex, a site, or a site section, following IFC composition semantics.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001" ] }, { "id": "site-primary-use", "name": "Primary use", "description": "The dominant operational use of the site, distinct from formal classification.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "classification-valid-from", "name": "Classification valid from", "description": "Date from which the classification value applies.", "value_kind": "date", "cardinality": "1", "required": true, "source_refs": [ "SRC-004" ] } ], "artifacts": [], "inline_only_rationale": "Classification is held inline as coded values against the site record. The governing schemes are externally maintained registries referenced by scheme identifier and version, and the assignment decision is captured in the site change log rather than as a standalone site artifact." }, { "id": "managed-extent-and-inclusion-rule", "name": "Managed extent and inclusion rule", "description": "The explicit, authored rule stating what is inside the site, covering discontiguous parts, third-party enclaves and areas the operator does not own.", "source_refs": [ "SRC-001", "SRC-011", "SRC-009" ], "questions": [ { "id": "q-inclusion-rule", "text": "What written rule determines whether a given area, facility or network falls inside this site's managed extent?", "kind": "definition", "answer_data": [ "Inclusion rule text", "Criteria used (management control, contiguity, ownership, operating licence)", "Authoring role", "Effective date" ] }, { "id": "q-discontiguous-parts", "text": "Is the site contiguous, and if not, what are its separate parts and what justifies treating them as one site?", "kind": "spatial", "answer_data": [ "Contiguity flag", "Part identifiers and geometries", "Justification for federation", "Distance or relationship between parts" ] }, { "id": "q-third-party-enclaves", "text": "Which areas inside the outer boundary are excluded from the managed extent, and who controls them?", "kind": "exception", "answer_data": [ "Excluded area identifier and geometry", "Controlling party reference", "Basis of exclusion", "Interface and coordination arrangements" ] }, { "id": "q-extent-authority", "text": "Who has authority to change the managed extent, and what evidence must accompany such a change?", "kind": "authority", "answer_data": [ "Authorising role", "Required evidence types", "Approval record reference", "Effective and recorded timestamps" ] } ], "data_elements": [ { "id": "managed-extent-statement", "name": "Managed extent statement", "description": "The authored inclusion rule expressed as text plus structured criteria.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "site-contiguity-flag", "name": "Contiguity flag", "description": "Whether the site's managed extent is a single connected area.", "value_kind": "boolean", "cardinality": "1", "required": true, "source_refs": [ "SRC-011" ] }, { "id": "site-part-reference", "name": "Site part reference", "description": "Reference to a discontiguous part or sub-site treated as within this site.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "excluded-enclave", "name": "Excluded enclave", "description": "An area geometrically within the outer boundary but outside the managed extent.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011" ] } ], "artifacts": [ { "id": "site-extent-definition", "name": "Site extent definition document", "description": "Approved statement of the inclusion rule, listed parts, listed exclusions and the authority that approved it.", "media_or_form": [ "approved definition document", "structured record with attached geometry" ], "serial": true, "identity_strategy": "Site identifier plus version number; each approved revision retains its predecessor reference and effective date.", "source_refs": [ "SRC-009", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "spatial-basis-and-context", "name": "Spatial basis and external context", "description": "Where the site is in measurable terms, what land it rests on, and how it meets the world at its edges.", "rationale": "Geometry without a declared coordinate reference system and vertical datum is unusable, and a site boundary is routinely distinct from the parcels beneath it. INSPIRE fixes the parcel attribute set and its locator role, CityGML supplies the encoding-independent geospatial conceptual layer, and IFC fixes the site reference point and elevation datum.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008", "SRC-010" ], "layers": [ { "id": "spatial-footprint", "name": "Spatial footprint", "description": "Boundary geometry, spatial referencing, accuracy and the vertical envelope of the site.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "findings": [ { "id": "site-boundary-geometry-and-vertical-extent", "name": "Site boundary geometry, spatial referencing and vertical extent", "description": "The geometric representation of the site's extent, the coordinate reference system and datums that make it interpretable, its positional accuracy and provenance, and how far it reaches above and below ground.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "questions": [ { "id": "q-boundary-geometry-crs", "text": "What geometry represents the site boundary, and in which coordinate reference system and vertical datum is it expressed?", "kind": "spatial", "answer_data": [ "Boundary geometry", "Geometry type (polygon, multi-polygon, solid)", "Coordinate reference system identifier", "Vertical datum identifier", "Units of measure" ] }, { "id": "q-positional-accuracy", "text": "What is the positional accuracy of the boundary, and by what survey or capture method was it derived?", "kind": "quality", "answer_data": [ "Stated accuracy value and unit", "Capture method", "Survey date", "Surveying organisation and credential", "Accuracy assessment basis" ] }, { "id": "q-reference-point", "text": "What single reference point represents the site for coarse location and relative placement, and how is it defined?", "kind": "spatial", "answer_data": [ "Latitude and longitude", "Reference elevation relative to the stated datum", "Definition rule (centroid, main entrance, survey monument)", "Coordinate reference system" ] }, { "id": "q-vertical-subsurface-extent", "text": "Does the managed extent include airspace, subsurface volume or water column, and to what stated limits?", "kind": "spatial", "answer_data": [ "Upper limit value and datum", "Lower limit value and datum", "Water body inclusion flag", "Basis for the stated limits" ] }, { "id": "q-boundary-versus-legal-line", "text": "Where does the operational boundary diverge from the legal parcel line, and how is that divergence recorded?", "kind": "constraint", "answer_data": [ "Divergence description", "Affected segments", "Reason (licence, occupation, easement, encroachment)", "Evidence reference", "Date identified" ] } ], "data_elements": [ { "id": "site-boundary-geometry", "name": "Site boundary geometry", "description": "Geometric representation of the outer managed extent of the site.", "value_kind": "geometry", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] }, { "id": "site-crs", "name": "Coordinate reference system", "description": "Identifier of the CRS in which all site geometry is expressed.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-008" ] }, { "id": "site-reference-latitude-longitude", "name": "Site reference latitude and longitude", "description": "Coarse world position of the site reference point.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "site-reference-elevation", "name": "Site reference elevation", "description": "Datum elevation of the site reference point relative to a stated vertical datum.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "site-positional-accuracy", "name": "Positional accuracy", "description": "Quantified positional uncertainty of the recorded boundary geometry.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "site-vertical-limits", "name": "Vertical extent limits", "description": "Upper and lower limits of the managed volume, each stated against a named datum.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [ { "id": "site-boundary-survey", "name": "Boundary survey plan", "description": "Surveyed delineation of the site boundary with control points, method statement, accuracy declaration and surveyor attribution.", "media_or_form": [ "survey drawing", "geospatial dataset", "survey report" ], "serial": true, "identity_strategy": "Survey job reference issued by the surveying organisation, plus revision letter and survey date; linked to the site identifier.", "source_refs": [ "SRC-004" ] }, { "id": "site-boundary-geodataset", "name": "Site boundary geospatial dataset", "description": "Machine-readable boundary geometry with declared CRS, accuracy metadata and lineage.", "media_or_form": [ "geospatial feature dataset", "encoding-neutral geometry record" ], "serial": true, "identity_strategy": "Site identifier plus dataset version and beginLifespanVersion timestamp.", "source_refs": [ "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "crs-origin-and-reference-point", "name": "CRS, site origin and reference point", "description": "Precise geospatial information shall be derived from project georeferencing entities relating the engineering coordinate system to a real-world CRS. IfcSite RefLatitude, RefLongitude and RefElevation, if asserted, establish the WGS84 point of local (0,0,0) for approximate use and are not a substitute for IfcMapConversion. INSPIRE recommends a reference point especially useful for small-scale portrayal. Observation time of a survey and event time of a legal boundary change are recorded separately.", "source_refs": [ "SRC-015", "SRC-018", "SRC-019" ], "questions": [ { "id": "crs-origin-and-reference-point-q01", "text": "What coordinate reference system, including datum, projection and epoch, is authoritative for this site?", "kind": "spatial", "answer_data": [ "crs_epsg_or_wkt", "geodetic_datum", "projection", "crs_epoch" ] }, { "id": "crs-origin-and-reference-point-q02", "text": "What easting, northing, orthogonal height, scale and rotation define the map conversion from the engineering system to the CRS?", "kind": "spatial", "answer_data": [ "easting", "northing", "orthogonal_height", "scale", "orientation" ] }, { "id": "crs-origin-and-reference-point-q03", "text": "If approximate WGS84 latitude, longitude and elevation are stored on the site, what is their precision and are they consistent with the map conversion?", "kind": "spatial", "answer_data": [ "ref_latitude", "ref_longitude", "ref_elevation", "precision_note", "consistency_flag" ] }, { "id": "crs-origin-and-reference-point-q04", "text": "When was the georeference surveyed (event time) and when was it ingested into this model (observation time)?", "kind": "temporal", "answer_data": [ "surveyed_at", "ingested_at", "survey_method", "surveyor_party" ] } ], "data_elements": [ { "id": "crs-origin-and-reference-point-data01", "name": "CRS identifier", "description": "EPSG code, WKT or named CRS for the site engineering-to-world mapping.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-015", "SRC-019" ] }, { "id": "crs-origin-and-reference-point-data02", "name": "Map conversion parameters", "description": "Parameters mapping the project engineering coordinate system to the geographic or map CRS.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "crs-origin-and-reference-point-data03", "name": "Reference latitude", "description": "World latitude at the site reference point in WGS84, degrees-minutes-seconds to optional millionths.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "crs-origin-and-reference-point-data04", "name": "Reference longitude", "description": "World longitude at the site reference point in WGS84.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "crs-origin-and-reference-point-data05", "name": "Reference elevation", "description": "Datum elevation of the site origin relative to the local height datum.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "crs-origin-and-reference-point-data06", "name": "Reference point geometry", "description": "INSPIRE-style reference point used for portrayal and locators when full polygon display is impractical.", "value_kind": "geometry", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-018" ] }, { "id": "crs-origin-and-reference-point-data07", "name": "Survey event time", "description": "RFC 3339 timestamp of the survey or legal measurement event, with explicit offset or Z.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-019" ] }, { "id": "crs-origin-and-reference-point-data08", "name": "Ingestion observation time", "description": "RFC 3339 timestamp when the georeference was recorded in this model.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-019" ] } ], "artifacts": [ { "id": "crs-origin-and-reference-point-artifact01", "name": "Georeferencing report", "description": "Survey or BIM-GIS georeferencing report stating CRS, conversion parameters, control points and residuals.", "media_or_form": [ "application/pdf", "application/xml", "model/ifc" ], "serial": true, "identity_strategy": "Survey job identifier plus revision; control-point marks use statutory or survey-network IDs.", "source_refs": [ "SRC-015", "SRC-019" ] } ], "inline_only_rationale": null } ] }, { "id": "land-basis-and-external-context", "name": "Land basis and external context", "description": "The parcels and tenure the site rests on, and the points at which the site meets public networks, addresses and neighbours.", "source_refs": [ "SRC-004", "SRC-010", "SRC-001" ], "findings": [ { "id": "parcel-and-tenure-linkage", "name": "Parcel coverage and tenure linkage", "description": "Which legal land units the site occupies, under what form of tenure, and where the governing legal instruments are held. Rights, restrictions and responsibilities are referenced, not modelled here.", "source_refs": [ "SRC-004", "SRC-010", "SRC-001" ], "questions": [ { "id": "q-parcels-covered", "text": "Which cadastral parcels or equivalent legal land units does the managed extent cover, wholly or partly?", "kind": "relationship", "answer_data": [ "National cadastral reference", "Governed parcel identifier such as inspireId", "Whole or partial coverage flag", "Covered area value and unit", "Coverage assessment date" ] }, { "id": "q-tenure-basis", "text": "Under what tenure does the operator hold each parcel or part, and for what term?", "kind": "ownership", "answer_data": [ "Tenure type", "Holding party reference", "Term start and end dates", "Instrument reference in the land administration model" ] }, { "id": "q-encumbrances", "text": "Which easements, rights of way, wayleaves or covenants constrain how the site may be used?", "kind": "constraint", "answer_data": [ "Encumbrance type", "Affected geometry or segment", "Benefiting party reference", "Instrument reference", "Operational consequence" ] }, { "id": "q-tenure-authority", "text": "Which register or authority is the source of truth for each tenure statement, and when was it last verified?", "kind": "provenance", "answer_data": [ "Register or authority name", "Verification date", "Extract or transaction reference", "Verifying role" ] } ], "data_elements": [ { "id": "covered-parcel-reference", "name": "Covered parcel reference", "description": "Reference to a legal land unit the site occupies, with coverage extent.", "value_kind": "reference", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-004", "SRC-010" ] }, { "id": "tenure-type", "name": "Tenure type", "description": "Coded form of holding under which the operator controls the parcel or part.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-010" ] }, { "id": "tenure-term", "name": "Tenure term", "description": "Start and end dates of the holding, where the tenure is time-limited.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "encumbrance-reference", "name": "Encumbrance reference", "description": "Reference to an easement, wayleave or covenant affecting the site.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "tenure-verified-at", "name": "Tenure verification timestamp", "description": "RFC 3339 timestamp of the most recent verification against the authoritative register.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-004" ] } ], "artifacts": [ { "id": "parcel-schedule", "name": "Parcel and tenure schedule", "description": "Tabular schedule of every parcel touched by the site with tenure type, coverage, encumbrances and register verification dates.", "media_or_form": [ "tabular schedule", "structured dataset" ], "serial": true, "identity_strategy": "Site identifier plus schedule revision and verification date; each row keyed by national cadastral reference.", "source_refs": [ "SRC-004", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "external-context-and-connection-points", "name": "External context, addresses and connection points", "description": "How the site meets the outside world: public access points, postal and emergency addresses, utility demarcation points and adjacency to neighbouring land uses.", "source_refs": [ "SRC-001", "SRC-008", "SRC-003" ], "questions": [ { "id": "q-public-access-points", "text": "At which points does the site connect to the public transport network, and what are the constraints on each?", "kind": "spatial", "answer_data": [ "Access point identifier and location", "Connecting route reference", "Permitted vehicle classes and dimensions", "Restrictions (hours, weight, height)", "Emergency service access flag" ] }, { "id": "q-addresses", "text": "Which addresses are associated with the site, for which purpose, and which is the emergency response address?", "kind": "relationship", "answer_data": [ "Address reference in the address model", "Address purpose (postal, delivery, emergency, registered office)", "Associated access point", "Validity period" ] }, { "id": "q-utility-demarcation", "text": "Where is the demarcation point for each incoming utility, and who is responsible on each side of it?", "kind": "authority", "answer_data": [ "Utility type", "Demarcation point location", "External network operator reference", "Responsibility split statement", "Connection agreement reference" ] }, { "id": "q-adjacency-and-context", "text": "What land uses and sensitive receptors adjoin the site, and what obligations do they create?", "kind": "relationship", "answer_data": [ "Adjoining land use classification", "Sensitive receptor type and distance", "Resulting operational constraint", "Source dataset and date" ] } ], "data_elements": [ { "id": "site-access-point", "name": "Site access point", "description": "A point at which the site connects to the external transport network, with its constraints.", "value_kind": "object", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-008" ] }, { "id": "site-address-reference", "name": "Site address reference", "description": "Typed reference to an address record held in the address sibling model.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "utility-demarcation-point", "name": "Utility demarcation point", "description": "Location and responsibility split for an incoming utility connection.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "adjoining-land-use", "name": "Adjoining land use", "description": "Classified land use or sensitive receptor adjoining the site boundary.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [ { "id": "site-context-plan", "name": "Site context and access plan", "description": "Plan showing site boundary in its surroundings with access points, addresses, utility connection points and adjoining land uses.", "media_or_form": [ "plan drawing", "geospatial dataset" ], "serial": true, "identity_strategy": "Site identifier plus drawing number and revision issued under the site information management process.", "source_refs": [ "SRC-008", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "development-controls-and-easements", "name": "Development controls and easements", "description": "Pset_SiteCommon records BuildableArea, SiteCoverageRatio, FloorAreaRatio, BuildingHeightLimit and TotalArea according to local building codes. LandInfra covers easements, SuperficieObject and condominium interests that legally protect or constrain facilities even when utility design is out of scope. Planning authority is distinct from land owner.", "source_refs": [ "SRC-026", "SRC-019" ], "questions": [ { "id": "development-controls-and-easements-q01", "text": "Which planning or building-code authority sets development controls for this site, and which zoning or plan-unit designations apply?", "kind": "authority", "answer_data": [ "planning_authority_id", "zoning_codes", "plan_unit_ids", "instrument_ids" ] }, { "id": "development-controls-and-easements-q02", "text": "What are the current buildable area, site coverage ratio, floor-area ratio, height limit and total planned area?", "kind": "constraint", "answer_data": [ "buildable_area", "site_coverage_ratio", "floor_area_ratio", "building_height_limit", "total_area" ] }, { "id": "development-controls-and-easements-q03", "text": "Which easements, rights of way, superficie or other interests in land encumber the site, and which facilities do they protect or restrict?", "kind": "constraint", "answer_data": [ "easement_ids", "easement_geometries", "benefited_party_ids", "protected_facility_ids" ] }, { "id": "development-controls-and-easements-q04", "text": "If local code, campus master plan and recorded easements conflict, which constraint is binding for a proposed development?", "kind": "decision", "answer_data": [ "conflicting_controls", "binding_control", "legal_opinion_ref" ] } ], "data_elements": [ { "id": "development-controls-and-easements-data01", "name": "Buildable area", "description": "Maximum site utilisation area according to local building codes.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-026" ] }, { "id": "development-controls-and-easements-data02", "name": "Site coverage ratio", "description": "Maximum utilisation ratio TotalArea/BuildableArea.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-026" ] }, { "id": "development-controls-and-easements-data03", "name": "Floor area ratio", "description": "Maximum ratio of all floor areas to buildable area.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-026" ] }, { "id": "development-controls-and-easements-data04", "name": "Building height limit", "description": "Allowed maximum height of buildings on this site according to local codes.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-026" ] }, { "id": "development-controls-and-easements-data05", "name": "Total planned area", "description": "Total planned area for programming the site space.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-026" ] }, { "id": "development-controls-and-easements-data06", "name": "Easements and interests in land", "description": "Easements, superficie and similar LandInfra interests.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-019" ] } ], "artifacts": [ { "id": "development-controls-and-easements-artifact01", "name": "Planning permit or campus master plan", "description": "Zoning designation, master plan or building-permit envelope that states development controls.", "media_or_form": [ "application/pdf", "application/gml+xml", "image/tiff" ], "serial": true, "identity_strategy": "Permit or plan identifier issued by the planning authority.", "source_refs": [ "SRC-026" ] }, { "id": "development-controls-and-easements-artifact02", "name": "Easement or right-of-way instrument", "description": "Recorded interest in land with geometry where available.", "media_or_form": [ "application/pdf", "application/gml+xml" ], "serial": true, "identity_strategy": "Statutory instrument number; geometry uses cadastral or survey identity.", "source_refs": [ "SRC-019" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "composition-and-internal-structure", "name": "Composition and internal structure", "description": "What the site contains and how its interior is organised into facilities, infrastructure, ground, zones and routes.", "rationale": "The registry defines this model by containment, so the containment edge must be modelled precisely. IFC fixes what a site may aggregate and where a facility record takes over; CityGML supplies grouping, land cover and transportation concepts; ISO 41011 supplies the service and space vocabulary for operated areas.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008", "SRC-014" ], "layers": [ { "id": "contained-facilities-and-infrastructure", "name": "Contained facilities, infrastructure and ground", "description": "The physical contents of the site: built facilities, on-site networks, and the ground and open space between them.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "findings": [ { "id": "contained-facilities-and-containment-semantics", "name": "Contained facilities and containment semantics", "description": "Which facilities the site contains, what containment means for each, and where the site record hands over to the facility record.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "q-facility-inventory", "text": "Which facilities does this site contain, and what identifier does each carry in the facility model?", "kind": "composition", "answer_data": [ "Facility identifier", "Facility type", "Containment start date", "Whether containment is full or partial" ] }, { "id": "q-containment-versus-reference", "text": "For each contained facility, is the relationship exclusive containment or a non-exclusive reference, and can a facility belong to two sites?", "kind": "relationship", "answer_data": [ "Relationship type", "Exclusivity flag", "Justification where a facility is shared", "Conflict resolution rule" ] }, { "id": "q-handover-boundary", "text": "Where does site responsibility end and facility responsibility begin for services, structure and information?", "kind": "authority", "answer_data": [ "Handover point description per discipline", "Responsible party on each side", "Governing agreement reference" ] }, { "id": "q-third-party-facilities", "text": "Which facilities on the site are owned or operated by a party other than the site operator, and what does the site record hold about them?", "kind": "exception", "answer_data": [ "Facility identifier", "Operating party reference", "Information the site operator is entitled to hold", "Access and coordination arrangements" ] } ], "data_elements": [ { "id": "contained-facility-reference", "name": "Contained facility reference", "description": "Reference to a facility record contained by the site, with relationship metadata.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "containment-relationship-type", "name": "Containment relationship type", "description": "Coded semantics of the site-to-facility edge, distinguishing aggregation from spatial containment.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "containment-effective-period", "name": "Containment effective period", "description": "Period during which the facility is treated as part of this site.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "facility-operator-reference", "name": "Facility operating party reference", "description": "Reference to the party operating the facility where it differs from the site operator.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "site-facility-register", "name": "Site facility register", "description": "Authoritative list of facilities contained by the site with identifiers, types, containment periods and operating parties.", "media_or_form": [ "register", "structured dataset" ], "serial": true, "identity_strategy": "Site identifier plus register version; each entry keyed by the facility's own authoritative identifier.", "source_refs": [ "SRC-002", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "on-site-infrastructure-and-networks", "name": "On-site infrastructure and distribution networks", "description": "The site-owned infrastructure between facilities: roads and hardstanding, distribution networks, drainage, on-site generation and storage, and buried assets.", "source_refs": [ "SRC-001", "SRC-008", "SRC-009" ], "questions": [ { "id": "q-network-inventory", "text": "Which distribution and drainage networks does the site own or operate, and what does each serve?", "kind": "composition", "answer_data": [ "Network type", "Network identifier", "Served facilities or zones", "Ownership and operating party" ] }, { "id": "q-buried-assets", "text": "What record exists of buried and concealed infrastructure, at what confidence, and when was it last verified?", "kind": "evidence", "answer_data": [ "Survey or record type", "Confidence or quality level", "Verification date", "Coverage gaps", "Excavation control procedure reference" ] }, { "id": "q-capacity-and-redundancy", "text": "What capacity and redundancy does each on-site network provide, and what is its current headroom?", "kind": "measurement", "answer_data": [ "Rated capacity and unit", "Measured or assessed current load", "Redundancy configuration", "Assessment date and method" ] }, { "id": "q-network-demarcation", "text": "At what point does each on-site network hand over to a facility or to an external operator?", "kind": "authority", "answer_data": [ "Demarcation point identifier", "Party on each side", "Metering point reference", "Governing agreement" ] } ], "data_elements": [ { "id": "on-site-network", "name": "On-site network", "description": "A site-operated distribution, drainage or communications network, with type and served extent.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "network-capacity", "name": "Network capacity", "description": "Rated capacity of an on-site network with unit of measure.", "value_kind": "quantity", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "buried-asset-record-quality", "name": "Buried asset record quality", "description": "Coded confidence level of the record of concealed infrastructure.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "on-site-generation-or-storage", "name": "On-site generation or storage", "description": "Site-level energy or water generation and storage capability relevant to the reporting boundary.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] } ], "artifacts": [ { "id": "site-services-drawing-set", "name": "Site services and utilities drawing set", "description": "As-built or record drawings of on-site networks including buried services, with record confidence and issue status.", "media_or_form": [ "drawing set", "geospatial dataset", "information container" ], "serial": true, "identity_strategy": "Information container identifier assigned under the site information management process, with revision and suitability code.", "source_refs": [ "SRC-012" ] }, { "id": "excavation-permit", "name": "Excavation or ground-disturbance permit", "description": "Issued control document authorising ground disturbance against verified buried-service records.", "media_or_form": [ "permit record" ], "serial": true, "identity_strategy": "Sequential permit number scoped to the site identifier, with issue and expiry timestamps.", "source_refs": [ "SRC-006", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "ground-landscape-and-open-space", "name": "Ground, landscape and open space", "description": "The surface condition of the site between and around facilities: land cover, landscape and ecology, parking, laydown and unbuilt reserve.", "source_refs": [ "SRC-008", "SRC-014" ], "questions": [ { "id": "q-land-cover", "text": "How is the site surface distributed across land cover and surface types, and by what area measure?", "kind": "measurement", "answer_data": [ "Land cover class", "Area value and unit", "Measurement basis and date", "Source dataset" ] }, { "id": "q-protected-features", "text": "Which ecological, heritage or protected features exist on the site, and what constraints do they impose?", "kind": "constraint", "answer_data": [ "Feature type and designation", "Designating authority", "Geometry or location", "Operational constraint", "Designation reference and date" ] }, { "id": "q-operational-open-space", "text": "Which open areas are designated for parking, laydown, storage or circulation, and what are their capacities?", "kind": "composition", "answer_data": [ "Area designation", "Geometry", "Capacity value and unit", "Permitted uses and exclusions" ] }, { "id": "q-grounds-responsibility", "text": "Who is responsible for maintaining each category of open space, and under what service arrangement?", "kind": "ownership", "answer_data": [ "Responsible party reference", "Service agreement reference", "Maintenance regime", "Period of responsibility" ] } ], "data_elements": [ { "id": "land-cover-class", "name": "Land cover class", "description": "Coded surface type covering a defined portion of the site.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "land-cover-area", "name": "Land cover area", "description": "Measured area attributed to a land cover class.", "value_kind": "quantity", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "protected-feature", "name": "Protected feature", "description": "An ecological, heritage or otherwise designated feature within the site with its designating authority.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "designated-open-area", "name": "Designated open area", "description": "An open area with a declared operational designation and capacity.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014" ] } ], "artifacts": [ { "id": "landscape-and-land-cover-plan", "name": "Landscape and land cover plan", "description": "Plan or dataset delineating land cover, landscape zones, protected features and designated open areas with areas and maintenance responsibility.", "media_or_form": [ "plan drawing", "geospatial dataset" ], "serial": true, "identity_strategy": "Site identifier plus drawing or dataset version and survey date.", "source_refs": [ "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "internal-zoning-and-circulation", "name": "Internal zoning and circulation", "description": "How the site's interior is subdivided for management purposes and how people, vehicles and goods move through it.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-006" ], "findings": [ { "id": "site-zones-precincts-and-phases", "name": "Site zones, precincts and development phases", "description": "The overlapping subdivisions used to manage the site: functional precincts, security zones, environmental zones and construction or development phases.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ], "questions": [ { "id": "q-zone-taxonomy", "text": "Which zoning schemes apply to this site, and what zones does each define?", "kind": "classification", "answer_data": [ "Zoning scheme name and purpose", "Zone identifier and label", "Zone geometry", "Governing authority" ] }, { "id": "q-overlapping-zones", "text": "Where do zones from different schemes overlap, and which scheme governs when their rules conflict?", "kind": "constraint", "answer_data": [ "Overlap description", "Precedence rule", "Conflicting rules and resolution", "Approving role" ] }, { "id": "q-phase-status", "text": "Which parts of the site are in a development, construction, commissioning or decommissioning phase, and until when?", "kind": "state", "answer_data": [ "Phase identifier", "Affected geometry", "Phase state", "Planned start and end dates", "Handover criteria" ] }, { "id": "q-zone-authority", "text": "Who may create, alter or dissolve a zone, and what record captures that decision?", "kind": "authority", "answer_data": [ "Authorising role", "Decision record reference", "Effective timestamp", "Notification obligations" ] } ], "data_elements": [ { "id": "site-zone", "name": "Site zone", "description": "A managed subdivision of the site under a named zoning scheme, with geometry and governing rules.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "zone-scheme-identifier", "name": "Zone scheme identifier", "description": "Identifier of the zoning scheme under which a zone is defined.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "development-phase", "name": "Development phase", "description": "A time-bounded phase affecting part of the site, with state and planned dates.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "zone-precedence-rule", "name": "Zone precedence rule", "description": "Rule determining which zoning scheme governs where zones overlap.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "site-zoning-plan", "name": "Site zoning plan", "description": "Plan or dataset delineating all zones by scheme, including security and environmental zones and current development phases.", "media_or_form": [ "plan drawing", "geospatial dataset" ], "serial": true, "identity_strategy": "Site identifier plus zoning scheme name and plan revision; superseded revisions retained.", "source_refs": [ "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "circulation-routes-and-control-points", "name": "Circulation, routes and control points", "description": "The internal movement network of the site including vehicle and pedestrian routes, gates and control points, accessible routes and emergency vehicle access.", "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "q-internal-route-network", "text": "What internal route network exists for vehicles, pedestrians and goods, and what restrictions apply to each route?", "kind": "composition", "answer_data": [ "Route identifier and geometry", "Route mode and permitted users", "Dimensional and load restrictions", "One-way or directional constraints" ] }, { "id": "q-control-points", "text": "Which gates, barriers and control points sit on the internal network, and what is each capable of enforcing?", "kind": "process", "answer_data": [ "Control point identifier and location", "Enforcement capability", "Operating hours", "Fallback procedure on failure" ] }, { "id": "q-accessible-routes", "text": "Which routes are designated as step-free or otherwise accessible, and when was this last verified?", "kind": "requirement", "answer_data": [ "Accessible route identifier", "Accessibility standard applied", "Verification date and method", "Known deficiencies" ] }, { "id": "q-emergency-vehicle-access", "text": "What routes and hardstanding are reserved for emergency vehicle access, and what keeps them clear?", "kind": "exception", "answer_data": [ "Emergency route geometry", "Vehicle class and dimensions accommodated", "Keep-clear enforcement measure", "Agreement with emergency services" ] } ], "data_elements": [ { "id": "internal-route", "name": "Internal route", "description": "A defined circulation route within the site with mode, geometry and restrictions.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "control-point", "name": "Control point", "description": "A gate, barrier or checkpoint on the internal network with its enforcement capability.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "accessible-route-flag", "name": "Accessible route flag", "description": "Whether a route is designated accessible under a named standard.", "value_kind": "boolean", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "emergency-route-reference", "name": "Emergency vehicle route reference", "description": "Reference to a route reserved for emergency vehicle access.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "site-circulation-plan", "name": "Site circulation and access plan", "description": "Plan of internal routes, control points, accessible routes and emergency vehicle access, issued to occupants and emergency services.", "media_or_form": [ "plan drawing", "wayfinding signage set", "geospatial dataset" ], "serial": true, "identity_strategy": "Site identifier plus plan revision and issue date; issue recipients logged.", "source_refs": [ "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "control-authorisation-and-access", "name": "Control, authorisation and access", "description": "Who is accountable for the site, what public authorisations it holds, and who may physically enter it or see information about it.", "rationale": "ISO 55001 requires assigned accountability and a defined management-system scope; EPA FRS demonstrates that regulatory interests attach to a site independently of who owns it; NIST SP 800-53 PE controls give a normative pattern for physical access authorisation, enforcement and logging. Site information is itself a controlled asset, since boundary and security detail is exploitable.", "source_refs": [ "SRC-003", "SRC-007", "SRC-009", "SRC-012" ], "layers": [ { "id": "ownership-and-authorisation", "name": "Ownership, accountability and authorisation", "description": "The parties accountable for the site and the public authorisations under which it operates.", "source_refs": [ "SRC-003", "SRC-009", "SRC-010" ], "findings": [ { "id": "ownership-operator-and-accountability", "name": "Ownership, operatorship and accountability", "description": "Distinguishing the legal owner, the operator, the duty holder and delegated site management roles, each with scope and effective dates.", "source_refs": [ "SRC-009", "SRC-010", "SRC-014" ], "questions": [ { "id": "q-owner-versus-operator", "text": "Who is the legal owner of the site, who operates it, and are they the same party?", "kind": "ownership", "answer_data": [ "Owning party reference", "Operating party reference", "Basis of the operating relationship", "Effective period" ] }, { "id": "q-duty-holder", "text": "Which named role carries statutory duty-holder accountability for the site, and for which duties?", "kind": "authority", "answer_data": [ "Role title", "Party or person reference", "Duties covered", "Statutory basis", "Appointment date" ] }, { "id": "q-delegation-scope", "text": "What decisions has the accountable party delegated to site management, and what limits apply?", "kind": "authority", "answer_data": [ "Delegated decision types", "Financial or scope limits", "Delegate role", "Delegation instrument reference", "Review date" ] }, { "id": "q-accountability-change", "text": "How is a change of owner, operator or duty holder recorded, and what must be transferred with it?", "kind": "lifecycle", "answer_data": [ "Change event type", "Effective and recorded timestamps", "Information handover checklist", "Regulatory notification obligations" ] } ], "data_elements": [ { "id": "owning-party-reference", "name": "Owning party reference", "description": "Reference to the legal owner in the organisation or party model.", "value_kind": "reference", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-010" ] }, { "id": "operating-party-reference", "name": "Operating party reference", "description": "Reference to the party responsible for day-to-day operation of the site.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "duty-holder-role", "name": "Duty holder role", "description": "Named accountable role with its statutory basis and appointment date.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "delegation-instrument-reference", "name": "Delegation instrument reference", "description": "Reference to the document that establishes delegated authority and its limits.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "accountability-effective-from", "name": "Accountability effective from", "description": "RFC 3339 timestamp from which an accountability assignment takes effect.", "value_kind": "timestamp", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "accountability-matrix", "name": "Site accountability matrix", "description": "Approved record of owner, operator, duty holders and delegates with scope, limits and effective dates.", "media_or_form": [ "approved matrix document", "structured record" ], "serial": true, "identity_strategy": "Site identifier plus matrix version and approval timestamp; superseded versions retained for audit.", "source_refs": [ "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "regulatory-authorisations-and-registry-interests", "name": "Regulatory authorisations and registry interests", "description": "The permits, licences and consents the site holds, and the external regulatory registries in which the site appears as a regulated entity.", "source_refs": [ "SRC-003", "SRC-006", "SRC-009" ], "questions": [ { "id": "q-authorisations-held", "text": "Which permits, licences and consents does the site hold, from which authority, and with what validity period?", "kind": "authority", "answer_data": [ "Authorisation type", "Issuing authority", "Authorisation identifier", "Valid from and valid to dates", "Current status" ] }, { "id": "q-authorisation-conditions", "text": "Which conditions attached to each authorisation constrain site operations or trigger reporting?", "kind": "constraint", "answer_data": [ "Condition text or reference", "Constrained activity", "Reporting frequency and recipient", "Consequence of breach" ] }, { "id": "q-registry-interests", "text": "In which regulatory registries does this site appear, under what registry identifier, and does the registry record match the managed extent?", "kind": "interoperability", "answer_data": [ "Registry name", "Registry identifier for the site", "Program interest types", "Extent alignment assessment", "Last reconciliation date" ] }, { "id": "q-authorisation-renewal", "text": "What are the renewal, variation and surrender triggers for each authorisation, and who owns each action?", "kind": "process", "answer_data": [ "Trigger type", "Lead time", "Responsible role", "Evidence required", "Next action due date" ] } ], "data_elements": [ { "id": "authorisation-reference", "name": "Authorisation reference", "description": "Reference to a permit, licence or consent held for the site, in the authorisation sibling model.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "issuing-authority", "name": "Issuing authority", "description": "The public authority that issued an authorisation.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "authorisation-validity-period", "name": "Authorisation validity period", "description": "Valid-from and valid-to dates of an authorisation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "registry-interest", "name": "Regulatory registry interest", "description": "An entry recording that the site appears in a named external regulatory registry under a specific identifier and interest type.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "registry-extent-alignment", "name": "Registry extent alignment", "description": "Assessment of whether an external registry record covers the whole site, part of it, or more than it.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "authorisation-register", "name": "Site authorisation register", "description": "Register of every permit, licence and consent with authority, identifier, validity, conditions and next action date.", "media_or_form": [ "register", "structured dataset" ], "serial": true, "identity_strategy": "Site identifier plus register version; each entry keyed by the issuing authority's authorisation identifier.", "source_refs": [ "SRC-003", "SRC-009" ] }, { "id": "compliance-report", "name": "Regulatory compliance report", "description": "Periodic report submitted to a regulator against authorisation conditions.", "media_or_form": [ "submitted report", "structured submission" ], "serial": true, "identity_strategy": "Authorisation identifier plus reporting period and submission timestamp in RFC 3339.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "physical-and-information-access", "name": "Physical and information access", "description": "Control of entry to the site and control of disclosure of information about it.", "source_refs": [ "SRC-007", "SRC-012", "SRC-003" ], "findings": [ { "id": "physical-access-control-and-perimeter", "name": "Perimeter, physical access authorisation and logging", "description": "How the site perimeter is defined and defended, how entry authorisations are granted and enforced at defined entry and exit points, and what access records are kept.", "source_refs": [ "SRC-007", "SRC-006" ], "questions": [ { "id": "q-perimeter-definition", "text": "What physically constitutes the site perimeter, and which entry and exit points are designated for access enforcement?", "kind": "security", "answer_data": [ "Perimeter description and geometry", "Designated entry and exit point identifiers", "Barrier type per segment", "Publicly accessible areas within the perimeter" ] }, { "id": "q-access-authorisation-model", "text": "Who authorises physical access to the site and to each security zone, and on what basis is authorisation granted and revoked?", "kind": "access", "answer_data": [ "Authorising role", "Authorisation criteria", "Credential type issued", "Review and revocation triggers", "Access list maintenance frequency" ] }, { "id": "q-visitor-and-contractor-control", "text": "How are visitors and contractors identified, escorted and accounted for while on site?", "kind": "process", "answer_data": [ "Identification requirement", "Escort rule by zone", "Induction requirement", "Sign-in and sign-out record", "Maximum permitted duration" ] }, { "id": "q-access-logging-retention", "text": "What physical access records are captured at each point, and how long are they retained?", "kind": "retention", "answer_data": [ "Logged fields", "Log capture point", "Retention period", "Lawful basis for retention", "Disposal method" ] }, { "id": "q-access-device-inventory", "text": "How are keys, cards and other physical access devices inventoried, and when are combinations changed?", "kind": "security", "answer_data": [ "Device inventory frequency", "Device holder register", "Change triggers (loss, compromise, transfer, termination)", "Last inventory date" ] } ], "data_elements": [ { "id": "perimeter-segment", "name": "Perimeter segment", "description": "A described segment of the site perimeter with its barrier type and condition.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "designated-entry-point", "name": "Designated entry or exit point", "description": "A point at which physical access authorisations are enforced.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "access-authorisation-record", "name": "Access authorisation record", "description": "A grant of physical access to the site or a zone, with holder, scope and validity.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "access-event-log-entry", "name": "Access event log entry", "description": "A recorded entry or exit event with timestamp, point and credential reference.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "access-log-retention-period", "name": "Access log retention period", "description": "Declared retention duration for physical access logs.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "site-security-plan", "name": "Site physical security plan", "description": "Controlled document describing perimeter, zones, entry points, authorisation model, escorting rules and device management.", "media_or_form": [ "controlled document" ], "serial": true, "identity_strategy": "Site identifier plus plan version and approval timestamp; classified and distribution-controlled.", "source_refs": [ "SRC-007" ] }, { "id": "physical-access-log", "name": "Physical access log", "description": "Time-series record of entry and exit events at designated points, retained under a declared retention period.", "media_or_form": [ "append-only log", "structured dataset" ], "serial": true, "identity_strategy": "Entry point identifier plus RFC 3339 event timestamp and credential reference.", "source_refs": [ "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "site-information-sensitivity-and-disclosure", "name": "Site information sensitivity and disclosure control", "description": "Classification of site information by sensitivity, the rules for redaction and need-to-know sharing, and the tension between mandatory public disclosure and security-driven withholding.", "source_refs": [ "SRC-012", "SRC-007", "SRC-003" ], "questions": [ { "id": "q-sensitivity-classification", "text": "How is each class of site information classified for sensitivity, and who assigns the classification?", "kind": "privacy", "answer_data": [ "Information class", "Sensitivity level", "Classification scheme reference", "Assigning role", "Review date" ] }, { "id": "q-redaction-rules", "text": "Which site details must be withheld or redacted before information leaves the controlled environment, and on what basis?", "kind": "security", "answer_data": [ "Withheld element types", "Redaction rule", "Justification and legal basis", "Approving role", "Redacted derivative identifier" ] }, { "id": "q-mandatory-disclosure", "text": "Which site information must be published or disclosed on request regardless of the operator's preference?", "kind": "access", "answer_data": [ "Disclosure obligation source", "Information covered", "Disclosure channel and timescale", "Permitted exemptions" ] }, { "id": "q-conflict-disclosure-security", "text": "Where a disclosure obligation conflicts with a security restriction, what process resolves it and who decides?", "kind": "exception", "answer_data": [ "Conflict description", "Resolution process", "Deciding role", "Decision record reference", "Date of decision" ] } ], "data_elements": [ { "id": "information-sensitivity-class", "name": "Information sensitivity class", "description": "Coded sensitivity level assigned to a class of site information.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "redaction-rule", "name": "Redaction rule", "description": "Rule stating which elements are removed or generalised in externally shared derivatives.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "disclosure-obligation-reference", "name": "Disclosure obligation reference", "description": "Reference to the legal or contractual basis compelling disclosure of specified site information.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "sensitivity-review-date", "name": "Sensitivity review date", "description": "Date on which the sensitivity classification is next due for review.", "value_kind": "date", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "information-classification-register", "name": "Site information classification register", "description": "Register mapping each class of site information to its sensitivity level, redaction rule, disclosure obligations and review date.", "media_or_form": [ "register", "structured dataset" ], "serial": true, "identity_strategy": "Site identifier plus register version and classification review date.", "source_refs": [ "SRC-007", "SRC-012" ] }, { "id": "redacted-site-dataset", "name": "Redacted public site dataset", "description": "Derivative dataset produced for external publication with security-sensitive elements removed under an approved redaction rule.", "media_or_form": [ "published dataset", "published plan" ], "serial": true, "identity_strategy": "Parent dataset identifier plus redaction profile identifier and publication timestamp.", "source_refs": [ "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-operations-and-resilience", "name": "Lifecycle, operations and resilience", "description": "How the site changes over time, how it is operated day to day, and how it withstands and responds to hazards.", "rationale": "ISO 55001 requires life-cycle planning and control of change; ISO 19650 supplies the trigger-event pattern that drives information updates; OSHA 29 CFR 1910.38 sets the normative minimum content of a site emergency action plan. Together these establish state, change and resilience as distinct, evidenced concerns rather than free-text attributes.", "source_refs": [ "SRC-006", "SRC-009", "SRC-012" ], "layers": [ { "id": "lifecycle-and-operations", "name": "Lifecycle, change events and operating model", "description": "Site states and their transitions, boundary change and lineage, and the operating regime under which the site runs.", "source_refs": [ "SRC-009", "SRC-012", "SRC-014" ], "findings": [ { "id": "lifecycle-states-and-boundary-change-events", "name": "Lifecycle states, transitions and boundary change lineage", "description": "The controlled vocabulary of site states, the authority and evidence needed to transition between them, and how splits, merges and boundary changes preserve traceable lineage with separate event and record times.", "source_refs": [ "SRC-009", "SRC-012", "SRC-004" ], "questions": [ { "id": "q-state-vocabulary", "text": "What controlled vocabulary of site states applies, and which state is current as at which effective date?", "kind": "state", "answer_data": [ "State vocabulary and version", "Current state value", "Effective date of current state", "Prior state and transition date" ] }, { "id": "q-transition-authority-evidence", "text": "Who may authorise each state transition, and what evidence must exist before the transition is recorded?", "kind": "authority", "answer_data": [ "Transition type", "Authorising role", "Required evidence artifacts", "Approval record reference", "Preconditions checked" ] }, { "id": "q-split-merge-lineage", "text": "When a site is split, merged or partly transferred, how are predecessor and successor identifiers linked?", "kind": "provenance", "answer_data": [ "Event type (split, merge, transfer, absorption)", "Predecessor identifiers", "Successor identifiers", "Effective date", "Portion of extent affected" ] }, { "id": "q-event-versus-record-time", "text": "For every recorded change, what are the event time and the observation or ingestion time, and do they differ?", "kind": "temporal", "answer_data": [ "Event time (RFC 3339 with offset or Z)", "Recorded or ingested time (RFC 3339)", "Divergence explanation where material", "Recording actor" ] }, { "id": "q-trigger-events", "text": "Which foreseeable and unforeseeable trigger events require the site record to be updated, and within what timescale?", "kind": "event", "answer_data": [ "Trigger event type", "Foreseeable flag", "Required information update", "Response timescale", "Responsible role" ] } ], "data_elements": [ { "id": "site-lifecycle-state", "name": "Site lifecycle state", "description": "Current coded state of the site drawn from a versioned state vocabulary.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "state-effective-from", "name": "State effective from", "description": "RFC 3339 timestamp at which the current state took effect in the world.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-004" ] }, { "id": "state-recorded-at", "name": "State recorded at", "description": "RFC 3339 timestamp at which the state change was recorded in the system, held separately from the event time.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005" ] }, { "id": "predecessor-site-reference", "name": "Predecessor site reference", "description": "Identifier of a site record that this site succeeded through split, merge or transfer.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "successor-site-reference", "name": "Successor site reference", "description": "Identifier of a site record that succeeded this one.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "trigger-event-record", "name": "Trigger event record", "description": "A recorded occurrence that required the site information to be created or updated.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "site-change-log", "name": "Site change and lineage log", "description": "Append-only record of every state transition, boundary change and lineage link with event time, record time, authorising role and evidence references.", "media_or_form": [ "append-only log", "structured dataset" ], "serial": true, "identity_strategy": "Site identifier plus monotonically increasing change sequence number and RFC 3339 record timestamp.", "source_refs": [ "SRC-012", "SRC-004" ] }, { "id": "state-transition-approval", "name": "State transition approval record", "description": "Approval capturing the decision to move the site to a new state, with preconditions evidenced.", "media_or_form": [ "approval record", "signed decision document" ], "serial": true, "identity_strategy": "Site identifier plus transition type and approval timestamp; references the change log sequence number.", "source_refs": [ "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "operating-model-hours-and-site-rules", "name": "Operating model, hours, site rules and services", "description": "The regime under which the site runs: operating periods, mandatory site rules and inductions, permit-to-work controls, and the services provided to occupants and how they are sourced.", "source_refs": [ "SRC-014", "SRC-009", "SRC-006" ], "questions": [ { "id": "q-operating-periods", "text": "What operating hours and seasonal or shift regimes apply to the site and to individual zones?", "kind": "temporal", "answer_data": [ "Operating period definition", "Applicable zones", "Time zone and offset handling", "Exceptions and closure dates" ] }, { "id": "q-site-rules-induction", "text": "What rules must every person on site comply with, and what induction or competence is required before entry?", "kind": "requirement", "answer_data": [ "Rule set reference and version", "Induction requirement by person category", "Validity period of induction", "Verification method" ] }, { "id": "q-permit-to-work", "text": "Which activities on this site require a permit to work or equivalent control, and who issues them?", "kind": "process", "answer_data": [ "Controlled activity type", "Permit type", "Issuing role", "Preconditions and isolations", "Permit validity period" ] }, { "id": "q-service-provision", "text": "Which facility services are provided across the site, by whom, and under what agreed performance levels?", "kind": "process", "answer_data": [ "Service type", "Providing party reference", "Agreement reference", "Performance measures and targets", "Coverage extent" ] } ], "data_elements": [ { "id": "operating-period", "name": "Operating period", "description": "A defined operating window for the site or a zone, with explicit time zone handling.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "site-rule-set-reference", "name": "Site rule set reference", "description": "Reference to the versioned set of rules binding on persons on site.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "permit-to-work-type", "name": "Permit-to-work type", "description": "A controlled activity category requiring formal permit authorisation on this site.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "site-service-arrangement", "name": "Site service arrangement", "description": "A facility service delivered across the site, its provider and its performance basis.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014" ] } ], "artifacts": [ { "id": "site-rules-and-induction-pack", "name": "Site rules and induction pack", "description": "Issued rules, induction content and acknowledgement record binding on all persons entering the site.", "media_or_form": [ "issued document", "training package", "acknowledgement record" ], "serial": true, "identity_strategy": "Site identifier plus rule set version and issue date; acknowledgements keyed by person reference and timestamp.", "source_refs": [ "SRC-009", "SRC-014" ] }, { "id": "permit-to-work-record", "name": "Permit-to-work record", "description": "Issued permit authorising a controlled activity with preconditions, isolations, validity window and sign-off.", "media_or_form": [ "permit record" ], "serial": true, "identity_strategy": "Sequential permit number scoped to the site identifier, with RFC 3339 issue and expiry timestamps.", "source_refs": [ "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "construction-work-site-and-temporary-holdings", "name": "Construction site of the work and temporary holdings", "description": "ISO 6707-1 site is where construction or other development is undertaken. 29 CFR 5.2 extends site of the work to secondary fabrication sites and adjacent dedicated support sites for wage law. Pset_LandRegistration.IsPermanentID distinguishes temporary identities. A construction envelope may exist only for a duration and must not silently replace the permanent campus identity.", "source_refs": [ "SRC-027", "SRC-016", "SRC-024" ], "questions": [ { "id": "construction-work-site-and-temporary-holdings-q01", "text": "Is this instance a permanent holding, a time-bounded construction site of the work, or a secondary/support site, and what are its start and planned end times?", "kind": "lifecycle", "answer_data": [ "holding_kind", "valid_from", "valid_to", "is_permanent_id" ] }, { "id": "construction-work-site-and-temporary-holdings-q02", "text": "Which secondary construction or adjacent support sites are linked to the primary site of the work, and are they inside the permanent campus?", "kind": "relationship", "answer_data": [ "secondary_site_ids", "support_site_ids", "inside_campus_flag" ] }, { "id": "construction-work-site-and-temporary-holdings-q03", "text": "Does a labour-law site-of-the-work envelope differ from the operational campus, and which activities are excluded as general manufacturing?", "kind": "exception", "answer_data": [ "wage_envelope_geometry", "exclusions", "legal_basis" ] } ], "data_elements": [ { "id": "construction-work-site-and-temporary-holdings-data01", "name": "Holding kind", "description": "permanent, primary-construction, secondary-construction or adjacent-support.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-027", "SRC-016" ] }, { "id": "construction-work-site-and-temporary-holdings-data02", "name": "Valid from", "description": "RFC 3339 start of the construction or temporary holding.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-027" ] }, { "id": "construction-work-site-and-temporary-holdings-data03", "name": "Valid to", "description": "RFC 3339 planned or actual end of the temporary holding.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-027" ] }, { "id": "construction-work-site-and-temporary-holdings-data04", "name": "Linked permanent site identifier", "description": "Permanent campus or site that a temporary construction envelope overlays.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] } ], "artifacts": [ { "id": "construction-work-site-and-temporary-holdings-artifact01", "name": "Construction site notice or wage determination attachment", "description": "Notice identifying primary, secondary and support sites of the work.", "media_or_form": [ "application/pdf" ], "serial": true, "identity_strategy": "Contract or project identifier plus labour-agency determination number.", "source_refs": [ "SRC-027" ] } ], "inline_only_rationale": null } ] }, { "id": "hazards-and-emergency", "name": "Hazards, environmental conditions and emergency response", "description": "What can go wrong at this site and what is in place to prepare for and respond to it.", "source_refs": [ "SRC-006", "SRC-003", "SRC-009" ], "findings": [ { "id": "hazard-exposure-and-environmental-conditions", "name": "Hazard exposure, contamination and environmental constraints", "description": "The site's exposure to natural and process hazards, its contamination status and legacy, and the environmental constraints that limit what may be done on it.", "source_refs": [ "SRC-003", "SRC-009", "SRC-008" ], "questions": [ { "id": "q-natural-hazard-exposure", "text": "To which natural hazards is the site exposed, at what assessed severity and return period, and from which authoritative dataset?", "kind": "measurement", "answer_data": [ "Hazard type", "Severity or zone classification", "Return period or probability", "Source dataset and version", "Assessment date" ] }, { "id": "q-contamination-status", "text": "What is the known contamination status of the site's ground and groundwater, and what remediation history exists?", "kind": "evidence", "answer_data": [ "Contaminant types identified", "Investigation report references", "Remediation actions and dates", "Residual constraints", "Regulatory position" ] }, { "id": "q-process-hazards", "text": "Which hazardous substances or processes are present on site, in what quantities, and what regulatory thresholds do they engage?", "kind": "constraint", "answer_data": [ "Substance or process type", "Quantity and unit", "Threshold regime engaged", "Notification status", "Separation distances required" ] }, { "id": "q-assessment-currency", "text": "How current is each hazard and environmental assessment, and what triggers reassessment?", "kind": "quality", "answer_data": [ "Assessment date", "Validity or review period", "Reassessment triggers", "Responsible role", "Known gaps" ] } ], "data_elements": [ { "id": "natural-hazard-exposure", "name": "Natural hazard exposure", "description": "Assessed exposure of the site to a named natural hazard, with severity and source dataset.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "contamination-status", "name": "Contamination status", "description": "Coded status of known ground or groundwater contamination on the site.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "hazardous-substance-inventory-entry", "name": "Hazardous substance inventory entry", "description": "A hazardous substance held on site with quantity and applicable threshold regime.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "hazard-assessment-date", "name": "Hazard assessment date", "description": "Date of the most recent assessment for a given hazard.", "value_kind": "date", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "site-hazard-assessment", "name": "Site hazard and environmental assessment report", "description": "Assessment covering natural hazard exposure, ground conditions, contamination and environmental constraints, with method, date and author.", "media_or_form": [ "assessment report", "structured dataset" ], "serial": true, "identity_strategy": "Report reference issued by the assessing organisation plus assessment date, linked to the site identifier.", "source_refs": [ "SRC-003", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "emergency-preparedness-and-response", "name": "Emergency preparedness and response arrangements", "description": "The site's emergency action plan and supporting arrangements: alarm, evacuation, muster and accounting, assigned roles, and the triggers that require the plan to be reviewed.", "source_refs": [ "SRC-006", "SRC-009" ], "questions": [ { "id": "q-written-plan-requirement", "text": "Is a written emergency action plan required for this site, and where is the current approved version held?", "kind": "requirement", "answer_data": [ "Requirement basis and jurisdiction", "Written or oral permitted", "Plan document reference and version", "Approval date", "Location of controlled copies" ] }, { "id": "q-evacuation-and-accounting", "text": "What evacuation type, exit route assignments and muster points apply, and how are all persons accounted for afterwards?", "kind": "process", "answer_data": [ "Evacuation type", "Exit route assignments by zone", "Muster point identifiers and locations", "Accounting method and roster source", "Time target for accounting" ] }, { "id": "q-alarm-system", "text": "What employee alarm system is in place, what distinct signals does it use, and how is it maintained and tested?", "kind": "requirement", "answer_data": [ "Alarm system description", "Signal meanings", "Coverage extent", "Maintenance and test regime", "Last test date" ] }, { "id": "q-emergency-roles-and-review", "text": "Who has assigned emergency duties including rescue, medical and critical-operations roles, and what triggers a review of the plan with them?", "kind": "authority", "answer_data": [ "Role title and holder reference", "Duties assigned", "Training record reference", "Review triggers (plan created, duties changed, plan modified)", "Last review date" ] }, { "id": "q-external-responder-interface", "text": "What arrangements exist with external emergency responders, including site access, hazard briefing and rendezvous points?", "kind": "relationship", "answer_data": [ "Responder organisation reference", "Access arrangement", "Hazard information provided", "Rendezvous point", "Agreement or liaison date" ] } ], "data_elements": [ { "id": "emergency-action-plan-reference", "name": "Emergency action plan reference", "description": "Reference to the current approved emergency action plan for the site.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "muster-point", "name": "Muster point", "description": "A designated assembly location with identifier, geometry and capacity.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "alarm-system-descriptor", "name": "Alarm system descriptor", "description": "Description of the employee alarm system, its signals and coverage.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "emergency-role-assignment", "name": "Emergency role assignment", "description": "Assignment of a named emergency duty to a role or person, with training evidence.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "plan-last-reviewed-at", "name": "Plan last reviewed at", "description": "RFC 3339 timestamp of the most recent review of the emergency action plan.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "emergency-action-plan", "name": "Emergency action plan", "description": "Controlled plan covering emergency reporting, evacuation type and exit route assignments, critical-operations staff, post-evacuation accounting, rescue and medical duties, and named contacts.", "media_or_form": [ "controlled document", "structured plan record" ], "serial": true, "identity_strategy": "Site identifier plus plan version and approval timestamp; controlled distribution list retained.", "source_refs": [ "SRC-006" ] }, { "id": "drill-and-test-record", "name": "Emergency drill and alarm test record", "description": "Record of each evacuation drill and alarm test with date, participation, accounting time achieved and corrective actions.", "media_or_form": [ "test record", "structured dataset" ], "serial": true, "identity_strategy": "Site identifier plus drill sequence number and RFC 3339 start timestamp.", "source_refs": [ "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "measurement-evidence-and-interoperability", "name": "Measurement, evidence and interoperability", "description": "How the site is quantified, monitored, evidenced and made intelligible to other systems and standards.", "rationale": "EPA campus benchmarking and the GHG Protocol both show that a site's reporting boundary is a deliberate construct with its own aggregation rules; SOSA/SSN supplies the observation pattern with normative time separation; ISO 19650 supplies information containers and the common data environment; IFC, CityGML and FRS define the crosswalk targets an agent must reconcile against.", "source_refs": [ "SRC-005", "SRC-008", "SRC-011", "SRC-012", "SRC-013" ], "layers": [ { "id": "measurement-and-reporting-boundary", "name": "Measurement and reporting boundary", "description": "Quantities describing the site and the deliberately constructed boundaries used for resource and emissions accounting.", "source_refs": [ "SRC-011", "SRC-013", "SRC-004" ], "findings": [ { "id": "site-quantities-areas-and-capacity", "name": "Site quantities, areas, occupancy and capacity", "description": "The measured quantities that describe the site, each with a declared measurement basis, unit, method and date, distinguishing land area from aggregated floor area and design capacity from actual occupancy.", "source_refs": [ "SRC-004", "SRC-011", "SRC-014" ], "questions": [ { "id": "q-area-measures", "text": "Which area measures are recorded for the site, on what measurement basis, and in which units?", "kind": "measurement", "answer_data": [ "Measure name (site land area, aggregated gross floor area, hardstanding area)", "Value and unit", "Measurement basis or standard applied", "Measurement date", "Source of measurement" ] }, { "id": "q-area-versus-registered", "text": "Where the measured site area differs from registered parcel area values, which prevails for which purpose?", "kind": "quality", "answer_data": [ "Measured value", "Registered value", "Difference and tolerance", "Prevailing value by purpose", "Explanation" ] }, { "id": "q-occupancy", "text": "What occupancy or population does the site carry, measured how and over what period?", "kind": "measurement", "answer_data": [ "Occupancy metric definition", "Value and unit", "Measurement period", "Collection method", "Peak versus average basis" ] }, { "id": "q-capacity-limits", "text": "What capacity limits constrain the site, and which are regulatory rather than physical?", "kind": "constraint", "answer_data": [ "Capacity type", "Limit value and unit", "Regulatory or physical basis", "Authorising reference", "Current headroom" ] } ], "data_elements": [ { "id": "site-land-area", "name": "Site land area", "description": "Measured area of the site's managed extent with unit and measurement basis.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "aggregated-gross-floor-area", "name": "Aggregated gross floor area", "description": "Sum of gross floor area of facilities within the reporting boundary, with the standard applied.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "site-occupancy", "name": "Site occupancy", "description": "Population metric for the site with period and collection method.", "value_kind": "quantity", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "capacity-limit", "name": "Capacity limit", "description": "A constraining capacity value with its regulatory or physical basis.", "value_kind": "quantity", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "measurement-taken-at", "name": "Measurement timestamp", "description": "RFC 3339 timestamp at which a quantity was measured or determined.", "value_kind": "timestamp", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] } ], "artifacts": [ { "id": "site-quantity-schedule", "name": "Site quantity schedule", "description": "Schedule of all recorded site quantities with basis, unit, method, source and measurement date.", "media_or_form": [ "tabular schedule", "structured dataset" ], "serial": true, "identity_strategy": "Site identifier plus schedule version and measurement reference date.", "source_refs": [ "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "reporting-boundary-and-resource-accounting", "name": "Reporting boundary and resource accounting", "description": "How energy, water, waste and greenhouse-gas accounting boundaries are drawn over the site, how parent and child aggregation works, and how shared plant and campus-wide meters are allocated.", "source_refs": [ "SRC-011", "SRC-013" ], "questions": [ { "id": "q-reporting-boundary-definition", "text": "For each reporting scheme, what boundary is drawn over the site, and how does it differ from the managed extent?", "kind": "definition", "answer_data": [ "Reporting scheme name and version", "Boundary definition", "Included and excluded facilities", "Divergence from managed extent", "Reporting period" ] }, { "id": "q-parent-child-aggregation", "text": "Is the site represented as a parent property with child properties, and what aggregation rules apply?", "kind": "composition", "answer_data": [ "Parent property identifier", "Child property identifiers", "Aggregation rule", "Nesting restriction acknowledged", "Eligibility for campus-level scoring" ] }, { "id": "q-meter-coverage-allocation", "text": "Which meters serve the whole site versus individual facilities, and how is shared plant consumption allocated?", "kind": "measurement", "answer_data": [ "Meter identifier and type", "Served extent", "Recording level (parent or child)", "Allocation method and basis", "Estimation flag where readings are missing" ] }, { "id": "q-consolidation-approach", "text": "Which greenhouse-gas consolidation approach applies to this site, and which scopes are reported for it?", "kind": "decision", "answer_data": [ "Consolidation approach (equity share, financial control, operational control)", "Ownership or control percentage", "Scopes reported", "Base year", "Recalculation policy" ] }, { "id": "q-reporting-data-quality", "text": "What is the completeness and quality of each reported quantity, and how much is estimated?", "kind": "quality", "answer_data": [ "Completeness percentage", "Estimated versus metered split", "Estimation method", "Assurance level and assurer", "Restatement history" ] } ], "data_elements": [ { "id": "reporting-boundary-definition", "name": "Reporting boundary definition", "description": "Named boundary drawn over the site for a specific reporting scheme and period.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011", "SRC-013" ] }, { "id": "parent-property-reference", "name": "Parent property reference", "description": "Identifier under which the site is registered as a parent property in a benchmarking scheme.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "child-property-reference", "name": "Child property reference", "description": "Identifier of a single-building property associated with the parent.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "meter-coverage", "name": "Meter coverage", "description": "A meter with its served extent and the level at which its readings are recorded.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "consolidation-approach", "name": "GHG consolidation approach", "description": "Coded organizational boundary approach applied to the site's emissions.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "reported-quantity", "name": "Reported quantity", "description": "A reported consumption or emissions value for a scheme and period, with estimation flag.", "value_kind": "quantity", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] } ], "artifacts": [ { "id": "reporting-boundary-statement", "name": "Reporting boundary statement", "description": "Documented definition of each reporting boundary, its inclusions, exclusions, allocation methods and consolidation approach.", "media_or_form": [ "statement document", "structured record" ], "serial": true, "identity_strategy": "Site identifier plus reporting scheme name, reporting period and statement version.", "source_refs": [ "SRC-011", "SRC-013" ] }, { "id": "site-consumption-dataset", "name": "Site consumption and emissions dataset", "description": "Periodic dataset of metered and estimated energy, water, waste and emissions values at parent and child level.", "media_or_form": [ "time-series dataset", "submitted return" ], "serial": true, "identity_strategy": "Site identifier plus scheme, reporting period start and end in RFC 3339, and submission version.", "source_refs": [ "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "observation-evidence-and-records", "name": "Observation, evidence and records", "description": "Site-scale sensing and the documentary record that evidences everything asserted about the site.", "source_refs": [ "SRC-005", "SRC-012", "SRC-003" ], "findings": [ { "id": "site-monitoring-and-observations", "name": "Site-scale monitoring and observations", "description": "Monitoring deployed at site rather than facility scale, following the SOSA observation pattern with explicit separation of the time a result applies to the feature of interest from the time the observing activity completed.", "source_refs": [ "SRC-005", "SRC-003" ], "questions": [ { "id": "q-monitored-properties", "text": "Which observable properties of the site are monitored, on which features of interest, and by which sensors or platforms?", "kind": "measurement", "answer_data": [ "Observable property", "Feature of interest reference", "Sensor and platform identifiers", "Deployment location", "Sampling interval" ] }, { "id": "q-observation-times", "text": "For each observation, what is the phenomenon time and what is the result time, and how is the difference handled?", "kind": "temporal", "answer_data": [ "Phenomenon time (RFC 3339)", "Result time (RFC 3339)", "Latency where material", "Time zone or offset handling", "Clock source" ] }, { "id": "q-monitoring-obligation", "text": "Which monitoring is mandated by an authorisation or standard rather than chosen by the operator?", "kind": "requirement", "answer_data": [ "Obligation source reference", "Mandated parameters", "Required frequency and method", "Reporting recipient and deadline" ] }, { "id": "q-sensor-data-quality", "text": "How is the quality of site monitoring data established, including calibration, drift and gap handling?", "kind": "quality", "answer_data": [ "Calibration date and certificate reference", "Stated uncertainty", "Drift correction applied", "Gap-filling method", "Validation status of each series" ] } ], "data_elements": [ { "id": "monitoring-platform", "name": "Monitoring platform", "description": "A platform hosting sensors at site scale, with location and hosted sensor references.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "observable-property", "name": "Observable property", "description": "A property of a site feature of interest that is observed.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "observation-phenomenon-time", "name": "Observation phenomenon time", "description": "RFC 3339 time to which the observation result applies for the feature of interest.", "value_kind": "timestamp", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "observation-result-time", "name": "Observation result time", "description": "RFC 3339 time at which the observing activity was completed, recorded separately from phenomenon time.", "value_kind": "timestamp", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "observation-result", "name": "Observation result", "description": "The value produced by an observation, with unit and stated uncertainty.", "value_kind": "quantity", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005" ] } ], "artifacts": [ { "id": "monitoring-plan", "name": "Site monitoring plan", "description": "Plan describing monitored properties, platform and sensor deployment, sampling regimes, obligations and quality procedures.", "media_or_form": [ "plan document", "structured configuration record" ], "serial": true, "identity_strategy": "Site identifier plus monitoring plan version and effective date.", "source_refs": [ "SRC-005", "SRC-003" ] }, { "id": "observation-series", "name": "Site observation series", "description": "Time series of observations with phenomenon time, result time, result, unit, sensor reference and validation status.", "media_or_form": [ "time-series dataset", "observation stream" ], "serial": true, "identity_strategy": "Sensor identifier plus observable property and RFC 3339 phenomenon time; series versioned on reprocessing.", "source_refs": [ "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "site-records-evidence-and-provenance", "name": "Site records, evidence, provenance and retention", "description": "The information containers that evidence assertions about the site, how their provenance and currency are established, and how long each must be kept before disposal.", "source_refs": [ "SRC-012", "SRC-007", "SRC-003" ], "questions": [ { "id": "q-evidence-for-assertions", "text": "Which record evidences each material assertion about the site, and what is that record's status and suitability?", "kind": "evidence", "answer_data": [ "Assertion identifier", "Evidencing information container reference", "Revision and suitability code", "Issue date", "Issuing party" ] }, { "id": "q-provenance-chain", "text": "For each record, who produced it, from what inputs, by what method, and who approved it?", "kind": "provenance", "answer_data": [ "Producing party", "Input sources", "Method or procedure", "Approving role", "Approval timestamp" ] }, { "id": "q-currency-and-supersession", "text": "How is a record known to be current, and how are superseded versions marked and retained?", "kind": "validation", "answer_data": [ "Currency check rule", "Review period", "Superseded flag and successor reference", "Retention of superseded versions", "Last verification date" ] }, { "id": "q-retention-and-disposal", "text": "What retention period applies to each record class, on what legal basis, and what is the approved disposal action?", "kind": "retention", "answer_data": [ "Record class", "Retention period and trigger", "Legal or contractual basis", "Disposal action", "Disposal authorisation role" ] }, { "id": "q-common-data-environment", "text": "Which common data environment is the agreed source of information for this site, and how is access to it controlled?", "kind": "access", "answer_data": [ "Environment identifier and location", "Container naming and status conventions", "Access roles and permissions", "Audit trail arrangements" ] } ], "data_elements": [ { "id": "information-container-reference", "name": "Information container reference", "description": "Reference to a named, versioned information container evidencing site information.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "container-suitability-status", "name": "Container suitability status", "description": "Coded status indicating the permitted use of a record revision.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "record-provenance", "name": "Record provenance", "description": "Producing party, inputs, method and approval for a record.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "retention-period", "name": "Retention period", "description": "Declared retention duration for a record class, with its trigger.", "value_kind": "duration", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "disposal-authorisation", "name": "Disposal authorisation", "description": "Record of authorised disposal including approving role and disposal timestamp.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "site-information-register", "name": "Site information register", "description": "Register of all site information containers with status, revision, provenance, sensitivity, retention period and disposal position.", "media_or_form": [ "register", "structured dataset" ], "serial": true, "identity_strategy": "Site identifier plus register version; entries keyed by information container identifier and revision.", "source_refs": [ "SRC-012", "SRC-007" ] }, { "id": "retention-and-disposal-schedule", "name": "Retention and disposal schedule", "description": "Approved schedule mapping record classes to retention periods, legal basis, disposal actions and authorising roles.", "media_or_form": [ "approved schedule", "structured record" ], "serial": true, "identity_strategy": "Organisation-level schedule reference plus version and effective date, scoped to the site identifier.", "source_refs": [ "SRC-007", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "interoperability-and-reconciliation", "name": "Interoperability and reconciliation", "description": "How the site record maps to external schemas and operational systems, and how competing records of the same site are reconciled.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008", "SRC-004" ], "findings": [ { "id": "standards-alignment-and-system-crosswalks", "name": "Standards alignment, crosswalks and record reconciliation", "description": "Declared alignments to external schemas, the information lost or distorted in each mapping, the rules for matching this site to records in other systems, and the evidence required before any conformance claim is made.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008" ], "questions": [ { "id": "q-alignment-targets", "text": "To which external schemas is this site record aligned, at which version, and is the alignment full or partial?", "kind": "interoperability", "answer_data": [ "Target schema name and version", "Aligned elements", "Full or partial alignment", "Alignment author and date", "Alignment artifact reference" ] }, { "id": "q-mapping-loss", "text": "What information is lost, generalised or forced in each mapping, and what compensating record is kept?", "kind": "quality", "answer_data": [ "Lossy element", "Nature of loss", "Compensating local element", "Impact assessment", "Reviewer" ] }, { "id": "q-matching-rules", "text": "By what rules is this site matched to a candidate record in an external system, and what confidence does a match carry?", "kind": "validation", "answer_data": [ "Matching attributes and weights", "Match threshold", "Confidence score", "Manual review requirement", "Reconciliation timestamp" ] }, { "id": "q-conformance-evidence", "text": "What evidence supports any claim of conformance to an external standard, and where a claim cannot be evidenced how is it recorded?", "kind": "evidence", "answer_data": [ "Standard and clause claimed", "Test or certification evidence reference", "Certifying body", "Validity period", "Explicit statement where only alignment, not conformance, is claimed" ] }, { "id": "q-deprecated-elements", "text": "Which elements of an aligned schema are deprecated, and how are they handled in exchange?", "kind": "constraint", "answer_data": [ "Deprecated element name", "Deprecating version", "Replacement element or model", "Handling rule on import and export" ] } ], "data_elements": [ { "id": "alignment-declaration", "name": "Alignment declaration", "description": "A declared mapping between this model and a named external schema at a specific version.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "mapping-loss-note", "name": "Mapping loss note", "description": "Recorded description of information lost or generalised in a specific mapping.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "match-confidence", "name": "Match confidence", "description": "Confidence assigned to a match between this site and an external record.", "value_kind": "number", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "conformance-claim", "name": "Conformance claim", "description": "An explicit claim of conformance to a standard together with its supporting evidence reference.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "deprecated-element-handling", "name": "Deprecated element handling rule", "description": "Rule for handling an element deprecated by the aligned schema on import and export.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [ { "id": "crosswalk-specification", "name": "Crosswalk specification", "description": "Element-level mapping between this model and each aligned external schema, with cardinality, transformation rules and loss notes.", "media_or_form": [ "mapping specification", "structured mapping table" ], "serial": true, "identity_strategy": "Source model identifier plus target schema name and version plus crosswalk version.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "reconciliation-report", "name": "Record reconciliation report", "description": "Periodic report of matches, non-matches and unresolved conflicts between this site record and external system records.", "media_or_form": [ "report", "structured dataset" ], "serial": true, "identity_strategy": "Site identifier plus target system name and RFC 3339 reconciliation run timestamp.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-site", "name": "Register a site", "description": "Create a governed site record and assign its canonical identifier under the identity priority rule.", "inputs": [ "Proposed site name and classification", "Candidate authoritative identifiers from master systems", "Draft managed extent statement", "Owning and operating party references" ], "outputs": [ "Site record with primary identifier", "Identifier assignment timestamp in RFC 3339", "Initial lifecycle state" ], "preconditions": [ "A search for existing site records has been run and no duplicate confirmed", "At least one owning or operating party reference resolves", "The managed extent statement has an authoring role" ], "effects": [ "Site identifier reserved and marked active", "Registration event appended to the site change log", "Site becomes eligible for containment, authorisation and reporting links" ], "source_refs": [ "SRC-003", "SRC-009" ] }, { "id": "define-site-boundary", "name": "Define or revise the site boundary", "description": "Record boundary geometry with a declared coordinate reference system, vertical datum, positional accuracy and survey provenance.", "inputs": [ "Boundary geometry", "Coordinate reference system identifier", "Vertical datum identifier", "Survey provenance and accuracy statement" ], "outputs": [ "Versioned boundary geometry record", "Site reference point and reference elevation", "Divergence notes against parcel lines" ], "preconditions": [ "Site record exists and is not in a closed state", "Coordinate reference system and vertical datum are both declared", "Survey provenance identifies the surveying organisation and date" ], "effects": [ "Previous boundary version superseded and retained", "Derived areas flagged for recalculation", "Downstream zone and route geometries flagged for revalidation" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "attach-facility-to-site", "name": "Attach or detach a facility", "description": "Create or end a containment edge between the site and a facility record in WM-BLT-006, with relationship type and effective period.", "inputs": [ "Facility identifier", "Relationship type and exclusivity", "Effective from timestamp", "Handover boundary statement" ], "outputs": [ "Containment edge with effective period", "Updated site facility register" ], "preconditions": [ "Facility identifier resolves in the facility model", "Facility geometry lies within or is justified against the managed extent", "No conflicting exclusive containment exists elsewhere" ], "effects": [ "Facility appears in site composition views", "Reporting boundary recalculation triggered", "Change appended to the site change log with event and record times" ], "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "transition-site-state", "name": "Transition site lifecycle state", "description": "Move the site to a new state in the controlled vocabulary with authorisation, evidence and separately recorded effective and record times.", "inputs": [ "Target state", "Authorising role", "Evidence artifact references", "Effective timestamp" ], "outputs": [ "Updated current state", "State transition approval record", "Change log entry" ], "preconditions": [ "Target state is reachable from the current state", "Required evidence artifacts exist and are current", "Authorising role holds the delegated authority" ], "effects": [ "Prior state retained as history", "Downstream obligations such as monitoring and reporting re-evaluated", "Notifications raised to regulatory registry holders where required" ], "source_refs": [ "SRC-009", "SRC-012" ] }, { "id": "split-or-merge-site", "name": "Split, merge or transfer part of a site", "description": "Reorganise site records while preserving predecessor and successor lineage and reassigning contained facilities, authorisations and reporting boundaries.", "inputs": [ "Event type", "Affected extent geometry", "Target site identifiers", "Effective timestamp" ], "outputs": [ "New or amended site records", "Predecessor and successor identifier links", "Reassignment schedule for facilities and authorisations" ], "preconditions": [ "Boundary geometry for every resulting site is defined", "Every contained facility and authorisation has a declared destination", "Change is authorised under the extent authority rule" ], "effects": [ "Superseded site identifiers retired but never reassigned", "Reporting boundaries restated with an explicit restatement note", "Crosswalks to external registries flagged for reconciliation" ], "source_refs": [ "SRC-004", "SRC-003", "SRC-011" ] }, { "id": "reconcile-external-site-identifiers", "name": "Reconcile external site identifiers", "description": "Match the site against candidate records in external registries and operational systems and record match confidence and unresolved conflicts.", "inputs": [ "Candidate external records", "Matching attributes and weights", "Match threshold" ], "outputs": [ "Updated identifier crosswalk", "Match confidence per pairing", "Reconciliation report with unresolved conflicts" ], "preconditions": [ "Site has a primary identifier and boundary geometry or reference point", "Target system snapshot has a stated extraction timestamp" ], "effects": [ "Crosswalk table updated with reconciliation timestamp", "Below-threshold matches queued for manual review", "Extent misalignments recorded against registry interests" ], "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "authorise-physical-access", "name": "Grant or revoke physical site access", "description": "Issue, amend or revoke a physical access authorisation scoped to the site or a security zone, and enforce it at designated entry and exit points.", "inputs": [ "Holder reference", "Requested scope and zones", "Authorisation basis and validity period", "Induction and competence evidence" ], "outputs": [ "Access authorisation record", "Issued credential reference", "Access list update" ], "preconditions": [ "Requested zones exist in the current zoning plan", "Induction and competence evidence is valid at the effective date", "Authorising role is designated for the requested zones" ], "effects": [ "Enforcement updated at designated entry and exit points", "Access events logged against the authorisation", "Revocation triggers device inventory and combination change checks" ], "source_refs": [ "SRC-007" ] }, { "id": "record-site-observation", "name": "Record a site observation", "description": "Ingest an observation against a site feature of interest with its phenomenon time and result time held separately.", "inputs": [ "Sensor and platform references", "Feature of interest reference", "Observable property", "Result value and unit", "Phenomenon time and result time" ], "outputs": [ "Observation record appended to the relevant series", "Validation status" ], "preconditions": [ "Sensor is registered in the monitoring plan", "Both phenomenon time and result time are supplied in RFC 3339 with offset or Z", "Calibration record for the sensor is current" ], "effects": [ "Series statistics and gap tracking updated", "Threshold breaches raised as events", "Regulatory monitoring obligations progressed" ], "source_refs": [ "SRC-005", "SRC-003" ] }, { "id": "compile-reporting-boundary", "name": "Compile a reporting boundary and return", "description": "Assemble a scheme-specific reporting boundary from parent and child properties, meter coverage and allocation rules, and produce the reportable dataset.", "inputs": [ "Reporting scheme and period", "Parent and child property references", "Meter readings and estimation flags", "Consolidation approach" ], "outputs": [ "Reporting boundary statement", "Consumption and emissions dataset", "Completeness and estimation summary" ], "preconditions": [ "Every facility in the boundary has a declared inclusion decision", "Campus-serving meters are recorded at the parent level", "Consolidation approach is declared and unchanged within the period or the change is disclosed" ], "effects": [ "Reportable dataset versioned and locked for the period", "Restatements recorded against prior periods where methods changed", "Divergence from managed extent explicitly stated" ], "source_refs": [ "SRC-011", "SRC-013" ] }, { "id": "validate-site-record", "name": "Validate a site record", "description": "Run structural, referential and temporal validation over the site record and report defects against declared rules.", "inputs": [ "Site record", "Validation rule set and version", "Referenced model snapshots" ], "outputs": [ "Validation result with defect list", "Severity classification", "Validation timestamp" ], "preconditions": [ "Validation rule set version is declared", "Referenced sibling models are reachable or their unavailability is recorded" ], "effects": [ "Defects raised for remediation with owners", "Records failing mandatory rules blocked from publication", "Validation history retained as evidence" ], "source_refs": [ "SRC-012", "SRC-004" ] }, { "id": "close-and-dispose-site-record", "name": "Close a site and apply retention", "description": "Move a site to a closed state and apply the retention and disposal schedule to its records, retaining what regulation requires.", "inputs": [ "Closure justification and authorisation", "Retention and disposal schedule", "Outstanding regulatory obligations" ], "outputs": [ "Closed site record with closure timestamp", "Disposal actions applied or scheduled", "Residual retained record set" ], "preconditions": [ "No active authorisation requires an operating site", "Contamination and remediation position is recorded", "Successor responsibility for retained obligations is assigned" ], "effects": [ "Site identifier retired and never reassigned", "Records outside retention disposed under authorisation", "Retained records marked with their retention expiry" ], "source_refs": [ "SRC-003", "SRC-007", "SRC-009" ] }, { "id": "assign-party-roles", "name": "Assign party roles", "description": "Record owner, operator, occupier and LADM RRR, and optionally transfer AIM on ownership change.", "inputs": [ "party identifiers", "role types", "title or appointment instruments" ], "outputs": [ "updated party-RRR graph", "optional AIM handover record" ], "preconditions": [ "Parties are identified in a party register", "Instruments exist for ownership claims" ], "effects": [ "Ownership and operatorship are current", "ISO 19650-3 continuity obligation is either fulfilled or recorded as a gap" ], "source_refs": [ "SRC-021", "SRC-022", "SRC-014" ] }, { "id": "bind-cadastral-units", "name": "Bind cadastral units", "description": "Associate LandID, LandTitleID, INSPIRE locators or LADM spatial units and optional SpatialUnitGroup without collapsing legal parcels.", "inputs": [ "site identifier", "parcel and title identifiers", "optional SpatialUnitGroup criterion" ], "outputs": [ "cadastral binding", "optional SpatialUnitGroup identifier" ], "preconditions": [ "Statutory identifiers are well-formed for the jurisdiction", "Informal units are explicitly flagged" ], "effects": [ "Legal substrate is referenced", "Operational geometry remains independent" ], "source_refs": [ "SRC-024", "SRC-018", "SRC-021" ] }, { "id": "compose-site-structure", "name": "Compose site structure", "description": "Set COMPLEX/ELEMENT/PARTIAL composition and parent/child site relations, including disconnected members of a campus complex.", "inputs": [ "composition type", "parent and child site identifiers", "contiguity flag" ], "outputs": [ "updated spatial structure graph" ], "preconditions": [ "Referenced sites exist", "Composition types respect IFC COMPLEX/ELEMENT/PARTIAL stacking" ], "effects": [ "Aggregation edges are written", "Campus aggregation mode is recorded" ], "source_refs": [ "SRC-015", "SRC-022" ] }, { "id": "record-environmental-status", "name": "Record environmental status", "description": "Attach a contamination or statutory-facility overlay, affected geometry and responsible parties.", "inputs": [ "status code", "regulatory identifiers", "affected geometry", "party identifiers" ], "outputs": [ "environmental overlay", "assessment artifact reference" ], "preconditions": [ "Overlay is not used to replace site or facility class" ], "effects": [ "CERCLA/RCRA or equivalent overlay is queryable", "Occupancy and transfer constraints are visible" ], "source_refs": [ "SRC-020" ] } ], "composition": [ { "target": "WM-PLC-002 Place", "relation": "CHILD", "purpose": "Site / Campus specialises the generic place concept, inheriting spatial referencing and naming semantics while adding managed-container behaviour.", "required": true, "source_refs": [ "SRC-008" ] }, { "target": "WM-PLC-005 Settlement", "relation": "REFERENCE", "purpose": "Records the settlement or populated place that spatially contains the site, as an evidenced relationship rather than a derived truth, since a site may straddle or fall outside settlement boundaries.", "required": false, "source_refs": [ "SRC-008", "SRC-004" ] }, { "target": "WM-BLT-006 Facility", "relation": "COMPOSE", "purpose": "The site aggregates facility records; IFC 4.3 confirms a facility may be aggregated by a site and that facility-internal structure belongs to the facility.", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "Land administration / property right sibling model (LADM-aligned)", "relation": "REFERENCE", "purpose": "Supplies parcels, basic administrative units, parties and rights, responsibilities and restrictions that the site references but must not re-model.", "required": true, "source_refs": [ "SRC-010", "SRC-004" ] }, { "target": "Organisation and party sibling model", "relation": "REFERENCE", "purpose": "Resolves owner, operator, duty holder, service provider and regulator references; site identity must never be conflated with the operating legal entity.", "required": true, "source_refs": [ "SRC-009", "SRC-010" ] }, { "target": "Address and geocoding sibling model", "relation": "REFERENCE", "purpose": "Supplies typed addresses for postal, delivery, emergency and registered purposes; IFC deprecated the site-embedded address attribute, reinforcing external ownership of addressing.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "Authorisation, permit and licence sibling model", "relation": "REFERENCE", "purpose": "Holds permits, licences and consents as legal instruments; the site records only which authorisations apply, their validity and their operational conditions.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "Asset register and maintenance sibling model", "relation": "REFERENCE", "purpose": "Holds individual plant and equipment items and their work history; the site provides the location and management context under ISO 55001 rather than the asset records themselves.", "required": false, "source_refs": [ "SRC-009" ] }, { "target": "Utility network sibling model", "relation": "REFERENCE", "purpose": "Owns external network topology and operations; the site records only on-site distribution and the demarcation point where responsibility transfers.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "Observation and sensing mix-in (SOSA/SSN pattern)", "relation": "MIX-IN", "purpose": "Supplies Platform, Sensor, Observation, FeatureOfInterest and the normative separation of phenomenon time from result time, reused rather than redefined by this model.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "Lifecycle state and versioning mix-in", "relation": "MIX-IN", "purpose": "Supplies the versioned-object pattern with beginLifespanVersion and endLifespanVersion alongside real-world validFrom and validTo, keeping event time and record time distinct.", "required": true, "source_refs": [ "SRC-004", "SRC-010" ] }, { "target": "IFC 4.3 (ISO 16739-1) IfcSite and IfcFacility", "relation": "ALIGN", "purpose": "Alignment target for spatial structure, composition type and site reference geometry. Alignment only: LandTitleNumber and SiteAddress are deprecated in IFC 4.3 and are not carried forward.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "OGC CityGML 3.0 Conceptual Model (OGC 20-010)", "relation": "ALIGN", "purpose": "Alignment target for encoding-independent geospatial representation, city object grouping, land use and relief at site scale.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "INSPIRE Cadastral Parcels (D2.8.I.6 v3.1.1)", "relation": "ALIGN", "purpose": "Alignment target for parcel referencing and lifespan versioning attributes when operating in the European regulatory context.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "ISO 55001:2024 asset management system", "relation": "ALIGN", "purpose": "Alignment target for management-system scope, accountability, life-cycle planning and control of change applied to the site as a managed object.", "required": false, "source_refs": [ "SRC-009" ] }, { "target": "ISO 19650 information management framework", "relation": "ALIGN", "purpose": "Alignment target for information containers, suitability status, the common data environment as agreed source of information, and the trigger-event update pattern.", "required": false, "source_refs": [ "SRC-012" ] }, { "target": "GHG Protocol Corporate Standard boundary rules", "relation": "ALIGN", "purpose": "Alignment target for organizational and operational boundary setting when a site emissions inventory is compiled.", "required": false, "source_refs": [ "SRC-013" ] }, { "target": "EPA Facility Registry Service", "relation": "ALIGN", "purpose": "Alignment target for regulatory site identification and crosswalk reconciliation in the United States context; the FRS Registry ID is a master-system identifier candidate, not a global site identifier.", "required": false, "source_refs": [ "SRC-003" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "The adopting Dimension must name a single accountable owner for the site model package and a named deputy, consistent with ISO 55001 assignment of responsibility and authority.", "The package must declare its scope boundary against WM-BLT-006, WM-PLC-005 and the land administration sibling model, and must not redefine elements owned by those models.", "The package must publish its identifier policy, stating the master systems it recognises, its governed global identifier schemes and its fallback UUID or ULID generator.", "The package must declare a validation rule set version and the common data environment that acts as the agreed source of information for site records.", "The package must maintain a register of alignments and conformance claims, distinguishing evidenced conformance from declared alignment." ], "namespace_guidance": "Use one stable namespace per adopting Dimension, with a path segment for the model (site) and never a path segment for storage format or interface. Identifiers minted by the Dimension are opaque and are never derived from names, addresses, coordinates or dates. External identifiers are carried in a namespaced crosswalk, never merged into the local identifier space. Namespace changes require a redirect and a recorded supersession, since retired site identifiers are never reassigned.", "registry_links": [ "vr.wm-blt-008 (this model) in the world-model record plane", "WM-BLT-006 Facility as the contained-model registry entry", "WM-PLC-002 Place and WM-PLC-005 Settlement as parent and containing registry entries", "External registry references recorded per instance: national cadastral register, EPA Facility Registry Service, and any benchmarking scheme property registry" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonical form is the format-neutral logical record; JSON, YAML, Markdown, HTML, IFC, CityGML, Git objects and MongoDB documents are projections and never authoritative.", "All timestamps are canonicalised to RFC 3339 with seconds and an explicit offset or Z; local wall-clock times without offset are rejected at ingest.", "Geometry is canonicalised to a single declared coordinate reference system per record, with the CRS identifier stored alongside; reprojected copies are derived artifacts.", "Collections are ordered deterministically by identifier for hashing; ordering carries no semantics unless a rank attribute is present.", "Absent values are represented as absent, never as empty strings, zero or a sentinel date; a value that is deliberately withheld is marked withheld with a reason." ], "patch_rules": [ "Every change is expressed as an addressed patch against a specific record version, carrying both the event time and the record time.", "Identifier fields are immutable; a correction to a primary identifier is a supersession event with predecessor and successor links, not an in-place edit.", "Boundary geometry, lifecycle state and accountability changes require an authorising role reference on the patch and are rejected without one.", "Patches to reported quantities within a closed reporting period are recorded as restatements with an explicit reason, not as silent overwrites.", "Patches are append-only in the change log; the log is never rewritten, and rollbacks are expressed as compensating patches." ], "compatibility_rules": [ "Adding an optional element or a new coded value is a minor change; removing an element, tightening cardinality or narrowing a code list is a breaking change.", "Deprecated elements are retained and marked with their deprecating version and replacement, following the IFC precedent for LandTitleNumber and SiteAddress.", "Consumers must ignore unknown elements rather than fail, and must not infer meaning from element ordering.", "A crosswalk is versioned against both the source model version and the target schema version; a target schema upgrade invalidates the crosswalk until re-verified.", "No conformance to an external standard is claimed without a cited test or certification artifact; otherwise the relationship is recorded as alignment only." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier issued by the system of record for the site, for example an EPA FRS Registry ID or a national cadastral reference held by the responsible authority.", "Governed global identifier or IRI from a maintained scheme, for example an INSPIRE external object identifier or an IFC GlobalId, where a persistence and non-reallocation policy exists.", "UUID or ULID minted by the adopting Dimension, used only where no higher-priority identifier exists and recorded with the justification for its use.", "A date, a name, an address, a coordinate pair or a file path is never an identifier and must not be used as a key." ], "timestamp_rule": "All time values are recorded in RFC 3339 format with seconds precision and an explicit UTC offset or Z. Event time (when the thing happened in the world) and observation or ingestion time (when the system learned of it) are recorded as separate fields wherever they can differ, following the SOSA separation of phenomenon time from result time. Date-only values are used solely where the source itself is date-only and are labelled as such.", "serial_naming_rule": "Serial artifacts are named as ///, where sequence is monotonically increasing within the site and revision is issued by the producing party. Reporting artifacts substitute the RFC 3339 period start and end for sequence. Sequence numbers are never reused after retirement, and gaps are permitted and explained rather than backfilled.", "integrity_rule": "Every artifact carries a content digest over its canonical form, the producing party, the approving role and the approval timestamp. Superseded revisions are retained with a link to their successor and are never deleted before the retention period expires. Redacted derivatives carry a reference to their parent digest and the identifier of the redaction profile applied, so that any published extract can be traced to a controlled original." }, "policies": [ "Boundaries and containment are recorded as authored, evidenced decisions with an authorising role, never inferred from geometry alone; a facility whose footprint falls inside the boundary is not thereby part of the site.", "Legal, regulatory and commercial constructs are referenced by identifier and never re-modelled inside the site record; the site model holds applicability, validity and operational consequence only.", "No conformance to an external standard is asserted without cited evidence; unevidenced relationships are recorded as alignments and any conflict between standards is recorded rather than resolved silently.", "Security-sensitive site information is classified before publication, and any externally shared derivative is produced through an approved redaction profile traceable to its controlled original.", "Reporting boundaries are maintained as dated views over the site and are never allowed to overwrite or redefine the managed extent.", "Physical site records default to operator-controlled access; cadastral extracts follow the originating jurisdiction's disclosure law.", "Security-minded redaction of gates, utilities and occupancy applies to sensitive campuses before any public city-model publication.", "Temporary construction and contamination overlays expire or close by explicit state change; they are never deleted silently while legal obligations remain.", "Ownership transfer must attempt AIM continuity per ISO 19650-3; failure is recorded as a governed gap, not ignored." ], "crud": { "read": [ "Read of non-sensitive site identity, classification, boundary and composition is available to any authenticated agent within the adopting Dimension.", "Read of security-sensitive elements including perimeter detail, access authorisations, access logs and buried-service records requires an explicit named grant and is logged.", "Read of a superseded revision requires the same or stronger grant as the current revision and returns the supersession link.", "Bulk read and export require a declared purpose, and any export crossing a Dimension boundary is produced through an approved redaction profile." ], "create": [ "Site records are created only through the register-site function, which enforces the identity priority rule and a duplicate check.", "Containment edges to facilities are created only where the facility identifier resolves and no conflicting exclusive containment exists.", "Observations are created only for sensors registered in the current monitoring plan and only with both phenomenon time and result time supplied.", "Artifacts are created with a content digest, producing party and approval record; artifacts without provenance are rejected." ], "update": [ "Identifier fields are immutable; changes are expressed as supersession with predecessor and successor links.", "Boundary, lifecycle state, accountability and extent changes require an authorising role and supporting evidence artifacts.", "Updates carry both event time and record time; an update supplying only one of the two is rejected where they can differ.", "Updates within a closed reporting period are recorded as restatements with a stated reason and do not overwrite the locked period dataset." ], "delete": [ "Logical deletion only: records are retired or superseded, never physically removed while within their retention period.", "Physical disposal occurs only under the approved retention and disposal schedule, with a recorded disposal authorisation, action and timestamp.", "Retired site identifiers are permanently reserved and are never reassigned to a different site.", "Deletion is blocked while any active authorisation, unresolved regulatory obligation or open legal hold references the record." ] }, "roles": [ { "name": "Site model owner", "responsibilities": [ "Owns the model package, its scope boundary and its versioning", "Approves breaking changes and deprecations", "Maintains the register of alignments and conformance claims" ] }, { "name": "Site data steward", "responsibilities": [ "Maintains identifier assignment, crosswalks and reconciliation against external registries", "Adjudicates below-threshold matches and records unresolved conflicts", "Monitors completeness and currency of site records" ] }, { "name": "Site operator or facility manager", "responsibilities": [ "Maintains managed extent, containment, zoning, operating model and service arrangements", "Authorises physical access within delegated limits", "Ensures emergency and permit-to-work arrangements are current" ] }, { "name": "Geospatial and survey authority", "responsibilities": [ "Approves boundary geometry, coordinate reference system and vertical datum declarations", "Certifies positional accuracy and survey provenance", "Validates divergence between the operational boundary and legal parcel lines" ] }, { "name": "Compliance and reporting officer", "responsibilities": [ "Maintains the authorisation register and regulatory registry interests", "Defines and locks reporting boundaries and consolidation approaches", "Owns restatements, assurance evidence and submission records" ] }, { "name": "Security and information classification authority", "responsibilities": [ "Classifies site information by sensitivity and approves redaction profiles", "Governs access grants to security-sensitive elements and audits their use", "Adjudicates conflicts between disclosure obligations and security restrictions" ] } ], "access": { "default_rule": "Deny by default. Access is granted per scope to a named role for a stated purpose and a bounded period; grants at bundle scope do not cascade automatically to security-classified findings or artifacts within them.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency response override: designated emergency roles and external responders receive immediate read of emergency, hazard, muster and circulation findings during a declared incident, with the override logged and reviewed afterwards.", "Mandatory disclosure: information subject to a statutory publication or access-on-request obligation is released through the approved channel even where the operator would prefer to withhold it, with any permitted exemption recorded.", "Regulator access: an authority holding a registry interest in the site receives read of the findings within its remit without a per-request grant, scoped to that remit.", "Security withholding: perimeter detail, access authorisations, access logs, buried-service records and security-zone geometry are withheld from general and bulk read even where the containing bundle is otherwise readable.", "Legal hold: records under legal hold are readable to the holding authority and are exempt from scheduled disposal until the hold is lifted.", "Emergency responders may read access-regime, gate and affected-geometry under recorded emergency-access exceptions.", "Statutory cadastral publication may disclose parcel geometry even when campus security policy would redact operational fences.", "Temporary construction wage-law envelopes may be disclosed to labour authorities without granting full AIM access." ], "audit_requirements": [ "Every read of a security-classified finding or artifact is logged with actor, scope, purpose, RFC 3339 timestamp and grant reference.", "Every write is logged with actor, authorising role, event time, record time and the change log sequence number it produced.", "Every export crossing a Dimension boundary is logged with the redaction profile applied and the digest of both the parent and the derivative.", "Emergency overrides and mandatory-disclosure releases are reviewed within a defined period after the event and the review outcome is recorded.", "Audit logs are append-only, retained under the retention and disposal schedule, and are themselves subject to access control.", "Log create, update, delete, overlay and mapping changes with actor, event time and ingestion time.", "Log reads of security-sensitive geometry and environmental listings.", "Retain audit logs at least as long as the AIM archive obligation for the site." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Model ID and registry ID", "Version and effective date (RFC 3339)", "Owner and steward contact roles", "Scope boundary and explicit exclusions", "Identity policy and identifier priority", "Access default rule and classification scheme", "Alignment register and conformance-claim status", "Validation rule set version" ], "read_order": [ "AGENTS.md - establishes name, type and the four resolving URLs before any other action", "Specification URL - the format-neutral model semantics, scope, exclusions and boundary notes", "Storage type URL - how the current projection encodes the model, whether JSON, YAML, Markdown, Git, MongoDB or an IFC or CityGML exchange", "Interface URL - the available read and write operations, authentication and the access default rule", "Processes URL - the governed functions, their preconditions, authorising roles and effects", "Alignment and crosswalk register - target schema versions, mapping losses and any conflicts before attempting exchange", "Validation rule set - the rules a record must satisfy before publication" ] } }, "coverage": { "claim": "Covers identity, classification, managed extent, spatial basis and georeferencing, land basis with planning controls, composition, control and access, lifecycle including temporary construction overlays, hazards and emergency response, measurement and reporting boundary, evidence and interoperability for a managed site or campus. Bounded to the container: legal land units, facility internals, parties, permits-as-instruments and individual assets are referenced by identifier, never re-modelled. No claim of universal completeness across jurisdictions or site types; marine, subsurface and relocatable sites remain an open gap, and alignment to cited standards is declared, not conformance-evidenced.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Identity priority, master-system identifiers, governed global identifiers, UUID/ULID fallback, naming, retirement and non-reassignment are covered by the site-identity-and-designation finding and artifact_rules.identity_priority, grounded in EPA FRS (SRC-003), INSPIRE inspireId (SRC-004) and IFC GlobalId semantics (SRC-001)." }, { "dimension": "lifecycle", "status": "covered", "notes": "State vocabulary, transition authority and evidence, split/merge lineage and trigger events are covered, grounded in ISO 55001 control of change (SRC-009) and ISO 19650 trigger events (SRC-012). The specific state vocabulary itself is an adopter decision and is marked as such rather than asserted." }, { "dimension": "relationships", "status": "covered", "notes": "Containment to facilities, reference to settlement and place, parcel coverage, adjacency, connection points and third-party enclaves are covered, grounded in IFC aggregation rules (SRC-001, SRC-002) and INSPIRE parcel locator semantics (SRC-004)." }, { "dimension": "temporal", "status": "covered", "notes": "RFC 3339 with explicit offset or Z is mandated; event time and record time are held separately, reinforced by the SOSA phenomenonTime/resultTime distinction (SRC-005) and INSPIRE validFrom/beginLifespanVersion pairing (SRC-004)." }, { "dimension": "provenance", "status": "covered", "notes": "Producing party, inputs, method, approval and content digest are required for artifacts; survey provenance and register verification dates are explicit. Grounded in ISO 19650 information containers (SRC-012) and EPA FRS source-system precedence (SRC-003)." }, { "dimension": "ownership", "status": "covered", "notes": "Owner, operator, duty holder and delegation are separated with effective dates, grounded in ISO 55001 (SRC-009) and the LADM party and basic-administrative-unit separation (SRC-010). Legal title itself is explicitly out of scope." }, { "dimension": "validation", "status": "covered", "notes": "A validate-site-record function, declared rule set versioning, match thresholds, conformance-evidence questions and publication blocking on mandatory-rule failure are all present (SRC-012, SRC-004, SRC-003)." }, { "dimension": "access", "status": "covered", "notes": "Deny-by-default with four scopes, five exception classes and five audit requirements, grounded in the NIST SP 800-53 PE control pattern (SRC-007) and the ISO 19650 common data environment (SRC-012)." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retention periods with triggers and legal basis, disposal authorisation, logical-only deletion, permanent identifier reservation and legal hold are covered (SRC-007, SRC-003, SRC-009). Specific statutory retention durations are jurisdiction-dependent and are deliberately not asserted." }, { "dimension": "interoperability", "status": "covered", "notes": "Alignment declarations, mapping-loss notes, matching rules, deprecated-element handling and an explicit alignment-not-conformance policy are covered against IFC (SRC-001, SRC-002), CityGML (SRC-008), INSPIRE (SRC-004), FRS (SRC-003), ISO 19650 (SRC-012) and GHG Protocol (SRC-013)." }, { "dimension": "classification", "status": "covered", "notes": "Scheme-versioned classification, multi-classification precedence, IFC composition type and reclassification triggers are covered (SRC-001, SRC-008, SRC-014). No single universal site typology is asserted, because none was found in the primary sources." }, { "dimension": "spatial extent", "status": "covered", "notes": "Boundary geometry, CRS, vertical datum, positional accuracy, reference point and vertical or subsurface extent are covered (SRC-001, SRC-004, SRC-008). Three-dimensional site volumes are supported conceptually but their encoding is left to the projection." }, { "dimension": "measurement", "status": "covered", "notes": "Areas, occupancy, capacity, meter coverage, allocation and consolidation approach are covered with mandatory measurement basis and date (SRC-011, SRC-013, SRC-004)." }, { "dimension": "security", "status": "covered", "notes": "Perimeter, access authorisation, logging, device inventory and information sensitivity are covered from NIST SP 800-53 PE controls (SRC-007), including the disclosure-versus-security conflict resolution path." }, { "dimension": "emergency and safety", "status": "covered", "notes": "Written plan requirement, evacuation and exit route assignment, employee accounting, alarm system and review triggers are taken directly from 29 CFR 1910.38 (SRC-006). This is US-specific and is flagged under regional assumptions." }, { "dimension": "cost and commercial", "status": "not-applicable", "notes": "Valuation, rent, service charge and capital planning belong to real-estate and finance sibling models. No primary source reviewed places commercial terms within a managed-site container model, so no structure is proposed here." }, { "dimension": "marine, subsurface and mobile sites", "status": "gap", "notes": "IFC 4.3 introduces IfcMarineFacility (SRC-002) and CityGML has WaterBody (SRC-008), but no primary source reviewed defines a managed-site container for offshore platforms, underground mines or relocatable sites. The vertical-extent and water-body elements are provided as a partial accommodation and this remains an unresolved boundary." } ], "known_omissions": [ "No governed global location identifier scheme is prescribed. GS1 GLN was investigated as a candidate but gs1.org returned HTTP 403 to every fetch attempt, so no GLN allocation rule is cited or relied upon anywhere in this model.", "Reference designation systems for construction works (the ISO/IEC 81346 series, including RDS-CW) would give a rigorous site-to-facility-to-system designation grammar, but the texts are paywalled and no free normative extract was obtainable, so no designation grammar is asserted.", "Buried-service record quality is modelled as a coded confidence level without binding it to a specific quality-level standard, because no freely readable normative source for subsurface utility record quality levels was verified in this session.", "Waste, water discharge and air emission permit content is referenced but not decomposed; the decomposition belongs to an authorisation sibling model that does not yet exist in the registry.", "Site-level accessibility requirements are limited to a question about designated accessible routes. No accessibility standard was cited as primary, so no requirement structure is proposed.", "Biodiversity net gain, ecological baseline and habitat accounting appear only as protected-feature constraints; they may warrant their own layer in jurisdictions where they are mandatory.", "The ENERGY STAR campus rules were read from the EPA landing page and EPA-published summaries; the guide PDF itself was not machine-readable in this session, so clause-level wording is not quoted.", "No primary international feature type named Campus; higher-education, hospital and data-centre campus information models were not adopted as canonical classes.", "Military installation and NATO/DoD site schemas were not retrieved as primary sources.", "OSHA establishment combining nearby locations was only partially retrieved because eCFR blocked a full fetch; workplace mapping is therefore thinner than access policy.", "Customary and informal tenure is acknowledged via LADM but not operationalised with a regional code list.", "3D/4D cadastral air rights and subsurface volumes lack a single implementable geometry profile in this model.", "Wet-infrastructure networks are out of LandInfra's initial release and remain out of this site model except as easements.", "Biodiversity, occupancy, valuation (LADM Part 4) and climate normals are sibling models.", "Seveso/IED, UK COMAH and other non-US contamination regimes are not cited as primary overlays.", "IFC Pset_SiteWeather exists but weather is treated as observation, not as a climate sibling, and was not expanded." ], "conflicts": [ "IFC 4.3 deprecates IfcSite.LandTitleNumber and IfcSite.SiteAddress (SRC-001), while many operational systems and earlier IFC exchanges still populate them. This model treats title and address as external references and records the deprecation as an explicit import and export handling rule rather than carrying the attributes forward.", "EPA Portfolio Manager supports only a two-level parent and child property structure with no nested campuses (SRC-011), whereas IFC permits recursive site decomposition through COMPLEX, ELEMENT and PARTIAL composition types (SRC-001). The model keeps physical composition recursive and treats the benchmarking structure as a separate, flatter reporting view.", "A regulatory facility site in EPA FRS is a reporting unit clustered from roughly ninety program systems (SRC-003) and frequently does not align one-to-one with a managed site. The model records extent alignment and match confidence rather than assuming identity between the two.", "GHG Protocol organizational boundaries set by equity share or control (SRC-013) can include facilities the site operator does not manage and exclude ones it does. The model therefore forbids a reporting boundary from redefining the managed extent.", "LADM treats the spatial unit as the carrier of rights and defines land administration around basic administrative units (SRC-010), whereas a managed site is defined by operational control. Where the two diverge the model records both, and does not attempt to reconcile them into a single boundary.", "OSHA 29 CFR 1910.38 (SRC-006) permits an oral emergency action plan for employers with ten or fewer employees, which conflicts with the general expectation elsewhere in this model that controlling arrangements exist as retained artifacts. The finding records the requirement basis explicitly rather than mandating a written artifact universally.", "IEC 62264/ISA-95 Site may be logical; ISO 6707-1 and IfcSite are physical land or water.", "CERCLA 'facility' includes 'any site or area'; ISO 41011 'facility' is a collection of assets; Vercy WM-BLT-006 is the latter.", "INSPIRE cadastral parcel (homogeneous unique ownership) often does not coincide with a multi-parcel or multi-owner campus.", "IfcSite.RefLatitude/RefLongitude/RefElevation are approximate WGS84; IfcMapConversion is authoritative and may disagree.", "IFC4.3 ADD2 deprecates LandTitleNumber and SiteAddress that remain in widespread IFC2x3/IFC4 data.", "29 CFR 5.2 site of the work can include off-campus secondary fabrication sites that are not part of the permanent holding.", "CityGML LandUse is land cover/use, not a managed operator holding; grouping via CityObjectGroup is not equivalent to IfcSite." ], "regional_assumptions": [ "The emergency preparedness finding is grounded in United States federal OSHA regulation (SRC-006). Other jurisdictions impose different minimum content, review cycles and written-plan thresholds; the finding structure is intended to be jurisdiction-neutral but its specific elements are US-derived.", "Regulatory site identification is grounded in the US EPA Facility Registry Service (SRC-003). Equivalent national registries exist elsewhere with different identifier structures, matching rules and authority models.", "Parcel referencing is grounded in the INSPIRE Cadastral Parcels specification (SRC-004), which applies to European Union member states. Cadastral systems elsewhere differ in identifier structure, area authority and whether parcel geometry is legally definitive at all.", "Campus benchmarking rules including the parent and child structure and the restricted list of campus-certifiable property types are US EPA ENERGY STAR rules (SRC-011) and do not generalise to other benchmarking schemes.", "The physical access control pattern follows NIST SP 800-53 (SRC-007), a US federal control catalogue. Organisations operating under ISO/IEC 27001 Annex A or sector-specific regimes will map to equivalent but differently structured controls.", "Coordinate reference systems, vertical datums and land-cover classifications are all jurisdiction-specific; the model requires that each be declared and never assumes a default.", "Cadastral identifier schemes, title versus deeds systems, and whether government land is registered, are jurisdiction-specific.", "INSPIRE ETRS89 practices apply in the EU; WGS84 approximate points are common in BIM and may be inappropriate for cadastral use.", "CERCLA/RCRA overlays are United States law; other jurisdictions need local contaminated-land instruments.", "Davis-Bacon site of the work is United States labour law; other public-works wage envelopes will differ.", "Campus as an English operational term is common in ISO 19650-3 examples but is not a translated statutory class.", "Common-law versus civil-law treatment of easements, superficie and condominium will change RRR cardinality." ], "adversarial_checks": [ "Counterexample sought for site-facility separation: IFC 4.3 permits a facility to be aggregated directly by IfcProject without an intervening site (SRC-002), so a site is not universally required. The model therefore treats containment of a facility by a site as a recorded relationship with its own evidence rather than a structural necessity, and does not require every facility to have a parent site.", "Counterexample sought for contiguity: EPA campus guidance and real portfolio practice both include discontiguous holdings managed as one unit. The managed-extent finding therefore makes contiguity an explicit recorded flag with a federation justification, rather than assuming a single connected polygon (SRC-011).", "Attractive but unsupported structure rejected: a universal site typology (industrial, campus, port, depot and so on) was drafted and then rejected, because no reviewed primary source publishes a governed cross-domain site classification. Classification is instead modelled as scheme-versioned assignments with a precedence rule, and the absence of a canonical scheme is recorded in the checklist.", "Attractive but unsupported structure rejected: a site-owned tenure and rights sub-model was drafted and removed. LADM (SRC-010) and INSPIRE (SRC-004) place rights, restrictions and responsibilities with the land administration domain, and IFC 4.3 deprecated its own land-title attribute (SRC-001). Duplicating it here would have created two competing sources of legal truth.", "Boundary stress test between site and reporting view: because both EPA Portfolio Manager (SRC-011) and GHG Protocol (SRC-013) produce site-shaped boundaries that diverge from physical management, a policy was added forbidding a reporting boundary from redefining the managed extent. Without it an agent would silently corrupt the site definition when compiling a return.", "Identity stress test: a date, a name, an address and a coordinate pair were each tested as identifier candidates and rejected. FRS demonstrates that names and addresses are exactly the attributes that fail to resolve duplicate site records across roughly ninety systems (SRC-003), which is why match confidence, not attribute equality, governs reconciliation.", "Sourcing stress test: four intended sources could not be read live in this session (gs1.org and iso.org return HTTP 403, ecfr.gov redirects off-host, and the ENERGY STAR campus PDF is not machine-readable). Every claim that would have depended on GS1 GLN was removed rather than asserted from memory; ISO catalogue entries are cited for title, edition and scope only, never for clause-level text; and OSHA's own hosted text was used in place of eCFR.", "A site can exist without a cadastral parcel (unregistered public land, water, informal occupation); requiring LandTitleID would falsely exclude those holdings.", "A campus can be non-contiguous (satellite teaching hospitals, split data-centre halls); forcing a single polygon would corrupt identity.", "A construction site of the work can exist with IsPermanentID=false and no land title; collapsing it into the permanent campus would break wage-law and safety records.", "A company town can be both settlement and site; storing it only as WM-BLT-008 would hide populated-place semantics.", "A logical ISA-95 site with no geometry must not satisfy canonical physical-site validation.", "Multiple operators on one parcel (business park, hospital-plus-university) require many operator roles, not duplicate parcel identities.", "Air-rights or subsurface campuses over railways would fail a 2D fence-line-only model.", "A CERCLA plume extending off-site must not enlarge the managed campus identity.", "Publishing full IfcSite geometry for a secure campus would violate ISO 19650-5 security-minded practice even if CityGML interoperability encourages it." ] }, "researchAdjudication": { "providerMode": "dual-provider", "activeProviders": [ "claude", "grok" ], "waivedProviders": [], "providerPolicy": {}, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "Base (claude) types WM-BLT-008 as an entity; grok types it as an aggregate. A site is a singular governed thing with its own identifier, lifecycle, duty holder, authorisations and record, and it can exist with a single facility or none at all, so aggregation is not constitutive. The COMPLEX / ELEMENT / PARTIAL composition that motivates grok's 'aggregate' reading is a recursive relationship between site instances plus a containment edge to WM-BLT-006, which the entity typing already carries. Typing the model as an aggregate would blur the boundary against the facility model and against reporting-boundary constructs that are also site-shaped collections. Entry kind accepted as entity; grok's composition semantics are absorbed as relationships and a composition function." }, "decisions": [ { "concept": "Base provider selection", "disposition": "claude adopted as base", "rationale": "Claude states seven neighbour boundaries with explicit distinctions and source refs, separates managed extent from reporting boundary, legal parcel, settlement, utility network and asset-management system, and applies a consistent reference-not-re-model rule. Grok's in-scope list pulls rights, restrictions, responsibilities and planning controls inside while declaring the land-administration object out of scope, which is a less crisp edge. Size was not the deciding factor." }, { "concept": "Entry kind entity versus aggregate", "disposition": "entity accepted", "rationale": "A site holds identity, lifecycle, duty holder and authorisations independent of what it contains, and can contain zero facilities. Composition is modelled as recursive site relationships plus containment edges, so aggregate typing would add no expressive power and would blur the WM-BLT-006 edge." }, { "concept": "Georeferencing and map conversion", "disposition": "accepted from grok into spatial-footprint", "rationale": "Base declares CRS and datum but omits the engineering-to-map conversion and the approximate-WGS84 caveat on IfcSite reference latitude and longitude, which is the dominant real-world georeferencing failure and is directly evidenced in IFC 4.3 and LandInfra." }, { "concept": "Planning and development controls", "disposition": "accepted from grok into land-basis-and-external-context", "rationale": "Buildable area, coverage ratio, floor-area ratio and height limit are wholly absent from the base yet are core constraints on a managed land holding, evidenced by Pset_SiteCommon; planning authority is also distinguished from land owner, which the base never does." }, { "concept": "Construction site of the work as a time-bounded overlay", "disposition": "accepted from grok into lifecycle-and-operations", "rationale": "The base only has a phase flag on parts of a permanent site. A labour-law or construction envelope can be larger or smaller than the permanent holding and must not be collapsed into it; grok evidences this from 29 CFR 5.2 and IsPermanentID." }, { "concept": "Cadastral SpatialUnitGroup, informal tenure and strata fragmentation", "disposition": "rejected as a finding, deferred to research", "rationale": "Grok's cadastral-and-land-division-alignment overlaps the base's parcel-and-tenure-linkage on its primary question, and the genuinely novel parts (LADM SpatialUnitGroup grouping, unregistered or customary occupation, condominium and air-right fragmentation) sit on the land-administration side of the base's stated boundary. Deferred rather than duplicated." }, { "concept": "ISA-95 / IEC 62264 role-based site", "disposition": "rejected as a finding", "rationale": "A logical enterprise site with no land holding is an alignment target, not a canonical instance of a physical container. The base's standards-alignment-and-system-crosswalks finding already carries alignment targets, mapping loss and matching confidence, and grok itself records no distinctive artifact for this node." }, { "concept": "CERCLA / RCRA statutory facility overlay", "disposition": "rejected as a finding, deferred as a terminology hazard", "rationale": "Grok's contamination finding overlaps the base's hazard-exposure finding on contamination status and remediation. Its distinctive value is the warning that a statutory 'facility' is an environmental-liability object that must not be merged into WM-BLT-006; that belongs in boundary guidance and deferred research, and the responsible-party operation is captured by the added record-environmental-status function." }, { "concept": "Grok identity and naming findings", "disposition": "rejected as duplicative", "rationale": "canonical-identifiers and names-and-postal-address restate the base's site-identity-and-designation (master identifier, governed global identifier, Dimension UUID, naming and retirement) and its address questions under external-context-and-connection-points. Land title identifiers remain referenced through the parcel linkage." }, { "concept": "Site versus campus typology finding", "disposition": "rejected as duplicative", "rationale": "Base already asks composition type (complex, site, section), scheme-versioned classification and contiguity with a federation justification. Campus is retained as an operational alias in the scope statement rather than as a competing spatial primitive, consistent with ISO 19650-3 naming campuses without defining a feature type." }, { "concept": "Reporting boundary and resource accounting", "disposition": "retained from base, unmatched by grok", "rationale": "The rule that an ENERGY STAR parent/child structure or a GHG Protocol organisational boundary may never redefine the managed extent is a load-bearing safeguard present only in the base; without it an agent would corrupt the site definition while compiling a return." }, { "concept": "Site-scale monitoring and observation semantics", "disposition": "retained from base, unmatched by grok", "rationale": "SOSA phenomenon-time versus result-time separation grounds the model's temporal discipline for observations and has no counterpart in grok, which treats weather and observation as out of scope." }, { "concept": "Emergency preparedness and response", "disposition": "retained from base with regional flag", "rationale": "Written plan, evacuation, muster, accounting, alarm and review triggers come from US OSHA 29 CFR 1910.38 and are the only emergency structure either provider produced; the jurisdictional narrowness is carried as a publication hold, not a reason to drop the layer." }, { "concept": "Grok quantity and interoperability functions", "disposition": "rejected as duplicative", "rationale": "compute-site-quantities and publish-interop-mapping are covered by the base's validate-site-record, compile-reporting-boundary and reconcile-external-site-identifiers; the planned-versus-measured area distinction is absorbed into the base's existing quantities finding rather than a new operation." }, { "concept": "Service layer merge", "disposition": "applied", "rationale": "Both providers place measurement, evidence and interoperability in a single terminal bundle with identical intent, so the service-layer structures are merged into the base's bundle rather than kept as parallel branches." } ], "publicationHolds": [ "Source and live-version verification is incomplete: the two providers cite IFC 4.3 from different hosts (ifc43-docs.standards.buildingsmart.org versus standards.buildingsmart.org) and different documentation builds, and grok-sourced Pset_SiteCommon, Pset_LandRegistration and IfcMapConversion claims must be re-fetched and pinned against the single host and version chosen for the base before merge.", "Paywalled and blocked sources remain unverified at clause level: ISO catalogue entries (55001, 19650-1, 19650-3, 19152-1, 19152-2, 41011, 6707-1), IEC 62264-1 and the ENERGY STAR campus guide PDF were cited for title, edition and scope only; no clause-level wording may be published as quotation or requirement.", "Multi-profile domain validation is not complete: the synthesised model must be exercised against at least three materially different site profiles (for example a university or hospital campus, a process or industrial site, and a port, data-centre or utility holding) before publication, since the evidence pack contains no instance-level validation.", "Jurisdictional profile verification is outstanding: emergency planning (29 CFR 1910.38), regulatory site identity (EPA FRS), benchmarking (ENERGY STAR), physical security (NIST SP 800-53), contaminated land (CERCLA/RCRA) and construction wage envelopes (29 CFR 5.2) are all United States instruments; at least one non-US jurisdiction cross-check is required before the model is presented as jurisdiction-neutral.", "No governed global location identifier scheme is asserted: GS1 GLN could not be fetched (HTTP 403) and ISO/IEC 81346 reference designation texts are paywalled, so any identifier-grammar claim must stay out of the published draft." ], "deferredResearch": [ "LADM SpatialUnitGroup binding for multi-parcel campuses, plus unregistered, customary and informal occupation, and condominium, strata and air-right fragmentation: decide whether the site model needs an explicit binding pattern or remains a reference to the land-administration sibling model.", "Terminology collision between the statutory CERCLA/RCRA 'facility' (any site or area where a hazardous substance has come to be located, or all contiguous land under common control) and the ISO 41011 facility used by WM-BLT-006: an explicit overlay rule is needed so environmental-liability objects are never merged into the facility model or allowed to enlarge the managed extent.", "IEC 62264 / ISA-95 role-based site alignment: confirm that a geometry-less logical enterprise site is an alignment target only and cannot satisfy canonical physical-site validation, and record where the enterprise hierarchy is authoritative for rough-cut planning.", "Marine, subsurface, offshore and relocatable managed holdings: neither provider located a primary source defining a managed-site container for these cases; the vertical-extent and water-body accommodations are partial and the boundary is unresolved.", "Non-US contaminated-land and major-hazard regimes (Seveso, IED, UK COMAH and equivalents) as overlays on the hazard and authorisation structure, to test whether the US-derived structure generalises.", "Site-level accessibility requirements and biodiversity or ecological baseline accounting: both appear only as single questions or constraints, with no primary standard cited by either provider." ] }, "statistics": { "sources": 27, "bundles": 6, "layers": 13, "findings": 27, "questions": 115, "artifacts": 40, "functions": 15 } }