entry system

Reduce time to deliver product ASSUMPTION

Service
System Critical Data sources
users
Administrato interfacing
Infrastructu
rs re systems
INITIATIVE OUTCOME OUTCOME
Contribution Contribution Order to delivery time is an
important buying criterion
Reduce time to process order Reduce order processing cycle
(intermediate outcome)

Operational Concept Description (OCD)

[This page is intentionally left blank]
Operational Concept Description Version 2.3.3

Table of Contents

1 Introduction 9
1.1 Purpose of OCD 9
1.2 References 9

2 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

3 Domain Description 17
3.1 Organization Background 17
3.2 Organization Goals 18
3.3 Current Organization Activity Model 19
3.4 Description of Current System 20
3.5 Current Entity Model 22
3.6 Interaction Model 24
3.7 Current System Shortfalls 25

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

5 Prototyping 39
5.1 Objectives 39
Operational Concept Description Version 2.3.3

5.2 Approach 40
5.3 Initial Results 40
5.4 Conclusions 41

6 Common Definition Language 42

7. Appendix 43
Operational Concept Description Version 2.3.3

Version control

Date Author Changes Version

[Type today's date ] [Author's name ] [Changes made since last version ] 0.1

v
Operational Concept Description Version 2.3.3

vi
Operational Concept Description Version 2.3.3

List of Figures

vii
Operational Concept Description Version 2.3.3

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 ]

9
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].
Properties:

14
Operational Concept Description Version 2.3.3

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
Operational Concept Description Version 2.3.3

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 system’s 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 [Click here and type Title for project goal]
Description [Click here and type Description of project goal]
M [Click here and type How the goal is to be measured]
R [Click here and type Why the goal is relevant to this project]
S [Click here and type What specifically does the goal mean]
Organization Goal [Click here and type Reference to the Organization goal]
WinWin [Click here and type Reference to the WinWin Agreeement]
Agreement
2. PG-02
Title [Click here and type Title for project goal]
Description [Click here and type Description of project goal]
M [Click here and type How the goal is to be measured]
R [Click here and type Why the goal is relevant to this project]
S [Click here and type What specifically does the goal mean]
Organization Goal [Click here and type Reference to the Organization goal]
WinWin [Click here and type Reference to the WinWin Agreeement]

17
Operational Concept Description Version 2.3.3

Agreement

4.3 Capabilities
 Minimum information for each system capability is as indicated in the following suggested template:
1. CAP-01
Title [Click here and type Title for Capability]
Description [Click here and type Description of capability]
Priority [Click here and type Relative Priority for achieving this capability]
Rationale [Click here and type Rationale for requiring this feature]
Agreement [Click here and type Reference to the WinWin Agreement]
Organization [Click here and type Reference to the Organization activity]
Activity
2. CAP-02
Title [Click here and type Title for Capability]
Description [Click here and type Description of capability]
Priority [Click here and type Relative Priority for achieving this capability]
Rationale [Click here and type Rationale for requiring this feature]
Agreement [Click here and type Reference to the WinWin Agreement]
Organization [Click here and type Reference to the Organization activity]
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. LS-01
Title [Click here and type Title for Service level]
Description [Click here and type Description of service level]
M [Click here and type How the level is to be measured]
R [Click here and type Why the level is relevant to this project]
S [Click here and type What specifically does the service level mean]
Organization Goal [Click here and type Reference to the Organization goal]
WinWin [Click here and type Reference to the WinWin Agreeement]
Agreement
2. LS-02
Title [Click here and type Title for Service level]
Description [Click here and type Description of service level]
M [Click here and type How the level is to be measured]
R [Click here and type Why the level is relevant to this project]
S [Click here and type What specifically does the service level mean]
Organization Goal [Click here and type Reference to the Organization goal]
WinWin [Click here and type Reference to the WinWin Agreeement]
Agreement

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. SL-01
Title [Click here and type Title of operational model]
Stimuli [Click here and type How interaction begins]
Action [Click here and type What system does to respond]
Information [Click here and type What information flows during the interaction]
Prototype Screen [Click here and type Reference to the Prototype Screen shot in the
Appendix]
2. SL-02
Title [Click here and type Title of operational model]
Stimuli [Click here and type How interaction begins]
Action [Click here and type What system does to respond]
Information [Click here and type What information flows during the interaction]
Prototype Screen [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
User [Click here and type Usage Characteristics]
Characteristics

4.7.2 Organizational Relationships

22
Operational Concept Description Version 2.3.3

[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
Operational Concept Description Version 2.3.3

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]

25
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
Operational Concept Description Version 2.3.3

7. Appendix

[Click here and type]

27