Draft SOW BMS Production.docx

CUI

STATEMENT OF WORK

FOR

REQUIREMENTS BMS PRODUCTION CONTRACT

ENGINEERING SERVICES

1.0 SCOPE

This Statement of Work (SOW) defines the requirements for the acquisition and maintenance of the Bathymetry Mapping System (BMS) and BMS components. The BMS addresses the need of the United States Navy to be able to collect higher quality bathymetric and imagery data of the ocean floor with newer and more cost effective technology.

The intent of this contract is the sole source manufacturing of the production versions of the BMS Sensor Suite Engineering Development Model (EDM) developed by Hydroid Inc. and Kongsberg Maritime under contract N61331-15-C-0013.

This Statement of Work (SOW) specifies Contractor tasking for the production and delivery of complete BMS systems, BMS components as defined in Section 3.0, system topside software licenses, system Post Mission Analysis (PMA) software licenses, system software license maintenance, Engineering Services labor, and Travel to support Engineering Services labor.

2.0 APPLICABLE DOCUMENTS

2.1 Military Specifications: None

2.2 Military Standards:

2.3 Other Documents:

NOTE: Military Specifications, Standards, and Handbooks are available from: https://assist.dla.mil/online/start/. Reference 2.2(b) is provided with the solicitation.

3.0 REQUIREMENTS

The Contractor shall coordinate with the Contracting Officer's Representative (COR) and Contract Specialist to conduct a kickoff meeting within ten working days after the award of the contract. This meeting's date, time and location shall be determined at time of award.

3.1 BMS Sensor Suite Production

This subsection provides for the production and delivery of BMS Sensor Suites which include all of the components listed in section 3.4 below. The production and delivery of BMS Sensor Suites shall include integration of the components, program management, configuration management, and system tests in accordance with the Technical Data Package (TDP) referenced in 2.3(b) that was developed during the Engineering Development Model (EDM) contract (N61331-15-C-0013).

3.1.1 Program Management and Control (CDRL A001, A002, A003, A004)

The Contractor shall continue to organize, coordinate, and control all internal project activities (including subcontractors) to ensure a timely delivery of all supplies and services specified in this contract. The Contractor shall appoint a single program manager directly responsible for all aspects of the BMS program described in this SOW. The Contractor shall also establish a single point of contact empowered to commit the Contractor in execution of this effort. The Contractor shall continue to use and maintain the program management processes and procedures established under the previous production contract (N61331-18-D-0015) to manage all technical performance, cost, schedule, risk, and delivery requirements of this contract. The Contractor shall plan, control, coordinate, execute, and oversee all its activities related to the production fabrication, integration and testing of the BMS Sensor Suite production systems, including all technical performance, cost, schedule, and delivery requirements. The Contractor shall develop and deliver an Integrated Management Report (IMR) to include the Contract Work Breakdown Structure (CWBS) using MIL-STD-881 for guidance. The Contractor shall also include methodologies to be used for controlling and reporting progress and budget data, and the Integrated Product Team (IPT) structure and processes to be used in performing the work.

Technical Performance and Schedule Management The Contractor shall conduct technical performance and scheduling activities as an integral element of the program management effort. The Contractor shall take into consideration schedule impacts in all program decisions and shall promptly notify the Government in writing of any changes having a significant (any impact which affects the date of a major milestone) impact on program progress and schedule or any schedule slippage along the critical path. The Contractor shall review the program status and schedule at scheduled program reviews. The Contractor shall use baseline scheduling with traceability to the original schedule as changes occur. The Contractor shall develop and utilize an Integrated Master Schedule (IMS) and Work Breakdown Structure (WBS) defining the authorized contract work in a manner that describes the sequence of work and identifies significant task relationships required to meet the requirements of the Contract. The Contractor shall maintain the schedule and make it available for Government inspection upon request during the Contract period of performance as well as present scheduling information at scheduled program reviews. The Contractor shall include in the schedule all specified work from the lowest defined WBS element to the Contract milestones. The Contractor shall identify key milestones, activities, and events that delineate significant decision points, constraints, and interfaces. The Contractor shall, as required or at the specific request of the Government, create and formalize a work-around schedule when out-of-schedule conditions indicate the need for managed departure from existing approved schedules. The Contractor shall report progress on a monthly basis.

3.1.2 Technical Data Package (CDRL A005, A006, A007)

