N0024418R0017_FY18_PWS_ISS60_v4.3.docx

UNCLASSIFIED//FOUO

PERFORMANCE WORK STATEMENT (PWS)

FOR ISS-60 VERSION 3.X DELIVERY & FOLLOW-ON WITH VERSION 3.14 SOFTWARE UPGRADE

General Information

This Performance Work Statement (PWS) sets forth contractor requirements for engineering services support in the form of software integration and updates to the Integrated Survey System (ISS-60) software. This effort includes tasking necessary to upgrade the software in addition to follow-on integration and analysis. During the Period of Performance (PoP) integration of Version 3.X and the upgrade to Version 3.14 will be executed concurrently.

1.0 BACKGROUND

The ISS-60 is currently in-service aboard the T-AGS 60 class ships. These oceanographic survey vessels are capable of effectively performing operations that satisfy a broad spectrum of oceanographic requirements. The T-AGS 60 ships are Survey Ships that are designed and constructed to provide multi-purpose oceanographic capabilities in coastal and deep ocean areas including; physical, chemical, and biological oceanography; multi-discipline environmental investigations; ocean engineering and marine acoustics; marine geology and geophysics; and bathymetric, gravimetric, and magnetometric surveying.

The ISS-60 provides an integrated data collection, storage and processing capability for these platforms to perform a variety of missions. The ISS-60 acquires, stores, displays, and processes data collected by various mission systems using a fiber-optic network configuration. These configurations can be installed on a variety of vessels and reside on a single computer. Additionally, the ISS-60 configuration is maintained at the same version level across all platforms to provide end users with a familiar setting as they move ship-to-ship.

Additionally, the U.S. Navy recently stood up the Naval Information Dominance Command (NAVIDFOR). The U.S. Navy Information Dominance Roadmap 2013-2028 stresses the requirement for Position, Navigation and Timing (PNT) services in support of Command and Control (C2) and Battle Space Awareness. Consequently, ISS-60 is a critical component in the Naval Oceanographic Office’s (NAVOCEANO) ability to collect and integrate oceanographic information in support of surface and subsurface navigation as well as provide environmental characterization of the Battle Space. Furthermore, the data will be integral to the U.S. Navy in supporting the Information Dominance Roadmap in the future.

2.0 APPLICABLE DOCUMENTS

This section lists documents applicable to the accomplishment of this PWS. In the event of conflict between the documents referenced herein and the contents of this PWS, the text of the PWS takes precedence. The contractor shall be responsible for monitoring and conforming to all current Government standards, processes and procedures.

ISS-60 Procurement Applicable Documents

a. DoDI 8500.01: DISA: Application and Security Development Document, Security and Technical Implementation Guide Version 4 Release 3 dated 28 April 2017

b. DoDI 8500.2: IA Control: ECSC-1 Subject: Security Configuration Compliance

c. DoD Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs dated 9 January 2017

d. DOD 5000.02: Operation of the Defense Acquisition System dated 10 August 2017

e. Application and Security Development Document, Security and Technical Implementation Guide Version 4 Release 3

f. DoN Mandated Message (254/06) Cyber Asset Reduction and Security (CARS)

g. IEEE Std. 12207 – 2008

3.0 PRE-PLANNED PRODUCT IMPROVEMENTS (P3I) REQUIREMENTS AND ENGINEERING SUPPORT SERVICES

All tasks contained in this section describe the efforts required for the upgrade, integration, and testing of the ISS-60 in support of Version 3.X and follow-on Version 3.14 builds.

3.1 Program Management

The contractor shall perform program management activities to ensure all work conducted under this Task Order (TO) is planned and executed in a manner that will achieve all management, technical, cost, and schedule objectives stated within.

The contactor shall submit a Monthly Status Report (MSR) in accordance with (IAW) CDRL A001. The report shall document immediate plans, program status (including action item status), progress, risk, all Government Furnished Property (GFP) items received and required, schedule of upcoming events (including stop and start dates, meetings and reviews, and testing milestones), and other information as required. All risks identified in the MSR shall follow the guidance identified in the DoD Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs dated 9 January 2017.

CDRL Deliverable:

· A001: MSR (DI-MGMT 80227)

3.1.1 Conferences, Meetings, and Reviews

