W15QKN21R0025.pdf

SOLICITATION, OFFER AND AWARD 1. This Contract Is A Rated Order Under

DPAS (15 CFR 700)

Rating Page of Pages

2. Contract Number 3. Solicitation Number 4. Type of Solicitation 5. Date Issued 6. Requisition/Purchase Number Sealed Bid (IFB)

Negotiated (RFP)

7. Issued By Code 8. Address Offer To (If Other Than Item 7)

NOTE: In sealed bid solicitations ‘offer’ and ‘offeror’ mean ‘bid’ and ‘bidder’.

SOLICITATION

9. Sealed offers in original and copies for furnishing the supplies or services in the Schedule will be received at the place specified in item 8, or if handcarried, in the depository located in until (hour) local time (Date).

Caution - Late Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

10. For Information A. Name B. Telephone (No Collect Calls) C. E-mail Address

Call: Area Code Number Ext.

11. Table Of Contents

(X) Sec. Description Page(s) (X) Sec. Description Page(s)

Part I - The Schedule Part II - Contract Clauses A Solicitation/Contract Form I Contract Clauses

B Supplies or Services and Prices/Costs Part III - List Of Documents, Exhibits, And Other Attach.

C Description/Specs./Work Statement J List of Attachments D Packaging and Marking Part IV - Representations And Instructions E Inspection and Acceptance K Representations, Certifications, and F Deliveries or Performance Other Statements of Offerors G Contract Administration Data L Instrs., Conds., and Notices to Offerors H Special Contract Requirements M Evaluation Factors for Award

OFFER (Must be fully completed by offeror) NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within _____ calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. Discount For Prompt Payment 10 Calendar Days (%) 20 Calendar Days (%) 30 Calendar Days (%) Calendar Days (%) (See Section I, Clause No. 52.232-8)

