W91CRB18R0002_Amendment_0004.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

See SF 30 Continuation Page - Amendment 0004 Summary

1. CONTRACT ID CODE PAGE OF PAGES

S 1 37

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

16C. DATE SIGNED

BY 28-Nov-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 W91CRB-18-R-0002

X 9B. DATED (SEE ITEM 11)

20-Oct-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

28-Nov-2017

CODE

ACC - APG - W91CRB

4310 BOOTHBY HILL AVE

ABERDEEN PROVING GROUND MD 21005-3013

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W91CRB-18-R-0002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT 04 SUMMARY

SF Continuation Page:

1. Questions and Answers #3 has been added.

Section C SOW:

1. Paragraph 3.6 Realibility Testing has been updated.

QUESTIONS AND ANSWERS 3

Small Tactical Optical Rifle Mounted Micro-Laser Rangefinder II (STORM II)

Questions and Answers #3

48. Question: RFP: Requesting a fifteen (15) day extension to the proposed due date from 04 Dec 2017 to 19

Dec 2017.

Government Answer: Proposal due date will not be extended.

49. Question: SOW Section 3.6: “The Contractor shall conduct Reliability Qualification Testing (RQT) on the system(s) and as part of PQT, and on every production lot to verify continued compliance with the system reliability requirements.” Performance Specification Appendix A (Verification Matrix, Table 10), specification paragraph 3.9.1 indicates that reliability testing is to be completed annually. Please confirm that Reliability Testing is to be conducted as part of PQT and then annually per the performance specification and not on every production lot (monthly).

Government Answer: Section 3.6 of the STORM II is changed as follows:

3.6 Reliability Testing. The Contractor shall conduct Reliability Qualification Testing (RQT) on the system(s) as part of PQT and, as a minimum, on an annual basis to verify continued compliance with the system reliability requirements. Component level reliability testing shall only be required when system level testing is not being performed. The Contractor shall submit Production Reliability Acceptance Test (PRAT) reports for all reliability tests. Sampling of each lot shall be conducted IAW the approved QVM contained in the STORM II PS. The Contractor shall institute all necessary corrective actions to bring the systems/components into reliability compliance at no additional cost to the Government, to include all units delivered since the last previously successful reliability test as determined by the Government.

Demonstration of reliability compliance following institution of corrective actions shall be conducted by the Contractor at no additional expense to the Government.

50. Question: SOW Section 3.6: “Component level reliability testing shall only be performed during months when system level testing is not being performed.” Request the government clarify the intent of this statement.

Government Answer: The Government's intent is that should delivery of STORM II systems be completed on this contract and spares or contractor logistics support continue to be performed, components will be assembled into systems and reliability testing performed in order to continue qualification of the production line, as well as ensuring that the parts being sold as spares, or used in warranty and user damaged repair are still in compliance with contract requirements.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

The following documentation is provided for the solicitation for W91CRB-18-R-0002.

Recipients shall:

i. Read and comply with distribution markings.

ii. Direct all requests for distribution to other parties to Peter Buckless at peter.p.buckless.civ@mail.mil.

iii. Destroy the documents once they are no longer required to support this solicitation.

Recipients shall NOT: Redistribute the Statement of Work (SOW) outside of Distribution Statement A, of the program security classification guide, to include subsidiaries and subContractors within the corporate structure for this program.

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

Special Instructions:

1. This solicitation is for the procurement of Small Tactical Optical Rifle Mounted (STORM) micro Laser Range Finder (mLRF) II spares, associated data items, Contractor maintenance support, and COST support tasks.

2. This acquisition is being competed on a Full and Open competitive basis. The Government intends to award multiple Indefinite Delivery/Indefinite Quantity (ID/IQ) contracts on a Firm-Fixed Price (FFP) basis for a period of seven years (Fiscal Year (FY) 2018 – FY 2024).

