Corpus version: 3.1
License: CC-BY-4.0

CORENET X Notes (official rules & actual values — reference)

Verbatim capture of CORENET X Notes — official-page rules, notes and Actual Values tables not carried by the CoP-derived corpus. Reference only — rules are NOT allowed_values; actual_values record official vocabulary the CoP leaves free-input. Official typos are kept verbatim and flagged [sic]. Gateway/submission-process domain content (Design Gateway/CG/DG, PWCS, parking-provision policy) is deliberately excluded per owner decision.

62 entries across 34 components (30 rule, 28 note, 4 actual_values; 6 borderline).

Beam

rule · scope: component
Multiple beams elements shall be modelled from support to support for beams with continuous spans.

Borehole

rule · scope: component
The SI report for all boreholes shall be included and submitted in PDF & AGS format.
rule · scope: component
The borehole elements shall be modelled as per true coordinates in the IFC+SG structural model with the necessary information required as stipulated in the tables below.

Breeching Inlet

note · scope: component
Besides modelling the individual Breeching Inlet as an individual component, also ensure each Breeching Inlet is exported as part of the Dry Riser, Wet Riser, Foam Sprinkler or Sprinkler System respectively.
note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Building Storey

rule · scope: component
All disciplines must have be aligned in naming and z-value of the building storeys when geo-referencing their models for coordination.
'must have be' is an official grammar error [sic]
rule · scope: component · borderline
Roof level is required to be separately represented as a property to meet URA requirements

Column

rule · scope: component
Column working load is required for 1st storey column only.
rule · scope: component
Multiple columns elements shall be modelled from support to support (storey to storey) for continuous column.

Culvert/ Drains

note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Damper

note · scope: component · borderline
Refer here for fire safety equipment / provisions that need not be modelled in full and can be represented by suitable modelling objects / components.
rule · scope: component
Modelling Damper is voluntary.

Distribution Chamber

rule · scope: property
Depth, TopLevel and InvertLevel shall be accurately provided in the model.
rule · scope: component
Internal dimensions shall be accurately provided in the model.
rule · scope: component
Manhole ID shall be provided for manhole within the model.
note · SystemType (printed "System Type" [sic]) · scope: property
Refer to System for full list of system types that can be provided under "System Type" property.

Door

rule · ClearHeight · scope: property
All the door elements must indicate "ClearHeight" in its properties, to facilitate headroom checks.

Foam Inlet / Outlet

note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Footing / Pilecap

rule · scope: component
All the footing / pilecap elements shall be modelled as independent elements* in IFC+SG model with the necessary information required as stipulated in the tables below.

Grating

note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Green Verges

note · scope: component · borderline
Hence, please ensure that the soil depth shown in the model is at least 2.0m.

Gutter

note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Interceptor

note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Lamp Post

rule · scope: component
Only lamp post within the site boundary will need to be modelled, using placeholder objects. It is not necessary to replicate details of actual lamp posts.

Landscape Plants

rule · Girth · scope: property
Girth value shall be accurately input.

Pile

rule · scope: component
For pile performance-based design, the project team must submit separate sets of IFC+SG models for each distinct pile design parameter.
rule · scope: component
The pile elements shall be modelled as per true coordinates in the IFC+SG model with the necessary information required as stipulated in the tables below.

Pipes/ Ducts

note · scope: component
Sanitary drain-lines are to be submitted as schematic and/or 2D drawings. If industry would like to submit in 3D, it is optional and will also be accepted.
rule · scope: property
InnerDiameter, NominalDiameter and Thickness of Pipes shall be accurately provided.
rule · scope: component
Pipe size, location and gradient shall be accurately modelled.
note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Planting Areas

note · scope: component · borderline
Hence, please ensure that the soil depth shown in the model is at least 2.0m.

Prefabricated Building Systems and MEP Components

note · scope: component
Every element in the M&E system in the BIM models can be identified via a unique system name with a system classification based on the two key parameters "SystemName" and "SystemType".
note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Project Development Type

