entry system

Reduce time to deliver product

ASSUMPTION
Service
System
Critical
Data sources
users
Administrato
interfacing
Infrastructu
rs
systems
re
INITIATIVE
OUTCOME
OUTCOME
Contribution
Contribution
Order to delivery time is an
Reduce time to process order

Reduce order processing cycle

important buying criterion

(intermediate outcome)

Operational Concept Description (OCD)

[This page is intentionally left blank]

Table of Contents

Introduction
1.1 Purpose of OCD
1.2 References

9
9
9

Shared Vision
11
2.1 System Capability Description
11
2.1.1 Benefits Realized
11
2.1.2 Results Chain
12
2.2 Key Stakeholders
13
2.3 System Boundary and Environment
14
2.4 Major Project Constraints
15
2. 5 Top-Level Business Case
15
2.6 Inception Phase Plan and Required Resources16
2.7 Initial Spiral Objectives, Constraints, Alternatives, and
Risks 16

Domain Description
17
3.1 Organization Background
3.2 Organization Goals
3.3 Current Organization Activity Model
3.4 Description of Current System
3.5 Current Entity Model
3.6 Interaction Model
3.7 Current System Shortfalls

17
18
19
20
22
24
25

Proposed System
27
4.1 Statement of Purpose
4.2 Project Goals and Constraints
4.3 Capabilities
4.4 Levels of Service
4.5 Proposed System Description
4.6 Redressal of Current System Shortfalls
4.7 Effects of Operation

27
27
28
29
31
36
37

Prototyping
5.1 Objectives

39

39

Operational Concept Description

Version 2.3.3

5.2
5.3
5.4
6

Approach
Initial Results
Conclusions

Common Definition Language

7. Appendix

40
40
41
42
43

Version control

Date
[Type today's date ]

Author
[Author's name ]

Changes
[Changes made since last version ]

Version
0.1

Operational Concept Description

Version 2.3.3

vi

Operational Concept Description

Version 2.3.3

List of Figures

vii

1 Introduction

The operational concept description of [Project Name] will be introduced.

1.1 Purpose of the Operational Concept Description Document

The purpose of the Operational Concept Description (OCD) for Project Name is to describe to the
stakeholders of the system how the system will function in practice. The functions of the system are
included in the operational concept as well as the interactions of the system users.
The stakeholders include the customer, the users, the project manager, and the developers. The customer is
[Click here and type Customer's name] who [Click here and type Customer's designation]. The users
include [Click here and type System users].
The OCD will provide clear and concise documentation to the stakeholders, especially for reference and
guidance for all parties, to ensure that the correct system is being developed and the system is being
developed correctly. A clear understanding of how stakeholders will interact with the system and how they
interact with each other with regards to the system is a crucial function of the OCD. Specifically, the main
goals of the OCD are to enable the operational stakeholders to evolve knowledgeably from their current
and inadequate operational concept to the new operational concept, and to enable stakeholders to
collaboratively adapt the operational concept as new developments arise. Therefore, the operational
concept description is written in the common language of all interested parties.

1.2 References
System and Software Requirements Definition [Click here and type version referenced ]
System and Software Architecture Description [Click here and type version referenced ]
Feasibility Rationale Description [Click here and type version referenced ]
Life Cycle Plan [Click here and type version referenced ]
[Click here and type other references ]

Operational Concept Description

Version 2.3.3

2 Shared Vision

2.1 System Capability Description

[Click here and type For (target customer) ]
[Click here and type Who (statement of the need or opportunity)]
[Click here and type: The (product name) is a (product category))]
[Click here and type: That (statement of key benefit-that is, compelling reaon to buy))]
[Click here and type Unlike (primary competitive alternative))]
[Click here and type Our product (statement of primary differentiation))]

2.1.1 Benefits Realized

[Click here and type Benefits Realized ]

2.1.2 Results Chain

[Click here and type Results Chain]

2.2 Key Stakeholders

[Click here and type Key Stakeholders]

2.3 System Boundary and Environment

[Click here and type System Boundary and Environment]

10

Operational Concept Description

Version 2.3.3

2.4 Major Project Constraints

[Click here and type Major Project Constraints]

Special focus: Further Shared Vision Elements for Large Systems

[Click here and type System Special Focus]

2. 5 Top-Level Business Case

[Click here and type Top-Level Business Case]

