Concept of Operations

1
Lesson 3

• Concept of Operations

2
Course Outline Day 1

• Introduction to Systems Engineering
• Systems Engineering and Procurement
• Concept of Operations
• Requirements Engineering
• System Design Practices

3
Concept of Operations Learning Objectives

• List the stakeholders and their roles in
  projects
• List the elements that are included in the
  Concept of Operations
• Develop organizational practices and procedures
  for the Concept of Operations

4
Systems Engineering Life Cycle
Concept of Operations
Operations Maintenance
High Level Requirements
Control Gates
System Verification
Detailed Requirements
Integration Verification and Validation
High Level Design
Subsystem Verification
Definition and Decomposition
Detailed Design
Integration Test
Implementation
Time
5
Concept of Operations
The concept of operations is a document that
defines the environment in which the system is to
operate. The environment includes the
relationship between the system and the agencys
responsibilities, the physical environment, and
expectations (performance and life).
6
Concept of Operations

• Describes the systems operational
  characteristics
• Facilitates understanding of goals
• Forms the basis for long range planning
• Presents an integrated view of the stakeholder
  organization and mission

ANSI/AIAA G-043-1992 Guide for the Preparation of
Operational Concept Documents
7
The System Context
Support Environment
Objectives
System Constraints And Limitations
Operations Environment
The System
Operational Philosophies
Relevant Customer/Provider Policies
Operational System Characteristics
External Interfaces
8
Path to a Concept of Operations
Problem Definition
Concept of Operations
,,,,
Define visions, goals and solutions
9
Getting to a Concept of Operations

• Step 1 Define the Problem
• Define goals and objectives
• Concept Exploration
• Gap Analysis -Gaps in meeting the goals and
  objectives
• Stakeholder Identification and buy-in

10
Getting to a Concept of Operations

• Step 2 Bridge from Problem to Solution concepts
• Alternative Concepts/Solutions
• Scenarios of envisioned operations
• Constraints/Metrics
• Alternative Project Architectures
• Consensus Building

11
Intended Audience

• The concept of operations is developed for
• Users/operators/maintainers
• System engineers and architects
• System implementers
• Customers and buyers
• Testers
• Management

12
Concept of Operations Who is Responsible?
13
Developing the Concept of Operations
Work on the Details

• Deployment
• Practices procedures
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

Identify Stakeholders
Develop a Vision
14
The Concept of Operations is Developed by the
Stakeholders

• Stakeholders include
• Anyone affected by the project
• Operators
• Personnel involved with system inputs and outputs
• Owners of other systems to be interconnected
• Individuals whose processes will be changed
• Anyone with whom and to whom you should
  communicate about the project

15
Stakeholders

• System operators and dispatchers
• Maintenance personnel
• Service patrol
• Telecommunications
• Construction personnel
• Other agencies
• Police
• Fire and EMS
• Local jurisdictions

16
What a Concept of Operations Does For Stakeholders

• Provides a common definition of visions, and
  expectations
• Defines current organizational practices and
  procedures
• Describes new organizational practices and
  procedures
• Identifies required changes

17
Developing the Concept of Operations
Work on the Details

• Deployment
• Practices procedures
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

Identify Stakeholders
Develop a Vision
18
Begin with the Goals and Objectives

• Define expected outcome(s) from new system
• Defined prior to developing a vision
• Quantitative if possible
• Meaningful and Achievable
• Example Reduce incident response time by 10.

19
The Stakeholders Develop the Vision

• A definition of ultimate project outcome
• Typically described in one paragraph
• Represents stakeholder consensus
• Includes buy-in from senior management
• Used to define development phases

20
Sample Vision

• The transit dispatch system will be the focal
  point for controlling bus routing and scheduling
  in real-time under both normal and incident
  conditions. It will include the ability to
  locate and track buses, and to communicate with
  their drivers. It will include interface with
  other transportation systems. The dispatch
  system will disseminate real time bus arrival
  times to riders.

21
Workshop Problem 1

• Develop a vision for the XYZ Metropolitan Area
  Shown on the following slide using the
  description provided with the workshop problems

22
The XYZ Metropolitan Area
The State of Lincoln
I-905
I-994
Zapata County
Yazoo County
Xavier
I-994 Major truck route I-905 Heavy
commuter Traffic
Adams River
XYZ Intl Airport
The State of Harrison
23
Developing the Concept of Operations
Work on the Details

