DRAFT LRIP-FRP SOW.docx

Statement of Work for the Integrated Air & Missile Defense (IAMD) Integrated Fires and Mission Command (IFMC) Low Rate Initial Production/Full Rate Production (LRIP/FRP)

Version 5 December 2019

PREPARED BY:

IAMD Project Office

ATTN: SFAE-MSL-IA

Redstone Arsenal, AL 35898-5710

Table of Contents

W31P4Q-08-C-0418 Attachment 0001-IBCS SOW

FOR OFFICIAL USE ONLY

W31P4Q-20-R-0015 LRIP/FRP

INTRODUCTION

This Statement of Work (SOW), referred to herein as the Integrated Fires Mission Command (IFMC) System Of Systems (SoS) Hardware Low Rate Initial Production/Full Rate Production (FMC HW LRIP/FRP) SOW, is the primary document to support the IFMC hardware end item production for the Production and Deployment phase of the IAMD program.

SCOPE

This requirement is a Hardware production effort, but also requires maintaining approved software & firmware updates, cybersecurity, Authority to Operate, etc. on existing hardware components; as well as, any engineering changes executed in the performance period of this effort. This IFMC SoS HW LRIP/FRP segment is to build to print the IFMC SoS hardware end items via the supplied Technical Data Packages. In addition, discrete efforts to include new interface and integration efforts may be added by the Government and negotiated on a case-by-case basis and may cover program management, systems engineering, IFMC hardware and software end items modifications, integration, manufacturing readiness, test, logistics, cybersecurity, or any other effort required to support program objectives.

Potential new interface and integration opportunities pending Army priorities will be addressed via Engineering Change Proposals (ECPs). These efforts may include, but are not limited to the list incorporated into the AIAMD Requirements Prioritization 1-n Table, dated 20190911(Attachment 01).

Additionally, the IFMC HW LRIP/FRP requirements incorporate a collaborative approach to integration/test at the SoS level where IFMC Hardware and Software must integrate and perform in a cohesive and synchronous manner; the Government will provide oversight on this collaborative approach at the SoS level.

The current IFMC SoS Unit Configurations are as follows (reference only):

Quantity per Echelon

IFMC Battalion (BN)

IFMC BN Totals

IFMC Composite BN

IFMC Composite BN Totals

IFMC IFPC BN

IFMC IFPC BN Totals

Table 1: IFMC SoS Unit Configurations

BACKGROUND

The AIAMD SoS program provides the capability to enable Integrated Fires and Mission Command (IFMC), sensors, and weapons on an Integrated Fire Control Network (IFCN). The program supports Air and Missile Defense (AMD) operations (e.g., air defense, airspace management, fire control, identification, surveillance, weapons control, and IFCN operations) across all Air Defense Artillery (ADA) echelons, and with Unified Action Partners (UAP). AIAMD SoS provides several new additional capabilities: the IFCN relays, and Plug and Fight (P&F) kits that integrate legacy systems Major End Items (MEI). Network enabled IFMC allows ADA command nodes the ability to use data from organic and non-organic sensors to support engagements by ADA systems. The Integrated Defense Design allows commanders and staff at all echelons to develop, evaluate, store, and implement plans that integrate all ADA components while P & F allows dynamic tailoring of IBCS, sensors, and weapons within the network as changes occur during operations. This ability to in real time integrate multiple data sources enables the development and utilization of advanced engagement concepts which expand the footprints and capability of systems which historically operated independently potentially enable engagements of tracks that are not held by the interceptor's organic sensor. A key enabler for maneuver forces is the integration of IFMC into Air Defense Airspace Management (ADAM) Cells at Brigade Combat Team (BCT), Corps, and Division.

NOTE: HW end items previously referred to as the IAMD Battle Command System (IBCS) will now be referred to herein as IFMC.

NOTE: Radio Frequency Set is also known as Integrated Fire Control Network (IFCN) Relay

The IFMC SoS is made up of four components:

1. Engagement Operations Center (EOC), the Army AMD integrated fire control center provides AIAMD command, staff and engagement functions;

2. Integrated Fire Control Network (IFCN) Relay, IFC network with Tactical Mast Trailers equipped with IBCS B-side adaptation kits;

3. IFMC Software, Common Warfighter Machine Interface (CWMI);

4. Adaptation Kits (A-Kits), Adapts legacy sensors/shooters to the IFCN (Sentinel, PATRIOT, IFPC/Avenger etc.).

APPLICABLE DOCUMENTS

Applicable top level documents cited in this SOW are identified by number, version, title, date, and category in the Document Summary List (DSL). The document versions specified on the DSL take precedence over the generic references (without revision letters) cited in the SOW.

