Guidance for the Development of Statement Of Objectives (SOO)

Introduction

The Statement of Objectives (SOO) provides basic, top-level objectives of an acquisition and is provided in the request for proposal (RFP) in lieu of a government-written statement of work (SOW). It provides potential offerors the flexibility to develop cost-effective solutions and the opportunity to propose innovative alternatives meeting the objectives.

Background

The SOO should be compatible with the mission need statement, operational requirement document, program management directive, acquisition strategy, technical requirements documents or specifications, and the preliminary contract work breakdown structure (CWBS).

The SOO should address product oriented goals as opposed to performance oriented requirements and should not exceed 4 pages as a goal.

The SOO itself is typically appended to Part L of the RFP (Instructions, Conditions and Notices to Offerors). It does not become part of the contract.

The SOO is used by the offerors to develop a SOW, Contract Work Breakdown Structure (CWBS) Integrated Master Plan (IMP), Integrated Master Schedule (IMS) and other documents required by the RFP. Section L should include instructions requiring all offerors to address all aspects of the SOO in their proposal.

The SOO can be used for new training systems acquisition contracts or for modifications to existing training system acquisition contracts.

The SOO can be used for both services and supply type contracts.

Purpose

This document is intended for Integrated Product Teams (IPTs) to assist in identifying objectives that will be applicable to the acquisition of training systems. The document provides a suggested format to assist in organizing the objectives and a shopping list of generic objectives that can be used as applicable. The objectives listed here are meant to be demonstrative and are not all-inclusive, many programs are unique and will have objectives not identified here. As experience is gained with the use of the SOO document, more generic objectives will be added to this document.

Approach

The key to a successful SOO is the separation of requirements from objectives. Requirements should be identified in a separate document such as the Training System Requirements Document (TSRD), Training System Functional Description (TSFD), System Requirements Document (SRD), or Performance Specification.

Within these documents are identified conditions and constraints that must be incorporated into the training system program. This might include such things as where the training system must be located, details about the facility it will be in, the use of an existing visual system that must be incorporated, a required minimum student throughput, a required availability of the system, etc. The SOO approach allows contractors the maximum flexibility in their design approach, but there are almost always some conditions and constraints that must be accommodated in the design.

Suggested Format

First page or cover page that includes a SOO number, date, preparing activity (competency), and "prepared by" and "approved by" signature blocks.

Guidance and Generic Objectives for each Section

1.0 Overall Objectives. The Overall Objectives section should contain objectives that identify the primary purpose of the acquisition. This would include:

Identify the type of training system to be acquired. Is it a Maintenance Trainer, Weapon System Trainer, Tactics Trainer, Operator Trainer, Familiarization Trainer, etc.

Provide a system that utilizes the best (performance and life cycle cost considered) technical approach by emulating, simulating, or stimulating the applicable operational/weapon system

Provide a level of fidelity that (is equal to the operational/weapon system, or increases student skill levels, etc.)

Increase the level of student throughput above current training system

Increase the level of student achievement (skill level) above current training system

Provide a method of measuring the level of student achievement.

Reduce initial and life cycle costs from current training system

Increase integration of training system with the operational/weapon system

Train identified Government personnel in the operation and use of the training system

Train identified Government personnel in the configuration management responsibilities of the training system baseline.

For Services type contracts: Provide all support operations necessary to fully maintain the training system(s) and equipment to ensure their availability for each government scheduled use. This support and operations objective includes:

2.0 Contract Objectives. Note most contract objectives will already be identified within the contract schedule document. You may include certain contract objectives here for emphasis. If you do include this type of objective, you may need to include instructions for how you wish offerors to address these objectives within their proposals. Objectives identified within the SOO are addressed by offerors within a SOW, which they write. Therefore consider how objectives identified in this section could be addressed within a SOW.

3.0 Engineering Objectives.

Design a system which:

Has reliability and maintainability characteristics that support a system availability of __hrs/day, __days/week, __days/month, __days/year, with a ___% probability of completing a __ hour training mission, under the environmental conditions expected in the operational environment.

Is electromagnetically compatible with its own components and the facility/environment in which the training system operates,

Provides a level of security (physical, information systems, electromagnetic (TEMPEST), etc.) appropriate for the level of information that will be processed, distributed or displayed by the training system

Develop the training system using current commercial techniques and standards

Make maximum use of commercial products. The order of preference for products is: (1) Commercial products, (2) Non-Developmental Items (NDI), and then (3) Trainer Peculiar Equipment (TPE).

Provide Integration and testing of training system components at the earliest opportunity

Use test methodologies that reduce the level of government involvement yet increase the level of acceptability of the delivered system.

Install the system with a minimum impact to other systems that may be located in the designated facility.

Develop and document procedures for managing system engineering, software and hardware development. Utilize commercial standards and procedures to the maximum extent in achievement of this objective. The system engineering process includes parts management, quality assurance, Electro-Static Discharge (ESD) control, reliability, maintainability, system safety, etc.

Participate in the Government Industry Data Exchange Program (GIDEP).

Provide the latest possible technology available when the system is delivered. Ensure hardware technology advances can be easily incorporated throughout the delivery schedule.

4.0 Program Management Objectives

Establish a program management system based on the Integrated Master Plan/Integrated Master Schedule that provides accurate and timely schedule and performance information throughout the life cycle of the program.

Establish a sound risk management system, which mitigates program risks and provides for special emphasis on software development efforts through integration of metrics to monitor program status.

Establish a government/contractor IPT partnership that is beneficial to achieving program goals and reduces the overall level of government oversight required.

Establish a comprehensive configuration management system.

Obtain sufficient rights in technical data, both software and hardware, such that the Government can maintain and modify the training system using Government personnel and third party contractors.

Propose the most comprehensive and cost effective Contract Data Requirements List (CDRL) tailored to the proposed design solution. If a preliminary or minimum CDRL is specified by the government, that CDRL should be used as a baseline for offerors to propose a tailored CDRL for their design.

Use electronic technologies to reduce paper copies of program information generated throughout the life of this contract.

Use electronic technologies to communicate and pass data between government and contractor organizations. To assist offerors in this objective, current NAWCTSD electronic infrastructure capabilities are identified in a Government Concept Of Operations (GCO) For Electronic Commerce (EC) In An Integrated Digital Environment (IDE) document. This includes:

Other support elements needed to maintain and operate the training device when fielded

Hardware and software documentation which supports the life cycle of the training system (we may need to refer to specific existing types of maintenance and operation documents which will need updating to reflect what the overall system will become)

Establish contractor "turn-key" logistics support to operate and maintain the training system to a guaranteed reliability and availability level, including spares, associated user documentation, support data, test equipment, and maintenance training.