The contractor shall conduct meetings and reviews, including the below referenced meetings, in support of all tasks executed under this contract. The Contractor shall develop presentation material and conference agendas submitting IAW CDRLs A002 and A003. Upon completion of formal meetings and reviews, the contractor shall document meeting minutes and coordinate key action items resulting from the meeting with the Government IAW CDRL A004.

CDRL Deliverables:

A002: Presentation Material (DI-ADMN-81373) A003: Conference Agenda (DI-ADMN-81249B) A004: Report, Record of Meeting/Minutes (DI-ADMN-81505)

3.1.1.1 Program Status Reviews (PSRs)

The contractor shall conduct Program Status Reviews (PSRs). These reviews shall occur at the contractor’s facility unless specifically requested by the Government to occur elsewhere. The PSR content shall cover all aspects of this TO addressing delivery schedule and TO performance (e.g. to include topics such as progress against major milestones, risk management, configuration management, software engineering, logistics, and obsolescence). Prior to each PSR, the contractor shall provide presentation material and an agenda IAW CDRL A002 and A003. PSRs shall be conducted at the discretion of the Government and may consist of up to four (4) per year. Upon completion of each PSR, the contractor shall provide meeting minutes IAW CDRL A004.

CDRL Deliverables:

A002: Presentation Material (DI-ADMN-81373) A003: Conference Agenda (DI-ADMN-81249B) A004: Report, Record of Meeting/Minutes (DI-ADMN-81505)

3.1.1.2. Technical Meetings

The contractor shall conduct technical meetings, as required by the Government, and shall be defined at the Work Package Level. As an output to the meeting, the contractor shall provide meeting minutes, IAW CDRL A004. In addition to the standard content, the contractor shall include the following information:

CDRL Deliverable:

A004: Report, Record of Meeting/Minutes (DI-ADMN-81505)

3.1.2 Configuration Management (CM)

The contractor’s solution shall comply with the Department of Navy (DoN) Application and Database Management System (DADMS) to validate the approved version of Commercial-off-the-Shelf (COTS) products needed to build the ISS-60 software.

3.1.3 Quality Control (QC)

The contractor shall provide quality objective evidence (e.g. Capability Maturity Model Integrated (CMMI) information and documentation). All documentation shall be IAW the contractor’s current baselined CMMI requirements.

3.2 Systems Engineering

The contractor’s solution shall utilize Systems Engineering principles in design, development, integration, testing and delivery on the survey platform. Additionally, the contractor shall follow the guidance of DOD 5000.02, as related to System Engineering.

3.2.1 Software Engineering Services

The contractor shall perform software engineering services and verification functions that demonstrate all products delivered meet the requirements defined by the Government. The contractor shall meet the following performance standards defined below.

1) All software delivered by the contractor shall operate with Microsoft Windows 10 and Red Hat Linux Enterprise 7 or latest Government approved versions. All subroutines, libraries, files and scripts written shall conform to the Application and Security Development Document, Security and Technical Implementation Guide Version 4 Release 3. No deviations from these standards will be accepted unless approval is granted by the NAVOCEANO Software Point of Contact (POC) in writing.

2) The contractor shall deliver updated source code to the Government with each software version release, IAW CDRL A005. Each software release shall be properly version controlled and shall be coordinated with the Government to identify any system accreditation impacts prior to release, and determine the proper course of action.

3) The contractor shall provide proof-of-concept products that either demonstrate expected interfaces and functionality, such as story boards, or produce prototype demonstrations that show the operations of particular functions.

4) The contractor’s solution shall remain backward compatible with all previous software versions and sensors that remain in service onboard the T-AGS ships.

5) The contractor shall use current industry design and implementation tools to facilitate future enhancements. The system shall be scalable to process and store additional data sets and increasing volumes of data and use a modular, open-systems approach, when feasible. The contractor shall follow guidelines set forth by the DoN Mandated Message (254/06) Cyber Asset Reduction and Security (CARS) initiative.

6) The contractor’s solution shall be produced with preset configurations and workflow automation to remove repetitive and redundant steps to the maximum extent possible while retaining human review and quality control of data.

