Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.
21 C h a p t e r 5 With the 3-D model and schema defined, a proof-of-concept pilot demonstration of the 3-D model was executed using site information from an existing Virginia Department of Trans- portation (VDOT) project on Gallows Road in Fairfax County. The proof-of-concept system consisted of the spatial repos- itory, containing multiple features modeling utility infrastruc- ture (such as potable water, sanitary sewer, storm sewer, electric, gas, or telecommunications infrastructure). The sys- tem was designed to employ the unifying technology of a spa- tially enabled document management system that serves as the staging repository for all project documentation and design models, including 3-D models, 2-D CAD files, specifi- cations, image-based documents, and any other types of data required for a description of the project site. Although software products from other vendors (includ- ing Autodesk, Trimble, and Intergraph) could have been used, the project team decided to use a Bentley suite of software products for the proof-of-concept pilot demonstration. Bent- ley products are commonly used by state transportation agencies for highway-design work. The design team conducted a thorough analysis and review of legacy data associated with a recently completed VDOT project area at the interchange of Route 29 and Gallows Road in Northern Virginia. Before the proof-of-concept and pilot system development, many discussions were held with VDOT staff to understand the data creation process, accuracy, and new utility location techniques using RFID ball markers. A number of discussions addressed the needs of engineers who deal with the many legacy data types during the design phase of projects and the challenges they face in locating and retriev- ing content for their projects. As a result of these discussions and analysis, the pilot team assembled a notional workflow for the proof-of-concept dem- onstration that included five major activities. These activities are representational and may or may not correspond to the actual utility practice at a state DOT. Figure 5.1 presents the five major activities that would be tested during the pilot. System and process Architectural Diagram Overview The server environment is designed to manage the 3-D Utility Data Model and all supporting engineering content (see Fig- ure 5.2). Oracle Database 11g Release 2 (11g R2) was used for storing the 3-D Utility Data Model. Bentley Geo Web Pub- lisher allows for a live view of the data model from a web map- ping perspective. Bentley ProjectWise Geospatial Server manages the project and engineering-based content that is not stored within the database. A desktop or thick client environment contains tools for editing, reviewing, and managing the 3-D Utility Data Model throughout the project life cycle and engineering workflows. Web clients can also take advantage of the mapping view of the 3-D Utility Data Model for project and engineering plan- ning and review. Software Loading Procedures On the servers, Oracle 11g R2 was first installed on a Windows 2008 R2 virtual server. Installation was accomplished by using standard out-of-the box procedures to ensure a compliant installation. The 3-D utility data repository was reproduced in the empty Oracle database using the methods discussed in the Chapter 4 section Reproducing the Prototype 3-D Utility Data Repository. Once the 3-D data repository was reproduced, the next step was to create tablespace, called GTIGIS to match the pro- totype environment. This can be accomplished in Oracle SQL*Plus using CREATE TABLESPACE as follows, adjusting the DATAFILE, SIZE, and other parameters as needed: CREATE TABLESPACE GTIGIS DATAFILE âD:\Oracle\shrp2. dbfâ SIZE 100M AUTOEXTEND ON; To take full advantage of spatial capabilities, while support- ing 3-D geometry to and from engineering environments, a Proof-of-Concept Pilot Demonstration
22 Figure 5.1. Diagram of five activities tested in the pilot program. Source: Bentley Systems. Figure 5.2. Architectural overview.
23 custom compound coordinate system was used for the pilot project area. This compound coordinate system combines a geographic 2-D coordinate system, NAD83(HARN)/Virginia North (ftUS), with a standard Oracle gravity-related height coordinate system. The resulting coordinate system was given a Spatial Reference System Identifier (SRID) of 9989. Before importing the prototype exports, create the compound coor- dinate system reference in Oracle Spatial from Oracle SQL*Plus using the following script (line breaks are added here for clarity): INSERT INTO MDSYS.SDO_COORD_REF_SYSTEM ( SRID, COORD_REF_SYS_NAME, COORD_REF_SYS_KIND, COORD_SYS_ID, DATUM_ID, SOURCE_GEOG_SRID, PROJECTION_CONV_ID, CMPD_HORIZ_SRID, CMPD_VERT_SRID, INFORMATION_SOURCE, DATA_SOURCE, IS_LEGACY, LEGACY_CODE, LEGACY_WKTEXT, LEGACY_CS_BOUNDS) VALUES ( 9989, âNAD83(HARN) / Virginia North (ftUS)â, âCOMPOUNDâ, NULL, NULL, NULL, NULL, 2924, 5701, NULL, âEPSGâ, âFALSEâ, NULL, NULL, NULL); Once the 3-D utility database loaded in Oracle Spatial has the necessary tablespace and coordinate system, the data dump export can be loaded. From a command prompt, run the following: impdp system/password@dbservice SCHEMAS=GIS DIRECTORY=data_pump_dir DUMPFILE=shrp2_export .dmp TABLE_EXISTS_ACTION=REPLACE LOGFILE=shrp2_ import.log Replace password with your Oracle system account password, and replace dbservice with the destination service name. Once the import operation is complete, the final database tables and supporting objects are now in place. Bentley ProjectWise Geospatial Integration Server SS4 was installed on a separate Windows 2008 R2 server. The installation of Bentley ProjectWise followed out-of-the box procedures, ensuring a standard compliant installation. Bentley Geo Web Publisher V8i SS4 was installed on a third Windows 2008 R2 virtual server. Though the tools used for this projectâs purposes were Bentley software tools, another vendorâs products having highway-design capabilities (such as those of Autodesk, Trimble, or Intergraph) can be substituted. On the desktop clients, several pieces of software were installed to properly manage the 3-D Utility Data Model. To edit the model, the latest release of Bentley Power InRoads V8i SS3 and a soon-to-be released version of Bentleyâs Sub- surface Utilities Design and Analysis were included. Again, other leading highway-design software vendorâs products can be used for the processes conducted in the pilot. To manage the modelâs supporting engineering content, Bentley ProjectWise Geospatial Explorer V8i SS4 was also installed. Internet Explorer, with the Bentley Geo Web Pub- lisher ActiveX control, was used to view the model from a planning/web perspective. In summary, ⢠Content management solution: Spatially enabled docu- ment management system (Bentley ProjectWise Geo spatial Server). ⢠Content manipulation solution: 3-D highway-design CAD software (Bentley Power InRoads Subsurface Utilities Design and Analysis). ⢠Content review solution: Web-based geospatial viewer plugin (Internet Explorer with Bentley Geo Web Publisher). Working with the Model The 3-D Utility Data Model was housed within an Oracle Spatial database that supports 3-D storage of points, lines, and polygons. Bentley OpenRoads 3-D civil platform was connected to the modelâs specialized application layer for 3-D modeling in which the working set of utility objects can be manipulated (individual instances created, updated, deleted, and inspected) with civil design tools and then posted back into the repository (see Figure 5.3). 3-D Model Testing Procedures The first step was to load the legacy data into a content man- agement solution, ensuring that all relevant project content was available. All content that is loaded, whether it is an Adobe PDF, Microsoft Word document, or any other format, can be associated with geospatial locations. This step is necessary to
24 ensure that all of the available data are properly staged and managed for processing into the 3-D model. Any document management system that can be enabled with spatial indexing is suitable for this task. Document management systems with- out spatial indexing can also be used provided a suitable set of indexes is applied to the documents that are stored and the system supports a state management process, such as revision control or release management. Figure 5.4 shows not only the folder location of a source marker ball PDF but also the geospatial location of that file and a preview of its contents. The second step was to build the intelligent 3-D model (i.e., the spatial database with the individual feature defini- tions and properties that give the features intelligence). Once all the content was loaded into the content management solu- tion, a 3-D design tool, Bentley Power InRoads, was used to model the site in 3-D. Other CAD vendor packages are capa- ble of similar editing functions and can be configured to cre- ate the same 3-D CAD vector model. The final step was to use a Bentley product called ModelBuilder to create and store the spatial 3-D database from our intelligent 3-D design. ModelBuilder is capable of creating a 3-D representation of a CAD feature and storing it in a spatial database as 3-D point and line geometry. In the SHRP 2 project, each feature carries along with it the model intelligence (a collection of properties or feature attri- butes) to define an SDSFIE feature and enough information to allow the reconstruction of the 3-D CAD feature when the data are checked out by Bentleyâs CAD products for 3-D editing. Other vendorsâ CAD products can be configured to store their geometry in Oracle Spatial or any other database management system (DBMS) product with the proper spatial extensions applied. IBM Informix, IBM DB2 Spatial Extender, and PostgreSQL/SDE are all products that have capabilities to sup- port this environment. Files that provide the means to create the modified SDSFIE model that the project was built on are avail- able at http://www.trb.org/Main/Blurbs/171927.aspx. DOTs wishing to use this technology with other CAD vendorsâ soft- ware should verify that the software can store 3-D CAD data in a spatial DBMS. In addition, the CAD vendorsâ design software must be capable of augmenting the 3-D model with the needed rendering constructs and other information required to recon- struct the 3-D CAD utility feature once it is checked out for editing from the DBMS with spatial extensions. When all the site data were loaded, they were verified with the Internet Explorer Web Mapping tool. The screenshot in Figure 5.5 shows the software building the 3-D features and storing them in the 3-D spatial relational DBMS system (Oracle Spatial). Figure 5.6 represents a 3-D design-ready civil model extracted from the spatial database. This model functions with all the standard Bentley Power InRoads civil design tools. Also used for this project is Bentleyâs Geo Web Publisher, which is driven by Bentley Map, and has been used to verify that the 3-D Utility Data Model can be leveraged using an available commercial database-neutral publishing application. Figure 5.7 presents a web mapping view of this same model from the previous image. The model can be viewed, queried, or edited within either environment. With the entire project intersection now residing in the 3-D storage environment, a typical workflow is demonstrated in Figures 5.8 and 5.9, showing changes to the gas utility system. The example workflow is the extension of gas service to a local restaurant that occurred during the DOT construction Figure 5.3. 3-D model workflow.
25 phase of the project. This utility work was part of the Gallows RoadâRoute 29 VDOT project. In Figure 5.8, the area high- lighted in white shows the existing gas service and its length. Bentley ModelBuilder was used to create a new design model in the area of interest. The Bentley Power InRoads 3-D mod- eling tool was then used to add the extension to the gas ser- vice. Figure 5.9 shows the service extension in both 2-D and 3-D. Note the joint on the 3-D rendering showing the start of the gas service extension. Bentley ModelBuilder was used again to upload the 3-D design changes back into the 3-D Utility Data Model. Throughout the life cycle of the project, the project infor- mation and tracking capabilities of the content management solution proved valuable for controlling information input into the 3-D model. Figure 5.10 shows the various project documents that were converted to build the initial 3-D utility model and the information that can be tracked for status and conversion process control. Figure 5.11 depicts permits at various project locations. Note the different fill patterns showing the status of the per- mit. The representation of these permits overlaid on the utility infrastructure clearly defines areas where change has or will take place and provides a powerful tool for understanding and managing updates to the 3-D infrastructure. All 2-D represen- tations defining permits, DOT project extents, and other proj- ect administrative constructs are stored in the same spatial storage system (DBMS) as the 3-D utility data. A single con- nection to this unified environment yields data for both future design and the change management processes required to maintain an accurate 3-D utility model. Updates from Third-Party As-Built Drawings The next example demonstrates the inclusion of data sup- plied by a third party into the existing 3-D utility model of the Gallows RoadâRoute 29 project area. The example assumes that a new DWG civil design for a telecom line was submitted to a DOT operations group, responsible for utility model maintenance of a DOT project area. The example also assumes that the DOT project was completed and the 3-D model represented the final as-built condition. As a result, the content management solution sends an automated e-mail, instructing the DOT designer in the operations group to Figure 5.4. Folder hierarchy and 3-D model screenshot.
26 Figure 5.5. 3-D features and storage.
27 Figure 5.6. 3-D civil model (Bentley OpenRoads).
28 Figure 5.7. Web mapping view.
29 Service Extension Figure 5.8. Modifying elements of the model: A.
30 Gas Service Figure 5.9. Modifying elements of the model: B.
31 Figure 5.10. Illustration of document storage.
32 Figure 5.11. Illustration of permits.
33 Figure 5.12. Third-party data Step 1. review the new telecom line and then post the changes into the master 3-D Utility Data Model (see Figure 5.12). The designer uses Bentley Power InRoads to bring the DWG design file into the master 3-D design session (see Figure 5.13). The designer then incorporates the new civil design changes into the master 3-D Utility Data Model, posts those changes to the master 3-D Utility Data Model, and finalizes the state of the permit so that all interested parties know it is complete (see Figures 5.14 and 5.15). The permit colors change (see Figure 5.16) to show the update to the model was completed from within the content management solution, providing a clear point of project review for management (see Figure 5.17). Using the 3-D Utility Data Model for Interactive Design As part of the research, the addition of new utility objects into the 3-D Utility Data Model using conflict detection and advanced 3-D editing functions was also developed and dem- onstrated. The demonstrations once again used Bentley Power InRoads and ModelBuilder to show the various steps per- formed. The workflow was built from a new permit, adding a new gas main into an existing building. In Step 1, the new gas line is sited according to the permit requirements (see Figure 5.18). In Step 2, the 3-D civil intelligence is added to the gas line (see Figure 5.19). Step 3 verifies whether the new gas line meets clearance requirements (see Figure 5.20). In Step 4, the new gas line is adjusted by editing the profile view dynamically (see Figure 5.21). Step 5 verifies that the 3-D Utility Data Model compliant attributes are properly filled in (see Figure 5.22). These are mandatory attributes or properties that, at a minimum, are required to fully define an intelligent feature. Compliance is specified so that the features can consistently provide infor- mation about themselves. A property or attribute is often defined as mandatory or compliant so that a function can run against a collection of elements without fear that the system cannot be processed because a single linking property is miss- ing. Good examples are a switch or a fuse, or a gas or water
34 Figure 5.14. Third-party data Step 3. Figure 5.13. Third-party data Step 2.
35 Figure 5.15. Third-party data Step 4. Figure 5.16. Third-party data Step 5.
36 Figure 5.17. Third-party data Step 6. Figure 5.18. Interactive design Step 1. valve. Each has an operational property that is mandatory and that is its state. The fuse, valve, or switch must have a state. The state must be open or closed. The switch state can- not be null; a software trace will fail at each device that is null (not defined). These intelligent components must be opened or closed if their behavior is binary. Some valves may throttle, so their state can be open, closed, or some percentage of openâbut never null. Use the Bentley Power InRoads ModelBuilder to upload the changes from the design file to the 3-D Utility Data Model, and save the design file back into the content manage- ment repository for later retrieval (see Figure 5.23). Finally, in Step 7, the changes are reviewed through the con- tent management web viewer to verify that the graphics and the data that were written with the Bentley Power InRoads design application into the 3-D Utility Data Model have gone through (see Figure 5.24).
37 Figure 5.19. Interactive design Step 2. Figure 5.20. Interactive design Step 3.
38 Figure 5.21. Interactive design Step 4.
39 Figure 5.22. Interactive design Step 5.
40 Figure 5.23. Interactive design Step 6. Figure 5.24. Interactive design Step 7.
