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.
13 FUNCTIONAL AREA DEFINITION The planning functional area is primarily responsible for project initiation and feasibility study as well as collecting data for the design functional area for decision making. Daniel Streett of the New York State DOT describes its functional area as a pre-design unit that collects data for the development of project alternatives. PLANNING FUNCTION DELIVERABLES Responses to the survey questionnaire revealed the deliver- able types or datasets shown in Table 2 as being received, processed, or sent through the planning functional area. Responses are indicated by two numbers: response count followed by percentage of total responses for the functional area. For example, according to Table 2, 18 agencies reported receiving location survey data, 15 agencies reported that they process or generate (originate) these data, and 15 agencies reported that these data are transferred to another functional area for use. Also included in the responses shown in Table 2 are responses inserted into the surveyâs open-ended text boxes titled as âOtherâ indicating additional information/data received, processed, generated, or sent from the planning functional area. The questionnaire is included for review in Appendix A, and tabulated results of the survey are available in Appendix B. ADVANCED PROCESSES The advanced processes defined for the planning functional area are derived from both literature review and case studies. In this initial project stage, both of the DOT planning func- tions that were studied developed the process of creating three-dimensional (3D) terrain models of the project site. This not only sets the stage for addition of the 3D design model in the successive functional area, but also is used in the creation of a digital terrain model (DTM) for eventually sharing with the contractor. The contractor benefits by the ability to incorporate global positioning system (GPS)-enabled earth-moving operations. In addition, GPS software and hardware, along with inter- operable software, hastens the early development of the 3D model by creation of the DTM with fewer human resources than previously required for surveying. The New York State DOT (NYSDOT) performs a best practice in this functional area by creating a 3D terrain model of the projectâs surface. This practice is efficient because it serves two main purposes that reduce input procedures and efforts internally, externally, and across the projectâs life cycle. ⢠Internally: The 3D terrain model is passed to the design functional area where the balance of the projectâs design is implemented (added to). This reduces redundant data extraction from the terrain model into additional itera- tions of computer-aided design (CAD) files (only layers are added). ⢠Externally: The 3D terrain model is eventually shared with the contractor, allowing them to perform jobsite layout functions electronically and allowing the con- tractor to produce its own set of cross sections. This reduces DOT resources required to plot and print cross- section plans. Resources are saved on the contractorâs side because it can utilize the 3D terrain model for GPS layout and machine grading control. ⢠Life cycle: The 3D terrain model acts as the shell for a 3D design model that can follow the projectâs life-cycle stages acting as an information repository (allowing input and extraction of data throughout the projectâs life). Case Study #1 NYSDOT ⢠Work-Flow Process Diagram. Figure 6 displays a data work-flow diagram as communicated from the NYSDOT case study. ⢠Software Applications Utilized. Table 3 displays the software applications and data formats extracted from the IDEF0 diagram for the NYSDOT planning func- tional area. ⢠Hardware and Networks. A continuously operating ref- erence station (CORS) network is required to carry and measure GPS signals for verification and creation of survey markers. ⢠Challenges and Process Adjustments. CHAPTER THREE INFORMATION TECHNOLOGY FOR PLANNING
NYSDOT reported difficulty with interfacing the software applications Bentley Microstation and ESRI GIS (geographic information system). Case Study #2 Kentucky Transportation Cabinet ⢠Work-Flow Process Diagram. Figure 7 shows a data work-flow diagram for a planning functional area (source: Case Study KYTC). 14 ⢠The KYTC planning function work-flow process is shown in Figure 7 as a contrast. Advanced processes internally include Extensible Markup Language (XML) that is used whenever possible for data export and import between software applications. ⢠Software Applications Utilized. Table 4 displays the software applications and data formats extracted from the IDEF0 diagram for KYTC planning functional area. ⢠Hardware and Networks. Linux and Microsoft Win- dows 2003 Server networks are utilized. ⢠Challenges and Process Adjustments. KYTC reported the following challenges in the planning functional area: â Traffic data printed from mainframe computer not easily accessed or analyzed. â An increase in network security that often restricts access to needed data. â In-house personnel who have limited software skills. â Processing time for statewide traffic models that appears excessive. â An interoperability between software applications. â Inconsistencies with the overall systems graphical user interface (GUI). Application Software Application-Vendor Data File Formats ROW Mapping InRoadsâBentley Open CL Control InRoadsâBentley Open Transition Control InRoadsâBentley Open Surface Layer Elevations InRoadsâBentley Open DTM Features InRoadsâBentley GEOPAKâBentley Open GIS ArcViewâESRI Proprietary/Open File Storage ProjectWiseâBentley Proprietary CAD MicroStationâBentley Proprietary Operations/Maintenance Asset Inventory M/AMSâAASHTO Open TABLE 3 SOFTWARE APPLICATIONS AND DATA FORMATS USED BY NYSDOT PLANNING FUNCTIONAL AREA FIGURE 6 NYSDOT data work-flow diagram for planning functional area. Data Type Receive Process/Generate Send Location 18â78% 15â65% 15â65% Traffic 17â74% 20â87% 14â61% Environmental 14â61% 12â52% 13â57% Survey 11â48% 9â39% 7â30% Other Data: Roadway Characteristic 1â4% 1â4% Materials Information 1â4% 1â4% Pavement Management 1â4% 1â4% 1â4% Pavement Survey 1â4% 1â4% 1â4% Highway Features 1â4% Highway Centerline 1â4% 1â4% 1â4% From Outside Agencies 1â4% 1â4% TABLE 2 DATA RECEIVED, PROCESSED/GENERATED, SENT FROM DOT PLANNING FUNCTIONAL AREAS
15 FIGURE 7 KYTC data work-flow diagram for planning functional area.
16 Application Software Application-Vendor Data File Formats Infrastructure Asset ManagementâGIS Map Layers HIS-EXOR Corp. Oracle HighwaysâOracle Proprietary/Open Spreadsheet ExcelâMicrosoft Proprietary Desktop Database AccessâMicrosoft Proprietary GIS ArcGISâESRI Proprietary File Management InternalâKYTC Open Historical Estimating Bidhistory.comâHCSS Proprietary CAD TransCADâCaliper Corp. Proprietary CAD MicrostationâBentley Open Document Management Adobe ProfessionalâAdobe Proprietary Engineering/Economic Analysis HERSâSTâFHWA Open Highway Performance Monitoring System HPMSâFHWA Proprietary Text Documents WordâMicrosoft Proprietary TABLE 4 SOFTWARE APPLICATIONS AND DATA FORMATS USED BY KYTC PLANNING FUNCTIONAL AREA