The Contractor shall continue to maintain the BMS Sensor Suite TDP developed under the BMS Sensor Suite EDM and initial production programs. The TDP shall be kept current with all engineering changes including all drawings, data, parts lists, software modules, and processes during production. The Contractor shall provide information and support during the development of products to ensure supportability, maintainability and sustainability of the BMS Sensor Suite. The Contractor shall maintain the TDP in accordance with MIL-STD-31000A and the tailoring requirements established in the Contract Data Requirements List (CDRL). The Contractor shall prepare the drawings that support the production and manufacture of Hardware Configuration Items (HCI) as part of the TDP. The technical drawing portion of the TDP shall be compliant with MIL-STD-31000A Section 4.2. This Production Level package includes applicable product data fully defining the approved EDM configuration and includes models, drawings, associated lists, specifications, standards, performance requirements, quality assurance provisions (QAP) using a production quality assurance program that meets the requirements of ISO 9001:2015 (for hardware) and IEEE/EIA 12207 (for software), software documentation and packaging details. Note this TDP only provides details for procurement of a production system and does not provide component or assembly level manufacturing details as the items are proprietary commercial off the shelf (COTS) items with modified packaging specific to the BMS platform. In the event an engineering change or a need for a deviation is identified, the Contractor shall submit engineering changes or requests for deviation in accordance with the Government approved Configuration Management (CM) plan.

3.1.3 Status and Metric Reporting (CDRL A002, A008, A009)

The Contractor shall submit a Monthly Progress Report, which includes documentation and reporting of program progress with status of schedule milestones, cost (for CPFF/Cost CLINs only), technical performance data, problem areas, and recommended corrective actions. Break out of costs will be by material, labor, etc., for Kongsberg Underwater Technology LLC and each subcontractor. The Contractor shall ensure that configuration management, quality assurance, manufacturing, and system integration topics are highlighted, and address action items in each monthly progress report. The Contractor shall develop, maintain and deliver a production schedule to the Government for review or inspection. The schedule shall contain milestones/events, key tasks (significant accomplishment) for each milestone/event, accomplishment criteria for each task, and an event-oriented timeline for the manufacture, assembly, inspection, painting/coating, acceptance testing, and delivery to the Government.

3.1.4 Meetings, Reviews, and Audits (CDRL A010)

The meetings or reviews described in section 3.1.7.1 shall form the basis for formal programmatic and technical reviews between the Government and Contractor. All presentation materials presented or used at all meetings and reviews shall be compatible with Microsoft PowerPoint or Adobe Acrobat.

3.1.5 Factory Acceptance Tests (FAT) (CDRL A011, A012, A013)

A FAT shall be conducted on each production unit. The Contractor’s internal records of QA testing shall be made available to the Government. The Government will review and approve test procedures. Factory acceptance testing shall include the tests necessary to prove the deliverable product is fully functional. FAT shall include Built-In Test (BIT)/Built-In Test Equipment (BITE), visual inspections, and physical measurements, as a minimum. If there are deficiencies cited during the FAT, the Contractor shall be responsible for correcting all deficiencies and retesting the system(s) to verify the corrections. The Contractor shall also be responsible for correcting these deficiencies in all production systems. The Government reserves the right to observe the processes, facilities, equipment, tooling, and testing as part of the FAT acceptance. The Contractor shall notify the program sponsor office (ONI MSPMO) and NSWC PCD by electronic mail of the FAT at least 30 days prior to the scheduled tests. Attendance at these tests is optional on the part of the Government and failure of the Government representative to attend shall not constitute an excusable delay on the part of the Contractor. The Contractor shall prepare a FAT Report which shall include, as appropriate, appendices, personal notes, test analyses, error analyses, confidence levels, all computerized data collection, and reduction results and shall deliver the report to the Government within 30 days after each FAT.

3.2 BMS Sensor Suite Software (Cassandra Software) Acquisition

3.2.1 Cassandra Software License Acquisition

This subsection provides for the production and delivery of complete control, visualization, storage (CVS), mission planning and execution, target database, and HISAS processing software licenses for the BMS.

3.2.2 Cassandra Software License Annual Maintenance Acquisition This subsection provides for an annual software license maintenance agreement where the Contractor will provide software system upgrades and updates in order to keep the system in compliance with all referenced Information Technology standards.

3.3 BMS Sensor Suite PMA Software License Acquisition

