South Carolina Intelligent Transit System (ITS) Tools for Coordination Overview Presentation to CAL/ACT April 25-26, 200

1. South Carolina Intelligent Transit System (ITS) Tools for CoordinationOverviewPresentation to CAL/ACTApril 25-26, 2007 Presented by Bill Doyle, Information Solutions Group

2. Our Customers & Partners • Citizens who use mass transit • Organizations that provide mass transit • State & Federal agencies administering mass transit programs • Vendors that provide goods and services to mass transit agencies

3. Development of Transit in SC Mid 1970s: Regional Transportation Authority (RTA) legislation passed. This legislation enabled the establishment of the regional transportation authorities that currently operate in the state. Among the first RTAs established in SC were the Pee Dee RTA and the Santee-Wateree RTA. Mid 1980s: The Interagency Council on Public Transportation and the Governor’s Office coordinated public transportation statewide. 1986: Public Transportation Division created within the SC Department of Highways and Public Transportation. 1987: Legislation passed to provide that ¼ of one cent of gasoline tax be dedicated for mass transit purposes. 1993: Division of Mass Transit was created as a result of state government restructuring. Passenger rail development became an additional responsibility of the office. The agency’s name was also changed to the South Carolina Department of Transportation. 2000: Division of Mass Transit became the Mass Transit Office as a result of restructuring within the South Carolina Department of Transportation.

4. South Carolina’s Public Providers

5. Project Conception … Organize & Study Needs • February 1996: SCDOT initiated the SC Mass Transit Technology Committee (MTTC) with SCRA a charter member as a not-for-profit, state-affiliated research organization bringing IT expertise • 1996-1997: The MTTC conducted 9-month survey of South Carolina’s mass transit providers to determine current IT capabilities, resources, desires, and concerns

6. Findings of Initial Study The state’s mass transit providers are under extreme pressure to improve efficiency and reduce costs; however, they: • Lack the resources to adequately research the computer technology marketplace to locate and evaluate the products that best suit their needs; • Lack the capital funds to invest heavily in computing technologies, but even if they had the funds they … • Aren’t sure how to go about implementing these projects.

7. The VTE Vision To design, develop, demonstrate and implement technology solutions which will enable South Carolina’s 20 mass transit providers to: • remotely and cost-effectively share information, resources and software applications, • improve and integrate customer service, and • accomplish their operational and business-related activities in a more timely and accurate manner.

8. The “Virtual Enterprise” • A “Virtual Enterprise” (VE) enables independent, self-sufficient organizations to band together to solve mutual problems and share resources. • The VE appears to the outside world as a single entity with common goals and shared business processes. • The VE members also share knowledge, information and resources – building on the “strength in numbers” concept and making all members more effective.

9. The “Virtual Transit Enterprise” The Virtual TransitEnterprise (VTE) is a way for SCDOT and South Carolina 20 Public Providers to mutually solve transit problems by sharing knowledge, information, and resources. In addition to resource and information sharing, VTE will focus on: • rural transit problems (infrastructure, technology), and • supporting Public Providers in the implementation of Intelligent Transportation Systems (ITS) architecture and components. • Evolve into the Coordination of Transit Services

10. VTE Project Objectives • Maximize participation of all stakeholders in the requirements definition of the VTE solution • Develop and execute an Implementation Plan that will ensure success • Design and implement a VTE solution that will minimize cost, leverage the power of proven information technologies, and potentially yield a return on investment through royalties • Select a systems solution from packages currently in the marketplace which meet SCDOT business requirements • Adhere to National ITS Architectural Standards • Use standard informationand computer technology tools in customizing and expanding the software package More …

11. VTE Project Objectives (continued) • Provide more timely and accurate planning & reporting via electronic means to reduce overhead and turnaround time • Minimize costof implementing computer technology as well as total cost of ownership over the product life cycle • Make available to the smaller providers the same modern resources as large providers • Optimize transportation runs and routes to make transit more flexible and responsive • Increase ridership from the current capability to offer services to support initiatives such as aid to disabled persons and Welfare-to-Work Programs • Coordinate Transit Services (Wherever possible)

