Facility

Facility identifier set and resolution rules

The identifiers that pin a facility to a single real-world referent: the master-system key, governed registry identifiers issued by external authorities, and the rules for uniqueness, non-reuse, merge and split. EPA FRS demonstrates the pattern of assigning a registry identifier and then matching incoming program records to it.

1. Which identifier is the authoritative master-system key for this facility, which system issues it, and over what population is it unique? identity
2. Which governed external registry identifiers resolve to this facility, and what is their precedence for cross-system reconciliation? interoperability
3. Is the identifier persistent and never reused after the facility is decommissioned, merged into another facility or split? constraint
4. What deduplication and match-confidence rule applies when two source systems report what may be the same physical facility? validation

Facility naming and structured designation

Human-readable names, aliases and signage names alongside structured reference designations formed under ISO 81346-12. Names are mutable and non-unique and must never be used as identity, while reference designations encode a position in a functional, product or location aspect structure.

1. What is the preferred facility name, in which language and script, and which authority may change it? definition
2. Which alternate, historical, legal and signage names apply, and over what validity periods? temporal
3. What reference designation is assigned to the facility, and in which aspect structure is it expressed? classification
4. Where a downstream system keys on name rather than identifier, what compensating control prevents mis-resolution? validation

Functional and reporting classification

The facility's primary function and any secondary uses, expressed in one or more governed schemes (IFC facility subtype, Uniclass Complexes/Entities, ENERGY STAR property type, industrial activity codes used for regulatory reporting), with an explicit precedence for each downstream purpose.

1. What is the facility's primary function code, in which classification scheme and version, and as of what date? classification
2. Which secondary uses coexist at this facility and what share of floor area or activity does each represent? composition
3. Which classification is authoritative for regulatory reporting, and which is authoritative for benchmarking and portfolio analysis? authority
4. What change of use triggers reclassification, and what revaluation, permitting or benchmarking consequences follow? lifecycle

Building-code occupancy and hazard classification

The regulatory occupancy groups assigned under the applicable building code edition, construction type, mixed-occupancy treatment and the highest hazard class present. This classification is legally consequential and is asserted by an authority having jurisdiction, unlike operational typologies.

1. Which code occupancy group or groups apply, under which code edition adopted by which jurisdiction? classification
2. Where multiple occupancies coexist, is the facility treated as separated, non-separated or accessory, and where are the separation boundaries? constraint
3. What is the highest hazard classification present, and which stored or processed materials drive it? classification
4. Which authority having jurisdiction issued the occupancy determination and what evidence records it? authority

Facility geometry, georeference and level of detail

The representative point and boundary geometry of the facility, the coordinate reference system and vertical datum, positional accuracy, and the level of detail at which geometry is held. CityGML supplies LoD semantics, INSPIRE supplies accuracy and elevation reference expectations, and IFC supplies relative placement against site or parent facility.

1. Which geometric representations exist for the facility, and which one is authoritative for regulatory and emergency use? spatial
2. In which coordinate reference system and vertical datum is the geometry expressed, and what is its stated horizontal and vertical accuracy? measurement
3. At what level of detail is the geometry held, and what was the capture method and capture date? provenance
4. Is the facility placed absolutely or relatively to a site or parent facility, and what happens to the placement if the parent moves or is re-surveyed? relationship

Addressing and jurisdictional placement

Addresses used for postal, service, regulatory and emergency purposes, plus the administrative and jurisdictional units the facility falls within, including cases where it straddles a boundary. Address values are references into a sibling Address model; only role, authority and jurisdiction assignment are held here.

1. Which addresses are recorded for the facility and what role does each play (postal, regulatory reporting, emergency response, service delivery)? identity
2. Which administrative and jurisdictional units contain the facility, at which levels, and on what date were they determined? spatial
3. Does the facility straddle any jurisdictional, tribal, utility or emergency-response boundary, and how is the split resolved for reporting? exception

Site containment and boundary exclusivity

The typed edge from the containing Site to this Facility, whether that containment is exclusive, whether the facility spans multiple sites or parcels, and how facility identity survives site subdivision or amalgamation. IFC permits a facility with no site at all, so containment must be modelled as conditional.

