ACS Lite EconolitePerspective. Outline Development Experience Implementation Outlook.

Slides:



Advertisements
Similar presentations
© Copyrights 1998 Algorithmic Research Ltd. All rights Reserved D a t a S e c u r i t y A c r o s s t h e E n t e r p r i s e Algorithmic Research a company.
Advertisements

Business Development Suit Presented by Thomas Mathews.
AOC Services EPA Analytical Operations/Data Quality Center August 14 th, 2001 US Navy/NAVSEA Training Session.
What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Peek – ACS Lite Deployment Quixote Traffic Corporation Peter Ragsdale August 17, 2006.
U.S. Department of Transportation Federal Highway Administration ACS-Lite FHWA Adaptive Signal Control Systems Raj S. Ghaman, P.E. Team Leader, Office.
Alternate Software Development Methodologies
WMATA Bus ITS Project Update Transit Signal Priority Briefing to the Traffic Signals and Operations Working Group April 21, 2005.
The Facts are In… updated >. Understand how it works See the results data Compare to other options Understand the investment.
MotoHawk Training Model-Based Design of Embedded Systems.
WHY BOTHER TO UNIT TEST Suprinder Pujji. OVERVIEW What is Unit testing Emphasis of Unit testing Benefits of Unit Testing Popular Misconceptions Prevailing.
Council International Study Programs Internet Site Design March 12, 2001.
Gu & Maher University of Sydney, September 2004 DECO2005 Co-Authoring and Changes Management in ArchiCAD Teamwork.
1 SYSTEM and MODULE DESIGN Elements and Definitions.
Chapter 1 Software Development. Copyright © 2005 Pearson Addison-Wesley. All rights reserved. 1-2 Chapter Objectives Discuss the goals of software development.
Fundamentals of Information Systems, Second Edition
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
A Distributed Smart Signal Architecture for Traffic Signal Controls Dustin DeVoe Richard Wall, PhD University of Idaho Moscow, ID USA.
Advanced Evaluation Techniques and Hardware-In- The-Loop Simulation Darcy Bullock, P.E. Professor Purdue University.
OpenEdge BPM. 2 Challenges Process implementation not documented Processes should be explicit – not buried within an application or handled thru “tribal.
Leading Edge Climbing Equipment
Applied Transportation Analysis ITS Application SCATS.
The Pursuit for Efficient S/C Design The Stanford Small Sat Challenge: –Learn system engineering processes –Design, build, test, and fly a CubeSat project.
DYNAMICS CRM AS AN xRM DEVELOPMENT PLATFORM Jim Novak Solution Architect Celedon Partners, LLC
Software Engineering Muhammad Fahad Khan
Chapter 2 The process Process, Methods, and Tools
Class Specification Implementation Graph By: Njume Njinimbam Chi-Chang Sun.
Serial Port to Serial Port Switch Design team May03-11 Abstract: This project requires the design of a new serial port switching matrix to replace a current.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
© 2008 IBM Corporation ® Atlas for Lotus Connections Unlock the power of your social network! Customer Overview Presentation An IBM Software Services for.
1 © 2007 Cisco Systems, Inc. All rights reserved.Cisco Public Remote access typically involves allowing telnet, SSH connections to the router Remote requires.
IBM - CVUT Student Research Projects Remote Control of a Furby Toy with BlueTooth Tomáš Kunc
Chapter 10 Information Systems Analysis and Design
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
Reusability and Effective Test Automation in Telecommunication System Testing Mikael Mattas Supervisor: Professor Sven-Gustav Häggman Instructor: B.Sc.
Chapter 11 Maintaining the System System evolution Legacy systems Software rejuvenation.
Network Management Security
Topics of presentation
Remote Access Using Citrix Presentation Server December 6, 2006 Matthew Granger IT665.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Session 2 Equipment Requirements for Adaptive Traffic Control SCOOT Axel Reissnecker, EAGLE Traffic Control Systems, Austin, TX TRB Workshop on Adaptive.
Software Engineering, Lecture 4 Mohamed Elshaikh.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
1 Adaptive Control Software – Lite (ACS-Lite) Eddie Curtis, P.E. FHWA Resource Center / HOTM NTOC Webcast March 27, 2008.
Software In The Loop Applications for VISSIM TRB Traffic Signal Systems Committee – Simulation Subcommittee Kiel Ova, P.E., PTOE.
CS533 - Concepts of Operating Systems 1 The Mach System Presented by Catherine Vilhauer.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
1 CSCD 326 Data Structures I Software Design. 2 The Software Life Cycle 1. Specification 2. Design 3. Risk Analysis 4. Verification 5. Coding 6. Testing.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
11 CLUSTERING AND AVAILABILITY Chapter 11. Chapter 11: CLUSTERING AND AVAILABILITY2 OVERVIEW  Describe the clustering capabilities of Microsoft Windows.
 Design goals are derived form the non- functional requirements  Every subsystem is assigned to a team and realized independently  During system design,
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Team Members Charles Dunbar Ben Kallal Ankit Patel Peter Purcell Kody Reynolds 1 IRP Presentation Client Lisa Hein-Iowa Natural Heritage Foundation Faculty.
International Telecommunication Union © ITU-T Study Group 17 Integrated Application of SDL Amardeo Sarma NEC Europe Ltd.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
 Many models have been proposed to deal with the problems of defining activities and associating them with each other  The first model proposed was the.