This subsection provides for the production and delivery of complete Post Mission Analysis Software Tool licenses tailored for the BMS.

3.4 BMS Sensor Suite Component Acquisition

The Contractor shall produce and deliver the following system components as defined in each contract task order:

ID

3.5 BMS Sensor Suite System Inspection and Routine Maintenance (CDRL A014)

This section provides for the Contractor to conduct complete system inspections and routine maintenance, as needed, on systems that have been previously deployed and possibly in need of repairs, updates, or other types of maintenance.

3.6 Engineering Services (CDRL A015, A016, A017, A018)

The Contractor shall supply engineering services for BMS Sensor Suite efforts for work not incumbent on any other subsections. Engineering services shall support the integration of the Engineering Development Model (EDM) and production systems and shall augment Government conducted work, including:

a) System software modifications and enhancements

b) System software documentation updates (as needed following requirement a)

c) Directed studies, analysis, and reports

d) Field services

e) Logistics support

f) Supply support

g) Training

h) Software Engineering (plan, develop, code, integrate, test, document)

i) Engineering Change Proposals

j) Notice of Revision

k) Life Cycle Management and Open Systems

l) Failure mode, effects, and criticality analysis (FMECA)

m) Provide fabrication services

n) Support required test events

o) Provide feedback to current production and continuing engineering programs

p) Provide system supportability

q) Provide component and electronics engineering and integration

r) Maintain BMS Sensor Suite mandated design performance capabilities such as systems engineering and efforts associated with engineering change proposals

s) Perform corrective maintenance

t) Perform preventive maintenance

u) Conduct refurbishment or repair of the BMS Sensor Suite including Root Cause Corrective Action (RCCA) and Engineering Investigation (EI) of failures.

Contractor work performed under Studies, Analysis, and Services shall not impact cost, schedule, or increase risk to other tasks without the approval of the NSWC PCD PCO. Engineering services resources, to include key personnel, key equipment, and other critical resources shall not receive priority over activity or delivery on any other task without approval of the NSWC PCD PCO.

When required, the Contractor shall send technicians to other than Contractor facilities to conduct repairs on BMS Sensor Suite or associated equipment. The Contractor shall provide all required tools, support equipment and diagnostic test equipment to conduct the repairs.

Schedules and locations of meetings shall be at the mutual agreement between the NSWC PCD and the Contractor.

3.7 Travel

The Contractor may be required to travel from the primary performance location when supporting this requirement. Travel in support of this requirement is anticipated to include, but may not be limited to, the following alternate performance locations:

San Diego, CA Norfolk, VA Groton, CT Panama City, FL

The number of times the Contractor may be required to travel to each location cited above may vary as program requirements dictate, provided that the total estimated travel cost is not exceeded. All travel requirements will be approved by the Contracting Officer via a TI. Before initiating any travel, the Contractor(s) shall submit a detailed and fully-burdened estimate that includes the number of employees traveling, their expected travel costs for airfare, lodging, per diem, rental car, taxi/mileage and any other costs or actions requiring approval. The travel estimate shall be submitted to the Contracting Officer's Representative (COR) and Contract Specialist. Actuals cost, resulting from the performance of travel requirements, shall be reported as part of the Contractor's monthly status report. The reportable cost shall also be traceable to the Contractor's invoice. The Contractor(s) will be reimbursed for its reasonable actual travel costs in accordance with HQ B-2-0020 Travel Cost – Alt I (NAVSEA)(Dec 2005). Travel expenses are limited by the Department of Defense Joint Travel Regulations.

Report progress in accordance with Paragraph 3.1.3

4.0 GOVERNMENT FURNISHED PROPERTY (GFP)

4.1 Government Furnished Equipment (GFE):

The Bulkhead Connectors and Bulkhead Connector Pressure Caps will be provided to the Contractor for use in assembling each Pressure Vessel C2 (see section 3.4) component. Both of these GFE items will be returned when the Pressure Vessel C2 is delivered to the Government.

All GFE components returned to the government shall be accounted for using the form DD-1149.

4.2 Government Furnished Material (GFM): None

4.3 Government Furnished Information (GFI):

NSWC PCD will provide pertinent information as requested or as it becomes available. All GFI shall be returned to the Government at the completion of the order.

5.0 SECURITY

This requirement is CUI. The Contractor shall not require access to nor be required to generate or store classified information to perform this requirement.

