N00024-17-R-5392-0002.pdf

N0002417NR42131

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

The purpose of this ammendment is to update Solicitation N00024-17-R-5392. The Solicitation is updated as follow s:

1. CONTRACT ID CODE PAGE OF PAGES

S 1 95

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

16C. DATE SIGNED

BY 19-Jul-2017

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 N0002417R5392

X 9B. DATED (SEE ITEM 11)

19-Jun-2017

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 is extended, X 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 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

19-Jul-2017

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:

N0002417R5392

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

The following have been modified:

SECTION B NOTES

NOTE A – The Contractor may earn a schedule incentive in accordance with Section B clause entitled

“DETERMINATION OF SCHEDULE INCENTIVE FOR ITEM 0001.”

NOTE B – Funds are currently not available. Award will not be made until appropriated funds are made available.

NOTE C – Offeror shall complete the "Price Group" and "Estimated Total Price" blocks of each data item on the

Contract Data Requirements List(s), attached hereto.

NOTE D – Option item to which Section I FAR clause 52.217-7 OPTION FOR INCREASED QUANTITY –

SEPARATELY PRICED LINE ITEM (MAR 1989) (NAVSEA VARIATION I) (SEP 2009) (Applicable to Fixed

Price Options) or FAR 52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)

(NAVSEA VARIATION)(APR 2015) (Applicable to Cost Reimbursable Options) applies and which is to be supplied only if and to the extent said option is exercised.

NOTE E – RESERVED

NOTE F – The Government will not exercise CLIN 1003 without previously or concurrently exercising CLINs 1001 and 1002. If Option CLIN 1003 for HELIOS Lot #1 Production is exercised, Non-Recurring Engineering CLIN

1001 and Long Lead Material CLIN 1002 will be subsumed into CLIN 1003. For administrative purposes involving moving obligations and expenditures, the Government may, at its discretion, move the CLIN 1001 and 1003 requirements under CLIN 1002 and convert CLIN 1002 to a Fixed Price Incentive Firm Target (FPIF) line item for

HELIOS Lot #1 Production requirements as follows:

- CLIN 1002 Target Cost will become the combined CLIN 1001 Target Cost, CLIN 1002 estimated cost, and

CLIN 1003 Target Cost;

- CLIN 1002 Target Profit will become the combined CLIN 1001 and CLIN 1003 Target Profits;

- CLIN 1002 Ceiling Price will become the combined CLIN 1001 and CLIN 1003 Ceiling Prices; and

- CLIN 1002 will incorporate CLIN 1003 share ratios.

In the event of subsumption, Long Lead Material shall be considered Contractor Furnished in accordance with the

Section H special contract requirement entitled "SUBSUMPTION OF MATERIAL ITEMS 1002 AND 2002."

Profit on Long Lead Material may only be earned if Option CLIN 1003 is exercised and Long Lead Material is subsumed.

NOTE G – RESERVED

NOTE H – Stepladder Pricing, See Attachment J-24, Stepladder Pricing Option Template.

For all option CLINs with stepladder pricing, (CLINs 1002, 1003, 2002, 2003, 3003) the Government may unilaterally exercise a given line item more than once prior to the latest option exercise date identified in clause FAR

52.217-7 (see Section I). Option CLINs with stepladder pricing may be exercised until the total quantity purchased equals the maximum quantity listed for that option CLIN in Section B.

If any line item is exercised more than once within a 90 day period from the date the Option was initially exercised, the unit price of the CLIN shall be adjusted downward to reflect the appropriate stepladder unit price for the entire quantity purchased within that 90 day period and funds will be realigned, as necessary.

The following hypothetical example illustrates how pricing will be adjusted for option CLIN 0000 if the line item is unilaterally exercised more than once within a 90 day period:

CLIN 0000

Stepladder Quantity Unit Price

100-200 $150

201-300 $120

301-400 $100

Upon first exercise of option, $22,500 is obligated to subline item (SLIN) 0000AA to provide funds to acquire a quantity of 150 units at a unit cost of $150.

150*$150 = $22,500

Upon second exercise of an additional 200 units within 90 days, $12,500 is obligated to SLIN 0000AB to provide funds to acquire a total quantity of 350 units at a unit cost of $100.

350*$100 = $35,000

Following exercise of our first two options for CLIN 0000, our contract CLIN structure for CLIN 0000 is as follows:

CLIN QTY SLIN UNIT COST EXTENDED PRICE FUNDED AMOUNT

0000 350 $100.00 $35,000 $35,000

0000 150 AA $150.00 $22,500 $22,500

0000 200 AB $62.50 $12,500 $12,500

NOTE J – The Government will only exercise Option Items 1003, 2003, and 3003 in a combination that will procure no more than nine (9) total Production units.

PRODUCTION CLIN EXERCISED NUMBER OF PRODUCTION UNITS PROCURED

Total Units Purchased (NTE 9) :

This note will be unilaterally updated by the Contracting Officer upon exercise of any Production options.

NOTE K – The Government will not exercise CLIN 2003 without previously or concurrently exercising CLIN 2002.

If Option CLIN 2003 for HELIOS Lot #2 Production is exercised, Long Lead Material CLIN 2002 will be subsumed into CLIN 2003. For administrative purposes involving moving obligations and expenditures, the Government may, at its discretion, move the CLIN 2003 requirements under CLIN 2002 and convert CLIN 2002 to a Fixed Price

Incentive Firm Target (FPIF) line item for HELIOS Lot #2 Production requirements. CLIN 2002 Target Cost will become the combined CLIN 2002 estimated cost and CLIN 2003 Target Cost and will incorporate CLIN 2003

Target Profit, Ceiling Price, and Share Ratios. In the event of subsumption, Long Lead Material shall be considered