7) The contractor’s solution shall support a remote capability to monitor system status, troubleshoot, configure, correct defects, and install Cybersecurity patches to the maximum extent possible.

8) The contractor’s solution shall have innovative displays to plan and manage survey operations while operating multiple survey platforms and multiple concurrent operating shipboard over-the-side systems.

9) The contractor shall perform software modifications to improve the ISS-60. These improvements may be for any part of the system, to include but not limited to, graphical user interface, functionality, efficiency, workflow, or sensor interfaces.

Additionally, any updates to the baseline of the ISS-60 software shall be IAW the framework defined in IEEE Std. 12207 – 2008, and include updates to the following documents with each version release:

· All existing documentation in the software baseline to include Engineering Test Cycle documentation support for the ISS-60 software archives

· ISS-60 Source Code IAW CDRL A005

· Software Requirements Specification (SRS) IAW CDRL A006

· Software Design Specification (SDS) IAW CDRL A007

· Software Maintenance Manual (SMM) IAW CDRL A008

· Interface Control Document (ICD) IAW CDRL A009

· System Test Manual (STM) CDRL IAW CDRL A010

· User Manual (UM) IAW CDRL A011

· Version Description Document (VDD) IAW CDRL A012

· Software Development Plan (SDP) IAW CDRL A013

Any content errors in the above referenced documentation shall be captured in Documentation Discrepancy Cards (DDCs). For more information on DDCs as they relate to the performance standard of this contract, please reference Attachment 4, Quality Assurance Surveillance Plan (QASP).

CDRL Deliverables:

A005: Revisions to Existing Government Documents: ISS-60 Source Code (DI-IPSC-81488) A006: Revisions to Existing Government Documents: SRS (DI-IPSC-81427) A007: Revisions to Existing Government Documents: SDS (DI-IPSC-81435) A008: Revisions to Existing Government Documents: SMM A009: Revisions to Existing Government Documents: ICD (DI-SESS-81248B) A010: Revisions to Existing Government Documents: STM A011: Revisions to Existing Government Documents: UM (DI-IPSC-81443A) A012: Revisions to Existing Government Documents: VDD (DI-IPSC-81442A) A013: Revisions to Existing Government Documents: SDP (DI-IPSC-81427)

3.2.2 Capability Maturity Model Integration (CMMI)

The contractor shall possess, at a minimum, a CMMI Level 3 certification. The contractor, with concurrence from the Government, shall assess each task and determine the level of difficulty based on the established process. Any deviations from the approved assessments directed by the Government during the implementation phase will be defined as a new task with a new Work Package.

3.2.3 Work Package Agreements

As directed via Work Package Agreements, the contractor shall perform software engineering services and verification functions that demonstrate all products delivered meet the requirements defined by the Government. A Work Package Agreement will define the scope of work for each engineering activity. For more information on Work Package Agreements, see Attachment 1.

3.3 Installation and System Testing

The contractor shall support the following test events for each release of the system.

3.3.1 Test Environment

The contractor shall receive, install, and test a Government Furnished Equipment (GFE) ISS-60 testbed which replicates the functionality of the shipboard ISS-60 configuration. The testbed shall provide support for software updates as well as testing capabilities to support each Factory Acceptance Test (FAT).

The contractor shall ensure the operational status of the ISS-60 testbed through the tasking PoP and provide the facility space. The contractor shall receive and install upgrades for hardware, software, firmware, network capability and associated components in the testbed (these items may include Government Furnished Material (GFM), contractor purchased and provided items, or a combination thereof). The contractor shall report these changes monthly IAW CDRL A014.

The contractor shall troubleshoot and conduct tests of the integrated testbed components to verify and validate that the testbed is operational in accordance with Government’s specified limits and parameters.

The contractor shall, at the Government’s request, de-install the testbed and ship all components to the Government at the end of this contract.

CDRL Deliverable:

A014: Status of Government Furnished Equipment Report (DI-MGMT-80269)

3.3.2 Factory Acceptance Test (FAT)

The contractor shall conduct a FAT at the contractor’s facility utilizing the Testing Environment described in Section 3.3.1. At the conclusion of each FAT, the contractor shall provide a Software Test Report (STR) IAW CDRL A015.

CDRL Deliverable:

A015: STR (DI-IPSC-81440)