REQUIREMENTS

General Requirements The contractor shall provide the necessary services, personnel, labor, facilities, materials, supplies, and equipment necessary to perform the requirements of this SOW which include the following:

a. The contractor shall design, procure, build, fabricate, integrate, test and deliver IFMC systems IAW Army Integrated Air and Missile Defense (AIAMD) System of Systems (SoS) (MIS-PRF-56500)(Attachment 02), IFMC Technical Data Package (TDP) and this SOW.

b. The contractor shall ensure each end item is interoperable with all other IFMC SoS.

c. The contractor shall review/inspect each supplier/vendor to ensure materials procured for IFMC meets TDP specification and requirements. The contractor shall provide a continuous improvement plan which addresses Pre-Planned Product Improvements (P3I) and Unplanned Product Improvements. The contractor shall provide recommendations to take advantage of new technology and maximizes the use of Army and/or DoD standard components to deliver increased capability, supportability, and survivability of the IFMC SoS.

d. The contractor shall deliver deltas (new or modified TDP elements developed as a result of this contract)to the Government provided TDP for all variants of the IFMC SoS. The delta (new or modified TDP elements developed as a result of this contract) drawing package shall include all drawings necessary to integrate the IFMC SoS into design and manufacturing.

e. In addition, the Contractor shall provide the engineering, production (including facilities, tools/tooling, fabrication, and manufacturing equipment), and test engineering support; touch labor to support the requirements of the program office. This will include, but not limited to, support to logistics, test, quality, production, systems engineering, hardware, program management, obsolescence, cyber security, and software.

f. The contractor shall manufacture IFMC SoS components to support Army echelon from Platoon through Corps. The manufacture will include procuring, fabricating, and integrating the various components and subsystems in quantities specified in Attachment 03, to satisfy the requirement for the IFMC SoS capability.

g. The contractor shall participate with the USG Agile SW Development Process for synchronization and coordination purposes. The contractor will not be responsible for actual SW development however, the efforts required to ensure the HW, USG SW, and Operating System and Infrastructure Version (OIV)/Fire Control Network (FCN) Firmware activities are aligned and synchronized with Agile SW as follows:

• The contractor shall participate in periodic synchronization meetings in order to align milestones with overall solution objectives. This synchronization will take place at least once per quarter, preceding the Program’s PI Planning (Program Increment Planning) event. At the Pre-PI planning synchronization, the vendor will brief their progress towards upcoming milestones.

• The contractor shall present their accomplishments and provide feedback on the demonstrations of other suppliers and Agile Release Trains (ARTs) at the [one-day] quarterly Inspect and Adapt Workshop and Solution Demonstration event.

• The contractor shall participate in the quarterly 2-day Program Increment Planning event.

Engagement Operations Center (EOC) The Contractor shall fabricate, assemble, integrate, test and deliver the EOC IAW the product TDP.

Engagement Center Trailer (ECT) The contractor shall use Tobyhanna Army Depot via a Public/Private Partnership subcontract to build the ECT IAW the product TDP. The government will provide Environmental Control Unit (ECU), Generator, and Trailer to the contractor. The contractor shall utilize drawing ALH-215170 in order to build the ECT. The contractor shall evaluate and recommend ECT load plan changes per attached load plan. The contractor shall update and make available Load Plan and Emplacement Timeline analysis Documentation as part of TDP and Logistics Product update.

Integrated Collaborative Environment (ICE) The Contractor shall fabricate, assemble, integrate, test and deliver the ICE IAW the product TDP.

Integrated Fire Control Network (IFCN) Relay The Contractor shall fabricate, assemble, integrate, test and deliver the IFCN Relay IAW the product TDP.

Software Integration The contractor shall integrate Government Furnished IFMC software configuration items onto the hardware configuration items prior to delivery. Functional testing shall be accomplished with Government provided Test Equipment or Contractor developed Test Equipment. For discrepancies between the contractor provided hardware and the Government Furnished IFMC software configuration items, the contractor shall support and aid in the troubleshooting process to ensure integrated system functionality.

Over and Above (O&A) & Engineering Services for Elective Improvements The contractor shall furnish Over and Above (O&A) engineering, operations and support labor and material necessary for unscheduled repair, servicing, modification, component replacement, and for Government activities, missions, and acts not under the direction of the contractor. Below are examples of O&A type requirements:

(a) Government accidents or incidents;

(b) Results of war or contingency;

(c) Government-directed inspections;

(d) Service Bulletin (SB);should

(e) Safety Communiqué (SC);

(f) Government-approved operations support;

(g) Technical or Programmatic studies;

