1. INDOT’s Scheduling / Project Management System (SPMS) Vision & Objectives for Next Generation SPMS Mike Jenkins, Indiana DOT Teresa Franklin, Info Tech, Inc. October 2006

2. Presentation Outline Business Case History of SPMS SPMS Objectives SPMS Joint Development SPMS Product Overview Vision for Next Generation SPMS Alignment with Next Generation Trnsport Opportunities and Next steps

3. Business Case The unpredictable delivery of projects causes inefficient usage of human and economic resources. To achieve agency short term and long range goals, we must improve our program and project management processes to reduce variances in planned activities, schedules, budgets and resources…

4. History of SPMS In production since October 2000 Ongoing annual maintenance, support and enhancements Built by Info Tech using shared code components to align with c/s Trnsport Interfaces to Trnsport CES and MS Project Prototype interface with ESRI GIS ArcView AASHTO considering integration of SPMS with Next Generation Trnsport, pending agency interest and funds

5. SPMS Objectives Provide a comprehensive centralized Program and Project Management Information System Improve project scheduling and planning activities –project concept (pre-proposal) to project closure (open to traffic) and beyond (maintenance) Provide accurate and up to date information for on-time and within budget project delivery Complement Trnsport business lifecycle utilizing AASHTO software standards Interface with other systems –GIS, Land Records, Bridge Inventory, off the shelf project tools, etc.

6. SPMS Joint Development Approach Collaboration among interested agencies through survey, product overview and JAD session Develop and prioritize generic NG SPMS Product Backlog Work Plan and AASHTO Solicitation Agency participation in development and testing Licensing for future maintenance, support and enhancements

7. SPMS Joint Development Benefits SPMS integration with NGT, maintaining unified business rules, architecture and data model Shared funding Reduced costs for agency deployment, support operation, training and integration Reduced maintenance, support, and enhancement costs Provide input on product functionality Decreased dependence on custom programs

8. SPMS Product Overview Vision for Next Generation SPMS

9. SPMS Components

10. SPMS Feature Functions From concept to maintenance –Project management –Project scheduling and tracking –Project estimation and cost tracking –Organization management –Program management

11. SPMS Project Management General - ID, location, key dates, federal, division and district data Status - from concept of a project through post construction National Bridge Inventory (NBI) State route inventory data Utility, railroad, permit, inspection and vendor activities Group, associate projects, and create subprojects

12. SPMS Product Overview

13. SPMS Project Scheduling and Tracking Schedules and tasks based on customizable templates by type of project Tracks activity and sub-activity dates, durations, resources, logs, status Allows activity level security Predecessor and successor relationship adjustment Critical path calculations Interface to MS Project for Graphical Views

14. SPMS Product Overview

15. SPMS Project Estimate and Cost Tracking Cost estimates –All stages - design, land acquisition, environmental assessment –All project phases - ROW, utility, construction Funding –by funding program and amount –by fiscal year –by funding priority and associated appropriation codes Actual costs –voucher/purchase orders –direct expenditures

16. SPMS Product Overview

17. SPMS Organization Management Project and activity assignments by resource –consultants, utility companies, government agencies Position Tracking –General info - name, title, primary address, contact numbers and position –Position vacancies

18. SPMS Program Management Program Manager approval of budget appropriations and notification of over allocations by project phase Maintains funding programs by –federal –state –local –joint Maintains funding amounts by –fiscal year –program –appropriation code

19. Vision for Next Generation SPMS Move to Microsoft.NET development platform –web services, customizable UI and reports Develop generic solution for use by multiple agencies Expand program management Expand resource management Interface with other systems (GIS, Road Inventory)

20. Alignment with Next Generation Trnsport (NGT) Agile, test-driven development Alignment of SPMS with AASHTOWare ® strategic directions Architecture that meets the needs of current and future users Easier integration with non-Trnsport systems Bring value to a broader audience Reduce agency Total Cost of Ownership

22. Opportunities and Next Steps Schedule SPMS JAD hosted by INDOT to refine the product backlog and priorities Determine potential funding and licensing agencies beyond INDOT Obtain TTF and AASHTO approval Establish SPMS TRT and TAG Requirements gap analysis for interested agencies Assess use of c/s SPMS then NG SPMS as phased approach Initial NG SPMS functionality could be on preview site mid 2007

23. SPMS Contacts Jim Nugent, INDOT jnugent@indot.IN.gov jnugent@indot.IN.gov April Schwering, INDOT aschwering@indot.IN.gov aschwering@indot.IN.gov Mike Jenkins, INDOT mjenkins@indot.IN.gov mjenkins@indot.IN.gov Teresa Franklin, Info Tech teresa.franklin@infotechfl.com 352-381-4400 teresa.franklin@infotechfl.com