2005 Trns•port Task Force Report2005 Trns•port Task Force Report

Trns•port Users Group ConferenceNovember 6, 2005

Daytona Beach, Florida

Paul Neumann, Colorado DOTChair, Trns•port Task Force

Presentation OutlinePresentation Outline

• Trns•port Task Force Overview

• Strategic Directions

• Maintenance and Support

• Enhancements & New Development

• Conclusion

Trns•port Task Force OverviewTrns•port Task Force Overview

Trns•port MissionTrns•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 LicenseesTrns•port Licensees

AlaskaHawaii

New Brunswick

39 State Agencies, 1 Canadian Province, FHWA Federal Lands Highways, District of Columbia DOT, Pennsylvania Turnpike

Trns•port Implementation Statushttp://www.cloverleaf.net

Trns•port Task Force MembersTrns•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• Tim Lindberg, South Carolina

Trns•port Task Forcehttp://www.cloverleaf.net

Task Force Meeting ParticipantsTask Force Meeting Participants

• Regular participants at our meetings:– Chuck Conley, AASHTO Staff– Shirley Daugherty, Nebraska, SCOJD Liaison– John Morden, Florida, T&AA Liaison– Jim Ferguson, Nebraska, TUG Chair– Tom Rothrock, Info Tech– Margaret Andraka, Info Tech– Teresa Franklin, Info Tech

Trns•port Task Force Meeting Minuteshttp://www.cloverleaf.net

Task Force ResponsibilitiesTask Force Responsibilities

• Strategic Direction– Define long term vision– Establish product objectives– Determine annual goals– Develop marketing plan

AASHTOWare® Policies, Guidelines and Procedureshttp://www.aashtoware.org

Task Force ResponsibilitiesTask 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’s MSE operations– Determine operating platforms– Evaluate need for new modules

AASHTOWare® Policies, Guidelines and Procedureshttp://www.aashtoware.org

Trns•port Task Force OperationsTrns•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 Operationshttp://www.cloverleaf.net

Trns•port Task Force PositionsTrns•port Task Force Positions

• Seeking individuals who are interested in serving on the Task Force

• One opening per year, on average

• Submit resumes anytime

• Must have approval from agency

Strategic DirectionsStrategic Directions

Strategic GoalsStrategic Goals

• Business Goals– Align with the AASHTOWare® strategic direction– Eliminate unnecessary boundaries between and

within systems– Bring Trns•port’s value to a larger audience

• Executives, non-DOT personnel, mobile access

– Reduce agency Total Cost of Ownership (TCO)• Implementation, support, integration

Strategic GoalsStrategic Goals

• Technical and Architectural Goals– Provide architecture that meets the needs of

current and future customers• Web-enabled, with loosely coupled tiers

– Build a consistent, unified data model– Enable easier integration with other systems

Achieving Strategic GoalsAchieving Strategic Goals

• Web-enabling has been a strategic goal for several years– But simply web-enabling doesn’t go far enough– Even with a web interface, current architecture

would be too expensive to enhance and adapt to new technologies

– As technology matured, it became clear that a rewrite was necessary

Next Generation Trns•port (NGT)Next Generation Trns•port (NGT)

• More than web enabling• Web services architecture (using .NET)• Unification of data model, business rules, security

administration, look and feel• Easier to deploy and support• Easier integration with other systems• Supported by AASHTOWare® Strategic Plan and

IT survey

Maintenance and SupportMaintenance and Support

Maintenance and Support FocusMaintenance 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

Trns•port Modification Requests (TMRs)Trns•port Modification Requests (TMRs)

• Can be either maintenance or enhancement• Maintenance TMR priorities are verified by

the TTF– Urgent – can’t perform critical business function– Critical – prevents implementation or upgrade– High – major inconvenience– Medium – minor inconvenience– Low – nuisance

Maintenance During NGT DevelopmentMaintenance During NGT Development

• To maximize funds available for NGT:– Only Urgent and Critical maintenance TMRs will

automatically be funded for correction– TTF will evaluate high priority maintenance

TMRs on a case-by-case basis to determine whether a correction will be provided

TMR Policyhttp://www.cloverleaf.net

Maintenance During NGT DevelopmentMaintenance During NGT Development

• To maximize funds available for NGT:– Medium and low priority maintenance TMRs

won’t be corrected unless TTF approves an exception

– No formal TMR review this fiscal year

TMR Policyhttp://www.cloverleaf.net

Platform and Release SupportPlatform 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

Client/Server Platform SupportClient/Server Platform Support

• Supported July 1, 2005– Windows Server 2003

• Supported July 1, 2006– Oracle 10g

Trns•port Platform Component Statushttp://www.cloverleaf.net

Client/Server Platform SupportClient/Server Platform Support

• Support ending on June 30, 2006– SitePad on Palm OS– Oracle 8i– DB2 7.2– Pocket PC 2002