RELEASE OF INFORMATION

(a) Release of information shall be in accordance with Section I, Defense Federal Acquisition Regulation Supplement (DFARS) Clause 252.204-7000, Disclosure of Information.

(b) All technical data provided to the Contractor by the Government shall be protected from public disclosure in accordance with the markings contained thereon. All other information relating to the items to be delivered or services to be performed under this contract may not be disclosed by any means without prior approval of the appropriate NSWC PCD authority. Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nationals or by any other person or entity; publication of technical or scientific papers; advertising; or any other proposed public release. The Contractor shall provide adequate physical protection to such information to preclude access by any person or entity not authorized such access by the Government.

5.1 Controlled Unclassified Information (CUI)

Controlled unclassified information (CUI) is official information that requires the application of controls and protective measures for a variety of reasons and has not been approved for public release, to include technical information, proprietary data, information requiring protection under the Privacy Act of 1974, and Government-developed privileged information involving the award of contracts. CUI is a categorical designation that refers to unclassified information that does not meet the standards for National Security Classification under Executive Order 13526, but is (a) pertinent to the national interest of the United States or to the important interests of entities outside the Federal Government, and (b) under law or policy requires protection from unauthorized disclosure, special handling safeguards, or prescribed limits on exchange or dissemination.

5.2 Minimum Requirements for Access to Controlled Unclassified Information (CUI)

Prior to access, Contractor personnel requiring access to Department of the Navy (DON) controlled unclassified information (CUI) or "user level access to DON or DoD networks and information systems, system security and network defense systems, or to system resources providing visual access and/or ability to input, delete or otherwise manipulate sensitive information without controls to identify and deny sensitive information" contractors must have clearance eligibility, or submit an Electronic Questionnaire for Investigation Processing (SF 86) to NSWC PCD Security for processing and subsequent adjudication by the DON Central Adjudication Facility.

5.3 Minimum Protection Requirements for Controlled Unclassified Information

Security classification guides and unclassified limited documents (e.g., CUI), Distribution Statement Controlled) are not authorized for public release and, therefore, cannot be posted on a publicly accessible webserver or transmitted over the Internet unless appropriately encrypted.

5.4 CUI

CUI is a document designation, not a classification. CUI is used by Department of Defense (DoD) and a number of other federal agencies to identify information or material, which although unclassified, disclosure to the public of the information would reasonably be expected to cause a foreseeable harm to an interest protected by one or more provisions of the Freedom of Information Act (FOIA). This includes information that qualifies for protection pursuant to the provisions of the Privacy Act of 1974, as amended. CUI must be marked, controlled and safeguarded in accordance with DoDI 5200.48, Controlled Unclassified Information (CUI)

5.5 Security of Unclassified DoD Information on Non-DoD Information Systems (DoDI 8582.01) DoD Policy

Adequate security shall be provided for all unclassified DoD information on non-DoD information systems. Appropriate requirements shall be incorporated into all contracts, grants, and other legal agreements with non-DoD entities.

DoD policy: Information Safeguards are applicable to unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems, to the extent provided by the applicable contract, grant, or other legal agreement with the DoD.

Information Safeguards are applicable to unclassified DoD information that has not been cleared for public release may be disseminated by the Contractor, grantee, or awardee to the extent required to further the contract, grant, or agreement objectives, provided that the information is disseminated within the scope of assigned duties and with a clear expectation that confidentiality will be preserved. Examples include:

a. Non-public information provided to a Contractor (e.g., with a request for proposal).

b. Information developed during the course of a contract, grant, or other legal agreement (e.g., draft documents, reports, or briefings and deliverables).

c. Privileged information contained in transactions (e.g., privileged contract information, program schedules, contract-related event tracking).

It is recognized that adequate security will vary depending on the nature and sensitivity of the information on any given non-DoD information system. However, all unclassified DoD information in the possession or control of non-DoD entities on non-DoD information systems shall minimally be safeguarded as follows:

a. Do not process unclassified DoD information on publically available computers (e.g., those available for use by the general public in kiosks or hotel business centers).

b. Protect unclassified DoD information by at least one physical or electronic barrier (e.g., locked container or room, logical authentication or logon procedure) when not under direct individual control of an authorized user.

c. At a minimum, overwrite media that have been used to process unclassified DoD information before external release or disposal.