• Deployment
• Practices procedures
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

Identify Stakeholders
Develop a Vision
24
Deployment

• Where will the system be used?
• What jurisdictions will use it?
• What organizations will it support?
• What geographic area will it cover?
• Deployment should be defined for each of the
  development phases

25
Developing the Concept of Operations
Work on the Details

• Deployment
• Practices procedures
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

Identify Stakeholders
Develop a Vision
26
A Practice or a Procedure?

• Defines
• Activities to be performed
• Organizational relationships responsibilities
• Information flow
• Message priorities
• Archiving needs
• Administration (including security)

27
Organizational Practices and Procedures

• Functions are lists of system capabilities
• Typical functions include
• Respond to incidents
• Measure traffic speeds
• Process bus breakdowns
• Practices and procedures describe how functions
  are processed

28
Class Discussion

• Define a non-transportation function and its
  practices and procedures
• Define a transportation function and its
  associated practices and procedures

29
Practices and Procedures for a Bus Dispatch System

• Begins with high level identification of
  practices to be considered
• Tracking buses in service
• Controlling bus schedule adherence
• Responding to emergencies
• Dispatching for breakdowns
• Coordinating with other modes

30
Practices and Procedures - continued

• Dispatching for Breakdowns
• Radio communications from driver
• Bus location determined
• Maintenance is notified
• New bus requested from the yard
• Actions are verified
• Event is closed

31
The Operations to be Performed

• Dispatcher External to the system
• Actions taken by the system
• Process bus breakdown
• Locate bus
• Notify maintenance
• Request replacement bus
• Confirm actions
• Close events

32
Pictures Sometimes Help
Receive Notification of Disabled bus
Dispatch rules and messages database
Initiate location query
Locate Bus
Activate bus location system
Bus location
Access message database
Send notification
Initiate bus Breakdown messages
Initiate maintenance activity
Provide messages
Process Breakdown
Send Replacement bus
Request replacement
Confirm Actions and Close event
Action completed
Dispatcher
33
This example demonstrates the importance of the
concept of operations

• Stakeholders review the diagrams and decide that
• Maintenance should notify the yard
• Logging is missing
• New diagrams are needed.

34
The Revised Diagram
Receive Notification of Disabled bus
Dispatch rules and messages database
Initiate location query
Locate Bus
Activate bus location system
Bus location
Access message database
Send notification
Initiate bus Breakdown messages
Initiate maintenance activity
Provide messages
Process Breakdown
Log breakdown
Request replacement
Confirm
Bus status database
Send Replacement bus
Action completed
Confirm Actions and Close event
Log completion
35
Practices and procedures are important

• They provide an early definition of
  relationships.
• Stakeholders can agree on procedures.
• Agreement on functionality avoids costly
  reprogramming

36
What Isnt a Procedure or Practice

• Definition of system architecture
• Description of hardware and software
• Specification of system functions
• A practices and procedures define what must be
  done and who should do it.
• A practices and procedures do NOT define how to
  do it.

37
Developing the Concept of Operations
Work on the Details

• Deployment
• Practices procedures
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

Identify Stakeholders
Develop a Vision
38
Performance

• Defines critical parameters (captures
  expectations)
• Examples
• Delays (time to display messages)
• Measurement accuracy (location, speed)
• Processing accuracy (incident detection
  probability)

39
Developing the Concept of Operations
Work on the Details

• Deployment
• Practices procedures
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

Identify Stakeholders
Develop a Vision
40
Utilization Environment

• Under what conditions will various parts of the
  system be used
• Applicability limited
• Examples
• User skills
• Competing demands for users attention

41
Developing the Concept of Operations
Work on the Details

• Deployment
• Practices procedures
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

Identify Stakeholders
Develop a Vision
42
Effectiveness

• How well does the system perform its intended
  mission
• First step in defining performance evaluation
• Examples
• Reduced incident clearance time
• Improvements in planning for construction
• Increased bus ridership
• Reduced truck delays at weigh stations

43
Developing the Concept of Operations
Work on the Details

• Deployment
• Practices procedures
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

