RFP Amendment N00024-23-R-5108-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

RFP N00024-23-R-5108-0002 is amended to: 1) extend the proposal due date by 21 days; 2) update Attachment L-02 - Questions Comments and Data Request Form; and 3) update Attachment L-04 - Previous Contract Effort Narratives.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 49

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 29-Aug-2023

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N0002423R5108

X 9B. DATED (SEE ITEM 11)

08-Aug-2023

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

29-Aug-2023

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD, DC 20376-2030

N00024 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002423R5108

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 08-Sep-2023 01:00 PM to 29-Sep-2023 01:00 PM.

The depository location See Section L has been added.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

C.1.0 SCOPE/BACKGROUND

This Statement-of-Work (SOW) describes the systems, supplies and services to be furnished, manufactured, performed or processed to meet the training requirements of the United States (US) Navy, Foreign Military and US

Coast Guard. The scope of this contract is to continue the US Navy’s migration from legacy Battleforce Electronic

Warfare Trainer (BEWT) systems to the new and developing BEWT II systems; continue development of enhanced capabilities of the Surface Electronic Warfare Team Trainer (SEWTT) software; continue the development of the

Combined Integrated Air and Missile Defense and Anti-Surface Warfare Trainer (CIAT) training system; develop future training capabilities, such as Mk53(Nulka), MH60R, Specific Emitter Identification (SEI), High Gain High

Sensitivity, Soft Kill Coordinator (SKC) and Electronic Attack (EA), Laser Detect and Engage (LDE), and Electro-

Magnetic Spectrum Visualization Tool (ESVT) etc.; incorporate an enhanced After Action review with electronic scoring; deliver BEWT II systems to the US Coast Guard and US Navy; deliver training systems to CIAT training locations worldwide; provide Engineering expertise to the US Navy as required to advance all forms and facets of combat system training, both Electronic Warfare and Non-Electronic Warfare; and provide updates, repair, technical and engineering support services as required to the US Navy.

C.2.0 APPLICABLE DOCUMENTS FOR INCORPORATION AND REFERENCE

The following documents are applicable to the tasks described herein and are for use by the Contractor as required in the fulfillment of the SOW.

* Contractor is advised that the latest effective date, as of the date of the solicitation, of the mandatory and guidance documents below are to be used.

DOCUMENTS MANDATORY GUIDANCE

C.2.1 Cyber Security

DoD Instruction 8500.01, Cybersecurity of 14 March 2014 X SECNAVINST 5239.3C, Department of the Navy Information

Assurance (IA) Policy, 02 May 2016 X

SECNAV M-5239.2 DON Cyberspace Information Technology (IT) and CSWF Management and Qualification Manual, 27 Jun 2016 X

SECNAV 5239.20A DON Cyberspace IT and CSWF Management and Qualification, 10 Feb 2016 X

NAVSEAINST 9400.02A NAVSEA PIT Control Systems

Cybersecurity Governance and Guidance, 20 Sep 16 X

Department of the Navy Chief Information Officer Memorandum

02-10, Information Assurance Policy Update for Platform

Information Technology 26 April 2010, with Enclosure (1), PIT

X

Definitions for DON, and Enclosure (2), DON Platform IT IA

Guidance DoD Directive 8140.05, Cyberspace Workforce Management of 11

August 2015 X

DoD Manual 8570.1-M, Information Assurance Workforce

Improvement Program of 19 Dec 05 (Incorporating Change 4, 10

Nov 2015)

X

Navy C&A and Navy ODAA, C&A Guidance for PIT

Interconnection of 20 Jan 09 X

CJCSINST 6510.01F, Information Assurance (IA) and Computer

Network Defense, 9 Feb 2011 X

DODINST 8580.1, Information Assurance (IA) in the Defense

Acquisition System of 09 July 04 X

SECNAV M-5239.1 Department of the Navy Information Assurance

Program, Information Assurance Manual of Nov 05 X

SECNAV 5239.22 DON Cybersecurity Safety Program

(CYBERSAFE), 15 Nov 2016 X

DISA IAVA Process Handbook, Version 3.0, 14 Feb 2007 X NAVSEA Afloat Information Assurance (IA) Implementation

Manual 9400.2-M, April 2012 X

SECNAV 5510.36A DON Information Security Policy, 6 Oct 2006 X Test Procedure Preparation Directive NAVSEA T9050-AA-DIR-

X

NAVSEA S9AA0-AA-SPN-010/GEN-SPEC X

PEO IWS Instruction 5000.8 X PEOIWSINST 5234.1, Software Measurement Policy, dated 31 Jan

X

PEOIWSINST 5239.1, PEO IWS Surface Navy Combat System

Cybersecurity X

Security Technical Implementation Guides

(STIGs) X

Surface Navy Combat Systems Software Product Line

Architecture, Architecture Description Document, Version 1.0, dated 31 July 2009

X

Total Ship Test Program Manual, NAVSEAINST S9095 AD-

TRQ-010/TSTP

X

NIST Special Publication (SP) 800-53 X NIST Special Publication (SP) 800-53A X CNSS Instruction No. 1253 X NAVSEA Afloat PIT RMF Business Rules Interim v1.1, 14 Nov

X

SECNAV M-5510.36 DON Information Security Program Manual, June 2006 X

DONCIO Memo – DON Implementation of the Risk Management

Framework (RMF) for DOD Information Technology, 20 May

X

DONCIO Memo - RMF Process Guide v1.0, 13 Dec 2016 X AEGIS Security Classification Guide 03-011.04 X

C.2.2 System Safety Mil-Std 882E (current version E) (Department of Defense Standard

Practice System Safety) X

OPNAV INST 5100.Navy System Safety Policy (Program

Milestones) System Safety Working Group

NAVSEA INST 9410.2A NSWC Certification Policy, Risk

Assessments, Software Trouble Reports X

NAVSEA PEO IWS Instruction 5000.8 NAVSEA PEO IWS Risk

Management Policy (Standard Chemical Avoidance) X

NAVSEA SW020-AH-SAF-010 Weapon System Safety Guidelines