Contractor Furnished in accordance with the Section H special contract requirement entitled "SUBSUMPTION OF

MATERIAL ITEMS 1002 AND 2002." Profit on Long Lead Material may only be earned if Option CLIN 2003 is exercised and Long Lead Material is subsumed.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

SECTION C - STATEMENT OF WORK

1. Overview

1.1. Background

The High Energy Laser with Integrated Optical-dazzler and Surveillance (HELIOS) project is focused on accelerating the fielding of laser weapon systems to the Fleet, with an incremental approach for increasing capability as laser technology continues to mature. HELIOS will leverage proven mature technology to field a 60-150 kW class High Energy Laser (HEL), along with an integrated Counter Intelligence, Surveillance, and Reconnaissance

(C-ISR) laser for non-destructive dazzling capability against UAV-mounted sensors. The HELIOS project will deliver weapon systems to the Fleet as quickly and affordably as possible, providing modularity where practicable for future capability enhancements.

HELIOS will initially deliver two test units in FY20 (one for a DDG 51 FLT IIA and one at a Land Based Test Site), and will provide options for additional units in FY21 and beyond. To meet accelerated program delivery timelines within fiscal constraints, HELIOS will prioritize technical maturity and proven laser weapon concepts.

The overall HELIOS architecture includes the Contractor Furnished Equipment (CFE) Laser Weapon System

(LWS) as well as Government Furnished Equipment (GFE) such as the Laser Weapon Control System (LWCS) and the Laser Fire Control System (LFCS) which contains the Deconfliction Safety System (DSS). The CFE LWS consists of all non-GFE components including, but not limited to, the laser source(s), beam transport, beam conditioning, beam director, imaging sensors, tracking algorithms, Power Conversion Module (PCM), and any additional energy or thermal management components needed to supplement ship services. The interface requirements that the CFE LWS must meet can be found in the following documents:

a. SNLWS-HME IRD-0005 (Attachment J-07)

b. SNLWS-CS PNT IRS-0003 (Attachment J-09)

c. SNLWS-LWCS IRS-0007 (Attachment J-10)

d. SNLWS-LFCS IRS-0006 (Attachment J-11)

e. SNLWS-PCM IRS-0004 (Attachment J-12)

1.2. Objective

The primary objective of HELIOS is to deliver an initial Laser Weapon System capability to the Fleet meeting all of the requirements referenced in Section 3 of this Statement of Work.

1.3. Scope

The requirements in this SOW pertain only to the CFE LWS portion of the overall HELIOS architecture. The scope of the work to be performed by the Contractor during the development of the initial Test Units includes all of the following: Systems Engineering; Design and Fabrication; System Integration; Land-Based system installation and checkout; Testing and Evaluation; as well as Production of Technical, Programmatic, Training, and Safety Data.

This SOW will include a base contract beginning with design work leading to various design reviews and culminating with system acceptance at the end of a Testing and Evaluation period.

Additionally, there are options for the Sustainment of the initial Test Units (Paragraph 3.2); Physical Configuration

Audits (Paragraph 3.3), Development and Manufacturing of Production Units (Paragraph 3.4-3.5); Sustainment of the Production Units (Paragraph 3.6); as well as Technical and Field Engineering Services (Paragraphs 3.7-3.9) and associated Travel (Paragraph 3.10). The Production Unit development and sustainment options include, but are not limited to, systems engineering, component design, fabrication, integration, test and evaluation, troubleshooting, and repair of damaged components. The Technical Engineering Services consist of additional technical studies and/or simulations requested by the Government to provide a better understanding of HELIOS operation, support design upgrades, and develop additional training material. The Field Service Engineering Services consist of installation of

HELIOS units along with initial setup, calibration, and checkout of each system.

2. APPLICABLE DOCUMENTS

2.1. Mandatory Documents

The following documents form a basis for the work to be performed under this SOW:

1. Top Level Requirements (TLR) for SEASABER, Included as Attachment J-02

2. SNLWS-SSD-0002, SNLWS System Scope Document (SSD) with Appendices, Included as Attachment

J-03

3. Department of Defense Security Classification Specification (DD-254), Included as

Attachment J-04

4. SNLWS Program Protection Plan, Included as Attachment J-05

5. SNLWS-SEPP-0001, SNLWS Systems Engineering Program Plan (SEPP), Version

1.0, included as Attachment J-06

6. SNLWS-HME IRD-0005, SNLWS Hull, Mechanical, and Electrical Interface

Requirements Document (HM&E IRD), Include as Attachment J-07

7. SNLWS-CS PNT IRS-0003, SNLWS Combat System Positioning, Navigation, and

Timing (CS PNT) Interface Requirements Specification (IRS), Included as Attachment

J-09

8. SNLWS-LWCS IRS-0007, SNLWS Laser Weapon Control System Interface

Requirements Specification (IRS), Included as Attachment J-10

9. SNLWS-LFCS IRS-0006, SNLWS Laser Fire Control System (LFCS) Interface

Requirements Specification (IRS), Included as Attachment J-11

10. SNLWS-PCM IRS-0004, SNLWS Power Conversion Module Interface Requirements

Specification (IRS), Included as Attachment J-12

11. A Beam Quality Metric for High Power Lasers, High Energy Laser Joint Technology

Office, dated 26 May 2016

12. SECNAVINST 5100.14D, Military Exempt Lasers, dated 18 Oct 2005

13. NAVSEAINST 9700.2, Integrated Topside Safety and Certification Program for

Surface Ships, dated 11 Sep 1998

14. Department of Defense Instruction (DODI) 8500.01, Cybersecurity, dated 14 Mar 2014

15. ISO/IEC 15408, Common Criteria v3.1. Release 4, dated Sep 2012