d. Encrypt all information that has been identified as CUI when it is stored on mobile computing devices such as laptops and personal digital assistants, compact disks, or authorized removable storage media such as thumb drives and compact disks, using the best encryption technology available to the Contractor or teaming partner.

e. Limit transfer of unclassified DoD information to subcontractors or teaming partners with a need to know and obtain a commitment from them to protect the information they receive to at least the same level of protection as that specified in the contract or other written agreement.

f. Transmit e-mail, text messages, and similar communications containing unclassified DoD information using technology and processes that provide the best level of privacy available, given facilities, conditions, and environment. Examples of recommended technologies or processes include closed networks, virtual private networks, public key-enabled encryption, and transport layer security.

g. Encrypt organizational wireless connections and use encrypted wireless connections where available when traveling. If encrypted wireless is not available, encrypt document files (e.g., spreadsheet and word processing files), using at least application-provided password protected level encryption.

h. Transmit voice and fax transmissions only when there is a reasonable assurance that access is limited to authorized recipients.

i. Do not post unclassified DoD information to website pages that are publicly available or have access limited only by domain or Internet protocol restriction. Such information may be posted to website pages that control access by user identification and password, user certificates, or other technical means and provide protection via use of transport layer security or other equivalent technologies during transmission. Access control may be provided by the intranet (vice the website itself or the application it hosts).

j. Provide protection against computer network intrusions and data exfiltration, minimally including:

(1) Current and regularly updated malware protection services, e.g., anti-virus, anti-spyware.

(2) Monitoring and control of both inbound and outbound network traffic (e.g., at the external boundary, sub-networks, individual hosts), including blocking unauthorized ingress, egress, and exfiltration through technologies such as firewalls and router policies, intrusion prevention or detection services, and host-based security services. Prompt application of security-relevant software patches, service packs, and hot fixes.

k. Comply with other current Federal and DoD information protection and reporting requirements for specified categories of information (e.g., medical, proprietary, Critical Program Information (CPI), personally identifiable information, export controlled) as specified in contracts, grants, and other legal agreements.

l. Report loss or unauthorized disclosure of unclassified DoD information in accordance with contract, grant, or other legal agreement requirements and mechanisms.

m. Do not use external IT services (e.g., e-mail, content hosting, database, document processing) unless they provide at least the same level of protection as that specified in the contract or other written agreement.

5.6 Operations Security

Operations Security (OPSEC) is concerned with the protection of critical information: facts about intentions, capabilities, operations, or activities that are needed by adversaries or competitors to bring about failure or unacceptable consequences of mission accomplishment.

Critical information includes information regarding:

· Operations, missions, and exercises, test schedules or locations;

· Location/movement of sensitive information, equipment, or facilities;

· Force structure and readiness (e.g., recall rosters);

· Capabilities, vulnerabilities, limitations, security weaknesses;

· Intrusions/attacks of DoD networks or information systems;

· Network (and system) user identifications and passwords;

· Movements of key personnel or visitors (itineraries, agendas, etc.); and - Security classification of equipment, systems, operations, etc.

The Contractor, subcontractors and their personnel shall employ the following countermeasures to mitigate the susceptibility of critical information to exploitation, when applicable:

· Practice OPSEC and facilitate OPSEC awareness;

· Immediately retrieve documents from printers assessable by the public;

· Shred sensitive and Controlled Unclassified Information (CUI) documents when no longer needed;

· Protect information from personnel without a need-to-know;

· When promulgating information, limit details to that essential for legitimacy;

· During testing and evaluation, practice OPSEC methodologies of staging out of sight, desensitization, or speed of execution, whenever possible.

6.0 DATA DELIVERABLES

Data shall be delivered in accordance with the attached Contract Data Requirements List (CDRL) (DD Form 1423).

7.0 GOVERNMENT AND CONTRACTOR RELATIONSHIP

(a) The services to be delivered under this Task Order are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Task Order between the Government and the Contractor's personnel. It is, therefore, in the best interest of the Government to afford both parties a full understanding of their respective obligations.

(b) All Contractor, Subcontractor, and consultant personnel shall wear prominently displayed identification badges at all times when performing work on NSWC PCD property or attending meetings in the performance of this Task Order. The badge shall contain the individual's name, the company name and logo. When participating in such meetings (e.g., as a speaker, panel member), those individuals in Contractor employ must supplement physical identification (e.g., badges, place markers) with verbal announcements so that it is clear to the assembled group that they are employees of the Contractor, not NSWC PCD employees. In addition, when working on NSWC PCD property, all Contractor, Subcontractor, and consultant personnel shall have signs visible on their desks or at their work sites that clearly state that they are not NSWC PCD employees.

