1. Technical Committee on Electronic Engineering Data

2. Members Design: Design Resource EngineerMichael Balbierer, P.E., Delaware Design Resource Engineer Manager, Developmental BranchJeff Jasper, P.E., Kentucky Manager, Developmental Branch Assistant Design Engineer, SupportKent Nicholson, P.E., Iowa Assistant Design Engineer, Support Chief, Office of CADD and Engineering GIS SupportJesus Mora, P.E., California Chief, Office of CADD and Engineering GIS SupportConstruction: Director, Technical ServicesVictor Barbour, P.E., North Carolina Director, Technical Services State Construction EngineerGeorge Raymond, P.E., Oklahoma State Construction EngineerBridges/Structures: State Maintenance EngineerGeorge Conner, P.E., Alabama State Maintenance Engineer Bridge Design EngineerLoren Risch, P.E., Kansas Bridge Design Engineer Information Systems: CADD Services EngineerGeorge Kopp, P.E., Missouri CADD Services Engineer Information Systems ManagerBret Blair, P.E., Kentucky Information Systems ManagerFHWA VacantVacant AASHTO Liaison Jim McDonnell, P.E.

3. Committee Charge “…provide a forum for the development, publication, and maintenance of highway electronic engineering data standards to provide a non-proprietary exchange of data between and among software applications and data customers…” “…provide a forum for the development, publication, and maintenance of highway electronic engineering data standards to provide a non-proprietary exchange of data between and among software applications and data customers…” The Technical Committee’s goal is to promote the use of “vendor-neutral” formats to improve the exchange and use of electronic engineering data to reduce costs, save time, and improve quality over the life of a capital project or asset. The Technical Committee’s goal is to promote the use of “vendor-neutral” formats to improve the exchange and use of electronic engineering data to reduce costs, save time, and improve quality over the life of a capital project or asset.

4. Next Steps Guide the currently-developed engineering data schemas (i.e., TransXML) through the balloting process for official adoption by AASHTO Guide the currently-developed engineering data schemas (i.e., TransXML) through the balloting process for official adoption by AASHTO Establish operating procedures for the adoption, development, maintenance, and enhancement of these schemas, including stakeholder roles and responsibilities Establish operating procedures for the adoption, development, maintenance, and enhancement of these schemas, including stakeholder roles and responsibilities Engage external highway engineering data users such as the consulting engineers, construction contracting community, material suppliers, local agencies, and utility companies Engage external highway engineering data users such as the consulting engineers, construction contracting community, material suppliers, local agencies, and utility companies Communicate with State DOT members to determine their business needs Communicate with State DOT members to determine their business needs

5. Next Steps Collect input from and exchange ideas with other industry stakeholders such as contractors, software vendors, and hardware or equipment manufacturers Collect input from and exchange ideas with other industry stakeholders such as contractors, software vendors, and hardware or equipment manufacturers Develop research proposal(s) for subcommittee consideration and submission to NCHRP to expand TransXML Develop research proposal(s) for subcommittee consideration and submission to NCHRP to expand TransXML Maintain standardized methods, content, and formats for effective sharing of engineering data Maintain standardized methods, content, and formats for effective sharing of engineering data Identify and pursue appropriate funding sources to ensure long-term viability of the standards Identify and pursue appropriate funding sources to ensure long-term viability of the standards