16. MIL-STD-31000A – Technical Data Packages, dated 26 Feb 2013

17. MIL-STD-882E – System Safety, dated 11 May 2012

18. NAVSEA S9310-AQ-SAF-010, Technical Manual for Batteries, Navy Lithium Safety

Program and Procedures, dated 19 Aug 2004

19. NAVSEAINST 9310.1C, Naval Lithium Battery Safety Program, dated 12 Aug 2015

20. MIL-HDBK-189C, Reliability Growth Management, dated 14 Jun 2011

21. PEO IWS / Naval Sea Systems Command Research & System Engineering Warfare

System Engineering and Human Systems Integration Directorate Technical Review

Manual (TRM), Version 2, dated 18 Dec 2009

22. OPNAVINST 5100.24B, Navy System Safety Program Policy, dated 06 Feb 2007

23. NAVSEAINST 5100.12B, Requirements For Naval Sea Systems Command System

Safety Program For Ships, Shipborne Systems And Equipment, dated 03 Aug 2011

24. SAE GEIA-STD-0007B, Logistics Product Data, dated 10 Feb 2014

25. MIL-STD-130N, Identification Marking of U.S. Military Property, dated 17 Dec 2007

26. ANSI/EIA-748, Earned Value Management Systems, dated Oct 2006

27. MIL-STD-881C – Work Breakdown Structures for Defense Materiel Items, dated 03

Oct 2011

28. MIL-PRF-29612B, Training Data Products, dated 31 Aug 2001

29. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology

(IT), dated 12 Mar 2014

30. National Institute of Standards and Technology (NIST) Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems, dated Feb 2010

31. Subchapter III of Chapter 35 of Title 44, U.S. Code (aka "Federal Information Security

Management Act (FISMA) of 2008")

32. Committee on National Security Systems Instruction 1253, dated 27 Mar 2014, as amended

33. National Institute of Standards and Technology (NIST) Special Publication 800-53A

Rev 4, Security and Privacy Controls for Federal Information Systems and

Organizations, dated 18 Dec 2014

34. National Institute of Standards and Technology (NIST) Special Publication 800-18, Rev 1, Guide for Developing Security Plans for Federal Information Systems, dated

Feb 2006

35. IEEE Std. 12207, Systems and software engineering, Software life cycle processes, dated 2008

36. ISO/IEC/IEEE 15289, Systems and Software Engineering, Content of life-cycle information products (documentation), dated 2015

37. ASD-S1000D, Version 4.1, International Specification for Technical Publications

Utilizing a Common Source Data Base, dated 30 Sep 2009

38. MIL-STD-3034A, Reliability-Centered Maintenance (RCM) Process, dated 29 Apr

39. NAVSEA Hazardous Material Avoidance Process, T9070-AL-DPC-020/077-2, dated

28 Sep 2015

40. MIL-STD-1629A, Procedures for Performing a Failure Mode, Effects, and Criticality

Analysis (FMECA), 24 Nov 1980

41. OPNAVINST 5100.27B, Navy Laser Hazards Control Program, 02 May 2008

42. PEOIWSINST 4732.1, PEO IWS Element Certification Policy, dated 13 Nov 2012

43. PEOIWSINST 4730.1A, PEO IWS Combat System Certification Policy, dated 5 Jan

44. NAVSEAINST 9410.2A, Naval Warfare Systems Certification Policy, dated 24 Aug

45. MIL-D-23140D, Drawings, Installation Control for Electronic Equipment, 30 Apr 1992

46. Department of Defense Technology Readiness Assessment (TRA) Guidance, revised

13 May 2011

47. PEOIWSINST 5000.8, PEO IWS 2.0 Risk Management Policy, 13 Jan 2014

48. NAVSEAINST 5000.8, Naval SYSCOM Risk Management Policy, dated 21 Jul 2008

49. NAVSEAINST 9400.2A, NAVSEA Platform Information Technology-Control Systems Cybersecurity

Governance and Guidance, dated 20 Sep 2016

50. SECNAVINST 5239.22, Department of the Navy Cybersecurity Safety Program (CYBERSAFE), dated 15 Nov 2016

51. PEOIWSINST 5239.1, Surface Navy Combat System Cybersecurity, dated 31 May 2016

52. DoD AT Security Classification Guide (With Change 2), dated 19 May 2014

2.2. Guidance Publications

The following publications are available as guidance:

1. DoD Modeling and Simulation for the Acquisition Workforce, Version 1.0.1, dated Oct

2. SAE GEIA-HB-0007B, Logistics Product Data Handbook, dated 05 Jun 2007

3. DoDI 4140.67, DoD Counterfeit Prevention Policy, dated 26 Apr 2013

4. DoDI 5200.44, Protection of Mission Critical Functions to Achieve Trusted Systems and Networks (TSN), Change 1, dated 25 Aug 2016

5. SECNAVINST 4855.3C, Product Data Reporting and Evaluation Program, dated 27

Jun 2014

6. DOD Technical Implemntation Guide, Version 1.0, dated Nov 2016 (Classified Secret)

7. DOD Anti-Tamper Desk Reference, 2 nd

Edition, dated Apr 2017

8. MIL-STD-1472G, Human Engineering, dated 11 Jan 2012

9. Risk Management Guide for DoD Acquisition, 7th Edition (Interim Release), dated Jan

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

Research, Development, Test, and Evaluation (RDT&E), dated 28 May 2015

11. DoD Manufacturing Readiness Level (MRL) Deskbook,V2.4 dated Aug 2015

12. MIL-S-901D, Shock Tests, High Impact (HI) Shipboard Machinery, Equipment, and

Systems, Requirements, dated 17 Mar 1989 http://www.acq.osd.mil/chieftechnologist/publications/docs/TRA2011.pdf http://www.acq.osd.mil/chieftechnologist/publications/docs/TRA2011.pdf

13. MIL-STD-167-1A, Mechanical Vibrations of Shipboard Equipment, 02 Nov 2005

14. MIL-HDBK-2155, Failure Reporting, Analysis and Corrective Action Taken, 11 Dec

15. DoD Joint Software Systems Safety Engineering Handbook, dated 27 Aug 2010

16. NAVSEAINST 8020.6E, Department of the Navy Weapon Systems Explosives Safety

Review Board, dated 11 Mar 2008

17. NAVSEA SW020-AH-SAF-010, Weapons System Safety Guidelines Handbook, 01

Feb 2006

18. DoDI 5000.02, Operation of the Defense Acquisition System, dated 07 Jan 2015

19. MIL-HDBK-61A, Configuration Management Guidance, dated 07 Feb 2001

20. ANSI/EIA 649B, National Consensus Standard for Configuration Management, dated

01 Apr 2011

21. PEO IWS 2.0 Above Water Sensors Configuration Management Plan/Procedures, dated

30 Aug 2010

22. DoD Corrosion Prevention and Control Planning Guidebook for Military Systems and

Equipment, Spiral 4, 04 Feb 2014

23. DoD Diminishing Manufacturing Sources and Material Shortages (DMSMS)

Guidebook: A Guidebook of Best Practices for Implementing a Robust DMSMS

Management Program (SD-22), Jan 2016

24. North Atlantic Treaty Organization (NATO) Allied Ordnance Publication 52 (AOP-

52), Guidance on Software Safety Design and Assessment of Munition-Related

Computing Systems, Dec 2008

25. Deputy Assistant Secretary of Defense, Systems Engineering PPP Outline and

Guidance, Version 1.0, Jul 2011

26. MIL-HDBK-470A, Designing and Developing Maintainable Products and Systems, Volume I, 04 Aug 1997

27. MIL-HDBK-1390, Level of Repair Analysis, 29 Jan 2015

28. MIL-HDBK 29612/1A, Guidance for Acquisition of Training Data Products and

Services (Part 1 of 5 Parts), 31 Aug 2001

29. MIL-HDBK 29612/2A, Instructional Systems Development/Systems Approach to

Training and Education (Part 2 of 5 Parts), 31 Aug 2001

30. MIL-HDBK 29612/3A, Development of Interactive Multimedia Instruction (IMI) Part

3 of 5 Parts), 31 Aug 2001

