MSV(L)_DRAFT_-_Statement_of_Work_(SOW).pdf

DRAFT

Army Watercraft Systems Maneuver Support Vessel (Light) –

(MSV(L))

Statement of Work Section C

Version 41

MSV(L) Section C

CONTENTS

Introduction

System Requirement

Key Roles

Integrated Product Teams (IPTs)

Contract Data Requirements

Contracting Officers Representatives (CORs)

Internet Based Collaboration

Integrated Master Schedule (IMS) CDRL Changes

Cybersecurity

Controlled Unclassified Information (CUI)

Distribution Statements

Operations Security (OPSEC)

Security Classification Guide (SCG)

Contractor Proposals

Communications Security (COMSEC)

Receiving and Generating Classified Information

Security Training

Program Protection Working Group and Critical Program Information Assessment (CPIA)

Office Space

Desk Requirements

Telephones

Printing Capability

Toilet Facilities

Internet Access

Risk Management IPT

Risk Identification

Risk Management

Sub-contractor Risks

Participation and Administration

Start of Work Meeting (SOWM)

Business Management Reviews

Design Reviews

Major Reviews

System Design, Analysis, and Reports

Configuration Planning and Management

Functional Baseline

Allocated Baseline

Initial Product Baseline

Final Product Baseline

Maintenance of Configuration Documentation

Data Rights Markings on Tech Data Deliverables

Configuration Change Management

Technical Data Package (TDP)

ESOH Working Group (WG)

Environmental Compliance

Hazardous Materials Management (HAZ MAT)

Prohibited Materials

HAZMAT Waivers

Hazard Tracking System (HTS)

Safety Assessment Report (SAR)

System Safety Program Plan (SSPP)

Health Hazard Analysis (HHA)

HAZMAT Management Report (HMMR)

Environmental Protection Agency (EPA) Emissions Requirements

HSI Management Execution

Human Factors Evaluation

Contractor Corrosion Planned Activity Considerations

Deck Test Panels

Welding Procedures

Weld Repair Procedures

Weld Equipment

Welding Inspectors

Welder, Welding Operators, and Tack Welders

Armor Welding Design

Nondestructive Testing

Welding Fixtures

Contractor RAM Program

Reliability Predictions

Key Component RAM Data

Test Overview

Test Integrated Master Schedule

Government Witness of Contractor Testing

Scale Model Manufacturing and Testing

Component and Sub-system Testing

Contractor Vessel Testing

Contractor Personnel Support

Ballistic Testing

Production System Acceptance Tests

Corrective Acton

Corrective Action Cost

Corrective Action Approval

IPS Program

IPS Considerations ..................................... Error! Bookmark not defined.

IPS Program Management .......................... Error! Bookmark not defined.

IPS Program Management Plan .................. Error! Bookmark not defined.

IPS Management Control Log ..................... Error! Bookmark not defined.

Maintenance Concept and Maintenance Planning ..... Error! Bookmark not defined.

Correction of Errors ..................................... Error! Bookmark not defined.

Technical Manual Quality Assurance (TMQA) Program Plan .............. Error!

Bookmark not defined.

Technical Manual Plan ................................ Error! Bookmark not defined.

Logistics IPS SOWM ................................... Error! Bookmark not defined.

Interim Contractor Logistics Support (ICLS) Error! Bookmark not defined.

ICLS Metrics Reporting ............................... Error! Bookmark not defined.

Spares and Parts Management ................... Error! Bookmark not defined.

Warranty Management ................................ Error! Bookmark not defined.

PROVISIONING PROGRAM ...................... Error! Bookmark not defined.

Item Unique Item Identification .................... Error! Bookmark not defined.

Publications Program .................................. Error! Bookmark not defined.

Contractor Validation ................................... Error! Bookmark not defined.

Government Verification .............................. Error! Bookmark not defined.

Logistic Demonstration (LD) ........................ Error! Bookmark not defined.

Diminishing Manufacturing Sources and Material Shortages (DMSMS).

.................................................................... Error! Bookmark not defined.

Total Package Fielding (TPF) ...................... Error! Bookmark not defined.

Logistics Package Maintenance .................. Error! Bookmark not defined.

GFE / Government Furnished Information (GFI)

MISSING INFORMATION

MISSING INFORMATION

MISSING INFORMATION

Command, Control, Communications, Computers, Intelligence, Surveillance, Reconnaissance (C4ISR) and Subsystems

Test Vessel Refurbishment

GENERAL

Introduction

This Statement of Work (SOW) describes the requirement for the development, test, production, training, fielding and support of the Maneuver Support Vessel (Light) (MSV(L)). This SOW is intended to cover the ten year period of this contract; the Engineering and Manufacturing Development (EMD) Phase, the Low Rate Initial Production (LRIP) phase, and the Production phase. Estimated quantities are as follows:

One (1 ) MSV(L) for performance testing during EMD.

Four (4) LRIP MSV(L)s for verification of logistic products and Production Verification Testing (PVT).

Thirty-two (32) additional Full Rate Production (FRP) vessels; estimated total vessels thirty-seven (37).

System Requirement

