AASHTO’s Cooperative Software Development Program AASHTOWare ® Transportation Software Solutions Trnsport User Group Meeting October 2004 Mobile, Alabama.

Slides:



Advertisements
Similar presentations
OMT RETREAT (WORK PLANNING). The UNDG Operational Guidelines for the Implementation of Common Services were developed in 2000 by an inter-agency.
Advertisements

Reliability Center Data Request Task Force Report WECC Board Meeting April 2009.
Roles and Responsibilities. Collaborative Efforts to Improve Student Achievement Guidelines for developing integrated planning and decision making processes.
Contract and Project Management: A Field Perspective Moderator Michael Peek, PE CCE CFM Office of Engineering and Construction Management.
Subchapter M-Indian Self- Determination and Education Assistance Act Program Part 273-Education Contracts under Johnson-OMalley Act.
Insert software product logo (or name) on slide master AASHTO Civil Rights and Labor Management System Executive Summary.
ACA Directorate of Contracting, Fort Bragg RECAP OF COR FUNDAMENTALS BY ADMINISTRATION DIVISION 15 February 2007.
AASHTO’s Cooperative Software Development Program Trnsport User Group Meeting October 22 – 26, 2006 Portland, Maine Trnsport User Group Trnsport Task Force.
AASHTOWare  - Transportation Software Solutions Contents Participants Follow-up Purpose Introduction Results Trnsport 2004 Customer Satisfaction Survey.
2  A nonprofit, nonpartisan association  Represents highway and transportation departments in the 50 states, the District of Columbia, and Puerto Rico.
Department of Transportation Support Services Branch ODOT Procurement Office Intergovernmental Agreements 455 Airport Rd. SE, Bldg K Salem, OR
Congress and Contractor Personal Conflicts of Interest May 21, 2008 Jon Etherton Etherton and Associates, Inc.
AASHTOWare Program Benefits Standing Committee on Highways October 18, 2013 Tom Cole, Idaho DOT AASHTO Special Committee on Joint Development.
“RAC 101” An Introduction to the AASHTO Research Advisory Committee 26 July 2010.
AASHTO’s Cooperative Software Development Program Trnsport User Group Meeting October 6 – 10, 2007 St. Louis, Missouri Trnsport User Group Trnsport Task.
ZHRC/HTI Financial Management Training
Bridge Design-Rating 2014 Administrative Overview RADBUG Meeting Traverse City, MI Judy B. Skeen, P.E.
WELCOME TO THE PROCUREMENT SEMINAR Procurement and Contracts An Overview of Contract Administration.
Emerging Latino Communities Initiative Webinar Series 2011 June 22, 2011 Presenter: Janet Hernandez, Capacity-Building Coordinator.
The Executive Branch: An Overview Presented by Kris Kautz, Deputy Director Department of Administrative Services.
TUG, AASHTO, TTF Primer Class Tim Lindberg (TTF Member from South Carolina) October 6, 2007.
TUG, AASHTO, TTF Primer Class Tim Lindberg (TTF Member from South Carolina) November 6, 2005.
Working with Info Tech, Inc. Teresa Franklin Trnsport Product Manager November 6, 2005 A Primer for Trnsport Users.
Wisconsin Technical Service Providers (TSP) Plan.
Teacher Assistant Guidelines Student Services 2009.
School Councils 101 Fall School Council Orientation Forum YRDSB 2009.
Welcome Elizabeth Schanbacher Assistant Superintendent of Educational Technology.
INDIANA UNIVERSITY Graduate and Professional Student Organization Elected Officers.
TAC July 2, 2003 Market Design Implementation Process Recommendation.
Old Policy – which no one ever seem to have heard of.
HIGHWAY/UTILITY PROGRAM OVERVIEW ROADWAY CONFERENCE APRIL 20, 2009.
AASHTOWare Program Overview to the Safety Data Systems Task Group of the Safety Management Subcommittee Presented by Tony Bianchi, Project Manager AASHTO.
Texas Regional Entity Update Sam Jones Interim CEO and President Board of Directors July 18, 2006.
Best Practices: Financial Resource Management February 2011.
EMPOWERING LOCAL SENATES Kevin Bontenbal, South Representative Stephanie Dumont, Area D Representative.
10/16/2015 Roles and Responsibilities of Principal Investigators/ Program Directors/ Project Directors.
AASHTO Achieving Excellence in Transportation September 20, 2006 Safety Background.
SMS Planning.  Safety management addresses all of the operational activities of the entire organization.  The four (4) components of an SMS are: 1)
Organizational Structure Organizational Structure House of Delegates is comprised of 116 delegates Currently, there are 58 Chapters (one at each.
Maine Aeronautical Advisory Board November 8, 2012.
S C O F A — S T A N D I N G C O M M I T T E E O N F I N A N C E A N D A D M I N I S T R A T I O N H T T P : / / S C O F A. T R A N S P O R T A T I O N.
Chapter Officers Roles Officer roles and additional recommended officer roles.
Committees. Executive Committee Terms of Reference Committee Type – standing Purpose -. Manage the business and technical affairs of Open Health Tools.
Central Kitsap School District SHARED DECISION MAKING Central Kitsap High School March 2, 2006.
Division for Policy Administration 321 North Clark Street 21st Floor Chicago, IL (312) Fax: (312)
Systems Accreditation Berkeley County School District School Facilitator Training October 7, 2014 Dr. Rodney Thompson Superintendent.
Queensland Referees Referee Management Structure.
School Site Council (SSC) Essentials in brief An overview of SSC roles and responsibilities Prepared and Presented by Wanda Chang Shironaka San Juan Unified.
Amendment of Orange County Emergency and Non- Emergency Medical Care and Transportation Ordinance Board of County Commissioners Public Hearing January.
Roles and Responsibilities of School Councils A 3 hour training for experienced SBDM Council Members.
AFSA Chapter Officer Training Module 1 Officer Roles and Responsibilities.
Integrates and automates the transportation safety planning and management Software analysis tools to assist highway agencies to implement their SHSP and.
AASHTO’s Cooperative Software Development Program AASHTOWare ® Transportation Software Solutions Trnsport User Group Meeting November 6 – 9, 2005 Daytona.
Overview of SCOH Strategic Plan AASHTO Subcommittee on Design 2010 Annual Meeting Rick Land, Vice Chair AASHTO Highway Subcommittee on Design and Chief.
High Level Joint Committee (HLJC) Bodies of the HLJC Main tasks and working procedures Andreas Holtkotte, Focal Area Coordinator Environment and Energy,
SAFETYANALYST Integrates and automates the transportation safety planning and management Software analysis tools to assist highway agencies to implement.
Presented by the Outreach & Training Subcommittee of College Planning Council, as required by Section V.8 of the College Planning Council Handbook College.
TEXAS NODAL (ERCOT REVISIONS)
Audit Committees: Perspectives from an Elected Official
WP1 - Consortium coordination and management
Trust, Accountability and Integrity: Board Responsibility for
Money Bills Amendment Procedure and Related Matters Bill [B 75–2008]
AFSA Chapter Officer Training
Standing Committee on Highways
Roles and Responsibilities
Centralization of Texas State Contract Compliance Functions
Roles and Responsibilities
THE SCHOOL SITE COUNCIL
Position descriptions
Presentation transcript:

AASHTO’s Cooperative Software Development Program AASHTOWare ® Transportation Software Solutions Trnsport User Group Meeting October 2004 Mobile, Alabama

AASHTO, the Trnsport Task Force and the Trnsport User Group

So, just how does it all work together? Just plain luck? Magic?

So, just how does it all work together? Just plain luck? Magic

So, just how does it all work together? Organization Cooperation Participation Experience

AASHTO Organization Chart John Horsley Executive Director Tony Kane Director of Engineering and Technical Services Engineering Jan Edwards, Director ProjectOffice Project Managers PolicyPublications Meetings and Membership Services

What is AASHTO? Established by the State DOTs in 1914 to work toward common goals Primary functions: –Advocate for transportation issues in Washington, DC –Develop globally-recognized transportation engineering guides, standards, and software –Facilitate information-sharing between the Member Agencies through meetings, workshops, and the Internet –Represent the Member Agencies in national discussions with other groups

AASHTO Structure Governed by Board of Directors: CEO of each Full Member Agency 50 State DOTs, District Of Columbia DOT & Puerto Rico DOT

AASHTO Structure Modal Committees: –Aviation –Highways –Public Transportation –Railroads –Water Transportation Topic-Oriented Committees: –Administration –Environment –Planning 11 Standing Committees: Over 200 committees within the AASHTO Structure Members are primarily State DOT representatives Standing Committee on Highways is largest by far –Quality –Research –Safety

Standing Committee on Highways Consists of the Chief Engineer from each State DOT Primary responsibilities: –Developing policy related to the nation’s highway system –Approving technical documents developed by subcommittees and task forces –Responding to FHWA and other federal agencies regarding proposed regulations Nine subcommittees cover all aspects of highway work, from right-of-way to design to construction to operations to maintenance… Chair: Joe Perkins, AK Vice Chair: Frank Danchetz, GA

It is the AASHTO Program under which AASHTOWare ® is developed and managed AASHTOWare ® is software developed, supported and maintained through an economical, not-for-profit, pooled-fund process known as “AASHTO joint development” What is the Cooperative Software Development Program?

AASHTOWare Methodology Ensuring Delivery Documented processes and clearly defined roles and responsibilities allow defined, repeatable, and manageable results: –Cooperative Computer Software Policies, Guidelines and Procedures (contractually binding on Contractors). –AASHTOWare Standards and Guidelines notebook (contractually binding on Contractors). –AASHTOWare Strategic Plan. –Task Force Handbook. –AASHTOWare Catalog Member participation at all levels of process. AASHTO professional project management staff.

Governing Documents Cooperative Software Development Program Policies, Procedures and Guidelines (PG&P) This Policies, Guidelines and Procedures (P, G & P) document is intended to gather in one place the principal guiding documents relating to AASHTO's Cooperative Computer Software Development program. Included herein is AASHTO Administrative Resolution AR-2-86, which was most recently revised by the AASHTO Board of Directors on April 21, It constitutes the principal policy guidance on this important and growing AASHTO activity. Additional guidelines and procedures derived from and intended to clarify and provide further detail on AR are also included.

Special Committee on Joint Development Study all policy issues and topics with respect to the Cooperative Computer Development Program in consultation with all active product and project task forces and bring recommendations resulting therefrom before the Board of Directors and Executive Committee for action, as appropriate. Review and approve all procedural documents, manuals and other guidelines pertaining to the process and management of the Cooperative Software Program Approve the appointment and removal of Product and Project Task Force members as necessary and the designation of the chairperson of each.

Special Committee on Joint Development Establish advisory groups when appropriate on the recommendation of the product and/or project task forces. Recognize users groups when appropriate. Review project proposals, and authorize solicitation of the membership for participation and funding for Cooperative Computer Development Projects.

AASHTO Staff The Executive Director, or his authorized delegate(s), shall: Serve as an ex-officio, non-voting member of the Special Committee on Joint Development, all product and project task forces, and such other teams, working groups and other entities as are created in furtherance of this program. Attend the meetings of the Special Committee and all task forces, as required. Assemble and submit all budgets to the Executive Committee and approve all interim budget revisions. Approve all solicitations for proposals, quotations or qualifications attendant to the preparation of a contract for services or equipment in advance, whether oral or written.

AASHTO Staff (Continued) The Executive Director, or his authorized delegate(s), shall: Lead all contract negotiations and contract revision negotiations. Execute all contracts and contract modifications or revisions. As the AASHTO Contract Officer, establish guidelines and instructions for task force chairpersons and members concerning necessary record keeping, communications with contractors and such other topics as appropriate to ensure the proper management and administration of all contracts. Prepare and distribute detailed and summary financial information necessary for contract administration and management and distribute to the Special Committee and task force members, as appropriate.

Trnsport Task Force Prepare product information for distribution to the AASHTO membership by the Executive Director or his delegate. Prepare, refine and, when approved by the Special Committee on Joint Development, implement a product marketing plan including recommendation of appropriate fee schedules. Receive advice and recommendation from the users group. Develop and recommend work plans for contracts for maintenance, enhancement, and training. Monitor and direct the product distribution activities and also contract compliance and progress.

Trnsport Task Force Prepare and submit recommended budgets for product maintenance, enhancement and training, and task force travel needs to the Chairperson of the Special Committee on Joint Development and the Executive Director or his delegate. Review all contractor invoices and make recommendations by the Task Force Chairperson on contractor payments to the Executive Director or his delegate. Recommend requests to proceed with project or product related software development activities from AASHTOWare Contractors to the AASHTO Executive Director.

Trnsport User Group Individually represent his or her participating member department's, or licensed organization's interest in the product. Provide advice and recommendations to the Product Task Force on: –the Product's effectiveness, –the Product's deficiencies, and –any needed product enhancements. Define and detail any product training and support needs. Detail and prioritize maintenance, enhancement, and support needs. Submit the resulting recommendations to the Trnsport Task Force.

AASHTOWare Fundamental Principles Initiating an AASHTOWare Project: A single member department, group of member departments, or AASHTO committee(s) identify a need for a major new development area, or an enhancement to an existing product; With staff assistance, a project proposal is developed; Proposal reviewed by the Special Committee on Joint Development; Upon SCOJD approval, proposal distributed to AASHTO membership for voluntary commitment and participation

RECAP - AASHTOWare Process Management  User Groups provide advice and recommendations to the Product Task Force on: –the Product's effectiveness, –the Product's deficiencies, and –any needed product enhancements  Task Forces guide software development performed by contractors  Special Committee on Joint Development provides technical management oversight  Full-time AASHTO Staff management  All costs paid out of license fee revenue or project solicitations or additional financial participation

So, does it all work together? Cooperative Software Development is a REALITY !

The AASHTOWare web site

SOURCES for Information Policies, Procedures & Guidelines Publication AASHTOWare Catalog AASHTO Staff Web Sites ( and Trnsport Task Force