Technical Committee on Technical Committee on Electronic Engineering DataElectronic Engineering Data

MembersMembersDesign:Design:•• Michael Balbierer, P.E., Delaware

Design Resource EngineerDesign Resource Engineer•• Jeff Jasper, P.E., Kentucky

Manager, Developmental BranchManager, Developmental Branch•• Kent Nicholson, P.E., Iowa

Assistant Design Engineer, SupportAssistant Design Engineer, Support •• Jesus Mora, P.E., California

Chief, Office of CADD and Engineering Chief, Office of CADD and Engineering GIS SupportGIS Support

Construction:Construction:•• Victor Barbour, P.E., North Carolina

Director, Technical ServicesDirector, Technical Services •• George Raymond, P.E., Oklahoma

State Construction EngineerState Construction Engineer

Bridges/Structures:Bridges/Structures:•• George Conner, P.E., Alabama

State Maintenance EngineerState Maintenance Engineer •• Loren Risch, P.E., Kansas

Bridge Design EngineerBridge Design Engineer

Information Systems:Information Systems:•• George Kopp, P.E., Missouri

CADD Services CADD Services EngineerEngineer

•• Bret Blair, P.E., Kentucky Information Systems ManagerInformation Systems Manager

FHWAFHWA•• VacantVacant

AASHTO LiaisonAASHTO Liaison•• Jim McDonnell, P.E.

Committee ChargeCommittee Charge

“…“…provide a forum for the development, publication, provide a forum for the development, publication, and maintenance of highway electronic engineering and maintenance of highway electronic engineering data standards to provide a non-proprietary data standards to provide a non-proprietary exchange of data between and among software exchange of data between and among software applications and data customers…”applications and data customers…”

The Technical Committee’s goal is to promote the The Technical Committee’s goal is to promote the use of “vendor-neutral” formats to improve the use of “vendor-neutral” formats to improve the exchange and use of electronic engineering data to exchange and use of electronic engineering data to reduce costs, save time, and improve quality over reduce costs, save time, and improve quality over the life of a capital project or asset. the life of a capital project or asset.

Next StepsNext Steps Guide the currently-developed engineering data Guide the currently-developed engineering data

schemas (i.e., TransXML) through the balloting schemas (i.e., TransXML) through the balloting process for official adoption by AASHTOprocess for official adoption by AASHTO

Establish operating procedures for the adoption, Establish operating procedures for the adoption, development, maintenance, and enhancement of development, maintenance, and enhancement of these schemas, including stakeholder roles and these schemas, including stakeholder roles and responsibilitiesresponsibilities

Engage external highway engineering data users Engage external highway engineering data users such as the consulting engineers, construction such as the consulting engineers, construction contracting community, material suppliers, local contracting community, material suppliers, local agencies, and utility companiesagencies, and utility companies

Communicate with State DOT members to Communicate with State DOT members to determine their business needs determine their business needs

Next StepsNext Steps

Collect input from and exchange ideas with other Collect input from and exchange ideas with other industry stakeholders such as contractors, software industry stakeholders such as contractors, software vendors, and hardware or equipment manufacturersvendors, and hardware or equipment manufacturers

Develop research proposal(s) for subcommittee Develop research proposal(s) for subcommittee consideration and submission to NCHRP to expand consideration and submission to NCHRP to expand TransXMLTransXML

Maintain standardized methods, content, and Maintain standardized methods, content, and formats for effective sharing of engineering dataformats for effective sharing of engineering data

Identify and pursue appropriate funding sources to Identify and pursue appropriate funding sources to ensure long-term viability of the standardsensure long-term viability of the standards