Defining the Goals,
Objectives and Rationale for the Concept of Operations
Document
In the introduction of the
Concept of Operations Document, make sure
that you discuss the goals, objectives and rationale for developing this
system.
Download your template
here
Remember that the new system may be an
enhancement to an existing system. For this reason, you need to word
your documents carefully as the IT Architects who developed the first
system may also be involved in the evaluation, assessment, and design of
the new system.
In this section:
1. Identify the high-level goals of this
investment.
This usually links into the company’s strategic plan. How does the new
system compliment the investment and/ or commitments that have been made
to date?
You're unlikely to get support for a
project that contradicts or undermines the current strategic goals.
2. Define the overall goals and objectives
of the new system.
This must link into the strategic plan
but can go one better by alluding to future (i.e. potential) strategic
decisions that have yet to be under-taken.
Download your template
here
Emphasize the importance of
these commitments by demonstrating how and where benefits may be
realized. State the business problems that it will solve.
3. Discuss how the proposed project aligns
with or advances your strategic goals.
Identify how the new system will
help streamline processes, improve efficiencies, and drive down costs.
Demonstrate how the success of the system will be evaluated and
measured.
What type of objectives should I discuss?
One way to approach this is to look at
what is reduced, increased and controlled.
For example:
Decrease costs - Describe how you will
decrease costs in a specific business unit
Customer service - Describe how you
will improve the responsiveness of customer service
Market share - Describe how you achieve
this by partnering or acquiring another firm.
Read more:
1.
How to write the Concept Operations Document
2.
What it a Concept Operations Document?
3.
How to Define the Goals, Objectives and Rationale
4.
What you need to put into a Concept Operations Document
5.
How to Justify the New System to Project Stakeholders
6.
How to develop Use Cases to capture Work Scenarios
7.
What's the Connection Between the Concept of Operations and
Functional Requirements Document
~~~
Concept of Operations Template
Download Now for
$7.99 - Buy Here!
Table of Contents
toc
1 Introduction
1.1 Document overview
1.2 Background
1.3 Identification
1.4 Goals, objectives & rationale
1.5 Points of contact
2 Current System
2.1 Background
2.2 Scope
2.3 Policies and Constraints
2.4 Description of current system
2.5 Modes of Operation
2.6 Users classes & other stakeholders
2.7 Support Environment
3 Justification
3.1 Justification for change
3.2 Description of required changes
3.3 Priorities among the changes
3.4 Changes considered but not included
3.5 Assumptions
3.6 Constraints
4 Proposed System
4.1 Background, objectives, and scope
4.2 Operational policies and constraints
4.3 Description of the new system
4.4 User classes / categories of users
4.5 Modes of operation
4.6 Deployment and support environment
4.7 Non-functional requirements
4.8 Requirements traceability
5 Use Cases & Operation Scenarios
5.1 Process descriptions
5.2 Events
5.3 Use Case
6 Impacts
6.1 Risks
6.2 Issues
6.3 Operational impacts
6.4 Organizational impacts
6.5 Impacts during development
7 Analysis of the Proposed System
7.1 Improvements
7.2 Disadvantages & limitations
7.3 Alternatives
What's included in the template pack
The template is in
Microsoft Word format and can be downloaded online for only $7.99. The template pack includes the following documents:
|
Concept of Operations Template |
30 pages |
 |
Download Now for
$7.99 - Buy Here!
~~~
|
60-day Money-Back Guarantee
Secure Online
Order Form
Supports
Microsoft Word from 2002, 2003, 2007 and works across Windows 97, 2003, XP, Vista
and Apple Mac. 
I'm Ivan Walsh, the person behind this site. I help people improve how they write, publish and extend their business assets.