(h) Pre-Planned Product Improvements (P3I)

5.7.1The contractor will execute engineering services for elective improvements as requested by the Government and negotiated on a case-by-case basis prior to production. Elective improvements will also include program management, systems engineering, IFMC hardware end items modifications, integration, manufacturing readiness, test, logistics, and IFMC support in response to changes deemed necessary to achieving a positive full rate production decision. The Contractor shall maximize the utilization of standard Army common components throughout design, development, production and integration for these elective improvement. The contractor shall perform special studies as requested by the Government (e.g. design trade studies, cost benefit analyses, and CS&S maintenance/upgrade plans).

Detailed Requirements Program and Financial Management Program Management Review (PMR)

The contractor shall conduct a semi-annual PMR to provide the Government with an update of the contract performance including cost and schedule. The contractor shall document the minutes of the Review IAW DI-ADMN-81250 (CDRL A001).

Post Award Conference

The contractor shall participate in a post award conference no later than 30 calendar days after award. The contractor shall work together with the Government as part of the IPT process to develop the post award conference agenda for concurrence by the Government program lead seven (7) days prior to the conduct of the conference.

Integrated Product Team (IPT) The contractor shall participate in a Program Management IPT weekly and provide minutes. The contractor shall document the minutes of the meetings IAW DI-ADMN-81250 (CDRL A001). The contractor shall conduct a weekly Production IPT with an emphasis on the Production and Quality requirements defined in this SOW.

Reports Earned Value Management System (EVMS) The contractor shall establish, maintain, and use in the performance of the task order/contract, an integrated performance management system. Central to this integrated performance management system shall be a validated Earned Value Management System (EVMS) in accordance with Defense Federal Acquisition Regulation Supplement (DFARS) 252.234-7001, DFARS 252.234-7002, and the EVMS guidelines contained in ANSI/EIA-748. To establish the integrated performance management system, the EVMS shall be linked to and supported by the contractor’s management processes and systems to include the integrated master schedule, quantifiable backup data, contract work breakdown structure, change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes should provide for early indication of cost and schedule problems, and their relation to technical achievement as documented in the Integrated Program Management Report (IPMR) IAW DI-MGMT-81861 (CDRL A002). The contractor shall prepare, maintain and update, a Contractor Work Breakdown Structure (CWBS) and CWBS dictionary IAW DI-MGMT-81334 (CDRL A003) using the IAMD (Work Breakdown Structure) WBS and WBS Dictionary (Attachment 04). A common WBS will be used for IPMR, Integrated Master Schedule, and Cost Reporting Plan (Attachment 05). Each contract type will be evaluated separately for IPMR implementation. If level of effort tasks are excluded from the schedule, the contractor shall clearly document in an appropriate location how the cost and schedule for LOE effort is being planned and performance is being measured. The contractor shall flow down earned value management reporting requirements to subcontractors that, based on risk, schedule criticality, and dollar value, have the potential to impede the successful completion of the program. For applicable LRIP Delivery Order efforts, IPMR formats 1(WBS structure), 5(analysis), 6(Integrated Master Schedule (IMS)), and 7(Historical file) may be tailored as part of the Delivery Order requirements.

Project Status Report The contractor shall prepare Program Management reports, including the Project Status Report IAW DI-MGMT-80368 (CDRL A004).

Contractor Cost Data Report (CCDR) The contractor shall systematically collect and report actual contract costs provided to DoD. The contractor shall prepare and submit the Cost and hour Report, also known as the “FlexFile”, the associated Quantity Data Report and the associated Technical Data Report. The reports shall be submitted IAW DI-FNCL-82162 (CDRL A005) Cost and Hour Report (FlexFile), DI-MGMT-82164 (CDRL A006) Quantity Data Report, DI-MGMT-82165 (CDRL A007) Technical Data Report, and DI-FNCL-82765 (CDRL XXXX) Contractor Business Data Report. The contractor shall require and flow down the requirement for CCDR reporting from subcontractors at any tier with a subcontract that exceeds $50 million or any subcontracts valued between $20 million and $49 million that are designated by the Government as being high risk, high value, or high technical interest. For subcontracts that exceed $50 million, or if the Contractor changes subcontractors or makes new subcontract awards, the contractor shall notify the Government.

Contract Funds Status Report (CFSR) The contractor shall prepare a Contract Funds Status Report IAW DI-MGMT-81468 (CDRL A009).