Identify Stakeholders
Develop a Vision
44
Life Cycle

• How long do you expect the system to last
• Affects design in many ways
• Vision
• System capacities (expandability)
• Provisions for future upgrades
• Budgeting for capital expenditures

45
Developing the Concept of Operations
Work on the Details

• Deployment
• Practices procedures
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

Identify Stakeholders
Develop a Vision
46
Environment

• This category defines the conditions under which
  the system must operate.
• Examples
• Temperature
• Humidity
• Dust and dirt
• Power (both failures and fluctuations)

47
User Services of the National ITS Architecture

• Can be used to support the development of the
  Concept of Operations
• Describe generic ITS services
• Assist development of vision
• Provide good starting point for identifying items
  to be included

48
User Services - Organization
User Services (32)
User Service Bundles (8)
49
User Service Bundles

• Travel and Traffic Management
• Public Transportation Management
• Electronic Payment
• Commercial Vehicle Operations
• Emergency Management
• Advanced Vehicle Safety Systems
• Archived Data Information Services
• Maintenance Construction Operations

50
User Services Travel and Traffic Management
Example

• 1.1 Pre-trip Travel Information
• 1.2 En-route Driver Information
• 1.3 Route Guidance
• 1.4 Ride Matching and Reservation
• 1.5 Traveler Services Information

51
User Services Travel and Traffic Management
(contd.)

• 1.6 Traffic Control
• 1.7 Incident Management
• 1.8 Travel Demand Management
• 1.9 Emissions testing and mitigation
• 1.10 Highway-rail Intersection

52
User Services Can Help

• Deployment Locations of each service
• Practices and procedures Processes for each
  service
• Performance Performance criteria for each
  service
• Effectiveness Evaluation measures for each
  service

53
Do I Really Need a Concept of Operations?

• Yes!
• A Concept of Operations defines the relationship
  between the system and the organization
• Dont build a system until the processes it
  supports have been defined

54
Developing the Concept of Operations
Work on the Details

• Deployment
• Practices procedures
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

Identify Stakeholders
Develop a Vision
55
The Concept of Operations and the Timeline
Stakeholders
Vision
Details
Concept of Operations
Develop Deploy
Acceptance Test
Requirements
Design
Time

• Deployment
• Business practices
• Performance
• Utilization
• Effectiveness
• Life cycle
• Environment

56
Workshop Problem 2

• Developing organizational practices and procedures

57
Documenting the Concept of Operations

• Scope
• Referenced documentation           
• Current system or situation
• Justification For and Nature of Changes
• Concepts for the Proposed System
• Operational Scenarios
• Summary of Impacts
• Analysis of Proposed System
• See Appendix A for detailed outline

58
Relationship to the Federal Rule (Part 940)

• Systems Engineering requires a Concept of
  Operations
• The Federal rule requires an Operational Concept
• The two are similar but not identical

59
The Level of Detail Depends on the Purpose of the
Analysis
Planning Level (where, who and what)
Problem definition, MOUs, funding, Procurement,
Operational Concept Concept of Operations
High level Detailed level
Operational details
Project
60
Inputs to the Operational Concept

• Where corridor, region, etc.
• Who what jurisdictions, agencies, etc.
• What traffic management, dispatch, traveler
  information, etc.

61
Contents of the Operational Concept

• Funding Estimates and funding sources
• Players and MOUs
• Lead Agency(s)
• Description - High level list of functions
• Impact Affect on regional roles and
  responsibilities

62
Candidate ConOps Outlines

• IEEE Std P1362 V.3.2
• Scope
• Ref Doc
• Current System or Situation
• Justification for and Nature of changes
• Concepts for the Proposed system
• Operational Scenarios
• Summary of Impacts
• Analysis of Proposed System
• Notes
• Appendices
• Glossary

63
Concept of Operations Learning Objectives

• List stakeholders and their roles in projects
• List the elements that are included in the
  Concept of Operations
• Develop organizational practices and procedures
  for the Concept of Operations

64
Systems Engineering Life Cycle
Concept of Operations
Operations Maintenance
High Level Requirements
Control Gates
System Verification
Detailed Requirements
Integration Verification and Validation
High Level Design
Subsystem Verification
Definition and Decomposition
Detailed Design
Integration Test
Implementation
Time