3.3.3 Pre-System Acceptance Test (Pre-SAT)

After successful completion of the FAT, the contractor shall support the Pre-System Acceptance Test (Pre-SAT) conducted by the Government on an operational vessel at a location selected by the Government. The Government will host up to two (2) Pre-SATs during the PoP of this TO.

The contractor shall support the Pre-SAT in accordance with the Government’s schedule. The location(s) of the vessels will be made available approximately 30 days prior to the start of the test. The contractor shall provide on-site support at the discretion of the Government. If travel is required in support of a Pre-SAT, it shall be IAW Section 4.0 of this PWS.

3.3.4 System Acceptance Test (SAT)

The contractor shall prepare for and support the SAT conducted by the Government on an operational vessel at sea. The Government will host up to two (2) SATs during the POP of this TO.

The contractor shall be prepared to support the SAT in accordance with the Government’s schedule. The location(s) of the vessels will be made available approximately 30 days prior to the start of the test. If travel is required in support of a SAT, it shall be IAW Section 4.0 of this PWS.

Each test event shall result in Trial Cards (TC) generated and prioritized by the Government.

For each minor release of the software, the contractor shall support minor test events at the discretion of the Government. Each test event shall result in TCs generated and prioritized by the Government. The SAT shall be considered complete when it meets the requirements of the approved task during the test phase and is free of Level 1 and Level 2 Trial Cards (TCs). For more detail on TCs, please see Section 3.3.5 of this PWS and Attachment 3.

At conclusion of each SAT, the contractor shall provide a STR IAW CDRL A015.

CDRL Deliverable:

A015: STR (DI-IPSC-81440)

3.3.5 Trial Cards (TCs)

The contractor shall correct deferred deficiencies and TC corrections identified in the previous FAT, Pre-SAT, SAT, and Post-SAT events which affect the proper or preferred operation of the ISS-60. All high level specified software deficiencies shall be delivered by the next testing phase as either a new version or an alternate means of delivery, at the Government’s discretion. The Government will prioritize the TCs and provide the list to the contractor. The task shall be considered complete when it meets the requirements of the approved task during a testing phase and is free of Level 1 and Level 2 TCs; all remaining TCs will be “bundled” in the Deficiencies remediation task, prioritized, and worked within program funding constraints. Any deviations from the approved assessments directed by the Government will be defined as a new task and executed through a bi-lateral modification.

The contractor shall update the software with the latest Cybersecurity patches prior to software testing phase. The contractor shall verify the software functions properly in the testbed and onboard a T-AGS prior to the SAT and shall mitigate all deficiencies before the official acceptance of the software.

3.4 Training

The contractor shall provide shore-based training with every major software version release to plan and conduct survey operations as well as simulate the display, collection, processing, quality control, and dissemination of data to the maximum extent possible.

The contractor shall generate and deliver training materials IAW CDRL A016 and conduct training in-port and at-sea for the ISS-60, but may be delivered at any of the referenced places of performance. Training is usually provided after SAT on same software delivery platform. The contractor shall become familiar with the ISS-60 to provide services to conduct detailed training courses on all aspects of the ISS-60 system, modules and interfaces.

CDRL Deliverable:

· A016: Technical/Analysis Report, General: Training Material

4.0 TRAVEL

The contractor shall travel in support of deliveries, test events, meetings and other efforts related to the performance of ISS-60 support and operational oceanographic survey systems as required. The contractor shall provide a trip report IAW CDRL A017 for all travel associated with this task and deliver to the Government within three (3) business days after completion of the trip.

All contractor travel shall be coordinated with and approved by the primary or alternate COR prior to incurring travel expenses.

Note: If foreign travel is required, all outgoing Country/Theater clearance message requests shall be submitted to the SPAWAR Systems Center San Diego (SSC SD) foreign travel team for action. A Request for Foreign Travel form shall be submitted for each traveler, in advance of the travel to initiate the release of a clearance message at least 35 days in advance of departure.

Additionally, for work performed in Japan, a U.S.-Japan bilateral agreement governs the status of contractors and employees, criminal jurisdiction, and taxation. U.S. Forces Japan (USFJ) is a sub-unified command of Pacific Command (PACOM). The COR will coordinate all work effort with PACOM Staff Judge Advocate for logistical support and base privileges.