3. The minimum quantity is 50 qualification STORM II systems (Contract Line Item Number (CLIN) 0001) (pursuant to Federal Acquisition Regulation (FAR) 52.216-22 INDEFINITE QUANTITY (October 1995).

DISTRIBUTION STATEMENT A: Approve for public release; distribution is unlimited.

Small Tactical Optical Rifle Mounted micro-Laser Range Finder (STORM II)

STATEMENT OF WORK (SOW)

1.0. Scope. This SOW specifies the tasks and efforts the Contractor shall perform during this qualification, and production contract for the Small Tactical Optical Rifle Mounted micro-Laser Range Finder (STORM II), associated ancillary equipment, and spare and repair parts. This SOW also establishes the program management, quality assurance, testing, logisitics, provisioning, configuration management, maintenance, and safety requirements for the items sought under this procurement. The Contractor shall ensure that the STORM II complies with the requirements of the contractual performance specification and the requirements listed under SOW Section 3.0 Requirements. Note also that items in bold refer to requirements for Contract Line Item Numbers (CLINs) that become requirements if/when ordered.

1.0.1. Contract Data Requirements List (CDRL). CDRLs have corresponding Data Item(s) Descriptions (DIDs), which provide specific instructions on Contractor deliverables. The Contractor shall comply with the SOW, the CDRLs, and the DIDs for this program.

2.0. Applicable Documents. The Contractor shall adhere to the following documents that form parts of this SOW to the extent specified herein. Unless otherwise specified, the latest revision of each document in effect at the time of solicitation release shall apply.

2.1 Government Documents. The following specifications, standards, and handbooks may be downloaded from the Army Publishing Directorate website at http://www.apd.army.mil/ and Acquisition Streamlining and Standardization Information System (ASSIST) website at: https://assist.dla.mil/online/start/.

DTR 4500.9-R Defense Transportation Regulation Part 2 May 2014

STORM SCG

Security Classification Guide (SCG) For AN/PSQ-23 & AN/PSQ- 23A & B Small Tactical Optical Rifle Mounted Micro-Laser Range Finder (STORM mLRF)

27 February 2013

Electro –Optic Counter Measure SCG

Security Classification Guide (SCG) for Electro-Optic Countermeasure Technology

05 November 2015

AR 190-51

Security of Unclassified Army Property (Sensitive and Nonsensitive)

30 September 1993

AR 381-12 Threat Awareness and Reporting Program 1 June 2016 AR 700-145 Item Unique Identification (IUID) 18 February 2016 AR-750-1 Army Material Maintenance Policy 20 September 2007 DoD 5220.22-M with Change 2

National Industrial Security Program Operating Manual 18 May 2016

STORM II FDSC

STORM II Failure Definition and Scoring Criteria (FDSC) (Not Final)

10 May 2005

MIL-DTL-14072F Finishes for Ground Based Electronic Equipment 13 August 2013

MIL-PRF-28800F

General Specification Test Equipment for Use with Electrical and Electronic Equipment

24 June 1996

MIL-STD-129R Military Marking for Shipment and Storage 18 February 2014 MIL-STD-130N with Change 1

Identification Marking of U.S. Military Property 16 November 2012

MIL-STD 461G

Requirements for the Control of Electromagnetic Interface Characteristics of Subsystems and Equipment

11 December 2015

MIL-STD-2073-1E with Change 1

Department of Defense (DoD) Standard Practice for Military Packaging

7 January 2011

MIL-STD-464C

DoD Interface Standard, Electromagnetic Environmental Effects Requirements For Systems

1 December 2010

MIL-STD-1839D Standard Practice for Calibration and Measurement Requirements 12 May 2010

MIL-STD-40051-2C

Preparation of Digital Technical Information for Interactive Electronic Technical Manuals (IETMs)

15 December 2015

MIL-STD-40051-2B

Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)

30 November 2012

MIL-STD-810G with Change 1

DoD Test Method Standard - Environmental Engineering Considerations and Laboratory Tests

15 April 2014

MIL-STD-881C Work Breakdown Structures for Defense Materiel Items 3 October 2011 MIL-STD-882E System Safety 11 May 2012

MIL-STD 961E (3) Notice 3 DoD Standard Practice - Defense and Program-Unique Specifications Format and Content

27 October 2015

MIL-STD-1425A

Safety Design Requirements For Military Lasers and Associated Support Equipment

30 August 1991

STORM II Performance Specification

Performance Specification- STORM II 26 April 2017

N/A DoD Guide for Achieving Reliability, Availability and Maintainability

3 August 2005

Non-Government Documents. Are found on Institute of Electrical and Electronics Engineers Standards Association (IEEE-SA), International Standards Organization (ISO), and Society of Automotive Engineers (SAE) International websites.

SAE GEIA-STD-0007B Logistics Product Data 1 MAY 2013 SAE GEIA HB-0007-B Logistics Product Data Handbook 1 February 2014

SAE GEIA-STD-0009

Reliability Program Standard for Design, Development and Manufacturing

1 August 2008

ANSI/NCSL-Z540.3- Requirements for the Calibration and Measurement of Test 26 March 2013

2006 (R2013) Equipment ASME Y14.5-2009 Dimensioning and Tolerancing 27 March 2009 SAE EIA-649-1 Configuration Management Requirements for Defense Contracts 1 November 2014

ISO/IEC/IEEE

15288:2015

Systems and Firmware Engineering – System Life Cycle Processes

15 May 2015

IEEE STD 15288.1-

IEEE Standard for Application of Systems Engineering on Defense Programs

10 December 2014

IEEE STD 15288.2-

IEEE Standard for Technical Reviews and Audits on Defense Programs

15 May 2015

IEEE STD 315-1975

(R1993)