1. Which site or sites contain this facility, and is the containment exclusive for the period asserted? relationship
2. If no site is recorded, what justifies treating the facility as the outermost spatial container, and what supplies its georeference? exception
3. When the containing site is subdivided, merged or re-tenured, does the facility identifier persist and what event records the change? lifecycle

Facility part decomposition and building membership

How the facility breaks down into parts and which buildings or structures are members over which periods. IFC requires an explicit usage convention for each facility part, and permits a facility to be part of a facility part, which allows longitudinal or regional division of larger facilities.

1. Which decomposition convention governs the facility breakdown, and why was it chosen over the alternatives? composition
2. Which buildings and structures are members of this facility, and over what validity period is each membership asserted? relationship
3. How are shared, common or jointly used parts handled where membership is not exclusive? exception
4. How deep does the facility breakdown go before responsibility passes to the Building or Space model? constraint

Engineered systems and asset register linkage

Facility-level engineered systems (power, HVAC, water, drainage, fire protection, security, communications), their structured reference designations, the spaces or parts they serve, and the linkage from facility to the component asset register that holds individual equipment items.

1. Which engineered systems serve this facility, and what reference designation and aspect structure identifies each? composition
2. Which systems cross the facility boundary to a site-level or external utility, and where is the demarcation point? relationship
3. What key links facility records to the component asset register, and what proportion of installed assets is covered? interoperability
4. How is an asset that is relocated between facilities recorded, and which record retains its maintenance history? process

Non-building, mobile and exclusion cases

ISO 16739-1:2024 / IFC 4.3 extends facility to bridges, roads, railways, waterways and port facilities. FHIR includes mobile clinics, ambulances and vehicles. EPA includes monitoring stations and waste sites that cannot be classified as single facilities. ISO/TR 41013 states that a single asset such as a car or air-handling unit is not a facility, and that something not built, such as a nature preserve, is not a facility. Mobile versus fixed and instance versus kind must be explicit. Kind-of-location classifiers are out of scope as instances.

1. Is this a building-oriented facility, a civil or infrastructure facility, or a mixed campus, and which IFC or local subtype applies? classification
2. Is the facility fixed, mobile or relocatable, and if mobile what is the current position versus the home base? state
3. Does the candidate fail the facility test because it is a single asset, an unbuilt asset, a kind classifier, or a space or room? validation

Lifecycle phase, operational status and milestone events

The facility's position in the ISO 15686-1 life cycle (initiation, project definition, design, construction, commissioning, operation, maintenance, refurbishment, replacement, deconstruction and disposal), its current operational status, and the milestone events that changed either. INSPIRE supplies a construction-condition code list and ISO 19650-3 supplies operational trigger events that require an information exchange.

1. What is the facility's current lifecycle phase and operational status, on which code list, and since when? state
2. Which milestone events have occurred, and what are the event time and the observation or recording time for each? event
3. What evidence closes construction handover and opens operation, and who accepts it? evidence
4. Which terminal states exist (mothballed, disposed, demolished), and which obligations survive each of them? lifecycle

Condition assessment, service life and deferred maintenance

Measured or estimated physical condition of the facility, the method and date of assessment, design and remaining service life, and the accumulated deferred maintenance liability. Federal real-property reporting requires condition and related measures alongside a reassessment cadence.

1. What is the current condition measure, by which assessment method, and as of what assessment date? measurement
2. What design service life was specified and what remaining service life is now estimated, on what basis? quality
3. What is the deferred maintenance and repair liability, in which currency and price base, and as of when? measurement
4. How often must condition be reassessed, who is competent to do it, and what happens when the cadence is missed? process

Record versioning, valid time and observation time

The bitemporal discipline for facility records: record version validity bounds, real-world validity, event time, observation time and ingestion time, and the rule separating a correction of a past error from a genuine real-world change. INSPIRE mandates lifespan version bounds with time-zone information; CityGML supplies a versioning module for city object states.

1. What are this record version's validity bounds, and how do they differ from the facility's real-world validity period? temporal
2. For each time-bearing attribute, are event time, observation time and ingestion time recorded separately with explicit offsets? temporal
3. How is a correction of an erroneous earlier value distinguished from a record of a real-world change? provenance
4. What rule resolves overlapping or conflicting versions of the same facility record? validation

