Attachment_0001_LMWS_QRC_SOW_042417.pdf

W58RGZ-17-R-0211

ATTACHMENT 0001

i

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

FOR OFFICIAL USE ONLY

PROJECT MANAGEMENT OFFICE

AIRCRAFT SURVIVABILITY EQUIPMENT

STATEMENT OF WORK

FOR THE

PROTOTYPING AND PRODUCTION

OF

LIMITED INTERIM MISSILE WARNING SYSTEM

QUICK REACTION CAPABILITY

VERSION 1.0

PM ASE Document No.: W6DP01-P-00347

24 APRIL 2017

Prepared by Project Manager for Aircraft Survivability Equipment

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, USC, Sec 2751, et. Seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App 2401 et. Seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DOD Directive 5230.25.

ii

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

REVISION AND HISTORY

Revision Number Date Log of Changes Made and Description of

Reason Changes Approved By iii

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

TABLE OF CONTENTS

1. SCOPE

1.1. BACKGROUND

2. APPLICABLE DOCUMENTS

3. REQUIREMENTS

3.1. GENERAL REQUIREMENTS

3.2. PROGRAM MANAGEMENT

3.2.1. INTEGRATED MASTER SCHEDULE

3.2.2. CONTRACTOR INTEGRATED PERFORMANCE MANAGEMENT

3.2.3. CONTRACT WORK BREAKDOWN STRUCTURE

3.2.4. FINANCIAL REPORTING

3.2.4.1. CONTRACTOR COST DATA REPORTING

3.2.4.2. SOFTWARE RESOURCES DATA REPORTING

3.2.4.3. CONTRACTOR MANPOWER REPORTING

3.2.5. DATA MANAGEMENT

3.2.5.1. PROGRAM DOCUMENTATION

3.2.5.2. DATA SUBMISSION

3.2.5.3. NOTICE OF AVAILABILITY

3.2.5.4. CLASSIFIED CDRL

3.2.5.5. LIMWS WEB SITE

3.2.5.6. METRIC MEASUREMENTS

3.2.6. DISTRIBUTION STATEMENTS AND EXPORT CONTROL WARNING

3.2.6.1. GOVERNMENT SOURCE SURVEILLANCE/INSPECTION

3.2.7. SMALL BUSINESS

3.2.7.1. SMALL BUSINESS SUBCONTRACTING PLAN

3.2.7.2. SMALL BUSINESS OPPORTUNITIES

3.2.8. TRAVEL

3.3. SYSTEMS ENGINEERING

3.3.1. SYSTEMS ENGINEERING MANAGEMENT PROGRAM

3.3.2. SYSTEM ENGINEERING MANAGEMENT PLAN

3.3.3. PROGRAM REVIEWS, TECHNICAL REVIEWS, WORKING GROUPS

3.3.3.1. POST AWARD CONFERENCE/KICKOFF TECHNICAL INTERCHANGE MEETING

3.3.3.2. INTEGRATED BASELINE REVIEW

3.3.3.3. SYSTEM REQUIREMENTS REVIEW

3.3.3.4. PRELIMINARY DESIGN REVIEW

3.3.3.5. CRITICAL DESIGN REVIEW

3.3.3.6. PRODUCTION READINESS REVIEW

3.3.3.7. TECHNICAL INTERCHANGE MEETING

3.3.3.8. PROGRAM MANAGEMENT REVIEW

3.3.3.9. INTEGRATED PRODUCT TEAM MEETINGS

3.3.4. RISK MANAGEMENT

3.3.5. LIMWS SYSTEM DESIGN/DEVELOPMENT

3.3.5.1. TRADE STUDIES

3.3.5.2. SPECIFICATIONS

3.3.5.3. INTERFACE REQUIREMENT SPECIFICATIONS

3.3.5.4. INTERFACE CONTROL DOCUMENTS

3.3.5.5. SYSTEM/SUBSYSTEM DESIGN DESCRIPTION

3.3.5.6. INTERFACE DESIGN DESCRIPTIONS

3.3.5.7. REQUIREMENTS DATABASE

3.3.5.8. DEVELOPMENTAL LEVEL B-KIT TECHNICAL DATA PACKAGE

3.3.6. AIRWORTHINESS

3.3.6.1. AIRWORTHINESS QUALIFICATION SPECIFICATION

iv

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

3.3.6.2. HARDWARE AND SYSTEM TEST REQUIREMENTS

3.3.7. OPEN SYSTEM ARCHITECTURE

3.3.8. HUMAN FACTORS AND HUMAN SYSTEMS INTEGRATION

3.3.9. ENVIRONMENT, SAFETY, AND OCCUPATIONAL HEATLTH

3.3.10. ENGINEERING ANALYSIS FOR INSTALLED PLATFORM

3.3.11. SAFETY AND OCCUPATIONAL HEALTH PROGRAM

3.4. A-KIT DESIGN AND DEVELOPMENT

3.4.1. A-KIT DESIGN

3.4.1.1. A-KIT MATERIALS

3.4.1.2. A-KIT PARTS AND SPECIAL TOOLS

3.4.1.3. A-KIT WIRE HARNESS MARKINGS

3.4.1.4. A-KIT COVER/STOWAGE PLATES

3.4.1.5. ENVIRONMENTAL COVERS FOR INSTALLED SYSTEM

3.4.1.6. EXISTING AIRCRAFT ENVIRONMENTAL COVER MODIFICATION

3.4.2. AIRCRAFT SURVEY

3.4.3. ENGINEERING ANALYSIS FOR INSTALLED PLATFORM

3.4.4. PLATFORM VIBRATION AND THERMAL EVALUATIONS

3.4.5. PRODUCTION LEVEL A-KIT TECHNICAL DATA PACKAGE

3.4.5.1. DRAWING TREE

3.4.5.2. DRAWING REVIEWS

3.4.6. PROTOTYPE INSTALLATION

3.4.7. A-KITS FOR MODIFICATION WORK ORDER DEVELOPMENT AND TEST

3.4.8. CONTRACTOR GROUND TEST PLAN, EXECUTION, AND REPORT

3.4.9. AIRCRAFT-MODIFICATION WORK ORDER

3.4.9.1. AIRCRAFT – MODIFICATION WORK ORDER VALIDATION

3.4.9.2. AIRCRAFT – MODIFICATION WORK ORDER GOVERNMENT VERIFICATION