Handbook X

Navy Weapon System Safety Program, NAVSEAINST 8020.6E, X NAVSEA INST 5100.12B System Safety Engineering Program

Requirements X

NAVSEA INST 5100.12M System Safety Engineering Manual X MIL STD 6016F Interoperability / Force Level Safety X JSWRB / JS-SSA Joint Service Weapon Safety Review Board

(JSWRB) Endorsement of Joint Services Software Safety Authority

(JS-SSA)

X

NOSSA Letter N32-1581 dated 10 Oct 08 Department of Navy

Systems Of Systems (SOS) X

OPNAV INST 5100.24C Environmental Safety Occupational and

Health Considerations in Navy Capabilities and Systems

Engineering Process

X

NAVSEA OP 5, Vol 1, Revision 7, Ch 14 Ammunition and

Explosives Safety Ashore X

NAVSEA INST OP 4 NAVSEA Explosives Safety Afloat X OPNAV INST 5100.23G Navy Occupational Safety and Health

Program Manual X

NOSSA TECHNICAL MANUAL S9310-AQ-SAF-010 Department of Navy Lithium Batteries X

STANAG 4404 Training Safety Precepts Combat System and

Combat System Elements and Design Requirements X

OPNAV INST 1500.75A High Risk Training Policy and Procedures X SEC NAV INST 5100.10K Department of Navy Safety Policy X Joint Software Systems Safety Engineering Military Handbook

454B DoD Handbook Guidance on Software Safety Design X

NAVSEA S2020-AH-SAF-010 Guidelines for Electronic Equipment X OPNAV INST 5100.24C Environmental Safety Occupational and

Health Considerations in Navy Capabilities and Systems

Engineering Processes

X

OPNAV INST 1500.76C Naval Training Systems Requirements, Acquisition and Management X

NAVSEA Hazardous Material (HM) Avoidance Process Technical

Manual (T9070-AL-DPC-020/077-2 X

OPNAV INST 1500.76C CNO Naval Training Systems

Requirements, Acquisition and Management X

Allied Ordnance Publication (AOP 52) Assessment of Munitions

Related Computing Systems North Atlantic Treaty Organization

(NATO) (SSSTRP requested Architectural Analysis, via MIL

STD 882E, Task 205)

X

C.2.3 Test & Evaluation NAVSEA Instruction 9410.2A, Naval Warfare Systems Certification

Policy (NWSCP) X

PEO IWS Instruction 4730.1A, Combat System Certification Process, January 2005 X

PEOIWS Training Systems Directorate, Training Systems

Certification Process, December, 2009

NAVSEA Instruction 4215.1, Implementing Automated Test and Re-

Test Tools in NAVSEA Acquisition Programs, June 10, 2010 X

PEO IWS INSTRUCTION 9800.1, AEGIS Integration Event (AIE)

Process, JAN 23, 2012 X

Incorporating Test and Evaluation into Department of Defense

Acquisition Contracts Guide of October 2011 X

PEOIWSINST 4130.1B, IWS Enterprise Configuration Control

Process (ECCP), SEP 14, 2011 X

PEO IWS Instruction 4732.1, Element Certification policy (Draft) X PEO IWS Instruction 4731.1, Combat System Stress and Endurance

Test Requirements for Surface Programs (Draft) X

S9095-AD-TRQ-010/TSTP Total Ship Test Program (TSTP) MIL-

HDBK-61(SE) Configuration Management Guidance (para 6.2 and

6.3)

X

C.2.4 Logistics DoD Guide to Uniquely Identifying Items, v2.5 September 15, 2012 X DoD Instruction 5000.64 Accountability and Management of DoD-

Owned Equipment and Other Accountable Property, May 19, 2011 X

DoD Instruction 4140.01 DOD Supply Chain Material Management

Regulation, December 14, 2011 X

MIL-STD-31000 Technical Data Packages, Detail Specification, dated 9 Jul 2004 X

MIL-STD-129R Military Marking For Shipment and Storage, Sep

X

NAVSO P-3692 Department of the Navy Guide for Conducting

Independent Logistics Assessment, Revision 8, September 2012 X

SECNAVINST 4105.1 Independent Logistics Assessment and

Certification Requirements November 9, 2012 X

Government Electronics and Information Technology Association

(GEIA) SAE-GEIA-STD-0007, “Logistics Product Data” 1 AUG

X

C.2.5 Systems Engineering Government Electronics and Information Technology Association

(GEIA) GEIA-STD-0007, “Logistics Product Data” 1 AUG 2007 X

PEO Integrated Warfare Systems, Tailored Technical Review

Manual, Version 2.0, 18 DED 2009 X

C.2.6 Software Engineering IEEE 12207, "Standard for Information Technology - Software Life

Cycle Processes" X

IEEE1278 Distributed Interactive Simulation (DIS) Standards X IEEE1516 Standard For Modeling And Simulation (M&S) High

Level Architecture (HLA) Framework And Rules X

C.2.7 Human System Engineering

MIL-STD-1472G X

MIL-STD-46855A DoD Standard Practice Human Engineering

Requirements for Military Systems, Equipment and Facilities X

MIL-HDBK-1908B NOTE 1 X

ASTM-F1166 HUMAN Engineering Design for Marine Systems, Equipment and Facilities, HFS100 American National Standard for

HUMAN Factors Engineering of Visual Display Terminal

Workstations

BFTT Human Integration - Computer Interface (HCI) Design Guide X

MIL-STD 2525C DoD Interface Standard Common Warfighter

Symbology X

Workstation Production Methodology and Programmer’s Handbook, Revision 2, 01 March 2004 X

C.2.8 EW Training Systems Documents Integrated Training Systems / PEO IWS Tailored Technical Review

Manual (TRM) – Tailored 13 February 2013 X

C.2.9 Other Government Documents BFTT Operational Requirement Document (ORD) 21 March 1992 X

C.2.10 Commercial Standards and Specifications 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)

X

HTML for presentation layer (e.g., XML 1.0 www.webstandards.org) X

