Skip to main content

Information Technology for Efficient Project Delivery (2008) / Chapter Skim
Currently Skimming:

Gaps and Solutions
Pages 28-35

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 28...
... 2. Data can be converted between differing file structures by means of a common data map, which requires export–import between the software applications (data exchange)
Read the entire page →
From page 29...
... Until the last five years or so, data were exchanged between software with differing file formats by exporting from one program and importing into another utilizing a standard file format called ASCII text. This is simply alphanumeric and text characters that could be seen in a text editor (Microsoft Word Pad)
Read the entire page →
From page 30...
... 31 FIGURE 15 Database tables. FIGURE 16 ASCII text data exchange.
Read the entire page →
From page 31...
... With XML, as long as the two software applications share a common field name or label, and the data fields are structured similarly, exchange will occur. As long as the separate software programs share the same field names (or schema)
Read the entire page →
From page 32...
... NCHRP has funded research for the development of TransXML, an intended universal schema for transportation-related schemas. The magnitude and detail of datasets required for transportation agency specification requires interpretation of these schemas by differing software applications.
Read the entire page →
From page 33...
... When application interfaces are designed to a common data format, then only one mapping operation needs to be done regardless of the software applications involved. This operation scales linearly and can be successfully accomplished with XML schema.
Read the entire page →
From page 34...
... For XML-based standards, the use of XML namespaces allows sufficient partitioning of the domain data model to enable multiple disciplines or groups to work independently of each other, while providing a common core set of reusable data models that can be applied across multiple subject domains. The most important advantage of the partitioned domain approach is that writing application software interface mappings to domain-based applications is easier to match up with domain-based terminology in the standard.
Read the entire page →
From page 35...
... Whereas TIM would lend itself well to design-build project delivery, the predominate design-bid-build delivery is another story as contractors are used to getting 2D drawings at theoretical 100% design completion. • Legal issues in which innovative cooperation will be required to solve potential liability issues when sharing and relying on digital data supplied by others.
Read the entire page →

Key Terms

  • data model
  • software applications
  • data library
  • data formats
  • software application

  • software interoperability
  • digital data
  • reference data
  • data fields
  • partitioned domain

  • achieve interoperability
  • field names
  • domain data
  • data mapping
  • abstract data

  • model data
  • data map
  • software package
  • software mapping
  • software maps

  • creating software
  • commercial software
  • domain terminology
  • abstract domain
  • differing file

  • file structures
  • construction management
  • multiple domains
  • database integration
  • collaborating business


    • 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.