3.4.10. CONTRACTOR - AIRCRAFT POSSESSION RESPONSIBILITIES

3.4.10.1. AIRCRAFT - CONTRACTOR ACCEPTANCE

3.4.10.2. AIRCRAFT - CONTRACTOR INCOMING INSPECTION

3.4.10.3. AIRCRAFT - HIDDEN DAMAGE

3.4.10.4. AIRCRAFT MAINTENANCE

3.5. SOFTWARE/FIRMWARE

3.5.1. SOFTWARE/FIRMWARE PROJECT MANAGEMENT

3.5.1.1. CAPABILITY MATURITY MODEL INTEGRATION RATING

3.5.1.2. SOFTWARE/FIRMWARE INTEGRATED PRODUCT TEAM SUPPORT

3.5.1.3. SOFTWARE/FIRWARE MANAGEMENT REPORT

3.5.2. SOFTWARE/FIRMWARE DESIGN, DEVELOPMENT, AND TEST

3.5.2.1. SOFTWARE/FIRMWARE DESIGN/DEVELOPMENT

3.5.2.2. PLAN FOR SOFTWARE ASPECTS OF CERTIFICATION

3.5.2.3. SOFTWARE/FIRMWARE DEVELOPMENT PLAN

3.5.2.4. SOFTWARE/FIRMWARE DEVELOPMENT FOLDERS

3.5.2.5. SOFTWARE/FIRMWARE REQUIREMENTS SPECIFICATION

3.5.2.6. SOFTWARE/FIRMWRE DESIGN DESCRIPTION

3.5.2.7. SOFTWARE CODING

3.5.2.8. SOFTWARE CODE WALKTHROUGHS

3.5.2.9. SOFTWARE/FIRMWARE TEST/VERIFICATION PLAN

3.5.2.10. SOFTWARE/FIRMWARE TEST DESCRIPTION

3.5.2.11. SYSTEM INTEGRATION TEST DESCRIPTION

3.5.2.12. SOFTWARE INTEGRATION SUPPORT

3.5.2.13. SOFTWARE TEST READINESS REVIEW

3.5.2.14. SOFTWARE/FIRMWARE TEST TOOLS

3.5.2.15. SOFTWARE/FIRMWARE QUALIFICATION

3.5.2.16. SOFTWARE/FIRMWARE FORMAL QUALIFICATION TESTING

3.5.2.16.1. REGRESSION SOFTWARE/FIRMWARE FORMAL QUALIFICATION TESTING

v

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

3.5.2.17. SYSTEM INTEGRATION TEST

3.5.2.17.1. REGRESSION SYSTEM INTEGRATION TEST

3.5.2.18. SOFTWARE STRUCTURAL COVERAGE ANALYSIS/TESTING

3.5.2.19. SOFTWARE/FIRMWARE QUICK LOOK REPORT

3.5.2.20. SOFTWARE/FIRMWARE TEST REPORTS (SFTR)

3.5.2.21. SYSTEM INTEGRATION TEST REPORT

3.5.2.22. SOFTWARE INTEGRATION LAB INTEGRATION SUPPORT

3.5.2.23. SOFTWARE/FIRMWARE VERSION DESCRIPTION DOCUMENT (SVDD)

3.5.2.24. SOFTWARE/FIRMWARE DELIVERY

3.5.2.25. SOFTWARE ACCOMPLISHMENTS SUMMARY

3.5.2.26. SOFTWARE QUALITY ASSURANCE

3.5.2.27. SOFTWARE/FIRMWARE PROBLEM REPORTS

3.5.2.28. SOFTWARE/FIRMWARE RISK MANAGEMENT

3.5.3. SOFTWARE SAFETY

3.5.3.1. SOFTWARE FAILURE MODES AND EFFECTS CRITICALITY ANALYSIS

3.5.3.2. SOFTWARE SAFETY PROGRAM PLAN

3.5.3.3. SOFTWARE SAFETY CRITICAL FUNCTION ANALYSIS

3.5.3.4. SOFTWARE HAZARD TRACKING LOGS

3.5.4. BUILT-IN-TEST VALIDATION

3.6. MODELING AND SIMULATION

3.6.1. LIMWS DIGITAL SYSTEM MODEL

3.6.1.1. LIMWS DIGITAL SIMULATION MODEL VERIFICATION AND VALIDATION PLAN

3.6.1.2. LIMWS DIGITAL SIMULATION MODEL VERIFICATION AND VALIDATION REPORT . 47

3.6.1.3. LIMWS DIGITAL SIMULATION MODEL BASED PERFORMANCE ASSESSMENTS

3.6.2. HARDWARE-IN-THE-LOOP

3.7. CONFIGURATION MANAGEMENT

3.7.1. CONFIGURATION AND DATA MANAGEMENT AND CONTROL

3.7.2. CONFIGURATION DOCUMENTATION

3.7.2.1. CONFIGURATION DOCUMENTATION LIST

3.7.3. FUNCTIONAL BASELINE

3.7.4. USE OF EXISTING DATA

3.7.5. CLASSIFIED INFORMATION

3.7.6. ALLOCATED BASELINE

3.7.7. PRODUCT BASELINE

3.7.8. ENGINEERING RELEASE RECORD

3.7.9. GOVERNMENT CONFIGURATION CONTROL BOARD

3.7.10. GOVERNMENT CONTROLLED CONFIGURATION DOCUMENTATION

3.7.10.1. SOFTWARE CHANGE REPORT

3.7.11. CONTRACTOR CONTROLLED CHANGES

3.7.12. REQUEST FOR VARIANCE (DEVIATION AND WAIVER)

3.7.13. CONFIGURATION STATUS ACCOUNTING

3.7.14. SERIALIZATION, LOT AND BLOCK CONTROL

3.7.15. PHYSICAL CONFIGURATION AUDIT

3.7.16. FUNCTIONAL CONFIGURATION AUDIT

3.7.17. BUILD AND TEST ENVIRONMENT VERIFICATION

3.8. SYSTEM PERFORMANCE TEST AND EVALUATION

3.8.1. GOVERNMENT TESTING SUPPORT

3.8.1.1. TEST AND EVALUATION EQUIPMENT AND MATERIAL PURCHASES

3.8.2. CONTRACTOR TESTING

3.8.2.1. CONTRACTOR TEST DATA

3.8.2.2. NOTIFICATION TO GOVERNMENT OF CONTRACTOR TEST DATES