31. MIL-HDBK-729, Corrosion and Corrosion Prevention Metals, 21 Nov 1983

32. NAVSEA Drawing No. STD-407-5291780 EMI Reduction, dated 12 Jul 1991

33. MIL-STD-1310H Shipboard Bonding, Grounding, and Other Techniques for

Electromagnetic Compatibility, Electromagnetic Pulse (EMP) Mitigation, and Safety, dated 17 Sep 2009

34. MIL-STD-461G Requirements for the Control Of Electromagnetic Interference

Characteristics of Subsystems and Equipment, dated 11 Dec 2015

35. MIL-STD-464C Electromagnetic Environmental Effects Requirements for Systems, dated 1 Dec 2010

36. SECNAVINST 5000.42, Department of the Navy Accelerated Acquisition for the

Rapid Development, Demonstration, and Fielding of a Capability, dated 22 Dec 2016

37. TS9090-310G, Navy Modernization Program Management and Operations Manual

(NMP-MOM), Appendix H, Alterations to Ships Accomplished by Alteration

Installation Teams Technical Specification, dated 12 Feb 2015

38. MIL-STD-2106, Development of Shipboard Industrial Test Procedures, dated 04 Jun

39. MIL-STD-810G, Environmental Engineering Considerations and Lab Tests, dated 1

Jan 2000

40. ASTM F1166-07, Standard Practice for Human Engineering Design for Marine

Systems, Equipment, and Facilities, dated 2013

41. ASQC Q9001-2015, Quality Systems-Model for Quality Assurance In-Depth, Development, Production, Installation, and Servicing

42. LaWS QRC Lessons Learned Final, dated December 2015

2.3. Precedence

In the event of a conflict between the documents listed in Section 2.1, Mandatory Documents, and Section 2.2, Guidance Publications, the documents in Section 2.1 shall take precedence. In the event of a conflict between the documents listed in Section 2.2, the Contractor shall contact the Government and the Government will adjudicate on a case-by-case basis.

3. Requirements

3.1. Test Unit Development (CLIN 0001)

The exit criteria for Test Unit Development (CLIN 0001) are as follows (details are provided in subsequent paragraphs in the SOW):

a. The Contractor shall create an A-Specification (CDRL A001) for HELIOS which meets the requirements in the SNLWS System Scope Document (SSD).

b. The Contractor shall develop a design for an HELIOS Test Unit that meets the

HELIOS A-Specification (CDRL A001) and Government Furnished Information

(GFI) SNLWS External (Mechanical, Electrical, and Logical) Interface

Requirements consisting of the LWCS IRS, LFCS IRS, CS PNT IRS, PCM IRS, and the HM&E IRD.

c. The Contractor shall design, fabricate, and deliver two (2) HELIOS Test Units with each unit consisting of a High Energy Laser Weapon System combined with a C-

ISR capability for countering UAS-mounted sensors.

d. The Contractor shall verify that the HELIOS Test Units meet the HELIOS A-

Specification (CDRL A001) and GFI HELIOS Interface Requirements listed in

Section 3.1.b.

e. The Contractor shall build, integrate, checkout, install at the Land Based Test Site, provide T&E support, and provide training material (CDRL A061) for the HELIOS