XML for data transfer X Web services for remote system calls X ISO/IEC 19501:2005 Information technology – Open Distributed

Processing – Unified Modeling Language (UML) Version 1.4.2 X

ASME Y14.100-2004 Engineering Drawing Practices X IEEE/EIA Std 12207-2008 Systems and Software Engineering X ISO 9001:2000 Quality Management Systems -Requirements, dated

12 Dec 2000 X

ISO 10007:2003Quality Management-Guidelines for Configuration

Management X

JAVA SWING Application Program Interface, Addition 7 X ANSI/ISO/ASQ 9001-2008 Quality Management Systems X CMMI-DEV V1.3 or higher X

EIA/IS-632 X

IEEE 1220 X

IEEE Std 24765:2010 X

Note 1: Standards that are not specified within this contract or that are modified must be submitted via e-mail to and approved by the Integrated Warfare System (IWS) 1IT Principle Assistant Program Manager (PAPM) and the

Procurement Contracting Officer (PCO) prior to use.

Note 2: Documents listed are current as of the date of this solicitation. If a more current version becomes available the Contractor shall notify via e-mail IWS 1IT, the Contracting Officer Representative (COR), and the PCO prior to use.

Availability of Documents.

Copies of military handbooks, instructions, standards and specifications and DoD adopted non-Government standards may be obtained in accordance with Federal Acquisition Regulation (FAR) Subpart 52.211-2. Copies of specifications, standards, and data item descriptions cited in this solicitation, if listed in the DoD Index of

Specifications and Standards (DoDISS) or the Acquisition Management Systems and Data Requirements Control

List, DoD 5010.12-L (Dec 2003) may be obtained from:

(a) ASSIST database via the Internet at (https:www.assit.dla.mil/online/start/)