Contractor Manpower Reporting The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor shall report all contractor manpower (including subcontractor manpower) required for performance of this contract. The contractor shall completely fill in all the information in the format using the following web address: https://www.ecmra.mil. The required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer’s Representative (COR); (2) Contract Number, including task and delivery order number; (3) Beginning and ending dates covered by the reporting period; (4) Contractor name, address, phone number, e-mail address, identity of contractor employee entering data; (5) Estimated direct labor hours (including sub-contractors); (6) Estimated direct labor dollars paid this reporting period (including sub-contractors); (7) Total payments (including sub-contractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different); (9) Estimated data collection cost; (10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purpose of reporting this information); (11) Locations where contractor and sub-contractors perform the work (specified by zip code if in the United States and nearest city, or country, when it is an overseas location, using standardized nomenclature provided on the website); (12) Presence of deployment or contingency contract language; and (13) Number of contractor employees deployed in theater this reporting period (by country). As part of its submission, the contractor will provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period shall be the period of performance not to exceed 12 months ending 30 September of each government fiscal year and must be reported by 31 October of each calendar year.

Risk Management The contractor shall implement a Risk Management Program that addresses cost/affordability, schedule, technical, performance, and reliability risk management IAW the IAMD Risk Management Plan (Attachment 06), and develop Risk Reports IAW with DI-MGMT-81809 (CDRL A010).

Government Furnished Property (GFP) Accountability and Reporting The contractor shall create and maintain records of all property accountable to the contract, clearly identifying between Government Furnished Materiel (GFM) and Contractor Acquired Property (CAP).

The contractor shall perform property administration IAW FAR 52.245-1, Government Property, to manage and account for Government property accountable to the contract and track them in the Government approved web-based management information system. The contractor shall identify and inventory Government property accountable to the contract by Item Number, Item Description or Nomenclature, Quantity, Unit of Issue, Part Number/National Stock Number, Serial Number, and Location by Work Breakdown Structure (WBS) and deliver physical inventory results IAW DI-MGMT-80441 (CDRL A011).

The contractor shall account for all excess and/or shortages of GFM and request disposition instructions via the Plant Clearance Automated Reutilization Screening System (PCARSS) IAW DFARAS 252.245.7004. During the IPT, the contractor shall provide status of excess or shortage of GFM.

Subcontracting Opportunities The contractor shall submit a list of small business subcontractors IAW DI-MGMT-80368 (CDRL A012) which include the details of how the contractor will use those subcontractors in performing the contract. Also as part of its subcontracting plan, the contractor shall partner with Army Depot(s) in the form of a Public/Private Partnership (PPP) and allocate subcontract work to the Depot(s) as appropriate. The contractor shall identify work allocated to the Depot(s).

The Contractor shall submit to the Procuring Contracting Officer (PCO) a report that documents (at least quarterly) how the contractor is adhering to or exceeding their proposed utilization of its small business subcontractors. The PCO will use this report in determining an overall Contractor Performance Assessment Reporting System (CPARS) rating for subcontracting management by the contractor.

The Contractor shall coordinate with the PCO if small business firms identified in the list of subcontractors are substituted for or not use during the quarter. The Contractor must attempt to find like/similar small business firms matching the socio-economic categories identified in the original list of small business subcontractors when replacing/substituting small business subcontractors from the list. The PCO must agree with any small business subcontractor substitutions requested by the contractor prior to those replacement subcontractors performing any work on this contract.

Contractor shall make a good faith effort to find opportunities for small business subcontractors in the performance of this contract. The Contractor shall contact the local Procurement Technical Assistance Center (PTAC), the local Office of Small Business Programs, and use the Small Business Dynamic Search Website to assist in finding small business subcontractors that are capable of performing the work to be subcontracted.

For large business firms with an approved Comprehensive Subcontracting Plan, Federal Acquisition Regulation (FAR) Part 52.219-16, Liquated Damages, will not be part of the resultant contract; however not adhering to or utilizing your proposed list of small business subcontractors may result in a negative CPARS rating.

Contractor shall support small business opportunities throughout the period of performance of the contract. Contractor shall make a good faith effort in identifying opportunities for small business subcontractors including all socio-economic small business categories. Contractor shall make a good faith effort to meet or exceed their proposed subcontracting goals/targets as list in their proposed subcontracting plan. Prior to the completion of the next quarter, the Contractor must submit an explanation in writing, if they cannot meet their proposed subcontracting plan goals/target. The list of subcontractors shall be submitted with the proposal and revisions to the list may be made, with approval of the PCO, throughout the period of performance of the contract. The list of subcontractors will become part of the resultant contract once accepted by the PCO.

The contractor shall comply with FAR 52.244-5 Competition in Subcontracting. This clause reads as follows: “(a) The Contractor shall select subcontractors (including suppliers) on a competitive basis to the maximum practical extent consistent with the objectives and requirements of the contract.” As part of the list of subcontractors IAW DI-MGMT-80368 (CDRL A012), the contractor shall report the level of competition in subcontracting achieved or percent of subcontracts that are competed.