Test Units delivered under CLIN 0001.

f. The maximum amount of requirements shall be verified during Factory Qualification Testing (FQT) for both Test Units in accordance with the FQT Plan (CDRL A035) and FQT Procedures (CDRL

A036) prior to delivery to either the Land Based Test Site or pier-side.

g. The Contractor shall transport one (1) HELIOS Test Unit to the Land-Based Test

Site (LBTS) and perform all installation, alignment, and initial checkout procedures in accordance with the LBTS Requirements and Installation Plan (CDRL A039).

The Contractor shall deliver the Government approved Land Based System Test

Plan (CDRL A041), Operation Procedures (CDRL A038), and Test Report (CDRL

A040).

h. The Contractor shall transport one (1) HELIOS Test Unit to the pier-side location in accordance with Section F.

i. The Contractor shall have corrected all issues associated with Trouble Reports

(TRs) (CDRL A042) and implement all corresponding Revisions (CDRL A043)

(Subject to Government approval within the Local Configuration Control Board

(LCCB)).

j. The Contractor shall provide a final Reliability, Availability, Maintainability, and

Total Ownership Cost (RAMTOC) Model that reflects actual costs incurred during

Test Unit Development phase and clearly shows the relationship of Test Unit hardware costs to Production and future production costs. The RAMTOC Model shall be part of the Supportability Analysis (A058).

k. The Contractor shall close or have a Government-approved closure plan for all

Action Items (CDRL A003).

l. The Contractor shall deliver all required Contract Data Requirements Lists

(CDRLs) (Exhibit A) and receive Government approval for all approval CDRLs.

The Government will take ownership of both HELIOS Test Units once FQT and the Land Based Test Event have been completed along with delivery of the Ship-Based system pier-side in accordance with Section F. The two Test

Units shall be accepted at the same time once those conditions have been successfully satisfied.

3.1.1. Test Unit Development Overview

The purpose of the Test Unit Development is to develop a safe, affordable, and operationally useful system that meets the requirements specified in both this SOW and the SSD. The overall design of HELIOS shall ensure that all components including (but not limited to) electrical cables, plumbing, pressure vessels, batteries, chemicals, etc.

satisfy the safety, security, and installation requirements for a DDG 51 FLT IIA surface combatant. Any use of refrigerant shall be minimized to the maximum extent possible and, if required, shall be contained within a local loop and not present in manned spaces. The components associated with the four (4) modules defined in the HM&E

IRD are not expected to be located in manned spaces. Additionally, HELIOS should be designed such that the failure of one or more laser modules or video sensors shall not result in the failure of the entire system, and, in as much as is practicable, should not compromise the mission.

3.1.2. Systems Engineering

3.1.2.1. System Engineering Technical Reviews (SETRs)

The Contractor shall host and participate in formal SETRs. The following is a list of the SETRs to be conducted under CLIN 0001. These reviews shall be event driven and predicated upon satisfying the SETR Entrance Criteria.

a. System Requirements Review (SRR)/System Functional Review (SFR), chaired by the Government

b. Preliminary Design Review (PDR), chaired by the Government

c. Critical Design Review (CDR), chaired by the Government

d. Factory Qualification Test Readiness Review (TRR), chaired by the Government

e. Land Based TRR, chaired by the Government

Outside of the event-driven reviews listed above, less formal Design Disclosure Meetings (DDMs) will occur on a bi-monthly (every other month) basis through delivery to facilitate an accelerated schedule. The Government may decide to change the frequency of the DDMs as necessary. The Contractor shall host and participate in these DDMs, which shall sufficiently address the engineering material and documentation to convey a detailed understanding to the Government technical team. Component and subsystem details (including how they fit into the overall laser weapon system architecture), all design changes, risks, Test Observation Reports (TORs), and other important design related data shall be delivered in the Engineering Design Notebook (EDN) (CDRL A006). The DDMs will be used by the Government to review design decisions, provide recommendations on the path forward for procurement actions, and adjudicate comments in preparation for the PDR and CDR. Additionally, these meetings will include Program Management discussions as necessary to account for cost, schedule, technical, and/or any outstanding issues.

The Contractor shall post the draft PDR documents to the Government Integrated Digital Environment (IDE) at least

30 days prior to the scheduled event and the Government will provide review comments back to the Contractor at least 14 days prior to the scheduled event. The Contractor shall post the draft CDR material to the Government IDE at least 45 days prior to the scheduled event and Government personnel will provide review comments back to the

Contractor at least 20 days prior to the scheduled event. All final presentation materials (CDRL A002) shall be placed on the Government IDE.

To support HELIOS development, the Contractor shall provide Government personnel with local (a terminal) and remote access to all of the unclassified and classified documentation, analysis, Modeling and Simulation tools, software development environment, and software builds pertaining to HELIOS for Government review and inspection.

The Contractor shall recommend all reviews (scheduling, location, security requirements, agenda and content), subject to Government approval. The content along with the entrance and exit criteria of the reviews will be tailored from the Program Executive Office for Integrated Weapons Systems (PEO IWS)/Naval Sea Systems Command

Research & System Engineering Warfare Systems (SEA 05) Technical Review Manual (TRM) and included in the

SNLWS Systems Engineering Program Plan (SEPP). Additionally, for each SETR the Technical Review Action

Plan (TRAP) will be updated as necessary and provided as Government Furnished Information (GFI) 75 days prior to the event to describe the plan for a particular SETR and refine the entrance and exit criteria. Unless otherwise stated, the Contractor shall place read ahead material and Presentation Material (CDRL A002) on the Government

IDE one week prior to each review. The Contractor shall place final Presentation Materials on the Government IDE following the reviews. The Contractor shall prepare Minutes (CDRL A003) to include a database to capture and manage all Government and Contractor Action Items from the reviews. The database shall reside on the Government

