This view includes a library of systems engineering examples collected from real ITS projects, testimonials from practicioners on their use of systems engineering, three illustrative example projects that are used in the Systems Engineering Guidebook, and several case studies from around the country.
Library of Examples
||This site includes a library of systems engineering examples that have been collected from all types of ITS projects. This is the place to go if you are interested in seeing Systems Engineering Management Plans, Concepts of Operation, Requirements Specifications, and other documents that have been developed for ITS projects.
Systems Engineering Testimonials
||As many in the ITS industry begin to adopt systems engineering processes, we are beginning to hear feedback from practicioners on the benefits of systems engineering. Systems engineering testimonials provide insight into how systems engineering has provided value for some early adopters in the transportation industry.
The systems engineering approach must be tailored to address the specific complexities and risks of each ITS project. To illustrate tailoring, the Systems Engineering Guidebook describes the degree of systems engineering that would be applied to three example ITS projects that illustrate the range of ITS projects that might be encountered.
A guide to the level of effort required for each phase of the project is also provided. It should be noted that these are
estimates and that each project, even if they are similar to the ones listed, will need to be evaluated on its own merits.
The following example projects are defined:
Project Example 1
Adding field elements to an existing system - this example adds changeable message signs to an existing system.
The point of this example is to show that cost is not necessarily a driver in the amount of systems engineering needed. A 10 million
dollar project may need less systems engineering than a $500K project. Also, this example applies to field cameras, ramp metering,
intersection controllers, or detection.
Project Example 2
Adding new functionality to an existing system - this example builds on example 1 and adds another requirement for sharing control of the signs with a partnering agency. In this example, the existing control software
was not designed for this requirement and injected typical institutional issues that ITS projects face in developing regional systems.
The point of this example was that the requirement for sharing adds significant risk the project. Even though the estimated cost of the
software is small compared to the cost of the changeable message signs, the project risk is driven by the upgrade to the controlling
software and the institutional issues. This example also applies to the sharing of field devices such as cameras, signal systems, or
the integration of bus priority with signal systems.
Project Example 3
Implementing a new central management system - this example upgrades a signal system. This is a typical project and
provides a good example of the nominal amount of systems engineering required for a commercial off-the-shelf (COTS) product.
These are just typical activities and estimates of effort. This should not be taken as a "script" to follow. These same projects in your
environment may require more or less systems engineering effort.
Case studies provide real-world examples of the application of systems engineering to ITS projects. Documented case studies are an excellent opportunity to learn what worked and what didn't work, and benefit from lessons learned without the pain of actual experience. We are indebted to the three project case studies that have shared their experiences.
|Note: These case studies are included in the interest of information exchange, so others may benefit from the experience of early adopters of the systems engineering process. The case studies were produced collaboratively with each agency working cooperatively with the SEGB authors. They are not a result of any formal review or audit by USDOT or any other agency.
MTA New York City Transit ATS
- Key Lessons Learned
This project provides Automatic Train Supervision (ATS) for the A Division of the New York City subway system. It automates many of the real-time train control functions now performed manually, while generating train location and performance data for travelers and operators. It also allows a single control center to replace several regional manual control towers. The project is nearing completion as this report is written in the summer of 2006.
- Baltimore Traffic Management - Key Lessons Learned
The City of Baltimore Integrated Traffic Management System is a major upgrade of the City of Baltimore’s street traffic management system. It involved replacement of all traffic signal controllers and cabinets, installation of additional closed circuit television cameras and changeable message signs, upgrading and expansion of center-to-field communications infrastructure, video exchange with State agencies, a new traffic management center, new central computer hardware and software for remote management of field devices, and updated traffic signal timings. The main part of the project has been successfully completed.
- Maryland CHART Project - Key Lessons Learned
CHART (Coordinated Highways Action Response Team) is an incident management system for roadways in Maryland. It is a joint effort of the Maryland Department of Transportation, Maryland Transportation Authority (toll authority) and the Maryland State Police, in cooperation with other federal, state and local agencies. The system described here is actually the second version of the original CHART system, and is technically called CHART II. The CHART system was successfully deployed and has achieved its goals. Annual evaluations performed by the University of Maryland have documented the considerable benefits of CHART, which far exceed its cost.