Att 1 - ECDIS RFI DRAFT SOW .pdf

Attachment 1

ECDIS RFI DRAFT Statement of Work

SECTION C

Section C - Descriptions and Specifications STATEMENT OF WORK (SOW)

1. Scope

This Statement of Work (SOW) defines the efforts required for the production, sustainment, assembly, testing, and delivery of Navy Electronic Chart and Display Information System (ECDIS) Software (SW) and Hardware (HW).

The Contractor shall maintain, modify, upgrade and test the Navy ECDIS SW in accordance with the source code, provided as Government Furnished Information (GFI). The Contractor shall manufacture, assemble, modify, and test of the NAVY ECDIS HW items in accordance with the Technical Data Package (TDP), provided as GFI.

2. Applicable Documents

The following documents, in their specified versions, are considered part of the SOW as outlined. However, if any discrepancies arise between these referenced documents and the SOW, the provisions in the SOW shall take precedence.

2.1. Military Specifications, Standards, and Handbooks

MIL-STD-1472H HUMAN ENGINEERING 15SEP20

MIL-HDBK-502A

DEPARTMENT OF DEFENSE HANDBOOK: PRODUCT SUPPORT

ANALYSIS

27DEC22

MIL-DTL-81927C

MANUALS, TECHNICAL: WORK PACKAGE STYLE, FORMAT,

AND COMMON TECHNICAL CONTENT REQUIREMENTS;

GENERAL SPECIFICATION

23JUL19

MIL-STD-38784C

DEPARTMENT OF DEFENSE STANDARD PRACTICE: GENERAL

STYLE AND FORMAT REQUIREMENTS FOR TECHNICAL

MANUALS

04SEP24

MIL-STD-3048C

DEPARTMENT OF DEFENSE STANDARD PRACTICE AIR

FORCE BUSINESS RULES FOR THE IMPLEMENTATION OF

S1000D

15MAY2023

MIL-HDBK61B CONFIGURATION MANANGEMENT GUIDANCE 07APR20

MIL-STD-31000C TECHNICAL DATA PACKAGE 03FEB25

2.2. Department of Defense (DoD) and Other Government Documents

PEO IWS6 TDP ECDIS Technical Data Package (TDP)

PEO IWS6 CMP Configuration Management Plan 11MAR21

PEO IWS6 RMP PEO IWS 6.0 Risk Management Plan 20NOV14

PEO IWS6

DMSMS

PEO IWS 6 Government Diminishing Manufacturing Sources and

Material Shortages (DMSMS) Plan

30JUN23

PEO IWS6 IUID Item Unique Identification (IUID) Implementation Plan 11FEB19

PEO IWS6 SCG

Security Classification Guide (SCG) ID# 03-198, Shipboard Navigation

Systems, PEO IWS 6.0 Version 1

15DEC23

PEO IWS6 SPA Security Production Assurance Plan (SPA) 1NOV10

PEO IWS6 Navy

ECDIS SRD

Software Requirements Document (SRD) for the U.S. Navy Electronic

Chart Display and Information System (NAVY ECDIS), Rev 1.0 (with

Change 1)

13JAN16

PEO IWS6 Navy

ECDIS RTM

Requirements Traceability Matrix for the U.S. Navy Electronic Chart

Display and Information System (NAVY ECDIS), Rev 1.0 (with Change

1)

13JAN16

NAVSEAINST

9410.2A

Naval Warfare Systems Certification Policy 24AUG12

OPNAVINST

9420.2A

Navy Electronic Chart Display and Information System Policy and

Standards

31OCT14

PEO IWS /

NAVSEA 05H

Technical Review Manual, Version 2.0, 18DEC09

DoD Open Systems Architecture, Contract Guidebook for Program

Managers, v.1.1

Jun 2013

No. SNIPP-160030-

Electronic System Technical Manual for Navy Electronic Chart Display and Information System, Technical Manual Contract Requirement

(TMCR)

18DEC15

DoDI 5200.39 Critical Program Information (CPI) Identification and Protection Within

Research, Development, Test and Evaluation (RDT&E), 1OCT20

DoDI 8500.01 Cybersecurity 7OCT19