For the duration of the contract, the contractor shall be responsible for the overall component selection, (with the exception of Government Furnished Equipment (GFE)), design, development, integration, fabrication and testing of the MSV(L) to meet the requirements of Army Technical Purchase Description (ATPD) (Attachment 0001 and the classified section of the ATPD, Attachment 0002). The contractor shall employ the American Bureau of Shipping (ABS) to certify the MSV(L) design, and shall build to ABS High Speed Craft (HSC) rules. The contractor shall coordinate, gain,and maintain ABS classification for the duration of the contract for each MSV(L). The contractor shall provide access to Product Director Army Watercraft Systems (PD AWS) for ABS correspondence, i.e, letters, reports, reviews, certifications, etc.

Additionally, this SOW will specify the deliverables, support requirements for all Government conducted testing including but not limited to PVT, Logistics Demonstrations (LD), Operational Test (OT), Technical Manual (TM) development, and contractor validation and Government verification. The contractor shall be responsible for conducting scale model testing and must successfully demonstrate hull form and vessel stability prior to proceeding with building the full-scale prototype MSV(L). All testing and trials, through EMD and LRIP, must be successfully completed prior to proceeding to Full Rate Production (FRP). The Government will be the approval authority for contractor Detailed Test Plans (DTP) and will witness contractor-conducted testing. The Government will be responsible for conducting Human Factors Evaluation

(HFE), Electro-Magnetic Interferenc and Electro-Magnetic Compatibility (EMI/EMC) tests, and weapons performance test during the EMD phase. Reliability, Availability, and Maintainability (RAM) verification testing will be conducted in conjunction with all testing.

PROGRAM STRUCTURE AND MANAGEMENT

Key Roles

The contractor shall define and ensure key roles (e.g. Program Director and Integrated Product Team (IPT) leads) are staffed with personnel with commensurate education, training, work experience, and technical training necessary to effectively and efficiently perform the required tasks. Details of the key roles will be identified at the Start of Work Meeting (SOWM).

Integrated Product Teams (IPTs)

Any joint, deliberative or task-focused body, regardless of its formal or informal title, (e.g., "Working Group," "Integrated Design Team", etc.) shall be considered an Integrated Product (or Process) Team, or "IPT". IPTs shall be established to serve as the primary management tool and key method of communication for this contract. The first IPT meetings shall be held concurrently with the SOWM. Subsequent IPT meetings shall be held weekly, by phone, unless the Government and contractor agree to meet less frequently. The contractor shall be responsible for developing all IPT agendas and meeting minutes IAW Conference Agenda, CDRL A001, and Report, Record of Meeting Minutes, CDRL A002. The IPT meeting minutes shall be made available to the Government and discussed at subsequent IPT meetings. The contractor shall allow physical and dial-in access to the Government for all contractor IPT meetings and any contractor design reviews following the SOWM event, in order to allow mutual understanding, maintain the program direction, and ensure contractual requirements are being met. IPT Leaders and Co-Leaders shall be identified at the SOWM.

Contract Data Requirements

Data shall be delivered IAW the DD Form 1423, CDRLs. DIDs called out in the CDRLs can be found in the ASSIST website at http://quicksearch.dla.mil/. If data deliverables require revision after original delivery, and the date for delivery cannot be determined at time of award, the contractor shall deliver the data on a date mutually agreed to by the contractor and PCO. Except for those items that specifically require hard copy submission, all data specified in this contract shall be provided to the Government electronically through the Integrated Data Environment (IDE) unless otherwise specified in the CDRL.

Contracting Officers Representatives (CORs)

The Government will designate CORs. The CORs will be designated IAW DFARS 201.602-2 and authorized in writing by the PCO to perform specific technical functions.

The contractor will receive a copy of the COR appointment letters after award that will specify the extent of the COR authority to act on behalf of the PCO. The COR is NOT authorized to make any commitments or changes that will affect price, quantity, delivery or any other term or condition of this contract.

Internet Based Collaboration

The IDE consists of internet-based collaboration tools that shall be used to facilitate information sharing and collaboration within an encrypted Government server environment that provides controlled, distributed access to MSV(L) program information, both released and in-work. Types of information that shall be processed and maintained within the IDE will include MSV(L) program documents, reports, program management data, meeting-related information, modeling and simulation or analysis data, pertinent manufacturing information, and test data, consistent with the Army Watercraft Systems (AWS) Interim Security Classification Guide (Attachment 0003). Any posting to the IDE is considered a data deliverable in the context of Defense Federal Acquisition Regulation Supplement (DFARS) Data Rights clauses, including 252.227-7013 and 252.227-7014. The IDE shall only be used for sharing Controlled Unclassified Information (CUI) information. All classified information shall be sent via registered or express mail to the MSV(L) classified mailing address.

Government Sponsored Accounts

The Government will sponsor Army Knowledge Online (AKO), SharePoint, and any other required accounts. Personally Identifiable Information (PII) cannot be stored on SharePoint. Details will be provided at the SOWM. The Government can only sponsor accounts for U.S. Citizens. The contractor shall provide names, contact information, level of access (upload or download), and training required for personnel requiring access to these accounts not later than SOWM. All contractor and sub-contractor employees requiring access to these accounts must successfully complete the Department of Defense (DoD) Information Assurance Awareness training; this must be accomplished before approval will be given to access these accounts. The DoD Information Assurance Awareness training will be an annual requirement, thereafter.

The Army Training Certification Tracking System (ATCTS) is located here:

https://atc.us.army.mil/iastar/index.php and the required training will be offered through this site.