Graphic Symbols for Electrical and Electronics Diagrams 2 December 1993

ISO 9001:2015 Quality Management Systems – Requirements 23 September 2015

ISO/IEC/IEEE DIS

24748-2-2012

Systems and Software Engineering - Life Cycle Management - Part 2: Guide to the Application of ISO/IEC 15288 (System Life Cycle Processes)

18 April 2012

ISO/IEC/IEEE DIS

24748-4.2-2016

Systems and Firmware Engineering Life Cycle Management – Part 4: Systems Engineering Planning

15 May 2016

ISO/IEC 26702:2007

Systems Engineering – Application and Management of Systems Engineering Process

15 July 2007

ISO 10012:2003

(R2009)

Measurement Management Systems - Requirements for Measurement Processes and Measuring Equipment

15 April 2003

3.0 Requirements and Description. The Contractor shall fabricate, test, and deliver STORM IIs and identified spares and repair parts In Accordance With (IAW) this SOW and the delivery schedule specified in individual delivery orders (DOs). The Contractor shall ensure that the delivered STORM II components comply with all of the requirements of the STORM II Performance Specification. The Contractor also shall provide maintenance and repair support for the STORM II system IAW the Contractor Maintenance Support Effort (CMSE) delineated in this

SOW.

NUMBER OF SYSTEMS EVENT

After Receipt of Order

(ARO) +

Contractor Qualification Testing (CQT) Test

Readiness Review ( TRR) 6 Months

Public Health Command (PHC) Health Hazard

Assessment (HHA) 10 Months

Survivability & Lethality Analysis Directorate

(SLAD)

10 Months

2 80% Technical Manual (TM)/Training Review 10 Months

Instructor & Key Personnel Training

(I&KPT)/Logistics Demonstration (LD)

10.5 Months

10 Government Qualificaiton Testing (GQT) TRR 12 Months

Chemical, Biological, Radiological, and

Nuclear Chemical Survivability Assessment

(CBRNCSA)

13 Months

Electromagnetic Capability

(EMC)/Electromagnetic Interference (EMI)

13 MONTHS

3.1 Systems Engineering. The Systems Engineering (SE) effort is for Qualification, CDRL-BBB, DID B001.

3.2 Systems Engineering Objective. The objective of systems engineering under this contract is to ensure the Contractor successfully tailors their systems engineering processes, documentation and plans then maps them to the lifecycle of STORM II.

3.2.1 Engineering Management Plan (EMP). The Contractor shall discuss how their integrated Engineering Management Plan describes the Contractor’s processes and resources to incorporate Systems Engineering (SE) practices to build, test, deliver and support the STORM II during the Qualification phase, see CDRL-BBB, DID B001. The Contractor shall use IEEE 15288.1:2014, Section 6.3.1.4, Project Planning Process Outputs, when developing the EMP. Guidance for EMP attributes and elements can be found in ISO 26702:2007 and ISO/IEC/IEEE DIS 24748-2. The Contractor shall discuss how the Contractor operates and conforms to IEEE 15288.2:2014 for technical reviews and audits. The EMP is a living document to be updated when technical plans change, systems engineering activities complete, existing technical risks are mitigated or substantially change, new technical risks emerge, and any reason that a significant change is needed to the Contractor’s approach. The Contractor’s updated EMP shall be delivered at Design Review. The EMP shall be updated during Production, if the delivery order is awarded. The EMP shall contain the following:

a. Discussion of main STORM II components and primary system sub-components.

b. Discussion of wireless components (wireless transceivers, wireless protocol, processor, algorithms).

c. System performance to be achieved for each device including Key Performance Parameters (KPPs), to include a system and component/sub-component power allowance table.

d. STORM II Interface/Interoperability with other equipment.

e. Contractor’s SE organizational integration (Technical, Quality & Test, Logistics), including sub-

Contractors.

f. Contractor’s SE approach to the following topics for the system and components/sub-components:

Reliability, Maintainability/Supportability, Chemical, Biological, Radiological, and Nuclear Chemical Survivability Assessment (CBRNCSA), Electromagnetic Interference (EMI), Safety/Environmental, Human Factors Engineering (HFE), Producibility, Quality & Test (Q&T), Training.

g. STORM II technical risk management (Technical, Schedule, Cost).

h. Application of Modular Open Systems Architecture (MOSA) principals incorporated into STORM II design.

3.2.2 General Requirements for Firmware Development and Support. The Contractor shall modify/develop firmware, conduct firmware testing, and update firmware documentation as required to meet the requirements of this contract. The Contractor shall ensure that the STORM II system with any new or modified firmware complies with all requirements of the STORM II Performance Specification. The Contractor shall also provide change engineering and implementation support as required. The following general tasks, not listed in order of priority, are required in order to provide firmware engineering support for STORM II. All firmware plans, procedures, development files, test data, and test reports shall be made available for review by the Government upon request. The Contractor shall maintain/update STORM II firmware documentation. The following are the minimum firmware documents the Contractor shall develop and maintain.

a. Firmware & Firmware Management Plan.

b. Firmware & Firmware Qualification Test Plan.

c. Firmware & Firmware Qualification Test Procedures.

d. Firmware & Firmware Qualification Test Report.

3.2.3 Firmware Development Methods. The Contractor shall use systematic and documented, methods and procedures consisting of safety, security, a library for configuration, and quality assurance for all firmware development and modification activities. These procedures shall be made available for Integrated Product Team (IPT) review.

3.2.3.1 Firmware Safety Assurance. The Contractor shall maintain and update a Firmware Management Plan (FMP), see CDRL-BBB, DID B001, by identifying as safety-critical those Critical Firmware Configuration Items (CSCI) or portions thereof whose failure could lead to a hazardous system state (one that could result in unintended death, injury, loss of property, or environmental harm). The Contractor shall update the safety assurance plan, including both tests and analyses, to ensure that the requirements, design, implementation, and operating procedures for the identified firmware minimize or eliminate the potential for hazardous conditions.

3.2.3.2 Security Assurance. The Contractor shall establish a security assurance plan in the FMP to minimize or eliminate the potential for breaches of system security due to firmware changes. As part of the required firmware products, the Contractor shall provide evidence that the security assurance plan has been implemented.

3.2.3.3 Firmware Development Library. The Contractor shall develop, maintain and control an STORM II Firmware Development Library to facilitate the orderly update and support of STORM II firmware. The Firmware Development Library shall be within the CDRL Library. The Contractor shall maintain a configuration management program for STORM II firmware IAW the EMP.

3.2.3.4 Firmware Quality Assurance. The Contractor shall maintain a Firmware Quality Assurance Plan and procedures for STORM II firmware, CDRL-BBB, DID B001. The Contractor shall implement and maintain firmware quality plan and procedures as defined in the STORM II EMP to include resources required, schedules, tasks to be performed, and the Contractor's firmware quality organization and interfaces.

3.2.4 Firmware Testing. The Contractor shall conduct testing, analysis, recording and analysis of firmware testing, see CDRL-EEE, DIDs E001, E002, and E003.

3.2.4.1 Firmware Test Environment. The Contractor shall maintain a firmware test environment to perform module level testing, unit level and integration testing, and formal qualification testing. The Contractor shall ensure that each element of the environment performs its intended functions.

3.2.4.2 Firmware Module Testing. If applicable, the Contractor shall perform firmware implementation and module testing on any new or modified firmware for the STORM II. The Contractor shall use well-defined, written procedures and standards as outlined in the STORM II FMP, to include any qualification test plans and procedures.

Test plans and procedures shall be updated as required to reflect firmware modifications. All test results and analysis shall be documented in a Firmware Test Report and shall be made available for review by the Government, see CDRL-EEE, DIDs E001, E002, and E003 (Test Procedures, Plans and Reports). Government reserves the right to preview test results prior to test report submission.

3.2.4.3 Firmware Integration Testing. The Contractor shall perform unit and integration testing on all firmware.

The testing shall be IAW the module and integration test cases and procedures. The Contractor shall make all necessary revisions to the firmware, perform all necessary retesting, and update the firmware development files and other firmware products as needed, based on the results of integration testing. The Contractor shall analyze the results of integration testing and shall record the test and analysis results in the firmware development files and firmware test report. The Contractor shall conduct regression testing to verify that modified code does not break existing tested functionality, and works within the requirements of the system. All test results and analysis shall be documented in the Firmware Test Report, see CDRL-EEE, DID E003. Government reserves the right to preview test results prior to test report submission.

3.2.4.4 Analyzing and Recording Computer Software Configuration Item (CSCI) Qualification Test Results. The Contractor shall analyze and record the results of CSCI Qualification Testing. The results shall include all applicable items in the Test Report see CDRL-EEE, DID E003 .

3.2.5 Hardware Configuration Item (HWCI) Integration and Testing. The Contractor shall conduct CSCI/HWCI integration and testing as required. The testing shall be IAW the CSCI/HWCI integration test cases and procedures.

The Contractor shall update test cases (in terms of inputs, expected results, and evaluation criteria), test procedures, and test data for conducting CSCI/HWCI integration and testing, as required. The test cases shall cover all aspects of the system-wide and system architectural design. The Contractor shall record firmware-related information in appropriate firmware development files and test reports, see CDRL-EEE, DID E001, E002, and E003. Government reserves the right to preview all results prior to test report submission.