IDE. The Contractor shall update Action Item status including closure plans weekly.

3.1.2.2. Systems Engineering Management

The Contractor shall ensure all system requirements, their functional allocation and verification are accounted for with full traceability to the SNLWS Systems Scope Document (SSD). A requirements traceability analysis database, either Dynamic Object Oriented Requirements System (DOORS), or compatible with DOORS, shall be maintained, to which the Government has full access. The data shall be provided to the government by the last day of each month, or after a major revision on the Government IDE. The data shall be provided in a format that can be easily imported into the government DOORS database without loss of fidelity.

The Contractor shall ensure all architecture data, their functional allocation and verification are accounted for with full traceability to the SNLWS Systems Scope Document (SSD). An architecture database, either Magic Draw, or compatible with Magic Draw (MaigcDraw 18.X; Meta Object Facility Core Specification MOF 2.4.1

<http://www.omg.org/spec/XMI/>; Eclipse Modeling Framework (EMF) UML2 (v5.x) XMI File; Enterprise

Architect UML 2.1 XMI 2.1 File), shall be maintained, to which the Government has Government Purpose Rights to all data. The data shall be provided to the Government as part of the Engineering Design Notebook (EDN) (CDRL

A006) by the last day of each month, or after a major revision. The data shall be provided in a format that can be easily imported into the government Magic Draw database without loss of fidelity.

3.1.2.2.1. Systems Engineering Planning and Execution

The Contractor shall generate, maintain, and execute the Systems Engineering Master Plan (SEMP) (CDRL A007) in accordance with the GFI Systems Engineering Program Plan (SEPP). The SEMP shall address the HELIOS program through production of the Production Units. The SEMP shall describe how a fully integrated engineering effort will be managed and conducted. The plan shall provide details of the flow of requirements from the

Government’s SSD to the Contractor’s design documents. In addition, the SEMP shall include Technical

Performance Measures (TPMs) as identified in the SSD.

3.1.2.2.2. Integrated Product and Process Development

The Contractor shall form Integrated Product Teams (IPTs) and Working Groups (WGs) to support an integrated product development process. The Contractor shall generate the organizational structure and document it in the

SEMP (CDRL A007). The Government will assign representatives to participate in IPT/WG meetings to ensure a collaborative and streamlined environment where the Contractor and Government are working in parallel for design, development and integration. Government participation will be coordinated through the Contracting Officer’s

Representative (COR).

The Contractor shall host IPT/WG meetings and Technical Interchange Meetings (TIMs), with these meetings being coordinated with the Government. The Contractor shall coordinate and post information on the Government IDE including Meeting Agendas, Presentation Materials (CDRL A002), and Meeting Minutes / Action Items (CDRL

A003).

In addition to the IPTs/WGs for the Contractor Furnished Equipment (CFE), the list below represents proposed

Government / Industry teams in which the Contractor shall participate. The teams will be established and led by the

Government based on the architecture of the proposed system. The technology working groups will meet informally to provide updates on the program, system design and development, and provide rationale for requirements to aid in design decisions.

a. Platform Integration Working Group (PIWG) is established to manage and maintain the requirements and interfaces with the ship Hull, Mechanical, and Electrical

(HM&E) systems as well as manage and mitigate the topside environment including the Electromagnetic Environment (EME) and Radar Cross Section (RCS).

The PIWG is anticipated to meet monthly in the Washington, DC area with teleconferencing available. Personnel involved in this review process may be required to sign non-disclosure agreements and firewall their efforts and participation from vendor/company internal R&D efforts [as directed by the

Procurement Contracting Officer (PCO) and/or COR].

b. Laser Weapon System Working Group (LWSWG) is established to manage the requirements and interfaces involved with the laser weapon system. This will include the components to acquire and track a target; the HEL module(s); the non-destructive C-ISR laser module(s); the beam transfer system; the beam director; and http://www.omg.org/spec/XMI/ the ability to assess engagement effectiveness. LWSWG is anticipated to meet monthly in the Washington, DC area with teleconferencing available. Personnel involved in this review process may be required to sign non-disclosure agreements and firewall their efforts and participation from vendor/company internal R&D efforts [as directed by the Procurement Contracting Officer (PCO) and/or COR].

c. Test and Evaluation Working Group (TEWG) is established to manage the requirements, facilities, schedule, targets, and instrumentation required to successfully complete Factory Qualification Testing, Land-Based Testing and planning for any applicable Sea-Based Testing. The TEWG will discuss expectations and capabilities for Factory Qualification Testing as well as interface and support equipment requirements for the Land-Based test event. The TEWG is anticipated to meet quarterly in the Washington, DC area with teleconferencing available. In support of the test program, the TEWG will also organize Scenario

Working Groups to support Scenario Certification for requirement verification and will require contractor support.

d. Product Support Working Group (PSWG) is established to ensure that a highly capable system is affordable by coordinating the supportability analysis, RAMTOC model development, and affordability assessments for HELIOS. The PSWG will establish RAMTOC model assumptions, evaluate life cycle cost metrics, and monitor the Cost and Earned Value on the contract. The PSWG will also interface with the other IPTs. The PSWG will coordinate with the contractor to ensure that sustainment of the system meets all requirements throughout the period of performance. The PSWG is anticipated to meet quarterly in the Washington, DC area with teleconferencing available.

e. System Safety Working Group (SSWG) is established to study and manage system and software safety issues. The Government will identify a HELIOS Principal For

Safety (PFS) who will interface with the Contractor System Safety Lead (SSL).

The SSWG is anticipated to meet quarterly in the Washington, DC area with teleconferencing available.

