TransXML Home
Project Information
Links
Contacts
Sources and Resources
GML Experiment
Construction/Materials Schema
Bridge Structures Schema
Survey/Design Schema
Safety Schema

Search:
Go 

Login
Register
NCHRP 20-64 XML Schemas for the Exchange of Transportation Data     
TransXML Home > Construction/Materials Schema > Construction/Materials Schema Discussion
Discussion Forum

Author Thread: Scope of Quantities and Materials schema
Frances Harrison
Scope of Quantities and Materials schema
Posted: Friday, July 23, 2004 9:16 AM (EST)

Purpose and Scope

At the project construction site, inspectors record daily construction progress on pay items.  Associated with pay item progress is a parallel tracking of the component materials of the pay item and the extent to which these materials meet the agencies materials testing requirements. This information is gathered by project inspectors and laboratory personnel and communicated to the project engineer.  The project engineer prepares a progress estimate using this information and submits it to the central office to trigger a progress payment to the contractor.

The information being exchanged includes pay item descriptive information, and partial quantities placed, placement locations, materials samples collected, field tests performed, and the outcome of those tests.  The Installed Quantities and Materials Used and Tested schema will build upon the aecXML Infrastructure Project schema to enable association of a location with a partial quantity placed and to encompass material samples collected, field tests performed, and the outcome of those tests.

A broad range of field devices are used to measure construction progress and track material use, sampling, and testing.  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 will 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.

Base Schema/ Standards

·         aecXML Infrastructure Project schema

·         aecXML Common Object Schema

Resource Documents

·         IAI aecXML Domain Committee, aecXML.xsd and aecXML_infra_v33.xsd

·         AASHTO, AASHTOWare Trns•port product documentation

Sample Applications

Proposed application to be developed to demonstrate the use of this schema:

·         Develop an XSLT stylesheet to transform an Installed Quantities and Materials Used and Tested XML instance document into a construction progress report in HTML format.


Comments:

Author Thread:
Mike Hruska
Scope of Quantities and Materials schema
Posted: Friday, December 03, 2004 12:33 PM (EST)

You mention test lab and field tests in your definition of scope.

Is the plan for materials properties determined in the field and in the laboratory to be equally contained within the scope of the schema?

Have you reviewed matML schema (www.matml.org) for the inlcusion of necessary/relevant elements?

     

Bob DeHoff
Scope of Quantities and Materials schema
Posted: Friday, December 03, 2004 4:24 PM (EST)
Material properties determined in the field and lab do fall within the long term TransXML goals. Given the TransXML budget and time constraints, it was proposed that the scope be limited to addressing only the high level information about samples and tests that is required from the progress payment perspective. Were the required samples collected? Were the required tests performed and passed? Obviously that is just the surface of sampling and testing. Future TransXML initiatives would drill down into the sample details, the actual test measurements, and so on. We had not come across MatML. The intent is for TransXML to not reinvent the wheel if it already out there. MatML could serve as the foundation for future TransXML work in the materials area.

     

Todd Bergland
Scope of Quantities and Materials schema
Posted: Thursday, December 09, 2004 9:10 AM (EST)

Based on a cursory glance it appears that the matML may contain some useful information.  One thing that is important to our industry is the source of the material.  Information such as Source ID/Pit No, Location Lat/Long, date opened, date closed, active/inactive, owner, County and material currently in the pit.  If we are going to discuss material sampling I think it is important to include where the material orginated. 

     

Todd Bergland
Scope of Quantities and Materials schema
Posted: Thursday, December 09, 2004 10:27 AM (EST)

Other things that are important to quantities and materials tracking would be:

1. Time/Date

2. Temperature

3. Test Type

4. ID's related to pay items. For example entering an ID number for a light pole for tracking each items this is not the pay item number but a numebr entered on the signal plan.

5. Remarks column

6. Quantities are tracked either by percentage complete or by exact quantity.

 

 

 

     

Al Butler
Scope of Quantities and Materials schema
Posted: Tuesday, January 25, 2005 10:12 AM (EST)
I look forward to this standard offering a realistic mechanism for the transmission and geographic analysis of materials data in an as-built inventory.  For example, many pavement management systems rely on assumptions regarding material consistencies that may be unreasonable in the real world.  As a result, ESAL forecasts often absorb all the uncertainty in pavement design calculations.  Anything that makes it easier to record what really happened--field adjustments, material changes, whatever--will make it much easier to adopt a true facilities management approach and migrate this information to the post-construction period.  The first payoff will come in getting the construction-induced changes into the facility inventory.

     

Mike Hruska
Scope of Quantities and Materials schema
Posted: Thursday, April 07, 2005 1:06 PM (EST)

Just a few questions regarding the ReferenceTestMethod Class-

Would it be more beneficial to identify the SDO (Standards Development Organization) rather than just indicating the boolean condition of whether or not it was an AASHTO test?

Beyond just the test method, is the version of the test method used important?