14. Acknowledgment of Amendments (The offeror acknowledges Amendment No. Date Amendment No. Date receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

15A. Name and Code Facility 16. Name and Title of Person Authorized to Sign Offer Address of (Type or Print) Offeror

15B. Telephone Number 15C. Check if Remittance Address is 17. Signature 18. Offer Date Area Code Number Ext. Different From Above – Enter such

Address In Schedule

AWARD (To be completed by Government)

19. Accepted As To Items Numbered 20. Amount 21. Accounting And Appropriation

22. Authority For Using Other Than Full And Open Competition: 23. Submit Invoices To Address Shown In Item

10 U.S.C. 2304(c)( ) 41 U.S.C. 253(c)( ) (4 copies unless otherwise specified)

24. Administered By (If other than Item 7) Code 25. Payment Will Be Made By Code

26. Name of Contracting Officer (Type or Print) 27. United States Of America 28. Award Date

(Signature of Contracting Officer)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION Standard Form 33 (Rev. 9-97) Previous edition is unusable Prescribed By GSA-FAR (48 CFR) 53.214(c)

W15QKN-21-R-0025

X

2021AUG23

2021NOV2204:00pm

DOA5

2021AUG23 SEE SCHEDULE

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

ANGELICA M. MERINO

(973)724-7422

CCNJ-SL

ANGELICA.M.MERINO.CIV@MAIL.MIL

1 121

X 1

X 4 X 8

X 27 X 33 X 34

X 40

X 42

X 43

X 75

X 76

X 93

X 113

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: ANGELICA M. MERINO

Buyer Office Symbol/Telephone Number: CCNJ-SL/(973)724-7422

Type of Contract 1: Firm Fixed Price

Type of Contract 2: Time and Materials

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

Program: Remote Weapon Systems (RWS)_______

Description: This contemplated effort will continue procurement of new-system and spare-part production, engineering services,___________ sustainment, and product integration, to support current and future requirements of the Common Remotely Operated Weapons Station (CROWS) a varient of Remote Weapon Systems (RWS). The program will also support new and emerging customer requirements to include the CROWS variants such as Abrams CROWS-Low Profile (LP), Navy Mk-50, and United States Marine Corps (USMC) Amphibious Remote Weapon Station

(ARWS) and Stryker M151 conversion to RWS. This solicitation will result in single award.

Ceiling Amount: $1,498,061,956.94______________

Minimum Guarantee: First Article Test (FAT) Non-Recurring Expenses (NRE) for the First Article Testing (FAT) and four systems of each_________________ configuration; CROWS M153 (Tan), CROWS M153A2E1 Low Profile (TAN) and CROWS M153A4 (Green). Spare parts in the amount of $3,500,000.

If the FAT is waived following award, an equivalent dollar value of units will be ordered instead.

Solicitation Number: W15QKN-21-R-0025

Contracting Officer: Stephanie G. Kless

Contract Specialist: Angelica M. Merino

Security Level: Unclassified; however, a DD254 is required as classified information may be generated under this contract.______________

The following markings apply to the Technical Data Package and all associated drawings:

NOTICE TO ACCOMPANY THE DISSEMINATION OF ATTACHED CROWS TYPE 2 TECHNICAL DATA

Including: Export Control Warning, Tech Data License Rights, DoD Distr. B, & Proper Destruction/Final Disposition Notice

To obtain documents with a limited distribution, offerors are required to submit a fully executed Non-Disclosure and Non Use Agreement, and AMSTA-AR 1350 - Technical Data Request Questionnaire and a DD 2345 Military Critical Technical Agreement (certified current by the

U.S. and Canada Joint Certification Office (JCO)), all of which are attachments to this Request for Proposal (RFP). Requests for this information should be sent to the POC on this RFP.

EXPORT CONTROL WARNING - This document contains technical data whose export is subject to the Arms Export Control Act (Title 22, U.S.C.,_______________________

Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

SPECIAL LICENSE RIGHTS; Contract No. W15QKN-07-D-0018 Contractor Name: Kongsberg Defence & Aerospace Co. Contractor Address: Kongsberg______________________

3601, Norway. The Government's rights to use, modify, reproduce, release, perform, display, or disclose these technical data are restricted by Special License Agreement No. 1, of Contract W15QKN-07-D-0018. This CROWS Type 2 Technical Data may be disclosed to and used only by the U.S. Government, and any non-US Government recipients who have executed the Use and Nondisclosure Agreement appended to

Special License Agreement No. 1, with such disclosure and use restricted solely to the CROWS program purposes stated therein. Any reproduction of technical data or portions thereof marked with this legend must also reproduce the markings.

DISTRIBUTION STATEMENT B. Distribution authorized to U.S. Government Agencies only, to protect information not owned by the U.S.________________________

Government and protected by the contractor's "Special License Rights" defined within Special License Agreement No.1. Other requests for this data shall be referred to U.S. Army Picatinny Arsenal, NJ 07806, Attn: SFAE-SDRCSW, (attn: Remote Weapons System Division, Project

Manager Soldier Lethality, Picatinny Arsenal, New Jersey 07806-5000).

GENERAL INFORMATION TO OFFERORS OR QUOTERS__________________________________________

1. Responses must set forth full, accurate and complete information as required by this solicitation (including attachments). Fill-ins

2 121

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

are provided on Standard Form (insert form numbers), and other solicitation documents. Examine the entire solicitation carefully. The penalty for making false statements is prescribed in 18 U.S.C. 1001.

2. Responses must be plainly marked with the Solicitation Number and the date and local time set forth for bid opening or receipt of proposals in the solicitation document.

3. Information regarding the timeliness of response is addressed in the provision of the solicitation entitled either Late Submission, Modification and Withdrawal of Bid or Instructions to Offerors Competitive Acquisitions.

4. Procurement Information:

( X) This Procurement is unrestricted

5. Issuing Office:

U.S. Army Contracting Command New Jersey

ATTN: Angelica M. Merino

Office Symbol: ACC-NJ-SL

Picatinny Arsenal, NJ 07806-5000

Email: angelica.m.merino.civ@mail.mil

6. Point of Contact for Information:

Name: Angelica M. Merino

Title: Contract Specialist

Email: angelica.m.merino.civ@mail.mil

Or

Name: Stephanie G. Kless

Title: Contracting Officer

Email: stephanie.g.kless.civ@mail.mil

DISCLOSURE OF UNIT PRICE INFORMATION____________________________________

This constitutes notification pursuant to Executive Order 12600, Pre-Disclosure Notification Procedures for Confidential Commercial

Information (June 23, 1987), of our intention to release unit prices in response to any request under the Freedom of Information Act, 5

USC 552. Unit price is defined as the contract price per unit or item purchased. We consider any objection to be waived unless the contracting officer is notified of your objection to such posting prior to submission of initial proposals.

**Note: Foreign Military Sales (FMS) Orders will not have an applicable DO Rating.

*** END OF NARRATIVE A0001 ***

3 121

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 Ordering Periods

B.1.1 This is a Firm-Fixed Price (FFP), Indefinite Delivery-Indefinite Quantity (IDIQ), five year contract. Each Line Item Number (LIN) within the delineated ordering periods below can be awarded multiple times during the stated ordering period. The ordering periods will be as follows:

Ordering Period 1 = 12 months from the date of contract award.

Ordering Period 2 = 12 months from the end of Ordering Period 1.

Ordering Period 3 = 12 months from the end of Ordering Period 2.

Ordering Period 4 = 12 months from the end of Ordering Period 3.

Ordering Period 5 = 12 months from the end of Ordering Period 4.

B.1.2 The Government may award a LIN multiple times within an ordering period for quantities up to the highest range quantity. However, the quantity range does not limit the number of items the Government may order in a given ordering period. The total quantity ordered for any given item could be more than the items highest quantity range.

B.2 LINs

B.2.1 First Article Test (FAT). (See Attachment 0016 Exhibit E)

B.2.1.1 LINs 0001 to 0004 are for the systems to be used for FAT, based on a FFP for 1 Lot of a quantity of up to 4 systems. This FFP shall include all preparation, packaging and marking requirements in accordance with ASTM D 3951-98, MIL-STD- 129, and any other packaging requirements.

B.2.2 LIN 0005 is for Contract Data Requirements Lists (CDRL). This LINs shall be Not Separately Priced (NSP) (See Exhibit A)

B.2.3 LIN 0006 is for Contractor Manpower Reporting (CMR). CMR shall be proposed on applicable orders in accordance with the contractor's cost accounting system.

B.2.4 LINs 1000 to 1001 are for Field Service Technicians (FST). (Offeror shall submit their pricing information on Attachment 0016

Exhibit B)

B.2.4.1 LIN 1000 is for CONUS FST Support, based on FFP hourly rate in Attachment 0016 Exhibit B. The hourly rates shall be fully loaded.

B.2.4.2 LIN 1001 is for travel associated with FST Support. This LIN will be incorporated on a case by case basis utilizing Time and

Material (T&M) LINs.

B.2.5 LIN 1100 is for Engineering Services. This LIN includes labor categories to be used for NRE efforts, based on FFP hourly rates in

Exhibit C. The hourly rates shall be fully loaded. This LIN also includes material and travel cost that will be proposed, evaluated and negotiated on a Task Order basis. (Offeror shall submit their pricing information on Attachment 0016 Exhibit C)

B.2.6 LINs 2000 through 2013 are reserved for Remote Weapon Systems (RWS) systems, and shall be proposed on a Firm Fixed Price (FFP) basis. This FFP shall include all preparation, packaging and marking requirements in accordance with ASTM D 3951-98, MIL-STD- 129, and any other packaging requirements. (Offeror shall submit their pricing information on Attachment 0016 Exhibit D)

B.2.7 LINs 3000 through 3009 are reserved for RWS Kits, and shall be proposed on a Firm Fixed Price (FFP) basis. This FFP shall include all preparation, packaging and marking requirements in accordance with ASTM D 3951-98, MIL-STD- 129, and any other packaging requirements. (Offeror shall submit their pricing information on Attachment 0016 Exhibit F)

B.2.8 LINs 3100 through 3297 are reserved for Shop Replaceable Units (SRU), and shall be proposed on a Firm Fixed Price (FFP) basis.

This FFP shall include all preparation, packaging and marking requirements in accordance with ASTM D 3951-98, MIL-STD- 129, and any other packaging requirements. (Offeror shall submit their pricing information on Attachment 0016 Exhibit G)

B.2.9 LINs 4000 through 4364 are reserved for Line Replaceable Units (LRU), and shall be proposed on a Firm Fixed Price (FFP) basis.

This FFP shall include all preparation, packaging and marking requirements in accordance with ASTM D 3951-98, MIL-STD- 129, and any other packaging requirements. (Offeror shall submit their pricing information on Attachment 0016 Exhibit H)

B.2.10 LINs 5000 through 5050 are reserved for Kit Spares, and shall be proposed on a Firm Fixed Price (FFP) basis. This FFP shall include all preparation, packaging and marking requirements in accordance with ASTM D 3951-98, MIL-STD- 129, and any other packaging requirements. (Offeror shall submit their pricing information on Attachment 0016 Exhibit J)

B.2.11 LIN 5300 are for Depot Services. (Offeror shall submit their pricing information on Attachment 0016 Exhibit K)

4 121

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

B.2.11.1 LIN 5300 is for Depot Services, and shall be incorporated utilizing T&M LINs.

B.2.11.2 All labor, including prime and subcontractor, for depot services shall use LIN 5300, based on hourly rates in Attachment 0016

Exhibit K. The hourly rates shall be fully loaded.

B.2.11.3 For all Shop Replaceable Units included in Exhibit G, materials used for depot services, including prime and subcontractor effort, shall use FFP prices. (Offeror shall submit their pricing information on Attachment 0016 Exhibit G)

*** END OF NARRATIVE B0001 ***

5 121

PIIN/SIIN

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

0005 BASE CLIN FOR CDRL __________________

The below ELINs are associated with the Data Items on the Contract Data Requirements List (CDRL)(DD Form

1423), in Section J.

(End of narrative A001)

A001 CONTRACT DATA REQUIREMENTS LIST 1 LO $ ** NSP ** _______________________________ __________________

SERVICE REQUESTED: CDRL

CLIN CONTRACT TYPE:

Firm Fixed Price

This LIN applies to Exhibit A in Section J.

Contract Data Requirements Lists (CDRLs) are Not

Separately Priced (NSP).

Reference CDRL DD Form DD Form 1423.

(End of narrative B001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

DLVR SCH PERF COMPL

REL CD QUANTITY DATE ________ ______________ __________

001 1 SEE DD FORM 1423

0006 MANPOWER REPORTING 1 LO $ ** NSP ** __________________ __________________

SERVICE REQUESTED: MANPOWER REPORTING

Manpower Reporting rquirements apply to Exhibit B.

To be proposed on individual Task Orders basis IAW the Contractors Cost Accounting System. Applicable to

T&M LINs only.

Contractor Manpower Reporting (CMR): This shall be applicable for all ordering periods.

(End of narrative B001)

6 121

PIIN/SIIN

Page of

Name of Offeror or Contractor:

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Reference No. of Document Being Continued

MOD/AMD

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

DLVR SCH PERF COMPL

REL CD QUANTITY DATE ________ ______________ __________

001 1 UNDEFINITIZED

7 121

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

STATEMENT OF WORK

For

Remote Weapon Systems (RWS)

18 August 2021

C.1. SCOPE.

C.1.1. BACKGROUND. This Statement of Work (SOW) is for a family of remote weapon systems mounted on mobile or stationary platforms that are capable of mounting various small- to medium-caliber machine guns, missiles, rockets, and scalable non-lethal effects. The weapon system is typically externally mounted on the host platform; the target acquisition and engagement control capability is typically mounted inside the platform. The RWS provides the gunner with precise, stabilized remote weapon control and enhanced day/night target acquisition capabilities while allowing the gunner to be protected inside the platform or at a secure location.

C.1.2. The term RWS in this SOW refers to, and all requirements in this SOW are applicable to, all the configurations listed in specification GSPEC00008 (Attachment 0011) and all other applicable specifications, all items with a Contract Line Item Number (CLIN) /

Line Item Number (LIN) in Section B of this contract, and any other hardware or configuration developed or modified under this Contract.

C.1.3. GENERAL SCOPE. This SOW defines the work required to fabricate, test, and deliver systems to the Government in accordance with the various Specifications, this SOW, and associated product and data deliverables. The Contractor shall also provide engineering hardware, software, and services in support of future enhancements and integrations. The Contractor shall support and sustain the systems and recapitalize previously fielded systems for future fielding.

C.2. APPLICABLE DOCUMENTS.

C.2.1. GOVERNMENT DOCUMENTS.

C.2.1.1. GOVERNMENT STANDARDS.

- MIL-STD-129R; Military Marking for Shipment and Storage; 18 Feb 2014

- MIL-STD 130N; Identification Marking of U.S. Military Property; 16 Nov 2012

- MIL-STD-882E; Standard Practice for System Safety; 11 May 2012

- MIL-STD-31000A; Technical Data Packages; 05 Nov 2009

- AR 700-127; Integrated Product Support; 11 October 2016

- AR 725-50; Requisitioning, Receipt, and Issue System; 15 November 1995

- DOD Directive 8500.01E; Information Assurance; 23 Apr 2007

- DOD Instruction 8510.01; Risk Management Framework for DoD Information Technology; 24 May 2016

- AR 25-2; Information Assurance; 04 Apr 2019

- DOD Manual 5000.01-M-1; Cost and Software Data Reporting Manual; 04 Nov 2011

-MIL-STD-1472G, ISO 9241-11 and ANSI/HFERS 200

-IEEE/EIA 12207.0 and Army Regulation 381-12

-MIL-HDBK-338B and the FMECA should be IAW DI-SESS-81495A Failure modes

C.2.1.2. OTHER DOCUMENTS.

- GSPEC00008 DETAIL SPECIFICATION SYSTEM SPECIFICATION FOR ARMAMENT SUBSYSTEM, REMOTELY OPERATED: M153 COMMON REMOTELY OPERATED WEAPON

STATION (CROWS)

C.2.1.3. HANDBOOKS.

- MIL-HDBK-61A(SE); Configuration Management Guidance; 07 Feb 2001

- JSSSEH; Joint Software System Safety Engineering Handbook; 27 Aug 2010

(Unless otherwise indicated, copies of the above specifications, standards, handbooks, or publications are available from the

Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094. Any documents required by manufacturers in connection with specific acquisition functions should be obtained from the contracting activity or as directed by the

Procuring Contracting Officer (PCO).)

C.2.2. NON-GOVERNMENT DOCUMENTS.

- ISO/IEC 17025; General requirements for the competence of testing and calibration laboratories; 15 May 2005

8 121

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

- NCSL Z540.3; Requirements for the Calibration of Measuring and Test Equipment; 08 Aug 2006

- ANSI/EIA-649-C; National Consensus Standard for Configuration Management; 17 Jun 2011

- ISO 9001:2015; Quality Management Systems Requirements; 2015

- AS9100C; Quality Management Systems - Requirements for Aviation, Space and Defense Organizations; Jan 2009

- ISO/IEC/IEEE 42010-2011; ISO/IEC/IEEE Systems and software engineering -- Architecture description

C.3. REQUIREMENTS.

The SOW takes precedence over the respective Specifications. Conflicts between the respective Specifications and other sections of the contract shall be resolved by direction of the Contracting Officer. All timeframes shall be calendar days unless otherwise specified.

C.3.1. GOVERNMENT FURNISHED PROPERTY.

C.3.1.1. LICENSES, PERMITS, CLEARANCES. The Contractor shall obtain all licenses, permits, and clearances necessary to receive, use, and store Government furnished or loaned items. The Contractor shall also meet all Government requirements for secure storage of the same in accordance to FAR 52.223-4000 and DFARS 252.223-7007.

C.3.1.2. GOVERNMENT FURNISHED MATERIAL. Government furnished material shall be used only in conjunction with this contract and shall either be incorporated into deliverables or returned at completion of this contract.

-STORM PI, II AN/PSQ-23A,C for the 60201886-08

C.3.1.3. GOVERNMENT FURNISHED SOFTWARE. Government furnished software shall be used only in conjunction with this contract and shall either be returned or destroyed at completion of this contract.

-Firmware/SW listed in TDP comprehensive Software list.

C.3.1.4. GOVERNMENT FURNISHED INFORMATION. Government furnished information shall be used only in conjunction with this contract and shall either be returned or destroyed at the completion of this contract.

-System Safety Hazard Analysis Report

-Safety Assessment Report

-CSDR Plan

C.3.1.5. GOVERNMENT FURNISHED EQUIPMENT (GFE).

-GFE listed in Attachment 0001 GFP Schedule

C.3.1.5.1. The first provided RWS of each configuration is intended for complete tear down and inspection. Additional provided RWS are intended for operational experience and interchangeability testing. Deviations from these uses may be approved by the Government at its sole discretion.

C.3.1.5.2. Government furnished property shall only be used in conjunction with this contract, unless written permission is received from the Contracting Officer. Government furnished property shall be returned at the completion of this contract.

C.3.1.6. GOVERNMENT FURNISHED SOFTWARE/INFORMATION DEFICIENCY REPORT. Any and all deficiencies found on any Government furnished software or information shall be documented in detail in a Government Furnished Information Deficiency Report to be generated and submitted within 15 calendar days of the discovery of deficiency. The Contractor shall address all elements of the Government Furnished

Information Deficiency Report. (CDRL A001, DI-MGMT-80596, Government Furnished Information Deficiency Report)

C.3.1.7. QUALITY DEFICIENCY REPORT. Any and all deficiencies found on any Government furnished material or Government loaned property shall be documented in detail in a Quality Deficiency Report to be generated and submitted within 15 calendar days of the discovery of the deficiency. The Contractor shall address all elements of the Quality Deficiency Report. (CDRL A002, DI-QCIC-80736, Quality

Deficiency Report)

C.3.1.8. SHIPPING OR PACKAGING DISCREPANCY REPORT. Any and all shipping or packaging discrepancies found in the shipment of any

Government furnished material, Government loaned property, other Government shipments, or other shipments of Government property shall be documented in detail in a Shipping Discrepancy Report to be generated and submitted within 7 calendar days of the discovery of the discrepancy. The Contractor shall address all elements of the Shipping and Packaging Discrepancy Report. (CDRL A003, DI-MGMT-80503, Report of Shipping (Item) and Packaging Discrepancy)

C.3.2. HARDWARE/SOFTWARE SYSTEM REQUIREMENTS.

C.3.2.1. The Contractor shall produce, fabricate, test, and deliver RWS units to the Government per their respective Technical Data

Package (TDP). The hardware (with test software) delivered shall be a fully operational system and satisfy all the requirements of

9 121

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

GSPEC00008.

C.3.2.2. The Contractor shall produce, fabricate, test, and deliver accessory kits and spare parts for all line replaceable units, assemblies, and all individual parts to the Government per their respective TDP. The parts delivered shall satisfy all the requirements of GSPEC00008.

C.3.2.3. The Contractor shall convert RWS systems from the M151 or RWS configurations to any other feasible RWS configuration and test, and deliver to the Government. The parts delivered shall satisfy all the requirements of GSPEC00008 unless otherwise noted in this SOW.

C.3.2.4. The TDPs are provided to set the parameters within which the contractor shall build the RWS hardware. The Government does NOT warrant that all RWS built to the Technical Data Package will meet requirements or interface seamlessly with the provided software. The

Government only warrants that it is possible to build RWS, within the constraints of the Technical Data Package, which meet requirements. This is represented by the RWS provided to the contractor. The contractor shall be responsible for determining how to build RWS within the constraints of the Technical Data Package that (when combined with the provided software executable code) meet all requirements as outlined in this Statement of Work and the Detail Specification.

C.3.2.4.1. The delivered RWS shall integrate seamlessly with the existing provided RWS software executable code. The delivered RWS shall meet all Detail Specification and contract requirements when integrated with the existing RWS software executable code. Source code will not be disclosed to the contractor.

C.3.2.4.2. The delivered RWS shall be built within the constraints of the Technical Data Package, and the delivered RWS components shall be seamlessly interchangeable in both directions with all existing RWS components down to the lowest individual piece/part level.

C.3.2.4.3. The components of the delivered RWS when interchanged into an existing RWS in any combination shall not degrade the performance of the RWS.

C.3.2.4.4. The performance of the delivered RWS shall meet all requirements of the Detail Specification and this Statement of Work when any combination of components from any RWS is swapped in.

C.3.2.4.5. The contractor is responsible for the development of all test hardware and test software to ensure that all RWS systems, spares, kits, and components delivered under this contract meet all test requirements/specification of the delivered TDP.

C.3.2.4.6. Human Systems Integration (HSI): When designing, developing, or modifying hardware or software with which personnel must interact (e.g., control, view, hear, comprehend, supervise etc.), the contractor shall use Human Factors Engineering/Usability

Engineering design criteria and guidelines (e.g., MIL-STD-1472H, ISO 13407, ISO 9241-11, and ANSI/HFES 200) as guidance for the design of the hardware or software components. The contractor shall conduct Risk Assessments based on results of Usability tests, evaluations, or assessments of the hardware or software with which personnel must interact. The risks should relate to the HSI domains of Manpower, Personnel skills/qualifications, Training, Human Factors Engineering (a.k.a. Usability Engineering), Force Protection & Survivability, and Safety & Occupational Health (i.e., System Safety and Health Hazards). The contractor shall propose risk mitigation strategies to address the cost, schedule, and performance risks associated with human-system interaction issues; and the contractor shall propose mitigations to reduce risks to acceptable levels.

C.3.2.5. SOFTWARE.

C.3.2.5.1. Computer software means computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae, and related material that would enable the software to be reproduced, recreated, or recompiled. Computer software does not include computer databases or computer software documentation. Computer software in the context of this SOW also includes but is not limited to, configuration and data files; scripting; batch and command files; operating systems;

board support packages; firmware; device drivers for hardware interfaces to all subsystems; interfaces for inputs and outputs to other systems to include systems simulated for testing, training, and maintenance; and algorithms, computer simulators, model-based system designs used to auto-generate code, model-based logic designs used to auto-generate HDL, and previously developed software to include commercially developed software. Support software is made up of all software and technical data that are used for, or associated with, the generation, design, development, testing, integration, acceptance, execution, verification, and validation of the application software.

C.3.2.5.2. Runtime Licenses. The Contractor shall be responsible for acquiring and transferring to the United States Government (USG), the required runtime licenses for each RWS unit are provided in the TDP.

C.3.2.5.3. Government Provided Software.

C.3.2.5.3.1. The Government will provide software executable code to the contractor for the RWS. If there is a need to make a change that will affect software and/or firmware where the Government has provided the software executable object code, the contractor shall follow the following process:

C.3.2.5.3.2. Preliminary Engineering Change Proposal. The contractor shall submit a preliminary ECP as defined in section C.3.3.5.9.4

10 121

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

and provide adequate detailed technical, cost, and schedule information to support the needed change. The Government will use this as a basis for the design change decision. If the preliminary ECP is accepted by the Government, the contractor shall continue to the next section.

C.3.2.5.3.3. Detailed Planning. The contractor shall be responsible for producing and executing the detailed planning activities associated with the change. The Government will provide the contractor with estimated level-of-effort, and schedule information required to change the software executable object code in support of the contractors detailed planning activities.

C.3.2.5.3.4. Technical Information Interchange. The contractor shall provide all the technical data necessary in order for the

Government to make the changes to the software executable object code. The contractor shall supply the Government with necessary hardware assets to perform software development and testing. If requested, the contractor shall provide the Government with on-site technical support to facilitate using the provided hardware assets to perform software development and testing.

C.3.2.5.3.5. The contractor shall produce change management documentation and update the Technical Data Package in accordance with

C.3.3.5 to include any new software executable code part number and associated information and data provided by the Government.

C.3.2.5.4. Contractor Developed Software

C.3.2.5.4.1. The Government will act as Configuration Manager for RWS software. The Government may choose to utilize the Engineering

Services portion of this contract to have the Contractor develop software. Additionally, the Contractor may wish to develop and introduce software for the RWS through an Engineering Change Proposal (ECP) to incorporate new technologies or capabilities, enhance producibility, address obsolescence, etc.

C.3.2.5.4.2. The Contractor shall follow section C.3.3.5 when performing any changes to software items. The Government may choose to provide software source code to be used as a baseline for future software changes. Changes to software performed by the Contractor shall require the following additional tasks performed and CDRLs to be developed along with any software.

C.3.2.5.4.3. Software Project Planning and Management. The Contractor shall perform the software upgrade/maintenance project planning activities and software project management activities. The Contractor shall perform software quality management activities in accordance with IEEE/EIA 12207.0. The Contractor shall assess any proposed software changes against all respective Specification requirements and determine if these changes will impact the ability to meet any Specification requirements. The Contractor shall identify Mission

Critical, Reliability, and Safety Performance Characteristics (MRSC) for all RWS requirements for design impact and product quality assessment. The Contractor shall maintain a continuous bi-directional traceability of each RWS MRSC from the requirements specified at the respective Specification level to each primitive software requirement.

C.3.2.5.4.4. Software Collaboration. The Contractor shall collaboratively develop software with the USG Software Integration Lab (SIL) team under this contract throughout every stage of the development life cycle. The contractor shall be able to export/import software requirements, software design, software test, and software source code baselines with the USG SIL. The Contractor shall support a bi-weekly software collaboration meeting to cover software topics such as but not limited to: software requirements, software architecture/design, software version control, software test, software build and etc.

C.3.2.5.4.5. Software Development Environment - Software development environments include all hardware, software and supporting technical data used to upgrade/maintain, test and integrate the software as defined in the respective Specification Requirement

Document. The Software Development environment shall consist of all applicable materials defined in section C.3.2.5.1 The Contractor shall develop and deliver a Software Transition Plan (STRP). The Contractor shall purchase for and provide to the USG all development environments for USG SIL use. Site licenses necessary to use the environments in the USG Software SIL for software development, integration and test shall be acquired and provided to the USG. (CDRL A030, DI-IPSC-81429A, Software Transition Plan) and (CDRL A044, DI-

MCCR-80700, Computer Software Product End Items)

C.3.2.5.4.6. Software Design and Maintenance. The Contractor shall update and maintain a Unified Modeling Language (UML) model of the developed software. The Software Design shall define the nomenclature, source, data type, default value, and bounds of each data element and identifiable data structure output from or input to each and every component of the system. The Contractor shall provide the following deliverables:

C.3.2.5.4.6.1. Software Requirements Specification (SRS) - The Contractor shall maintain and provide an SRS. For each new requirement within the SRS, the Contractor shall document the Software Criticality Index (SwCI) level of the requirement and trace each requirement to the associated software function and component in the Software Design Description. The Contractor shall additionally trace the requirement to relevant test case(s), if applicable. (CDRL A031, DI-IPSC-81433A, Software Requirements Specification)

C.3.2.5.4.6.2. Interface Design Description (IDD) - The Contractor shall maintain and provide a Software IDD to support communications with any new Line Replaceable Units (LRUs). This document shall contain evidence of the Contractor's compliance with commercial standards in a table or matrix. (CDRL A032, DI-IPSC-81436A, Interface Design Description)

C.3.2.5.4.6.3. Architectural Description Document (ADD) - The Contractor shall maintain and provide an Architectural Description

Document (ADD) of the software architecture in accordance with (IAW) ISO/IEC/IEEE 42010-2011. In the ADD, the Contractor shall utilize

11 121

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Kruchten's methodology of "4+1" View Model of Software Architecture as a guideline. (CDRL A033, DI-IPSC-81435A, Software Design

Description (SDD))

C.3.2.5.4.6.4. Software Design Description (SDD) - The Contractor shall maintain and provide a SDD for newly implemented components. The

Software Design shall define the nomenclature, source, data type, default value, and bounds of each data element and identifiable data structure output from or input to each and every component of the system. (CDRL A034, DI-IPSC-81435A, Software Design Description)

C.3.2.5.4.6.5. Software Version Description (SVD) - The Contractor shall develop, maintain and provide a complete SVD for each Computer

Software Configuration Item (CSCI) for each upgrade of the software. Each SVD shall include changes and corrections made since the last

USG approved software version that the upgraded version is based on. (CDRL A004, DI-IPSC-81442A, Software Version Description)

C.3.2.5.4.6.6. Human Factors Engineering (HFE) The Contractor shall maintain and provide an HFE document describing the user interface to the system. (CDRL A049, DI-MISC-80508B, Technical Report Study/Services)

C.3.2.5.4.7. Software Testing. The Contractor shall perform the software test planning activities and generate the Software Test Plan

(STP) for the software. The Contractor shall perform software unit, engineering, and Formal Qualification Testing (FQT) at the CSCI.

C.3.2.5.4.7.1. Software Test Plan (STP) - The Contractor shall develop and deliver to the USG an STP. (CDRL A035, DI-IPSC-81438A, Software Test Plan)

C.3.2.5.4.7.2. Software Unit Level Test Description - The Contractor shall develop and deliver to the Government a Software Unit Test

Description. The Contractor shall trace unit/engineering-level tests that relate to safety significant (SWCI 1 -4) software requirements to provide confidence the safety critical code is properly implemented and is robust to error conditions. This document shall contain the compilation of all unit/engineering level testing that was performed for each software release. (CDRL A036, DI-IPSC-81439A, Software

Test Description (STD))

C.3.2.5.4.7.3. Software Unit Test Report. The Contractor shall develop and deliver to the Government a Software Unit Test Report. The test report shall contain the detailed information collected to verify and/or support empirical design data, design decision rationale, or defect resolution. This document shall contain the results of all unit/engineering level testing that was performed each software release. (CDRL A037, DI-IPSC-81440A, Software Test Report)

C.3.2.5.4.7.4. Software Test Description (STD) - The Contractor shall develop and deliver to the USG an STD. For Safety Critical

Software Requirement Specifications, the Contractor shall include tests that exhibit the appropriate Level of Rigor (LOR) as guided by

MIL-STD-882E, the JSSSEH and as guided by Software System Safety Implementation Process and Tasks Supporting MIL-STD-882E (JS-SSA-IG).

14 Mar 2018. For Software Requirement Specifications that require LOR-2 or LOR-1, the Contractor shall include boundary condition tests, stress tests and fault insertion tests in addition to requirements-based tests. (CDRL A038, DI-IPSC-81439A, Software Test Description)

C.3.2.5.4.7.5. Software Test Report (STR) - The Contractor shall develop and deliver to the USG an STR. (CDRL A039, DI-IPSC-81440A, Software Test Report)

C.3.2.5.4.7.6. Functional Code Analysis - The Contractor shall perform Functional Code Analysis of all non-testable requirements and deliver to the Government a Functional Code Analysis Report. (CDRL A006, DI-MISC-80711A, Scientific and Technical Reports)

C.3.2.5.4.8. Software System Safety Program (SSSP) - The Contractor shall conduct a Software System Safety Program using MIL-STD-882E and the JSSSEH as guidance. The SSSP shall fully support the System Safety Program. The SSSP shall include the necessary planning, coordinating, and engineering analysis to identify the safety significant functions (safety critical and safety related as guided by

Software System Safety Implementation Process and Tasks Supporting MIL-STD-882E (JS-SSA-IG). 14 Mar 2018) of the system and establish a protocol of analysis, design, test, and verification and validation for those functions within the software development activities and establish a software criticality assessment with a level of rigor protocol for the requirements, design, code, and test of safety-significant software functions.

C.3.2.5.4.8.1. Safety Code Review (SCR) - The Contractor shall execute a full SCR and update it as necessary to verify those requirements that cannot be tested during FQT. The Contractor shall give the Government 75 days advance notice of this review and facilitate Government witnessing. The SCR shall be based on any hazards addressed in the System Safety Hazard Analysis Report (SSHAR).

The Contractor will review software code vulnerabilities and provide software safety process code inspection evaluation, detailed code inspection, results and provide analysis and justification that the risks have been mitigated through the software design approach. The results shall be documented in a Safety Code Review Report. (CDRL A005, DI-MISC-80711A, Scientific and Technical Reports)

C.3.2.5.4.8.2. The Contractor shall perform a Software Functional Hazard Analysis (SwFHA) to identify and classify the system functions and the safety consequences of functional failure in accordance with Task 208 of MIL-STD-882E. The SwFHA shall include the rationale for the Software Control Category, severity level, and SWCI level of the listed functions. (CDRL A041, DI-MISC-80711A, Scientific and

Technical Reports)

C.3.2.5.4.8.3. For any new software code, the contractor shall mark safety significant code header with the appropriate SwCI assignment.

(CDRL A016, DI-SESS-80776A, Technical Data Package); (CDRL A040, DI-MCCR-80700, Computer Software Product End Items)

12 121

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.3.2.5.4.8.4. The Contractor shall support reviews, certifications, boards, and audits performed by or for the Government, to include preparing and presenting briefings and responding to requests for information, IAW Task 104 of MIL-STD-882E.

C.3.2.5.4.9. The Contractor shall furnish the Government with all technical data and assets described in section C.3.2.5 in (an) updated

Software Technical Data Package(s). (CDRL A040, DI-MCCR-80700, Computer Software Product End Items)

C.3.2.5.5. Government Software Integration Laboratory Availability. The Contractor may provide an RWS and/or production representative hardware/software to the Government in advance of any change for software risk mitigation or other purposes.

C.3.3. PROGRAM REQUIREMENTS. All meetings shall be conducted in English, and all documents and correspondence shall be written in

English.

C.3.3.1. PROGRAM MANAGEMENT.

C.3.3.1.1. The contractor shall maintain and provide an Integrated Master Schedule covering all aspects of this Statement of Work.

(A046, DI-MGMT-81650, Integrated Master Schedule (IMS))

C.3.3.1.2. The contractor shall maintain and provide a detailed Contract Work Breakdown Structure (CDRL A043, DI-MGMT-81334D, Contract

Work Breakdown Structure)

C.3.3.1.3. Security Requirements.

C.3.3.1.3.1. The Contractor will have access to Controlled Unclassified Information (CUI), and classified information up to the Secret level. The Contractor will be required to have a Secret facility security clearance with up to Secret safeguarding capabilities for receiving, generating and storing classified information, material, software, and hardware. Only U.S. Citizens are authorized to work on tasks involving classified information, material, or systems. Contractor personnel shall have a favorably adjudicated Secret security clearance, at minimum, prior to perform on this contract, and prior to access to classified information/material. The Contractor will have the appropriate level of investigation and security clearance for each site of performance of work. The Contractor will observe and comply with all security provisions in effect at each selected site. In performing this contract, the Contractor will be authorized to use the services of the Defense Technical Information Center (DTIC). Automated information system processing will be required at the

SECRET level at the Contractor's facility.

C.3.3.1.3.2. The Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified

Confidential, Secret, or Top Secret and requires contractors to comply with: the Security Agreement (DD Form 441); Contract Security

Classification Specifications (DD254); the National Industrial Security Program Operating Manual (DoD 5220.22-M); and any revisions to

DoD 5220.22-M, notice of which will be furnished to the contractor.

C.3.3.1.3.3. Information or data developed under this contract belongs to the Government. The Contractor will be required to comply with

DFARS SUBPART 204.73, SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT REPORTING. Contractor must obtain an External

Certificate Authority (ECA) certificate to access, encrypt, or transmit Controlled Unclassified Information (CUI) off installation.

Information regarding the External Certificate Authority can be found at http://iase.disa.mil/pki/eca/Pages/index.aspx .

Information for Department of Defense (DoD) Safe Exchange can be found at https://safe.apps.mil/ .

C.3.3.1.3.4. Random Antiterrorism Measures Program (RAMP) participation. Contractor personnel working on an installation are subject to participation in installation RAMP security program (e.g. vehicles searches, wearing of ID badges, etc.).

C.3.3.1.3.5. Contractor Personnel Who Require Access to Government Information Systems. All contractor employees with access to a government information system must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services and must successfully complete the DoD Information Assurance Awareness training prior to access to the information system and then annually thereafter.

C.3.3.1.3.6. Information Assurance (IA)/Information Technology (IT) Training. All contractor employees and associated subcontractor employees must complete the DoD Information Awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M, and AR 25-2 within six months of appointment to IA/IT functions.

C.3.3.1.3.7. Contractor will acquire and need to return all issued U.S. Government Common Access Cards, installation badges, and/or access passes upon contract completion, or termination from the contract.

C.3.3.1.3.8. Access and General Protection/Security Policy and Procedures. Contractor employees with an area of performance within an

Army-controlled installation, facility, or area, and all associated subcontractor employees shall provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of

Emergency Services, or Security Office. The contractor workforce must comply with all DoD, Headquarters Department of Army (HQDA), and/or local policy. Should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may

13 121

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

require changes in security matters or processes. During FPCONs Charlie and Delta, services may be discontinued/postponed due to higher threat. Services will resume when FPCON level is reduced to Bravo or lower.

C.3.3.1.3.9. For contractors requiring Common Access Cards (CAC). Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI/T1) or an equivalent or higher investigation in accordance with Army

Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD Federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the Federal Bureau of Investigation (FBI) fingerprint check and a successfully scheduled

NACI at the Office of Personnel Management (OPM).

C.3.3.1.3.10. For contractors that do not require a CAC, but require access to a DoD facility or installation. Contractor and all associated subcontractor employees shall comply with adjudication standards and procedures using the National Crime Information Center interstate identification index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility access and local security policies and procedures (provided by Government representative), or at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

C.3.3.1.3.11. Threat Awareness Reporting Program. All contractor employees with security clearances working on any Army contract must receive annual Threat Awareness and Reporting Program (TARP) training by a Counter Intelligence (CI) agent, or other authorized designated training method, per Army Regulation 381-12, para. 2-4b. TARP.