3.8.2.3. NOTIFICATION TO GOVERNMENT OF CONTRACTOR TEST FAILURES

3.8.3. TEST AND EVALUATION DOCUMENTATION

3.8.3.1. CONTRACTOR TEST READINESS REVIEWS

vi

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

3.8.3.1.1. GOVERNMENT CREDIT FOR CONTRACTOR TEST READINESS REVIEW

3.8.3.1.2. NON-GOVERNMENT CREDIT FOR CONTRACTOR TEST READINESS REVIEW

3.8.3.1.3. TEST READINESS REVIEW PACKAGE

3.8.3.2. CONTRACTOR TEST PLANS

3.8.3.3. CONTRACTOR TEST REPORTS

3.8.4. TEST AND EVALUATION STRATEGY

3.8.5. TEST HARDWARE AND EQUIPMENT

3.8.5.1. TEST AND EVALUATION PRODUCT DATA RECORDER

3.8.5.2. TEST EQUIPMENT AND HARDWARE FAILURE/REPLACEMENT

3.8.6. CONTRACTOR FLIGHT TEST ENGINEERS

3.9. PRODUCTION

3.9.1. QRC A-KITS

3.9.2. QRC B-KITS

3.9.2.1. ENGINEERING PROTOTYPES

3.9.2.2. INITIAL PRODUCTION

3.9.2.3. PRODUCTION

3.9.3. CRITICAL DESIGN REVIEW MATERIAL PURCHASE PLAN

3.9.4. MANUFACTURING STRATEGY AND PLAN

3.9.5. PRODUCIBILITY

3.9.6. PRODUCTION QUALIFICATION

3.9.7. PILOT PRODUCTION LINES

3.9.8. SPECIAL TOOLS, SPECIAL TEST EQUIPMENT, SPECIAL INSPECTION EQUIPMENT,

AND PECULIAR SUPPORT EQUIPMENT

3.10. QUALITY ASSURANCE PROGRAM

3.10.1. QUALITY MANAGEMENT SYSTEM/PRODUCT ASSURANCE

3.10.2. QUALITY PROGRAM PLAN

3.10.3. PROCESS MANAGEMENT

3.10.3.1. PROCESS VALIDATION PLANNING

3.10.3.2. PROCESS CAPABILITY

3.10.3.3. VARIABILITY REDUCTION

3.10.4. PROCESS VALIDATION

3.10.5. RECORDS

3.10.6. NON-CONFORMING MATERIAL

3.10.7. PRODUCT ACCEPTANCE

3.10.7.1. ACCEPTANCE TEST PROCEDURE

3.10.7.2. ENVIRONMENTAL STRESS SCREENING/HIGHLY ACCELERATED STRESS

SCREENING

3.10.8. EQUIPMENT ACCURACY AND CALIBRATION

3.10.9. GAUGE REPEATABILITY AND REPRODUCIBILITY

3.10.10. MASTER LIST OF EQUIPMENT

3.10.11. PARTS, MATERIALS, AND PROCESSES PROGRAM

3.10.12. ELECTROSTATIC DISCHARGE

3.10.13. FOREIGN OBJECT ELIMINATION/FOREIGN OBJECT DAMAGE AND DEBRIS

PROGRAM

3.10.14. DIMINISHING MANUFACTURING SOURCES MATERIAL SHORTAGES/

OBSOLESCENCE MANAGEMENT

3.10.14.1. REPORTING

3.10.14.1.1. PRODUCIBILITY

3.10.14.1.2. AVAILABILITY (PART AVAILABILITY/DMS REPORT)

3.10.14.1.3. OBSOLESCENCE EVENT

3.10.15. FIRST ARTICLE TEST/PRODUCTION QUALIFICATION TESTING/ PRE-PRODUCTION

VERIFICATION

3.10.15.1. PRODUCT RE-QUALIFICATION

3.11. RELIABILITY PROGRAM

vii

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

3.11.1. RELIABILITY, AVAILABILITY, AND MAINTAINABILITY

3.11.1.1. LIFE CYCLE RELIABILITY, AVAILABILITY, MAINTAINABILITY CONSIDERATIONS ... 64

3.11.1.2. RELIABILITY PROGRAM PLAN

3.11.1.3. SYSTEM RELIABILITY MODEL

3.11.1.4. SYSTEM-LEVEL OPERATIONAL AND ENVIRONMENTAL LIFE-CYCLE LOADS

3.11.1.5. LIFE-CYCLE LOADS ON ASSEMBLIES, SUBASSEMBLIES, AND COMPONENTS

3.11.1.6. IDENTIFY AND CHARACTERIZE FAILURE MODES AND MECHANISMS

3.11.1.7. FAILURE MODES AND EFFECT ANALYSIS/FAILURE MODE EFFECTS AND

CRITICALITY ANALYSIS

3.11.1.8. CLOSED-LOOP FAILURE-MODE MITIGATION

3.11.1.9. FAILURE REPORTING ANALYSIS AND CORRECTIVE ACTION SYSTEM

3.11.1.10. RELIABILITY ASSESSMENT

3.11.1.11. RELIABILITY VERIFICATION

3.11.1.12. MAINTAINABILITY

3.11.1.13. FAILURE DEFINITIONS

3.11.1.14. RELIABILITY, AVAILABILITY, MAINTAINABILITY TECHNICAL REVIEWS

3.11.1.15. OUTPUTS AND DOCUMENTATION

3.11.2. RELIABILITY TESTING

3.11.2.1. RELIABILITY CHARACTERIZATION TESTING

3.12. INTEGRATED LOGISTICS SUPPORT

3.12.1. INTEGRATED LOGISTICS SUPPORT PLANNING AND MANAGEMENT

3.12.2. PRODUCT SUPPORT STRATEGY

3.12.3. CONTRACTOR LOGISTICS SUPPORT ANALYSIS/PLANS AND WHITE PAPERS

3.12.4. GOVERNMENT FURNISHED PROPERTY

3.12.5. PRODUCT SUPPORT PLAN

3.12.6. CONTRACTOR LOGISTICS SUPPORT PLAN

3.12.7. MAINTENANCE

3.12.7.1. MAINTENANCE PLANNING

3.12.7.2. CONTRACTOR MAINTENANCE PLAN

3.12.7.3. LEVEL OF REPAIR ANALYSIS PLAN AND REPORT

3.12.7.4. CORROSION PREVENTION AND CONTROL PLAN

3.12.7.5. TRAINING SUPPORT PACKAGE

