Transportation Management Systems: Concept of Operations

1
Transportation Management Systems Concept of
Operations Requirements

• Brian L. Smith
• Center for Transportation Studies

Project Preview June 3, 2003
2
Presentation Overview

• Purpose
• Intended audience
• Project overview
• Key issues and topics to be covered
• Products
• Draft schedule
• Contacts

3
Project Purpose

• To develop a detailed document providing
  technical guidance and recommended practices for
  concepts of operations and requirements in
  transportation management systems
• Specifically address
• How to develop
• What to include
• How to use throughout system lifecycle

4
Intended Audience

• Individuals involved in, or responsible for, a
  wide range of TMC activities
• Management
• Planning
• Design
• Operation
• Maintenance

5
Foundation of the TMC
6
Concept of Operations

• Critical first step to define, at a very high
  level, what a TMC will do, and how it do it.
• Not a technical document it can be considered
  as the vision for the system
• Drives remainder of the systems engineering
  process

7
ConOps Address

• TMC roles responsibilities
• Functions
• Services
• Processes
• User expectations
• Resources required
• Maintenance

8
Why Important?

• First definitive expression describing the TMC to
  be developed and operated
• Tool for consensus building among stakeholders
• Bottom line if a clear ConOps cannot be
  developed, the system should go no further.

9
Requirements

• Statements of the capabilities that a system must
  have functions
• General requirements also include performance
  requirements what minimum standards must be
  met?
• Requirements are not specifications they are
  simply the what not the how for system
  development

10
Requirements Address

• Comprehensive description of what the system must
  accomplish
• Good requirements allow a developer to create a
  system that meets the needs of the agency
• Requirements describes what must be created in
  order to make the ConOps a reality

11
Why Important?

• Governs the development process
• Procurement
• Drives system design
• Traceability
• Foundation for acceptance testing
• Traceability

12
Our Approach

• Build on personal experience in Virginia
• Use the best of current transportation-related
  documents
• Many provide excellent, high-level introductions
• Pull in literature from the systems engineering
  and software engineering communities
• Focus on case studies
• What have we learned already?
• Examples from published ConOps and Requirements
  documents.

13
Similar Layout to CM Doc

• Implementation Guidance
• Implementation Guidance Summary
• Best Transportation Practices
• Navigation Assistance

14
What Do We Need?

• Case Studies
• Good and bad experiences
• Contacts
• Example documents
• ConOps
• Functional Requirements
• Tell me your needs
• Where have you needed guidance in these areas in
  the past?

15
Products

• Guidance Document
• Project Fact Sheet
• Subject Presentation
• Tri-Fold Brochure
• Primer
• Distribution Plan

16
Schedule

• 15 month project
• Expected start date July 1, 2003
• Frequent need for feedback from TMC PFS committee

17
Milestones (assumes 7/1/03 start)

• Annotated Outline
• Initial 9/1/03
• Draft 10/1/03
• Draft Document
• Chapters delivered incrementally between 1/1/04 -
  4/1/04
• Other products
• Delivered in Summer 2004

18
For More Information
Brian L. Smith briansmith_at_virginia.edu http//Smar
tTravelLab.virginia.edu Rebecca
Doyle doyler_at_saic.com