DoDI-8510.01 Risk Management Framework for DoD Systems 19JUL22

DoDI 5200.01 DoD Information Security Program: Protection of Sensitive

Compartmentalized Information (SCI)

01OCT20

DoDI 5200.44 Protection of Mission Critical Functions to Achieve Trusted Systems and

Networks (TSN)

16FEB24

NAVSEAINST

9093.5

INTEGRATED COMBAT SYSTEMS CERTIFICATION AND

ASSESSMENT PROGRAM FOR ALL SUBMARINES

8 MAY 2020

NAVSEAINST

9090-310G

NAVSEA Technical Specification 12-FEB-15

NIST SP 800-160

VOL 1 REV 1

National Institute of Standards and Technology (NIST) Engineering

Trustworthy Secure Systems

16NOV22

NIST SP 800-53

Rev 5

Security and Privacy Controls for Federal Information

Systems and Organizations

10DEC20

2.3. Non-Government Documents

SAE AS5553C

SAE International Standards: Counterfeit Electrical, Electronic, and

Electromechanical (EEE) Parts; 26MAR19

Avoidance, Detection, Mitigation, and Disposition

EIA649C Configuration Management Standard 07FEB19

ANSI/ISO/ASQ

Q9001

Quality Management Systems – Requirements 21OCT15

ASTM F1166-07 Standard Practice for Human Engineering Design for Marine Systems, Equipment, and Facilities

16AUG17

IEEE 1044-2009 Standard Classification for Software Anomalies 07JAN10

IEEE/EIA Std.

15289-2017

ISO/IEC/IEEE International Standard Systems and software engineering -- Content of life-cycle information items (documentation)

05JUN17

IEEE/EIA 12207-

Systems and software engineering -- Software life cycle processes 28SEP17

Security Technical Implementation Guides (STIGs)

Open Web Application Security Project (OWASP), Code Review Guide JUN17

The Contractor shall utilize the latest version available when performing tasks within this SOW.

2.4. Use of Standards

The Contractor shall use the following standards in descending order of importance:

a. Standards as specified in 3.1, 3.2 and 3.3.

b. Commercial standards developed by international or national industry standards bodies that have been widely adopted by industry. Examples of widely adopted standards include SQL for databases (e.g., SQL for databases ANSI ISO/IEC 9075-1, ISO/IEC 9075-2, ISO/IEC 9075-3, ISO/IEC 9075-4, ISO/IEC 9075-

5), HTML for presentation layer (e.g., XML 1.0 www.webstandards.org), XML for data transfer, Web services for remote system calls.

c. Standards adopted by industry consensus-based standard bodies and widely adopted in the market place.

d. De facto standards (those widely adopted and supported in the market place).

2.5. Government Furnished Information

Items noted as GFI (attachment J-3) will be provided as part of an electronic database.

3. Requirements

3.1. General

The Contractor shall perform the work required by this contract in accordance with the SOW requirements, TDP provided as GFI, the Navy ECDIS SW source code provided as GFI, and the Contract Data Requirements Data List

(CDRL), DD Form 1423-1, provided as Exhibit A. The Contractor shall develop, maintain, and submit a Data

Accession List. The Contractor shall procure all materials and labor to accomplish the efforts required by the contract and this SOW.

3.2. Detailed Tasks: Program Management and Control (Applicable to All CLINS)

3.2.1 Program Management Office

The Contractor shall establish a Program Management Office that is responsible for the management and control of all program elements, specified in this contract, in order to support the successful on-time delivery of the contract requirements.

3.2.2 Program Management Plan

The Contractor shall perform program management functions to ensure all the requirements in the SOW are executed and shall develop, maintain, and submit a Program Management Plan.

3.2.3 Schedule Management

The Contractor shall develop, update, and submit an Integrated Master Schedule (IMS).

3.2.4 Subcontractor Management

The Contractor shall develop, maintain, and submit a Technical Report- Study/Services, Subcontractor List, listing all subcontractors.

3.2.5 Risk Management

The Contractor shall develop, implement, and maintain a Contractor’s Risk Management Plan.

3.2.6 Meetings