Access to Government Systems

In order to access these systems, the contractor shall have or obtain an External Certification Authority (ECA) Certificates, or a DoD Common Access Cards (CAC) for the appropriate personnel. Details on the ECA program and authorized ECA vendors can be found at: http://iase.disa.mil/pki/eca/. Request for access to any other Government systems shall go through the PCO. The contractor shall designate an Information Assurance (IA) Officer to work with PD AWS and the Government IA Manager in order to obtain and implement usage of the CAC program in compliance with DoD Directive 8190.3 Smart Card Technology, and DoD 8520.2, Public Key Infrastructure (PKI) and Public Key (PK) Enabling.

CAC Automated contractor Verification System

CAC Applications

The contractor shall appoint an Information Assurance Officer to process CAC applications for its employees and Subcontractor employees IAW FAR 52.204-9, Personal Identity Verification of contractor Personnel, DoD Directive 8190.3 Smart Card Technology and DoD Instruction 8520.2 Public Key Infrastructure and Public Key Encryption.

Requests for CAC

The contractor shall submit requests for CAC via email to the COR.

Contractor Verification System (CVS)

The Government will establish a CVS application account for each CAC request and provide each contractor and subcontractor employee an User Identification (ID) and password via email.

CVS Access

The contractor’s and subcontractor’s employees shall access the CVS account and complete the CAC application.

CAC Request Status

The Government will inform the contractors and subcontractors employee via email the status of the CAC request. The status will be one of the following: (1) Approved;

contractor shall proceed to nearest Real-Time Automated Personnel Identification System (RAPID) Defense Enrollment and Eligibility Reporting System (DEERS) location to obtain CAC. (2) Returned; additional information or correction to application required by contractor employee. (3) Rejected; Government in separate correspondence will provide reason(s) for rejection.

CAC Approved and Rejected Applications

The contractor shall maintain records of all approved and rejected CAC applications.

CAC Period of Performance

Issued CACs may be for a period of performance not longer than two years or the contract performance completion date (inclusive of all options), whichever is earlier. If a requirement for a CAC exists beyond two years, the contractor shall submit a new request.

CAC Return

The contractor shall return issued CACs to the DEERS office IAW FAR 52.204-9. The contactor shall notify the Government of all CACs returned to the DEERS Office.

Integrated Master Schedule (IMS) CDRL Changes

The contractor shall notify the Government no later than 10 business days prior to a foreseen baseline date change to all CDRL deliveries. The notification shall include: (1) the reason for the change and (2) the revised schedule. The Government reserves the right to review and approve any contractor proposed IMS updates that impact contract delivery schedules. The Integrated Master Schedule shall be provided IAW CDRL A003.

IMS Planned Activity Changes

The contractor shall notify the Government of a change to a date of an planned activity no later than 14 calendar days prior to the start of that planned activity. The notification shall include: (1) the reason for the change and (2) the revised schedule. Failure to notify the Government within the required timelines shall result in the contractor being required to reconduct some or all of the plan activity at the Government’s discretion at no additional cost to the Government. The Government reserves the right to review and approve any contractor proposed IMS updates that impact contract delivery schedules.

Cybersecurity

Cybersecurity Program Plan

The contractor shall provide a Cybersecurity Program Plan IAW CDRL A004. The contractor shall manage security activities at the unclassified, CUI, and all applicable classification levels encompassing all security disciplines (Information Security, Operations Security, Anti-Terrorism and Force Protection, International Security, Physical Security, Communications Security, Information Systems Security, and Personnel Security). This requirement is to utilize the above security functions to protect the programs information and technology.

Cybersecurity Accreditation Artifact Package

For the life of the contract, the contractor shall provide a Cybersecurity Artifact Package

IAW CDRL A005.

Cybersecurity and Software Scans

For the life of the contract, the contractor shall provide the Government access to the software source code repositories for all MSV(L) software (excluding closed-source Commercial Off The Shelf (COTS)) for Software Code Scans to determine if there are any vulnerabilities in the system. The contractor shall ensure each source code repository can accept the Government's Hewlett Packard (HP) Fortify 360 Suite Static Code Analyzer scanning software tool.

Baseline Cybersecurity and Software Scan

For the life of the contract, The contractor shall provide the Government access to the contractor System Integration Lab (CSIL) for the Baseline Cybersecurity scan. The Baseline Scans shall be held NLT 150 calendar days after Contract Award.

Follow-on Cybersecurity Scans

For the life of the contract, the contractor shall provide the Government access to the CSIL for additional testing identified at the Baseline Cybersecurity and Software Code Scans. The follow-on-scans will only be conducted if the baseline scan requires action on the contractor's part to resolve deficiencies.

Recurring Cybersecurity and Software Scans

For the life of the contract, the contractor shall provide the Government access to the CSIL and software source code repositories for all MSV(L) software and systems for recurring scans. The scans shall be conducted not less than annually and following significant changes to the MSV(L) software or architecture.

Telecommunications Electronics Material Protected from Emanating

Spurious Transmissions (TEMPEST) Review