rule · ProjectDevelopmentType · scope: model
Only one Project Development Type property applies to the entire IFC model

Pump

note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Sanitary Appliances

note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Seating

note · scope: component · borderline
To determine Occupancy Load for Assembly Spaces (e.g. Auditorium, Theatre), it is necessary to indicate the type of seating

Space

rule · scope: model · borderline
AVF_IncludeAsGFA must be checked for all areas that are proposed to be included as GFA and AGF_DevelopmentUse must be keyed in for all areas in relation to GFA evaluation.
rule · scope: model
They shall be exported to Space with IFC Sub-type "AREA_GFA".

Space (Area Requirements)

rule · scope: property
Below recommended values for AGF_Names sorted based on their associated development use. These values shall be used as much as possible before alternatives are considered.
actual_values · ALS_GreeneryFeatures · scope: property
Green Buffer; Peripheral Planting Verge; Landscape Deck - Vertical Greenery; Landscape Deck - Surface Greenery; Communal Ground Garden; Sky Terrace; Roof Top Landscaping; Ground Landscaping; Urban Farm / Greenhouse; Vertical Greenery; Extensive Green Roof; Green Verge
actual_values · ALS_LandscapeType · scope: property
Turfing; Groundcovers; Shrubs; Decked / Patterened Floor; Water Feature; Landscaped Footpath; Playground; BBQ Pit
'Decked / Patterened Floor' is an official typo for 'Patterned' [sic]; the 'Shrubs' value carries footnote 1 (see the note entry).
note · ALS_LandscapeType · scope: property
Note that Shurbs will include both within Site Boundary and outside Site Boundary (in Green Verge)
'Shurbs' is an official typo for 'Shrubs' [sic]; footnote 1 annotating the ALS_LandscapeType 'Shrubs' value.
actual_values · ALS_Species · scope: property
Ophiopogon jaburan (Example); Codiaeum variegatum (Example); Dracaena marginata (Example); Murraya paniculata (Example)
example-only — each value is tagged '(Example)' on the page; not a closed list.
actual_values · AVF_IncludeAsGFA · scope: property
Yes; No
the page states the type as '[Booelan]' [sic] (Boolean) and renders the values as a single 'Yes / No' cell; the corpus renders Booleans as TRUE / FALSE — discrepancy recorded in crosscheck.

Space (Usage)

note · scope: component
For toilet or shower clusters, accessible toilet or shower cubicles shall be modelled as a separate space from the rest of the toilet clusters.
rule · scope: component
*** All Ramp Spaces must include modelling of ramp components (IfcRamp).
rule · scope: component
Every space in the development shall be modelled and tagged as a space in the BIM model.
rule · scope: component
The space shall start from dominant FFL of the space or lowest FFL.
rule · scope: component
Every space component should include inputs for both Occupancy Type and Space Name parameters.
rule · scope: component
Spaces across BCA, LTA, NEA, PUB, and SCDF have been harmonized and standardized for checks into Occupancy Types and Space Name categories.
rule · scope: component
Thus, all Spaces should be accompanied by both Space Name and Occupancy Type parameters.

Sprinkler (Non-Fire; For NEA)

note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

System

note · scope: component
The Foam Fire Extinguishing System should include Foam Inlet and Foam Outlet components.
note · scope: component
The Foam Sprinkler System and Sprinkler System should include Breeching Inlet components.
note · scope: component
The Wet Riser System and Dry Riser System should include Breeching Inlet and Landing Valve components.

Valve

note · scope: component
Ensure the Landing Valve is also exported as part of the Wet Riser System and Dry Riser System
note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Wall

rule · scope: component
Multiple wall elements shall be modelled from storey to storey for continuous wall.

Waste Terminal

note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.

Water Meter

note · SystemType · scope: property
Refer to System for full list of system types that can be provided under "SystemType" property.