(b) DoD issuances (https://www.esd.whs.mil/DD/DoD-Issuances)

(c) DON issuances (https://www.secnav.navy.mil/doni/classified.aspx)

(d) PEO IWS documents (Please email the Contracting Officer Representative (COR))

(e) By submitting a request to the

Department of Defense Single Stock Point (DoDSSP)

Building 4, Section D

700 Robbins Avenue

Philadelphia, PA 19111-5094

Telephone (215) 697-2667/2179, Facsimile (215) 697-1462

(f) Naval Systems Data Support Activity (NSDSA) website at: https://nsdsa2.phdnswc.navy.mil/

(g) DoD Information Technology Standards Registry at: https://disronline.disa.mil

Copies of non-Government publications not listed in the DoDISS may be obtained from the respective industry association.

Note: Document Precedence

In the event of conflict between the Mandatory and Guidance documents in the preceding paragraphs, the order of precedence shall be the Mandatory documents and then any other Guidance document(s).

C.3.0 REQUIREMENTS

C.3.1 GENERAL REQUIREMENTS- PROGRAM MANAGEMENT – Applicable to all CLINs and (if exercised) Option CLIN(s)

NOTE: As stated in Note A, the use of “X” represents a CLIN series. For example, X005 represents CLINs 0005, 1005, 2005, 3005, 4005.

The Contractor shall perform program management functions to ensure all the contract requirements are met in accordance with the Contract Data Requirements List (CDRL package) – Exhibit A, Exhibit B and Exhibit C. The

Contractor management functions include, but are not limited to:

a. Manage and maintain DD Form 1423 CDRL to ensure compliance with development and delivery requirements.

b. Maintain information liaison with all stakeholders.

c. Track and maintain records of direction and authorization from Contracting Officer Representative

(COR), Alternate Contracting Officers Representative (ACOR), Program Management Office (PMO), Procuring Contracting Officer (PCO), Administrative Contracting Officer (ACO) and Technical

Instruction (TI).

d. Development and tracking of cost data as a management element of the program.

e. Complete inspection and test records.

f. Provide and maintain a Quality Management System (QMS) that meets or exceeds those standards identified by MIL-PRF-31032 GF Hybrid 18 Layer standards, MIL-PRF-55110 standards, 31032 GI

8-layer standards, AS9100D with ISO 9001:2015 standards, and PCB Board UL - USA standards.

g. Maintain auditable records of all costs charged to this contract.

h. Manage production flow to ensure delivery requirements are met.

i. Manage execution of the Technical Instructions.

j. Manage contract funding to ensure that appropriations are expended in an allowable manner and

Limitation of Funds and Cost Clauses are followed.

k. Manage data call responses.

https://mcas-proxyweb.mcas-gov.us/certificate-checker?login=false&originalUrl=https%3A%2F%2Fnsdsa2.phdnswc.navy.mil.mcas-gov.us%2F&McasCSRF=c6eeeb8961786fbf7bfc69b098c514385124dd7b12bfda2f77c66f9162703d5a https://mcas-proxyweb.mcas-gov.us/certificate-checker?login=false&originalUrl=https%3A%2F%2Fdisronline.disa.mil.mcas-gov.us&McasCSRF=c6eeeb8961786fbf7bfc69b098c514385124dd7b12bfda2f77c66f9162703d5a

l. Ensure management practices as necessary to execute this contract in a cost effective and professional manner.

m. Provide and maintain a Contractor Counterfeit Electronic Part Detection and Avoidance System that meets or exceeds those standards identified in DFARS 246.870-3, DFARS 231.205-71, DFARS

252.246-7007, DFARS 252.246-7008, and DFARS 252.244-7001.

n. Maintain and keep account for all Government Furnished Property (GFP) and Government

Furnished Information (GFI) to ensure records and disposition are accurate.

The Government reserves the right to attend meetings between the prime and any of its subcontractors. The

Government requires fourteen (14) calendar days’ notice prior to any prime and subcontractor meetings. The

Contractor shall plan to host a one-day Post Award Kickoff Meeting in accordance with NAVSEA text C-242-H002

Post Award Meeting. The Contractor shall participate in semi-annual program reviews.

PRODUCTION PROCESS IS AS FOLLOWS:

After award of the contract or contract modification containing funded production CLINs, (X005), the Government will provide a Technical Instruction (TI), in accordance with NAVSEA text C-242-H003 – Technical Instructions, containing final production unit configuration, delivery dates and delivery locations.

The Contractor will build, test and deliver in place units that comply with the requirements defined in the applicable

TI, TDP and testing documents. Units that pass the Factory Acceptance Test (FAT), Attachment J-06, will be accepted by the Government via form DD250. The accepted units will then be transferred, via form DD1149, back to the Contractor for completion of any Hull Specific Variations (HSV)-configuration customization to match each ships specific build requirements defined in the applicable TI. The Contractor will use Labor CLINs X001 and other direct costs CLINs X003 to complete the required HSV.

C.3.1.1 Contractor Communication

The Contractor shall communicate to IWS 1IT and document its plans, processes and approaches to meet all program and contract requirements. The Contractor’s Program Management team members shall each possess and maintain Project Management Professional (PMP) certification. The Contractor shall use a metrics-based management approach for planning, scheduling and technical, cost, risk, and quality monitoring/reporting of program-wide visibility of plan versus actual efforts under this contract. The Contractor shall establish, deliver and maintain a program management process that outlines performance against cost schedule and technical objectives.

(CDRL A001, A003)

3.1.1.1 The Contractor shall provide support to the IWS 1IT Integrated Product Team (IPT). The Contractor shall tailor, maintain and deliver (as requested) to the Government its current Systems Engineering Plan (SEP) ensuring that it incorporates the items identified in the IWS 1IT Technical Review Manual (TRM) (Attachment J-10) and

IWS 1IT SEP Inclusion List (Attachment J-11). (CDRL A014)

3.1.1.2 The Contractor shall deliver (as requested) the Contractor’s current Configuration Management Plan (CMP)

(MIL-STD-3046) (CDRL A018) that describes the Contractor’s configuration management program, and the methods, procedures and controls, effective configuration identification, change control, status accounting, and audits of the total configuration, including hardware, software and firmware. The principle use is to provide the

Government a basis for review, evaluation and monitoring of the Configuration Management (CM) program and its proposed components.

3.1.1.3 The Contractor shall develop, tailor, maintain and deliver (as requested) to the Government a Product Road

Map (PRM) (CDRL A055) for each separately funded developmental TI executed and all funded production

CLINs. The Contractor shall develop, tailor, maintain and deliver to the Government all associated Technical Data

Packages (TDP) (CDRL B007).

3.1.1.4 The Contractor shall develop, maintain and deliver (as requested) to the Government a Project Plan for each project funded and defined in a TI by IWS 1IT as shown in the SAMPLE Project Plan (Attachment J-12). (CDRL

A014)

C.3.1.2 Program Management Meetings and Technical Reviews

3.1.2.1 Post Award Kick-off Meeting – The Contractor shall provide a detailed briefing on its management and contract execution strategy at the Post-Award Kick-off Meeting to be held within thirty (30) calendar days of contract award and in accordance with NAVSEA text C-242-H002 Post Award Meeting. The Contractor shall plan for a one-day Post Award Kick-off Meeting to be held at the Contractors facility. As options under the contract are executed, the Government reserves the right to conduct additional kick-off meetings.

3.1.2.2 Program Management Reviews – The Contractor shall conduct semi-annual Program Management Reviews

(PMR), beginning ninety (90) calendar days after award. The Contractor shall document the PMRs, which may be conducted via a Government approved online utility tool or other Government-approved means, with agendas, minutes and presentation materials delivered IAW (CDRLs A007). The purpose of the reviews is to ensure the management approach remains sound, meets the requirements, and is properly documented. The Contractor shall develop and deliver minutes of meetings, in accordance with (CDRL A002) or as directed by the COR for all meetings that have a formal agenda. The PMRs shall include but are not limited to the following:

The objectives and scope of the work for each requirement;

Review of metrics;

Confirmation of resolved issues and managing outstanding issues. This shall include status of significant problems faced by the program manager and current plans to resolve the problems or mitigate their impacts.

Identification and evaluation of risk factors, mitigations, and address areas where risk has changed;

Identification of cost and schedule variance;

Identification of problems with Government Furnished Information or Equipment, impact, and work-around or solutions;

Identification of production status;

Review of Action Items (AIs).

3.1.2.3 Technical Reviews – The Contractor shall schedule all Technical Reviews in the IMS. The technical packages for formal review shall be developed and delivered in accordance with the TI, available electronically to Government

Team ten (10) business days prior to the review.

3.1.2.4 The Contractor shall host and support Technical Interchange Meetings (TIMs) and milestone reviews for development tasking and production quarterly, or as needed on an emergent basis to address critical program issues.

C.3.1.3 Integrated Digital Data Environment

The Contractor shall utilize the secure Integrated Training Systems (ITS) Teams portal operated by Integrated

Warfare Systems 1IT, that provides ready access to create, store, access, manipulate, and exchange digital data via

NIPRNET. The working guide is provided as Total Ship Training Capability (TSTC) Teams Quick Reference

Guide (Attachment J-13). No CLASSIFIED information, documents, software code, or other data shall be loaded to or saved on the TSTC Teams portal. The Contractor shall provide e-mail notification to addressees (see Exhibit A

Attachment 1) within five (5) calendar days of when a deliverable is posted or updated.

All items posted by the Contractor to the ITS Teams portal, including drafts of deliverables that are not final versions, shall be considered delivered for purposes of the DFARS data rights clauses (and subject to the same rights asserted for final deliveries). However, these non-final versions shall not constitute acceptance for purposes of

Section E or the DFARS data rights clauses.

Section 3.1 Deliverables IAW CDRLs:

A001 DI-FNCL-80166C PROGRAM COST AND TECHNICAL DATA REPORTS (FINANCIAL

& TECHNICAL STATUS REPORT)

A002 DI-ADMN-81505 REPORT, RECORD OF MEETING/MINUTES

A003 DI-MGMT-81928 CONTRACTOR’S PROGRESS AND STATUS REPORT

A004 DI-MISC-80508B TECHNICAL REPORT – STUDY/SERVICES (ANALYSIS REPORTS)

A005 DI-MGMT-80596 GOVERNMENT FURNISHED INFORMATION DEFICIENCY

REPORT (DEFICIENCY/ DISCREPANCY REPORTS)

A006 DI-NDTI-80809B TEST/INSPECTION REPORT

A007 DI-ADMN-81373 PRESENTATION MATERIAL (PRESENTATION AND BRIEFING

MATERIAL)

A008 DI-MISC-80508B TECHNICAL REPORT – STUDY/SERVICES (HARDWARE TROUBLE

REPORTS (HTR))

A009 DI-QCIC-80553A ACCEPTANCE TEST PLAN (PRODUCTION ACCEPTANCE TEST

PLAN (PATP))

A010 DI-SESS-80639E ENGINEERING CHANGE PROPOSAL (ECP)

A011 DI-SESS-81830 AS BUILT CONFIGURATION LIST - COMMON (ABCL-C)

A012 DI-MGMT-8227 DIMINISHING MANUFACTURING SOURCES AND MATERIAL

SHORTAGES (DMSMS) HEALTH ASSESSMENT REPORT (DMS

ENGINEERING, MODELING AND HEALTH ASSESMENT)

A013 DI-MGMT-81804A ITEM UNIQUE IDENTIFICATION (IUID) MARKING ACTIVITY,

VALIDATION AND VERIFICATION REPORT

A014 DI-MISC-80508B TECHNICAL REPORT – STUDY/SERVICES

A015 DI-SESS-80255B FAILURE SUMMARY AND ANALYSIS REPORT (CORRECTIVE

ACTION SUMMARY REPORT)

A016 DI-MGMT-80269 STATUS OF GOVERNMENT FURNISHED EQUIPMENT (GFE)

REPORT (GOVERNMENT FURNISHED EQUIPMENT (GFE)

REPORT)

A017 DI-NDTI-80603A TEST PROCEDURE

A018 DI-SESS-81875 CONFIGURATION MANAGEMENT PLAN

A019 DI-IPSC-81434A INTERFACE REQUIREMENTS SPECFICATION (IRS)

A020 DI-IPSC-81436A INTERFACE DESIGN DESCRIPTION (IDD)

A021 DI-IPSC-81438A SOFTWARE TEST PLAN (STP)

A022 DI-IPSC-81440A SOFTWARE TEST REPORT (STR)

A023 DI-IPSC-81431A SYSTEM/SUBSYSTEM SPECIFICATION (SSS)

A024 DI-IPSC-81432A SYSTEM/SUBSYSTEM DESIGN DESCRIPTION (SSDD)

A025 DI-MGMT-81797 PROGRAM MANAGEMENT PLAN

A026 DI-MGMT-81861C INTEGRATED PROGRAM MANAGEMENT DATA AND ANALYSIS

REPORT (IPMDAR) (INTEGRATED MASTER SCHEDULE)

A027 DI-HFAC-81743A HUMAN SYSTEMS INTEGRATION PROGRAM PLAN

A028 DI-IPSC-81437A DATABASE DESIGN DESCRIPTION (DBDD)

A029 DI-IPSC-81438A SOFTWARE TEST PLAN (STP)

A030 DI-IPSC-81427B SOFTWARE DEVELOPMENT PLAN (SDP)

A031 DI- IPSC-81435B SOFTWARE DESIGN DESCRIPTION (SDD)

A032 DI-IPSC-81442A SOFTWARE VERSION DESCRIPTION (SVD)

A033 DI-IPSC-81443A SOFTWARE USER MANUAL (SUM)

A034 DI-IPSC-81433A SOFTWARE REQUIREMENTS SPECIFICATION (SRS) (ELEMENT

B5's)

A035 INTENTIONALLY LEFT BLANK

A036 DI-SESS-8l785A SYSTEMS ENGINEERING MANAGEMENT PLAN (SEMP)

A037 DI-ILSS-80095 INTEGRATED LOGISTICS SUPPORT PLAN

A038 DI-ILSS-80872 TRAINING MATERIALS (TRAINING DATA PRODUCT)

A039 DI-IPSC-81488 COMPUTER SOFTWARE PRODUCT (SOFTWARE SOURCE CODE

AND DOCUMENTATION)

A040 DI-IPSC-81756 SOFTWARE DOCUMENTATION (SOFTWARE DOCUMENTATION

AND TEST READINESS)

A041 DI-MGMT-81842 VULNERABILITY SCAN COMPLIANCE (VSC) REPORT (SYSTEM

SECURITY MANAGEMENT)

A042 DI-MGMT-81843 INFORMATION ASSURANCE (IA) TEST REPORT

A043 DI-MGMT-81844 INFORMATION ASSURANCE (IA) TEST PLAN

A044 DI-MGMT-81845 INFORMATION ASSURANCE (IA) DESIGN REVIEW

INFORMATION PACKAGE (DRIP)

A045 DI-NDTI-80809B TEST/INSPECTION REPORT (SOFTWARE)

A046 DI-NDTI-80809B TEST/INSPECTION REPORT (HARDWARE)

A047 DI-MISC-81283 SPECIFICATION REQUIREMENT VERFICIATION MATRIX

A048 DI-MGMT-81844 INFORMATION ASSURANCE (IA) TEST PLAN (CYBERSECURITY

TEST PLAN)

A049 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(GOVERNMENT FUNISHED INFORMATION DEFICIENCY REPORT)

A050 DI-SAFT-81065 SAFETY STUDIES REPORT

A051 DI-MGMT-82002B CYBERSECURITY IMPLEMENTATION PLAN

A052 DI-QCIC-81794A QUALITY ASSURANCE PROGRAM PLAN (QAPP) (QUALITY

MANAGEMENT PLAN) (QMP)

A053 DI-MGMT-81808 CONTRACTOR’S RISK MANAGEMENT PLAN

A054 DI-SESS-81613A RELIABILITY AND MAINTAINABILITY (R&M) PROGRAM PLAN

A055 DI-IPSC-82297 PRODUCT ROADMAP

A056 DI-MGMT-82274 DIMINISHING MANUFACTURING SOURCES AND MATERIAL

SHORTAGES (DMSMS) LIFE CYCLE MANAGEMENT DATA (DMS

ENGINEERING, MODELING AND HEALTH ASSESMENT)

A057 DI-MISC-80508B TECHNICAL REPORT - STUDY/SERVICES (OPSEC OPERATIONS

TRAINING MANUAL)

B001 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(TECHNICAL DATA PACKAGE (TDP))

B002 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(PRODUCTION DRAWINGS)

B003 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(PRODUCT DRAWINGS/ MODELS AND ASSOCIATED LIST)

B004 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(CONCEPTUAL DESIGN DRAWINGS/MODELS)

B005 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(DEVELOPMENTAL DESIGN DRAWINGS/MODELS AND

ASSOCIATED LISTS)

B006 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(ENGINEERING DOCUMENTATION PRODUCT DRAWINGS)

B007 DI-ADMN-80776B TECHNICAL DATA PACKAGE (TDP)

B008 DI-SESS-81000F PRODUCT ENGINEERING DESIGN DATA AND ASSOCIATED LISTS

B009 DI-SESS-81002F DEVELOPMENTAL DESIGN DRAWINGS AND ASSOCIATED LISTS

C001 DI-TMSS-81677B SYSTEM TECHNICAL MANUAL (SANITIZED) (TECHNICAL

MANUALS)

C.3.2 FIRST ARTICLE UNIT

C.3.2.1 FIRST ARTICLE UNIT PRODUCTION - Applicable to CLIN 0008

The Contractor shall produce, test, and deliver first article unit (FAU) consistent with the system specifications and technical direction identified in the Build-to-Print documentation provided in Attachment J-02.

C.3.2.2 FIRST ARTICLE TESTING

The Contractor shall perform FAU testing of the BEWT II using Attachment J-06, BEWT II Factory Acceptance

Test (FAT) Procedure with Instructions. The Contractor shall ensure compliance with the provided Attachment J-06 instructions and Federal Acquisition Regulation (FAR) 52.209-3 First Article Approval-Contractor Testing.

The Contractor shall develop and deliver First Article Unit Test (FAUT) reports in accordance with

CDRL A006.

Section C.3.2 Deliverables IAW CDRLs:

A006 DI-NDTI-80809B TEST/INSPECTION REPORT

C.3.3 TRAINING (BEWT II) SYSTEM PRODUCTION

C.3.3.1 BATTLEFORCE ELECTRONIC WARFARE TRAINING (BEWT II) SYSTEM PRODUCTION –

If exercised, Applicable to CLIN series X005

The Contractor shall produce, test, and deliver training systems consistent with the system specifications and technical direction identified in the Build-to-Print documentation provided in Attachment J-02. The Contractor shall implement and maintain UIID marking as required by DFARS 252.211-7003 “ITEM UNIQUE IDENTIFICATION AND

VALUATION.” System baseline, software version, delivery date and receiving location shall be as directed in the modification exercising the option for each system.

The Contractor shall evaluate all Cyber Security guidance changes discovered under C.3.1.5 for impact to system production. Any required design changes shall be documented in the Engineering Change Process (ECP) and submitted to the Government using the established process.

The BEWT II system is Grade B Shock, Power Qualification, and Electro Magnetic Interference (EMI) certified in accordance with MIL-S-901D, Medium Weight Shock Machine (MWSM), Grade B, Type A, Class I equipment;

MIL-STD-1399, Section 300B; and MIL-STD-461 F (Surface Ships). Specific configurations and delivery instructions for all production units will be identified by a TI.

The Contractor shall perform Factory Acceptance Testing (FAT) using BEWT II Factory Acceptance Test Procedures

(Attachment J-06).

In the event that production is impacted due to diminishing manufacturing sources and material shortages (DMSMS) or other matters related to parts issues, the Contractor shall notify the COR and PMO, via email, within five (5) working days of receipt of notification.

C.3.3.2 PROTOTYPE AND MISCELLANEOUS PRODUCTION - CLIN 0001, and if exercised, CLINS series

X001, X003, and X007.

The Contractor shall procure parts and components to assemble, integrate, test, and label prototype and miscellaneous production units to meet the requirements as defined in the TI. The assembled systems shall be labeled with label plates in accordance with the Item Unique Identification (IUID) requirements pursuant to DFARS

252.211-7003. All production units shall be stored until shipment. The storage space shall be dry and climate controlled (Air conditioning and Heat) and secured with access control. All allowable and allocable costs for production of prototypes and miscellaneous items are allocable to Labor CLINs X001, X007 and other direct costs

CLINs X003. The Contractor shall make no changes to the system, system parts and components without

Government Approval.

C.3.3.3 PRODUCTION FACILITIES Applicable to all CLINs and (if exercised) Option CLIN(s)

The Contractor shall provide the following Production Facility capabilities:

a. 120VAC 60Hz, 1-phase electrical power available in the facility.

b. Capability to safely load and unload from covered and uncovered trucks, crated or uncrated electronic equipment.

c. A production area to support production preparation as necessary to meet the estimated annual production requirement as identified in the TI.

d. Access to secured storage sufficient in size to support the estimated annual production requirement and pre-acceptance storage of (one) 1 to five (5) units.

e. Facility to support the integration of equipment, hardware, components, and test of limited production runs.

f. Ability to fabricate foundations, chassis, front panels, Input/Output (I/O) panels, brackets and other sheet metal components; including machining, bending, drilling, welding, punching, cleaning, anodizing, priming, painting, engraving and silk-screen marking either in-house or via vendor.

g. Ability to fabricate, assemble, test and perform continuity checks on connectors, cables, wire and cable harnesses either in-house or via vendor.

Section C.3.3 Deliverables IAW CDRLs:

B001 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(TECHNICAL DATA PACKAGE (TDP))

B002 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(PRODUCTION DRAWINGS)

B003 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(PRODUCT DRAWINGS/ MODELS AND ASSOCIATED LIST)

B004 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(CONCEPTUAL DESIGN DRAWINGS/MODELS)

B005 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(DEVELOPMENTAL DESIGN DRAWINGS/MODELS AND

ASSOCIATED LISTS)

B006 DI-ADMN-80925A REVISIONS TO EXISTING GOVERNMENT DOCUMENTS

(ENGINEERING DOCUMENTATION PRODUCT DRAWINGS)

B007 DI-ADMN-80776B TECHNICAL DATA PACKAGE (TDP)

B008 DI-SESS-81000F PRODUCT ENGINEERING DESIGN DATA AND ASSOCIATED LISTS

B009 DI-SESS-81002F DEVELOPMENTAL DESIGN DRAWINGS AND ASSOCIATED LISTS

C.3.4 SYSTEMS ENGINEERING, DESIGN, DEVELOPMENT, IMPLEMENTATION, TEST, AND

SUPPORT (Level Of Effort)

C.3.4.1 SAFETY Applicable CLIN 0001, and if exercised, to CLIN series X001

The Contractor shall design all systems and components to provide the users the ability to maintain positive control over the capability to inject synthetic information into a shipboard combat system. A Permission-To-Train (PTT) authorization is required from the combat system before simulators and stimulators can inject synthetic data into the combat system. This authorization must be capable of being retracted automatically if safe conditions are no longer being met. A designated operator must also be able to retract this permission. Loss of PTT must cause simulation and stimulation of combat system elements to immediately cease. Training and stimulation to the combat system can resume once PTT is restored.

Systems Engineering tasking will be directed by the Government through the use of TIs as defined in Section C

NAVSEA Text “ C-242-H003” TECHNICAL INSTRUCTIONS.”

C.3.4.2 DEVELOPMENT AND SUPPORT Applicable to CLIN 0001, and if exercised, CLIN series X001

The Government will task the Contractor, via TI, to provide engineering support. The engineering efforts will include, but not limited to, the following:

1. Surface Electronic Warfare Team Trainer (SEWTT),

2. Battleforce Electronic Warfare Trainer II (BEWT II),

3. Combined Integrated Air and Missile Defense (IAMD) and Anti-Surface Warfare (ASW) Trainer

(CIAT),

4. Nulka/Countermeasures

5. BEWT Legacy and BEWT II In-Service Engineering Agent (ISEA) sustainment and support.

3.4.2.1 SEWTT

The SEWTT trains AEGIS and SSDS EW watch standers, individually and as a Team, when interfaced with the

BFTT system, through the stimulation of the SLQ 32V6 tactical electronic warfare consoles both onboard ships and at shore-based facilities. The SLQ 32V6 is the processing and human interface portion of the most recent upgrade to the Navy’s electronic warfare tactical capability being undertaken. This multi-year multi-phase upgrade is known as the Surface Electronic Warfare Improvement Project (SEWIP). SEWTT is a Computer System Configuration Item

(CSCI) integrated into the SLQ 32V6 software.

3.4.2.2 BEWT II

The BEWT trains AEGIS and SSDS watch standers, individually and as a Team when interfaced with the BFTT system, through the stimulation of the SLQ 32A and SLQ 32B tactical electronic warfare consoles both onboard ships and at shore-based facilities. The latest version of the BEWT system is the BEWT II. The BEWT II adds capability, enhances fidelity of the training experience, and significantly reduces production and sustainment costs from the

BEWT Legacy by moving all the processes into a laptop and Integration Management Unit (IMU).

3.4.2.3 CIAT

The CIAT trains AEGIS IAMD and ASW watch standers individually and as a team, in a high fidelity, shore-based training environment that will replicate the environmental and tactical conditions of real-world operations. The trainer will require trainees to respond to the threats with approved Navy and Joint doctrine and capability as they would in live combat operations.

3.4.2.4 Nulka/Countermeasures

Countermeasures include Nulka and other active and passive devices and capabilities that individually and as a group are used by the ship to deflect or dissuade a hostile missile away from the ship. This training component will be designed for integration into BEWT II and SEWTT.

3.4.2.5 BEWT Legacy and BEWT II ISEA

The BEWT Legacy and BEWT II ISEA sustainment and support is provided to ship and shore as required to insure uninterrupted operation of the training systems. This support includes telephone, email, and on-site as necessary;

depot level repair; and parts support.

C.3.4.3 DESIGN AND IMPLEMENTATION - Applicable to CLIN 0001 and if exercised, CLIN series X001

The Contractor shall, adhering to the PEO IWS Technical Review Manual (TRM) Version 3.0 (Attachment J-10), perform the system engineering design and implementation required to design, develop, test, and deliver hardware and software and documentation changes to update training system capabilities as directed in the TI. Systems engineering activities shall include: engineering analyses to establish the technical approach and the integration requirements for training; pursuit of new technologies beneficial to that tasking; development of the integration concept and alternatives; development of interface hardware and software requirements and alternatives; development of Engineering Change Request (ECRs) for the implementation of new capabilities or replacement of hardware/software for enhanced capabilities; and assessment of technical, cost, and schedule risks as directed in the

TI. The Contractor shall update and revise, as tasked, documentation provided under Government Furnished

Information (Attachment J-00). In addition, the Contractor shall support, as directed in the TI, the training system integrators and design agents in the integration of products into new and existing system baselines.

C.3.4.4 DEVELOPMENT PROGRAM PLAN - Applicable to CLIN 0001, and if exercised, CLIN series X001 and X007

The Contractor shall develop and deliver a Project Plan (PP) (Attachment J-12) (CDRL A014) for each development project as directed in the TI. (e.g. SEWTT, BEWT II, CIAT, and NULKA/Countermeasures). The PPs shall describe the specifics of how the requirements will be executed, monitored, scheduled, and controlled. The PPs shall include:

1. Organization Plan that outlines how information flows between internal stakeholders and how decisions are made;

1. Organization chart showing the management organization for implementation of the contract;

2. Description of management tools for the purpose of evaluating status, early detection of problems and problem resolution;

3. Description of financial status and procedures for reporting work progress;

4. Identification of project TPOC’s that are authorized by the Contractor to interface with the

Program Office;

5. Quality Assurance (QA) plan outlining the process that the Contractor will use to ensure software

QA process is implemented and maintained that, at a minimum, adheres to the requirements of

ANSI/ISO/ASQ 9001-2008 Quality Management Systems;

6. Address Risk Management (RM) outlining the process the Contractor will use to track, report and manage and mitigate risk for each TI;

7. Security Management (SM) plan outlining the procedures and processes the Contractor will impose to stay consistent with the security classification guide and all appropriate security instructions.

C.3.4.5 SCHEDULE & COST PERFORMANCE REPORTING - Applicable to CLIN 0001, and if exercised, CLIN series X001 and X007

To effectively manage the efforts assigned under this contract, the Contractor shall, in addition to the information reporting identified in 3.1, implement an integrated schedule and cost performance reporting process.

Product Road Map (CDRL A055) – The Contractor shall implement and maintain an Integrated Master Schedule for each development TI (e.g. SEWTT, CIAT, Countermeasures). The IMSs shall identify all development milestones, major tasks, efforts, and activities necessary to successfully execute the tasks with estimated labor hours and costs associated with each. The IMSs shall provide rigorous schedule management, facilitate the identification of task interdependencies, and provide additional insight through the use of critical path analysis. The IMSs shall be created in Microsoft Project 2013 or earlier, or Government approved substitute. The IMSs shall be reviewed at the semi-annual PMRs with emphasis on approved changes, missed or potentially missed deadlines or deliveries, cost changes, risks, and problem solving.

The Contractor shall report financial data IAW Program Cost and Technical Data Reports (CDRL A001) under this contract operating IAW commercial accounting standards as promulgated by the Financial Accounting Standards

Board (FASB). The Contractor shall provide this data electronically. The financial data shall be integrated by the

Contractor with the IMS to provide the Government with an integrated schedule and cost performance picture.

C.3.4.6 OPEN SYSTEMS APPROACH AND GOALS - Applicable to CLIN 0001, and if exercised, CLIN series

X001

In satisfying the Government’s requirements, the following system architecture approach characteristics shall be utilized:

a. Open Architecture – The contractor shall develop and maintain an architecture that incorporates appropriate considerations for reconfigurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

i. Ensure that external information exchange requirements are implemented in a standard and open manner as part of this effort. These actions shall include planning that identifies the contractor’s specific approach to ensuring system and interface data is well-defined, available to all programs, and uses a standards-based tool for definition within the context of DoD and

Service upgrade programs. The contractor shall develop system upgrades, IT system capabilities and business rules that ensure that: 1) data will be posted to shared spaces for users to access and download except when limited by security, policy, or regulations; 2) data shall provide for interoperability with many-to-many exchanges of data, and verified trust and integrity of users and applications; and 3) data, including applicable markings if any, shall be transmitted through well and openly defined interfaces.