(c) The Contractor is responsible for supervision of all Contractor personnel assigned to this Task Order. The Contractor shall exercise ultimate over all aspects of Contractor personnel day-to-day work under this Task Order including the assignment of work, means and manner of Contractor employee performance and the amount of Contractor supervision provided. The Contractor shall be ultimately responsible for all aspects of performance under this Task Order including the work of its Contractor personnel.

Contractor personnel under this Task Order shall not:

(1) Be placed in a position where they are under the supervision, direction, or evaluation of a Government employee.

(2) Be placed in a position of command, supervision, administration or control over Government personnel, or over personnel of other Contractors under other NSWC PCD contracts, or become a part of the Government organization.

(3) Be used in administration or supervision of Government procurement activities.

(4) Have access to proprietary information belonging to another without the express written permission of the owner of that proprietary information.

(d) Employee Relationship:

(1) The services to be performed under this Task Order do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.

(2) Rules, regulations, directives and requirements that are issued by the U.S. Navy and NSWC PCD under its responsibility for good order, administration, and security are applicable to all personnel who enter the Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with non-personal services Task Order.

(e) Inapplicability of Employee Benefits: This Task Order does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

(1) Payments by the Government under this Task Order are not subject to the Federal income tax withholdings.

(2) Payments by the Government under this Task Order are not subject to the Federal Insurance Contributions Act.

(3) The Contractor is not entitled to unemployment compensation benefits under the Social Security Act, as amended, by virtue of performance of this Task Order.

(4) The Contractor is not entitled to workman's compensation benefits by virtue of this Task Order.

(5) The entire consideration and benefits to the Contractor for performance of this Task Order are contained in the provisions for payment under this Task Order.

(f) Notice. It is the Contractor's, as well as, the Government's responsibility to monitor Task Order activities and notify the Contracting Officer if the Contractor believes that the intent of this clause has been or may be violated.

(1) The Contractor should notify the Contracting Officer in writing promptly, within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this clause. The notice should include the date, nature, and circumstances of the conduct, the name, function and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct, identify any documents or substance of any oral communication involved in the conduct, and the estimate in time by which the Government must respond to this notice to minimize cost, delay or disruption of performance.

(2) The Contracting Officer shall promptly, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:

(i) confirm the conduct is in violation and when necessary direct the mode of further performance,

(ii) countermand any communication regarded as a violation

(iii) deny that the conduct constitutes a violation and when necessary direct the mode of further performance; or

(iv) in the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor and the date.

8.0 PERFORMANCE BASED REQUIREMENTS

The Task Order service requirements are summarized below into Performance Objectives, Performance Standards and Acceptable Quality Levels (AQLs) that relate directly to mission essential items. The performance thresholds describe the minimally acceptable levels of service required for each requirement and are considered critical to mission success. Procedures as set forth in the FAR 52.246-5, Inspection of Services – Cost Reimbursement, shall be utilized to remedy all deficiencies. (IF FFP USE FAR 52.246-4, Inspection of Services – Firm Fixed Price)

Objective

Method

Performance Work Statement (PWS) para. 3.1.1 Program Management and Controls Develop and deliver Integrated management Report 100% of documentation inputs are provided by due dates

FAR 52.246-5

Inspection of Services – Cost Reimbursement

Performance Work Statement (PWS) para. 3.1.1 and 3.1.3 Program Management and Controls Develop and maintain an Integrated Master Schedule (IMS)

FAR 52.246-5

Inspection of Services – Cost Reimbursement

Performance Work Statement (PWS) para. 3.1.1 Program Management and Controls

FAR 52.246-5

Inspection of Services – Cost Reimbursement

Performance Work Statement (PWS) para. 3.1.1 Program Management and Controls Develop and maintain a Work Breakdown Schedule (WBS)

FAR 52.246-5

Inspection of Services – Cost Reimbursement

Performance Work Statement (PWS) para. 3.1.2 Technical Data Package

FAR 52.246-5 Inspection of Services – Cost Reimbursement

Performance

(PWS) para. 3.1.2 Technical Data Package

FAR

52.246-5 Inspection of Services – Cost Reimbursement