The contractor shall provide C4ISR SMEs; vessel access, documentation for all vessel and equipment (CFE & GFE) configurations; vessel wiring diagrams and routing locations; types and locations of lighting during TEMPEST reviews with a CTTA (Certified TEMPEST Technical Authority). The technical reviews shall consist of a TEMPEST Baseline Review to the vessel equipment or wiring. The results of the TEMPEST reviews will determine the extent of vessel. TEMPEST testing. The TEMPEST Baseline review shall be held NLT 180 calendar days after Contract Award.

The Government estimates the contractor to provide two (2) SMEs for ten (10) business days for the TEMPEST Baseline review and no more than five (5) business days for Follow-On reviews. TEMPEST reviews shall occur at the contractor’s facility.

Tactical Public Key Infrastructure (TPKI) Implementation Analysis

The contractor shall conduct an analysis to determine how PKI could be integrated into the MSV(L) computing enclaves to provide identification, digital signature for communications and software (CFE and GFE), and encryption. The analysis shall include plans for a ruggedized PKI token (used for group and individual certificates), PKI authentication infrastructure and interoperation with DoD GIG PKI, and future interface with GFE devices that will utilize MSV(L) and MSV(L)-hosted resources to connect to the GIG. (Tactical Public Key Infrastructure Implementation Analysis, CDRL A006).

Cybersecurity Workforce

For the life of the contract, the contractor shall designate at least one individual as subject matter expert for Cybersecurity in the MSV(L). This person will be the single point of contact in regard to all Cybersecurity issues at the contractor’s facility. The contractor's Cybersecurity subject matter expert shall meet the requirements for IA Technical (IAT) Level III IAW DoD 8570.01-M, Information Assurance Workforce Improvement Program.

Cybersecurity Testing

The contractor Cybersecurity personnel shall attend execution of and recovery from Cybersecurity readiness (Blue and Red Team) testing. Cybersecurity readiness testing will be conducted during the developmental and operational test and evaluation planned activity. The Government estimates the contractor to provide two (2) SMEs for 14 calendar days.

Cybersecurity Log Management Plan

For the life of the contract, the contractor shall conduct an analysis to determine how logistics files (e.g. security, system, application, firewall, antivirus) will be collected and archived from both classified and unclassified smart displays and network devices in the MSV(L). Once the plan is approved by the Government, the contractor shall adhere to all process and activities contained within the approved Cybersecurity Log Management Plan. (Cybersecurity Log Management Plan, CDRL A007)

Cybersecurity Vulnerability Management Software Maintenance Plan

For the life of the contract, the contractor shall conduct an analysis to determine how Information Assurance Vulnerability Alert (IAVA) patches and software updates (operating systems, applications and firmware) will be implemented across the active platforms including CSIL, GSIL, CM and test fleet, and to delivered operational fleet.

Implementation plan must address both cyclic and out-of-cycle updates based on severity. Once the plan is approved by the Government, the contractor shall adhere to all process and activities contained within the approved Cybersecurity Vulnerability Management Software Maintenance Plan. (Cybersecurity Vulnerability Management Software Maintenance Plan, CDRL A008)

Cybersecurity Vulnerability Management - Notification Monitoring

For the life of the contract, the contractor shall monitor Government, vendor, and industry releases by subscribing to vulnerability notification services and reviewing other data available to identify vulnerabilities in software and hardware in the MSV(L) C4I and Vetronics systems. The contractor shall subscribe to the Government email notifications from the Information Assurance Vulnerability Management notification system, currently hosted at https://iavm.csd.disa.mil/.

Cybersecurity Vulnerability Management – Database

For the life of the contract, the contractor shall maintain a database of vulnerabilities in software and hardware in the MSV(L) C4ISR and Vetronics systems. The database shall include the vulnerability identifier, severity, applicability to MSV(L) systems, and implementation status.

Cybersecurity Vulnerability Management - Software Code Scan

For the life of the contract, the contractor shall correct deficiencies identified in all software (including open source software) evaluated in the software code scans.

Annual Cybersecurity Review

For the life of the contract, the contractor shall provide C4ISR and Cybersecurity SMEs;

vehicle access; documentation for all vessel and equipment (CFE & GFE) configurations for joint Government and contractor annual security reviews. The reviews shall occur annually from the date of baseline cybesrsecurity and software scan.and annual security review. The Government estimates the contractor will need to provide two (2) SMEs for 5 work days per planned activity.

Controlled Unclassified Information (CUI)

CUI is unclassified information requiring application of access, distribution controls, and protective measures which meets the standards for safeguarding and dissemination controls pursuant to statute, and government-wide policies under Executive Order (EO) 13556. The types of information considered CUI for the program are technical data and information marked Unclassified//For Official Use Only (U//FOUO) by the U.S.

Government. Examples of technical data include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, catalog-item identifications, and related information, and computer software documentation. When handling U//FOUO information, the contractor shall adhere to the below guidelines, the DD Form 254, Attachment 0004, and the respective continuation sheets, DoDM 5200.01-V4, Army Regulation (AR) 25- 55, AR 25-2, and AR 25-11.

Distribution Statements

Marking of Technical Data will include the statement provided in the Security Classification Guide. If the contents of the technical document require more than one Distribution Statement, apply the most restrictive statement. This does not preclude additional mandated markings as may be required by the contract. Other request for this document shall be referred to AMSTA-CSS, 6501 E. 11 Mile Road, MS 105, Warren, MI

48397-5000, COM (586) 282-5862.

Operations Security (OPSEC)

