Kansas DOT Experience with web Trnsport Preconstruction

1
Kansas DOT Experience with web Trnsport
Preconstruction

• Fran McAdoo, Kansas DOT
• Application Programmer II
• Bureau of Computer Services
• (Operations Unit)

2
Topics

• KDOT involvement
• Hardware/software specifications
• KDOT web Trnsport environment
• KDOT participation
• Activities completed
• Issues and resolution
• Ongoing and next steps
• Overall experience
• KDOT Goals

3
Why Did Kansas Get Involved?

• KDOT uses only a subset of current PES/LAS
  functionality
• KDOT is still on the mainframe with Trnsport
  PES/LAS and BAMS/DSS
• KDOT was looking at options for web-based
  preconstruction application

4
How Did Kansas Get Involved?

• Industry standard web platform
• Based on Microsoft .NET foundation
• Unified data, business, and security models and
  look-and-feel
• Agency customizability extensibility
• Customize user interface, reports, database
• Integrate agency-developed programs

5
How Did Kansas Get Involved? Continued

• TTF approached KDOT to see if we were interested
  in previewing web Trnsport Preconstruction
• KDOT agreed with the TTF to preview web Trnsport
  before the production release
• Gave KDOT the ability to see if web Trnsport
  would work in our business environment
• Allowed KDOT to assist with development of web
  Trnsport by testing it in an agency environment

6
How Did Kansas Get Involved? Continued

• TTF, Info Tech, and KDOT communicated
  expectations and coordinated the preview period
• Start date January 22, 2007
• End date on-going

7
What Resources At KDOT Have Been Involved?

• Assistant Bureau Chief/Trnsport EUD
• Application Developer Supervisor
• Operations Support (Application Developer)
• IIS Support Bureau of Computer Services
• Database Administrators
• Current Trnsport Management and Users

8
KDOT web Trnsport Hardware Specs

• 2 servers (database and web)
• HP ProLiant DL385 server
• AMD 250 Opteron 2.4GHz
• 4GB memory

9
web Trnsport Web Server Specs

• Windows Server 2003, Standard edition SP 1
  configured as an Application Server to include
  IIS 6 and .asp file extensions
• .NET Framework 2.0
• Oracle database drivers

10
web Trnsport Database Server Specs

• Window Server 2003, Standard edition SP 1
• web Trnsport database server has Oracle 10g
  Version 10.2.0.1 32 bit

11
KDOT web Trnsport Environment

• Test - delivered acceptance test validation area
• generic installation of web Trnsport - no KDOT
  customizations
• Development - KDOT specific web Trnsport
  validation area
• customized development area - KDOT customizations
  and testing applied

12
KDOT web Trnsport Environment

• Production KDOT production area
• Future environment when KDOT moves to production
  with web Trnsport

13
How Has KDOT Participated In Development By
Previewing web Trnsport?

• Participating in benchmark testing to resolve
  application issues before first release
• Providing feedback to the TRT, TTF, and the web
  Trnsport development team
• Submit call tickets
• Questions
• Errors found in application
• Functionality gaps
• Requests for functionality

14
What Activities Has Kansas Completed?

• Completed KDOT project life cycle from estimation
  through award in web Trnsport
• Monthly updates of web Trnsport
• Run web Trnsport automated acceptance test suite
  with each installation
• Currently there are 90,000 tests

15
Issues Encountered During Preview

• Initial installation issues location data
  conflict
• Resolution KDOT database creation template had
  default Oracle Spatial table with same name as
  web Trnsport table (renamed the web Trnsport
  table to LOCATION_POINT)

16
Issues Encountered During Preview

• Acceptance tests - not completing successfully
• Resolution Info Tech identified two different
  issues
• KDOT does not have DSS estimation web service
• report tests used EST date/times

17
Issues Encountered During Preview

• Performance slow retrieval of large data lists
• Example
• Sprint 19 (first KDOT install) - 7 minutes to
  retrieve 17,252 records from ITEMLIST
• Sprint 20 - 3 minutes to retrieve 17,263 records
  from ITEMLIST
• Sprint 26 30 seconds to retrieve 18,142 records
  from ITEMLIST

18
Issues Encountered During Preview

• Resolution Data retrieval performance improved.
  Also, user interface can be modified to display
  fewer records at a time. (Does the user really
  need to view all 17,000 records at once?)

19
Issues Encountered During Preview

• Missing acceptance test sprint 21 export to
  expedite had errors
• Resolution Info Tech identified error and
  provided KDOT with an emergency fix in
  twenty-four hours and the gap in test coverage
  was corrected
• Because of Info Tech having developed both
  modules, they had access to both sides which
  helped in coming to a quick solution.

20
Issues Encountered During Preview

• Problems with Import/Export to Expedite
• ResolutionBacklog items created and have been
  added to sprints

21
How Issue Resolution Has Been Handled

• Identify issue/concern
• Create call ticket and submit to Info Tech
• 63 call tickets submitted as of September
• Info Tech researches and creates backlog item (if
  applicable)
• Info Tech updates the call ticket so KDOT can
  review status

22
How Issue Resolution Has Been Handled Continued

• Info Tech presents results and recommendations to
  TRT during weekly TRT meeting
• TRT prioritizes the backlog item (sprint
  development cycle and release)
• KDOT has a weekly support meeting with Info Tech
  - open and active communication on progress of
  issue resolution

23
Ongoing/Next Steps For KDOT

• Identifying KDOT reports that web Trnsport can
  replace
• Identifying KDOT reports that need to be modified
  to work with web Trnsport
• Identifying current processes that will become
  obsolete by moving to web Trnsport
• Identifying interfaces to external applications
• Validate data mapping to BAMS/DSS

24
Ongoing/Next Steps For KDOT Continued

• Customizing screens in web Trnsport
• Changing existing labels
• Adding KDOT specific fields to windows
• Customizing field validations (required fields,
  etc.)
• Customizing existing web Trnsport reports to
  meet KDOT requirements
• Using report customizer utility provided with web
  Trnsport
• User has ability to change report layout and
  labels using drag-and-drop actions
• Very little training needed to use

25
Ongoing/Next Steps For KDOTContinued

• Rewrite KDOT specific reports for web Trnsport
• Volume testing
• measuring performance
• Security testing

26
Ongoing/Next Steps For KDOTContinued

• Establishing KDOT specific regression tests
• run tests after each sprint install that will
• cover the KDOT project life cycle
• Generate prices
• Stand alone DSS
• Training

27
Overall Experience

• With Agile - KDOT testers are able to get short
  turn around on issue resolution following this
  method
• Rewarding experience to see immediate results and
  changes to application
• Like the ease of customization of windows as well
  as reports
• Also like the gui screens vs green screens from
  mainframe.

28
Overall Experience Continued

• Like the web Trnsport online help
• Like sprint changes that are posted to Cloverleaf
  and preview site
• KDOT has been pleased with the open and constant
  communication with Info Tech and the TTF
• Believe that web Trnsport will meet KDOT
  business requirements

29
KDOT Goals

• Goal is to move to web framework. As outstanding
  issues are completed. We will move to production.

30
Useful Link

• Link to web Trnsport portal
• http//www.cloverleaf.net/NGT
• Whats there?
• web Trnsport logical architecture paper
• web Trnsport preview site
• Preconstruction product backlog
• Detailed information about web Trnsport, Agile,
  and web Trnsport Forum
• Hardware and software requirements

31
Kansas DOT Experience with web Trnsport
Preconstruction

• QUESTIONS?