2.6 Inception Phase Plan and Required Resources

[Click here and type Inception Phase Plan and Required Resources]

2.7 Initial Spiral Objectives, Constraints, Alternatives, and Risks

[Click here and type Initial Spiral Objectives, Constraints, Alternatives, and Risks]

11

Operational Concept Description

Version 2.3.3

3 Domain Description

3.1 Organization Background

The[Sponsor Organization] located in [Click here and type Sponsor Location] was established in [Click
here and type Inauguration Year] for [Click here and type Purpose]. [Click here and type Additional
background information]

3.2 Organization Goals

The objectives of the Sponsor Organization are [Click here and type Customer objectives].
Specifically, the goals of the [Click here and type Sponsor Organization] in relation to Project Name are
listed below in decreasing order of their relative importance:
1. [Click here and type Customer Goal].
Relevance: [Click here and type Why the goal is relevant to this project].
Measure: [Click here and type How the goal is to be measured].
2.

[Click here and type Customer Goal].

Relevance: [Click here and type Why the goal is relevant to this project].
Measure: [Click here and type How the goal is to be measured].

3.3 Current Organization Activity Model

I. [Click here and type Organization activity]
A. [Click here and type Organization sub-activity])
1. [Click here and type Organization sub-activity]
2. [Click here and type Organization sub-activity]
B. [Click here and type Organization sub-activity]
II. [Click here and type Organization activity]
A. [Click here and type Organization sub-activity]

12

Operational Concept Description

Version 2.3.3

3.4 Description of Current System

The current system utilized in the [Sponsor Organization] is [Click here and type system description]

13

Operational Concept Description

Version 2.3.3

3.5 Current Entity Model

The following is a list of entities from the current system:
1. [Click here and type The entity name]
2. [Click here and type The entity name]
Entity: E-01
Title: [Click here and typeTitle for the entity]
Description: [Click here and type Entity description].
Properties:
1. [Click here and type Entity property]
2. [Click here and type Entity property]
Activities:
1. [Click here and type Entity activity]
2. [Click here and type Entity activity]
Connections:
1. [Click here and type Entity interaction]
2. [Click here and type Entity interaction]
Constraints:
1. [Click here and type Constraints imposed]
2. [Click here and type Constraints imposed].
Entity: E-02
Title: [Click here and typeTitle for the entity]
Description: [Click here and type Entity description].
14

Operational Concept Description

Version 2.3.3

Properties:
3. [Click here and type Entity property]
4. [Click here and type Entity property]
Activities:
3. [Click here and type Entity activity]
4. [Click here and type Entity activity]
Connections:
3. [Click here and type Entity interaction]
4. [Click here and type Entity interaction]
Constraints:
3. [Click here and type Constraints imposed]
4. [Click here and type Constraints imposed].

3.6 Interaction Model

3.7 Current System Shortfalls

[Click here and type]

15

4 Proposed System

The proposed system for [Click here and type Project Name] is analyzed in this section. This section
explains what the system is and what it performs and how well it performs.

4.1 Statement of Purpose

Refer to OCD 2, Shared Vision for the proposed systems purpose, context, and relation to organization
benefits realized. Elaborate how these relate to the Current System Shortfalls (OCD 3.7), System Boundary
and Environment (OCD 2.3), Organization Background (OCD 3.1), Organization Goals (OCD 3.2),
Operational Stakeholders (OCD 4.7.1)
[Consistent with Organization Background (OCD 3.1)]
[Consistent with Organization Goals (OCD 3.2)]
[Consistent with Operational Stakeholders (OCD 4.7.1)]
[Click here and type]

4.2 Project Goals and Constraints

The main goals of the project are:

1.

PG-01
Title
Description

M
R
S
Organization Goal
WinWin
Agreement
2. PG-02
Title
Description
M
R
S

[Click here and type Title for project goal]

[Click here and type Description of project goal]
[Click here and type How the goal is to be measured]
[Click here and type Why the goal is relevant to this project]
[Click here and type What specifically does the goal mean]
[Click here and type Reference to the Organization goal]
[Click here and type Reference to the WinWin Agreeement]
[Click here and type Title for project goal]
[Click here and type Description of project goal]
[Click here and type How the goal is to be measured]
[Click here and type Why the goal is relevant to this project]
[Click here and type What specifically does the goal mean]