If the contractor generates unclassified OPSEC sensitive information, this information will be protected at the same level as U//FOUO information. The contractor shall be responsible for the development of an OPSEC program, in accordance with DoDM 5205.02-M and AR 530-1, with specific features based on command or unit approved OPSEC requirements.

OPSEC Review

Because of antiterrorism/force protection, operations security, and counterintelligence concerns, the contractor will not release any diagrams, maps, floor plans, schematics, or digital pictures of any installations to outside organizations or companies without the approval of the COR and G2, TACOM LCMC. All information proposed for public release in any form (video, pictures, article, brochure, web site, etc.) will undergo a Program Executive Office (PEO) Combat Support and Combat Service Support (CS&CSS) OPSEC Review using the most current and approved PEO CS&CSS STA Form 7114.

OPSEC Sensitive Information

Examples of information that would be considered OPSEC sensitive: Equipment capabilities, limitations, and vulnerabilities; Detailed mission statements; Operation schedules; Readiness and vulnerability assessments; Test locations and dates;

Inventory charts and reports; Detailed budget data; Photographs of components;

Detailed organizational charts (with phones and e-mail listings); Technical and scientific data; Unclassified technical data with military applications; Critical maintenance information; Information extracted from a DoD Intranet web site; Lessons learned that could reveal sensitive military operations, exercises, or vulnerabilities; Logistics support (munitions, weapons, movement); Specific real time support to current or on-going military operations; Delivery schedules; and Manufacturing methods.

OPSEC Requests

OPSEC review requests should be sent to:

Program Security Manager, PM Transportation Systems

6501 E. 11 Mile Rd Warren, MI 48397

586-282-5862

Security Classification Guide (SCG)

Unclassified information will be protected in accordance with the applicable PEO CS&CSS Army Watercraft Systems Interim SCG (Attachment 0003) as well as the OPSEC Plan, respective DOD and Army Regulations, and additional guidance provided above.

Contractor Proposals

IAW the SCG, contractor proposals must be marked, handled, and stored as U//FOUO information.

Communications Security (COMSEC)

The contractor shall adhere to COMSEC guidelines and DoD and Army Regulations further identified in the attached DD Form 254 and their respective continuation sheets.

Receiving and Generating Classified Information

When receiving, generating, and/or handling classified information, the contractor shall adhere to the PEO CS&CSS Army Watercraft Systems Interim SCG, DoD 5220.22-M, the OPSEC Plan, and the attached DD Form 254 and their respective continuation sheets.

Security Training

All contractor personnel performing services in the execution of this contract shall complete the following training IAW respective security clauses as referenced in this contract: iWATCH; Antiterrorism Level I; and OPSEC training. The Government reserves the right to request completion verification from the contractor.

PROGRAM PROTECTION

The contractor shall comply with the security requirements imparted by the DD Form 254 (Attachment 0004), the National Industrial Security Program Operating Manual (NISPOM) DoD, 5220.22-M), and AR 70-77.

Program Protection Working Group and Critical Program Information Assessment (CPIA).

For the life of the contract, the contractor shall host a Program Protection Working Group (PPWG) not less than annually. The first PPWG shall be held as part of the Contract SOWM. Each PPWG will be chaired by the Government Systems Engineer and co-chaired by the contractor's System Security Engineer. The co-chair shall develop the agenda and action items (Reference CDRL A001, Agenda and CDRL A002, Report, Record of Meeting Minutes). The agenda will include a CPIA that will identify Critical Program Information (CPI) or CT (defined by DoDI 5200.39, July 16, 2008 Incl Change 1 Dec 28, 2010, CPI Protection within the DoD). Each PPWG will be a one day planned activity.

CONTRACTOR PROVIDED GOVERNMENT OFFICE SPACE

The contractor shall make available furnished office space, office equipment and telephones at the worksite for four Government representatives use. The site shall be capable of being secured and located in an area where the noise level does not exceed guidelines set by Occupational Safety and Health Administration (OSHA) for office environments. The office must be dedicated for use solely by the Government during the period of contract performance. The designated on-site Contracting Officer Representative (COR) must have a key to the office and the office must be accessible to the COR during the COR's normal working hours and days. The office must have heat, air conditioning, and lighting that is conducive to a good working environment.

Office Space

The office space must have, at a minimum, four desks, approximately 30” x 5’ (or larger) with two locking drawers and arm chairs. The keys to the desks shall be provided to the CORs.

Desk Requirements

A table or counter within the office space, approximately 4’ x 8’ (or larger) with six office chairs suitable for reading blueprints and conducting meetings shall be provided.

Telephones

Within the office space, telephones with dedicated touch tone line will be provided.

Printing Capability

A dedicated printer/scanner and copier, or equivalent multifunctional printer, co-located in the office space shall be provided. contractor shall provide toner and printer paper shall be provided.

Toilet Facilities

Toilet facilities within the same office area shall be provided.

Internet Access

Dedicated wired or wireless internet access for four computers at a speed of no less than four megabits per second (Mbit/s) downstream and 1 Mbit/s upstream (shared between two computers) shall be provided. Each Contracting Officer Representative (COR) and Subject Matter Expert (SME) will have full time access while performing duties.

RISK IDENTIFICATION AND MANAGEMENT

Risk Management IPT

