ADAPTIVE TRAFFIC SIGNAL CONTROL RICHARD W. DENNEY, JR. P.E. 1 December 15, 2011.

Slides:



Advertisements
Similar presentations
FHWA Guidance & Policies on Traffic Analysis James P. McCarthy, PE, PTOE Federal Highway Administration
Advertisements

Eric Graves, P.E. City Traffic Engineer Alpharetta, Georgia
Overview What is the National ITS Architecture? User Services
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
January 8, 2014 FMATS College Road Corridor Study FMATS Technical Committee Update.
Software Quality Assurance Plan
Planning for Success: Applying Systems Engineering to ASCT Implementation TRANSPO 2012 October 29, 2012 Eddie Curtis, PE FHWA Office of Operations / Resource.
Integrated Corridor Management Initiative Overview Brian Cronin Congestion Program Manager ITS Joint Program Office.
Integrated Corridor Management Overview and Status Mike Freitas ICM Initiative Coordinator U.S. DOT ITS Joint Program Office.
Planning for Success: Applying Systems Engineering to ASCT Implementation MOITS – Traffic Signals Subcommitte National Capital Region Transportation Planning.
Joe Olson SW Region Director December 8,  History/Background  Next Steps (Planning & Environmental Linkages (PEL)  PEL Process  Schedule  Questions.
Systems Engineering (SE) for ITS: Using FHWA’s New SE Handbook March 2007.
Lecture #12 Arterial Design and LOS Analysis. Objectives  Understand the factors in arterial design Understand how arterial LOS is determined.
Lecture 13 Revision IMS Systems Analysis and Design.
Urban landbuilding facilitiestransportation networkssystems technology National and Regional ITS Architectures Bart Cima, IBI Group February 26, 2007.
Advanced Public Transit Systems (APTS) Transit ITS CEE582.
Iterative development and The Unified process
Software Evolution Planning CIS 376 Bruce R. Maxim UM-Dearborn.
I n t e g r a t I n g C S S Practitioner Module 3 Module 3: CSS and Livability In Area Wide Planning.
RT-TRACS A daptive Control Algorithms VFC-OPAC Farhad Pooran PB Farradyne Inc. TRB A3A18 Mid-Year Meeting and Adaptive Control Workshop July 12-14, 1998.
Applied Transportation Analysis ITS Application SCATS.
Intersection & Interchange Geometrics (IIG) Innovative Design Considerations for All Users Module 8 Intersection- Interchange Evaluation Process.
U.S. Department of Transportation Pipeline and Hazardous Materials Safety Administration Harold Winnie, CATS Manager (Central Region) Leak detection for.
Best Practices Related to Research Problem Identification, Scoping, and Programming: A Researcher’s View Martin Pietrucha, Director The Thomas D. Larson.
Server Virtualization: Navy Network Operations Centers
CSUN Engineering Management Systems Engineering Management MSE607B Chapter 2, Part II The System Engineering Process.
TSM&O FLORIDA’S STATEWIDE IMPLEMENTATION Elizabeth Birriel, PEElizabeth Birriel, PE Florida Department of TransportationFlorida Department of TransportationTranspo2012.
Using Business Scenarios for Active Loss Prevention Terry Blevins t
ADAPTIVE SIGNAL CONTROL TECHNOLOGY MODEL SYSTEMS ENGINEERING DOCUMENTS 1 December 20, 2012.
1 Approaches for Integrating Systems Engineering into Your Agency’s Business Practices Presented by: Amy Tang McElwain August 2, 2007 Talking Technology.
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
PERT Overview Federal Perspective Annual PERT Workshop February 7-9, 2012 Nevada Site Office Evelyn Landini, Contracting Officer Brookhaven Site Office.
DR O.S ABIOLA DEPARTMENT OF CIVIL ENGINEERING UNIVERSITY OF AGRICULTURE, ABEOKUTA. CVE 505 HIGHWAY & TRANSPORTATION ENGINEERING I.
Siemens Traffic Controls Ltd ITSE99/Standards 1 Traffic Management and Control Workshop on Research and Technological Development for Information Society.
4. GEOMETRIC DESIGN OF HIGHWAYS
Transit Signal Priority (TSP). Problem: Transit vehicles are slow Problem: Transit vehicles are effected even more than cars by traffic lights –The number.
ConSysTec 3 rd Israel ITS AnnualMeeting Israel ITS Architecture Development Rob Jaffe, Ph.D. President, ConSysTec Shenorock, NY USA.
Transportation leadership you can trust. presented to Safety Data Analysis Tools Workshop presented by Krista Jeannotte Cambridge Systematics, Inc. March.
1 Adaptive Control Software – Lite (ACS-Lite) Eddie Curtis, P.E. FHWA Resource Center / HOTM NTOC Webcast March 27, 2008.
MIT - October 1, 2004Jeffrey D. Ensor 1 RSTP Planning for Operations Jeffrey D. Ensor Malaysia Transport Group M.I.T. October 1, 2004.
Adaptive Signal Control Technology: Bringing a Systems Approach to Implementation and Evaluation October 18, 2011 Kevin Fehon, P.E., PTOE DKS Associates.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
The Safety Problem Is Global The Safety Solution Is Local and Personal Business of Saving Lives.
The Fargo/Moorhead Area Interstate Operations Study Opportunities and Planned Activities Presentation for the Mn/DOT Travel Demand Modeling Coordinating.
Implementation: Results from the Using Your Regional ITS Architecture Peer Exchange Network Workshop Mac Lister FHWA Resource Center ITS America Annual.
1 V&V Needs for NextGen of 2025 and Beyond A JPDO Perspective Maureen Keegan JPDO Integration Manager October 13, 2010.
Systems Engineering “Understanding Where it Fits in Your Agency” a session in fhwa’s Systems Engineering t3 series aug. 02, 2007.
Smart Information for a Sustainable World True Adaptive Signal Control A Comparison of Alternatives Technical Paper # Presentation to the 18 th World.
Regional Concept for Transportation Operations: An action plan to address transportation operations in Southeast Michigan Talking Technology & Transportation.
IntegratedCorridorManagement 1 Integrated Corridor Management Overview and Activities Jeff Lindley Director, Office of Transportation Management FHWA February.
Integrated Corridor Management Initiative ITS JPO Lead: Mike Freitas Technical Lead: John Harding, Office of Transportation Management.
COUNTY ROAD 517 Improvements from State Highway 172 to Howe Drive DECEMBER 16, 2015 At Tribal Multipurpose Facility.
Integrated Corridor Management Initiative Dale Thompson Transportation Specialist Office of Operations R&D May 4, 2005.
Improving Communication and Coordination in Highway Work Zones Kimberly Peters Incident Management Program Director, INDOT Event Date.
Geometric Design: General Concept CE331 Transportation Engineering.
Federal Regional ITS Architecture Requirements 1 T3 Session Federal Requirements for Regional ITS Architectures.
Livingston County Transportation Connectivity Plan Final Report December 2013.
Meadowlands Adaptive Signal System for Traffic Reduction December 2011 Leo Almanzar P.E., P.P., P.T.O.E. Hong Yuan, P.E., P.T.O.E.
FHWA: Revision of Thirteen Controlling Criteria for Design; Notice for Request and Comment. Comments Due: December 7, 2015 Jeremy Fletcher, P.E., P.S.M.
AASHTO CV/AV RESEARCH NCHRP (98) NCHRP
Chapter 2 Signs, Signals, and Roadway Markings Start working on the Start working on the 8 questions on page 39! 8 questions on page 39!
Development of Traffic Simulation Models Course Instructors: Mark Hallenbeck, Director, UW TRAC Tony Woody, P.E., CH2M HILL Offered By: UW TRANSPEED xxxxx,
 System Requirement Specification and System Planning.
Project Management Team Meeting #3
The Implementation Experience of CTCS-3 Train Control System and the Implication of “Go Global” of China High-speed Railway Good morning. October 2017.
Draft Transportation Element September 6, 2017
First Article Inspection
Presented by (Abdisamad Abdullahi Abdulle)
PSS verification and validation
Presentation transcript:

ADAPTIVE TRAFFIC SIGNAL CONTROL RICHARD W. DENNEY, JR. P.E. 1 December 15, 2011

Agenda The Risky ASCT Marketplace Federal Funding and the CFR What is Systems Engineering? Using the SE Model Docs to Efficiently Create SE Deliverables 2

ASCT Is Not Easy Many prior ASCT projects abandoned. Why? ASCT products vary… –Different objectives –Different configurations –Different business models –Different sustainability requirements New products emerging continuously Strong marketing environment Lots of visibility and scrutiny

Many Products—All Different ACSLite BALANCE InSync LA ATCS MOTION OPAC RHODES SCATS SCOOT UTOPIA 4 QuicTrac NWS Voyage Multi-criteria Adaptive Control KLD Intelight Synchro Green System of the Month

Example Product Objectives Balance phase utilization—fair distribution of green Minimize arrivals on red—improve progressed flow Minimize queue-time density—serve the most cars waiting the longest Minimize combination of stops and delay—delay-offset optimization

Configurations—Operational Work within existing coordination parameters Override or ignore controller or system coordination Provide centralized adaptive operation Provide localized adaptive operation Optimization suited to grid networks or arterial streets?

Configurations—Architecture Built into central system Works in parallel to central system Built into local controller Separate local-cabinet processor Replaces field master Built into field master Uses system-to-controller interface Bypasses system-to-controller interface

Configurations—Infrastructure Separate processor may be required Varying interface to controllers/systems Varying communications requirements Detection –Existing detection –Special detection Pedestrians, emergency vehicles, transit vehicles, railroad crossings, interfaces with adjacent systems and operations, and other realities

Buying, Maintaining, and Operating High-capital, designed for large-scale networks Low-capital, designed for small-scale networks Agency-provided operations –Operations resources –Maintenance capability Supplier-provided operations –Accountability –Responsiveness –Term –Sustainability

Summary So Far… Product market diverse and poorly understood Agency objectives, strategies, and requirements often poorly understood or articulated Usual product selection approaches risky High scrutiny by vendors, elected officials and auditors All ASCT projects impose high technological risk

How Will We Meet This Goal? By December 2012, The EDC / ASCT tools are used to guide the implementation or programming of 40 ASCT systems. EDC / ASCT tools –Systems Engineering Process –SE Workshop –SE Model Documents 11

The Role of Systems Engineering Understanding the problem Managing risk –Poorly articulated needs and requirements –Acquisitions being challenged by bidders/proposers/vendors/auditors –Projects not meeting agency needs –Schedule and budget overruns as agencies and vendors understand needs and requirements too late (and it is mandatory for federal-aid projects)

13 23 CFR 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

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 14

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 Analysis can provide justification

What Is Systems Engineering?

Eisenhower Wants to Build Roads How fast Germans moved armies during WWII America embroiled in the Red Scare Post-war prosperity presented an opportunity 17

How We Would Use A New Roadway Network Move armies quickly Move people, goods & services efficiently 18

What Slows Armies Down? Intersections Narrow roads Tight curves Incomplete network 19

Basic Requirements Limited access Wide lanes with shoulders Divided highway High design speed Comprehensive network 20

Functional Requirements The highway shall have no at-grade crossings. The highway shall separate the two directions of travel. The highway shall accommodate vehicles traveling at 70 mph. The highway shall have 12’ foot lanes. The highway shall have vertical clearance of 16.5’. The highway shall have maximum grade of 6%. The highway network shall comprise principal east- west and north-south routes. 21

Did Eisenhower know anything about building roads? Do road builders know anything about moving armies? Do they need to? 22

Verification and Validation Did the road get built right? Did we build the right roads?

Systems Engineering Needs Testing Testing Requirements Design & Implementation 24

Mitigating Risk Designing the roads incorrectly Designing the wrong roads Spending too much Taking too long to build Responding to challenges 25

SE For ASCT Projects Too much work to develop from scratch Model documents therefore make it much easier to create: –Concept of Operations –Requirements –High Level Design –Verification Plan –Validation Plan 26

Concept of Operations The story of what the agency will DO: –Includes viewpoints from stakeholders –Written from the perspective of the system operator/maintainer/user –Defines high-level system concept to consider alternatives –Provides the basis for requirements –Provides criteria for validation 27

Requirements Describes what the system must do: –Necessary: Must be linked to a need in the ConOps –Clear: May get challenged! –Complete: Are all needs addressed? –Correct: Are needs addressed correctly? –Feasible: Is it possible? –Verifiable: Can you demonstrate it? Can you prove it? 28

Testing Verification Plan –Verifies that every step, if done correctly, will fulfill the requirements. Validation Plan –Validates that every step, if done correctly, will provide a system that meets user needs. 29

How To Use The Systems Engineering Model Documents

Model Systems Engineering Documents for ASCT Systems Purpose of the document Document organization and how to use it 31

Purpose of SE Model Documents Evaluate need for Adaptive Control Usual SE process too much work for small projects… …but small projects still impose big risk to small agencies Model documents greatly reduce effort by providing wording and documentation… …but agencies still must identify their needs

Basic Organization Guidance—How to do systems engineering for ASCT Table of Concept of Operations Statements –ConOps statements linked to Guidance section –ConOps statements linked to requirements Table of Requirements –Requirements linked to ConOps statements Templates for Verification and Validation Plans

First Steps Read the guidance—straight through Work through the ConOps Statements –Choose the statements that fit –Scratch out the statements that don’t fit –Don’t change wording at this time –Fill in required blanks –Write required paragraphs

35

Concept of Operations Template & Questions Purpose Scope Referenced Documents 4.0 – Background Network Characteristics Traffic Characteristics Signal Grouping Land Use Operating Agencies Existing Architecture / Infrastructure Limitations and proposed changes 36

Alternative Non-Adaptive Strategies (ConOps Ch. 5) (Guidance Section 4.5) Traffic Responsive Complex Coordination Features Variable Phase Sequence Coordinate alternate approaches Late Phase Introduction 37

Envisioned Adaptive Operations (ConOps Ch. 6) (Guidance Chapter 4.6) Objectives –Pipeline – Access Equity –Manage Queues –Variable Strategies / Scenarios 38

Adaptive Operational Scenarios Operational Scenarios for Traffic Events Using an Adaptive System (Chapter 11 of the Concept of Operation) Guidance Section

Specific Adaptive System and User Needs (ConOps Ch. 7) (ConOps Questions) Support Mobility –Vehicle –Pedestrian –Transit Provide Measurable Improvements –Delay –Travel Time –Safety 40

Envisioned Adaptive System Overview (Chap 8) Network Characteristics Type of Adaptive Operation Crossing Arterial Coordination Institutional Boundaries Failure Modes ……… 41

Operational & Support Environment ConOps Chapter 9 & 10 Guidance Chapter 4.9 &

Build Requirements For each selected ConOps statement: –Find referenced requirement –Select referenced requirement Scratch out unselected requirements

Review Requirements Are selected requirements not needed? –Does ConOps statement describe you? Check it! Are unselected requirements needed? –Did you miss a ConOps statement? Check it! Anything missing? –Write new ConOps statement and associated requirements. Don’t change requirement without changing ConOps statement

Design/Implementation Model docs now; product research later Use requirements in procurement process –Requirements are essay questions –What if no product fulfills requirements? –What if only one product fulfills requirements? –What if I’m doing more than one system? With different requirements?

Proving It Verify design fulfills requirements Verify implementation conforms to design Validate system supports operations

Verification A Plan—How will the agency/vendor demonstrate that –The design will fulfill all requirements? –The selected technologies/products fulfill all requirements? –The installed systems fulfill all requirements? 47

Validation Another Plan—How will the agency/vendor demonstrate that –The design will operate as described in ConOps? –The selected technologies/products will support agency activities described in ConOps? –The complete system supports agency activities as described in ConOps? 48

Contact Information Leo Almanzar P.E., P.P., P.T.O.E. New Jersey Meadowlands Commission James Fritz Brogdon, P.E. Volkert & Associates, Inc. Eddie Curtis, P.E. FHWA Resource Center in Atlanta, GA Richard W. Denney, Jr., P.E. FHWA Resource Center in Baltimore, MD Paul Olson, P.E. FHWA Resource Center in Lakewood, CO Cindy Shell Volkert & Associates, Inc. Hong Yuan, P.E., P.T.O.E. New Jersey Meadowlands Commission

Questions?