TransXML: XML Schemas for Exchange of Transportation Data (2007) / Chapter Skim
Currently Skimming:
Pages 21-30
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 21... ...
This in turn depends on the ease of getting consensus on a standard data structure, the business case that can be made for the schema, the incentives and disincentives for adoption across the stakeholder community, and the level of advocacy and assistance that is provided to overcome initial barriers to adoption. Therefore, poor candidates for XML schema have the following characteristics: • There is wide variation in data content across agencies and no mandates or incentives to standardize the data; • Information is shared across a small number of identifiable systems or individuals, mechanisms for data transfer are already in place and functioning well, and it would be costly to retool systems to read/write another format; • The structure of data content is highly dynamic in nature and therefore a schema could be obsolete by the time it is put into practice; • The data content is highly detailed and expression in the verbose XML format would result in performance problems for the intended applications; and/or • The data content is so simple or trivial that it is not worth the effort to pursue XML encoding.
|
From page 22... ...
The following subprocesses emerged as candidates for XML schema: • Sharing of roadway geometric design information (horizontal and vertical alignments, pavement section, superelevation, cross sections, geometrics) across design team members as it evolves throughout the design process; • Utilizing information produced in the design phase as the basis for developing as-built information from the construction phase, and then making the as-built information available for use during the maintenance and operation phase; • Sharing of surface models across design, survey and construction, including use of this information for automated machine control; • Transferring pay item information in the design phase for further development in the construction phase; and • Transferring GIS-based planning information on area features into CAD-based design software.
|
From page 23... ...
. The information being exchanged includes the standard contract pay items with their units of measure, and the quantities of each that will be used on this project.
|
From page 24... ...
The model and resultant XML schema developed here were further augmented within the construction business area in support of pay item data exchange for construction phase activities. The aecXML infrastructure break out was done under the IAI aecXML Domain Committee umbrella, but it was largely an independent effort by the aecXML Infrastructure Working Group.
|
From page 25... ...
These processes are listed below roughly in chronological order based on the life cycle of a construction project: • Acquire reference information for project cost estimates; • Submit project definition of work to oversight institution; • Bid package preparation; • Submit project bid; • Track installed quantities, materials used and tested during construction; • Publish construction status to stakeholders; • Change project scope; • Monitor civil rights, on-the-job training (OJT) , labor requirements compliance; and • Monitor subcontract progress.
|
From page 26... ...
Various elements of this information are communicated frequently among field, project office, test lab, and central office personnel throughout the construction project. A standard XML schema for this information would enable integration of the diverse data collection and data management systems utilized to track this information, thereby streamlining information flows and reducing the opportunity for error.
|
From page 27... ...
Acquire Reference Information for Project Cost Estimate Estimators use production, labor, and equipment rates and historical bid and as-built information to estimate labor, equipment, and material costs for the project pay items. An estimator often gets this reference information from a variety of internal and external sources, including data warehouses and commercial and government publications and services.
|
From page 28... ...
4.4 Highway Bridge Structures The topic areas for bridge structures included in Table 1 spanned the full life cycle of a bridge -- analysis and design, construction, inspection and load rating, management, operations, and maintenance. Given the common data exchanges that occur within and across these areas, three specific business processes within these areas were identified as good candidates for XML schema: • Bridge Analysis and Design; • Truck Permitting and Routing; and • National Bridge Inventory (NBI)
|
From page 29... ...
Their accuracy is critical. Even though crash data are not currently standardized, the Model Minimum Uniform Crash Criteria (MMUCC)
|
From page 30... ...
and relevant location and linear referencing elements needed to link crash records to highway inventory provide additional sources for such a schema. Functions/processes that could make use of this schema include the following: • Get highway information for a crash and store it in an archive for statistical analysis and queries; • Get highway information for a crash and use it to validate information on the crash report (e.g., consistency of different location attributes of the crash record, pavement surface type, median type)
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.