Performance Work Statement (PWS) para. 3.1.2 Technical Data Package

FAR 52.246-

5 Inspection of

Performance

(PWS) para. 3.1.3 Status and Metric Reporting Provide Status Reports

CDRL.

In accordance with

FAR 52.246-5

Inspection of Services – Cost Reimbursement

Performance Work Statement (PWS) para. 3.1.3 Status and Metric Reporting Maintain Configuration Management Plan

(CMP)

FAR 52.246-5

Inspection of

Performance

(PWS) para. 3.1.4 Meetings, Reviews, and Audits Presentation Material

FAR 52.246-5

Inspection of

Performance

(PWS) para. 3.1.5 Factory Acceptance Tests Maintain Quality Assurance Testing records

FAR 52.246-5

Inspection of Services – Cost Reimbursement

Performance Work Statement (PWS) para. 3.1.5 Factory Acceptance Tests Develop and Maintain Factory Acceptance Test Plan

FAR 52.246-5

Inspection of

Performance

(PWS) para. 3.1.5 Factory Acceptance Tests Develop FAT Report Submitted material is technical accurate and grammatically correct.

Documentation delivered IAW CDRL. FAT report is delivered IAW agreed upon schedule. 100% of FAT reports are provided by due dates.

FAR 52.246-5

Inspection of

Performance

(PWS) para. 3.5 BMS Sensor Suite System Inspection and Routine Maintenance Maintenance Service Report

MSR

Submitted material is technical accurate and grammatically correct.

Documentation delivered IAW CDRL. MSR is delivered IAW agreed upon schedule. 100% of MSR’s are provided by due dates.

FAR 52.246-5

Inspection of

Performance

(PWS) para. 3.6 Engineering Services Engineering Support Documentation Submitted material is technical accurate and grammatically correct. Documentation delivered IAW CDRL.

Documentation is delivered IAW agreed upon schedule. 100% of documents are provided by due dates.

FAR 52.246-5

Inspection of Services – Cost Reimbursement

Performance Work Statement (PWS) para. 3.6 Engineering Services Develop and Maintain Engineering Change Proposals

(ECP)

Submitted material is technical accurate and grammatically correct. Documentation delivered IAW CDRL.

Documentation is delivered IAW agreed upon schedule. 100% of documents are provided by due dates.

FAR 52.246-5

Inspection of Services – Cost Reimbursement

Performance Work Statement (PWS) para. 3.6 Engineering Services Develop and Maintain Notice of Revisions

(NOR)

Submitted material is technical accurate and grammatically correct. Documentation delivered IAW CDRL.

Documentation is delivered IAW agreed upon schedule. 100% of documents are provided by due dates.

FAR 52.246-5

Inspection of Services – Cost Reimbursement

Performance Work Statement (PWS) para. 3.6 Develop Root Cause Corrective Action and

FAR 52.246-5

Inspection of

Engineering Services Engineering Investigation

IAW CDRL.

Documentation is delivered IAW agreed upon schedule. 100% of documents are provided by due dates.

Services – Cost

9.0 DISTRIBUTION STATEMENTS

Technical documentation generated under this contract shall carry the following distribution limitation statement. Word processing/electronic files shall have the statements included in the file such that the first page of any resultant hard copy shall display the statements. For drawings, the statements shall be as near to the title as possible without obscuring any detail of the drawing. Additionally, any DVD or CD-ROM delivered shall be marked externally with the statements.

DISTRIBUTION STATEMENT “F”: DISTRIBUTION RESTRICTION: FURTHER

DISSEMINATION ONLY AS DIRECTED BY THE COMMANDER, OFFICE OF NAVAL

INTELLIGENCE (ONI-34) (NOVEMBER 2007) OR HIGHER DOD AUTHORITY

DESTRUCTION NOTICE - CLASSIFIED INFORMATION, DESTROY IN ACCORDANCE

WITH SECNAV M-5510.36, (DON INFORMATION SECURITY PROGRAM) OR NISPOM

RULE. UNCLASSIFIED LIMITED DOCUMENTS, (E.G., CUI, DISTRIBUTION

STATEMENT CONTROL) DESTROY BY ANY METHOD THAT WILL PREVENT DISCLOSURE OF CONTENTS OR RECONSTRUCTION OF THE DOCUMENT.

10.0 ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA)

Report in accordance with basic contract PWS paragraph 6.0.