12. The Concept Becomes a Project • The Concept for VTE was drafted and briefed to FTA reps and Congressional staffers throughout 1997-- universal consensus was that VTE is urgently needed and that it has national applicability • Strategic partnership established between SCDOT and SCRA in response to DMT’s stated requirement for technical support for IT-related endeavors within the state

13. Overview of the Initial VTE Plan • Comprehensive Needs Assessment, System Design, and Cost-vs.-Benefit Analyses • Establishment of a Transit Technology Lab , Evaluation of Commercial Hardware & Software Products, and Selection of the leading and “Best of Breed” solutions • Installation and Integration of a Distributed Information Sharing System • Networking of all System Assets Via Both Existing and New Telecommunications Resources

14. The Three Point Plan 1 2 Information Sharing with External Entities Grants Management 3 Integrated Scheduling & Dispatching and AVL/GPS 14

15. Phase I Accomplishments • Defined and implemented project governance structure (e.g., Steering Committee, Development Partners, ) • Conducted on-site data gathering surveys at SCDOT and Providers • Carried out VTE system requirements definition, researched alternatives and developed recommendations • Developed 3-Point model for prioritizing and carrying out VTE development • Identified and documented procurements specifications for VTE hardware and software • Developed technology transfer plan outlining a migration plan from today’s systems to a statewide transit model

16. Phase II Accomplishments • Installed $200,000 in computers & printers at providers • Developed code and IT infrastructure for Electronic Reporting/Invoices/Grant Making • Carried out requirements definition for proposed Schedule & Dispatch application • Developed and released the Request-for-Proposal (RFP) for all priority Scheduling & Dispatching components • Coordinated activities with the Comptroller General’s Office in regards to electronic invoicing and e-commerce • Engaged in a Comprehensive Computer Training Program for the 20 Public Transportation providers • Procured Networking Hardware • Brought up Internet access to all Providers • Definition thru implementation of standard fleet management package More …

17. Phase II Accomplishments (Continued): • Completed design & development of intranet database that tracks computer asset inventory, procurement, and support/maintenance activities; work included: • Developed data dictionary, structures, tables, and forms • Database includes all products (hardware, software, equipment, and services) procured for the VTE project to include headquarters & public provider sites.

18. Phase III Planned ActivitiesCompleted • Issued RFP for Schedule & Dispatch software solution • Selected RM Software package & negotiated contract • Developed Project Charter • Developed Detailed Project Work Plan • Completed user requirements definition • Install server-side system (Data Hosted in Atlanta, Ga.) • Carry out server and client system testing • Conduct pilot user training and implementation • Conducted user training for providers • 15 Providers currently using the software • Upgraded all current users with Desktops and Servers • Added Nextel GPS mid-level solution Regionally (1) • Tested the RM Coordination Module Regionally (1)

19. Outstanding Activities • Complete the Web-Site development and Implementation • Complete the start-up of the Statewide Pilot for full blown AVL/MDC in Spartanburg with RM and Mentor • Review other Technologies for integration (IVR, Smart Card, and Emergency Preparedness Components)

20. Some Lessons Learned • Consistent and committed Project Management – with large diverse group of participants, complex interactions involving technical components, with a prolonged development period • Retain committed by-in by the providers – Keep them involved in all communications • The importance of conducting thorough requirement analysis • More of a regionalized approach to thoroughly test system functions prior to a statewide rollout • Project communication platform designed, developed and implemented to keep everyone in the loop, get feedback, organize a user group to communicate individual experiences…ie.. (Website).. etc • Training to be customized for like providers, or have only individualized training by provider when you’re ready to “Go-Live” • Make sure you have a resource of updated GIS data….

21. Thank You! Any Questions?