3.12.7.6. TRAINING

3.12.8. PROVISIONING AND PUBLICATIONS

3.12.8.1. ENGINEERING DATA FOR PROVISIONING

3.12.8.2. ENGINEERING SUPPORT

3.12.8.3. VERIFICATION SUPPORT

3.12.9. DEMILITARIZATION AND DISPOSAL PLAN

3.12.10. PACKAGING, HANDLING, STORAGE, AND TRANSPORTATION

3.12.10.1. SHIPPING AND STORAGE CONTAINERS

3.12.10.2. TRANSPORTATION OF ASSETS

3.12.11. MARKING FOR SHIPPING AND STORAGE

3.12.12. UNIQUE IDENTIFIER

3.12.13. UNIQUE IDENTIFIER REGISTRY

3.12.14. LOGISTICS DEMONSTRATION

3.13. PROGRAM SECURITY MANAGEMENT

3.14. PROGRAM PROTECTION

3.15. CONTRACTOR DELIVERABLES/REPORTS

APPENDIX A. ACRONYMS

APPENDIX B. PROHIBITED PARTS, MATERIALS, AND PROCESSES

APPENDIX C. QRC PHASE GREEN STRATEGY

APPENDIX D. USG WORK BREAKDOWN STRUCTURE

viii

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

APPENDIX E. TEST ASSETS RESOURCE ALLOCATION CHART

APPENDIX F. CHANGE VERIFICATION MATRIX

APPENDIX G. REQUIREMENTS MATRIX FOR SOW OPTIONS

APPENDIX H. REQUIREMENTS MATRIX FOR SOW OPTIONS

APPENDIX I. ENVIRONMENTAL, SAFETY, AND OCCUPATIONAL HEALTH

APPENDIX J. PROGRAM PROTECTION

LIST OF TABLES

TABLE I. IPTS AND FREQUENCIES

LIST OF FIGURES

NONE

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

1. SCOPE

The overall scope of this Statement of Work (SOW) includes all work to be performed in the basic effort to include engineering and test support, product support planning, the delivery of technical data, and the delivery of prototype and production units of the Limited Interim Missile Warning System (LIMWS) as well as options for additional production. The expression “LIMWS” includes Hardware (HW), Software (SW), Field Programmable Gate Arrays (FPGA), Firmware (FW), associated LIMWS support equipment, technical data and any rights in such data, and LIMWS SW/FW support tools, unless otherwise specified. The Contractor will design the system to meet all requirements as specified in the LIMWS System Performance Specification, ASE-17- 001.

1.1. BACKGROUND

The purpose of the LIMWS Quick Reaction Capability (QRC) is to bridge the gap between the current AAR-57 Common Missile Warning System and next Army threat warning system Program of Record. LIMWS will provide performance beyond the current capabilities of the Common Missile Warning System.

For the LIMWS QRC effort, the Contractor will design, develop, fabricate, integrate, and test the B-Kit for the LIMWS System. The Contractor will design, develop, fabricate, qualify, integrate, and test platform A-Kits for the US Army UH-60M helicopters. The effort will include all engineering and material required for the LIMWS system.

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

2. APPLICABLE DOCUMENTS

Applicable top level documents are contained in the Document Summary List (DSL), Attachment 00XX, attached to this contract, by number, title, and date. The document versions specified in the DSL take precedence over the generic references (without revision letters) cited in this

SOW.

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

3. REQUIREMENTS

3.1. GENERAL REQUIREMENTS

LIMWS’ primary components shall include a suite of mid-wave infrared sensors, the LIMWS System Processor and a Control/Display Unit. Two critical capabilities which must be provided by the sensors include the detection and tracking of Man Portable Air Defense System threats for Missile Warning (MW) and the detection of various forms of hostile fire to provide Hostile Fire Indication (HFI). LIMWS passes MW cues to the Common Infrared Countermeasure (CIRCM) system (not part of the LIMWS system), which utilizes two pointer-tracker assemblies when a threat is detected. LIMWS commands the AN/ALE-47 when a threat is declared. Simultaneously, LIMWS passes MW and HFI audio and display information to the pilot vehicle interface via the Control/Display Unit or through the Aircraft Gateway Processor (AH-64E only).

The Contractor shall design and document the physical, electrical, mechanical, electromagnetic, and environmental interface constraints of the LIMWS System to meet all requirements as specified in ASE-17-001.

The Contractor shall design, develop, integrate, and test platform installation kits (A-Kit) for US Army UH-60M helicopters.

The Contractor shall design, develop, fabricate, integrate, and test the B-Kit for LIMWS.

The Contractor shall utilize an Open System Architecture (OSA) to enable fully functional interfaces with CIRCM and AN/ALE-47 in accordance with their Interface Control Documents

(ICD).

For purposes of this document, all USG notifications shall be submitted in writing to the Contracting Officer (KO) and Contracting Officer Representative (COR).

3.2. PROGRAM MANAGEMENT

The Contractor shall establish and maintain program management practices throughout the period of performance of this effort, including any extensions of the period of performance, either by mutual agreement or the exercise of options. Program management practices shall provide continual visibility into the contractor’s organization and techniques used in managing all aspects of the program, specifically subcontractor and data management. The Contractor shall establish, maintain, and deliver a Program Management Plan in accordance with DI- MGMT-80004A, CDRL A001 for the LIMWS program that provides for the planning and control of costs, risk and schedule, and the measurements of performance. This program management plan shall be presented during the Post Award Conference (PAC). Adherence to schedule and affordability (i.e., cost) on LIMWS will be addressed in the Program Management Plan and status provided during technical reviews.

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

Key personnel, at a minimum, are identified as Program Manager, Project Leads, Lead Systems Engineer, Lead Software Engineer, and Business Lead.

The Contractor shall be responsible for performance of requirements delineated in this SOW.

The Contractor shall institute appropriate management actions relative to subcontractor performance. The Contractor shall develop, maintain, and deliver a Subcontractor Management Plan which describes the management and control procedures for all subcontracts in accordance with CDRL A001. The Contractor shall conduct a business case analysis and justify rationale for desired changes to Program and Subcontractor management plans for submittal to the US Government (USG) per CDRL A001. The Contractor shall flow down and verify compliance with all applicable quality requirements, associated specifications, and any other contractual agreements throughout the supply chain (Line Replaceable Unit (LRU) manufacturers, subcontractors, and suppliers). The USG reserves the right to accompany and observe the Prime contractor’s subcontractor audits and meetings. Additionally the USG reserves the right to review all data and analyses submitted to the Prime contractor by the subcontractor relative to the subcontractor’s performance.

