Planning for Success: Applying Systems Engineering to ASCT Implementation

Transcription

1 Planning for Success: Applying Systems Engineering to ASCT Implementation Eddie Curtis, P.E. Traffic Management & Operations Specialist FHWA Office of Operations & Resource Center

2 Time of Day Signal Timing PEAK 15 Min VPH (vehicles per hour) AM MID PM 12:00 AM 2:00 AM 4:00 AM 6:00 AM 8:00 AM 10:00 AM 12:00 PM 2:00 PM 4:00 PM 6:00 PM 8:00 PM 10:00 PM Time of Day 2

3 Adaptive Signal Control Technology Trigger Event Data Collection 1 Monitor Traffic Modeling / Optimization Implement & Fine Tune Reporting 3 Update Timing 2 Evaluate Performance 3

4 Better, Faster, Smarter o o o o o o o o Shortening Project Delivery Planning & Environmental Linkages Legal Sufficiency Enhancements Expanding Use of Programmatic Agreements Use of In Lieu Fee and Mitigation Banking Clarifying the Scope of Preliminary Design Flexibilities in ROW Flexibilities in Utility Accommodation and Relocation Enhanced Technical Assistance on Ongoing EISs Technology Innovation Warm Mix Asphalt Precast Bridge Elements Geosynthetic Reinforced Soil Safety Edge Adaptive Signal Control Technology

5 Benefits Better Benefits to Road Users & Agencies Travel time reduction 13% - 50% Fuel Consumption 8% - 38% Ongoing performance measurement Smarter Solves problems that are difficult to address with time-of-day and traffic responsive Saves cost of mundane data collection and retiming Faster Reduces retiming intervals from years to minutes

6 ASCT Deployment Status Mid 1980s Dec 2010 Source: Aleksandar Stevanovic, Florida Atlantic University

7 What have we learned Adaptive systems produce substantial benefits over coordinated TOD signal timing Travel time, Delay, Emissions, Congestion, Safety Most effective where demand conditions are Variable and unpredictable Linear Arterials, limited success within tight grids Under Saturated

8 What we know about us

9 Barriers to Adoption Complexity Cost Uncertainty about Benefits 9

10 Available Systems ACSLite BALANCE InSync LA ATCS MOTION OPAC RHODES SCATS SCOOT UTOPIA QuicTrac NWS Voyage Multi-criteria Adaptive Control ACDSS Synchro Green 10

11 Possible Approaches Consumer Reports Evaluate Available Technology Consult with vendors / Distributors Deploy small scale system Evaluate Abandon or Expand Systems Engineering Objectives Needs / Constraints Requirements Design Implement Verification Validation Abandon or Expand 11

12 Successful Deployment Goals well understood Agency describes its needs Positive response to requirements in RFP Requirements are verified Performance objectives are validated over the duration of the life cycle 12

13 What are the Risks - ASCT? Problem could be solved with other strategies Functional Objectives of the system do not align with agency objectives Loss of other critical functions / features Constraints not properly addressed Cost Maintenance 13

14 Other Risk Issues Technology NEW to most Technology still evolving Most systems have very limited track record Documented history of failed ASCT projects (40%+) Significantly increased complexity Extremely dependant upon infrastructure Communications systems Detection Staff Not one size fits all Marketing often exceeds performance 14

15 The Daylight Test 15

16 Procurement Strategies 16

17 The Role of Systems Engineering Understanding the problem Managing risk Projects getting bogged down with shifting requirements Acquisitions being challenged by unsuccessful bidders/proposers/vendors Projects not meeting agency needs + it is mandatory for federal-aid projects

18 Rule Requirements All ITS projects must be developed using a Systems Engineering (SE) analysis The analysis shall be on a scale commensurate with the project scope SE analysis shall address (7) requirements 18

19 Seven Requirements of SE Analysis 1. Identify portions of the regional ITS architecture being implemented 2. Identification of participating agencies roles and responsibilities 3. Requirements definitions 4. Analysis of technology options to meet requirements 5. Procurement options 6. Identification of applicable ITS standards and testing procedures 7. Procedures and resources necessary for operations and management of the system 19

20 Procurement Regulations Proprietary Materials (23 CFR ) Certification of no available competitive product Uniquely fulfills the requirements imposed on the product Achieves synchronization with existing systems Public Interest Finding for proprietary purchase despite alternative available competitive products Limited experimental application Systems Engineering provides justification

21 Systems Engineering Needs Testing Requirements Testing Design & Implementation 21

22 Purpose of SE Model Documents Evaluate need for Adaptive Control Help agencies identify verifiable, needs-driven requirements for evaluating design and implementation choices Model documents greatly reduce systems engineering effort by providing wording and documentation but agencies still must identify their needs

23 Model Document Process Build Requirements Answer questions About the situation About you Select and tailor ConOps statements Select and tailor requirements Evaluate Alternatives Evaluate proposed approaches/products against requirements Solution feasible given constraints? Continue Tailoring Until Solutions Fulfill requirements Are feasible

24 Model Systems Engineering Documents for ASCT During the planning process Define the overall objective of the project Funding During the engineering process Define requirements Procurement 24

25 States Engaging the Process Georgia Meadowlands, NJ Tennessee Puerto Rico Indiana New Mexico Pennsylvania Alaska South Dakota Massachusetts Illinois Idaho Washington Washington, DC Arizona Florida Oregon

26 Influencing Change Innovation is not what the customers does it is what the customer adopts ~ Jesse Glazer CAL-SOUTH Change Agent 26

27 Support FHWA Division Office Eddie Curtis, P.E. Traffic Management Specialist (404)