Reviews Preliminary Design Review (PDR) The contractor shall conduct a PDR in as part of the ECP process. The contractor shall propose and the Government will approve the entry and exit criteria. The contractor shall provide: preliminary material selections; design tradeoffs; the decision rationale for design solutions to functional and technical requirements for; the ability of design concepts to meet performance specification requirements; and the contractor path for completing a design that meets all contractual and performance requirements for Government evaluation. Additionally, splinter sessions will be held with the various functional areas in order to further review specific areas of interest, which may include logistics/training materials, Failure Reporting, Analysis, and Corrective Action System (FRACAS), test plans, product assurance plans, reliability, configuration management, engineering data products, and safety/environmental issues. The contractor shall provide written notice to the Government of its readiness to hold a PDR 30 days prior to the event. The Government will provide written notification of the contractor’s readiness to hold the PDR. The contractor shall proceed into detail design upon Government approval.

Critical Design Review (CDR) The contractor shall conduct a CDR as part of the ECP process. The contractor shall propose and the Government will approve the entry and exit criteria. The contractor shall provide: critical material selections, design tradeoffs, and baseline design for Government evaluation. The contractor shall demonstrate the design meets all contractual and performance requirements. Additionally, splinter sessions will be held with the various functional areas in order to further review specific areas of interest, which may include plans and procedures, logistics/training/provisioning, test, product assurance, configuration management, engineering, safety and environmental. The contractor shall provide written notice to the Government of its readiness to hold a CDR 30 days prior to the event. The Government will provide written notification of the contractor’s readiness to hold the CDR. The contractor shall proceed into production and integration of production representative systems upon government approval.

Technical Interchange Meetings (TIMs) The contractor shall participate in TIMs at a rate of at least two (2) per month alternating between PM and the contractor's facility. These TIMs shall be held in conjunction with other formal reviews as scheduled and shall be for resolution of requirements, technical, or process issues.

Integrated Program Reviews (IPRs) The contractor shall prepare for and participate in IPRs with Government program personnel on a quarterly basis. The reviews shall cover the latest status of overall contract effort with emphasis on problems and achievements in all program areas to include the following: program metrics, costs, schedules, Technical Performance Measures (TPM)s, requirements verification, operational suitability, interoperability, and risk. IPRs shall be conducted in conjunction with other program reviews when achievable.

Design Reviews The contractor shall participate in a Design Review for all new or modified IFMC hardware end item and associated Line Replacement Unit (LRU). The contractor shall propose and the Government will approve the entry and exit criteria. The contractor shall identify and inform the Government of any system performance impacts for the new or modified hardware end item. The contractor shall identify and inform the Government at Design Review of all firmware changes resulting from incorporation of new or modified HW end item. The contractor shall identify and present resulting firmware changes to the Government for adjudication and possible submittal as a software Configuration Items (CIs) that may affect OIV/FCN or the IFMC SW application. If HW end items and firmware changes are necessary, the contractor shall follow the ECP process defined in the Configuration Change Management section of this SOW.

Test Readiness Reviews (TRRs) The contractor shall perform TRRs with government participation at the contractor test facility prior to that start of any Acceptance Test (AT). The TRR shall address all items potentially affecting readiness for test and inspection. The contractor shall address test configuration status, and items that affect evaluation and interpretation of test data and results. During the TRR the contractor shall validate that the entrance criteria has been met for the tests. TRRs shall be conducted NLT 5 working days prior to the AT.

Integrated Baseline Review (IBR) The contractor shall prepare for and participate in an IBR within 60 days after Contract Award (CA). The IBR focuses on assessing the realism of the contractor’s integrated Performance Measurement Baseline (PMB) and the appropriateness of the Earned Value methodology to be employed under the contract. Incremental IBRs shall be conducted as determined by the Government throughout the life of the contract. IBRs shall also be conducted on subcontracts that meet or exceed the EVM application threshold. The prime contractor shall lead the subcontractor IBRs, with active participation by the Government.