The Contractor shall manage and document procedures and policies for subcontractor and supplier quality. The Program Management Plan shall identify processes for selecting, qualifying and managing subcontractors and suppliers, managing product and processes, flowing applicable quality requirements to subcontractors and suppliers, assessing subcontractor/supplier capabilities, verifying compliance of subcontractors and suppliers, and establishing metrics for continuously monitoring and rating supplier quality performance. The plan shall identify key subassembly manufacturing or processes to be performed by the sub-tier suppliers. The Contractor shall maintain a list of qualified suppliers and the current rating for that supplier. A key process is defined as a process that produces or affects one or more product characteristics that compose the products fit, function; or a process that is susceptible to variability such that the process inputs must be frequently adjusted. The Contractor’s supplier rating system shall be made available for USG review via in-plant reviews or on-line quality system. The Subcontractor Management Plan shall address product acceptance requirements for suppliers and place emphasis on product verification at the supplier level in order to reduce the amount of incoming (receiving) inspection and test. The Contractor shall identify key features, characteristics, and performance requirements to be verified at the component acceptance test level. The Contractor shall develop and have available for USG review, a flow chart showing the supply chain (once subcontractors and suppliers are selected) for the item being manufactured. Manufacturers of any Critical or Key components/assemblies shall be specifically identified on the flow chart.

3.2.1. INTEGRATED MASTER SCHEDULE

The Contractor shall prepare, deliver, and maintain an Integrated Master Schedule (IMS) in accordance with CDRL A002, to include, at minimum, the third level of the Contract Work Breakdown Structure (CWBS). The IMS shall identify all studies, program management, Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document engineering, development, production line activities, production readiness reviews, integration, test, fielding, and sustainment planning activities including asset utilization forecasts, and Government Furnished Property (GFP) requirements. The program schedule shall include all significant events, and a Program Planning Milestone Chart depicting major tasks and events from start to completion of the contract. Program activities shall be represented on the master schedule with linkages to critical paths identified and monitored. A thorough review of the program schedule shall be presented during the PAC. The requirement for the PAC is detailed in paragraph 3.3.3.1. The Contractor shall provide a recommended program schedule, including review and evaluation techniques, which provide for the earliest delivery schedule while at the same time satisfying all requirements in a cost effective manner. The Contractor shall provide written notification to the USG of any anticipated or projected work stoppages or critical path schedule delays of more than five (5) working days within one (1) working day of becoming aware of the delay or anticipated stoppage. The Contractor shall provide written notification to the USG contracting officer of any anticipated or projected work stoppages or critical path schedule delays that will impact any major program milestones or reviews in writing within one

(1) working day of becoming aware of the delay or anticipated stoppage. The written notification shall include a description of the issue and plan for how to correct the issue and recover from the delay. The IMS shall only be re-baselined with prior written consent of the Procurement Contracting Officer (PCO) or KO.

3.2.2. CONTRACTOR INTEGRATED PERFORMANCE MANAGEMENT

The Contractor shall deliver Performance and Cost Reports in accordance with DI-FNCL-80912, CDRL A003. The Performance and Cost report shall track hours to the functional element from the Organizational Breakdown Structure which is Format 2 Organizational Breakdown Structure of the Contract Performance Report.

The Contractor shall deliver the following reports:

a. Contract Invoicing and Payment Report in accordance with CDRL A004

b. Contract Funds Status Report in accordance with CDRL A005

c. Contractor Business Data Report in accordance with CDRL A006

3.2.3. CONTRACT WORK BREAKDOWN STRUCTURE

The Contractor shall develop, deliver, update, and use the CWBS and CWBS Dictionary as the basis for planning, monitoring, and reporting system performance, cost, and schedule using relevant metrics for measurement in accordance with CDRL A007. The Contractor shall assign program details to each Task Breakdown structure element. Program details shall include start date, stop date, duration of days, physical percent complete, point of contact, and calculated earned value efficiency indexes.

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

3.2.4. FINANCIAL REPORTING

The Contractor shall implement a financial reporting plan consistent with the prime requirements subject to USG review or approval. The Contractor shall report Firm Fixed Price status at intervals specified per the Contract Data Requirements Lists (CDRL). For the Cost portions of the contract, the Contractor shall document performance and cost reports in accordance with CDRL A002, for a summary level report.

3.2.4.1. CONTRACTOR COST DATA REPORTING

The Contractor shall systematically collect and report actual contract costs to provide Department of Defense (DoD) cost analysts with needed data to estimate future costs. The Contractor shall prepare and deliver Contractor Cost Data Reports in accordance with the following:

a. Cost Data Summary Report in accordance with CDRL A008

b. Functional Cost-Hour Report in accordance with CDRL A009

c. Progress Curve Report in accordance with CDRL A010

3.2.4.2. SOFTWARE RESOURCES DATA REPORTING

The USG identifies SW resources data on the elements identified within the attached CSDR Plan, DD Form 2794. The data for each marked element are contained in the most recently approved versions of CDRL A011. The USG objective is to collect a subset of the same data that the contractor normally collects to oversee and manage SW development efforts. Therefore, the Contractor shall tailor the sample formats to be consistent with data it normally collects.

The USG will approve the tailored formats proposed by the contractor. The Contractor shall provide a SW Resources Data Report Data Dictionary with the customized formats.

3.2.4.3. CONTRACTOR MANPOWER REPORTING

The Contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for LIMWS via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/.

Reporting inputs will be for the labor executed during the period of performance during each USG fiscal year (FY), which runs 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, beginning with 2017. Contractors may direct questions to the help desk at help desk at: http://www.ecmra.mil.

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

3.2.5. DATA MANAGEMENT

The Contractor shall implement a data management program to control and track the delivery of data items required by the CDRLs.

3.2.5.1. PROGRAM DOCUMENTATION

The Contractor shall deliver, upon request, technical, and program documentation generated as a result of this acquisition in support of, and in execution of the LIMWS program, in accordance with CDRL A012.

3.2.5.2. DATA SUBMISSION

The Contractor shall submit all data items electronically in accordance with the CDRLs and contract. Content of these electronic data items shall be in accordance with the Data Item Description (DID) delivered to the USG.