For the life of the contract, the contractor shall conduct monthly Risk IPT with Government participation. The Risk IPT shall decide which risks are accepted, approved, and tracked at the system level.

Risk Identification

The contractor shall provide a Contractor Risk Management Plan (RMP) that outlines the processes and procedures for establishing and managing risks for the program IAW Contractor Risk Management Plan, CDRL A009. In this plan, the contractor shall show how risk sources and categories are determined, define risk parameters (such as likelihood, consequence, etc.) and establish thresholds to trigger management activities.

Supporting products to the risk management process, such as risk source lists, risk evaluation sheets, risk logs, vendor risk processes and supporting identification documentation, and watch lists shall be provided to the Government as supporting data.

The contractor shall update these throughout the performance of the contract IAW CDRL A009 and Government Risk Management Plan, Attachment 0005.

Risk Management

The contractor shall manage risks to the program and technical baselines through examination of each element in the Contract Work Breakdown Structure (CWBS). The contractor shall conduct formal risk assessments, interview SMEs, and utilize lessons learned from similar programs and products and conduct an examination of Government Furnished Information (GFI). The contractor shall produce a list of risks that shall be evaluated, categorized, and prioritized. The contractor shall establish a strategy to handle each risk, along with a strategy for the allocation of resources to support the management of the risk. The contractor shall develop and maintain a closure strategy for these risks. These closure strategies shall be reviewed and coordinated with the Government during the monthly Risk IPT. The contractor shall update these throughout the performance of the contract IAW CDRL A009 and Government Risk Management Plan, Attachment 0005.

Sub-contractor Risks

The contractor shall include risks identified by its subcontractors in the risk identification, tracking, and management listing.

MEETINGS, REVIEWS, AND REPORTING

Participation and Administration

The contractor shall plan, host, attend, coordinate, support and conduct the meetings and formal reviews as identified in this section. The reviews shall be conducted via

Government approved online meeting tool, teleconference, or face to face based on Government approval. All such reviews shall be included in the contrator’s IMS. The contractor shall consolidate meetings and reviews whenever practical to reduce administrative and travel cost. The Government reserves the right to cancel any review or to require any review to be scheduled at critical points during the period of performance. Upon mutual agreement between the contractor and the Government, meetings and review dates may be changed after agenda and meeting presentation material is delivered.

Agendas

The contractor shall submit an agenda for all meetings and reviews IAW Agenda, CDRL A001, which shall include discussions on contract progress and issues (e.g.

performance goals, schedule progress, risks and mitigation, and cost impact).

C.6.1.2 Minutes

The contractor shall record and provide meeting minutes for all meetings and reviews IAW CDRL A002. The contractor’s recorder shall be identified at the beginning of each meeting.

Start of Work Meeting (SOWM)

The contractor shall host a SOWM at the contractor's facility within 20 calendar days after contract award. The contractor shall provide an agenda and meeting minutes IAW CDRL A001 and A002. The SOWM will also include the review of the PD and other project requirements necessary to ensure contract compliance. The SOWM, to include the Logistic Integrated Product Support (IPS) SOWM IAW Section XXX, shall not exceed four calendar days.

Contractor Integrated Master Schedule (IMS)

The contractor shall develop, manage and present the contractor’s IMS at the SOWM IAW Integrated Master Schedule, CDRL A003. The schedule shall identify dates for all program events and data deliverables. The schedule will be reviewed by the Government and managed by the contractor for the life of the contract. The schedule and program progress will be reviewed at each In-Process Review (IPR), Production Management Review (PMR) and at applicable IPT meetings for the life of the contract.

For the life of the contract, the contractor shall develop and maintain, as a subset of the MSV(L) program IMS, an IPS Schedule to manage the MSV(L) IPS activities. The IPS Schedule shall reflect the details of the IPS work content requirements of this contract.

The contractor shall incorporate the IPS Schedule into the MSV(L) IMS (reference

CDRL 003).

SOWM Focus

The SOWM will focus on reviewing the following:

a. Contract terms and conditions

b. IMS

c. Data requirements and data development guidance

d. Required specifications

e. Test requirements and schedules

f. Program Schedule to include all Engineering and Integrated Logistics Support

(ILS) planned activities and data deliverables

g. Risk Management Plan

h. Initial Risk Assessment

i. Work Breakdown Structure (WBS)

j. Key Roles of personnel

k. CFE and GFE hardware review

l. Additional actions as determined by the SOWM Agenda

SOWM Key Roles

The contractor and Government shall identify the personnel assigned to key roles at the SOWM. The key roles are as follows: Program Manager, and leads for IPTs for Engineering, Logistics, Procurement, Purchasing, Quality, OPSEC, and Test. At SOWM, the contractor shall outline their plan for communicating and transitioning personnel changes throughout the duration of the contract. The contractor shall provide 20 calendar days written notice to the COR prior to the personnel transition and discussed at weekly IPT meetings.

Business Management Reviews

The contractor shall conduct by phone monthly reviews of the Performance and Cost Report, CDRL A010, at least two business days prior to each CDRL A010 submittal date. These reviews shall be supported by the appropriate contractor Program/Project Management, Business Management, and Technical personnel.

Performance and Cost Report

The contractor shall deliver a Performance and Cost Report, IAW CDRL A010. The information used to create the Performance and Cost Report shall be delivered to the Government and discussed at IPT meetings IAW CDRL A010.