ii.The contractor shall ensure that its projects, at the architectural and operational level, continue to promote the use of an open architecture as well as adoption of other standards and requirements, tailored to meet its specific Military Service, Coalition and Joint Military

Service requirements as defined throughout this document.

b. Modular, Open Design – The contractor shall develop an architecture that is layered and modular and uses standards-based Commercial-Off-The-Shelf (COTS)/Non-Developmental-Item (NDI) hardware, operating systems, and middleware that all utilize either non-proprietary or non-vendor-unique key module or component interfaces. The contractor’s design approach shall be applied to all subsystems and components. As part of its Open System Management Plan, the contractor shall, at a minimum, - describe how the proposed system architecture meets these goals, including the steps taken to use non-proprietary or non-vendor unique COTS or reusable NDI components wherever practicable.

i.Module Coupling – The contractor’s design approach shall result in loose coupling, minimal dependencies on other modules, as evidenced by simple, well-defined interfaces and by the absence of implicit data sharing. The purpose is to ensure that any changes to one module will not necessitate extensive changes to other modules, and hence facilitate module replacement and system enhancement. The Contractor shall describe their approach used determine the level of coupling and the design trade-off.

ii.Module Cohesion – The contractor’s design shall result in modules that are characterized by the singular assignment of identifiable and discrete functionality. The purpose is to ensure that any changes to system behavioral requirements can be accomplished by changing a minimum number of modules within the system. The Contractor shall describe their approach used to determine the level of cohesion and the design trade-off.

