SlideServe
Menu
Préférences
© SlideServe · v2026

Technical Committee on Electronic Engineering Data

zelig avatar
5 diapositives · 212 Views · Aug 29, 2014

Technical Committee on Electronic Engineering Data. Members. Bridges/Structures: • George Conner, P.E., Alabama State Maintenance Engineer • Loren Risch, P.E., Kansas Bridge Design Engineer Information Systems: • George Kopp, P.E., Missouri CADD Services Engineer

Technical Committee on Electronic Engineering Data - slide 1
01 / 5Technical Committee on Electronic Engineering Data
1 / 17

Télécharger la présentation

Technical Committee on Electronic Engineering Data
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation
  1. Technical Committee on Electronic Engineering Data

  2. Members Bridges/Structures: • George Conner, P.E., AlabamaState Maintenance Engineer • Loren Risch, P.E., KansasBridge Design Engineer Information Systems: • George Kopp, P.E., MissouriCADD Services Engineer • Bret Blair, P.E., KentuckyInformation Systems Manager FHWA • Vacant AASHTO Liaison • Jim McDonnell, P.E. Design: • Michael Balbierer, P.E., DelawareDesign Resource Engineer • Jeff Jasper, P.E., KentuckyManager, Developmental Branch • Kent Nicholson, P.E., IowaAssistant Design Engineer, Support • Jesus Mora, P.E., CaliforniaChief, Office of CADD and Engineering GIS Support Construction: • Victor Barbour, P.E., North CarolinaDirector, Technical Services • George Raymond, P.E., OklahomaState Construction Engineer

  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…” • 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 • 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 • 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 • 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 • Identify and pursue appropriate funding sources to ensure long-term viability of the standards