Contractor Manpower Reporting (CMR)

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor will report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via secure data collection site. The contractor is required to completely fill in all required data fields in the format using the following web address: https://cmra.army.mil. The required information includes the following:

a. Contracting Office, PCO, Contracting Officer's Technical Representative;

b. Contract number, including task and delivery order number;

c. Beginning and ending dates covered by reporting period;

d. contractor name, address, phone number, e-mail address, identity of contractor employee entering data;

e. Direct labor hours (including sub-contractors);

f. Direct labor dollars paid this reporting period (including sub-contractors);

g. Total payments (including sub-contractors);

h. Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different);

i. Data collection cost;

j. Organizational title associated with the Unit Identification Code (UIC) for the

Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information);

k. Locations where contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website);

l. Presence of deployment or contingency contract language; and

m. Number of contractor and sub-contractor employees deployed in theater this reporting period (by country).

Reporting Inputs

Reporting inputs will be for the labor executed during the period of performance during each Government Fiscal Year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year of the contract. contractors may direct questions to the help desk at: https://cmra.army.mil.

EMD Cost and Software Data Reporting (CSDR)

The contractor shall collect actual contract costs, prepare, and submit IAW the CDRLs listed below and the EMD CSDR Plan (reference Attachment 0006). CSDR reporting is required for and shall include reporting against any and all costs expended by the contractor or subcontractors during the execution of this contract. The requirement to report costs is independent of the amount of costs incurred, the contract type used to award funding, the source of funding, or how the contractor executes the funds and scope associated with the contract. The Government may audit any CSDR deliverable for completion, correctness, and compliance to the associated DID, CDRL and EMD CSDR Plan (Attachment 0006). If at any point errors or deficiencies are found in a deliverable, the contractor shall, at their own expense, correct all deficiencies or errors and resubmit the deliverable.

Contract Work Breakdown Structure (CWBS) Index & Dictionary

The contractor shall produce, deliver, and maintain a product oriented Work Breakdown Structure (WBS) Index and Dictionary in accordance with the CSDR Plan (reference Attachment 0006). WBS Indices and Dictionaries shall be completed to at least the Level 3 specified in MIL-STD-881C Appendix E: Sea Systems (3 Oct 2011) unless otherwise specified by the EMD CSDR Plan (reference Attachment 0006). Any changes to an approved CWBS require Government approval. (Contract Work Breakdown Structure (CWBS) Index & Dictionary, CDRL A011)

Cost Data Summary Report (SDSR) (DD Form 1921)

The contractor shall prepare and submit the Cost Data Summary Report (DD Form 1921) which reports direct and indirect actual cost data on both a recurring and non-recurring basis by CWBS level as specified in the EMD CSDR plan (reference Attachment 0006). (Cost Data Summary Report (CDSR) (DD Form 1921), CDRL A012,)

Functional Cost-Hour Report (DD Form 1921-1)

The contractor shall prepare and submit a Functional Cost-Hour Report (DD Form 1921-1) which reports information on resources including labor hours, overhead costs, material costs, and other direct and indirect cost data on both a recurring and non-recurring basis by CWBS level as specified in the approved EMD CSDR plan (reference Attachment 0006). (Functional Cost-Hour Report (DD Form 1921-1), CDRL A013)

Software Resources Data Report (SRDR) Initial

The contractor shall prepare and submit the Software Resource Data Report (SRDR) which provides results of software development and upgrade efforts as specified in the approved EMD CSDR plan (reference Attachment 0006). (Software Resources Data Report: Initial Developer Report and Data Dictionary, CDRL A014)

Software Resources Data Report (SRDR) Final

The contractor shall prepare and submit the Software Resource Data Report (SRDR) which provides results of software development and upgrade efforts as specified in the approved EMD CSDR plan (reference Attachment 0006). (Software Resources Data Report: Final Developer Report and Data Dictionary, CDRL A015)

Other Cost Reports

Current and Prior Configuration Indentured Bill of Materials

The contractor shall prepare and maintain an indentured Bill of Materials (BOM) of any and all parts that are or were ever included in the MSV(L) configuration to include all ECPs, VECPs, and other configuration modifications. The indentured BOM shall be prepared in indenture level sequence and will report the current configuration (e.g. latest part numbers, includes ECOs and ECPs) and any prior BOM configurations (e.g.

obsolete part numbers, the configuration prior to ECPs cut-in) of the MSV(L). A mapping of the BOM to Level 3 WBS must be provided. (Bill of Material (BOM) mapped to Level

3 CWBS, CDRL A016)

Cost and Software Data Reporting (CSDR) Plan Readiness Review

NLT 45 calendar days after contract award, the contractor shall conduct a Cost and Software Data Reporting (CSDR) Plan Readiness Review. The purpose of this meeting is for the contractor to present their plan for implementing the CSDR requirements. The contractor shall describe the process to be used to satisfy the requirements of the CDRLs, listed above along with their associated data item descriptions (DIDs); demonstrate how contractor cost and data reporting (CCDR) will be based, to the maximum extent possible, upon actual cost transactions and not cost allocations; demonstrate how the data from its accounting system will be mapped into the CWBS included in the EMD CSDR Plan (Attachment 0006) and into the standard reporting categories required in the CCDR data item descriptions; describe how recurring and nonrecurring costs will be segregated; explain the methodology for reporting completed units on the DD Form 1921 reports; identify all potential problems with fulfilling the EMD CSDR Plan requirements; and provide comments regarding the adequacy of the EMD CSDR Plan (Attachment 0006). For planning purposes, this meeting is anticipated to be a one day teleconference. The contractor shall provide meeting minutes to the Government within 7 business days after the meeting. The Government will review the minutes and provide comments to the contractor within 5 business days. Final meeting minutes incorporating Government comments (if any) will be furnished to the Government NLT 17 business days after the meeting.