3.2.5.3. NOTICE OF AVAILABILITY

The Contractor shall provide a Notice of Availability when a CDRL is available. The Notice of Availability shall be sent via email to the Program Manager (PM) Aircraft Survivability Equipment (ASE) Data Management as specified on the CDRLs unless additional e-mail accounts are identified on individual CDRLs. File names of CDRLs will include a unique file number or a document identification number assigned by the contractor, the contract number, and the delivery or task order the delivery is for. Additional deliveries of the same document, i.e., monthly schedules, may reuse the number by appending a dash and a second unique number for that delivery.

3.2.5.4. CLASSIFIED CDRL

The Contractor shall deliver classified CDRLs on Compact Disks, Digital Video Disks, or other USG approved media. The Contractor shall mail classified CDRLs to the USG in accordance with individual CDRL instructions.

3.2.5.5. LIMWS WEB SITE

The USG has established a Secure Website herein referred as the “Contract Website” for receiving Unclassified CDRL and Non-CDRL data resulting from this contract.

The Contractor shall establish and maintain the ability to deliver Unclassified CDRL and Non- CDRL data to the Contract Website for the life of the contract.

Access to the Contract Website web site shall be restricted and controlled with password protection or some similar form of protection as specified by the USG

Contractor shall utilize the USG secure website to post support-related (Logistics) management, maintenance, Failure Reporting and Corrective Action Report (FRACAS) Reports/Data, LRU

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document status and location information, as well as LIMWS Technical and Logistics Support Program-related CDRL items. The Contractor shall notify PM ASE Data Management, as specified on each CDRL, of all web site postings.

File names of CDRLs shall include a unique file number assigned by the contractor, the CDRL number, and the contract number. Additional deliveries of the same document, i.e., monthly schedules, may reuse the number by appending a dash and a second unique number for that delivery. CDRLs shall be delivered in either native format, i.e., Microsoft Office files, or as PDFs.

If PDFs are delivered, they shall be unlocked so that information can be copied from them for the convenience of the USG.

3.2.5.6. METRIC MEASUREMENTS

All Configuration Documentation (CD), changes and new design items, unless not feasible, shall be documented in the metric system of units.

3.2.6. DISTRIBUTION STATEMENTS AND EXPORT CONTROL WARNING

The Contractor shall mark data items in accordance with DODD 5230.24. The distribution statements used shall be those identified in the CDRL.

3.2.6.1. GOVERNMENT SOURCE SURVEILLANCE/INSPECTION

The USG reserves the right to inspect, at the source, LIMWS components and items not manufactured or services not performed at the contractor’s facilities. The contractor shall require its subcontractors to provide USG representatives reasonable physical access to subcontractor facilities for the purpose of USG Source Surveillance/Inspection. USG Source Inspection performed at supplier facilities shall not constitute USG acceptance of any item or service, or replace normal contractor inspection and acceptance, nor in any way release the contractor from its obligations with regard to Quality Assurance (QA).

3.2.7. SMALL BUSINESS

The Contractor shall submit a list of small business suppliers and/or service providers (subcontractors) and include how they will utilize those suppliers and service providers in performing this work effort, in accordance with CDRL A013. The list of small business suppliers and service providers will become part of the resultant contract. The Contractor shall submit to the PCO a report that documents (at least quarterly) how they are adhering to or exceeding their proposed utilization of small business suppliers and/or service providers. The PCO will use this report in determining an overall Contractor Performance Assessment Reporting System (CPARS) rating for subcontracting management. The Contractor shall coordinate with the PCO if small business firms identified in the list are substituted or not utilized over the quarter. The PCO must agree with the substitution prior to replacements performing on this contract.

Contractor substituting small business firms must find similar small business firms matching the socio-economic categories as identified in the list of suppliers and service providers.

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

3.2.7.1. SMALL BUSINESS SUBCONTRACTING PLAN

The Contractor shall make a good faith effort to find opportunities for small business suppliers and service providers in the performance of this work effort. The Contractor shall contact the local Procurement Technical Assistance Center, the local Office of Small Business Programs, and utilize the Small Business Dynamic Search Website to assist in finding small business suppliers and services providers that are capable of performing the subcontracted work. For large business firms with an approved Comprehensive Subcontracting Plan (through December 2017), Liquated Damages, will not be part of the resultant contract nor are you required to report in Electronic Subcontracting Reporting System/Individual Subcontract Report; however not adhering to or utilizing your proposed list of suppliers or service providers may result in a negative CPARS rating.

3.2.7.2. SMALL BUSINESS OPPORTUNITIES

The Contractor shall support small business opportunities throughout the period of performance. The Contractor shall make a good faith effort in identifying opportunities for small business suppliers and service providers including all socio-economic small business categories. The Contractor shall pay small business subcontractors within 15 (fifteen) days of receiving the subcontractor’s invoice and provide proof of payment to the KO Representative COR. The Contractor shall make a good faith effort to meet or exceed the proposed subcontracting goals/targets noted above or explain why the above goals cannot be met for this effort. The list of subcontractors shall be submitted with the proposal and revisions to the list can be made throughout the contract performance. The list of suppliers and service providers will become part of the resultant contract once accepted by the PCO.

3.2.8. TRAVEL

Travel by contractor personnel under this contract shall follow the guidelines of the Joint Travel Regulations. The Contractor shall request approval from the COR at least three (3) business days prior to each travel event.

3.3. SYSTEMS ENGINEERING

3.3.1. SYSTEMS ENGINEERING MANAGEMENT PROGRAM

The Contractor shall establish and maintain a Systems Engineering (SE) management program staffed and organized to manage and control the engineering activities as apportioned in the LIMWS WBS. The Contractor shall establish effective control over the systems engineering process (including subcontracted items and services, contract cost, performance, and schedule requirements) to provide early detection of risk. The Contractor shall conduct engineering investigations and assessments to support design of LIMWS. Engineering status reports shall be prepared and delivered in accordance with CDRL A014.

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

The Contractor shall use established systems engineering processes to maintain proper control and allocation of system requirements throughout the QRC effort. The Contractor shall utilize Technical Performance Measurements (TPM) to assess technical progress and technology maturity against Critical Technical Parameters (CTP). The TPMs and CTPs shall provide visibility into the technical performance of key elements of the work breakdown structure and the highest areas of cost, schedule, or technical risk. These TPMs and CTPs shall be presented to the USG for concurrence at the PAC.

