STATEMENT OF WORK
Guided Multiple Launch Rocket System (GMLRS)
Alternative Warhead (AW) Integration and Demonstration
21 October 2008
The contractor shall support an Alternative Warhead (AW) Integration and Demonstration Phase that includes the refinement of AW concepts, warhead component level testing, warhead fabrication and integration with the Guided Multiple Launch Rocket System (GMLRS) and flight testing of the GMLRS AW rocket. Two warhead contractors will be awarded contracts to perform the tasks summarized in this Statement of Work (SOW). This warhead is intended to replace the GMLRS Dual Purpose Improved Conventional Munition (DPICM) warhead. The goal of the AW Integration and Demonstration phase is to develop data sufficient to enable the Government to down-select to a final candidate for further development and testing under a GMLRS AW Engineering and Manufacturing Development and Demonstration (EMDD) follow-on phase. This Integration and Demonstration phase shall include component level testing, system level pre-flight testing and limited flight testing as well as preliminary estimates for production capability and cost, and analysis of performance against requirements. The competing designs shall have the capacity to replace the current GMLRS DPICM warhead with enhancements relative to tactical capability and overall system effectiveness where possible. The resulting GMLRS AW designs, as integrated with the GMLRS rocket, shall comply with all applicable US Government environmental laws, regulations, and statutes.
Applicable top level documents are contained in Attachment 002 to the Contract, Document Summary List (DSL), by number, title, and date. The document versions specified on the DSL take precedence over the generic references (without revision letters) cited in the SOW.
2.0 Objectives/Scope Summary
2.1 The Government’s objective for the GMLRS AW is that it eliminate all residual unexploded ordnance (UXO) (less than one (1) percent required/zero (0) percent objective). Also, the Government’s objective is that the AW will be equal to or better than the effectiveness requirements in the Multiple Launch Rocket System (MLRS) Operational Requirements Document (ORD). Warhead cost shall be minimized; and insensitive munitions rating shall be maximized where possible.
2.2 The GMLRS AW, as integrated with the GMLRS rocket, shall be capable of being fired from the MLRS M270A1 and High Mobility Artillery Rocket System (HIMARS) launchers.
2.3 During the Integration and Demonstration Phase the warhead contractors shall refine their proposed design; conduct any necessary component performance tests (arena, drop, or other) to collect data against predictions; finalize/refine interfaces with the integration contractor’s GMLRS rocket and identify any integration contractor hardware surrogates required for component testing; fabricate and deliver warheads for integration into the GMLRS rocket pre-flight testing and flight testing; and provide refined analysis of the effectiveness of the warhead against requirements identified in MLRS ORD. The contractor shall support integration activities with the integration contractor and shall support pre-flight testing and flight testing efforts. All such support efforts by the warhead contractors shall be inclusive of this contract.
2.4GMLRS AW components and subsystems developed and/or modified and tested under this contract shall be considered for future transition into an EMDD and possible cut-in to GMLRS production at a later date. Therefore, the contractor shall minimize integration complexity and maximize producibility while meeting AWP effectiveness requirements.
2.5. The contractor shall develop a Master Program Schedule (MPS) of all activities for this Integration and Demonstration Phase effort, which is consistent with the Government schedule shown in Attachment 004. MPS shall be prepared in accordance with (IAW) DI-MGMT-81650.
2.6 The contractor shall formulate a preliminary EMDD program schedule, in association with the integration contractor. It shall contain sufficient detail to convey specific activities and durations consistent with that shown in Attachment 004. EMDD program schedule shall be prepared IAW DI-MGMT-81650. In order to accomplish the interface and coordination of warhead parameters and associated details and estimates, the contractor shall be required to develop and implement an Associate Contractor Agreement (ACA) with the integration contractor. Cost of interfacing with the integration contractor shall be part of this contract.
2.7 The contractor shall refer to the Interface Documents provided in Attachment 003 for refinement of their warhead concept. Any follow-on adjustments/deviations deemed necessary shall be coordinated with the integration contractor under the ACA.
3.0 Systems Engineering
3.1General - The contractor shall use their established system engineering practices in performance of this integration and demonstration support activity. The system engineering program shall include the following:
3.2 Engineering Trade Studies- The contractor shall conduct engineering trade studies relative to any alternative approaches to electrical and mechanical interfaces, operational scenarios required for the warhead functional requirements, and determine any acceptable interface deviations/adjustments to best accommodate warhead integration and test. The contractor shall coordinate with the integration contractor for determining acceptable solutions to interface deviations. A report describing the trades performed, results, and conclusions shall be prepared IAW DI-MISC-80508.
3.3Component/System Optimization - The contractor shall perform an analytical assessment of their warhead design in meeting the Technical Requirements Document for GMLRS AW in Attachment 003. The contractor shall be required to coordinate with the integration contractor in support of a system level performance analysis to be performed by the integration contractor. System optimization shall include the following: effectiveness, cost, risk, producibility, and Insensitive Munitions (IM) performance. The contractor shall also address any potential modifications to the GMLRS operational structure (rocket, launcher, Special Test Equipment (STE), and Command and Control (C2)). Based on the analytical assessment and results of component level testing, the contractor shall optimize their warhead design and fabricate warheads for delivery to the integration contractor for integration with the GMLRS rocket and the conduct of pre-flight testing and flight testing.
3.4Interfaces - The contractor shall comply with the interface requirements and account for the environmental parameters in the Technical Requirements Document. Mechanical, electrical, and software/data interface deviations shall be coordinated, via the ACA, with the integration contractor for acceptability/compatibility.
3.5 Simulation/Analysis - The contractor shall provide technical analysis and simulation details to the GMLRS Unitary Government Simulation Direction Team (SDT) and inform this group of contractor developed component performance simulation efforts. The contractor shall develop and/or use existing contractor simulations and models necessary to predict performance against requirements to include a three degree of freedom (3-DOF) simulation for warhead payload dispense and warhead ground pattern prediction and analysis for the warhead design. The contractor shall coordinate with the integration contractor for component level simulations/models and/or inputs for inclusion in the system level performance simulation/model. The contractor shall deliver to the Government GMLRS AW component simulation supporting documentation describing methodology used during this contract to develop AW performance or effectiveness data. The contractor shall make available to the Government data developed from analysis, simulation, and verification testing conducted under this contract. The contractor shall prepare a report IAW DI-MISC-80508.
3.6 Component Preliminary Design Review (PDR) - The contractor shall conduct a Component PDR for the warhead design no later than indicated in Attachment 004. This review shall include sufficient information and analysis to convey the details of the component design, indicate expected performance, and identify any issues with integration on the GMLRS rocket. An earlier timing of this design review may be proposed by the contractor and coordinated with the Government and the integration contractor for acceptability. The contractor shall prepare PDR material IAW DI-MISC-80508.
4.0Software - The contractor shall identify preliminary software requirements to accommodate their GMLRS AW integrated design. The contractor shall coordinate with the integration contractor any software changes necessary to support integration testing and flight testing. The integration contractor shall accomplish these changes, where necessary, under separate contract with the Government for integration testing, preflight testing, and flight testing.
5. System Integration
5.1 Component Testing Support - The contractor shall coordinate with the integration contractor any surrogate GMLRS nose sections and inert rocket motor sections required for the warhead contractor component level integration and testing. The procurement of the necessary surrogate hardware shall be the responsibility of the warhead contractor.
5.2 Common Hardware– The contractor shall coordinate with the integration contractor any GMLRS-common hardware required to support the proposed design. The procurement of the necessary hardware shall be the responsibility of the warhead contractor.
5.3 Rocket/Warhead Integration - The warhead contractors shall coordinate with the integration contractor for final determination of interface approach and details to support the delivery of hardware to the integration contractor for integration, preflight testing, and flight testing. The contractor shall be responsible for this portion of the coordination effort.
6.0 Program and Financial Management
1. Integrated Product Team (IPT) and Integrated Product and Process Development (IPPD) -
The contractor shall integrate all the functional disciplines required to perform this SOW through the implementation of IPT principles. The resultant integrated organization shall have access to all contractor and subcontractor facilities and data developed and utilized in the performance of this contract. The integration of required functional disciplines shall facilitate technical interchange between Government and contractor personnel on a continual basis, and shall utilize electronic media when possible. The integration of required functional disciplines shall facilitate the execution of contract activities in an effective and efficient manner toward meeting technical, cost, performance, supportability, and schedule requirements.
6.2Program Reviews (PR)
6.2.1 Warhead Contractor Reviews - The contractor shall conduct two program reviews consistent with the Government program schedule reflected in Attachment 004. The contractor, in conjunction with the Government, shall develop an appropriate agenda, IAW DI-ADMN-81249 prior to the reviews. The contractor shall conduct these tailored reviews capturing component level designs and performance predictions as well as cost and schedule information and updates to Average Procurement Unit Cost (APUC) predictions. These reviews will be no longer than one (1) day, at the contractor’s facility. The first of these reviews can be combined with the Component PDR, discussed in paragraph 3.6. The integration contractor will support the technical portion of all reviews via the ACA. The contractor shall conduct a final program review 15 days after the end of the system level flight test and analysis period consistent with the schedule shown in Attachment 004. This review shall convey the updated information/predictions contained in the original contractor proposal.
6.2.2 System Level Reviews - The contractor shall support system level program reviews to be held at the integration contractor’s facility for this integration and demonstration effort. The contractor, in conjunction with the integration contractor, shall determine the appropriate level of support required. The contractor shall support one system level program review and one system level PDR with the Government, at the integration contractor’s facility, during the Integration and Demonstration Phase.
6.3Master Program Schedule (MPS) - The MPS shall be presented at program component level reviews, as identified above. Schedule details on support to pre-flight testing and flight testing shall be identified and coordinated with the integration contractor.
6.4 Logic Network Schedule and Work Breakdown Structure (WBS) - Within 45 days after contract award, the contractor shall provide Government access to a logic network schedule arranged by WBS which accurately portrays the sequence and relationship of activities that define the contractor and subcontractor activities and events. The network shall include the WBS on each activity and shall be implemented on a computer-based system that utilizes a critical path method network analysis. The network shall be used to provide contractor schedules and to develop the baseline by which project progress will be measured. The contract WBS shall be prepared IAW DI-MGMT-81334.
6.5WBS Cost Reporting - Contract cost data shall be prepared IAW DI-FNCL-81565 and DI-FNCL-81566.
6.5.1Electronic Transfer - The contractor shall electronically transfer cost and schedule performance data at the lowest WBS level which can be summarized by the Government and which is consistent with the electronically transferred performance data supplied in the network.
7.0 Test and Evaluation (T&E)
7.1The objective of the GMLRS AW Integration and Demonstration program is to collect data at the component and system levels to support a down-select decision on the GMLRS AW, leading into EMDD. The T&E program shall consist of a logical sequence of component and subsystem level hardware and software tests. Results from these tests shall be used by the contractor to identify future design refinements and proposal updates as specified in section L of the Request for Proposal (RFP). The contractor shall perform component level testing necessary to assess performance and shall support system level testing.
7.2 Component and Subsystem Testing - The contractor shall conduct warhead component level tests and conduct/support subsystem testing that will provide data on warhead technical parameters. The contractor shall perform any necessary GMLRS subsystem testing to ensure warhead compatibility prior to full integration and flight testing. The overall test program shall provide sufficient data for the Government to assess compliance with the user requirements and to assess the warhead/system compatibility and integrity. This shall include warhead performance testing, limited warhead/system compatibility testing, limited system level preflight testing and limited flight testing sufficient to indicate the levels of risk with each warhead system.
7.2.1 Software Interface Testing - In support of a GMLRS AW Flight Test, software tests shall be conducted by the integration contractor to verify the proper operation and interface between the GMLRS AW and M270A1 and HIMARS launchers. The warhead contractor shall support these tests where necessary.
7.2.2 Flight Testing - Flight Tests shall be single rocket fire missions at various ranges. The impact area will be populated with witness panels/targets and instrumentation sufficient to indicate the relative effectiveness of each warhead as integrated on GMLRS.
184.108.40.206 Flight Test Quantities/Conditions - The contractor shall fabricate and deliver four (4) warheads to the integration contractor to support preflight testing and flight testing at White Sands Missile Range (WSMR) no later than shown in Attachment 004. No Stockpile-to-Target Sequence (STS) or temperature testing will be performed on test rockets. The contractor shall plan to support three (3) missions of one (1) rocket per mission. Ranges, launch points and impact areas shall be coordinated among the Program Management Office (PMO), WSMR and the integration contractor. The M270A1 launcher will be used for these flights.
220.127.116.11 Telemetry (TM) - The Redstone Technical Test Center (RTTC) TM package shall be the baseline for each flight test rocket. This telemetry package does not currently support transmission of warhead parameters.
7.3Test Readiness Reviews - The contractor shall conduct a component test readiness review before the start of the hardware test series. The contractor shall notify the Government at least seven (7) days in advance of the time and place of the review. These reviews will be IAW contractor practices and formats. The contractor shall support system test readiness reviews as coordinated with the integration contractor.
7.4 Test Planning and Documentation
7.4.1 Test Plans - The contractor shall prepare detailed component test plans IAW DI-NDTI-80566. For system level testing the warhead contractor shall coordinate with the integration contractor for support to development of required range documentation, inclusive of warhead parameters and peculiarities.
7.4.2 Test Results - The contractor shall prepare and deliver a final test report, IAW DI-NDTI-80809, for each component test conducted.
7.4.3 Explosive Ordnance Disposal (EOD) Source Data - The contractor shall coordinate with the integration contractor to provide essential information required to develop and publish EOD source data. This data shall be delivered IAW DI-SAFT-80931 and shall be made available to the integration contractor prior to flight tests at WSMR.
8.0 Quality Assurance
8.1 Quality System - The contractor shall utilize a quality system that meets the requirements of ISO 9001. The system shall provide control of process and product characteristics and include criteria and methodology that are used to validate conformance to performance specifications and to achieve continuous improvement. The quality system shall be integrated with other functional areas in the design, test, fabrication, and management processes. The quality system shall employ effective inspection and test methodology to ensure product pedigree and integrity. Quality records shall be available for Government review.
8.2 Software Quality System (SQA) - The contractor shall utilize their existing software quality system. The contractor's SQA program shall also assure that adequate testing of all applicable software requirements is conducted prior to entering the test phase and Proof and Validation activities. Quality records shall be available for Government review.
8.3 Reliability and Maintainability (RAM) - The contractor shall utilize their existing RAM program. The contractor shall coordinate with the integration contractor to ensure that their system will not degrade the reliability of the system. Preliminary RAM allocations and predictions shall be available for Government review.
9.0 Risk Management - The contractor shall maintain a risk management function, including Risk Identification/Ownership, Risk Assessment, Risk Reduction, and Risk Management. The contractor’s risk management function is required for monitoring and controlling risk. Risk Management shall be established at contract award. A policy of continuous risk management shall be pursued throughout the Integration and Demonstration Phase, with measures put in place to reduce or control these risks. Periodic reviews of all the risks to assess any change in their impact or likelihood of occurrence shall be conducted by the contractor and reported at Program Reviews and the Preliminary Design Review, if conducted separately.
10.0 Government Furnished Property/Government Furnished Equipment (GFP/GFE) – The Government does not intend to provide any GFP/GFE to the contractor.
11.0 Explosive Hazard Classification - Data required for interim hazard classifications for explosive components/system hardware requiring shipment shall be consistent with that of TB 700-2. This data shall be provided to the US Army Aviation and Missile Command (AMCOM) Safety Office in the format of Attachment 005 no later than 60 days prior to shipment.
12.0 Configuration and Data Management
12.1 Configuration Management. The contractor shall implement a configuration management (CM) program to support the development, identification, and tracking of AW configuration documentation (CD). The CD for the AW Integration and Demonstration phase shall consist of Developmental Design Drawings/Models and Associated lists prepared/revised IAW DI-SESS-81002, applicable product drawings/models and associated lists prepared/revised IAW DI-SESS-81000 applicable performance specifications prepared/revised IAW DI-SDMP-81465, and applicable Interface Control Documentation prepared/revised IAW DI-CMAN-81248.
12.2 Data Management (DM). The contractor shall implement a data management program to control and track the delivery of data items required by the Contract Data Requirements List (CDRL), DD Form 1423. The contractor shall host a Government accessible website to be used for the on-line delivery of all CDRL items.
12.2.1 Data Submission. The contractor shall submit all data items electronically via the website IAW the CDRL. Content of these electronic data items shall be IAW the Data Item Description (DID), as tailored by the Document Summary List.
12.2.2 Distribution Statements and Export Control Warning. The contractor shall mark data items IAW DODD 5230.24. The distribution statements used shall be those identified in the CDRL.
13.1 Security classification shall be IAW the Contract Security Classification Specification, DD Form 254.
13.2 Facilities, Classified Storage, Security Clearances. The contractor is required to maintain facilities for storage and discussions of classified materials at the DoD Secret level. The contractor is responsible for compliance with all applicable laws and regulations governing access to classified information IAW DoD 5220.22-M.
14.0 Hazardous Material Management. All Contractor and subcontractor activities shall be in compliance with applicable federal, state, and local environmental laws and regulations. The Contractor shall ensure that design, maintenance, operation, manufacturing, programmatic decisions, and trade-off studies strive to eliminate or reduce hazardous materials and waste. The contractor shall implement a Hazardous Materials Management Program (HMMP), IAW National Aerospace Standard (NAS) 411. The contractor shall prepare a HMMP Plan IAW DI-MGMT-81398. The contractor shall request Government approval to use any of the substances identified in the EPA 17 List (available at http://www.epa.gov/opptintr/3350/33finb1.htm) for those substances not previously approved for use by the Government. Any previously approved EPA 17 List substance that is to be used in a new manner and/or on a new item requires Government reapproval. The contractor shall not use any Class I Ozone Depleting Chemical/Ozone Depleting Substance (ODC/ODS) (identified at http://www.epa.gov/ozone/ods.html) in the manufacture or support of items required by this SOW unless a waiver is obtained from the Government. The Contractor shall provide, electronically and through the IPT process, immediate notification of any proposed hazardous material mitigation/elimination efforts that may adversely impact schedules and/or cost, or performance. The Contractor shall prepare annual HMMP Report IAW DI-MISC-81397 to report perchlorates, Class II ODC/ODSmaterials listed at http://www.epa.gov/ozone/ods.htmland/or any substances listed in Emergency Planning and Community Right-to-Know Act (EPCRA) Section 313 "toxic chemicals" and EPCRA Section 302, "extremely hazardous substances"(available at http://www.epa.gov/swercepp/pubs/title3.pdf). The HMMP Report shall also identify via technical drawing/publication the specific location of each hazardous material contained in the final end item(s). Any hazardous materials used in the manufacturing process shall be identified as such in the HMMP Report. Contractor shall use existing documentation where possible.