Workflow Stephen Aylward Luis Ibanez. Goals Identify 3 main challenges in this area Identify 3 specific problems that can be solved by a collaborative.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Implementation Review1 Archive Ingest Redesign March 14, 2003.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
® IBM Software Group © 2009 IBM Corporation Essentials of Modeling with IBM Rational Software Architect V7.5 Module 13: Traceability with WebSphere Business.
From the customer’s perspective the SRS is: How smart people are going to solve the problem that was stated in the System Spec. A “contract”, more or less.
The Obermeier Software OPC-SNMP Enterprise Agent 3.0 Obermeier Software SNMP OPC Gateway Features and The S4 Group, Inc. Services Presented by Steve Jones.
Software Defined Networking and OpenFlow Geddings Barrineau Ryan Izard.
Cornell Information Technologies Information Systems/Data Delivery ACTUATE RETIREMENT PROJECT ASPC UPDATE 12/7/06 Objectives Primary - Retire Actuate Reduce.
Business System Development
CS 5150 Software Engineering
Team Skill 6 - Building The Right System Part 1: Applying Use Cases
Presentation transcript:

ACS Lite EconolitePerspective

Outline Development Experience Implementation Outlook

ACS Lite - Development Experience Involved from outset of project – bleeding edge Initial effort focused on architecture and ACS Lite Object development –Preliminary concept of working through Master was not practical due to high development costs and risk. USE of NTCIP and ACS Lite Objects allowed develop teams (Siemens ITS, ITT and Econolite) to work fairly independent of each other –Teams worked well together and open and frequent communications kept developers in the loop. –Initial lab integration with CORSIM went fairly well after all interfaces were understood. No major surprises during field integration

ACS Lite - Implementation Field Test – Gahanna, Ohio –CORSIM lab simulations and Gahanna field tests implemented with ASC/2S controllers. –Modified version of ASC/2S NTCIP 1B software. Modifications implemented support and functionality of required ACS Lite MIB objects. –NTCIP 1202 ASC Objects used by ACS Lite application that were not supported by ASC/2S were handled using ASC/2S MIB objects via ACS Lite API. –Additional detection required for phase utilization data as test intersections were semi-actuated.

ACS Lite - Implementation Communication Architecture –Standard interface maintained for Master (ASC/2M) to Local communications. Allows full functionality of existing closed loop system (Aries). –Separate NTCIP communication path to Local controller for ACS Lite application. Uses ASC/2S Port 2 in test site application. –Separate data rates and interfaces supported on the two communications paths (Gahanna used twisted pair at 1200 & 9600 bps). –User could disable ACS Lite remotely via closed loop system if problems found.

ASC/2S Local Controllers ASC/2M Master Aries Central System ACS Lite Application Full Duplex ECPIP 9600bps/FSK Full Duplex NTCIP 1200 bps/FSK RS 232 PSTN Internet

ACS Lite - Outlook Promising cost effective adaptive control system solution for small systems Good alternate to traditional Traffic Response control in closed loop systems –Typically easier to implement. –May require additional detection for phase utilization and flow profile. –Comparison with well timed Traffic Responsive system needs to be evaluated. Next generation Field Masters will support NTCIP so integration will be simplified –ACS Lite algorithms should be able to run on the same field processor as the Master giving user option of TOD, TR or Adaptive control –Single communications channel to locals

ACS Lite - Outlook Next Steps –Become familiar with software and algorithms after formal handoff by research team. –Port ACS Lite MIB to ASC/3. –Find early adopter opportunities for further field testing/experience and evaluation.