3.1.2.2.3. Modeling and Simulation Plan

The Contractor shall generate, maintain, and execute the Modeling and Simulation (M&S) Plan as part of the SEMP

(CDRL A007). DoD Modeling and Simulation for the Acquisition Workforce, Version 1.0.1, dated October 2008, is available as guidance. The M&S Plan shall address the development of Models & Simulations (CDRL A008) for

HELIOS and the use of Models & Simulations to support development, System/Subsystem Testing, Land-Based

Testing, and production of the Production Units. All M&S developed under this effort shall be delivered to the government. The Government will approve M&S use prior to System/Subsystem Testing and LBTS Testing.

The M&S Plan shall describe the computing environment necessary for each Model & Simulation such that delivered code can be hosted and run at equivalently configured Government computing sites. The M&S Plan shall describe how the HELIOS system will be integrated and used with Models & Simulations for design, evaluation, and test.

The following shall be addressed in the M&S Plan:

a. HELIOS system power interface model that accurately represents HELIOS's stability, inrush current, and ramp rate, from the perspective of the ship power interface to HELIOS during start up, shut down, and mode transitions (e.g., Laser

Firing);

b. HELIOS thermal interface model that accurately represents HELIOS’s flowrate, pressure drop, and waste heat load (heat-to-liquid and heat-to-air) during different modes (Standby, Firing, etc);

c. Optical modeling;

d. Mechanical modeling such as shock and vibration; and

e. Radar Cross Section (RCS)

The Contractor shall provide the Government with HEL and C-ISR system performance data that will allow the

Government to produce a lethality assessment through the Government owned and operated Effectiveness Tool Box

(ETB). At a minimum, this data for both the HEL and C-ISR lasers shall include:

a. Laser power out of the aperture;

b. Wavelength of the laser;

c. Diameter of the aperture / sub-aperture;

d. Diameter of any central obscuration (if applicable);