Ownership, custody and legal interest

The legal interest held in the facility (owned, leased, licensed or otherwise managed), the party holding title, the organisation with custody and control where different, and the encumbrances, easements and lease terms that constrain use. Federal real-property reporting treats legal interest, ownership and custodial agency as distinct reportable facts.

1. What type of legal interest is held in the facility, by which party, and over what term? ownership
2. Which organisation has custody and control of the facility for operational purposes, if different from the title holder? authority
3. Which encumbrances, easements, covenants or lease conditions constrain how the facility may be used or altered? constraint
4. What process records a change of ownership or interest, and what evidence must accompany it? process

Operator and facility-management accountability

The chain from demand organisation to facility-management service provider, the scope of services delegated, the governing agreement, and the named accountable person for statutory duties. ISO 41011 makes the demand-organisation and service-provider distinction the core of facility-management vocabulary.

1. Which organisation is the demand organisation for this facility and which is the facility-management service provider? ownership
2. What scope of services is delegated, under which agreement, and what is expressly retained by the demand organisation? authority
3. Who is the named accountable person or role for statutory duties at this facility, and how is competence evidenced? authority
4. How is a change of operator or service provider recorded, and what information must transfer with it? process

Regulatory programme interests, permits and statutory inspections

The regulatory programmes under which the facility is regulated or monitored, the programme identifiers issued by each regulator, the permits and authorisations in force with their validity and conditions, and the statutory inspection and certification regime with due dates, results and open nonconformities. EPA FRS models this as environmental interest types linking program records to a single facility registry identifier.

1. Which regulatory programmes apply to this facility, which regulator is competent for each, and what programme identifier has each issued? authority
2. Which permits and authorisations are currently in force, with what validity dates and what operating conditions? requirement
3. Which statutory inspections and certifications are required, and what are the last completion and next due dates for each? evidence
4. Which nonconformities are open, what corrective action is committed, and by when must it complete? exception
5. What periodic reporting obligations follow from each programme interest, and at what cadence? requirement

Occupancy authorization and authority having jurisdiction

Under IBC 111.1, a building or structure shall not be used or occupied, and a change of occupancy shall not be made, until the building official has issued a certificate of occupancy. Certificates that presume authority to violate the code are not valid. Work exempt from permit may be excepted. This rule is building-code-centric; roads, railways and some civil facilities are authorized by other AHJs. A CO authorizes occupancy under the building code; it does not by itself satisfy ongoing fire-code, elevator or environmental program duties. Phased projects may require occupancy authorization before occupying portions.

1. Has a certificate of occupancy or equivalent occupancy authorization been issued for this facility or a described portion, and by which AHJ? authority
2. What use, occupancy classification, construction type, code edition and design occupant load does the certificate authorize? authority
3. Is occupancy authorized in phases or for only a portion of the facility, and what is still prohibited? exception
4. When was the certificate issued or occupancy authorized, and when was that fact observed or ingested into this model? temporal

Compliance monitoring status

ECHO reports compliance monitoring activity counts, last monitoring date and statute-specific compliance status, including inactive facility. These determinations often reflect alleged rather than finally adjudicated violations. This finding is an alignment to US environmental operating data; it is not a universal compliance model and must not be treated as a court judgement.

1. What is the current reported compliance status by statute, and as of which refresh date? state
2. When did the last compliance monitoring activity occur, of what type, and is the date an on-site inspection or an evaluation completion date? event
3. Is the reported violation or noncompliance an alleged status used for tracking, or a final adjudication, and what caveats apply? quality

Facility security level and protective posture

The assessed security level of the facility derived from mission criticality, symbolism, facility population, facility size and threat to tenants, the baseline countermeasures that follow, implemented versus required status, and any accepted deviations. The ISC standard defines five levels with associated requirements.

1. What security level has been assessed for this facility, and what score did each determination factor contribute? security
2. Which protective measures are required at this level, which are implemented, and which deviations have been accepted by whom? security
3. Is the facility designated critical infrastructure, under which sector and by which authority? classification
4. When was the security assessment performed, when is reassessment due, and what event forces an early reassessment? temporal

