DI-SESS-82195

Contractor's Engineering Program Plan

Describes the contractor's overall Engineering and Configuration Management program, including its organization and conduct, providing the government a basis for review, evaluation, and monitoring.

Approval DateApril 18, 2018

AMSC NumberN9912

Preparing ActivitySH

Project NumberSESS-2018-006

OPR—

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Contractor's Engineering Program Plan describes the contractor's overall Engineering and Configuration Management (CM) program, how it is organized, how it will be conducted, and the interrelationships between the Engineering and Configuration Management programs. The principal use is to provide the government a basis for review, evaluation and monitoring of the program.

This data item description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

Preparation Instructions

1FormatThe Contractor's Engineering Program Plan shall be in contractor's format.

2ContentThe Contractor's Engineering Program Plan shall identify the contractor's engineering and CM program organization, the methods, procedures, and controls that shall be employed, as well as the various government-approved engineering tasking that may be assigned.

2.1The plan shall include details of thecontractor process and the interactions with the procuring activity Project Process.

2.2The plan shall contain Engineering and CM proceduresfor the following:

2.2.1Resolving Operation and Maintenance (O&M) hardware,software, and firmware problems for systems that are still being actively used and for equipment that is inoperable and requires engineering expertise.

2.2.2Engineering, installation, integration and surveyingor drafting support for contract equipment, systems and facilities.

2.2.3Developing and installing Temporary Engineering Changes(TECs), Engineering Change Proposals (ECPs), Notices of Revision (NORs), and Specification Change Notices (SCNs).

2.2.4Performing Naval Surface Warfare Center (NSWC),Corona approved engineering tasking, which include the following:

2.2.4.1Bringing new, inoperative, or 'mothballed'equipment or systems to operational status.

2.2.4.2Relocating, re-configuring, installing, modifying, and integratingcontract equipment, systems, and facilities to meet new operational requirements, facility build-up, and range configuration and development changes.

2.2.4.3Implementing approved system modifications, enhancements, andupgrade (e.g., System Life-cycle Extension Program, Inspect and Replace).

2.2.5Maintaining an on-line master Engineering ProjectStatus Listing.

2.2.6Maintaining, inventorying, and controlling the contentsof the Technical Library and the on-line electronic Document Database, available to the government.

2.2.7Establishing an active Configuration Control Board(CCB) consisting of both NSWC and contract personnel, establishing CCB review and approval processes.

2.2.8Evaluating contract requirements, contract equipment, systems,facilities, and associated technical data/documentation to establish appropriate levels of identifiers for use in management and configuration of each applicable contract item.

2.2.9Defining and identifying the type and levelof system configuration information that is necessary for control of each piece of contract equipment, system, or facility.

2.3The plan shall identify the Configuration Managementprogram in accordance with the contractor's processes and procedures. The ANSI/EIA-649, National Consensus Standard for Configuration Management (paragraphs 5.2.5 and 5.3.3) may be useful in defining content.

2.4The plan shall also include how CMwill be conducted, and the methods and controls for effective identification, change control, status accounting, and audits.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer