18-R-5113_Amendment_1.pdf

N0002418R5113

N0002417NR46544

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

Amendment 1 updates Box 9, Section C, Section L, Attachments L-08 and L-11, and Section M.

1. CONTRACT ID CODE PAGE OF PAGES

U 1 53

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

16C. DATE SIGNED

BY 12-Jun-2018

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 N0002418R5113

X 9B. DATED (SEE ITEM 11)

30-May-2018

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 2 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

12-Jun-2018

CODE

NAVAL SEA SYSTEMS COMMAND, SEA 02

1333 ISAAC HULL AVE. S.E.

BLDG. 197, 5W2531

WASHINGTON DC 20376

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

The following items are applicable to this amendment:

1) Box 9 has been updated

FROM: 6 July 2018 TO: 17 July 2018

2) As Posted:

C.1.2 Scope The scope of this contract is to continue the US Navy’s migration from legacy BEWT systems to the new and developing BEWT II systems; continue development of enhanced capabilities of the SEWTT software; continue the development of the 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; incorporation of 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.

As Amended:

C.1.2 Scope The scope of this contract is to continue the US Navy’s migration from legacy BEWT systems to the new and developing BEWT II systems; continue development of enhanced capabilities of the SEWTT software; continue the development of the CIAT training system; develop future training capabilities, such as Advanced Off- Board Electronic Warfare (AOEW), 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; incorporation of 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.

3) As Posted:

C.3.2.2 Development and Support

(Applicable to CLINs 0001, and if exercised 1001, 2001, 3001, 4001)

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 BEWT II In-Service Engineering Agent (ISEA) sustainment and support.

As Amended:

(Applicable to CLINs 0001, and if exercised 1001, 2001, 3001, 4001)

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. AOEW/Countermeasures

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

4) As Posted:

3.2.2.4 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. These training components will be designed for integration into BEWT II and SEWTT as applicable.

As Amended:

3.2.2.4 Countermeasures include AOEW, 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. These training components will be designed for integration into BEWT II and SEWTT as applicable.

5) As Posted:

C.3.2.4 Development Program Plan

The Contractor shall develop and deliver a Program Plan (PP) (CDRL A012) for each development TI executed.

(e.g. SEWTT, BEWT II, CIAT, and NULKA/Countermeasures).

As Amended:

(Applicable to CLINs 0001, and if exercised 1001, 2001, 3001, 4001)

The Contractor shall develop and deliver a Program Plan (PP) (CDRL A012) for each development TI executed.

(e.g. SEWTT, BEWT II, CIAT, and AOEW/Countermeasures).

6) As Posted:

1.1. The following attachments are applicable to the preparation of the offer:

Attachment L-01 – Cross Reference Matrix (CRM) Attachment L-02 – Addressing a new EW Capability Attachment L-03 – NULKA Capability Design & Implementation Attachment L-04 – Question Submittal Form Attachment L-05 – Pre-Award Accounting System Adequacy Checklist Attachment L-06 – Previous Contract Effort Narratives Attachment L-07 – Past Performance Questionnaire Attachment L-08 – Cost and Price Proposal Tables Attachment L-09 – Contractor Award Information Attachment L-10 – Facilities Checklist Attachment L-11 – Employee Qualification Form

As Amended:

1.2. The following attachments are applicable to the preparation of the offer:

Attachment L-01 – Cross Reference Matrix (CRM) Attachment L-02 – Addressing a new EW Capability

Attachment L-03 – AOEW Capability Design & Implementation Attachment L-04 – Question Submittal Form Attachment L-05 – Pre-Award Accounting System Adequacy Checklist Attachment L-06 – Previous Contract Effort Narratives Attachment L-07 – Past Performance Questionnaire Attachment L-08 – Cost and Price Proposal Tables Attachment L-09 – Contractor Award Information Attachment L-10 – Facilities Checklist Attachment L-11 – Employee Qualification Form

7) Attachment L-08 has been updated

8) Attachment L-11 has been updated

9) As Posted:

a. Section L 2.1 – Proposal Format and Delivery

The contents of the proposal (with page limitations, copy requirements, and references to explanatory paragraphs in this section) are summarized in the table below:

Section 2.1, Table 1: Proposal Summary Copies Returned Volume Title Page Limit Paper Electronic

I Executive Summary 5 1 2

II

Technical Proposal

1 2

Factor 1 – Production 5 Factor 2 - Sample Problems -Addressing a New EW Capability 15 -NULKA Capability Design & Implementation

Factor 3 – Technical Approach -Technical Plans and Engineering Approach

-Key Personnel and Letters of Intent 9 -Employee Qualification Form Unlimited

III

Factor 4 - Management Approach

1 2 Process Management 5

IV

Factor 5 - Past Performance

1 2 Previous Contract Effort Narratives 3 each Past Performance Questionnaires 3 each

V Factor 6 - Cost/Price Proposal None 1 2

As Amended:

1.3. Section L 2.1 – Proposal Format and Delivery

The contents of the proposal (with page limitations, copy requirements, and references to explanatory paragraphs in

I Executive Summary 5 1 2

II

Technical Proposal

1 2 Factor 1 – Production 5 Factor 2 - Sample Problems

-Addressing a New EW Capability 15 -AOEW Capability Design & Implementation

Factor 3 – Technical Approach -Technical Plans and Engineering Approach

-Key Personnel and Letters of Intent 9 -Employee Qualification Form Unlimited

III

Factor 4 - Management Approach

1 2 Process Management 5

IV

Factor 5 - Past Performance

1 2 Previous Contract Effort Narratives 3 each Past Performance Questionnaires 3 each

V Factor 6 - Cost/Price Proposal None 1 2

10) As Posted:

2. Section L 3.0 – Proposal Contents

The EWTS proposal shall be organized in accordance with the following instruction. FAILURE TO FOLLOW

THESE INSTRUCTIONS MAY RESULT IN REJECTION OF THE PROPOSAL.

Proposals shall be organized into five separate volumes, (I) Executive Summary, (II) Technical Proposal, (III) Management Proposal, (IV) Past Performance, and (V) Cost and Price Proposal.

An outline is provided below.

Volume I – Executive Summary Volume II – Technical Proposal o Factor 1: Production o Factor 2: Sample Problems

Addressing New EW Capability NULKA Capability Design & Implementation o Factor 3: Technical Approach Technical Plans and Engineering Key Personnel and Letters of Intent Employee Qualifications Form

Volume III – Management Proposal o Factor 4: Management Approach

Process Management Volume IV – Past Performance o Factor 5: Past Performance Previous Contract Effort Narratives Past Performance Questionnaires

Volume V – Cost and Price Proposal o Factor 6: Cost and Price

3. Section L 3.0 – Proposal Contents

The EWTS proposal shall be organized in accordance with the following instruction. FAILURE TO FOLLOW

THESE INSTRUCTIONS MAY RESULT IN REJECTION OF THE PROPOSAL.

Proposals shall be organized into five separate volumes, (I) Executive Summary, (II) Technical Proposal, (III) Management Proposal, (IV) Past Performance, and (V) Cost and Price Proposal.

An outline is provided below.

Volume I – Executive Summary Volume II – Technical Proposal o Factor 1: Production o Factor 2: Sample Problems

Addressing New EW Capability AOEW Capability Design & Implementation o Factor 3: Technical Approach Technical Plans and Engineering Key Personnel and Letters of Intent Employee Qualifications Form

Volume III – Management Proposal o Factor 4: Management Approach

Process Management Volume IV – Past Performance o Factor 5: Past Performance Previous Contract Effort Narratives Past Performance Questionnaires

Volume V – Cost and Price Proposal o Factor 6: Cost and Price

11) As Posted:

3.1.2.2 Factor 2: Sample Problems

The Offeror shall submit a response that fully explains its analysis of each of the provided Sample Problems, its proposed solution, and all additional response requirements defined in each individual Sample Problem.

The Offeror’s response to the sample problems shall demonstrate a practical application of the Offeror’s technical approach to resolving discrete problems posed in the sample problems. The Offeror shall discuss the degree of risk associated with the methodology(ies) and analytical techniques the Offeror applies to fulfilling the stated requirements.

See Attachment L-02: Addressing a New EW Capability See Attachment L-03: NULKA Capability Design & Implementation

As Amended:

3.1.2.2 Factor 2: Sample Problems

The Offeror shall submit a response that fully explains its analysis of each of the provided Sample Problems, its proposed solution, and all additional response requirements defined in each individual Sample Problem.

The Offeror’s response to the sample problems shall demonstrate a practical application of the Offeror's technical approach to resolving discrete problems posed in the sample problems. The Offeror shall discuss the degree of risk associated with the methodology(ies) and analytical techniques the Offeror applies to fulfilling the stated requirements.

See Attachment L-02: Addressing a New EW Capability See Attachment L-03: AOEW Capability Design & Implementation

12) As Posted:

3. Employee Qualifications: Using Attachment L-11 (Employee Qualification Form), the Offeror shall matrix proposed labor categories to the Government Labor Categories. In the format described by Attachment L-11 (Employee Qualification Form) Offerors shall provide the following information set:

a. Offeror’s proposed corresponding labor category

b. Individual’s Name

c. Employer (employee’s company name)

d. Years of related professional experience

e. Highest educational degree obtained

f. Degree area

g. Security Clearance level

h. Relevant certification and other notes

i. Citizenship

In the event the Offeror has not identified a firm candidate for a proposed labor category, include the word “pending” in lieu of an individual’s name. Offerors should attempt to minimize the number of proposed labor personnel for which candidates have not been identified. From an evaluation perspective, proposal risk in terms of “Technical Capability” and “Cost Realism” may increase if candidates have not been identified for proposed labor category positions. The labor categories for all proposed CLINs will be the same mix and amount of hours as detailed in Attachment L-08 (Cost and Price Proposal Tables). Data contained in Attachment L-11 (Employee Qualification Form) shall not conflict with data provided for the Key Personnel.

Requirement Labor Category

Senior Mid-Level Junior

Percentage of Personnel as Compared to Offer's Total Number of Labor Resources

34% 33% 33%

Relevant Experience in Their Specific Task Area

8 years or more Greater than 3 and less than 8

At least one year and up to three

3. Employee Qualifications: Using Attachment L-11 (Employee Qualification Form), the Offeror shall matrix proposed labor categories to the Government Labor Categories. In the format described by Attachment L-11 (Employee Qualification Form) Offerors shall provide the following information set:

a. Offeror’s proposed corresponding labor category

b. Individual’s Name

c. Employer (employee’s company name)

d. Years of related professional experience

e. Highest educational degree obtained

f. Degree area

g. Security Clearance level

h. Relevant certification and other notes

i. Citizenship

In the event the Offeror has not identified a firm candidate for a proposed labor category, include the word “pending” in lieu of an individual’s name. Offerors should attempt to minimize the number of proposed labor personnel for which candidates have not been identified. From an evaluation perspective, proposal risk in terms of “Technical Capability” and “Cost Realism” may increase if candidates have not been identified for proposed labor category positions. The labor categories for all proposed CLINs will be the same mix and amount of hours as detailed in Attachment L-08 (Cost and Price Proposal Tables). Data contained in Attachment L-11 (Employee Qualification Form) shall not conflict with data provided for the Key Personnel.

Requirement Labor Category

Senior Mid-Level Junior

Percentage of Personnel as Compared to Offer's Total Number of Labor Resources

40% 30% 30%

Relevant Experience in Their Specific Task Area

8 years or more Greater than 3 and less than 8

At least one year and up to three

13) As Posted:

2. Sample Problem: Attachment L-03 (NULKA Capability Design & Implementation)

Evaluation: The Government will evaluate whether the Offerors submission –

a) demonstrate the technical knowledge required to execute the task;

b) detail processes and engineering skill sets required;

c) detail a software design & development capability;

d) demonstrate an understanding of the system performance requirements;

e) define the degree of risk associated with the methodology(ies) to be applied to the problem set and analytical techniques the Offeror applies to risk discovery with corresponding risk mitigation;

f) define the required test and evaluation skills and processes;

g) detail cyber security compliance requirements and compliance process;

h) demonstrate an understanding of the documentation and logistics required to support the capability;

i) detail the process of developing a single training capability for each of the three (3) different training systems;

j) detail any differences in the Offeror’s approach to each of the training systems, highlighting any unique interfaces or communications requirements;

k) detail external resources and products necessary to integrate and deliver the training capability;

l) list and describe the documentation required to meet the Objective Qualification Evidence (OQE) requirements for delivery to an Aegis Engineering Assessment prior to entry into an Aegis Integration Event (AIE).

The Government will evaluate whether the responses to the sample problems provide a sound and executable path forward to delivering this new training capability to the Fleet.

2. Sample Problem: Attachment L-03 (AOEW Capability Design & Implementation)

Evaluation: The Government will evaluate whether the Offerors submission –

a) demonstrate the technical knowledge required to execute the task;

b) detail processes and engineering skill sets required;

c) detail a software design & development capability;

d) demonstrate an understanding of the system performance requirements;

e) define the degree of risk associated with the methodology(ies) to be applied to the problem set and analytical techniques the Offeror applies to risk discovery with corresponding risk mitigation;

f) define the required test and evaluation skills and processes;

g) detail cyber security compliance requirements and compliance process;

h) demonstrate an understanding of the documentation and logistics required to support the capability;

i) detail the process of developing a single training capability for each of the three (3) different training systems;

j) detail any differences in the Offeror’s approach to each of the training systems, highlighting any unique interfaces or communications requirements;

k) detail external resources and products necessary to integrate and deliver the training capability;

l) list and describe the documentation required to meet the Objective Qualification Evidence (OQE) requirements for delivery to an Aegis Engineering Assessment prior to entry into an Aegis Integration Event (AIE).

The Government will evaluate whether the responses to the sample problems provide a sound and executable path forward to delivering this new training capability to the Fleet.

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 06-Jul-2018 11:00 AM to 17-Jul-2018 12:00 AM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

C.1.0 INTRODUCTION

C.1.1 Background The Battle Force Tactical Training (BFTT) Program is an Acquisition Category (ACAT) IV-M acquisition program that provides the hardware and software required to integrate onboard trainers and simulators and stimulators into a baseline multi-warfare and multi-ship combat system team training capability. An integral part of the programs under the BFTT are the Battle Force Electronic Warfare Trainer (BEWT), Surface Electronic Warfare Team Trainer (SEWTT) and Combined Integrated Air and Missile Defense and Anti-Surface Warfare Trainer (CIAT). The BEWT, SEWTT and CIAT systems, whether integrated with BFTT or operating in standalone mode, are the sole providers of tactical EW training to the US Navy and US Coast Guard.

C.1.2 Scope 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 US Navy and US Coast Guard. The scope of this contract is to continue the US Navy’s migration from legacy BEWT systems to the new and developing BEWT II systems; continue development of enhanced capabilities of the SEWTT software; continue the development of the CIAT training system; develop future training capabilities, such as Advanced Off-board Electronic Warfare (AOEW), 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; incorporation of 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 DOCUMENTS FOR INCORPORATION OR REFERENCE

The specifications or standards (government and commercial) necessary for successful performance of this contract are listed in sections below. Additional specifications, standards, instructions, directives, and other publications may be cited in individual TIs as guidance and clarification for the Contractor. The contractor shall use all documents in C.2.1-2.10 denoted as “Incorporation” as requirements in executing the SOW. All documents denoted as reference shall be used as reference guides during performance.

DOCUMENTS INCORPORATION REFERENCE

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

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 Definitions for DON, and Enclosure (2), DON Platform IT IA Guidance

X

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

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 2012

X

PEOIWSINST 5239.1, PEO IWS Surface Navy Combat System Cybersecurity

X

Security Technical Implementation Guides X

(STIGs) 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 2014

X

DONCIO Memo - RMF Process Guide v1.0, 13 Dec 2016 X BFTT Security Classification Guide 2-15-17 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

X

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

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

X

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, 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

Government Electronics and Information Technology Association X

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

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

X

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

BFTT T46D System Hardware Description and Operational Overview, Version P, 26 March 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+IPPD V1.3 or higher 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 IWS 1IT PAPM and the 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 COR, and the PCO prior to use.

Note 3: Copies of military handbooks, instructions, standards and specifications and DoD adopted non-Government standards may be obtained in accordance with the 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:

1. ASSIST database via the Internet at https://assist.dla.mil/

2. DoD issuances (http://www.dtic.mil/whs/directives/)

3. DoN issuances (http://doni.dla.mil/default.aspx)

4. PEO IWS documents (Please email Michelle.A.Greene@navy.mil)

5. By submitting a request to the

Department of Defense Single Stock Point (DoDSSP) Building 4, Section D 700 Robbins Avenue Philadelphia, PA 19111-5094

6. Naval Systems Data Support Activity (NSDSA) website at:

https://www.navsea.navy.mil/nswc/porthueneme

7. DoD Information Technology Standards Registry; https://disronline.csd.disa.mil/a/

8. ITS Portal – https://nserc.nswc.navy.mil/its (Requires an account)

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

Note 4: Document Precedence

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

EIA/IS-632 X

IEEE 1220 X

IEEE Std 24765:2010 X

C.3.0 STATEMENT OF WORK

C.3.0.1 Section C Contents Table

SOW Section Applicable CLINs

3.1 Program Management Common Across All CLINs

3.2 Systems Engineering, Design, Development, Implementation, Test, and Support

Level Of Effort: CLIN 0001, and if Exercised 0007, 1001, 1007, 2001, 2007, 3001, 3007, 4001, 4007 and CLINs in support of Level of Effort 0003, 0004, and if Exercised 1003, 1004, 1006, 2003, 2004, 2006, 3003, 3004, 3006, 4003, 4004, 4006

3.3 Production Production of BEWT II Systems if Exercised 0005, 1005, 2005, 3005, 4005

3.6 Government Furnished Material Storage Storage 0006, and if Exercised 1006, 2006, 3006, 4006

C.3.1 Program Management (Applicable to all CLINs)

The Contractor shall perform program management functions to ensure all the requirements are met. The Contractor management functions include, but are not limited to, manage and maintain DD Form 1423 to ensure compliance with development and delivery requirements; maintain information liaison with all stakeholders; track and maintain records of direction and authorization from Contracting Officers Representative (COR), Alternate Contracting Officers Representative (ACOR), Program Management Office (PMO), Procuring Contracting Officer (PCO) and Administrative Contracting Officer (ACO); development and tracking of cost data as a management element of the program; inspection and test records; provide and maintain a quality management system; maintain auditable records of all costs charged to this contract; manage production flow to ensure delivery requirements are met;

manage execution of the Technical Instructions; manage contract funding to ensure that appropriations are expended in an allowable manner and Limitation of Funds and Cost Clauses are followed; manage data call responses; maintain and keep account for all GFP and GFI to ensure records and disposition are accurate; and ensure management practices as necessary to execute this contract in a cost effective and professional manner.

C.3.1.1 Contractor Communication The Contractor shall communicate to the COR and document its plans, processes and approaches to meet all program and contract requirements. The Contractors 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, A012)

3.1.1.1 The Contractor shall provide support to the Integrated Product Team (IPT) structure documented in the Government furnished Systems Engineering Plan (SEP) (Attachment J-03). The Contractor shall provide a Systems Engineering Management Plan (SEMP) that integrates with the IWS 1IT SEP (Attachment J-03). (CDRL A024)

3.1.1.2 The Contractor shall update the Government furnished PEO IWS 1.0 Work Breakdown Structure (WBS), Attachment J-05, and include WBS assignments in the Integrated Program Management Report (IPMR) (IMS) (CDRL A013) and the Technical portion of the monthly report (CDRL A001).

3.1.1.3 The Contractor shall deliver the Contractor’s current Configuration Management Plan (CMP) (CDRL A041) 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 (CDRL A023). The principle use is to provide the Government a basis for review, evaluation and monitoring of the CM program and its proposed components.

3.1.1.4 The Contractor shall develop, tailor, maintain and deliver to the Government an Integrated Master Schedule (IMS) (CDRL A013) for each separately funded developmental TI executed and all funded production CLINs along with the associated Technical Data Packages (TDP) (CDRL B001).

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 two (2) weeks of contract award.

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) 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 (CDRLs A022) and presentation materials delivered IAW (CDRLs A021). 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 A022) 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 CDRL A021, 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.

The Contractor shall:

Submit TIM Agendas and any read ahead documents (CDRL A021);

Publish meeting minutes for each IPT meeting (CDRL A022);

C.3.1.3 Integrated Digital Data Environment

The Contractor shall utilize the secure Integrated Training Systems (ITS) 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 ITS Portal 2010 Quick Reference Guide (Attachment J-06). No CLASSIFIED information, documents, software code, or other data shall be loaded to or saved on the ITS portal.