System Engineering The contractor shall execute the system engineering activities and reviews necessary to perform the effort defined in this PWS. These activities and reviews shall be scheduled on the Integrated Master Schedule (IMS). The engineering products shall be in formats, tools, and databases that conform with those of the Government. The contractor shall conduct performance analysis of designs using Government approved engineering tools to include, but not limited to, IAMD Simulation Software (IAMDSIM). The contractor shall use the Government – System Integration Laboratory (G-SIL) or other specified Government led integration facility for performance analysis and test assessments. The contractor shall analyze the IFMC SoS for technology insertion upgrades, capability upgrades, improved supportability, and standardization across all echelon levels. The contractor shall design hardware versions that support the Army’s network centric plug and fight concept, with upgraded networking equipment and communications assets including radio suites and software applications appropriate for the echelon level, automated data processing equipment, tactical power, and video distribution equipment that are logistically supported. The hardware design upgrades shall be capable of incorporating major software systems currently used in air defense operations.

Performance Management

Configuration Management (CM) General The contractor shall establish and implement a CM program to manage the configurations provided under this contract. The program shall consist of configuration identification, configuration change control, configuration audits and reviews, configuration status accounting and data management. The contractor shall prepare and deliver CM Plan (CMP) IAW DI-SESS-80858 (CDRL A013).

Configuration Documentation (CD) The contractor shall prepare and deliver updates to interface control documents (ICDs) IAW DI-SESS-81248 (CDRL A014). The contractor shall prepare and deliver updates to system and subsystem specifications IAW DI-IPSC-81431 (CDRL A015). The contractor shall prepare and deliver updates to the technical data package (TDP) IAW DI-SESS-80776 (CDRL A016) and MIL-STD-31000 (See TDP Option Selection Worksheet).

Commercial and Government Entity (CAGE) The contractor shall ensure CAGE codes assigned by the Government appear on all drawings and specifications. The contractor shall use Government part numbers for all items developed under this contract.

Use of Existing Data The contractor shall ensure existing Government data are screened and selected for use IAW the requirements of this contract prior to the preparation of new CD.

Configuration Change Management Government Controlled CD The contractor shall only change the Government-controlled CD as a result of a Government approved Engineering Change Proposal (ECP). ECPs apply to hardware and firmware changes. The contractor shall prepare an ECP only after the Government has authorized preparation by an approved Change Request or by Government direction. The contractor shall prepare and deliver ECPs IAW DI-SESS-80639 (CDRL A017) with Notices of Revision (NORs) prepared IAW DI-SESS-80642 (CDRL A018). The contractor shall document all revised Government-controlled CD on an Engineering Release Records approved by the Government. The contractor shall prepare and deliver ERRs IAW DI-SESS-80463 (CDRL A019).

Request for Variance (RFV) Any deviations from the Government controlled documentation shall require the contractor generation and Government approval of an RFV. The contractor shall prepare an RFV IAW DI-SESS-80640 (CDRL A020) against Government controlled documentation.

Serialization, Lot and Block Control The contractor shall serialize using Government approved serial numbers. The contractor shall use approved Government serialization for each hardware CI. For lower level assemblies and components, the contractor shall develop and implement a system for serialization and lot control IAW the IFMC CMP. The contractor shall use this program for manufacturing, identification of required hardware, and lot and block control of hardware to be delivered under this contract.

Configuration Audits and Reviews Physical Configuration Audit (PCA) The contractor shall conduct PCAs / Delta PCAs for all major subassemblies at the time of the first article inspection to validate the PBL documentation. The contractor shall conduct an IFMC system level PCA to validate the final PBL documentation for each end product. The contractor shall prepare an IFMC PCA Plan IAW DI-SESS-81646 (CDRL A021).The contractor shall prepare a PCA Report IAW DI-SESS-81022 (CDRL A022). The Government may choose to co-chair all audits as a voting member.

Configuration Status Accounting (CSA) The contractor shall perform a CSA function IAW the contractor's Government approved IFMC CMP. The CSA data and information shall be recorded and reported for all CD. The CSA system shall depict the as-designed, as-built, and as-modified configurations and shall be indexed for ready reporting and retrieval. The contractor shall provide the Government with on-line access to the CSA system.

Data Management The contractor shall implement a data management program to control and track the delivery of data items required by the CDRL, DD Form 1423. The contractor shall host a Government accessible website to use for the on-line delivery of all CDRL items and deliver CDRLs formally to the Government via a Government hosted website.

Data Submission The contractor shall submit all data items according to the instructions stated on the DD Form 1423. The contractor shall ensure that the content of these electronic data items is IAW the Data Item Description, as tailored by the DSL.

Data Accession List The contractor shall prepare a Data Accession List (DAL) IAW DI-MGMT-81453 (CDRL A023) of all documentation developed as part of the effort. The contractor’s CM office shall provide individual documents listed on the DAL at the Government’s request. Upon notification from the Procuring Contracting Officer, the contractor shall furnish a copy of any DAL Requested Documentation IAW DI-MISC-80508 (CDRL A024).