• Support ending on June 30, 2007– Sybase Adaptive Server Enterprise– Windows 2000

Trns•port Platform Component Statushttp://www.cloverleaf.net

Release SupportRelease Support

• Release versions become unsupported 12 months after the next full release becomes available

Warranty ProvisionsWarranty Provisions

• Regression failures (things that used to work)– Functionality working in the June 2005 and later

releases is warranted in future releases for as long as the release is supported, up to 24 months (except for technology upgrades)

• Initial release of NGT will have a 300-day warranty

Enhancements & New DevelopmentEnhancements & New Development

Enhancement & New Development ProcessEnhancement & New Development Process

• Input– Trns•port Users Group ballot– Strategic direction– Licensee funding

• Managed by Task Force– TRT appointed whenever practical

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered December 2004– Trns•port Test Suite 1.0a– 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

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered 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

• Delivered March 2005– Expedite x.509 Certificate Authority Enhancement– Expedite PGP Toolkit upgrade

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered March 2005– SRS for Reference File Sharing (ties into Next

Generation Trns•port data model unification)

• Delivered June 2005– FieldNet 2.0– Projects Should Be Locked in PES When

Proposal Checked Out– PES/LAS Add Tabbed Folder Functionality

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered June 2005– CES Enhancement Bundle

• Display web-based 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

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered June 2005– 9 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

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered June 2005– 9 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

• Provide more control of how date is used in the HREG model

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered June 2005– 9 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

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered June 2005– Add Generic Fields

• Item List, Vendor, Vendor Address tables

– Estimator Enhancements• Undo/Redo function requirements and design• Build Projects in Item Number Order• Add Filter to Bid History Catalog

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered June 2005– FieldManager Enhancements

• Assign Items to Subcontractors• FieldManager – Contract Display

– Modifications to LAS Pass to SiteManager process

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered July 2005– Next Generation Trns•port Mobilization Effort

• Project Methodology Document• Technical Standards and Tools Document• Test Driven Approach Document• User Input Planning Document

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered August 2005– SiteManager 3.6a

• Sample Information (Big 15)• Sample Information Window Access Lock• Superpave Mix Design Enhancement• Search Window - Item code to display with line item

number• Integrate new GetTemplate• SMSI Lock Sample, Generic Field Func., &

Attachments

Delivered Since Last ConferenceDelivered Since Last Conference

• Delivered September 2005– Expedite 5.6a

• Sub Folders and Conditional Bid Withdrawal• Add Generics to print sequences• Add support for radio buttons

Enhancements During NGT DevelopmentEnhancements During NGT Development

• To maximize funds available for NGT:– TTF will not fund enhancements to the AASHTO-owned

modules during NGT development, unless TTF determines an exception is warranted for the benefit of the Trns•port community

• Ballot is still very important– TTF will use as an indicator of priorities for NGT

development

• Agencies may still fund TMRs

Current Enhancement EffortsCurrent Enhancement Efforts

• TRACER, Phase 1– New module – Cost-based parametric

estimation– Nearly ready for delivery

• Estimator– 6836 – ‘Undo/Redo’ function

Current Enhancement EffortsCurrent Enhancement Efforts

• FieldManager– 6299 – Add Report Customization Functionality

in FieldManager– 8776 – Enable Site Time tracking in FieldBook

IDRs

• SiteManager– 8135 – Enhancements to Stockpile Materials

(allow update of conversion factor)

Current New Development EffortCurrent New Development Effort

• Next Generation Trns•port, Phase 1– Development began in July 2005– Functionality equivalent to client/server PES/LAS– Build necessary architecture– Begin reengineering data model– Agile development methodology– Continuous oversight by TTF– Agency migration impact assessment

Next Generation Trns•port RoadmapNext Generation Trns•port RoadmapAASHTO Fiscal Year

Phase Increment 05-06 06-07 07-08 08-09 09-10

1 Proposal, Letting and Award

2 Bid Analysis

3 Materials Management

3 Construction and Materials Field Reporting

4 Contract Monitoring and Reporting

5 Construction Management

6 Cost-based and Parametric Estimation

This plan is tentative, and is subject to change due to factors such as funding availability.

Pending New DevelopmentPending New Development

• Civil Rights and Labor Management System (CRLMS)– To be built as a new module using NGT

architecture

• NGT Materials preliminary work

• TRACER, Phase 2

ConclusionConclusion

We’re Making ProgressWe’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 Trns•port development underway

How You Can HelpHow You Can Help

• Stay informed– Information on Cloverleaf– Task Force meeting minutes

• Keep the Task Force informed– Cloverleaf NGT Message Board– Keep agency status reports accurate– Complete surveys distributed by TTF

• Keep up with current releases

It’s All About CooperationIt’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

2005 Trns•port Task Force Report2005 Trns•port Task Force Report

For further information, contact any Trns•port Task Force member