1. Oct. 14 2015

2. Need for spatial hierarchy (what relevance do spatial concepts have in your domain and do they align with the current IFC spatial hierarchy?)

5. Road Spatial Parts (Current) 1.Road Spatial Parts extended IfcCivilSpatialStructureElement_K that represent structures and IfcCivilSpatialBoundary_K that defines conceptual space of road 2.IfcCivilSpatialBoundary_K is divided into vertical sub space, linear reference space, and curvilinear node space 3.IDM is specified spatial elements and expressed requirement information for road spatial definition. Exchange Requirements

6. Need for IFC concepts (what are the major concepts that differ significantly from the existing building concepts in IFC?) IFC4 Road Expansion Count 비고 EntityEntities+ 64 26 object entity including Bridge, Tunnel TypeEnumeration types + 45 (13 bridge, tunnel type) Total 294 type enumeration extension including bridge and tunnel (140 type enumeration), these enum. Have been added on existing IFC4 MaterialMaterial Part+11 8 – IfcConstructionMaterialResourceTypeEnum – ASPHALT etc. 12 – IfcEarthworkMaterialResourceTypeEnum – GRAVEL etc. Attribute and Property Attribute + 37 (13 bridge, tunnel type) New PredefinedType Addition PropertySet+70 Road, structure, drainage, subsidiary, space Property+ 476 Detailed properties for each entity 1. The IFC schema is defined into road structure, drainage, subsidiary facilities, earthwork, component and parts, material, road space. 2. The IFC schema is defined entities and their types (type enumeration) as physical shape elements, and is structured with hierarchical system. 3. Road spatial part is defined as conceptual road space elements. 4. General design elements for each entity are defined with Pset-Common. We are configuration properties related to QTO process for case study project.

7. Shared Road Elements Shared Civil Service Elements Shared Civil Earthwork Elements Need for demarcation(which concepts do you expect to use from other domains and/or extension?) New Domain? Road Material Parts Extended Spatial Parts Extended Road Component Parts Extended Newly Suggested 1. Shared Road Elements: - Road structure 2. Shared Civil Service Elements: - Road drainage, subsidiary, parts 3. Shared Civil Earthwork Elements: - Earthwork parts (Terrain) 1.3 new Shared Element addition to existing Interoperability Layer 2.Extension of Share Component Elements as road component and parts 3.Extension of Core Layer(Product Extension) for road space 4.Domain Layer (Construction Management Domain) extension for road materials 5.Definition of new domain is required. 1.Overlapping area with existing architectural elements utilizes current architectural entities such as pipe, footing, slab, and wall etc. 2.In case that new detailed types are required, such types are added under existing entity (Ex: Slab Type – Invert Material Resource Extension

8. Need to use object type libraries(what do you see as the role of object type libraries in your domain; have you considered how to use the bsDD in your domain?) 1. IfcRoad schema is representing entities and physical road objects types. 2. Road Object has a hierarchy structure. 3. Standardized and generalized object names in English needs to be discussed again in the perspective of bsDD Object type library? - BIM Library object type? - type entity with enumeration?

9. Are there any other integration issues that emerged from the work carried so far within your domain? We have been trying to do our best to integrate with GIS in terms of CityGML and IFC4, but since it is not easy to do that, we provisionally hold off. If necessary for GIS integration, GIS + BIM integration issue can be considered by ontology concept with RDF.