Space (Usage) — Notes

Provenance

• Source: CORENET X Code of Practice v3.1, Section 4 (BIM Data Representation — IFC+SG), pages 114–171.
• Source link: CORENET X — IFC-SG Glossary of Identified Components ↗
• Related: Space Usage (Others) ↗
• Discipline: ARC · Authorities: BCA, SCDF
• 1 IFC binding(s), 31 parameter(s).

IFC binding breakdown

• IfcSpace — subtypes: SPACE — 31 param(s), table format 6col.

Glossary page split (verified 2026-07-10)

On the live IFC-SG glossary, this component's content is split across two pages under the parent Space component:

The "Others" page intro: "In addition to Occupancy Type and Space Name parameters and values listed earlier, some space components may require additional parameters listed below." — i.e. the other 29 are conditional, applied per space type.

⚑ Required pair (parent Space page)

The parent Space component states: "each space only require 2 'IfcSpace' properties to address their usage requirements: 1) SpaceName 2) Occupancy Type".

• SpaceName ⚑ — values from the Space Usage catalogue page
• OccupancyType ⚑ — the development-part occupancy type (see Semantics of the required pair below), values from the same catalogue

Both are input_limited — pull accepted values from the Space Usage page's lookup tables, not free text.

Semantics of the required pair

The two are not two flavours of the same classification — they answer different questions, and a checker that treats OccupancyType as a room-level label will read the model wrong.

• OccupancyType — the development typology. Each of the 95 values names a building or development type (most page entries open "Applicable for a …") and carries that typology's crosswalk to every authority's project-level classification: SCDF Table 1.4A Purpose Group, BCA Table 2.2A Type of Occupancy, BCA Accessibility Code building type, PUB SSW, NEA. It describes the development, or in a mixed-use development the part of it a space sits in, so every IfcSpace in that part carries the same value.
• SpaceName — the function of the space itself (Bedroom, Kitchen, Operation Theatre).
• Together they resolve the SCDF Functional Space, which is what occupant load is read against (Table 1.4B, Occupant Load Factors). The space-name tables pair each name with one or more functional spaces, and the parenthetical building types inside those strings — Guestroom/ Accommodation Unit - (Capsule Hotel) — are the occupancy type that picks between them. Hence "Note that the OL of Guestroom Space will depend on what is indicated in its Occupancy Type".

Full catalogues and the per-category pairing tables: _reference/space_usage.md / _reference/space_usage.json.

Other input-limited parameters

These accept values from a defined list in the COP source table (not part of the global structural enums); see examples in parameters.json:

• Accreditation_MAS, AmbulantDisabled, BarrierFreeAccessibility, ChildrenFriendly, ElderlyFriendly, EmergencyVoiceCommunicationSystem, FireDetectionAndSuppressionSystem, FireEmergencyVentilationMode, FireExit, FullyCoveredWithTreesShrubs, HearingEnhancement, LargerAccessible, OccupancyType, Retrofit, SmokeControlSystem, SpaceName, StepRampAccess, TwentyFourHourMannedStation, VentilationMode