Additionally, the contractor shall follow and adhere to the current DoN Travel Policies.

CDRL Deliverable:

· A017: Trip/Travel Report (DI-MISC-81943)

5.0 PRIMARY PLACE(S) OF PERFORMANCE

Activities performed under this TO shall be performed at the contractor’s site or other locations deemed appropriate by the Government. The Government shall not incur any additional costs if the contractor changes the location for convenience. Any changes to the location must be mutually agreed upon by the Government and the contractor.

6.0 SECURITY REQUIREMENTS

As specified in this contract and the Contract Security Classification Specification form, DD-254, classified work shall be performed under this TO. The contractor shall have SECRET clearance prior to commencement of classified work.

7.0 GOVERNMENT FURNISHED PROPERTY (GFP)

7.1 Government Furnished Equipment (GFE)

GFE includes Property, Plant and Equipment (PP&E) (equipment, machine tools, test equipment, etc), Special Test Equipment (STE), and Special Tooling (ST). GFE to be provided to the contractor shall consist of equipment identified in the Scheduled Government Furnished Property (SGFP) form. All GFE will be provided within 30 days after TO award, see GFE/GFI inventory list Attachment 3. All material provided by the Government shall remain in designated Government spaces after completion of contract. The Government will provide the following property in an "as is" condition. After receipt of GFE, the contractor shall update and complete all information listed in the SGFP/RGFP and return any revisions to the COR and Ordering Officer within seven (7) days of receipt. The contractor shall also update the Wide Area Workflow (WAWF) GFP property module to receipt property transfer. The Ordering Officer will upload the SGFP/RGFP form(s) to Electronic Document Access (EDA).

7.2 Government Furnished Information (GFI)

The contractor shall use online sources to obtain copies of any necessary documentation needed for performance on this TO. For those documents not available online, the Government will provide the following GFI listed in the table below as well as identified software in Attachment 3- GFE/GFI Inventory List. The contractor shall inventory all GFI by tracking distribution and location and provide a GFI inventory to the Government as needed. The contractor shall use the GFI provided to only support this TO – use of GFI document(s) to support other projects beyond this TO is not allowed. Unless otherwise specified, all GFI will be provided by the Government by the estimated delivery date listed in the table below, and the contractor shall return all GFI to the Government at completion of the TO. Note: If a Contractor requires additional GFI other than what is listed, the contractor shall submit a request to the COR within 30 days after TO award.

8.0 TECHNICAL ASSISTANCE AGREEMENT (TAA)

Within six (6) months after TO award, the contractor shall obtain a Technical Assistance Agreement (TAA) with foreign businesses as part of the International Traffic in Arms Regulations (ITAR). Part 120 from ITAR defines the TAA as a means for the disclosure of regulated technical data. The foreign businesses include the following:

· Kongsberg Maritime

· University of New Brunswick/Ocean Mapping Group

· Applanix

· RESON

· Rolls Royce (Moving Vessel Profiler)

9.0 PERFORMANCE BASED CRITERIA

9.1 Performance Requirement

The contractor shall provide services and deliverables IAW this PWS and the attached TO CDRL items.

9.2 Performance Standard

The contractor’s performance shall meet all of the requirements of this PWS and comply with all applicable guidance, directives, and standards. The contractor shall deliver all TO data items IAW the authorities, content, format, media, marking, application, quantities, frequency and submission date, delivery method, addressee, and requirements specified in the CDRL DD Form 1423.

9.3 Acceptable Quality Level

The effectiveness of the contractor’s deliverables and services will be measured for 100% compliance with all PWS and CDRL requirements.

9.4 Method of Surveillance

The Government will monitor and assess the contractor’s performance against the Acceptable Quality Level in accordance with this TO’s Quality Assurance Surveillance Plan (QASP) (Attachment 4).

9.5 Incentive

Failure to meet acceptable quality levels may result in an unsatisfactory past performance report by the Government.

10.0 LIST OF ATTACHMENTS

Attachment 1 – Work Package Agreement Attachment 2 – TC Guide Attachment 3 – GFE and GFI Inventory List Attachment 4 – QASP

UNCLASSIFIED//FOUO