Distribution Statements and Export Control Warning The contractor shall mark data items IAW DODI 5230.24. The contractor shall use the distribution statements and export control warnings identified in the CDRLs identified in the SOW.

Data Item Master Schedule The contractor shall provide a Schedule for Data Items IAW DI-MISC-80508 (CDRL A025). The contractor shall ensure the schedule details the previous month's submittals and data items forecasted to be delivered for the following month.

Environmental, Safety, Occupation and Health

IFMC Safety and Health Support The contractor shall provide a Safety and Health subject matter expert to conduct the following activities:

· Maintain safety-significant requirements/traces in DOORS.

· Track/assess/resolve safety-significant trouble reports.

· Verify safety-significant functionality via Level of Rigor (LOR) testing.

· Maintain/update Hazard Tracking System database.

The contractor shall deliver an updated IFMC Safety Assessment Report (SAR) IAW DI-SAFT-80102 (CDRL A026), to include as attachments: Hazard Tracking System Logs; Fault Tree Analysis (or equivalent level of detailed safety analysis) for catastrophic and critical hazards related to Radio Frequency (RF) emissions or activation of ordnance; System Safety Risk Assessments (SSRA); and, Legacy system SARs that are deemed still applicable to IFMC aligned with LRIP/FRP and address design updates to hardware end items. Update and keep current a Hazard Tracking System (HTS) database to document, track, and manage all hazards identified during design, development, and test activities. The contractor shall prepare and implement an updated IFMC System Safety Program Plan (SSPP) IAW DI-SAFT-81626 (CDRL A027), AMCOM Policy 385-17 and MIL-STD-882. The contractor shall deliver an updated Health Hazard Assessment Report IAW DI-SAFT-80106 (CDRL A028) and AR 40-10. The contractor shall update, delivery, and implement the Hazardous Materials Management Program (HMMP) Plan IAW DI-MGMT-81398 (CDRL A029). The contractor shall deliver updated HMMP Reports IAW DI-MISC-81397 (CDRL A030) for major updates to hardware end items. The HMMP Reports shall identify via graphic or drawing of the specific location of each hazardous material contained in the final end item(s). The Government will access and determine major updates based on form, fit and function architecture changes as well as if the change affects OIV/FCN and IFMC SW.

Environmental All contractor and subcontractor activities shall be in compliance with applicable federal, state and local environmental laws and regulations.

The Contractor shall report the data elements found in MIL-STD-882, Task 108, section 108.2.4 a, b, and d for Tracked HAZMATs. The contractor shall report coatings (identified by MIL SPEC), functional fluids (e.g. coolant, hydraulic fluid, lubricants, etc.), radionuclides (40 CFR 302.4, Appendix B) and energetics/solid rocket motor components (including Explosives Class Number) with the same 108.2.4 a, b, and d data elements. The Contractor shall provide Material Safety Data Sheets (MSDSs) or Safety Data Sheets (SDSs) for all reported materials.

The Contractor shall report any hazardous material, as defined in NAS 411-1, to be used for the maintenance, sustainment, and demilitarization of the end item under this contract. The hazardous material shall be properly identified and include any applicable identification number, such as National Stock Number or Special Item Number. The Contractor hazardous materials list shall be updated during performance of the contract whenever the Contractor determines that any other material to be used in the maintenance, sustainment, and demilitarization of the end item under this contract is hazardous.

The contractor shall not use any Class I or Class II Ozone Depleting Chemical/Ozone Depleting Substance (ODC/ODS), identified by the lists at https://www.epa.gov/ozone-layer-protection/ozone-depleting-substances/, in the manufacture or support of items required by this SOW unless approved IAW Army ODS policy and/or Title 10 United States Code section 2302. All ODS alternatives must be in compliance with the U.S. Environmental Protection Agency (EPA) Significant New Alternatives Policy (SNAP) program and identified as approved – per the specific application – in the lists at https://www.epa.gov/snap/snap-substitutes-sector/.

All ODS alternatives must also receive a Toxicity Clearance for the specific application from the US Army Public Health Center.

Quality Assurance Quality Assurance (QA) Program The contractor shall maintain a quality system IAW current versions of ISO 9001, AS 9100, or equivalent system as agreed between the contractor and the Government. Any exclusion to the contractor’s quality management system shall be agreed to between the contractor and the Government. The contractor shall make available, for review by the Government, quality system procedures, planning, and all other documentation and data that comprise the contractor's quality system. The Government may perform any necessary inspections, audits, or evaluations to confirm conformance to requirements and adequacy of the quality system.

Quality system procedures, planning, and all other documentation and data that comprise the contractor's quality system shall be made available to the Government via the contractor’s CSA system.

