Next Generation Trnsport Presented to the AASHTOWare Trnsport User Group October 14, 2004

Next Generation Trns•portNext Generation Trns•port

Presented to the AASHTOWare Trns•port User Group

October 14, 2004

Where is Trns•port Today?Where is Trns•port Today?

• Mainframe platform recently dropped

• Client/server platform is mature– About 10 years old

• Several agencies need thinner clients– Bridging the gap with Citrix & Terminal Services

• Some progress made towards web– Trns•port Intranet– CES web-based parametric estimation function

Motivations for Next GenerationMotivations for Next Generation

• AASHTOware strategic direction• Expectations of prospective licensees• Increase value for existing licensees

– Reduce agency Total Cost of Ownership– Bring Trns•port value to a broader audience– Enable easier integration with other systems– Provide modern reporting capabilities

• Reduce system boundaries for users• Support a variety of devices (web, handheld, etc.)

Roadmap for Next GenerationRoadmap for Next Generation

• Phase I– PES/LAS functionality– Initial architecture for PES/LAS functions– Forward-looking design for other modules– Agile approach to mitigate risks while

maximizing value delivered

• Later phases – Incrementally address remaining functional

areas

Phase I StatusPhase I Status

• Virginia DOT championing Next Generation– VDOT proposing to fund Phase I– TTF and VDOT reviewing Phase I proposal

• Technical Review Team (users) closely involved throughout development

• Frequent hands-on review and validation

• TRT prioritizes what is to be developed to provide maximum value for budget available

Web Services FoundationWeb Services Foundation

• Encapsulate business logic as “services”

• Service access based on industry standards

• Separate business logic, presentation and data– Enables user interface (most volatile part) to

evolve with less impact on core business logic– Support multiple client types

• Enable integration with rest of enterprise

Current ArchitectureCurrent Architecture

D atab as e

B a tc hA p p lic a tio n

S e rv e r

W ebB ro w s er

W eb F unc tio nS erver

ExternalS ys tem s

T hic kC lients

M o bile &Standalo ne

M o dule s

Next Generation ArchitectureNext Generation Architecture

L e g a cy

D atab as e

W e b S e rvic e s

W ebB ro w s er

U s er Interfac e(W eb S erver)

ExternalS ys tem s

M o bile &Standalo ne

M o dule s

B atc h Applic at io nSe rve r

Some Next Generation QuestionsSome Next Generation Questions

• RTF reports still supported?– Yes, though newer methods will become prevalent

• Screen & report configurability still supported?– Yes, but not necessarily in early phases

• Agency customizations still supported?– Existing client-server “plug-ins” won’t fit, but similar new

capabilities are expected

• How long will C/S platform be supported?– Certainly for several years. There’s no timetable for

phasing it out

Next Generation - SummaryNext Generation - Summary

• Much more than just “web-enabling”– Services-oriented approach offers one solution

to each problem, usable by many components

• Need more modern infrastructure for:– Improved user experience– More modern reporting– Better integration into the enterprise– Reduced Total Cost of Ownership

• Next Generation Trns•port will be added to the Trns•port Long Range Work Plan

Contact InformationContact Information

• AASHTO– Chuck Conley - cconley@aashto.org

• Trns•port Task Force– Paul Neumann - paul.neumann@dot.state.co.us

• Virginia DOT– Joe Pugh - joe.pugh@virginiadot.org

• Info Tech– Bob DeHoff – bob.dehoff@infotechfl.com

Next Generation Trns•portNext Generation Trns•port

Presented to the AASHTOWare Trns•port User Group

October 14, 2004