Information disclosure and access constraints

Which facility attributes may be published, which must be withheld or generalised, on what legal basis, who may grant exceptions, and what must be logged. Federal real-property publication law expressly authorises excluding assets for national-security reasons and under freedom-of-information exemptions, establishing that facility inventories are not uniformly public.

1. Which attributes are withheld, generalised or precision-reduced in public releases, and on what legal basis is each? privacy
2. What sensitivity marking applies to each bundle, layer, finding and artifact of this facility record? access
3. Who may grant an access exception, for what duration, and under what justification? exception
4. What must be logged when restricted facility attributes are read, exported or shared with an external party? access

Area, capacity, occupancy and utilisation

Area measures under a declared measurement standard, design capacity, occupant population by category, operating schedule and derived utilisation. Gross floor area and operating-hours style use details are the mandatory inputs to benchmarking, while facility population and size are two of the five security-level determination factors.

1. Which area measures are recorded, under which measurement standard, and as of what date? measurement
2. What is the design capacity, what is actual utilisation, and by what formula is utilisation derived? measurement
3. What are the peak and typical occupant populations by category, how are they counted and how current is the count? measurement
4. What is the operating schedule, including weekly operating hours and seasonal or shift variation? temporal
5. How are shared and common areas apportioned across member buildings and tenants, and does the total reconcile? validation

Energy, water and emissions performance with measurement provenance

Benchmarked resource and emissions performance for the facility over stated reporting periods, the normalisation and benchmark reference used, the metering boundary relative to the facility boundary, and the share of values that are metered rather than estimated. Multi-building facilities are benchmarked as a parent property aggregating child buildings, which makes the boundary declaration mandatory rather than optional.

1. Which energy, water and emissions metrics are tracked, over what reporting period, and in what units? measurement
2. Which normalisation and benchmark reference is applied, and against which comparison population? quality
3. Does the metering boundary coincide with the facility boundary, and what is included or excluded? constraint
4. What share of reported consumption is metered versus estimated, and what estimation method was used? provenance
5. How are restatements of previously published performance figures identified, justified and propagated? process

Performance evaluation and service life

Service life is the period after installation during which a building or its parts meet performance requirements. Post-occupancy evaluation analyses how functional and comfortable a building is after users have occupied it. ISO 19650-3 includes post-occupancy or implementation evaluation as a point on the operational timeline. Key performance indicators and indoor environmental quality are measurement alignments; detailed energy-benchmarking schemes such as ENERGY STAR are known omissions unless later aligned.

1. What service-life period and performance requirements apply to the facility or its major parts? requirement
2. Has a post-occupancy or implementation evaluation been completed, when, and what outcomes were recorded? quality
3. Which key performance indicators are governed at facility level, including any indoor environmental quality measures, and what is the current result? measurement

Maintenance strategy and work management linkage

The maintenance strategy applied per system, the planned maintenance tasks and their frequencies, the linkage from work orders back to facility, system and component, and the maintenance backlog with its ageing profile. Handover data schemas carry planned job, resource and event tables that seed this regime at commissioning.

1. Which maintenance strategy applies to each facility system, and what evidence justifies the choice? decision
2. Which planned maintenance tasks and frequencies are defined, and from which source were they derived? process
3. How do work orders resolve back to facility, system and component, and what happens when the component is unknown? relationship
4. What is the maintenance backlog, how is it aged, and what threshold escalates it to a condition or risk finding? measurement

Criticality, hazard exposure and operational continuity

The facility's criticality or mission-dependency rating and the method behind it, the natural and human-caused hazards it is exposed to, redundancy and alternate-facility arrangements, and when continuity plans were last exercised. Criticality drives both asset-management investment prioritisation and the mission-criticality factor in security-level determination.

1. What criticality or mission-dependency rating does the facility carry, derived by which method and reviewed when? classification
2. Which natural and human-caused hazards is the facility exposed to, and on what likelihood and severity basis is each assessed? measurement
3. What redundancy, alternate-facility or degraded-mode arrangements exist if the facility becomes unavailable? process
4. When were the risk assessment and the continuity plan last reviewed and exercised, and what did the exercise find? evidence