Non-Conforming Material Decisions to accept or use nonconforming material (variances from contractor drawings and specifications) require Government notification and approval by the Procuring Contracting Officer (PCO). The contractor shall use its Material Review Board (MRB) process to document, evaluate, and recommend disposition of nonconforming material. Standard Repair Procedures shall be approved by the Government IAMD Performance Management Division (PMD) Chief prior to use. The non-conformance process shall include analyses of nonconforming material to determine root cause, recommendations for and preventive/corrective actions through implementation, and the tracking of nonconforming material dispositions that require a Request for Variance (RFV). The contractor shall include IAMD Project Office (PO) or designee representation on the MRB and shall notify the Government five (5) working days prior to the scheduled MRB. Nonconforming material shall not be given a disposition of “use as is” or “repair” through contractor action without Government approval of a RFV. The contractor shall control the identification, documentation, evaluation, disposition, and segregation requirements of non-conforming products. The contractor shall upon discovery, immediately notify the PCO and IAMD PO of any nonconforming material that exists in previously delivered products. Notification shall include a description of the suspected nonconforming material, potential risk or product impact, contract number, Part Number, National Stock Number (NSN), affected serial numbers, and/or lot numbers when applicable.

Counterfeit Parts Prevention The contractor shall prepare, or update an existing, Counterfeit Risk Management Plan IAW DI-MISC-81832 (CDRL A031). The Counterfeit Risk Management Plan shall meet the requirements of SAE AS5553 for electronic items and SAE AS6174 for non-electronic items. The contractor shall procure parts from original manufacturers or the original manufacturers’ franchised distributors. The contractor shall report counterfeits and suspected counterfeits to the Government and in the Government Industry Data Exchange Program (GIDEP), in accordance with the GIDEP Operations Manual, SO300-BT-PRO-010 and track using a risk mitigation plan or countermeasure to eliminate the problem.

Product Acceptance The contractor shall propose acceptance test criteria from the IFMC System Specifications for Government approval. The contractor shall develop, implement, and maintain an IFMC Acceptance Test Plan (ATP) IAW DI-QCIC-80553 (CDRL A032) and Acceptance Test Procedures IAW DI-NDTI-80603 (CDRL A033) for each hardware end item. The contractor shall perform acceptance testing on all hardware end items prior to delivery to the Government. For vendor/subcontractor supplied COTS items that are to be used as spares, Certificates of Conformance from the supplier are acceptable to satisfy acceptance test requirements. The contractor shall request Government approval for changes to Acceptance Test Plans, Procedures, and associated equipment, to include SIE/STE. The contractor shall notify the Government at least five (5) working days prior to conduct of each Acceptance Test event in order for the Government to witness the testing.

The Hardware end item Acceptance Test event shall:

The ATP results/reports, including supporting documentation and data that comprise the report, shall be made available to the Government via the CSA system.

Failure Reporting, Analysis, and Corrective Action System & Failure Review Board The contractor shall maintain/implement a FRACAS. The contractor shall ensure that all suppliers develop and implement a compatible FRACAS that supports the contractor’s FRACAS. The contractor shall track all hardware, firmware, and OIV/FCN failures to include Government Furnished Equipment (GFE), and shall include Government generated Failure Reports (FR) in the FRACAS. The contractor shall participate in a weekly Failure Review Board (FRB), jointly conducted by the contractor and the IAMD Project Office. The joint FRB will review and assign failures, and the contractor shall present associated failure trend data. Within 45 days after notification from the IAMD Project Office, the contractor shall perform failure analysis on each failure, excluding GFE, and respond to the IAMD Project Office with identification of root cause, a corrective action recommendation, a corrective action implementation and verification plan, and any associated schedule impacts. Requests for extension of this 45 day requirement will be evaluated on an individual basis by the IAMD Project Office. The IAMD Project Office (via the joint FRB) is the approval authority for closing a failure. If there is a discrepancy between the contractor and the IAMD Project Office on failure analysis, etc., and the FRB cannot resolve the discrepancy, the issues will be brought to the Government Contracting Officer and the IAMD executive FRB. The contractor shall support the IAMD executive FRB. The contractor shall apply the FRACAS results into the design, production, and logistics processes. The planned FRACAS approach shall be included in the PPAP (CDRL A034).

Program Product Assurance Plan The Contractor shall develop and implement a Government approved Program Product Assurance Plan (PPAP) IAW DI-QCIC-81722 (CDRL A034), that provides for effective application and integration of Quality Assurance, Reliability, and Parts Management principles and integration with other disciplines such as configuration and data management, systems engineering, design, test and logistics, to ensure the integrity of SoS…