{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-blt-008","code":"wm-blt-008-site-campus","url":"https://ver.cy/models/wm-blt-008-site-campus/","name":"Site / Campus","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"entity","plane":"","domain":["PHY.BLT.SITE"],"industry":["Cross-industry"],"navPath":"NAV.PHY.BLT.SITE","tags":["site","campus","phy.blt.site"],"facets":{}},"whatItIs":"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.","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":{"in":["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":["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"],"boundaries":[{"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."},{"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."},{"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."},{"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."},{"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."},{"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."},{"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."}]},"distinguishingFeatures":["A bounded area of land under coordinated management control, containing facilities but not equal to any one building.","Differs from a cadastral parcel, a legal unit of ownership that may be split across or combined into a site.","Differs from a settlement or place, which are geographic and civic rather than managed operational containers.","Reporting boundaries such as energy or emissions perimeters are dated views over the site, not its extent."],"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.","layers":[{"id":"identity-and-designation","name":"Identity and designation","description":"Identifier assignment, identifier priority, naming and the rules governing retirement or reuse.","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.","questions":[{"text":"Which identifier is the authoritative master-system identifier for this site, and which system issues and maintains it?","id":"q-authoritative-identifier","kind":"identity"},{"text":"Which governed global identifiers or IRIs resolve to this site, and what persistence guarantee does each carry?","id":"q-governed-global-identifiers","kind":"interoperability"},{"text":"If no external authoritative identifier exists, what UUID or ULID has the adopting Dimension assigned, and when?","id":"q-surrogate-key","kind":"identity"},{"text":"What official, legal, trading and wayfinding names does the site carry, in which languages, and which is canonical?","id":"q-names-and-languages","kind":"definition"},{"text":"Under what conditions may this identifier be retired, and may it ever be reassigned to a different site?","id":"q-identifier-retirement","kind":"constraint"}]}]},{"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.","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.","questions":[{"text":"Against which governed classification schemes is this site classified, and what is the scheme version for each assigned value?","id":"q-classification-schemes","kind":"classification"},{"text":"Can the site hold more than one classification at the same time, and how are conflicting values reconciled?","id":"q-multiple-classifications","kind":"constraint"},{"text":"Is this record a site complex, a site, or a site section, and what does that imply for its parent and child records?","id":"q-composition-type","kind":"composition"},{"text":"What events oblige the site to be reclassified, and who may authorise the change?","id":"q-reclassification-trigger","kind":"lifecycle"}]},{"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.","questions":[{"text":"What written rule determines whether a given area, facility or network falls inside this site's managed extent?","id":"q-inclusion-rule","kind":"definition"},{"text":"Is the site contiguous, and if not, what are its separate parts and what justifies treating them as one site?","id":"q-discontiguous-parts","kind":"spatial"},{"text":"Which areas inside the outer boundary are excluded from the managed extent, and who controls them?","id":"q-third-party-enclaves","kind":"exception"},{"text":"Who has authority to change the managed extent, and what evidence must accompany such a change?","id":"q-extent-authority","kind":"authority"}]}]}]},{"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.","layers":[{"id":"spatial-footprint","name":"Spatial footprint","description":"Boundary geometry, spatial referencing, accuracy and the vertical envelope of the site.","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.","questions":[{"text":"What geometry represents the site boundary, and in which coordinate reference system and vertical datum is it expressed?","id":"q-boundary-geometry-crs","kind":"spatial"},{"text":"What is the positional accuracy of the boundary, and by what survey or capture method was it derived?","id":"q-positional-accuracy","kind":"quality"},{"text":"What single reference point represents the site for coarse location and relative placement, and how is it defined?","id":"q-reference-point","kind":"spatial"},{"text":"Does the managed extent include airspace, subsurface volume or water column, and to what stated limits?","id":"q-vertical-subsurface-extent","kind":"spatial"},{"text":"Where does the operational boundary diverge from the legal parcel line, and how is that divergence recorded?","id":"q-boundary-versus-legal-line","kind":"constraint"}]},{"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.","questions":[{"text":"What coordinate reference system, including datum, projection and epoch, is authoritative for this site?","id":"crs-origin-and-reference-point-q01","kind":"spatial"},{"text":"What easting, northing, orthogonal height, scale and rotation define the map conversion from the engineering system to the CRS?","id":"crs-origin-and-reference-point-q02","kind":"spatial"},{"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?","id":"crs-origin-and-reference-point-q03","kind":"spatial"},{"text":"When was the georeference surveyed (event time) and when was it ingested into this model (observation time)?","id":"crs-origin-and-reference-point-q04","kind":"temporal"}]}]},{"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.","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.","questions":[{"text":"Which cadastral parcels or equivalent legal land units does the managed extent cover, wholly or partly?","id":"q-parcels-covered","kind":"relationship"},{"text":"Under what tenure does the operator hold each parcel or part, and for what term?","id":"q-tenure-basis","kind":"ownership"},{"text":"Which easements, rights of way, wayleaves or covenants constrain how the site may be used?","id":"q-encumbrances","kind":"constraint"},{"text":"Which register or authority is the source of truth for each tenure statement, and when was it last verified?","id":"q-tenure-authority","kind":"provenance"}]},{"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.","questions":[{"text":"At which points does the site connect to the public transport network, and what are the constraints on each?","id":"q-public-access-points","kind":"spatial"},{"text":"Which addresses are associated with the site, for which purpose, and which is the emergency response address?","id":"q-addresses","kind":"relationship"},{"text":"Where is the demarcation point for each incoming utility, and who is responsible on each side of it?","id":"q-utility-demarcation","kind":"authority"},{"text":"What land uses and sensitive receptors adjoin the site, and what obligations do they create?","id":"q-adjacency-and-context","kind":"relationship"}]},{"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.","questions":[{"text":"Which planning or building-code authority sets development controls for this site, and which zoning or plan-unit designations apply?","id":"development-controls-and-easements-q01","kind":"authority"},{"text":"What are the current buildable area, site coverage ratio, floor-area ratio, height limit and total planned area?","id":"development-controls-and-easements-q02","kind":"constraint"},{"text":"Which easements, rights of way, superficie or other interests in land encumber the site, and which facilities do they protect or restrict?","id":"development-controls-and-easements-q03","kind":"constraint"},{"text":"If local code, campus master plan and recorded easements conflict, which constraint is binding for a proposed development?","id":"development-controls-and-easements-q04","kind":"decision"}]}]}]},{"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.","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.","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.","questions":[{"text":"Which facilities does this site contain, and what identifier does each carry in the facility model?","id":"q-facility-inventory","kind":"composition"},{"text":"For each contained facility, is the relationship exclusive containment or a non-exclusive reference, and can a facility belong to two sites?","id":"q-containment-versus-reference","kind":"relationship"},{"text":"Where does site responsibility end and facility responsibility begin for services, structure and information?","id":"q-handover-boundary","kind":"authority"},{"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?","id":"q-third-party-facilities","kind":"exception"}]},{"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.","questions":[{"text":"Which distribution and drainage networks does the site own or operate, and what does each serve?","id":"q-network-inventory","kind":"composition"},{"text":"What record exists of buried and concealed infrastructure, at what confidence, and when was it last verified?","id":"q-buried-assets","kind":"evidence"},{"text":"What capacity and redundancy does each on-site network provide, and what is its current headroom?","id":"q-capacity-and-redundancy","kind":"measurement"},{"text":"At what point does each on-site network hand over to a facility or to an external operator?","id":"q-network-demarcation","kind":"authority"}]},{"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.","questions":[{"text":"How is the site surface distributed across land cover and surface types, and by what area measure?","id":"q-land-cover","kind":"measurement"},{"text":"Which ecological, heritage or protected features exist on the site, and what constraints do they impose?","id":"q-protected-features","kind":"constraint"},{"text":"Which open areas are designated for parking, laydown, storage or circulation, and what are their capacities?","id":"q-operational-open-space","kind":"composition"},{"text":"Who is responsible for maintaining each category of open space, and under what service arrangement?","id":"q-grounds-responsibility","kind":"ownership"}]}]},{"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.","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.","questions":[{"text":"Which zoning schemes apply to this site, and what zones does each define?","id":"q-zone-taxonomy","kind":"classification"},{"text":"Where do zones from different schemes overlap, and which scheme governs when their rules conflict?","id":"q-overlapping-zones","kind":"constraint"},{"text":"Which parts of the site are in a development, construction, commissioning or decommissioning phase, and until when?","id":"q-phase-status","kind":"state"},{"text":"Who may create, alter or dissolve a zone, and what record captures that decision?","id":"q-zone-authority","kind":"authority"}]},{"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.","questions":[{"text":"What internal route network exists for vehicles, pedestrians and goods, and what restrictions apply to each route?","id":"q-internal-route-network","kind":"composition"},{"text":"Which gates, barriers and control points sit on the internal network, and what is each capable of enforcing?","id":"q-control-points","kind":"process"},{"text":"Which routes are designated as step-free or otherwise accessible, and when was this last verified?","id":"q-accessible-routes","kind":"requirement"},{"text":"What routes and hardstanding are reserved for emergency vehicle access, and what keeps them clear?","id":"q-emergency-vehicle-access","kind":"exception"}]}]}]},{"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.","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.","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.","questions":[{"text":"Who is the legal owner of the site, who operates it, and are they the same party?","id":"q-owner-versus-operator","kind":"ownership"},{"text":"Which named role carries statutory duty-holder accountability for the site, and for which duties?","id":"q-duty-holder","kind":"authority"},{"text":"What decisions has the accountable party delegated to site management, and what limits apply?","id":"q-delegation-scope","kind":"authority"},{"text":"How is a change of owner, operator or duty holder recorded, and what must be transferred with it?","id":"q-accountability-change","kind":"lifecycle"}]},{"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.","questions":[{"text":"Which permits, licences and consents does the site hold, from which authority, and with what validity period?","id":"q-authorisations-held","kind":"authority"},{"text":"Which conditions attached to each authorisation constrain site operations or trigger reporting?","id":"q-authorisation-conditions","kind":"constraint"},{"text":"In which regulatory registries does this site appear, under what registry identifier, and does the registry record match the managed extent?","id":"q-registry-interests","kind":"interoperability"},{"text":"What are the renewal, variation and surrender triggers for each authorisation, and who owns each action?","id":"q-authorisation-renewal","kind":"process"}]}]},{"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.","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.","questions":[{"text":"What physically constitutes the site perimeter, and which entry and exit points are designated for access enforcement?","id":"q-perimeter-definition","kind":"security"},{"text":"Who authorises physical access to the site and to each security zone, and on what basis is authorisation granted and revoked?","id":"q-access-authorisation-model","kind":"access"},{"text":"How are visitors and contractors identified, escorted and accounted for while on site?","id":"q-visitor-and-contractor-control","kind":"process"},{"text":"What physical access records are captured at each point, and how long are they retained?","id":"q-access-logging-retention","kind":"retention"},{"text":"How are keys, cards and other physical access devices inventoried, and when are combinations changed?","id":"q-access-device-inventory","kind":"security"}]},{"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.","questions":[{"text":"How is each class of site information classified for sensitivity, and who assigns the classification?","id":"q-sensitivity-classification","kind":"privacy"},{"text":"Which site details must be withheld or redacted before information leaves the controlled environment, and on what basis?","id":"q-redaction-rules","kind":"security"},{"text":"Which site information must be published or disclosed on request regardless of the operator's preference?","id":"q-mandatory-disclosure","kind":"access"},{"text":"Where a disclosure obligation conflicts with a security restriction, what process resolves it and who decides?","id":"q-conflict-disclosure-security","kind":"exception"}]}]}]},{"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.","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.","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.","questions":[{"text":"What controlled vocabulary of site states applies, and which state is current as at which effective date?","id":"q-state-vocabulary","kind":"state"},{"text":"Who may authorise each state transition, and what evidence must exist before the transition is recorded?","id":"q-transition-authority-evidence","kind":"authority"},{"text":"When a site is split, merged or partly transferred, how are predecessor and successor identifiers linked?","id":"q-split-merge-lineage","kind":"provenance"},{"text":"For every recorded change, what are the event time and the observation or ingestion time, and do they differ?","id":"q-event-versus-record-time","kind":"temporal"},{"text":"Which foreseeable and unforeseeable trigger events require the site record to be updated, and within what timescale?","id":"q-trigger-events","kind":"event"}]},{"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.","questions":[{"text":"What operating hours and seasonal or shift regimes apply to the site and to individual zones?","id":"q-operating-periods","kind":"temporal"},{"text":"What rules must every person on site comply with, and what induction or competence is required before entry?","id":"q-site-rules-induction","kind":"requirement"},{"text":"Which activities on this site require a permit to work or equivalent control, and who issues them?","id":"q-permit-to-work","kind":"process"},{"text":"Which facility services are provided across the site, by whom, and under what agreed performance levels?","id":"q-service-provision","kind":"process"}]},{"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.","questions":[{"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?","id":"construction-work-site-and-temporary-holdings-q01","kind":"lifecycle"},{"text":"Which secondary construction or adjacent support sites are linked to the primary site of the work, and are they inside the permanent campus?","id":"construction-work-site-and-temporary-holdings-q02","kind":"relationship"},{"text":"Does a labour-law site-of-the-work envelope differ from the operational campus, and which activities are excluded as general manufacturing?","id":"construction-work-site-and-temporary-holdings-q03","kind":"exception"}]}]},{"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.","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.","questions":[{"text":"To which natural hazards is the site exposed, at what assessed severity and return period, and from which authoritative dataset?","id":"q-natural-hazard-exposure","kind":"measurement"},{"text":"What is the known contamination status of the site's ground and groundwater, and what remediation history exists?","id":"q-contamination-status","kind":"evidence"},{"text":"Which hazardous substances or processes are present on site, in what quantities, and what regulatory thresholds do they engage?","id":"q-process-hazards","kind":"constraint"},{"text":"How current is each hazard and environmental assessment, and what triggers reassessment?","id":"q-assessment-currency","kind":"quality"}]},{"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.","questions":[{"text":"Is a written emergency action plan required for this site, and where is the current approved version held?","id":"q-written-plan-requirement","kind":"requirement"},{"text":"What evacuation type, exit route assignments and muster points apply, and how are all persons accounted for afterwards?","id":"q-evacuation-and-accounting","kind":"process"},{"text":"What employee alarm system is in place, what distinct signals does it use, and how is it maintained and tested?","id":"q-alarm-system","kind":"requirement"},{"text":"Who has assigned emergency duties including rescue, medical and critical-operations roles, and what triggers a review of the plan with them?","id":"q-emergency-roles-and-review","kind":"authority"},{"text":"What arrangements exist with external emergency responders, including site access, hazard briefing and rendezvous points?","id":"q-external-responder-interface","kind":"relationship"}]}]}]},{"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.","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.","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.","questions":[{"text":"Which area measures are recorded for the site, on what measurement basis, and in which units?","id":"q-area-measures","kind":"measurement"},{"text":"Where the measured site area differs from registered parcel area values, which prevails for which purpose?","id":"q-area-versus-registered","kind":"quality"},{"text":"What occupancy or population does the site carry, measured how and over what period?","id":"q-occupancy","kind":"measurement"},{"text":"What capacity limits constrain the site, and which are regulatory rather than physical?","id":"q-capacity-limits","kind":"constraint"}]},{"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.","questions":[{"text":"For each reporting scheme, what boundary is drawn over the site, and how does it differ from the managed extent?","id":"q-reporting-boundary-definition","kind":"definition"},{"text":"Is the site represented as a parent property with child properties, and what aggregation rules apply?","id":"q-parent-child-aggregation","kind":"composition"},{"text":"Which meters serve the whole site versus individual facilities, and how is shared plant consumption allocated?","id":"q-meter-coverage-allocation","kind":"measurement"},{"text":"Which greenhouse-gas consolidation approach applies to this site, and which scopes are reported for it?","id":"q-consolidation-approach","kind":"decision"},{"text":"What is the completeness and quality of each reported quantity, and how much is estimated?","id":"q-reporting-data-quality","kind":"quality"}]}]},{"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.","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.","questions":[{"text":"Which observable properties of the site are monitored, on which features of interest, and by which sensors or platforms?","id":"q-monitored-properties","kind":"measurement"},{"text":"For each observation, what is the phenomenon time and what is the result time, and how is the difference handled?","id":"q-observation-times","kind":"temporal"},{"text":"Which monitoring is mandated by an authorisation or standard rather than chosen by the operator?","id":"q-monitoring-obligation","kind":"requirement"},{"text":"How is the quality of site monitoring data established, including calibration, drift and gap handling?","id":"q-sensor-data-quality","kind":"quality"}]},{"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.","questions":[{"text":"Which record evidences each material assertion about the site, and what is that record's status and suitability?","id":"q-evidence-for-assertions","kind":"evidence"},{"text":"For each record, who produced it, from what inputs, by what method, and who approved it?","id":"q-provenance-chain","kind":"provenance"},{"text":"How is a record known to be current, and how are superseded versions marked and retained?","id":"q-currency-and-supersession","kind":"validation"},{"text":"What retention period applies to each record class, on what legal basis, and what is the approved disposal action?","id":"q-retention-and-disposal","kind":"retention"},{"text":"Which common data environment is the agreed source of information for this site, and how is access to it controlled?","id":"q-common-data-environment","kind":"access"}]}]},{"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.","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.","questions":[{"text":"To which external schemas is this site record aligned, at which version, and is the alignment full or partial?","id":"q-alignment-targets","kind":"interoperability"},{"text":"What information is lost, generalised or forced in each mapping, and what compensating record is kept?","id":"q-mapping-loss","kind":"quality"},{"text":"By what rules is this site matched to a candidate record in an external system, and what confidence does a match carry?","id":"q-matching-rules","kind":"validation"},{"text":"What evidence supports any claim of conformance to an external standard, and where a claim cannot be evidenced how is it recorded?","id":"q-conformance-evidence","kind":"evidence"},{"text":"Which elements of an aligned schema are deprecated, and how are they handled in exchange?","id":"q-deprecated-elements","kind":"constraint"}]}]}]}]},"agentConduct":{"may":["Register a site with boundary, identifiers and responsible operator.","Reconcile site identifiers across registries and asset systems.","Record observations such as condition, environmental status or occupancy counts.","Compile a reporting boundary view for a declared period."],"mustNot":["Redefine a site boundary from geometry alone without an authorized decision.","Grant or revoke physical access to the site.","Publish security-sensitive layouts, gates, utilities or occupancy data.","Close a contamination or construction overlay without evidence.","Treat the site as the legal owner of land parcels."],"requiresHuman":["Changing the managed boundary, splitting or merging sites.","Granting physical access credentials.","Closing a site and releasing environmental obligations."]},"ethics":{"considerations":["Sites hold people at work, study or care, so access and hazard information is a safety matter.","Contamination and emissions affect neighbours and ecosystems beyond the boundary.","Public site data can expose critical infrastructure to attack."],"affectedParties":["People working, living or studying on the site","Neighbouring communities","Emergency services"]},"owners":{"steward":"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.","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"]}],"masterSystems":[]},"relations":[{"target":"WM-PLC-002 Place","type":"child","note":"Site / Campus specialises the generic place concept, inheriting spatial referencing and naming semantics while adding managed-container behaviour."},{"target":"WM-PLC-005 Settlement","type":"references","note":"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."},{"target":"WM-BLT-006 Facility","type":"composes","note":"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."},{"target":"Land administration / property right sibling model (LADM-aligned)","type":"references","note":"Supplies parcels, basic administrative units, parties and rights, responsibilities and restrictions that the site references but must not re-model."},{"target":"Organisation and party sibling model","type":"references","note":"Resolves owner, operator, duty holder, service provider and regulator references; site identity must never be conflated with the operating legal entity."},{"target":"Address and geocoding sibling model","type":"references","note":"Supplies typed addresses for postal, delivery, emergency and registered purposes; IFC deprecated the site-embedded address attribute, reinforcing external ownership of addressing."},{"target":"Authorisation, permit and licence sibling model","type":"references","note":"Holds permits, licences and consents as legal instruments; the site records only which authorisations apply, their validity and their operational conditions."},{"target":"Asset register and maintenance sibling model","type":"references","note":"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."},{"target":"Utility network sibling model","type":"references","note":"Owns external network topology and operations; the site records only on-site distribution and the demarcation point where responsibility transfers."},{"target":"Observation and sensing mix-in (SOSA/SSN pattern)","type":"composes","note":"Supplies Platform, Sensor, Observation, FeatureOfInterest and the normative separation of phenomenon time from result time, reused rather than redefined by this model."},{"target":"Lifecycle state and versioning mix-in","type":"composes","note":"Supplies the versioned-object pattern with beginLifespanVersion and endLifespanVersion alongside real-world validFrom and validTo, keeping event time and record time distinct."},{"target":"IFC 4.3 (ISO 16739-1) IfcSite and IfcFacility","type":"aligned","note":"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."},{"target":"OGC CityGML 3.0 Conceptual Model (OGC 20-010)","type":"aligned","note":"Alignment target for encoding-independent geospatial representation, city object grouping, land use and relief at site scale."},{"target":"INSPIRE Cadastral Parcels (D2.8.I.6 v3.1.1)","type":"aligned","note":"Alignment target for parcel referencing and lifespan versioning attributes when operating in the European regulatory context."},{"target":"ISO 55001:2024 asset management system","type":"aligned","note":"Alignment target for management-system scope, accountability, life-cycle planning and control of change applied to the site as a managed object."},{"target":"ISO 19650 information management framework","type":"aligned","note":"Alignment target for information containers, suitability status, the common data environment as agreed source of information, and the trigger-event update pattern."},{"target":"GHG Protocol Corporate Standard boundary rules","type":"aligned","note":"Alignment target for organizational and operational boundary setting when a site emissions inventory is compiled."},{"target":"EPA Facility Registry Service","type":"aligned","note":"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."},{"target":"WM-BLT-006 Facility","type":"neighbor","note":"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."},{"target":"Land parcel / cadastral parcel (land administration sibling model)","type":"neighbor","note":"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."},{"target":"WM-PLC-005 Settlement and WM-PLC-002 Place","type":"neighbor","note":"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."},{"target":"Regulatory facility registry entries (e.g. EPA FRS facility site)","type":"neighbor","note":"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."},{"target":"Reporting boundary constructs (ENERGY STAR property, GHG Protocol organizational boundary)","type":"neighbor","note":"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."},{"target":"Utility network model","type":"neighbor","note":"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."},{"target":"Asset management system (ISO 55001) and asset information model (ISO 19650)","type":"neighbor","note":"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."},{"target":"WM-PLC-002","type":"parent"},{"target":"WM-BLT-006","type":"contains"}],"interaction":{"identity":{"applicability":"required","items":["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."]},"properties":{"applicability":"required","items":["Land area in square metres or hectares, computed from the authorized boundary in a declared coordinate reference system.","Boundary coordinates in a declared coordinate reference system, with positional accuracy in metres.","Elevation in metres above a declared vertical datum.","Perimeter length in metres along the authorized boundary.","Occupancy as a count of people on site, stated with observation time and method.","Energy use in kilowatt-hours and water use in cubic metres within a declared measurement boundary and period."]},"recognition":{"applicability":"required","items":["A site is recognized by a named boundary, entrances, signage, fences and the facilities it contains.","On the ground it is confused with a single building, a land parcel or a neighbourhood.","Records of the same site appear under different identifiers in cadastral, regulatory and asset registries."]},"capabilities":{"applicability":"required","items":["Register a site: Create a governed site record and assign its canonical identifier under the identity priority rule.","Define or revise the site boundary: Record boundary geometry with a declared coordinate reference system, vertical datum, positional accuracy and survey provenance.","Attach or detach a facility: Create or end a containment edge between the site and a facility record in WM-BLT-006, with relationship type and effective period.","Transition site lifecycle state: Move the site to a new state in the controlled vocabulary with authorisation, evidence and separately recorded effective and record times.","Split, merge or transfer part of a site: Reorganise site records while preserving predecessor and successor lineage and reassigning contained facilities, authorisations and reporting boundaries.","Reconcile external site identifiers: Match the site against candidate records in external registries and operational systems and record match confidence and unresolved conflicts.","Grant or revoke physical site access: 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.","Record a site observation: Ingest an observation against a site feature of interest with its phenomenon time and result time held separately.","Compile a reporting boundary and return: Assemble a scheme-specific reporting boundary from parent and child properties, meter coverage and allocation rules, and produce the reportable dataset.","Validate a site record: Run structural, referential and temporal validation over the site record and report defects against declared rules.","Close a site and apply retention: Move a site to a closed state and apply the retention and disposal schedule to its records, retaining what regulation requires.","Assign party roles: Record owner, operator, occupier and LADM RRR, and optionally transfer AIM on ownership change.","Bind cadastral units: Associate LandID, LandTitleID, INSPIRE locators or LADM spatial units and optional SpatialUnitGroup without collapsing legal parcels.","Compose site structure: Set COMPLEX/ELEMENT/PARTIAL composition and parent/child site relations, including disconnected members of a campus complex.","Record environmental status: Attach a contamination or statutory-facility overlay, affected geometry and responsible parties."]},"hazards":{"applicability":"required","items":["Wrong boundary leading to unreported contamination or emissions.","Emergency response delayed by wrong entrances or access data.","Unauthorized entry when access records are stale.","Exposure of sensitive layouts."]},"interfaces":{"applicability":"required","items":["OGC CityGML 3.0 conceptual model.","ISO 16739-1 Industry Foundation Classes (IfcSite).","ISO 19152 Land Administration Domain Model.","ISO 19650 information management for built assets.","ISO 55001 asset management systems.","IETF RFC 7946 GeoJSON and ISO 6709 for coordinates."]},"context":{"applicability":"required","items":["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."]}},"sources":[{"title":"IfcSite - IFC 4.3.2 Documentation","url":"https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcSite.htm","note":"buildingSMART International"},{"title":"IfcFacility - IFC 4.3.2 Documentation","url":"https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcFacility.htm","note":"buildingSMART International"},{"title":"FRS Description - Facility Registry Service","url":"https://www.epa.gov/frs/frs-description","note":"United States Environmental Protection Agency"},{"title":"D2.8.I.6 INSPIRE Data Specification on Cadastral Parcels - Technical Guidelines","url":"https://inspire-mif.github.io/technical-guidelines/data/cp/dataspecification_cp.html","note":"European Commission - INSPIRE Maintenance and Implementation Group"},{"title":"Semantic Sensor Network Ontology (SSN/SOSA)","url":"https://www.w3.org/TR/vocab-ssn/","note":"World Wide Web Consortium (W3C)"},{"title":"29 CFR 1910.38 - Emergency action plans","url":"https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.38","note":"United States Department of Labor - Occupational Safety and Health Administration"},{"title":"NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations","url":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","note":"National Institute of Standards and Technology"},{"title":"OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard","url":"https://www.ogc.org/standard/citygml/","note":"Open Geospatial Consortium"},{"title":"ISO 55001:2024 Asset management - Asset management system - Requirements","url":"https://www.iso.org/standard/83054.html","note":"International Organization for Standardization"},{"title":"ISO 19152-1:2024 Geographic information - Land Administration Domain Model (LADM) - Part 1: Generic conceptual model","url":"https://www.iso.org/standard/81263.html","note":"International Organization for Standardization"},{"title":"How to Benchmark a Campus in Portfolio Manager","url":"https://www.energystar.gov/buildings/tools-and-resources/how-benchmark-campus","note":"United States Environmental Protection Agency - ENERGY STAR"},{"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","url":"https://www.iso.org/standard/68078.html","note":"International Organization for Standardization"},{"title":"GHG Protocol Corporate Accounting and Reporting Standard","url":"https://ghgprotocol.org/corporate-standard","note":"World Resources Institute and World Business Council for Sustainable Development"},{"title":"ISO 41011:2024 Facility management - Vocabulary","url":"https://www.iso.org/standard/82405.html","note":"International Organization for Standardization"},{"title":"IfcSite — IFC 4.3.2.0 (IFC4X3_ADD2) official documentation","url":"https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcSite.htm","note":"buildingSMART International"},{"title":"ISO 6707-1:2020 Buildings and civil engineering works — Vocabulary — Part 1: General terms","url":"https://www.iso.org/obp/ui/es/?_escaped_fragment_=iso:std:77077:en","note":"International Organization for Standardization"},{"title":"OPC UA Common Object Model: ISA-95 — ISA95EquipmentElementLevelEnum","url":"https://reference.opcfoundation.org/specs/OPC-10030/7.4","note":"OPC Foundation"},{"title":"INSPIRE Data Specification on Cadastral Parcels — Technical Guidelines","url":"https://inspire-mif.github.io/technical-guidelines/data/cp/dataspecification_cp.pdf","note":"European Commission INSPIRE Maintenance and Implementation Group"},{"title":"OGC Land and Infrastructure Conceptual Model Standard (LandInfra)","url":"https://docs.ogc.org/is/15-111r1/15-111r1.html","note":"Open Geospatial Consortium"},{"title":"42 U.S. Code § 9601 — CERCLA definitions","url":"https://www.law.cornell.edu/uscode/text/42/9601","note":"United States Congress"},{"title":"ISO 19152-2:2025 Geographic information — Land Administration Domain Model (LADM) — Part 2: Land registration","url":"https://www.iso.org/standard/81264.html","note":"International Organization for Standardization"},{"title":"ISO 19650-3:2020 Information management using BIM — Part 3: Operational phase of the assets","url":"https://www.iso.org/obp/ui/en/?_escaped_fragment_=iso:std:75109:en","note":"International Organization for Standardization"},{"title":"OGC CityGML 3.0 Conceptual Model Standard","url":"https://www.ogc.org/publications/standard/citygml/","note":"Open Geospatial Consortium"},{"title":"Pset_LandRegistration — IFC 4.3.2.0","url":"https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/Pset_LandRegistration.htm","note":"buildingSMART International"},{"title":"IEC 62264-1:2013 Enterprise-control system integration — Part 1: Models and terminology","url":"https://standards.iteh.ai/catalog/standards/iso/db90faa8-7d04-4c7f-aeb0-627675ee5a1e/iec-62264-1-2013","note":"International Electrotechnical Commission"},{"title":"Pset_SiteCommon — IFC 4.3.2.0","url":"https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/Pset_SiteCommon.htm","note":"buildingSMART International"},{"title":"29 CFR 5.2 — Definitions, including site of the work","url":"https://www.ecfr.gov/on/2024-10-07/title-29/section-5.2","note":"United States Department of Labor"}],"openQuestions":["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.","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."],"resources":{"spec":"/models/wm-blt-008-site-campus/spec.yaml","agents":"/models/wm-blt-008-site-campus/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-008"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-blt-008-site-campus/spec.yaml","ver-cy/world-models/card-supplements/wm-blt-008-site-campus.json"],"providers":["Claude","Grok"],"researchStatus":"reviewable-draft","generatedAt":"2026-08-24T10:16:53Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"filled","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}