The Contractor shall coordinate, schedule, prepare, conduct, facilitate and participate in reviews, meetings and conferences specified.

3.2.6.1 Post Award Kickoff Meeting

The Contractor shall schedule a Post Award Kickoff Meeting within twenty-one (21) calendar days after contract award and hold the Post Award Kickoff Meeting within forty-five (45) calendar days after contract award, at

Contractor facility.

3.2.6.2 Navy ECDIS Quarterly Program Review

The Contractor shall participate in the Navy ECDIS Quarterly Program Reviews.

3.2.6.3 Monthly Interchange Meetings

Monthly interchange meetings shall be conducted.

3.2.6.4 Technical Meetings/Data Exchanges

The Contractor shall plan for an average of three two-hour meetings per week.

3.2.7 Quality Assurance (QA)

The Contractor shall develop, maintain, and submit a Quality Assurance Program Plan (QAPP).

3.2.8 System Safety

The Contractor shall prepare and provide a System Safety Program Plan.

3.2.9 Program Security

The Contractor shall handle, and store classified material up to the SECRET Level as referenced in Attachment J-1, DD Form 254. The Contractor shall maintain a facility clearance of SECRET or higher and be Communications

Security (COMSEC) certifiable or certified per the DD Form 254.

The Contractor, and any of their subcontractors or suppliers, shall also comply with all requirements set forth in the

DD-254.

