## 4 Case Study
### Multi-Scale Information Collaborative Management in Xiong'an New District
#### 4.1.1 Micro-Meso Information Collaborative Management  
* Format uniformity  
In terms of model file formats, different software tools are used in different engineering industries, resulting in different model file formats being delivered. The planning and construction of Xiong'an New District cover 15 subsectors, including planning, construction, transportation, rail transit, water supply and drainage, gas, heat, electricity, sanitation, a comprehensive pipe corridor, communication, garden, wetland, woodland, and water conservancy. This basically realizes the full coverage of all individual projects in the new district space. Therefore, a variety of BIM software tools are needed to create models in the application process of BIM. The XDB format, serving as a universal data standard exchange format, demonstrates remarkable compatibility with a diverse range of BIM software models prevalently utilized in disparate fields such as architecture and municipal engineering. This compatibility empowers the seamless integration and effortless spanning of file formats across multiple BIM software platforms, thereby facilitating the harmonization and coordination of model information management. In the application practice of Xiong'an New District, common information model format files such as RVT, DGN, and PLN in different industries are uniformly converted into XDB format (a general data standard exchange format) through format conversion plug-in tools, as shown in Figures 17 and 18. By unifying various BIM software model formats in many fields such as architecture and municipal administration, Xiong'an New District has realized the spanning of file formats among multiple BIM software. After the different BIM software model formats are transformed and unified, they can be classified and stored in the information model finished product repository of the corresponding construction unit, so as to provide a convenient way for the construction unit to unify and coordinate the management of each individual project model information. reduced to 29. In addition, XDB files take JSON as the core, which is very efficient in writing, transmission, and parsing. The data stored in this format can be compressed to save the bandwidth cost caused by the transmission model, so as to realize the lightweight processing of the information model. The result of lightweighting is shown in Figure 19.  
* Standard Unification  
In terms of data standards, the Planning and Construction Bureau of the Xiong'an New Area Management Committee issued the BIM data object encoding technical guidelines. In addition, Xiong'an Group has compiled and published the \"BIM Technical Standards for Construction Projects of Xiong'an Group of China\" based on national industry standards and local standards of the Planning and Construction Bureau of the Xiong'an New Area. This standard covers BIM technology standards in various fields, including architecture, municipal engineering, transportation, gardening, and water conservancy, and provides a unified specification for professional codes and component coding systems. In general building construction projects, the model element classification and coding rules for civil engineering objects used in the Xiong'an Park Main Venue project are shown in Figure 20. In this way, the coding standard of the model is unified, and the model elements are connected with the data coding system. After assigning model component codes under the same data coding standard system, the construction unit can extract its required control data from the model database according to its needs. By embedding the Xiong'an New Area calculation translation rules into the XDB plug-in, the plug-in is able to extract, calculate and translate the required control data indicators when exporting data to a.xdb file in Revit. An example of the M&C data results required by the construction unit obtained from the Xiong'an Park Main Venue project is shown in Figure 21.  
Figure 19: Model file lightweighting.