3.3.2. SYSTEM ENGINEERING MANAGEMENT PLAN

The Contractor shall prepare and submit a System Engineering Management Plan (SEMP) in accordance with CDRL A015. The SEMP shall encompass the SE activities during the QRC phase and provide a plan for systems engineering during the Production and Deployment phase. The Program Management Plan, WBS, and IMS shall be the basis for development of the SEMP. The SEMP shall describe the Systems Engineering processes referenced in CDRL A015.

3.3.3. PROGRAM REVIEWS, TECHNICAL REVIEWS, WORKING GROUPS

3.3.3.1. POST AWARD CONFERENCE/KICKOFF TECHNICAL INTERCHANGE MEETING

The Contractor shall host a PAC at a location agreed to be the USG not later than 15 (fifteen) days after contract award at a location agreed to by the USG. The purpose of the PAC (FAR 42.5) is to aid both the USG and contractor personnel to: (1) Achieve a clear and mutual understanding of the SOW and all contract requirements and (2) Identify and resolve potential problems.

The Contractor shall present their Program Management Plan, IMS, Risk Management Plan (RMP), SEMP, pre-Critical Design Review (CDR) design with opportunities for improvement, path to meet CDR entrance criteria, Allocated Baseline (ABL), SW Development Plan, CWBS, key personnel, Digital System Model (DSM) HW requirements, and program implementation processes. The Contractor shall present their pre-CDR Material Purchase Plan as a piece-part level Bill of Materials (BOM) with cost and risk. The Contractor shall prepare and deliver agendas and TIM presentation materials in accordance with CDRL A017. The Contractor shall prepare and deliver minutes in accordance with CDRL A016.

The Contractor shall host a Kickoff Technical Interchange Meeting (TIM) at the contractor’s facility not later than 45 (forty-five) days after contract award.

The Kickoff TIM shall, at a minimum, address:

a. Basic Technical Approach

b. Protoype, DSM, Data Acquisition Unit, and SW Integration Lab (SIL) delivery schedule

c. Manufacturing Readiness and Producibility

d. Risks

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

e. IMS

f. Agreement on CTPs and TPMs

g. Demonstrate the SE, Development, and SW Configuration Management (CM) processes

h. Agreement on weekly meeting schedule

3.3.3.2. INTEGRATED BASELINE REVIEW

The Contractor shall conduct an Integrated Baseline Review (IBR) in accordance with the Office of the Secretary of Defense IBR Guidebook and Defense Acquisition Guidebook (DAG).

The IBR process shall be conducted not later than 60 (sixty) calendar days after contract award.

The IBR process shall be conducted not later than 60 (sixty) calendar days after the exercise of significant contract options or the incorporation of major modifications. The USG will verify during the IBR that the contractor has established and maintains a reliable Performance Measurement Baseline (PMB). The PMB shall include the entire contract technical scope of work consistent with contract schedule requirements. The PMB shall employ appropriate management processes and have adequate resources assigned. The Contractor shall use earned value methods to accurately status contract cost, schedule, and technical performance. The IBR will be used to achieve a mutual understanding of the baseline plan, cost and schedule risk, resourcing and the underlying management processes used for planning and controlling the project.

Subsequent IBRs may be performed, when warranted by the USG, following major baseline changes, incorporation of major modifications, incorporation of an Over Target Baseline or Over Target Schedule, review of subsequent detail planning windows (often referred to as Rolling Wave or Block Planning) unavailable at the previous IBR event, or in support of Estimate at Completion site visits.

The IBR shall be held at the contractor’s facility and not exceed three (3) working days. In coordination with the COR or KO, the Contractor shall set the IBR meeting date at least 30 (thirty) days prior to IBR. The Contractor shall coordinate identified agenda topics with the USG at least 10 (ten) days prior to the IBR. The Contractor shall coordinate with designated product teams and allow USG access to associated documentation, to include but not limited to Control Account Manager notebooks, for the entrance and exit criteria to the USG no less than 30 (thirty) days prior to the IBR.

The Contractor shall prepare and deliver minutes for all IBRs conducted in accordance with

CDRL A016.

3.3.3.3. SYSTEM REQUIREMENTS REVIEW

The Contractor shall conduct a System Requirements Review (SRR) no later than five (5) months after award of the QRC contract. The Contractor shall include reviews of the SPS, SOW, and schedule during the SRR. The SRR shall be held at the contractor's facility or another agreed

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document upon location with the USG. The Contractor shall prepare and deliver agendas and SRR presentation materials in accordance with CDRL A017. The Contractor shall prepare and deliver minutes for all SRRs conducted in accordance with CDRL A016.

3.3.3.4. PRELIMINARY DESIGN REVIEW

The Contractor shall conduct a Preliminary Design Review (PDR) no later than six (6) months after award of the QRC contract

The PDR shall be held at the contractor’s facility and not exceed three (3) working days. In coordination with the USG, the Contractor shall set the PDR meeting date at least 30 (thirty) days prior to the PDR. The Contractor shall coordinate with the USG the agenda topics to be identified at the PDR. The Contractor shall coordinate entrance and exit criteria with the USG no less than 30 (thirty) days prior to the PDR. The Contractor shall prepare and deliver agendas and PDR presentation materials in accordance with CDRL A017. The Contractor shall prepare and deliver minutes for all PDRs conducted in accordance with CDRL A016.

3.3.3.5. CRITICAL DESIGN REVIEW

In accordance with DoDI 5000.02 and the DAG, the Contractor shall conduct a CDR for the LIMWS A-Kit and B-Kit designs no later than seven (7) months after contract award. In coordination with the USG, the Contractor shall set the CDR meeting date and submit a completed CDR checklist in accordance with CDRL A018, to demonstrate the contractor’s readiness to conduct the CDR. The Contractor shall coordinate entrance and exit criteria with the Government no less than thirty (30) days prior to the CDR. The Contractor shall coordinate the final CDR agenda topics with the USG 30 (thirty) days prior to the CDR. The Contractor shall demonstrate to the USG their ability to meet CDR entrance criteria at least thirty (30) days prior to the CDR.

3.3.3.6. PRODUCTION READINESS REVIEW

