## 4 Naming Process for Bridge Components
### Basic Bridge Geometric Modeling and Information Reassigning
In this study, the \"Population\" of the generated IPF was compiled using ST-Developer from STEP Tools, Inc. To process multiple PSETs, a \"DO\" loop was applied (Line 2). The _relatedObject_ (Line 3) is the same as _\"RelatedObjects\"_ in Figure 2 and represents the object to which PSET is connected. The _relatedObject_ can be retrieved through the inputted GUID. Lines 7-12 show the steps for creating entities and attributes  
Figure 6: Information reassigning concept for the bridge information modeling. Figure 7: Basic framework for IFC-based bridge information modeling process. of _IfcPropertySet_ and create related information about _IfcProperty_ using Lines 15-23. The generated data are linked with _IfcPropertySet_ via Line 24. The connection between the object and the property shown in Figure 2 is implemented through the createRelationship function, which refers to the creation of a relationship entity (Line 30) and the connection of the object (Lines 32-35) through the assignment of its attributes. ``` Input 1: psetListNode - XML nodes type of Pset_SteelBoxBridgeComponentIdentification property set including name and value data of property. Input 2: GUID of an object - string type Input 3: Population of generated IFC file - schemaParser.Population type Output: Creating the Pset_SteelBoxBridgeComponentIdentification related entities
1 NodeList postListNode
2 do (Node post : end of psets)
3 relatedObject in Figure 2: IFC entity correlated to the GUID
4 psetGuid: new GUID of ifcPropertySet
5 psetName: getting property set name from the pset
7 IfcpropertySet in Figure 2: IfcPropertySet class for inclusion in Population
9 //setting the IfcPropertySet attributes to the Ifcpropertyset class
10 Ifcpropertyset.setGlobal(psetGuid)
11 Ifcpropertyset.setOwnerHistory(getIfcOwnerHistoryInPopulation(ref Population))
12 Ifcpropertyset.setName(psetName)
13 SetIfcproperty: set of IfcProperty in Figure 2
14 NodeList properties: properties included in the pset
15 do (Node property : end of properties)
16 propertyName: getting a property name from the property
17 propertyValue: getting a property value from property

Figure 8: Developed user-interface for generating and managing the semantic information of a bridge component. ### Automated Naming Algorithm for the Identification of Bridge Components

We investigated the method of automatically generating the identifiers for the bridge components for which the semantic information of function and usage has been generated. In this study, the application of the automated identifier generation method was based on the assumption that the information for _Girder_ and _Span_ properties is already included, with regard to the _Assembled Assembly_ and _Parts Assembly_ in Figure 5. Here, the exclusion of the _Structural System_, _Girder_, and _Span_ properties occur because it is likely that the introduction of an automated technique to problems with few elements, such as the classification of a bridge sub/superstructure or abutment/pier, will be inefficient compared with the manual operation. Since the feature-based semantic identification of components in greater detail than _Parts Assembly_ is not within the scope of this study, it was also excluded. The identification information of the bridge components was generated by forming feature sets, as shown in Equation (1). \[OF_{i}=[SP(m),Gd(n),\;Or_{L}(S_{mn}(i))] \tag{1}\]

where \(OF_{i}\) denotes the feature set of object \(i\). \(Gd(n)\) refers to the identifier of the \(n\)th girder and \(Sp(m)\) indicates the identifier of the \(m\)th span. \(Or_{L}(S_{mn}(i))\) is the ordinal information of object \(i\) arranged along the axis of the bridge in the spanwise direction (\(\Upsilon^{\prime}\)-direction). \(S_{mn}\) is defined as shown in Equation (2). \[S_{mn}(i)=\{i|S(Sp(m))\cap S(Gd(n))\} \tag{2}\]

where \(S(Sp(m))\) and \(S(Gd(n))\) are for the \(i\)th object that belongs to \(Sp(m)\) and \(Gd(n)\). Figure 9 shows an example of \(OF_{i}\). Objects that are recurrently arranged, such as a section, are identified using the following rule.