2. Project Background  Several recent initiatives have helped transform the system in positive ways – New brand and logo – New website and real-time bus arrival information – New bus maintenance facility  Improvements have not gone unnoticed – 40% ridership growth in last three years – Recognized as best system of its size by APTA  More improvements to come – 30 new buses on order – Modern fareboxes / modern payment options – Installation of hundreds of bus stop signs  Time is right to focus on service

3. COA Study Goals  Identify strengths and weaknesses of existing system – Ridership – Productivity – Unmet Service Needs  Recommend service improvements – Serve existing riders better – Attract new riders – Improve over-all system productivity

4. Guiding Principles  Service Should be Simple: −For people to use transit, service should be designed so that it is easy to use and intuitive to understand  Service Should Operate at Regular Intervals: −In general, people can easily remember repeating patterns, but have difficulty remembering irregular sequences.  Routes Should Operate Along a Direct Path: −The fewer directional changes a route makes, the easier it is to understand. Circuitous alignments are disorienting and difficult to remember.  Routes Should be Symmetrical: −Routes should operate along the same alignment in both directions to make it easy for riders to know how to get back to where they came from.  Routes Should Serve Well Defined Markets: −Routes should include strong anchors, but should avoid unintended service duplication.  Service Should be Well Coordinated: −At major transfer locations, schedules should be coordinated to the greatest extent possible to minimize connection times for the predominant transfer flows.

5. Guiding Principles  Service Should Operate at Regular Intervals: – In general, people can easily remember repeating patterns, but have difficulty remembering irregular sequences.

6. Guiding Principles  Routes Should Operate Along a Direct Path: – The fewer directional changes a route makes, the easier it is to understand. Circuitous alignments are disorienting and difficult to remember.

7. Guiding Principles  Routes Should be Symmetrical: – Routes should operate along the same alignment in both directions to make it easy for riders to know how to get back to where they came from.

8. Guiding Principles  Routes Should Serve Well Defined Markets: – Routes should include strong anchors, but should avoid unintended service duplication.

9. Guiding Principles  Service Should be Well Coordinated: – At major transfer locations, schedules should be coordinated to the greatest extent possible to minimize connection times for the predominant transfer flows.

10. Guiding Principles  Service Should be Simple: −For people to use transit, service should be designed so that it is easy to use and intuitive to understand  Service Should Operate at Regular Intervals: −In general, people can easily remember repeating patterns, but have difficulty remembering irregular sequences.  Routes Should Operate Along a Direct Path: −The fewer directional changes a route makes, the easier it is to understand. Circuitous alignments are disorienting and difficult to remember.  Routes Should be Symmetrical: −Routes should operate along the same alignment in both directions to make it easy for riders to know how to get back to where they came from.  Routes Should Serve Well Defined Markets: −Routes should include strong anchors, but should avoid unintended service duplication.  Service Should be Well Coordinated: −At major transfer locations, schedules should be coordinated to the greatest extent possible to minimize connection times for the predominant transfer flows.

11. Other Factors Considered  Market Analysis −Population and Employment density −Population characteristics −Land-use characteristics −Regional travel patterns  Service Analysis −Ridership −Productivity −On-time Performance  Stakeholder Input −Riders −Non-riders −Staff −Stakeholders

12. Market Analysis

13. Service Analysis

14. Stakeholder Input

15. Development of Service Alternatives  Approach: – Follow guiding principals – Incorporate technical findings and stakeholder input – Provide options Scenario I: Maximize Weekday Service Scenario II: Add Sunday Service Scenario III: Hybrid Approach

16. Development of Service Alternatives  Coverage: Current Network

17. Development of Service Alternatives  Coverage: Proposed Network

18. Development of Service Alternatives  Coverage: Proposed Network

19. Development of Service Alternatives  Coverage:

20. Development of Service Alternatives  Coverage:

21. Development of Service Alternatives  Coverage: