W15QKN19R0014-0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offers 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 amendments: (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 ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: 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 data, 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.)

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)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Cost Plus Fixed Fee

0001 2018OCT30

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

JOHN SCOTT

EMAIL: JOHN.C.SCOTT158.CIV@MAIL.MIL

W15QKN-19-R-0014

2018OCT25

X

X

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 31

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: JOHN SCOTT

Buyer Office Symbol/Telephone Number: ACC-NJ-MC/(973)724-9061

Type of Contract 1: Cost Plus Fixed Fee

Type of Contract 2: Firm Fixed Price

Kind of Contract: Research and Development Contracts

*** End of Narrative A0000 ***

1. The purpose of Amendment 1 to W15QKN-19-R-0014 is to incorporate the following updates:

a. Update Section B CLIN 0003 to reflect CDRLs A001-A0049.

b. Update Section C to clarify paragraph numbering as well as CDRL numbering.

c. Update CDRLS A005, A040, A041, and A042 to correct the Section C reference.

2. All other terms and conditions remain unchanged.

*** END OF NARRATIVE A0003 ***

2 31

W15QKN-19-R-0014

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

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

0003 EMD CONTRACT DATA REQUIREMENTS LIST 1 LO $ ** NSP ** ___________________________________ __________________

SERVICE REQUESTED: EMD CDRLS

This CLIN applies to EMD Contract Data Requirements

List (CDRLs).

CDRLS A001-A049

Not Separately Priced

(End of narrative A001)

Inspection and Acceptance _________________________

INSPECTION: Destination ACCEPTANCE: Destination

3 31

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

Statement of Work (SOW) for Engineering and Manufacturing Development (EMD) Phase, Low Rate Initial Production (LRIP), and Full Rate

Production (FRP) of the Cartridge, 40mm, High Velocity, XM1176 High Explosive Dual Purpose Air Burst (HEDP-AB) and Fuze Setter:

Programming Unit, 40mm High Velocity Dual Purpose Air Burst (HEDP-AB), XM101

1.0 Scope

1.1 Overview

This Statement of Work (SOW) encompasses development and production efforts including design, fabrication of components, assembly, integration, testing, packaging and verification for the 40mm High Velocity (HV) XM1176 High Explosive Dual Purpose Air Burst (HEDP-AB) system during Engineering and Manufacturing Development (EMD) and Production. Herein, the XM1176 HEDP-AB system is defined as a

M430/M430A1 cartridge that has been retrofitted with an air burst capable fuze (retrofitted cartridge) and a XM101 fuze programming unit

(programming unit). The XM1176 EMD effort will be divided into two (2) Phases during which the contactor shall: 1) develop a fuze that has air burst, point detonating, and self-destruct capabilities, 2) develop a fuze programming unit, 3) develop a process to remove the

Point Initiated Base Detonating (PIBD) fuzes from previously produced and accepted M430/M430A1 cartridges, and 4) develop a process to assemble the newly designed fuzes onto the de-fuzed M430/M430A1. The complete XM1176 HEDP-AB system shall meet all the performance specification requirements per the cartridge and programming unit Performance Specifications (MIL-PRF-XM1176 and MIL-PRF-XM101, herein referred to as the Performance Specifications). The Performance Specifications are the governing documents for this contract. In the event that there is a conflict between the Performance Specifications and the TDP that will be developed, the Performance Specifications take precedence. EMD Phase 1 and 2 are approximately 33 months in duration. These efforts will lead to a final retrofitted cartridge and programming unit design, subsequent qualification of Developmental Test and Evaluation (DT&E) hardware and Type Classification

Limited Procurement (TC-LP) and Milestone C (MS C) actions. Consistent with successful MS C and TC-LP actions, the Contractor shall develop the necessary manufacturing processes and process controls to ensure producible cartridge and programming unit designs, complete production facilitization, and establish appropriate quality controls.

2.0 Applicable Documents

2.1 Mandatory Documents

2.1.1 MIL-PRF-XM1176 Cartridge, 40mm, High Velocity (HV), XM1176 High Explosive Dual Purpose Air Burst (HEDP-AB)

2.1.2 MIL-PRF-XM101 Fuze Setter: Programming Unit (PU), 40mm High Velocity Dual Purpose Air Burst (HEDP-AB), XM101

2.1.3 Security Classification Guide (SCG) for Cartridge, 40mm, High Velocity (HV) XM1176, High Explosive Dual Purpose Air Burst (HEDP-

AB)

2.1.4 ASME Y14.5M-1994 Dimensioning and Tolerancing

2.1.5 ASME Y14.100-2004 - Engineering Drawing Practices

2.1.6 MIL-A-70625 - Automated Acceptance Inspection Equipment Design, Testing and Approval

2.1.7 MIL-STD-961 - Defense Specifications

2.1.8 MIL-STD-1168 - Ammunition Lot Numbering and Ammunition Data Cards

2.1.9 MIL-STD-1316E Fuze Design, Safety Criteria for, dated 10 July 1998

2.1.10 MIL-STD-331 - Fuze and Fuze Components, Environmental and Performance Tests For

2.1.11 MIL-STD-1916 - DoD Preferred Methods for Acceptance of Product

2.1.12 ANSI/NCSL Z540-1 - General Requirements for Calibration of Laboratory measuring and Test Equipment

2.1.13 MIL-STD-1472 - Human Engineering Design Criteria for Military Components, Equipment and Facilities

2.1.14 MIL-STD-130 - Identification Marking of U.S. Military Property

2.1.15 MIL-HDBK-237 Electromagnetic Environmental Effects and Spectrum Supportability Guidance for The Acquisition Process

2.1.16 AR 25-2 - Information Assurance - Rapid Action Revision (RAR)

2.1.17 ANSI/EIA-748 - Earned Value Management Systems

2.1.18 DoD 5100.76-M - Physical Security of Conventional Arms, Ammunition and Explosives

2.1.19 TB 700-2, Joint Technical Bulletin - Ammunition and Explosives Hazard Classification Procedures

2.1.20 JOTP-052, Joint Ordnance Test Procedure Guidance for Qualification of Fuzes, Safe and Arm (S&A) Devices, and Ignition Safety

Devices (ISD)

2.1.21 ARDEC General Specification for 3-Dimensional Modeling Standards

2.1.22 AR 530-1 Operations Security

2.1.23 Defense Transportation Regulation 4500.9-R-Part II June 2008, Cargo movement for transportation of Sensitive Conventional AA&E

2.2 Drawings

2.2.1 13073870 Interface Control Drawing, Programming Unit, Hardware

2.2.2 13073960 Interface Control Document, Programming Unit, Electronic

2.2.3 9287854 Body Assembly

2.2.4 8886405 Linking of 40mm High Velocity Ammunition

2.2.5 11691393 Link, Cartridge, Metallic Belt 40mm, M16A2

2.2.6 12928042 Packing and Marking of Shipping and Storage Container PA120 with linked 40mm Cartridges

2.2.7 13072800 Cartridge, 40mm, HEDP-AB, XM1176

2.2.8 13075802 Programming Unit, 40mm: HEDP-AB, XM101

2.2.9 13074780 Cable Assembly, Junction, XM101 to FWS/CS

2.2.10 A3260830 Mount Assembly, Mk19

4 31

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

2.2.11 A3260832 Adjust Mount, Mk19

2.3 Explosive Ordnance Disposal (EOD) Documents

2.3.1 AR 700-142, Type Classification, Material Release, Fielding and Transfer (See Appendix I)

2.4 Reference Documents

2.4.1 MIL-STD-882E System Safety Program Requirements, 11 May 2012

2.4.2 DoD 4160.21-M-1, Defense Materiel Disposition Manual

2.4.3 U.S. Nuclear Regulatory Commission (NRC) provisions of 10 CFR, especially Parts 19, 20, 21 and 40, or equivalent Agreement

State regulations or comparable foreign regulations, if applicable.

2.4.4 DD Form 254 (DD254) - Contract Security Classification Specification.

3.0 General Requirements

Unless otherwise specified, the requirements in Section 3.0 apply to all phases of work for the XM1176 HEDP-AB system.

3.1 Security

The Contractor shall have available, or have the ability to obtain, the resources and personnel capable of reviewing, analyzing, and processing classified information up to the required classification level in accordance with the contract DD Form 254 (DD254) - Contract

Security Classification Specification.

3.1.1 Physical Security

The Contractor shall be capable of providing storage and accountability in accordance with DOD Directive 5100.76M, which outlines physical security guidance for the protection of DOD Sensitive Conventional Arms, Ammunition, and/or Explosives (AA&E).

Prior to contract award, the Contractor shall have a pre-award Physical Security Inspection of their facility conducted by Defense

Security Service (DSS), with verification that all security requirements of DoD 5100.76M are being met.

The Contractor shall meet the standards set forth in Defense Transportation Regulation 4500.9-R-Part II June 2008, Cargo movement for transportation of Sensitive Conventional AA&E.

The Contractor shall ensure that all items are properly protected and stored. Storage of material and equipment shall be in accordance with procedures approved by the Contracting Officer (CO). The Contractor shall arrange all items in safe and protective storage in a manner to facilitate stock control, physical inventory, issuance, and security. Highly pilferable items (as identified by the CO) shall be safeguarded and controlled. The Contractor shall be responsible for all material handling within the storage facility, this includes receiving into and shipping from the facility. The Contractor shall be responsible for the safe operation of all material handling equipment, and be properly trained and licensed to operate the equipment (i.e. forklifts, etc.).

3.1.2 OPSEC

The contractor shall develop an OPSEC Standard Operating Procedure (SOP)/Plan (DI-MGMT-80934C) within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan will include 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 will be an OPSEC Coordinator. The contractor will ensure this individual becomes OPSEC Level II certified per AR 530-1. Per AR 530-1, Operations Security, new Contractor employees must complete

Level I OPSEC training within 30 calendar days of their reporting for duty. All contractor employees must complete annual OPSEC awareness training.

Reference CDRL - A001 OPSEC Plan

3.1.3 Classification

The highest security classification level for this effort is Secret. The Contractor will only receive classified materials at the actual performance location(s) as identified in the DD254. All contractor personnel handling Secret data shall be required to have a Secret or higher clearance.

3.1.4 Contractor Facility Clearance

The Contractor shall obtain and maintain a Facility Clearance at the Secret level. The Contractor shall comply with all security requirements as specified in this SOW, the DD Form 254, and applicable contract clauses. The Contractor shall be responsible for ensuring that the provisions of security related contract clauses apply to its subcontractors, by flowing the clauses down to those sub-

Contractors and requiring that those same sub-Contractors subsequently flow them down to their lower tier sub-Contractors. A copy of DD

Form 254 issued a sub-Contractor must be provided to the COR and the certifying official identified in the prime contract DD Form 254.

3.1.5 Security Classification Requirements

The Contractor shall adhere to the security requirements in accordance with the Security Classification Guide for 40mm, Cartridge, HEDP-

AB, XM1176. The Contractor shall extend all relevant security requirements to any sub-Contractors.

3.1.6 Handling or Access to Classified Information

Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to classified information and requires

5 31

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Contractors to comply with - (1) The Security Agreement (DD Form 441), including the NISPOM (DoD 5220.22-M); any revisions to DoD

5220.22-M, notice of which has been furnished to the Contractor. The Contractor shall support the Government in ensuring that all aspects of security are maintained on developmental systems during all activities including, but not limited to: field tests and evaluations, test site surveys, relevant test data maintenance, reduced and limited test site security and test site administration activities.

3.1.7 Information Protection

Information or data developed under this contract is the property of the United States Army. All rights are reserved to the U.S.

Government. The Contractor (or sub-Contractor) shall not distribute or use the information and data without the express and specific written approval of the Picatinny Arsenal Public Affairs Office. Instructions for clearing technical material for release to the public and a sample clearance form (SFAE-AMO Form 3002) are included as an attachment to this contract.

3.1.8 Transmittal of Controlled Unclassified Information (CUI)

CUI is a Department of Defense term that is used to collectively describe all information to which access or distribution limitations have been applied in accordance with applicable national laws or regulations. CUI is official Government information that is unclassified, but that has been determined by designated officials to be exempt from public disclosure under the Freedom of Information

Act (FOIA) (Title 5 U.S.C. Section 522) as amended. All CUI that is transmitted between the Government and Contractor shall be done via encrypted channels. Material can be provided via US postal service, or electronically via a file encryption platform such as Encryption

Wizard (free software download at spi.dod.mil), or the U.S. Army Aviation and Missile Research Development and Engineering Center

(AMRDEC) Safe Access File Exchange (SAFE) found at https://safe.amrdec.army.mil/SAFE/ ).

3.1.9 Antiterrorism (AT) Awareness Level Training

All Contractor employees, to include sub-Contractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable and 30 days after new employee hired. The Contractor shall submit certificates of completion for each affected Contractor employee and sub-Contractor employee, to the Government Technical Representative or to the Contracting Officer, if a Government Technical Representative is not assigned, within 15 calendar days after completion of training by all employees and subcontractor personnel. All contracts per AR 525-13, paragraph 5-19, Standard 18, AT Measures for

Logistics and Other Contracting are required to include AT Level I requirements. AT level I awareness training is available at the following website: http://jko.jten.mil/courses/atl1/launch.html

3.1.10 iWATCH Training

All Contractor employees, to include sub-Contractor employees, requiring access to Army installations, facilities and controlled access areas shall complete iWATCH Training. The Contractor and all associated sub-Contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity AT Officer). 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 Government Technical

Representative. This training shall be completed and results reported to Government Technical Representative or Contracting Officer within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance.

3.1.11 Information Assurance (IA) / Information Technology (IT) Training

All Contractor employees and associated sub-Contractor employees must complete the DoD IA 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

DoD 8570.01, DoD 8570.01-M and AR 25-2 within six (6) months of employment.

3.1.12 Access and General Protection / Security Policy and Procedures

For Contractor and sub-Contractor employees with an area of performance within an Army controlled installation, facility or area, the

Contractor and all associated sub-Contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by Government representative).

The Contractor shall also 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 as directed by DoD, 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.

The Contractor shall provide the Government access to prime and sub-Contractor facilities so that regulatory surveys, inspections and investigations can be conducted.

The DoD has designated Joint Personnel Adjudication System (JPAS) as its system of record for Contractor eligibility and access to classified information. This means that JPAS is the "Cognizant Security Agency (CSA) - designated database" referenced in the National

Industrial Security Program Operating Manual (NISPOM) (Paragraph 2-200b). Requests for site visit authorization shall be submitted in accordance with DoD 5220.22M (Industrial Security Manual for Safeguarding Classified Material) and applicable Industrial Security

Letters (ISLs). The Contractors request for site visit authorization shall be submitted no later than one (1) week prior to visit.

The Contractor will have a law enforcement background check completed for all employees who will be entering Army-controlled

6 31

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

installations or facilities. Documentation of these checks will be made available to the Government Technical Representative upon request. The Contractor will provide to the Government Technical Representative, seven (7) days in advance of the event, names and

Social Security Numbers (or equivalent identification numbers for non-U.S. citizens) of all employees who will be entering Army-controlled installations or facilities.

The Contractor shall ensure that employees requiring entry into Army-controlled installations or facilities have obtained access badges and passes in accordance with facility regulations and that these badges and passes are obtained in advance so as not to delay the accomplishment of contract performance. The Contractor will return all issued U.S. Government Common Access Cards (CAC), installation badges, and/or access passes to the Government Technical Representative when the contract is completed or when a Contractor employee no longer requires access to the installation or facility.

3.1.13 Contractor Employees Who Require Access to Government Information Systems (IS)

All Contractor employees with access to a Government info 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 prior to access to the IS and then annually thereafter.

3.1.14 Threat Awareness Reporting Program (TARP)

Per AR 381-12 Threat Awareness and Reporting Program (TARP), Contractor employees must receive annual TARP training by a counter-intelligence (CI) agent or other trainers as specified in 2-4b.

3.2 Program Management

The Contractor shall plan and implement a program management process to minimize technical, cost, and schedule risk while meeting or exceeding performance specification requirements. The Contractor shall be responsible for establishing and maintaining an effective internal management and control system to ensure that appropriate contract goals and objectives are met, resources are safeguarded, laws and regulations are followed, and reliable data are obtained, maintained, and fairly disclosed through applicable contract data requirements. The management system utilized by the Contractor shall provide for the capability to plan and control the organization, schedule, cost, technical performance, accurate progress reporting procedures, and to forecast potential results of alternate program actions. The Contractor shall assess, approve, and document the performance, cost, schedule, and risk of proposed changes to the evolving functional architecture, physical hierarchy, and baselines prior to implementation. The Contractor shall inform and obtain

Government approval for any changes that potentially can increase contract cost, schedule, risk, and affect system requirements before the changes are implemented.

3.2.1 Integrated Product Teams (IPTs)

The Government requires the establishment of Integrated Product Teams (IPTs) that shall meet on a weekly basis. These IPTs shall be comprised of an amalgamation of Government and Contractor personnel, including appropriate sub-Contractors. The Contractor shall furnish the appropriate personnel to these IPTs. The Contractor IPT members shall provide Government IPT members all technical and programmatic status updates including but not limited to, design progress, build status, test plans and test results, improvements, risks and issues.

3.2.2 Contract Work Breakdown Structure (CWBS)

The Contractor shall develop and maintain the CWBS (DI-MGMT-81334D) and CWBS dictionary for this contract. The Contractor shall extend the CWBS down to the appropriate level required to provide adequate internal management, surveillance, and performance measurement, regardless of the reporting level stipulated in the contract for Government visibility. The CWBS shall serve as a framework for contract planning, budgeting, and reporting of cost and schedule status to the Government. The Contractor shall submit an updated CWBS as applicable during the execution of the contract. Updates to the CWBS shall be briefed during PMRs.

Reference CDRL - A002 Contract Work Breakdown Structure (CWBS)

3.2.3 Contractor Performance Management System

The Contractor shall utilize its existing, internal performance management system to plan, schedule, budget, monitor, manage, report cost, schedule, and technical status applicable to the contract. The Contractors internal performance management system shall serve as the single, formal, integrated system that meets the Contractors internal management requirements for timely, reliable, and auditable performance information. The Contractors system shall meet the guidelines and be maintained in accordance with the requirements of the

Contractors own documented system description.

3.2.4 Integrated Master Plan (IMP) and Integrated Master Schedule (IMS)

The Contractor shall develop, maintain, and manage the program in accordance with the IMP (DI-MGMT-80004A) and an IMS (DID-MGMT-81861A, Tailored to include 3.6.7 and 3.7 only). The Contractor shall submit updates to the IMP and IMS to the Government one (1) month prior to

Program Management Reviews for review. The IMP and IMS shall delineate component and system integration testing. The Government sponsored test events (DET-1, DET-2, and DT&E) shall be an integral part of the IMP and IMS. The IMS shall also be directly correlated to the CWBS levels and titles. The IMS shall sufficiently detail critical and high-risk efforts identified and planned realistically to ensure successful program execution. It shall be extended and expanded as the contract or agreement unfolds and additional insight is needed. The IMS shall include the efforts of all activities, including sub-Contractors and suppliers.

Reference CDRL - A003 Integrated Master Plan (IMP)

Reference CDRL - A004 Integrated Master Schedule (IMS)

7 31

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

3.2.5 Contractor Manpower Reports

The Contractor shall report all Contractor labor hours (including sub-Contractor labor hours) required for performance of services provided under this contract for EMD, via a secure data collection web site. The Contractor shall completely fill in all the required data fields using web site: http://www.ecmra.mil/ . Reporting inputs shall be for labor executed during the period of performance during each Government FY, which runs from October 1 through September 30. While inputs may be reported any time during the

FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk at:

http://www.ecmra.mil/ .

3.2.6 Contract Funds Status Report (CFSR) (For EMD Only)

The Contractor shall prepare and update the CFSR (DI-MGMT-81468) as a best practice throughout this contract. The CFSR reporting level shall be reported monthly and be at the total contract level.

Reference CDRL - A005 Contract Funds Status Report (CFSR)

3.3 Systems Engineering

The Contractor shall manage the program via a Systems Engineering (SE) approach that optimizes total system performance while minimizing total ownership costs. The Contractor shall develop the necessary data and models to assess the XM1176 HEDP-AB system life-cycle cost

(development, procurement, support and disposal). The Contractor shall employ best engineering practices and methods in an iterative process to develop a design that meets all requirement as stated in the XM1176 HEDP-AB system Performance Specifications. The Contractor shall develop balanced design and production solutions to optimize the Technical Performance Measures (TPMs), control product and process variation, and eliminate waste. Trade studies and other engineering decisions shall consider the full range of requirements, design constraints, and programmatic considerations. These analyses shall be documented for historical purposes and made available to the Government as necessary.

3.3.1 Systems Engineering Management Plan (SEMP)

The Contractor shall provide a SEMP (DI-SESS-81785A) that transforms program requirements and guides all technical aspects of the acquisition program. The Contractor shall develop, maintain, and manage the program in accordance with an approved SEMP and provide updates to the SEMP during Program Management Reviews (PMRs). The Contractors SEMP shall address both Government and Contractor activities and responsibilities. The Contractors SEMP shall describe the overall technical approach, including systems engineering processes, resources, key technical tasks, activities and events along with metrics and success criteria. The Contractors SEMP shall be integrated or linked with other program management control efforts such as the IMP, IMS, and life-cycle cost containment. The Contractor shall document their activities relevant to technical performance, cost, schedule, and risk in the SEMP.

Reference CDRL - A006 Systems Engineering Management Plan (SEMP)

3.3.2 Risk Management

The Contractor shall establish a risk management and mitigation process and plan. The plan shall address performance, cost, and schedule and shall include risk mitigation plans. Risk tracking shall be integral to the Systems Engineering Plan (SEP) process. Impact of risk on program progress and IMS status shall be included.

3.3.3 Master Test Plan (MTP)

During EMD the Contractor shall prepare and execute a MTP that supports program Milestones. The MTP shall delineate component and system integration testing; include quantities, objectives, configuration, test equipment and methods and an integration path to a complete system including the Government sponsored tests. Any revisions to the MTP shall be communicated to the Government IPT lead.

3.3.4 Technical Performance Measure (TPM)

As part of the Systems Engineering process, the Contractor shall identify the TPMs and specific key design features that drive system performance; specifically, accuracy, lethality, range, and reliability. The Contractor shall draft TPMs to support the Preliminary

Design Review (PDR). Finalized TPMs, along with a current assessment of the system performance for each TPM, shall be prepared to support CDR.

3.4 Configuration Management (CM) System

The Contractor shall have a CM system that assures integrity and control of the configuration of the cartridge and programming unit, including software configuration items, throughout the programs life cycle.

3.4.1 Configuration Management Plan (CMP)

The Contractor shall prepare and maintain a documented CMP. The plan must detail the chain of command for the evaluation and approval process for all design (hardware and software) and process/procedure approvals including Request for Deviations, Engineering Change

Notices and Engineering Change Proposals. All EMD and production hardware and software shall be under configuration management. The CM system shall use the latest revision of MIL-STD-3046 or similar industry standard as guidance for hardware; and IEEE 828, ISO/IEC 12207, or a similar industry standard for management of software configuration items.

3.4.1.1 Software Configuration Management

The Contractor shall establish and maintain a software configuration management system in accordance with its CM plan and Software

Development Plan (SDP) to establish and maintain a software baseline. The Contractor shall implement a change control process for the approval or rejection of all change requests that are sent against any baseline. The Contractor shall maintain a software identification table for each piece of software and its corresponding hardware component. This list shall consist of the hardware serial number and its

8 31

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

correlating software version number to ensure that correct software versions resides on the production hardware.

3.4.2 Performance Specifications and TDP Control

The Government shall have control of the XM1176 Performance Specifications, XM1176 MIL-PRF-XM1176 and MIL-PRF-XM101. The Contractor has control of changes to its TDP up to the point of the creation of the Initial Production Baseline for the production of DT&E hardware.

The Performance Specifications are the governing documents for this contract. In the event that there is a conflict between the

Performance Specifications and the TDP that will be developed, the Performance Specifications take precedence.

3.4.2.1 Technical Data Package (TDP)

The Contractor shall create and maintain a 3-D TDP in accordance with (IAW) the ARDEC General Specification for 3-Dimensional Modeling

Standards. The TDP shall be prepared IAW MIL-STD-31000. The TDP shall include cartridge, programming unit, component level drawings, associated lists, Software Control Drawings (SCDs), and Altered Item Drawings (AIDs) as applicable for the hardware on which the software resides, associated QAPs and specifications at the production level. The Contractor shall denote any components that are determined to be safety-critical (any component that directly contributes or controls arming) as CSI (Critical Safety Item) on the components drawing. Hard copies (2-D) or an alternate electronic format approved by the Government may be acceptable for drawings that are not available in Creo.

The Contractor shall perform configuration management in accordance with the provisions and clauses pertaining to Engineering Change

Proposals (ECPs), Value Engineering Change Proposals (VECPs), Notices of Revision (NORs), and Requests for Variance (RFVs). Submission of all these documents shall address ozone-depleting chemicals (ODCs), as required by Public Law 102-484, Section 326.

The Contractor shall establish the Initial Product Baseline TDP and submit to the Government fourteen (14) days prior to CDR (DI-SESS-

81000E). All TDP elements must be submitted in English language. The Contractor has control of changes to its TDP up to the point of creation of the Initial Product Baseline TDP for the production of DT&E hardware. The IPT will review the level of detail in the TDP for adequacy to define and control the configuration of hardware. In order to ensure that the round will comply with the Performance

Specifications, the TDP must be approved by the Government prior to use in manufacturing of the DT&E hardware. The Government reserves the right not to accept delivery of the DT&E cartridges until Contracting Officer approval of the TDP.

Following successful completion of DT&E, the Initial Product Baseline TDP shall become the Verified Production Baseline TDP for use in subsequent production. Once the Verified Production Baseline TDP has been established, the Government shall have control of changes to the TDP, where an Engineering Change Proposal (ECP) shall be submitted for approval for any changes from the Verified Product Baseline

TDP. Upon Government approval of the ECP, the Contractor shall re-submit the modified drawings to the Government to be included with the latest version of the TDP.

Reference CDRL - A007 Technical Data Package

3.4.2.2 Key Characteristics (KC)

The Contractor shall develop a list of key and critical characteristics (hardware and software) which affect the ability of the XM1176

HEDP-AB system to meet the respective Performance Specification requirements. Key Characteristics (KC) are features of materials, processes, or parts (including assemblies) whose variation within the specified tolerance has a significant influence on product fit, performance, service life, or manufacturability. A Critical Characteristic is any feature throughout the life cycle of a Critical

Safety Item (CSI), such as dimension, tolerance, finish, material or assembly, manufacturing or inspection process, operation, field maintenance, or depot overhaul requirement that if nonconforming, missing or degraded may cause the failure or malfunction of a Critical

Safety Item. The process by which key characteristics are determined shall include the extent of modeling, simulation, or ballistic testing needed to qualify proposed changes to these characteristics as Major Configuration Management (CM) actions. The Contractor shall use MIL-STD-3046 to address critical, major, minor, and administrative characteristics (DI-MISC-80508B) and submit to the

Government thirty (30) days after EMD Base and updates shall be provided to the Government fourteen days prior to CDR.

Reference CDRL - A008 Key and Critical Characteristics List

3.4.2.3 Critical Safety Item (CSI) Components

The Contractor shall ensure that all components that are determined to be safety critical (any component that directly contributes or controls arming) are denoted as CSI (CSI stands for Critical Safety Item) on each component drawing.

3.5 Energetic Material

3.5.1 Energetic Material Qualification

For EMD, it is recommended that US Military qualified energetics are used in design and production of the air burst capable fuze to be used on the XM1176 cartridge.

For all production (LRIP1, LRIP2, and PY1 options) following the completion of EMD, the Contractor shall use US Military qualified energetics in the production of the fuze used on the XM1176 cartridge.

Energetics are expected to be used in the fuze/ignition train. Use of US Military qualified energetics eliminates the need to have a qualification plan for these items. In the event that a non-qualified material is required, the Contractor shall prepare and submit an energetic material qualification plan for review and approval by the ARDEC Energetic Material Qualification Board (EMQB) for each energetic that has not been previously qualified for use by the US Military. The plan shall be submitted for Government approval (DI-

9 31

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

NDTI-80566A) within two (2) months of the introduction of non-qualified material into the design. The Contractor shall prepare and submit a qualification report (DI-MISC-80508B) within one (1) month of completing testing in accordance with the approved energetic material qualification plan.

Reference CDRL - A009 - Energetic Material Qualification Plan

Reference CDRL - A010 - Energetic Material Qualification Report

3.5.2 Energetic materials compatibility

The Contractor shall submit to the Government energetic materials compatibility data as required by the XM1176 MIL-PRF-XM1176 IAW DI-

MISC-80508B within fifteen (15) months after EMD Base award and updated as necessary.

Reference CDRL - A011 Energetic Material Compatibility Report

3.6 System Safety Program

The Contractor shall conduct a system safety management and engineering program using MIL-STD-882E as guidance. The program shall include the necessary planning, coordinating, and engineering analysis to:

Identify the safety-significant functions (safety critical and safety related) of the system and establish a protocol of analysis, design, test, and verification and validation of those functions with the system and software developed activities.

Establish a software criticality assessment with a level of rigor for the requirements, design, code, and test of safety-significant software functions.

Tailor and communicate generic or initial software safety requirements or constraints to the system and software designers as early in the lifecycle as possible.

Analyze the existing documented hazards to determine software influence on these hazards in terms of causal initiation or causal propagation.

Identify, document, and track system and subsystem-level hazards.

Identify the system-level effects of each identified hazard.

Provide input to system safety engineering as to the potential contributions or implications of the software that would affect probability of occurrence.

Categorize each identified hazard in terms of severity and probability of occurrence (specify qualification or quantification of likelihood).

Conduct in-depth analysis to identify each failure pathway and associated system and software causal factors. This analysis will be to the functional depth necessary to identify logical, practical, and cost-effective mitigation techniques and requirements for each failure pathway initiator (causal factor). This analysis shall consider all hardware, software, and human factor interfaces as potential contributors.

Derive safety-specific hazard mitigation requirements to eliminate or reduce the likelihood of each causal factor within the system and software functional architecture.

Provide engineering evidence (through appropriate inspection, analysis, and test) that each mitigation safety requirement and software safety requirement is implemented within the design, and the system functions as required to meet the stated level of rigor, safety goals, and objectives.

Conduct a safety assessment of residual safety risk after all design, implementation, and test activities are complete.

Conduct a safety impact analysis on all Software Change Notices or ECPs for engineering baselines under configuration management.

Submit for approval to the acceptance or certifying authority all waivers and deviations where the system does not meet the safety requirements or certification criteria.

Submit for approval to the acquiring authority an integrated system safety schedule that supports the programs engineering and programmatic milestones.

The results of all safety engineering analysis performed, including software analyses, shall be formally documented in a closed-loop hazard tracking database system. The information shall be correlated in such a manner that it can be easily and systematically extracted from the database to produce the necessary deliverable documentation as required by the contract. The maturity of the safety analysis shall be commensurate with the maturity of system design in accordance with the acquisition lifecycle phase.

Technical specialists as well as sub-Contractors, within other disciplines shall support the system safety effort as required, including support of a System Safety Working Group (SSWG). Actions to eliminate or minimize risk shall be coordinated with System Safety

Engineering and have approval decision authority prior to implementation. Since the retrofitted cartridge being developed in EMD is a munition system; MIL-STD-882E shall be used as guidance on assessment of safety of the munition. Execution of the elements of the safety program shall be reported in design reviews (PDR and CDR) and at SSWG meetings.

3.6.1 System Safety Program Plan (SSPP)

The Contractor shall develop, maintain, and update an SSPP based on the precepts of MIL-STD-882E throughout the program and shall submit this program plan for Government review (DI-SAFT-81626). The SSPP shall define the Contractors safety requirements, planned safety activities, and the safety certification process for the system. The SSPP shall be submitted to the Government within 30 days following the EMD base contract award and updated within 30 days after LRIP Option 1 award.

Reference CDRL - A012 System Safety Program Plan

3.6.2 System Safety Hazard Analysis (SSHA) Report

The Contractor shall prepare a system safety hazard analysis report (DI-SAFT-80101C) and submit it to the Government within 60 days

10 31

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

after LRIP Option 1 award in accordance with MIL-STD-882E, which shall be used as a guide to establish severity and probability levels for all hazards that are assessed. The SSHA shall be used as an integral part of the IPT activities. The system safety hazard analysis shall address both hardware and software safety as an integral part of the overall system safety effort. The analysis shall include a design compliance analysis with respect to MIL-STD-1901 and MIL-STD-1316, as applicable. The analysis performed shall include an initial hazard analysis, follow-on system hazard analysis, and detailed analysis (including quantified Fault Tree Analysis (FTAs) and Failure

Mode, Effects, and Criticality Analysis (FMECA)) to estimate the safety system failure rate, identify any single-point or credible failure modes, and to meet the safety requirements of the cartridge and programming unit Performance Specifications, MIL-STD-1901, and

MIL-STD-1316, as applicable. Documentation to be provided as part of the system safety hazard analysis report shall include, but will not be limited to, system hazard analysis and detailed analysis, including quantified FTAs and FMECA. The SSHA risks shall be presented at program reviews.

Reference CDRL - A013 System Safety Hazard Analysis Report (SSHAR)

3.6.3 Accident/Incident Reports

The Contractor shall report immediately to the Contracting Officer and Government Program IPT any major accident/incident (including fire) resulting in any one or more of the following: one or more fatalities; one or more disabling injuries; damage of Government property exceeding $10,000; affecting program planning or production schedules; degrading the safety of equipment under contract, such that personal injury or property damage may be involved; identifying a potential hazard requiring corrective action. The Contractor shall prepare a report (DI-SAFT-81563) for each incident/accident within 14 days after each occurrence.

Reference CDRL - A014 Accident/Incident Report

3.6.4 Safety Assessment Report (SAR)

The Contractor shall prepare a SAR (DI-SAFT-80102C) to evaluate the risks associated with testing/demonstrating a system at a Government facility. The SAR shall identify all safety features of the system, all related hazards associated with testing/demonstration, and the mitigations (procedures, precautions, etc.) required to minimize risks and safely conduct testing. The SAR shall contain range safety data (e.g. recommended Surface Danger Zone). The SAR shall contain results from the Contractors safety assessments, hazard analyses, and testing. MIL-STD-882E can be used for guidance. A SAR shall be submitted for each unique configuration to be tested/demonstrated at a

Government facility. This may require preparation and delivery of more than one SAR. SARs shall be prepared and submitted to the

Government 60 days prior to Government sponsored test events (e.g. DET-1, DET-2, and DT&E).

Reference CDRL - A015 Safety Assessment Report (SAR)

3.6.5 Software Safety

3.6.5.1 Software System Safety (SSS)

Software system safety shall be an integral part of the system safety program. This program shall fully support the existing system safety engineering program and functionally link software architecture to hazards and their failure pathways. The Contractor shall conduct a SSS program in accordance with MIL-STD- 882E, JSSSEH, AOP-15, and AOP-52, as applicable. AOP-52 shall be used as guidance on

SSS design and assessment of munition-related computing systems. AOP-52 defines an end-to-end process for ensuring safety-critical software is properly identified and handled from design and development through production and beyond. It provides guidelines to achieve a reasonable level of assurance that software and software-like devices will behave within a munition system context and operational environment with an acceptable level of risk. The Contractors software technical specialists as well as sub-Contractors, to include system safety and SSS specialists, shall support the SSS effort as required, including support of a Software System Safety Working Group

(SSSWG). The Contractor shall present the software design to members of the SSWG and Army Fuze Safety Review Board (AFSRB) (DI-MGMT-

81373) during EMD to gain concurrence on any safety-critical software in the Contractors design. All software safety analysis shall be conducted and made available to support the goals, objectives, and schedule of the parent system safety program.

Reference CDRL - A040 AFSRB Briefings

3.6.5.2 Software System Safety Program Plan (SSSPP)

The Contractor shall develop a SSSPP, which shall be included with the SSPP. In the SSSPP, the Contractor shall address the design implementation in order to show that the software is not safety-critical. The SSSPP shall address integration of SSS within system safety, the software development process, planned safety activities, and safety certification of the software. The SSSPP shall address all software used in the system, including NDI, COTS, and reuse software, as well as firmware and software embedded in programmable logic devices. The SSS process shall incorporate the software life-cycle process, including the analysis of the architecture, code peer reviews (such as unit-level and system-level coding), integration of hardware and software, verification and validation of safety critical code, and configuration management control. Incorporating the hazards and mitigations identified by these software activities shall be included in the overall hazard tracking system. The Contractor shall gain Government approval prior to using any software programming languages or software programming language style guides within the system.

3.6.5.3 Safety Significant Software

Safety significant software is a term applied to a condition, event, operation, process, or item that…