The Contractor shall facilitate assessments of manufacturing readiness (Production Readiness Reviews (PRR)), using the definitions, criteria, and processes defined in the MRL Deskbook as a guide (http://www.dodmrl.org). The PRR will include site visits by a USG PRR team to the contractor’s manufacturing facilities and to their major suppliers’ manufacturing facilities and to any sub-tier critical suppliers as specified by the USG. The assessments will be led by the Product Manager (PdM) MW at the prime contractor’s facilities. The Prime Contractor shall lead the assessments at their major suppliers and include USG participants (using the MRL Deskbook as a guide).

The Contractor shall conduct a PRR planning meeting at an agreed upon date with the USG at the contractor’s site to propose a formal PRR Schedule, in accordance with CDRL A019.

The selection of supplier assessments shall be proposed by the contractor and agreed to by the USG at the PRR planning meeting.

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

The USG will provide a PRR Report not later than 60 (sixty) days after completion of the PRR.

The Contractor shall provide a response to all USG recommendations, including any plans for implementation of these recommendations, not later than 30 days after receiving the USG report.

The Contractor shall develop and implement manufacturing maturation plans or their equivalent for criteria in which the MRL is lower than the target MRL 8. The Contractor shall monitor and provide status at all program reviews for in-house and major supplier MRLs.

3.3.3.7. TECHNICAL INTERCHANGE MEETING

The Contractor shall conduct and host monthly Technical Interchange Meetings (TIM) for the duration of this effort. The Contractor shall prepare and deliver TIM agendas and presentation materials in accordance with CDRL A017. The Contractor shall prepare and provide TIM minutes, with actions assigned, and submit in accordance with CDRL A016.

3.3.3.8. PROGRAM MANAGEMENT REVIEW

The Contractor shall conduct Program Management Reviews (PMR) quarterly at the contractor’s facility or other site mutually agreed upon by the USG and the contractor.

The PMRs shall be conducted to provide the USG the necessary visibility into the conduct and consequences of the various efforts of the contractor and its subcontractors. During the review, the Contractor shall present and review the status of issues surrounding the technical, financial, and schedule performance of the contract and highlight problem areas and recommendations for corrective actions. The Contract shall prepare and deliver agendas and presentation materials in accordance with CDRL A017.

PMRs shall be structured in an Integrated Product Team (IPT) format, and review agendas shall include, but not be limited to, the following topics:

a. A brief overview and status/progress toward achieving program objectives.

b. Earned value review - A review of updated Integrated Master Plan, IMS, and CWBS elements, including critical path analyses. IPT leads or functional managers shall include cost information in discussions of schedule status, technical performance, and risk, using earned value as an integrating tool. Cost/schedule trends, significant cost/schedule/technical variances, projected impacts, quantified risk assessments, and corrective action plans shall be addressed.

c. Risk and Opportunity status.

d. Staffing.

e. Changes in established system design/configuration and rationale for those same changes.

f. Hardware and SW development status.

g. Reliability program status.

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

h. Review of contract modifications/changes since last PMR and proposed additional contract modifications/changes, including rationale.

i. Technical Performance Measures/Metrics status.

j. Leading performance indicators in use by the contractor.

k. SW process improvement status.

l. Open Architecture status of key interfaces and design considerations in other IPT efforts.

m. Logistics.

n. Test status, including test planning and results, and any issues relative to test resources, assets, and facilities.

o. Anti-Tamper, Information Assurance, and System Security status.

p. Subcontractor activities and status and results of subcontractor reviews since last PMR.

q. Action Item review.

The Contractor shall prepare and deliver minutes for all PMRs conducted in accordance with CDRL A016. These minutes shall cover significant questions, deviations, conclusions, and action items resulting from the meeting. The minutes will constitute the meeting report and be submitted in accordance with CDRL A016. Conclusions from discussions conducted during concurrent meetings (e.g., side meetings) shall be summarized in the main meeting and appropriate comments and be read into the official minutes. Recommendations not accepted shall be recorded together with the reason for non-acceptance.

3.3.3.9. INTEGRATED PRODUCT TEAM MEETINGS

The Contractor shall establish IPTs consistent with their SEMP and conduct IPT meetings with the USG. Participation shall include contractor subject matter experts and contractor functional leads. The IPT meeting may be cancelled at any time at the discretion of the USG. The contractor shall conduct the following IPTs at a minimum: Management and Business, Systems Engineering and Risk, Software, A-Kit, Test and Evaluation (T&E), and Production and Quality at the frequencies shown in Table I.

The Contractor shall prepare and deliver agendas and conference presentation materials in accordance with CDRL A017. The Contractor shall prepare and deliver minutes for all IPT meetings conducted in accordance with CDRL A016.

TABLE I. IPTs and Frequencies

IPT Name Frequency Management and Business Monthly

Systems Engineering and Risk Weekly Software Weekly

A-Kit Weekly

Use or disclosure of this information is subject to the restriction(s) on the title page or on the first page of this document

Test and Evaluation Bi-Weekly Production and Quality Weekly

The Contractor shall support the USG established IPT meetings with contractor subject matter experts.

3.3.4. RISK MANAGEMENT

The Contractor shall implement risk management processes that are consistent with the USG RMP, W6DP01-P-00245, to identify, assesses, track, and mitigate risks associated with the development and implementation of the LIMWS program from a technical, cost, and schedule perspective. The Contractor shall prepare and submit an RMP in accordance with DI-MGMT-

81808, CDRL A020.

3.3.5. LIMWS SYSTEM DESIGN/DEVELOPMENT

The Contractor shall develop a LIMWS ICD that meets the performance requirements defined in ASE-17-001. The Contractor shall present the initial Product Baseline (PBL) design of the LIMWS System to the USG during the PDR. The LIMWS System development process shall include risk identification and management and the requisite functional allocations to support the LIMWS design/configuration. The Contractor shall update the LIMWS ICD and PBL as changes occur and present at CDR.

3.3.5.1. TRADE STUDIES

The Contractor shall document the results of up to ten (10) trade studies performed in accordance with CDRL A021.

3.3.5.2. SPECIFICATIONS

The Contractor shall decompose LIMWS Subsystem Performance Specification (SPS) requirements in order to develop and derive sub-system level requirements necessary for functional allocation of the requirements down to the appropriate HW and SW specifications.

The Contractor shall provide the LIMWS System Specification Tree, in accordance with CDRL A022, which identifies the requirements specifications and documents developed for all components and assemblies in the LIMWS System and their inter-relationships. The Contractor shall develop, maintain, and deliver a System Performance Specification in accordance with CDRL A023. The Contractor shall develop, maintain and deliver a System/SPS (SSPS) in accordance with CDRL A024.