Today’s Trns•port (simplified)

Download Report

Transcript Today’s Trns•port (simplified)

TUG, AASHTO, TTF
Primer Class
Tim Lindberg
(TTF Member from South Carolina)
October 6, 2007
Trns•port Task Force (TTF)
Membership
• 9 members
– Cross-section of users and IT support staff
– Cross-section of Trns•port usage
• Typical member is a Trns·port user and
has been active in the TUG for several
years
Organization
Special Committee on Joint Development
Trns·port Product
Task Force
Trns·port User
Group, TRTs,
TAGs
Trns·port Licensing Agencies
TTF Represented States
Trns•port Task Force (TTF)
Appointments
• Resumes solicited from all licensing agencies
• TTF reviews qualifications and recommends
short list of applicants to Special Committee on
Joint Development (SCOJD) **
• SCOJD makes final selection of members to be
appointed to TTF **
• Chair and Vice-Chair determined by SCOJD
with input from TTF members **
** (Recent Changes to appointment process)
Trns•port Task Force
Responsibilities
• Determines when new products should be
developed
• Determines appropriate software platforms
• Annual Maintenance Support and
Enhancement (MSE) contract with
contractor
• Long Range Work Plan (LRWP)
MSE Document
1. Overview
2. Maintenance and Support Services
3. Maintenance and Support Budget
4. Enhancement Work Items
5. Shared Products
6. Service Units
http://www.cloverleaf.net/files/480
Service Units
• Contracting through AASHTO rather than
sole source contracting to Info Tech
• Services in $13,500 units
• Support activities examples
–
–
–
–
Installing Trns•port and setting system parameters
Customizing screens and report templates
Converting data and populating the Trns•port database,
Analyzing differences between Trns•port and current
agency practices
– Providing orientation and training
– Funding Enhancements
Task Force Meetings
• 5 meetings per year
– Sept / December / January / April / June
• MANY E-Mail exchanges
• Frequent conference calls
• Lots of work done in subgroups
September TTF Meeting
• Primary Objective
– Strategic Planning
• Additional Objectives
– Prepare for TUG
– Review results of previous FY MSE
• Normally held in Gainesville
– More attendees from ITI’s staff
December Meeting
• Primary Objective
– Start preparation of LRWP and MSE
• Review enhancement ballot results
– Ask ITI to prepare estimates of TTF selected
enhancements
January TTF Meeting
• Primary Objective
– Finalize LRWP and MSE
• Determine enhancements
• Prepare for Annual Chairs Meeting
– Meeting of all AASHTOWare Task Force Chairs
with SCOJD
April TTF Meeting
• React to directions received at Annual
Chairs Meeting
• Review status of current MSE
– Enhancements
– Budget concerns
June TTF Meeting
• Year end “stuff”
– June software releases
– Final adjustments to next FY MSE
Technical Review Teams
(TRTs)
• Appointed by TTF
– Assist TTF in working with contractor in
development of new product/enhancement
• 3 to 5 members
– Users familiar with product/functions
– Agencies contributing funding
• Business normally conducted by e-mail or
conference calls
• Chaired by TTF member
TRTs
• Review software prototypes as software is
developed
• Provides contractor guidance on user needs
• Reviews and recommends acceptance of
results of the software testing
Testing of Software
•
•
•
•
Contractor’s QC/QA
Alpha testing
Beta testing
Warranties
Alpha Testing
• Formalized testing at a controlled site
– Required by AASHTOWare guidelines
• Normally at contractors offices
• Normally performed by contractor
– Can utilize agency users
• Test results reviewed and accepted by TTF
Beta Test Sites
• User agency testing prior to release of new
enhancements
– Required by AASHTOWare guidelines
• Number of sites based on magnitude of the
enhancement
– Multiple sites (on different platforms) for complex
enhancements
– Beta sites selected by TTF
• 30-60 day Beta testing typical
• Test results reviewed and accepted by TTF
Beta Test Sites
• Need commitment from user agencies to
perform adequate pre-release testing
– Necessary third party software
– Commitment of staff
– Coordinate with Trns•port contractor
Warranties
• 120 days on enhancements
– Longer for special cases
• Includes fixing things broken in the release
Trns•port Task Force
Left to Right
John Riedl (OR)
Tim Lindberg (SC)
Jim Ramsey (AASHTO)
Liz Wunderlich (NE)
Barbara Scruggs (VA)
Don Grayson (MS)
Jim Johnson (FL)
Loren Lemmen (MI)
Todd Bergland (MN)
(Not pictured)
Denis Glascock (MO)