e. Laser beam quality (M

f. Estimate of wavefront error through the beam director;

g. Overall system jitter; and

h. Power-in-the-Bucket Measurement (PIBM)

The Contractor shall provide the above HEL and C-ISR Performance Data (CDRL A070) as a High Energy Laser

Consolidated Modeling Engagement Simulation (HELCoMES) input file which contains measured or best-estimate inputs for the laser weapon system, including the tracking and adaptive optics systems (if applicable). The

Contractor shall provide measured data for normalized Power-in-the-Bucket (PIB) for both the laser subsystem and overall weapon system.. The laser beam quality and PIB measurements shall be made in accordance with the High

Energy Laser Joint Technology Office (HEL JTO) document A Beam Quality Metric for High Power Lasers, Dated

26 May 2016.

The Contractor shall provide the Government with accurate performance data for the imaging sensors (CDRL A071) and associated optics used on HELIOS that will allow the Government to assess the system’s imaging capabilities.

This data shall be in the form of a Night Vision – Integrated Performance Model (NV-IPM) software input deck(s)

(*xml files).

For accurate modeling purposes, the Government reserves the right to use and modify conditions such as atmospheric transmission to model system behavior in various scenarios. Throughout the development effort, the

Government will use all provided information and the results of the M&S as part of an evaluation of the HELIOS capabilities.

3.1.2.2.4. Risk Management and Reporting

The Contractor shall generate, maintain, and execute the Risk Management Plan (RMP) as part of the SEMP (CDRL

A007) for the HELIOS program through Production. The Contractor shall implement and maintain a risk management program in accordance with the approved RMP to identify and manage risks associated with achievement of the program’s technical (including performance), cost, and schedule requirements. Risks shall be reported to the Government during IPT/WG meetings, Design Disclosure Meetings (DDMs) and SETRs. Risk management and reporting shall be in accordance with PEOIWSINST 5000.8 (PEO IWS 2.0 Risk Management

Policy) and NAVSEAINST 5000.8 (Naval SYSCOM Risk Management Policy). Risk Management Guide for DoD

Acquisition, 7th Edition (Interim Release), dated Jan 2017 is available as guidance.

The Contractor shall capture risks and associated mitigation plans in a risk database and provide status updates for all documented risks in the Engineering Design Notebook (EDN) (CDRL A006).

3.1.2.3. Program Protection Implementation Plan (PPIP)

The Contractor shall develop and deliver a Program Protection Implementation Plan (PPIP) (CDRL A009) through

Test Unit production, in accordance with the SNLWS Program Protection Plan (PPP) and the Navy Laser Weapon

Systems and Technology Security Classification Guidance (SCG); The Contractor shall also use the following documents as guidance: DoDI 5000.02, DoDI 4140.67, DoDI 5200.39, DODI 5200.44, and SECNAVINST

4855.3C.

The PPIP shall address program protection requirements outlined in Sections 2 through 11 of the PPP, including identification of Critical Program Information (CPI) and Mission Critical Functions (CF) and Components (CC), risk assessment, and identification of potential countermeasures. The PPIP shall, at a minimum, include the following information:

a. Description of Security Management Structure;

b. Identification of CPI (Organic, and Inherited if applicable);

c. Description of Criticality Analysis (CA) to be performed, and subsequent identification of CFs/CCs

d. Identification of CPI physical locations under the Contractor’s or Subcontractors’ control;

e. Identification of the countermeasures to be implemented at each site where CPI is held;

f. Special handling procedures required for CPI, and procedures for recovering CPI in the event of a mishap;

g. Identification of risk mitigation techniques to counter threats to the Contractor’s supply chain; and

h. Procedures for ensuring compliance with U.S. Government export statutes and regulations.

3.1.2.3.1. HELIOS Cybersecurity

To ensure successful integration with Sea-based and Land-based platforms, the Contractor shall implement cybersecurity processes and procedures in accordance with:

a. Subchapter III of Chapter 35 of Title 44, U.S. Code (aka "Federal Information Security Management

Act (FISMA) of 2002");

b. NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal Information

Systems (Feb 2010, as amended);

c. Committee on National Security Systems Instruction (CNSSI) 1253 Security Categorization and

Control Selection for National Security Systems (27 Mar 2014, as amended);

d. NIST SP 800-53A, Assessing Security and Privacy Controls in Federal Information Systems and

Organizations: Building Effective Assessment Plans;

e. DoDI 8500.01, Cybersecurity;

f. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology;

g. Information Assurance (IA) Technical Authority (TA) Standards;

h. NAVSEA 9400.2-M, PIT-Control System Cybersecurity Implementation Manual;

i. SECNAVINST 5239.22, Navy Cybersecurity Safety Program (CYBERSAFE);

j. PEOIWSINST 5239.1, Surface Navy Combat System Cybersecurity

The Contractor shall establish appropriate administrative, technical, and physical safeguards to protect any and all

Government systems and data, to ensure the confidentiality, integrity, availability, authentication, and non-repudiation of Government data. This shall include provisions for personnel security, electronic security, and physical security. In accordance with the SNLWS Cybersecurity Strategy, the HELIOS program will require an

Authority to Operate (ATO) for the deployed afloat system and land-based system, and Interim Authority To Test

(IATT), if required, to support Test and Evaluation (T&E) events during development.

The Contractor shall generate, maintain and execute an SNLWS System Security Plan (SSP) (CDRL A010), using the SNLWS Cybersecurity Strategy (CSS), SNLWS Program Protection Plan (PPP), and NIST SP 800-18 (Guide for Developing Security Plans for Federal Information Systems as guidance). The SSP shall provide a mechanism to identify and resolve implementation issues related to this effort’s Information Technology (IT), including National

Security Systems (NSS), infrastructure support and IT and NSS interface requirements. The SSP shall identify and address the cybersecurity strategy for technical exchange of information as well as the strategy to address

TEMPEST and Emission Security or Emanations Security (EMSEC). Cybersecurity technical reference documents can be downloaded from the DISA IASE website at http://iase.disa.mil/stigs/Pages/index.aspx.

The Contractor shall also develop and deliver the following cybersecurity-related information in the SSP:

a. Cybersecurity Control Requirements Traceability Matrix to include tailored-out controls;

b. STIG Applicability Review and Report (including Security Requirements Guides

(SRG) and Security Checklists);

c. Assessment & Authorization (A&A) Plan and which includes Defense-in-Depth

Architecture Diagrams for the system, the sub-network, and platform network into which the system will be integrated. The A&A Plan shall also include

Cybersecurity Test Objectives and Plans, and Cybersecurity T&E procedures/results to verify the system works as designed, and that the stated

Cybersecurity requirements have been met.

d. Information Assurance (IA) Residual Risk Assessment and Mitigation Plan; and

e. System Security Administrator Operations Manual (SSAOM).

3.1.2.3.2. Anti-Tamper

The Contractor shall generate, maintain, and execute the Anti-Tamper (AT) Plan (CDRL A072) for HELIOS through Test Unit production. The AT Plan includes measures to protect Critical Program Information (CPI) defined by DoDI 5200.39 and DoDI S-5230.28; the Contractor shall also use the following documents as guidance:

DOD Technical Implementation Guide (Version 1.0, Nov 2016) and DOD Anti-Tamper Desk Reference (2 nd

Edition, Apr 2017).

The Contractor shall follow all requirements of the DoD AT Security Classification Guide (Change 2 of 19 May

2014), the Navy Laser Weapon Systems and Technology Security Classification Guidance (SCG), and the SNLWS

Program Protection Plan (PPP).

The AT Plan shall generally include a list of CPI, identified vulnerabilities, an analysis of AT methods that apply to

HELIOS, and an explanation of which AT method(s) will be implemented. The Anti-Tamper Plan shall, at a minimum, include the following information:

a. Contractor’s proposed HELIOS architecture;

b. Critical Protection Information (CPI) for the proposed architecture, and locations of

CPI in the architecture;

c. Identify impacts if CPI is exploited by an adversary;

d. Identify vulnerabilities of CPI in the proposed system;

e. Attack tree analysis;

f. Identify available AT techniques for HELIOS;

g. Identify potential AT solutions and AT architecture for HELIOS;

h. Key Management Plan to address Cryptographic requirements;

i. AT V&V Plan;

http://iase.disa.mil/stigs/Pages/index.aspx

j. Anti-Tamper development schedule, including SETRs, AT TIMs, and T&E events;

and

k. AT implementation cost

3.1.2.4. System/Subsystem Specification (A-Specification)

HELIOS shall meet all requirements in the GFI SNLWS System Scope Document (SSD). The Contractor shall develop and maintain the HELIOS System/Subsystem Specification (SSS) (A-Specification) (CDRL A001).

The Contractor shall perform required analyses, modeling and simulation, functional allocation, and flow down of requirements from the SNLWS System Scope Document (SSD) to the HELIOS A-Specification (CDRL A001). In addition, the A-Specification shall capture requirements based on the PPIP (CDRL A009) and the SSP (CDRL

A010). The A-Specification shall include a traceability matrix with rationale that traces each requirement in the A-

Specification to the requirement in the SSD. Each requirement within the A-Specification (CDRL A001) shall contain a verification statement consisting of the verification method, objective, environment, and success criteria.

3.1.2.5. Hardware Specification (B2-Specification)

The Contractor shall generate and maintain HELIOS Hardware Specifications (B2-Specifications) (CDRL A011) for each hardware CI.