c. System Requirements Accountability – The contractor shall ensure that all system requirements

(including those contained in the Initial Capabilities Document, Capabilities Development Document, Capabilities Production Document, and in this Section C) are accounted for through a demonstrated ability to trace each requirement to one or more modules that consist of components that are self-contained elements with well-defined, open and published interfaces implemented using open standards.

d. Inter-component Dependencies – The contractor’s designs shall result in a layered system design, maximizing software independence from the hardware, thereby facilitating technology refresh. The design shall be optimized at the lowest component level to minimize inter-component dependencies. The layered design shall also isolate the application software layers from the infrastructure software (such as the operating system) to enhance portability and to facilitate technology refresh. The design shall be able to survive a change to the computing infrastructure with minimal or no changes required to the application logic. The interfaces between the layers shall be built to open standards or the technical data describing the interface shall be available to the Government with at least Government Purpose Rights. The system architecture shall minimize inter-component dependencies to allow components to be decoupled and reused, where appropriate, across various DoD or Service programs and platforms.

e. Modular Open Systems Approach (MOSA) – The contractor shall describe its rationale for the modularization choices made to any designs generated on this contract. These components shall be of a size that supports competitive acquisition as well as reuse. The contractor’s design approach shall emphasize the selection of components that are available commercially or within the DoD, to avoid the need to redevelop products that already exist and that can be reused. The contractor’s rationale shall explicitly address any tradeoffs performed, particularly those that compromise the modular and open nature of the system.

f. MOSA Objectives – The contractor shall specify how it plans…