The Contractor shall provide e-mail notification to addressees (see Exhibit A) within five (5) days of when a deliverable is posted or updated.

All items posted by the Contractor to the ITS 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.

C.3.1.4 Contract Security Requirements

The Contractor shall maintain an active facilities security clearance and safeguarding of CLASSIFIED materials up to Secret and maintain certification by Defense Security Service (DSS) for the development, receipt, shipment, handling and storage of classified and FOUO marked hardware, software, and documentation as required in support of this contract. The information required to develop and test electronic warfare training systems includes library models and entities classified Secret. The production and repair of systems includes GFE maintenance, handling and de-militarization of hard drives containing classified and FOUO software and data.

The Contractor shall comply with the requirements of the DD 254 (Attachment J-07), for implementation of and to ensure proper safeguarding of classified materials, events and processes, also including proper unclassified documentation designation and marking per the Security Classification Guide (SCG). This shall include documentation developed by the Contractor or received in support of working groups and IPTs.

The Contractor shall ensure personnel coming in contact with; developing and designing; repairing, maintaining and updating; or handling classified material, data, or hardware, hold a valid SECRET clearance.

C.3.1.5 Cyber Security

The Contractor shall ensure the system design and engineering processes employed in system design include Cyber Security (CS) and Information Assurance (IA) considerations as delineated in the technical reference documents table, marked for incorporation (Section C.2.1), correctly implemented in the systems hardware and software.

Reference documents identified in Section C.2.1 table can be downloaded from the http://iase.disa.mil website.

The Contractor shall remain up to date on changes to cyber security guidance and be prepared to implement updated policy and guidance. If it is determined that a change in guidance will impact the system or software design, or other contract deliverables, the Contractor shall notify the PCO, COR, and IWS 1IT within thirty (30) days of determination.

The Contractor shall develop and deliver CS related deliverables as required in the Technical Instructions (TI).

Examples include, but not limited to:

1. IA Defense-in-Depth Architecture Diagrams for the system under development, and updates to the sub-network and platform network diagrams into which the system will be integrated

2. List of IA validation and test procedures performed by the Offeror to verify that the stated IA requirements have been met; (validation and test results should be made available upon request)

3. IA Residual Risk Assessment

4. IA Risk Mitigation Plan

5. IA test objectives and plans

6. Results of DISA Gold Disk Scans

7. DISA SRR Scripts, or e-Eye Retina Scans, as appropriate

8. Results of IA test procedures and validation procedures

(CDRLs A031, A032, A033, A034)

C.3.2 Systems Engineering, Design, Development, Implementation, Test, and Support (Level Of Effort)

C.3.2.1 Safety

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. (CDRL A042)

Systems Engineering tasking will be directed by the Government through the use of TIs as defined in Section H Clause “NAVSEA 5252.242-9115 TECHNICAL INSTRUCTIONS.”

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

6. Surface Electronic Warfare Team Trainer (SEWTT),

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

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

9. AOEW/Countermeasures

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

3.2.2.1 SEWTT, Surface Electronic Warfare Team Trainer, 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.2.2.2 BEWT, The Battleforce Electronic Warfare Trainer, 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.2.2.3 CIAT, the Combined Integrated Air and Missile Defense (IAMD) and Anti-Submarine Warfare (ASW) Trainer, will train 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.2.2.4 Countermeasures include AOEW, Electronic Attack and Advanced Off-board Electronic Warfare (AOEW) 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.2.2.5 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.2.3 Design and Implementation (Applicable to CLINs 0001, and if exercised 1001, 2001, 3001, 4001) The Contractor shall, adhering to the PEO IWS Technical Review Manual (TRM) – Tailored 13 February 2013 (Attachment J-02), 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; pursue 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 assessing 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-01). 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.

(CDRLs A004, A005, A006, A007, A008, A009, A010, A011, A014, A015, A016, A017, A018)

The Contractor shall develop and deliver a Program Plan (PP) (CDRL A012) for each development TI executed.

(e.g. SEWTT, BEWT II, CIAT, and AOEW/Countermeasures). The PPs shall describe the specifics of how the requirements will be executed, monitored, scheduled, and controlled.