3.2.6 STORM II Interoperability. The Contractor shall ensure that STORM II devices procured under this contract meet all contractual requirements. The Contractor shall describe STORM II is able to interface/interoperable with other equipment , see STORM Performance Specification (PS –STORM), weapon mounts (MIL-STD 1913 rail), Military Global Positioning System (GPS) devices such as Defense Advanced GPS Receiver (DAGR), etc.).

Additionally, at Post Award Conference (PAC) the Contractor shall submit a preliminary stage 2, DD1494 application for equipment frequency allocation for spectrum certification for the STORM II.

3.2.7 Participation in Technical Integrated Product Teams (IPTs). The Contractor shall participate in Government established IPTs with other Contractors to resolve technical issues to enable interoperability with family of weapon sights, fire control or Military GPS devices, if necessary, which may be procured from other sources.

3.2.8 Operational Security (OPSEC). The Contractor shall develop an OPSEC Standard Operating Procedure (SOP)/Plan within 30 calendar days of contract award (and updated annually thereafter), to be reviewed and approved by the responsible Government OPSEC officer. The Contractor shall use the provided STORM II Security Classification Guide (SCG) and the Electo-Optic Counter Measure SCG in developing the SOP/Plan. The SOP/Plan shall specify the Government’s critical information, why it needs to be protected, where it is located, who is responsible for it and how to protect it. In addition, the Contractor shall identify an individual who shall be an OPSEC Coordinator. The Contractor shall ensure that this individual becomes OPSEC Level II certified. The Government will evaluate Contractor OPSEC performance on an annual basis or as conditions warrant. The Contractor shall implement an employee verification process, whether through background checks or other similar processes, and provide a written response explaining how the verification process was completed and attest to the trustworthiness of the workforce, within 45 days of contract award. The Contractor shall comply with FAR 52.204- 2, Security Requirements. This clause involves access to information identified as “Confidential”, “Secret” or “Top Secret” and requires Contractors to comply with: (1) the Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); and (2) any revisions to the DoD 5220.22 or Contractor OPSEC Training. Per Army Regulation (AR) 530-1, Operations Security, new Contractor employees must complete Level I OPSEC training within 30 calendar days of their reporting for duty and all Contractor employees must complete annual OPSEC awareness training.

3.2.8.1 Level 1 Anti-terrorism (AT) Awareness Training. This standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area. All contractor employees, to include subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete Level 1 AT Awareness Training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the Contracting Officer Representative (COR) or to the contracting officer, if a COR is not assigned, within 30 calendar days after completion of training by all employees and subcontractor personnel. Level 1 AT Awareness Training is available at the following website:

http://jko.jten.mil

3.2.8.2 Access & General Protection / Security Policy & Procedures. This standard language is for contractor employees with an area of performance within Army controlled installation, facility, or area. Contractor and all associated sub-contractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DoD, Headquarters Department of the Army (HQDA) and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

3.2.8.3 Non-Common Access Card (CAC) Holders. For contractors that do not require CAC, but require access to a DoD facility or installation. Contractor and all associated sub-contractors 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 and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at Outside the Continental United States (OCONUS) locations, in accordance with status of forces agreements and other theater regulations.

3.2.8.4 iWATCH Training. This standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area. The contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity Anti-terrorism Officer (ATO)). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR No Later Than (NLT) 30 calendar days after contract award.

3.2.8.5 OPSEC Training. For contracts that require OPSEC Training. Per AR 530-1 Operations Security, the contractor employees must complete Level I OPSEC Awareness Training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter.

3.2.8.6 Classified Information. For contracts that require handling or access to classified information. 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— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); (2) any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

3.2.8.7 Threat Awareness Reporting Program (TARP). For all contractors with security clearances. Per AR 381-12 TARP, contractor employees must receive annual TARP training by a Counterintelligence (CI) agent or other trainer as specified in paragraph 2-4b.

3.3 Program Management Objective. The Contractor shall manage all aspects of the contract with respect to cost, schedule, system design, development, engineering, fabrication, configuration management, risk management, test and technical performance. The Contractor shall provide timely, programmatic, schedule and performance information to the Government throughout the life of the contract. The Contractor shall maintain a program management structure with a single point of contact for program oversight. The Contractor shall perform administrative, technical, business, and financial management functions during the course of this effort to include organizing, directing, and controlling actions, reporting status, recommending solutions, and resolving issues to ensure the successful execution of efforts needed to achieve contract objectives. The Contractor, at a minimum, shall implement processes for the following:

3.3.1 Program Planning, Management, and Control. The Contractor shall manage and participate in necessary business and administrative planning, test planning, organizing, directing, coordination, and approving actions designated to accomplish overall program objectives. The Contractor shall ensure that only technically qualified personnel with the proper security clearances and training support the program.

3.3.1.1 SubContractor and Contractor Management. The Contractor shall maintain a subcontract management program. The Contractor shall facilitate Government and subContractor discussions/activities as required by the Government.

3.3.2 Integrated Program Management Report (IPMR). The Contractor shall prepare and submit a monthly IPMR, see CDRL-AAA, DID A001, specifically providing Format 1, 5, and 6. Furthermore, the IPMR shall address the following subparagraphs.

3.3.2.1 Work Breakdown Structure (WBS). Defines performance, schedule and cost data by product-oriented WBS. The Contractor Work Breakdown Structure (CWBS) shall be extended to the lowest appropriate level required by the Government to provide adequate management, surveillance, and performance measurement and shall be the basis for tracking, controlling, measuring and reporting all costs, risks and schedule performance under this contract.

3.3.2.2 Organizational Categories. Defines performance, schedule and cost data by the Contractor’s organizational structure (e.g., Functional or IPT).

3.3.2.3 Baseline. Defines changes to the baseline system performance.

3.3.2.4 Staffing. Defines staffing forecasts.

3.3.2.5 Integrated Master Schedule (IMS). The Contractor shall prepare and submit an IMS for the quantites in all CLINs. The IMS submitted with the proposal shall serve as the baseline at the start of the effort. The purpose of the IMS is to provide a common schedule by which the Government and Contractor can effectively manage the program. It shall indicate major tasks, major sub-tasks, milestones, program reviews, test dates, deliverables, critical path, and other mutually agreed upon items. The Contractor shall maintain a current schedule during the period of performance and provide to the Government, or upon request.

3.3.3 Risk Management/Mitigation Plan. The Contractor shall conduct and document an risk management program to identify, analyze, track, and plan alternatives to reduce schedule and technical risks. Risk items and their mitigation efforts shall be presented at formal program reviews and on an as needed basis during other meetings.

The Contractor shall discuss system risk management (technical, schedule, cost). The risk management/mitigation plan shall include, but is not limited to, the following: risk description, rating (stoplight or low, medium, high), program impact, mitigation strategy, action officer, schedule and status, see CDRL-AAA, DID A002.

3.3.4 Integrated Product Team (IPT). The goal of the IPT is to resolve many issues and concerns at the lowest level possible and to expeditiously escalate issues that need resolution at higher levels. The Government and Contractor will conduct an Overarching Integrated Product Team (OIPT), while smaller groups conduct business related to their specialty in Working-level Integrated Product Teams (WIPTs).

3.3.4.1 IPT Overview. The Contractor shall coordinate with the Government to incorporate an IPT discipline into the STORM II program. The objectives of the IPT are to foster an open, shared data/information environment and to implement a disciplined systems engineering approach to influence the design, manufacturing, testing, logistics support, and on-schedule delivery of specification compliant units, while striving to continuously improve the various Government/Contractor processes and reduce system life cycle cost. The IPT shall also complete the following additional actions throughout the life of the contract:

a. Hold IPT reviews.

b. Use risk management techniques to document, track, and manage program areas of risk.

c. Review/concur on program documentation.

d. Review follow-on qualification testing with the goal of reducing repetitive testing.

e. Review/concur on all Failed Item Analysis Reports (FIARs)/Engineering Change Proposals

(ECPs)/Waivers/Deviations/Trades.

f. Review and provide input to maintain the accuracy of the Integrated Master Schedule.

3.3.4.2 IPT Membership. The IPT will consist of Government and Contractor personnel associated with the STORM II program and related efforts. The Government STORM II Assistant Product Manager (APM) will co-chair the IPT with the associated Contractor counterpart. The IPT chairpersons will work in good faith to reach agreement on all items requiring IPT approval/concurrence. If agreement cannot be reached between the co-chairpersons, then the issue(s) will be escalated per each organization’s chain of command. The co-chairs will define the membership of the IPT at the Post Award Conference.

3.3.4.3 Plans, Reports, Reviews, & Meetings. The IPT co-chairs shall develop an agenda for all reviews/meetings, see CDRL-AAA, DID A003.

3.3.4.4 IPT Reviews. IPT reviews shall provide a forum to identify, discuss and resolve issues that could affect the system performance, design, production, testing, logistics support, system deliveries, life cycle cost and program schedule, see CDRL-AAA, DID A003. The Contractor shall participate in and support IPT Reviews at NLT 90 calendar day intervals throughout the life of the contract, or as agreed to by the IPT chairpersons. IPTs include major program management meetings such as design and test readiness reviews. The first IPT review will be conducted on or about 30 calendar days after the Post Award Conference (PAC). After the PAC, IPT reviews may be conducted as teleconferences or video-teleconferences (VTCs) if mutually agreed upon by the IPT co-chairpersons; however face-to-face meetings are preferred to be at the Contractor’s facility. With Government concurrence, IPT reviews may be relaxed in frequency, and/or may be combined with significant meeting events.

IPT reviews will also address the status of all Government Furnished Equipment (GFE), if applicable. At a minimum, the IPMR and the Risk Mitigation Document shall be reviewed at these meetings, as well as, an co-drafted agenda approved by the Government that includes items such as: deliverable status, test status and Technical Manual (TM) development status, etc.

3.3.5 STORM II Working-level Integrated Product Teams. The STORM II APM will designate Government chairs to lead WIPTs. The Contractor shall support separate STORM II functional area WIPTs for Acquisition, Cost, Supportability, Technical, Quality Assurance and Test & Evaluation (T&E). The Contractor shall designate their respective subject matter expert for relevant WIPT participation.

3.3.5.1 WIPT Reviews. The Contractor shall participate in and support the WIPT. WIPT reviews shall provide a working level forum to identify, discuss and resolve issues that could affect the system performance, design, production, testing, logistics support, system deliveries, life cycle cost and program schedule. WIPTs resolve issues cited by the IPT, and prepare information for the IPT reviews. The WIPT will, whenever possible, attempt to minimize travel costs for both parties by utilizing teleconferences or VTCs to conduct these informal reviews.

WIPT will meet frequently and informally in order to develop strategies, tailor documentation, resolve issues and promote working progress.

3.3.6 STORM II Informal and Formal Reviews. The contractor shall support informal and formal reviews.

3.3.6.1 STORM II Formal Reviews: PAC, Design Review (DR), Test Readiness Review (TRR), Product Qualification Testing (PQT),Contractor, Government Development Test (GDT), and Production Readiness Review (PRR). The Contractor shall host a PAC within 30 calendar days of contract award. The Contractor shall host a DR within 30 calendar days after receipt of order (ARO). The Contractor shall host a TRR, as a minimum, five (5) business days prior to test event start. The TRR shall review the Contractor’s preparation and ability to execute test events in accordance with approved test procedures. At a minimum, test articles must pass Group A Testing (per the STORM II PS). The T&E WIPT will assess the system’s readiness to enter PQT and the status of planning for and the capability to conduct GDT, to include resources and other equipment. The PQT, unless otherwise specified in the contract or performance specification, shall be performed by the Contractor. PQT shall consist of the inspections/tests as specified in the PS. The Contractor shall provide a PQT report (CDRL-EEE, DID E003).

3.3.6.1.1 STORM II Post Award Conference Exit Criteria. The Contractor shall host a PAC at the Contractor facility not later than 30 calendar days ARO. The purpose of the conference is to ensure there is a mutual understanding of the terms, conditions, contract requirements and risks among all parties responsible for the management, performance of the contract, requirements and proposed work, review general approach, schedule and level of effort, and provide any necessary clarifications. Action items shall be mutually developed and assigned to the appropriate party (Government or Contractor) and shall be reflected in the meeting minutes, see CDRL-AAA, DID A003. The PAC minutes shall be mutually prepared and distributed at the conclusion of the meeting. The Contractor shall successfully address the following questions and deliver all CDRLs associated with this event. IPT agreement on the following:

a. Contract terms, conditions, and contract requirements.

b. Requirements for on-line technical information.

c. Public announcements.

d. Configuration Management Plan.

e. Risk Identification, Risk Analysis and Risk Mitigation Plan.

3.3.6.1.2 STORM II Design Review. The Contractor shall successfully address the following questions and deliver all CDRLs associated with this event, CDRL-BBB, DID-B002. Exit Criteria is Government approval that the Contractor has accomplished/verified the following:

a. All required system performance for Qualification is fully decomposed and defined in the functional baseline.

b. Design, as disclosed, satisfies the STORM II System Level Performance and Component specifications.

c. Summarize status of the reliability and maintainability engineering design activities (i.e., allocations, models, block diagrams, predictions, anticipated failure modes and effects).

d. Established and documented system allocated baseline to enable the design to proceed with proper configuration management.

e. Established adequate processes and metrics for the program to succeed.

f. Included human integration design factors in the overall system design.

g. Identified program risks and established risk mitigation plan, and are on track, for all functional areas (SE, Program Management, Quality/Test, Reliability, Logistics, Manufacturing, etc.).

h. Program schedule is executable (technical, cost, risk).

i. Program is staffed properly.

j. Identify all required unique tooling and test equipment required to produce and test the STORM II.

k. Traceability of requirements/specifications to testing is clear in the allocated baseline. Identification of all precious metals (including amount in grams), toxic or hazardous materials and all material(s) for each optical element, of the entire design (to include ancillary items).

l. STORM II Logistics Product Data delivered.

m. Presentation of component design tolerances and compatibility between components.

n. Identification of long lead parts and suppliers.

o. Initial system and data architectures shown.

p. Draft Test plans are developed and ready for submission for Government review.

q. Updated risk assessment for all functional areas (SE, Program Management, Quality/Test, Reliability, Logistics, Manufacturing, System Architecture, etc.), and mitigating strategies are identified.

r. Updated program development schedule including fabrication, test and evaluation, firmware coding, critical path drivers, etc.

s. Updated Logistics Product Data (LPD) describes program sustainment development efforts and schedules based on current budgets, test evaluation results and firm supportability design features.

t. Identification of all exposed materials of the design (to include ancillary items) to support the Chemical, Biological, Radiological, and Nuclear Chemical Survivability Assessment (CBRNCSA).

u. Test procedures are delivered for Government review.

v. Established system initial product baseline.

w. Updated risk assessment for all functional areas (SE, Program Management, Quality/Test, Reliability, Manufacturing, etc.).

x. Updated program development schedule including fabrication, test and evaluation, firmware coding, critical path drivers, etc.

y. Updated Logistics Support Plan shall include the Contractor’s plan for long-term (10-year) supportability for all production systems. The Contractor shall update program sustainment development efforts and schedules based on current budgets, test evaluation results and firm supportability design features.

z. Identification of all precious metals (including amount in grams), toxic or hazardous materials, and all material(s) for each optical element, of the entire design (to include ancillary items).

3.3.6.1.3 STORM II Qualification TRR. The Contractor shall conduct a TRR no less than five (5) business days prior to start of Contractor testing at the Contractor facility. The purpose of the TRR is to assure the Government that the Contractor has the personnel, material, and facility resources to test the STORM II. The Contractor shall prepare and submit the TRR presentation material in Contractor format. Contractors shall submit a Safety Assessment Report, see CDRL-CCC, DID C009, a minimum of one (1) month prior to any scheduled test event that includes Soldiers.

The Contractor shall prior to the start of PQT, conduct a TRR to assess test objectives, test methods and procedures, scope of tests, safety, and verify required test resources have been properly identified and coordinated to support planned tests. The Contractor shall host pre-PQT TRR for the events no later than 60 calendar days before the start of the test. At the pre-PQT TRR, the T&E WIPT shall verify the traceability of planned tests to program specifications and determine the completeness of test procedures and their compliance with test plans and descriptions. The Contractor shall provide evidence to assess the system for development maturity, cost/schedule effectiveness and risk to determine readiness to proceed to formal testing. The Contractor shall meet the Exit criteria for the completion of the TRR shall (at a minimum) include:

a. Test plan(s) completed.

b. Test Procedures completed, when applicable.

c. Completed identification and coordination of required test resources, to include roles and responsibilities of all test participants identified.

d. Test/inspection data on subsystem and components verifying that the requirements in the System

Requirements Management System have been met for those items.

e. Identified risk level acceptable to the program leadership.

f. Configuration of the systems under test has been identified; both hardware and firmware, and all units and test are of the same configuration.

g. All action items from previous technical and design reviews have been completed and closed.

3.3.7 STORM II Production Readiness Review. The Contractor shall host a Production Readiness Review, in conjunction with the Government, at the Contractor’s facility no more than 150 calendar days ARO. The purpose of the PRR is to assure the Government that the STORM II design is finalized and that the Contractor has the personnel, material, and facility resources to produce the STORM II. The Contractor shall prepare and submit the PRR presentation material in Contractor format. The Contractor shall fully address the following criteria. The Government will determine whether the Contractor has accomplished/verified the following:

a. Design is ready for production; Contractor meets Manufacturing Readiness Level (MRL) 9.

b. No unacceptable production risks (cost, schedule, performance) exist for prime and subContractors.

c. Established and documented system product baseline.

d. Established adequate processes and metrics for the program to succeed.

3.3.8 STORM II Production Phase. The Contractor shall deliver the Production Manufacturing Plan, see CDRL- AAA, DID A004. Prior to Production, the Contractor shall provide to the Government a Production Manufacturing Plan.

3.3.8.1 Production Systems. The Contractor shall provide STORM II systems, components, and spare parts that meet the requirements in the STORM II PS. Components include cables, carrying case, manuals, cleaning materials, remote, batteries, and battery charger.

3.3.8.2 Production Management. The Contractor shall track the status of STORM II production management with critical suppliers, inventory control, resources and schedule problem identification, implementation, and material Line Of Balance (LOB) (This information shall be made available for review by the Government upon request). If the Contractor determines a need to change suppliers, they shall notify the Government in advance, develop a requalification plan, and obtain concurrence prior to implementing those changes.

3.3.9 Correspondence Transmission. The Contractor shall submit written program correspondence and documentation Microsoft (MS) Office 2013 compatible format for dissemination via electronic submittal to members of the IPT. The preferred method of file submission is via e-mail. If the Contractor proposes an alternative method for correspondence transmission that is approved by the Government IPT chairperson(s) or Contracting Officer, the Contractor shall manage availability and distribution to the members of the IPT, at no cost to the Government.