3.2.9.1 International Traffic in Arms Regulations (ITAR and Export Administration Regulations

(EAR)

The Contractor shall be solely responsible for obtaining any State Department approvals, licenses, Technical

Assistance Agreements (TAA), etc., required by the ITAR and EAR, and shall obtain specific written authorization from the PCO, COR, and IWS 6 Security Manager before seeking such approvals or licenses.

3.2.9.2 Contractor Information Systems (IS) Networks

Contractor Information Systems (IS) networks involved in the development or operation of systems shall be configured and operated in accordance with controlling laws, regulations, and DOD policy

3.3 Detailed Tasks: Configuration, Obsolescence, and Technical Data Management (APPLICABLE TO

CLINs 0004 and 0005, and if exercised, CLINs 1004, 1005, 2004. 2005. 3004, 3005, 4004, and 4005)

The Contractor shall maintain and execute configuration management, obsolescence management, and technical data synchronicity between Government Personnel, and Program Office Representatives.

3.4 Configuration Management (CM) (IF EXERCISED, APPLICABLE TO CLINs 0004, 0005, 1004, 1005, 2004. 2005. 3004, 3005, 4004 and 4005)

3.4.1 Configuration Management Plan (CMP)

The Contractor shall develop and implement a Supplier’s Configuration Management Plan in accordance with that incorporates the principles of the IWS 6.0 CMP, provided as GFI.

3.4.2 Configuration Status Accounting (CSA)

The Contractor shall maintain a Configuration Status Accounting Database to record and track the status of hardware and software associated with engineering changes and their implementation activities.

3.5 Obsolescence Management (IF EXERCISED, APPLICABLE TO CLINs 0004, 0005, 1004, 1005, 2004.

2005. 3004, 3005, 4004, AND 4005)

The Contractor shall monitor, identify, plan for, and recommend solutions for Diminishing Manufacturing Sources and Material Shortages (DMSMS) and obsolescence issues in accordance with the PEO IWS 6.0 DMSMS

Management Plan and PEO IWS 6.0 Risk Management Plan.

3.5.1 Obsolescence/DMSMS Identification

The Contractor shall implement and maintain a process to identify and immediately notify the Government of pending and emergent recall notices, plan for, obsolescence notices, or vendor implemented changes associated with the CETPS product baseline hardware, software, and firmware (all variants).

4. ECDIS Software

4.1. SW Engineering support (Items if option exercised APPLICABLE TO CLINS 0004, 1004, 2004. 3004, AND 4004)

The Contractor shall perform engineering efforts to support the sustainment of Navy ECDIS SW under this contract.

ES shall be performed in accordance with TIs provided by the COR and PCO. TI’s will specify the tasks to be performed, period of performance, and required deliverables.

4.2. Software Sustainment (IF EXERCISED, APPLICABLE CLINs 0004, 1004, 2004. 3004, AND 4004)

The Contractor shall perform all necessary tasking to incorporate Government directed changes into the existing system and the current system design provided to the Contractor as GFI and GFP as directed via TI.

4.3. Software Architecture and Modeling

The Contractor shall develop and deliver a system model inclusive of each of all Navy ECDIS Elements describing the functions performed by, and the logical and physical interfaces, using an approved software modeling language

(e.g., Unified Modeling Language).

4.4. Software Builds for Specific Navy Ships

The Contractor shall successfully integrate the new software capability into a ship-specific build and test it.

4.5. Software Requirements Specification (SRS)

The Contractor shall prepare and submit an SRS for each CSCI as directed via TI. The SRS shall be reviewed and updated, if required, with each Navy ECDIS SW Build.

4.6. Software Version Description (SVD)

The Contractor shall document software builds and component interfaces from CM through a SVD (CDRL A058).

4.7. Software Product Specification (SPS)

The Contractor shall prepare and submit an Software Product Specification (SPS). The SPS shall be reviewed and updated with each Navy ECDIS SW Build.

4.8. Software Design Description (SDD)

The Contractor shall perform all necessary tasking to incorporate Government directed changes into the applicable elements and the current system design provided to the Contractor as GFI and GFP.

4.9. Interface Control Document (ICD)

The Contractor shall develop, update and maintain an ICD for each external interface and shall specify design criteria and interface characteristics of the system and subsystems.

4.10. Software Transition Plan (STrP)

The Contractor shall prepare and submit a STrP. The STrP shall be reviewed and updated, if required by the

Government and directed via TI, with each Navy ECDIS SW Maintenance Build.

4.11. Interface Design Description (IDD)

The Contractor shall prepare and submit the IDD. The IDD shall be reviewed and updated, if required, with each

SW Maintenance Build.

4.12. Software Quality Assurance (QA)

The Contractor shall establish and maintain a quality management system that complies with E-246-H020

QUALITY MANAGEMENT SYSTEM REQUIREMENTS (NAVSEA)(OCT 2018) and shall adhere to the quality program controls outlined in E-246-H023 QUALITY REQUIREMENT FOR SOFTWARE DEVELOPMENT OR

PRODUCTION (NAVSEA)(JAN 2019).

4.13. Commercial Off the Shelf (COTS) Software

The Contractor shall evaluate the current COTS software products used by the system and identify any necessary updates to those products as required by support schedule.

The Contractor shall provide to the Government all necessary COTS based software products, along with supporting documentation and all required licenses – System/Subsystem Specification (SSS).

4.14. Contractor's Master Test Plan (MTP)

The Contractor shall develop Test Plan - Master Test Plan (MTP).

4.15. Software Test Plan (STP)

The Contractor shall prepare and submit the Software Test Plan (STP). The STP shall be reviewed and updated with each Navy ECDIS SW Maintenance Build.

4.16. Test Readiness Review (TRR)

The Contractor shall successfully complete a Test Readiness Review (TRR) before the commencement of the associated Environmental Qualification Test.

4.17. Environmental Qualification Testing- Completion Tasks(APPLICABLE TO CLINS 0001 AND IF

EXERCISED, 0003, 1003, 2003, 3003, AND 4003)

The Contractor shall develop, execute, maintain Test Plans/Test Procedures, Environmental Qualification Test.

4.18. Software Test Description (STD)

The Contractor shall prepare and submit the Software Test Description (STD).

4.19. Software Test Report (STR)

The Contractor shall prepare and submit the Software Test Report (STR) (CDRL A052 ) for each of the SW

Maintenance Builds. The STR is a record of the results of all qualification tests performed.

4.20. Installation

The Contractor shall support the ISEA with the fielding of Ship Change Documents (SCDs) as directed via TI.

4.21. Human Systems Integration (HSI)

The Contractor shall apply HSI principles and design activities during the planning, design, integration production, and sustainment of the Navy ECDIS SW/HW.

4.22. Human Systems Integration Program Plan (HSIPP)

The Contractor shall develop an HSIPP that describes specific activities to be conducted to effectively address each of the seven HSI domains as they relate to the ECDIS system

The Contractor shall submit A, Human Systems Integration Program Plan and Human Systems Integration Report.

4.23. HSI Integrated Product Team or Working Group

The Contractor shall identify the HSI representatives for a Government-led quarterly HSI IPT, which shall meet to review HSI issues across Navy ECDIS SW/HW.

4.24. Human Factors Engineering (HFE)

The Contractor shall develop effective human-system interfaces and preclude system characteristics that require extensive cognitive, physical, or sensory skills; complex manpower or training intensive tasks; or result in frequent or critical errors on Navy ECDIS SW/HW.

4.25. Human Engineering Design Approach– Operator (CDRL A064)

The Contractor shall describe the equipment which interfaces with operators, providing a source of data to evaluate the extent to which equipment having an interface with operators meets human performance requirements and HFE criteria for Navy ECDIS SW/HW.

4.26. Human Engineering Design Approach – Maintainer (CDRL A065)

The Contractor shall describe the equipment which interfaces with maintainers, providing a source of data to evaluate the extent to which equipment having an interface with maintainers meets human performance requirements and HFE criteria on Navy ECDIS SW/HW.

4.27. Human Computer and Graphical User Interface Development

The Contractor shall improve upon existing design process to integrate the sailor with the new Navy ECDIS capability and hardware, conducting usability analysis, standardizing Human System Interfaces designs and conducting design-to-human effectiveness in accordance with MIL-STD-1472G and utilizing Common Presentation

Layer (CPL) Guide as directed via TI.

4.28. Open System Architecture (OSA)

The Contractor shall produce software with an OSA using modular design, standards-based interfaces, and widely supported consensus-based standards in accordance with the requirements documents wherever possible. The

Contractor shall define, document, and follow an Open Systems Management Plan.

4.29. Navy ECDIS Ship Integration

The Contractor shall support Systems Integration for elements as defined in the scope of the SOW. Activities for this role include the following engineering areas, the associated processes, and products. The Contractor shall support integration of Navy ECDIS SW/HW without degrading service, performance or function of existing or previously installed systems.

4.30. Navy ECDIS Baseline Management

The Contractor shall implement element-level baseline management processes to ensure element configurations are defined and controlled throughout development, testing, fielding, and sustainment.

4.31. Navy ECDIS Participating Acquisition Managers (PARM) Coordination

The Contractor shall support coordination with associated the Assistant Program Managers (APMs) in support of delivering certified Navigation elements to surface and submarine Shipbuilding Programs.

4.32. Navy ECDIS In- Service Fleet Support

The Contractor shall provide:

a. The Contractor shall provide technical support for all ship classes.

4.33. Navy ECDIS Configuration Management (CM) (IF EXERCISED APPLICABLE TO CLINS 0004, 1004, 2004. 3004, 4004)

The Configuration Management (CM) process comprises the five tenets of Configuration Planning, Configuration

Identification, Configuration Control, Configuration Status Accounting, and Configuration Audit. Subparagraphs to section 4.33 shall be completed as directed via TI.

4.33.1. Navy ECDIS Configuration Planning

The Contractor shall develop, maintain, submit, and implement Configuration Management. The Contractor shall participate in Program Reviews, Configuration Control Boards (CCBs), configuration audits, process improvement teams, working groups, and certification events.

4.33.2 Navy ECDIS Configuration Item (CI) Identification

The Contractor shall maintain a record of the CI, starting with the initial established configuration Product Baseline

(PBL) and continuing with configurations resulting from the incorporation of approved Engineering Changes (ECs).

4.33.3. Navy ECDIS Configuration Control Board

The Contractor shall establish a Configuration Control Boards (CCBs) to control SW/HW baselines.

4.33.4. Navy ECDIS Configuration Control Documentation

The Contractor shall generate and/or support development of Change Proposals (ECPs) in accordance with (CDRL

A018), and/or Requests for Variance (RFVs) in accordance.

4.33.5. Navy ECDIS Configuration Status Accounting (CSA)

The Contractor shall establish a CSA database to record and track the status of each hardware and software engineering change and their implementation activities.

4.33.6. Navy ECDIS Configuration Verification and Audit

The Contractor shall conduct both a Functional Configuration Audit (FCA) and a Physical Configuration Audit

(PCA).

4.34. Navy ECDIS System Safety

The Contractor shall develop, maintain, and submit a System Safety Program Plan (SSPP)(CDRL A012).

The Contractor shall provide Systems Safety Engineering support to Navigation related working groups, integrated product teams, control boards, land-based test, underway testing, and PEO IWS Navigation related system engineering and Technical Governance activities.

4.35. Navy ECDIS ISEA Support

The contractor shall provide assistance in generating engineering, training, technical publication development, program management, technical support, and other support relating to surface vessel navigation systems and steering/propulsion control systems as directed via TI.

4.36. Navy ECDIS System Engineering Technical Review (SETR) Event Requirements

The Contractor shall conduct SETR events in accordance with the NAVSEA Technical Review Manual (TRM) and as directed via TI.

4.37. Software Deficiency/Problem Corrections

The Contractor shall utilize Government data repositories website database to document and manage all identified software discrepancies.

4.38. Software Delivery

The Contractor shall provide the executables, source code, Application Program Interfaces (APIs), and development tools for any Contractor developed software scripts and software applications not developed exclusively or partially at private expense in accordance with DFARS 252-227-7017.

4.39. Software User’s Manual

The Contractor shall develop and maintain a manual that includes installation procedures for complete installation, configuration and set-up of Navy ECDIS SW.

4.40. Operator’s Manual

The Contractor shall develop and maintain a Navy ECDIS SW Operations Manual.

5. ECDIS HARDWARE

5.1 Detailed Tasks: First Article Units (CLIN 0001) – Completion Tasking

5.1.1. First Article Unit (FAU) Production

The Contractor shall manufacture FAUs for the AN/SYN-1 system as referenced in the provided TDP.

5.1.2. HW First Article Testing. (Applicable only to CLIN 0001)

The Contractor shall conduct first article testing on the first article unit delivered for Navy ECDIS HW.

5.1.2. Functional Configuration Audits (FCA)

The Contractor shall support the Government in supporting a Functional Configuration Audit (FCA).

5.1.3. Physical Configuration Audit (PCA)

The Contractor shall support a Government witnessed PCA.

5.1.4. Exit Criteria for Acceptance of FAU

The Contractor shall have completed FAU CLINs 0001.

5.2. Production Readiness Review (PRR) (CLIN 0002)

The Contractor shall conduct a PRR to determine whether the production facility is ready for production.

5.2 Detailed Tasks: Manufacture, Assembly, and Testing (If options are exercised, CLINs 0003,1003, 2003, 3003, 4003)

5.2.1. Manufacture and Assembly

The Contractor shall manufacture and assemble the Navy ECDIS systems, back fit kits and Installation and

Checkout (INCO) kits in accordance with the SOW, the TDP (Attachment J-X), unit specifications, and all documentation provided as GFI.

5.2.2. Item Unique Identification (IUID)

The Contractor shall apply DoD IUID marking to the Unit level assemblies, and their associated LRU/SRA procured under this contract as required by DFAR 252.211-7003, ITEM UNIQUE IDENTIFICATION AND VALUATION, and Unit/LRU lists provided as GFI.

5.2.3. Packaging, Handling, Storage and Transportation

The Contractor shall develop and update, as directed via TI, a PHS&T program to reflect the manufacture and repair of Navy ECDIS HW.

5.2.4. As-Built Configuration List (ABCL)

The Contractor shall develop a, As-Built Configuration List for each delivered item.

5.2.5. Testing

The Contractor shall develop, maintain, and submit a Test Plan, in accordance with the Acceptance Test Procedures provided as GFI.

5.2.6. Security Production Assurance Plan (SPA)

The Contractor shall develop, maintain, and submit a Test Plan, Security Production Assurance Plan (SPA).

5.2.7. Manufacturing Acceptance Testing (MAT)

The Contractor shall conduct component level manufacturing testing on all COTS items, manufactured items, modified items, and repaired items as directed via TI.

5.2.8. Final Acceptance Testing (FAT)

The Contractor shall perform FAT in accordance with the Government approved Test Plan, Acceptance Test Plan.

5.2.9. Counterfeit Parts and Materials

The Contractor shall develop, maintain, and submit a Counterfeit Prevention Plan.

5.2.10. Detailed Tasks: Integrated Logistics Support (ILS)

The Contractor shall provide integrated logistics support and reporting of Navy ECDIS systems and system components as directed via TI.

5.2.11. Integrated Logistics Support Working Group (ILSWG) (Items if option exercised CLINS 0005, 1005, 2005, 3005, 4005)

The Contractor shall provide a representative to participate in the Navy ECDIS Integrated Logistics Support

Working Group (ILSWG).

5.3. Travel and Other Direct Costs (ODC), CLIN(s) 0006, 1006, 2006, 3006, 4006 (if exercised) in support of

Engineering support CLIN(s) 0004, 0005, 1004, 1005, 2004. 2005. 3004, 3005, 4004, 4005 (if exercised)

The Contractor shall provide Travel and Other Direct Costs (ODCs) in support of Engineering Services Support

CLIN(s) 0006, 1006, 2006, 3006, 4006 (if options are exercised).

5.4. HW Engineering Support (Items if option exercised CLINS 0005, 1005, 2005, 3005, 4005)

The Contractor shall perform engineering efforts in support of the production and sustainment of Navy ECDIS HW under this contract.

5.5. Non-Recurring Engineering (NRE) (Items if option exercised CLINS 0005, 1005, 2005, 3005, 4005)

The Contractor shall perform non-recurring engineering efforts to support the incorporation of the next generation

Navy ECDIS HW configuration referred to as AN/SYN-1Vx into the production TDP.

5.6. Technical Data Package (TDP)

The Contractor shall develop, maintain, and update the TDP after approval of all ECP’s. The Contractor shall maintain the TDP without any proprietary markings and with Government Purpose Rights (GPR) as defined by the clause under Section I of this contract entitled DFARS 252.227-7013 and DFARS 252.227-7014.

Acronym List

AIS Automated Information Systems

CDR Critical Design Review

CDRL Contract Data Requirements Lists

CLIN Contract Line Item Number

CM Configuration Management

CMMI Capability Maturity Model Integration

COTF Commander, Operational Test and Evaluation Force

COTS Commercial Off-The-Shelf

CPI Critical Program Information

CSCI Computer Software Configuration Items

CSP Compute Software Product

CUI Controlled Unclassified Information

DoD Department of Defense

DSS Defense Security Services

ECDIS Electronic Chart Display and Information System

FOUO For Official Use Only

FQT Formal Qualification Test

GFE Government Furnished Equipment

GFI Government Furnished Information

GPR Government Purpose Rights

HWCI Hardware Configuration Items

HMI Human Machine Interface

HSI Human Systems Integration

HSIPP Human Systems Integration Program Plan

IDD Interface Design Description

IDE Integrated Data Environment

IMS Integrated Master Schedule

IRS Interface Requirements Specification

ISEA In-Service Engineering Agent

ITAR International Traffic in Arms Regulations

NISPOM National Industrial Security Program Operation Manual

NIST National Institute of Standards and Technology

NSWC PD Naval Surface Warfare Center, Philadelphia Division

OSA Open System Architecture

OWASP Open Web Application Security Project

PDR Preliminary Design Review

QA Quality Assurance

QAPP Quality Assurance Program Plan

RFV Request For Variance

SCCB Software Configuration Control Board

SCM Software Configuration Management

SDD Software Design Description

SDP Software Development Plan

SPIR Software Problem Improvement Reports

SPS Software Product Specification

SRR System Requirements Review

SRS Software Requirements Specification

SSR Software Specification Review

STD Software Test Description

STIG Security Technical Implementation Guide

STP Software Test Plan

STrP Software Transition Plan

STR Software Test Report

SVD Software Version Description

SOW Statement of Work

SW Software

TAA Technical Assistance Agreements

TI Technical Instruction

TRR Test Readiness Review