Operational Concept Description

Organization Goal
WinWin
Agreement

Version 2.3.3

[Click here and type Reference to the Organization goal]

[Click here and type Reference to the WinWin Agreeement]

4.3 Capabilities
1.

2.

CAP-01
Title
Description
Priority
Rationale
Agreement
Organization
Activity
CAP-02
Title
Description
Priority
Rationale
Agreement
Organization
Activity

[Click here and type Title for Capability]

[Click here and type Description of capability]
[Click here and type Relative Priority for achieving this capability]
[Click here and type Rationale for requiring this feature]
[Click here and type Reference to the WinWin Agreement]
[Click here and type Reference to the Organization activity]
[Click here and type Title for Capability]
[Click here and type Description of capability]
[Click here and type Relative Priority for achieving this capability]
[Click here and type Rationale for requiring this feature]
[Click here and type Reference to the WinWin Agreement]
[Click here and type Reference to the Organization activity]

4.4 Levels of Service

18

Operational Concept Description

Version 2.3.3

The proposed system shall exhibit the following levels of service:

1.

2.

LS-01
Title
Description
M
R
S
Organization Goal
WinWin
Agreement
LS-02
Title
Description
M
R
S
Organization Goal
WinWin
Agreement

[Click here and type Title for Service level]

[Click here and type Description of service level]
[Click here and type How the level is to be measured]
[Click here and type Why the level is relevant to this project]
[Click here and type What specifically does the service level mean]
[Click here and type Reference to the Organization goal]
[Click here and type Reference to the WinWin Agreeement]
[Click here and type Title for Service level]
[Click here and type Description of service level]
[Click here and type How the level is to be measured]
[Click here and type Why the level is relevant to this project]
[Click here and type What specifically does the service level mean]
[Click here and type Reference to the Organization goal]
[Click here and type Reference to the WinWin Agreeement]

4.5 Proposed System Description

19

Operational Concept Description

Version 2.3.3

4.5.1 Proposed Activities

The operational scenarios of the proposed system are:
1.

2.

SL-01
Title
Stimuli
Action
Information
Prototype Screen
SL-02
Title
Stimuli
Action
Information
Prototype Screen

[Click here and type Title of operational model]

[Click here and type How interaction begins]
[Click here and type What system does to respond]
[Click here and type What information flows during the interaction]
[Click here and type Reference to the Prototype Screen shot in the
Appendix]
[Click here and type Title of operational model]
[Click here and type How interaction begins]
[Click here and type What system does to respond]
[Click here and type What information flows during the interaction]
[Click here and type Reference to the Prototype Screen shot in the
Appendix]

20

Operational Concept Description

Version 2.3.3

4.5.2 Proposed Entities

[Click here and type]

21

Operational Concept Description

Version 2.3.3

4.5.3 Proposed Interactions

[Click here and type]

4.6 Redressal of Current System Shortfalls

[Click here and type]

4.7 Effects of Operation

[Click here and type]

4.7.1 Operational Stakeholders

The operational stakeholders include:
1.
Stakeholder
[Click here and type Name of stakeholder]
Activities
[Click here and type Proposed Activity Performed]
Performed
Usage
[Click here and type Usage Characteristics]
Characteristics
2.
Stakeholder
[Click here and type Name of stakeholder]
Activities
[Click here and type Proposed Activity Performed]
Performed
22

Operational Concept Description

User
Characteristics

Version 2.3.3

[Click here and type Usage Characteristics]

4.7.2 Organizational Relationships

[Click here and type]

4.7.3 Operational Policies and Constraints

[Click here and type]

4.7.4 Operational Impacts

[Click here and type]

4.7.5 Organizational Impacts

[Click here and type]

23

5 Prototyping

5.1 Objectives
[Click here and type Objectives]

5.2 Approach
[Click here and type]

5.2.1 Scope and Extent

[Click here and type]

5.2.2 Participants
[Click here and type]

5.2.3 Tools
[Click here and type]

5.2.4 Revision History

[Click here and type]

5.3 Initial Results

[Click here and type]

5.4 Conclusions
[Click here and type]

Operational Concept Description

Version 2.3.3

6 Common Definition Language

[Click here and type Domain term]

[Click here and type Term description]
[Click here and type Domain term]
[Click here and type Term description]

26

7. Appendix

[Click here and type]