## 5 Verification of the Proposed Methodology through the Railway Track Modeling
Figure 10a shows that \"\(x\)-angle\", \"\(y\)-angle\", and \"\(z\)-angle\", which are rotation parameters, were included in the \"Dimensions\" attribute information of the sleepers, with the values of \(-0.212^{\circ}\), \(13.493^{\circ}\), and \(137.056^{\circ}\), respectively. Figure 10b,c show that the \(z\)-angle and \(y\)-angle, which are the attribute values for the presented rotation, are also reflected in the geometry of the information model, with values of \(137.056^{\circ}\) and \(13.493^{\circ}\), respectively. The attribute information referred to as \"PBScode\" was additionally created to identify objects during the creation of the extended IFC-based information model based on the methodology proposed in Section 4.2. Figure 11a-c depict that \"sleepers\" included \"BA202\", whereas \"ballasts\" and \"rails\" included \"BA301\" and \"BA101\". The classification codes are shown in Table 1. The attribute information of the extended IFC entities was defined using the developed module described in Section 3.2. For example, \"PredefinedType\" and \"FunctionType\" (the attributes in \"IfcTrackSleeper\" that represent the sleepers) were defined as \"WOODENSLEPER\" and \"MonoBLOCK\", respectively. \"PredefinedType\", \"TrackGauge\", and \"Slack\", which are the attribute information in \"IfcTrackPart\", were defined as \"MAINTRACK\", \"1500\", and \"0\", respectively. The design information not included in the attributes of the extended IFC entities was represented by adding properties. For example, \"TechnicalStandard\", representing the design standard, was added to the sleeper model, with its value set to \"KS\", as indicated by Figure 11d. Under spatial information, \"Track_9-11 km\" was created as an \"IfcTrack\" element under \"IfcSite\". \"Station1\" and \"Station3\", which are earthwork sections, as well as \"Station2\", which is a bridge section, were created as \"IfcTrackPart\" elements under \"Track_9-11\", in accordance with the aims of this study. Figure 10: An example of the information model of discontinuous objects: (**a**) Properties of a sleeper; (**b**) model in the xy-plane; and (**c**) model in the xz-plane. Table 3 presents a part of the model created based on the extended IFC using the methodology presented in Section 3. In the case of the \"Sleeper-#2195949\" object, the physical information was represented using \"IfcTrackSleeper(#2195949)\". \"PredefinedType\" and \"FunctionType\", which are attributes of the physical entities, were defined as \"WOODENSLEEPER\" and \"MONOBLOCK\", respectively, as mentioned above. The geometric information of \"Sleeper-#2195949\" was represented using \"IfcProductDefinitionShape(#870446)\". Additionally, \"IfcTrackSleeper(#2195949)\" was combined with \"IfcTrackPart(#2199347)\", which represents \"Station1\" through \"IfcRelContainedInSpatial Structure(#11)\". In this instance, \"PredefinedType\", \"TrackGauge\", and \"Slack\", which are attributes in the spatial entities of \"Station1\", were defined as \"MAINTRACK\", \"1500\", and \"0.0\", respectively, as previously mentioned. \"#2199347\", which represents \"Station1\", was combined with \"IfcTrack(#10)\", which represents \"Track_9-11 km\", using \"IfcRelAggregates(#2172040)\". Moreover, \"Track_9-11 km\" was combined with \"IfcSite(#2172046)\", which represents the entire space of the information model, using \"IfcRelAggregates(#2172039)\". \"Identity Data (Type)\", which was integrated in the modeling process, was represented as \"IfcPropertySet(#2172105)\" and was combined with \"IfcTrackSleeper(#2195949)\" using \"IfcRelDefinesByProperties(#542197)\". \"Identity Data (Type)\"--an attribute set--was connected to \"IfcPropertySingleValue(#2199441)\", which represents the attribute  
Figure 11: Railway track model in Autodesk Revit. (**a**) PBScode of sleeper; (**b**) PBScode of rail; (**c**) PBScode of ballast; and (**d**) An example of the information of sleeper. \"Type\", and its value was created as \"Wood\". Moreover, the alignment information was represented using \"IFCAligment(#2785901)\".