Production (LRIP & FRP) Cost and Software Date Reporting (CSDR)

The contractor shall collect actual contract costs, prepare, and submit IAW the CDRLs listed below and the Production CSDR Plan (reference Attachment 0007). CSDR reporting is required for and shall include reporting against any and all costs expended by the contractor or subcontractors during the execution of this contract. The requirement to report costs is independent of the amount of costs incurred, the contract type used to award funding, the source of funding, or how the contractor executes the funds and scope associated with the contract. The Government may audit any CSDR deliverable for completion, correctness, and compliance to the associated DID, CDRL and Production CSDR Plan (Attachment 0007). If at any point errors or deficiencies are found in a deliverable, the contractor shall, at their own expense, correct all deficiencies or errors and resubmit the deliverable.

Contract Work Breakdown Structure Index & Dictionary

The contractor shall produce, deliver, and maintain a product oriented Work Breakdown Structure (WBS) Index and Dictionary in accordance with the Production CSDR Plan (reference Attachment 0007). WBS Indices and Dictionaries shall be completed to at least the Level 3 specified in MIL-STD-881C Appendix E: Sea Systems (3 Oct 2011) unless otherwise specified by the Production CSDR Plan (reference Attachment 0007).

Any changes to an approved CWBS require Government approval. (Contract Work Breakdown Structure (CWBS) Index & Dictionary, CDRL A011)

Cost Data Summary Report

The contractor shall prepare and submit the Cost Data Summary Report (DD Form 1921) which reports direct and indirect actual cost data on both a recurring and non-recurring basis by CWBS level as specified in the Production CSDR plan (reference Attachment 0007). (Cost Data Summary Report (CDSR) (DD Form 1921), CDRL A012)

Functional Cost-Hour Report

The contractor shall prepare and submit a Functional Cost-Hour Report (DD Form 1921-1) which reports information on resources including labor hours, overhead costs, material costs, and other direct and indirect cost data on both a recurring and non-recurring basis by CWBS level as specified in the approved Production CSDR plan (reference Attachment 0007). (Functional Cost-Hour Report (DD Form 1921-1), CDRL A013)

Progress Curve Report

The contractor shall prepare and submit the Progress Curve Report (DD Form 1921-2) which reports production cost and hours data specified in the approved Production CSDR plan (reference Attachment 0007). (Progress Curve Report (DD Form 1921-2), CDRL A017)

Software Resources Data Report (SRDR) Initial

The contractor shall prepare and submit the Software Resource Data Report (SRDR) which provides results of software development and upgrade efforts as specified in the approved Production CSDR plan (reference Attachment 0007). (Software Resources Data Report: Initial Developer Report and Data Dictionary, CDRL A014)

Software Resources Data Report (SRDR) Final

The contractor shall prepare and submit the Software Resource Data Report (SRDR) which provides results of software development and upgrade efforts as specified in the approved Production CSDR plan (reference Attachment 0007). (Software Resources Data Report: Final Developer Report and Data Dictionary, CDRL A015)

Other Cost Reports

Current and Prior Configuration Indentured Bill of Materials

The contractor shall prepare and maintain an indentured Bill of Materials (BOM) of any and all parts that are or were ever included in the MSV(L) configuration to include all ECPs, VECPs, and other configuration modifications. The indentured BOM shall be prepared in indenture level sequence and will report the current configuration (e.g. latest part numbers, includes ECOs and ECPs) and any prior BOM configurations (e.g.

obsolete part numbers, the configuration prior to ECPs cut-in) of the MSV(L). A mapping of the BOM to Level 3 WBS must be provided. (Bill of Material (BOM) mapped to Level

3 CWBS, CDRL A016).

Design Reviews

System Requirements Review (SRR)

The contractor shall host and conduct, at the contractor’s build site, a SRR in order for the contractor and Government to assess the system requirements as captured in the PD to ensure the requirement is understood and acceptable within the budget and schedule constraints. The SRR shall be conducted immediately following the program SOWM and shall take no longer than one 8 hour work day. The contractor shall establish the Functional Product Baseline in conjunction with the SRR. The contractor shall provide all visual aids and documentation necessary to communicate the proposed configuration and design IAW Design Review Documentation, CDRL A018.

SRR Entrance Criteria

The contractor shall ensure that the following entrance criteria have been met prior to conducting the SRR:

a. A preliminary agenda has been submitted IAW CDRL A001 prior to the SRR.

b. SRR technical products listed below for both hardware and software system elements have been made available to the cognizant SRR participants prior to the review:

1. Preliminary System specification (Purchase Description, Attachment 0001 and 0002)

2. System software functionality description

3. Draft SEP (Systems Engineering Plan)

4. Updated Human Systems Integration related documentation

5. System architecture (hardware, software,…