Fire, life safety and risk

IfcFacility may carry Pset_SpaceFireSafetyRequirements (fire risk factor, flammable storage, fire exit, sprinkler protection, air pressurization) and Pset_Risk (likelihood, consequence, mitigation). These are facility-scale assertions and do not replace storey- or space-level life-safety design. ISO 41011 emergency preparedness is the capability to mitigate emergency consequences. National fire-code inspection programs such as NFPA 25 or 72 are known omissions as primary sources.

1. What fire-risk, sprinkler, exit and related life-safety assertions are made at facility scale, and where is detailed design held? constraint
2. What named risks are assessed for the facility, with unmitigated and mitigated likelihood, consequence and significance? constraint
3. What emergency-preparedness capability is asserted, and what evidence supports it? evidence

Asset information requirements and accepted deliverables

The organisational, asset and exchange information requirements that apply to this facility, the trigger events during operation that require an information exchange, the asset information model held for the facility, and how information is accepted or rejected. ISO 19650-3 establishes asset information requirements at asset level and exchange information requirements per appointment and trigger event.

1. Which organisational and asset information requirements apply to this facility, and which appointment-level exchange requirements derive from them? requirement
2. Which operational trigger events require an information exchange, to whom, and within what deadline? event
3. What constitutes the accepted asset information model for this facility, and where is its authoritative copy held? provenance
4. How are information acceptance and rejection recorded, and what happens to rejected deliverables? process

Attribute provenance, source precedence and validation

Per-attribute lineage to the supplying source system, the precedence rule when sources disagree, the validation rules a facility record must pass before publication, and the confidence attached to matched or derived values. Federated registries demonstrate the need: values are integrated from many program systems, matched, and periodically re-selected by an automated best-pick process.

1. For each attribute, which source system supplied the value, when was it observed and when was it ingested? provenance
2. What precedence rule resolves conflicting values for the same attribute from different sources? decision
3. Which validation rules must a facility record pass before publication, and which are blocking versus advisory? validation
4. What confidence or quality measure accompanies matched, derived or estimated values, and how is it computed? quality

External standard alignments and crosswalk fidelity

The external schemas, ontologies and classifications this model is aligned to, at which versions, whether each mapping is lossless, which concepts have no faithful counterpart, and what evidence would be required before asserting conformance. Notably, the widely used building topology vocabulary has no facility class between site and building, and IFC subordinates buildings to facilities by type rather than by aggregation.

1. Which external standards is this model aligned to, at what version, and in which direction does each mapping run? interoperability
2. Which concepts cannot be expressed faithfully in a given target, and what is lost or approximated? interoperability
3. What evidence would be required before claiming conformance rather than alignment to any target standard? evidence
4. How is alignment breakage detected when a target standard is revised, and who is accountable for repair? process

Retention, disposition and archival transfer

Which retention schedule governs each class of facility record, the disposition trigger and period, which records are permanent rather than temporary, and how destruction is evidenced. Government-wide scheduling treats routine facility operation and maintenance records as temporary with destruction three years after creation or supersession, while requiring the oldest records be offered for archival transfer before any disposition is applied.

1. Which retention schedule and item governs each class of facility record, and what is the disposition trigger and period? retention
2. Which facility records are permanent or must be offered for archival transfer, and on what criterion? retention
3. Which records must be retained for the life of the structure plus a defined period, and how is that end date computed? retention
4. How is destruction authorised and evidenced, and what residual metadata survives it? evidence

Canonical payload, packaging and interface neutrality

The canonical logical payload of a facility record independent of any serialisation, how artifacts are packaged and integrity-checked, how partial updates are expressed and validated, and the bootstrap manifest that must accompany any store. Handover schemas that publish equivalent content as spreadsheet, model-file and JSON demonstrate that meaning must be defined before format.

1. What is the canonical logical payload of a facility record, independent of document, graph, relational or document-database projection? interoperability
2. How are artifacts packaged, integrity-checked and referenced from the facility record? interoperability
3. How are partial updates expressed, ordered and validated against the canonical payload? process
4. What agent bootstrap contract must accompany any store or interface exposing this model? interoperability