Transcript Trns•port Task Force Report

2004 Trns•port Task Force Report
Trns•port Users Group Conference
October 14, 2004
Mobile, Alabama
Paul Neumann, Colorado DOT
Chair, Trns•port Task Force
Presentation Outline
•
•
•
•
•
Task Force Overview
Maintenance and Support
Enhancements
Strategic Directions
Conclusion
Task Force Overview
Trns•port Mission
• The mission for Trns•port is to serve
the operational and executive
management information needs of the
transportation agency associated with
the development and management
of construction projects.
Trns•port Long Range Work Plan (LRWP)
http://www.cloverleaf.net
Trns•port Licensees
New Brunswick
Philippines
Alaska
Hawaii
39 State Agencies, 1 Canadian Province,
FHWA Federal Lands Highways, DC Dept.
of Public Works, Philippines DPWH
Trns•port Implementation Status
http://www.cloverleaf.net
Trns•port Task Force Members
•
•
•
•
•
•
Paul Neumann, Colorado, Chair
Roger Bierbaum, Iowa, Vice Chair
Jim Johnson, Florida
Loren Lemmen, Michigan
Todd Bergland, Minnesota
Denis Glascock, Missouri
Trns•port Task Force
http://www.cloverleaf.net
Task Force Meeting Participants
• Regular participants at our meetings:
–
–
–
–
–
–
–
Chuck Conley, AASHTO Staff
Dominic Cali, Louisiana, SCOJD Liaison
John Morden, Florida, T&AA Liaison
David Bollie, Alabama, TUG Chair
Tom Rothrock, Info Tech
Margaret Andraka, Info Tech
Teresa Franklin, Info Tech
Trns•port Task Force Meeting Minutes
http://www.cloverleaf.net
Task Force Responsibilities
• Strategic Direction
–
–
–
–
Define long term vision
Establish product objectives
Determine annual goals
Develop marketing plan
AASHTOWare® Policies, Guidelines and Procedures
http://www.aashtoware.org
Task Force Responsibilities
• Product Management
– Prepare 5-year Long Range Work Plan (LRWP)
– Establish annual budget
– Prepare annual Maintenance, Support and
Enhancement (MSE) work plan
– Manage/direct contractor
– Determine operating platforms
– Evaluate need for new modules
AASHTOWare® Policies, Guidelines and Procedures
http://www.aashtoware.org
Trns•port Task Force Operations
• Five meetings each year (plus the TUG)
• Other meetings as required
– Presentations to potential licensees
– SCOJD/Task Force Chairs meeting
•
•
•
•
Numerous conference calls
Countless e-mails
Subgroups
Technical Review Teams (TRTs)
Trns•port Task Force Operations
http://www.cloverleaf.net
Trns•port Task Force Positions
• Currently one opening; generally one
opening per year
• Seeking individuals who are interested in
serving on the Task Force
– Experience with BAMS/DSS and estimation
modules desirable for current opening
• Submit resumes anytime
– By November 1, 2004 for current opening
• Must have approval from agency
Maintenance and Support
Maintenance and Support Focus
• Quality of releases
– More important than quantity
– Improving installation and deployment
– Lowest possible number of errors
• Communications
– Posting more information on Cloverleaf
– More frequent notifications to users
Fixed-Price Maintenance
• Initiative from SCOJD
– Fixed price, rather than time and materials
– Intended to increase quality and decrease time
to resolve errors, because funding level is no
longer an issue
– Shifts risk from AASHTO to contractor
• FY 2005 contract includes $379,159 for
fixed-price maintenance
FY 2005 Fixed-Price Maintenance
• 17 BAMS/DSS Documentation TMRs
• 16 BAMS/DSS View TMRs
• 6 BAMS/DSS Import/Export TMRs
• 5 BAMS/DSS LAS View TMRs
• 72 PES TMRs
– All known PES maintenance TMRs as of
April 18, 2004
FY 2006 Fixed-Price Maintenance
• Intent is to place PES under fixed-price
maintenance as of July 1, 2005
– Stable module selected to start with
• Accumulate data to determine whether
fixed-price maintenance is costeffective
Annual TMR Review
• Review maintenance TMR backlog
–
–
–
–
Combine duplicate or similar TMRs
Determine whether any are obsolete
Determine whether priorities are correct
Over 500 maintenance TMRs removed
since 2002
Trns•port TMRs
• Plan for FY 2005
– Continue combining / bundling of TMRs
• Looking for the right solution
– Deliver high priority maintenance TMRs
as quickly as possible
– Continue collaboration with TRTs and
subgroups to prioritize remaining
maintenance TMRs
Platform and Release Support
• Challenges
– Trns•port must not be either too far ahead
or too far behind licensee environments
– There is a limited amount of money
available for maintenance, support and
enhancements
– The more platforms and releases we
support, the more it costs
Platform Support
• Mainframe support ended June 30,
2004
• Supported July 1, 2005
– Windows Server 2003
• Supported July 1, 2006
– Oracle 10g
Platform and Release Support
• Support ending on June 30, 2006
– SitePad on Palm OS
– Oracle 8i
– DB2 7.2
• Release versions become unsupported
12 months after the next full release
becomes available
New Warranty Provisions
• July 1, 2003 – 120-day warranty on errors in
previously-working functionality (except for
technology upgrades)
• Functionality working in the June 2005 and
later releases will be warranted in future
releases for as long as the release is
supported, up to 24 months (except for
technology upgrades)
Enhancements
Enhancement Process
• Input
– Trns•port Users Group ballot
– Strategic direction
– Licensee funding
• Managed by Task Force
– TRT appointed whenever practical
• New for FY 2005: Milestone-based
payment for enhancement deliverables
Delivered Since Last Conference
• SiteManager Sampling & Testing
Requirements (Big 5)
• Currency Width Configuration
Changes
• HTTP-enabled DPS
• SiteManager/FieldManager Interface
• Cloverleaf Product Updates Grouping
and Archive
Delivered Since Last Conference
• FY 2004 Estimator Enhancements
– Revamp Printing Architecture
– Set Price Based on Estimate Total Item
Quantity
– Generalize and Extend Browser Support
– Calculate Mobilization as a Percentage of
the Estimate
Delivered Since Last Conference
• SiteManager Marking of Critical Items
Anytime
• Integrated Object Store 2 Into
SiteManager
• Web Enabling CES Parametric
Estimation
2003 TUG Resolution
• “… the TUG requests the Trns•port
Task Force make every effort to
substantially increase its expenditures
in the coming fiscal year in the area of
balloted Trns•port enhancements,
above those budgeted in the current
fiscal year”
Current Enhancement Projects
• Projected delivery December 2004
–
–
–
–
–
–
Trns•port Test Suite Phase II
BAMS/DSS Edit Database
LAS, BAMS/DSS SiteXchange Interfaces
LAS – New Data Validations for LASINIT
LAS – Attach Proposals to a Letting
Integrate Object Store 2 into CES, PES,
LAS, CAS, BAMS/DSS
Current Enhancement Projects
• Projected delivery December 2004
– CAS – SITETIME Record Will Not Accept
a Negative Value
– Rewrite RTF User Guide
– Add RTF to PDF Output in CES, PES,
LAS, CAS, SiteManager
Current Enhancement Projects
• Projected delivery April 2005
– Reference File Sharing, Phase I
• Seeking TRT members – contact Jim Johnson
• Projected delivery May 2005
– FieldNet 2.0
• Projected delivery June 2005
– Projects Should Be Locked in PES When
Proposal Checked Out
– PES/LAS Add Tabbed Folder Functionality
Current Enhancement Projects
• Projected delivery June 2005
– CES Enhancement Bundle
• Display scatter plot and price basis for bid
histories
• Copy tasks at the item level, including
copying to an existing item
• Add bridge ID and other bridge information
Current Enhancement Projects
• Projected delivery June 2005
– 8 BAMS/DSS HREG TMRs
• Documentation on how regressions and
averages are generated for CES
• Documentation on bid history files for CES
and Estimator
• Option to use date work began, rather than
letting date, for bid history calculations
Current Enhancement Projects
• Projected delivery June 2005
– 8 BAMS/DSS HREG TMRs
• New report to identify items/models with
positive quantity coefficients. Include
information on why reverse curve is
generated.
• New report to compare average and
regression prices to ensure that they’re
consistent with each other
Current Enhancement Projects
• Projected delivery June 2005
– 8 BAMS/DSS HREG TMRs
• Provide options for both averages and regressions to
control the exclusion of outliers from the bid history
calculations
• Add an option for the period of time for the regression
model to be different (longer) than that for the
averages
• Create an model profile that contains a FREEPROP
select on the CNDISTR field
• Seeking TRT members – contact Roger Bierbaum
Current Enhancement Projects
• Projected delivery June 2005
– Add Generic Fields
• Item List, Vendor, Vendor Address tables
– FY 2005 Estimator Enhancements
• Undo/Redo, Phase 1
• Build Projects in Item Number Order
• Add Filter to Bid History Catalog
Current Enhancement Projects
• Projected delivery June 2005
– FY 2005 FieldManager Enhancements
• Assign Items to Subcontractors
• FieldManager – Contract Display
• Projected delivery August 2005
– SiteManager Sample Information (Big 15)
• TRACER
– New module – Cost-based parametric estimation
– Projected delivery June 2005
Pending Proposals
• Trns•port Test Suite Phase III
• SitePad Phase II
• TrnsNet
– Secure, reliable information transfer
between modules
Strategic Directions
Strategic Directions
• Next Generation Trns•port
–
–
–
–
–
More than web enabling
Web services architecture (using .NET)
Easier to deploy and support
Easier integration with other systems
Supported by AASHTOWare® Strategic Plan and
IT survey
– Virginia DOT has funded development of an
initial proposal (migrate PES/LAS)
Strategic Directions
• Next Generation Trns•port
Considerations
–
–
–
–
All construction modules
Civil rights
Planning
Recognize that people just want to do
their jobs – architecture is irrelevant
unless they see a concrete benefit
Strategic Directions
• Address executive information needs
• Provide mobile access to Trns•port
information
• BAMS/DSS rewrite
• Continued process improvements
Conclusion
We’re Making Progress
• Trns•port continues to grow, adding new
functionality and progressing with new
technologies
• Remains a robust suite of software modules
• Current licensees adding modules
• Other states and countries are looking at
Trns•port to meet their needs
• Next Generation on the horizon
How You Can Help
• Stay informed
– Information on Cloverleaf
– Task Force meeting minutes
• Keep the Task Force informed
– Keep agency status reports accurate
– Complete AASHTOWare IT survey
– Complete Customer Satisfaction survey
• Keep up with current releases
It’s All About Cooperation
• By continuing to work together, we can
insure that Trns•port will fulfill its
mission
–
–
–
–
–
Trns•port Users Group
Users Group Board of Directors
Trns•port Task Force
AASHTO Staff
Trns•port Contractor
2004 Trns•port Task Force Report
For further information, contact
any Trns•port Task Force member