DO_Attach_1_-_DO_1_SOW_9_Aug.docx

Statement of Work (SOW) for FY19 Weapon Planning Software (WPS) Development and Legacy Enhancement Delivery Order (DO)

Contract Number: FA8681-19-D-0006 DO Number: FA8681-19-F-1001

9 August 2018

Prepared by:

Department of the Air Force

AFLCMC/EBDW

207 West D Ave STE 225 Eglin AFB, FL 32542

Table of Contents

Appendix A: WPS 2.X Product Build Plan 15 Appendix B: Contractor Acquired Equipment……………………………………………………… 16

Statement of Work for Delivery Order (DO) #1 FY19 Weapon Planning Software (WPS) Development and Legacy Enhancement

1. Scope: This SOW identifies the tasking for software integration of the GPS Jamming capability within the GPS Common Component (CC), the integration with Weather CC, and the creation of a WPS Timeline Tool with the WPS v2.2 product suite. It also identifies maintenance fixes of prioritized deficiency reports (DRs) and deferred requirements from previously delivered versions of the WPS product. These requirements shall be compatible with all Combat Air Force (CAF) strike aircraft Mission Planning Environments (MPEs). This SOW provides for the software development, integration and documentation to design, build, test and provide an engineering releasable product for a software upgrade that will be included in the development WPS v2.2 Engineering Release (ER) and a legacy enhancement delivery of WPS v2.1.X production release to include a formal qualification test (FQT). This SOW also identifies support for existing WPS v2.1 DRs, the Joint Mission Planning System (JMPS) 64 bit compatible Framework (FW) and sustainment support to address Change Requests (CR) and DRs from the CAF end user.

1.1 General Information: This SOW includes tasking to implement prioritized software changes and enhancements identified and assigned by the WPS Program Office (PO). The intent of this SOW is to:

1.1.1 Maximize work on WPS v2.X resulting in delivery of v2.2 ER encompassing GPS jamming requirements, integration of native 64 bit JMPS CCs, integration of the CAF MPE 4.1, and addressing prioritized CR & DRs.

1.1.2 Continued sustainment support on Network Enabled Weapon (NEW) legacy enhancements while providing prioritized CR and DR fixes for the CAF to be included in a WPS v2.1.X delivery.

1.1.3 Required tech refresh in which the Contractor shall procure JMPS/WPS laptops (see Appendix B).

1.1.4 Travel and meeting support necessary to maintain and develop the WPS software products.

1.2 The WPS v2.0 ER#3 shall be the software baseline for development and enhancements.

1.3 Period of Performance (PoP)/Delivery Schedule: See Section F of this DO for detailed PoP and Deliveries.

2. Specific Requirements:

2.1 Transition Phase-in: This DO SOW invokes the basic contract SOW paragraph 2.8, Transition, paragraph/subparagraphs 3, General Requirements and 4, Contractor Performance. This DO requirement includes all efforts to prepare for the performance of this contract, including, but not limited to;

2.1.1 Post award conference at the contractor’s location for initial team introductions (within 30 days of award), receipt of applicable GFP/GFI, and to review the basic contract along with the awarded DO (review the SOW, IMS, WBS and CDRL requirements).

2.1.2 The support required to undergo the transfer of architecture design and any in-progress weapons software development from the predecessor contractor, if required. The contractor shall successfully build and execute both WPS 1.x and 2.x code baselines.

2.1.3 Associate Contract Agreements (ACAs) for any portion of the DO requiring joint participation in the accomplishment of the Government’s requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the development and integration of WPS products, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract (see compliance document JMPS Business Rules Section 1.3).

2.1.4 Preparation and execution of the initial Integrated Baseline Review (IBR) (IBR shall occur within 90 days of award). (Applicable CDRLs: A002, A003, A004, A005, A006, A010, A012, A013, A015, A014, A016, A018)

2.2 Development to WPS v2.2: This DO SOW invokes the basic contract SOW paragraphs 2.1, Prototype, and 2.1.1, Engineering Release (ER). This DO is to modernize WPS 2.1 baseline to v2.2 providing functional software for MPE developers and test organizations to evaluate. New capability/new Change Requests (CRs) shall be used to investigate and implement changes to WPS software for WPS v2.X versions to resolve defects, provide enhancements, or comply with changes in the framework (FW), aircraft Unique Planning Components (UPC), other JMPS CCs, and the Air Force Standard Desktop Configuration (SDC). The contractor is required to integrate GPS jamming requirements with native 64-bit JMPS common components (CCs) and integrate with the CAF MPE 4.X, and address prioritized CRs & DRs to be included in the prototype and WPS v2.2 ER(tested within this CLIN). (Applicable CDRLS: A001, A002, A004, A005, A006, A007, A008, A009, A010, A012, A013, A015, A016, A017, A018)

2.2.1 Current generation Precision Guided Munitions (PGM) rely heavily upon GPS guidance to meet Circular Error Probable (CEP) specifications. With the proliferation of inexpensive and sophisticated GPS jammers, PGM mission planners must assess the impact of jamming on weapon performance. The Offeror shall propose a software design to add GPS jamming analysis to WPS v2.X. GPS analysis calculations shall use the GPS Interference and Navigation Tool (GIANT) available through the JMPS GPS CC (documentation is found in the Export Controlled CD/DVD under the Initial DO file).

The WPS v2.X Software baseline shall be modified to incorporate GPS jamming analysis tool(s). This DO SOW identifies tasking to update the WPS software to integrate with the GPS CC GIANT database/tools. Specific goals are to provide GPS jamming analysis and potential solution(s) to assist the mission planner to optimize PGM deliveries in a GPS contested environment. The required work includes requirements analysis, risk identification, key stakeholder coordination, software design, software development, testing, scheduling, software releases, and documentation needed to meet the identified task requirements. Coordination with other JMPS Component developers, USAF and USN software test teams, and agencies providing GPS jamming source data is critical to this effort. A list of Key Stakeholders will be provided upon award for coordinating execution of ACAs during the transition period.

2.2.2 The contractor shall integrate WPS with the JMPS Weather CC to provide an option to automatically retrieve forecast wind data as required by each weapon Fly-Out-Model (FOM).

2.2.3 The contractor shall develop a WPS Timeline Tool that visually depicts mission action points along a timeline for selected Joint Designated Points of Impact (JDPI).

2.2.4 The contractor shall provide a software prototype 6 months after contract award (ACA). WPS PO will review the software design to ensure it provides a viable approach to continue onto the ER build to be delivered March 2020. The contractor shall ensure WPS software meets the following requirements:

2.2.4.1 GPS Jamming Requirements

· WPS shall integrate with the GPS CC GIANT tools to provide GPS jamming analysis.

· The WPS software shall provide GPS jamming analysis results to the planner in a clear and understandable manner.

· The user shall be able to use the GPS jamming results to optimize PGM deliveries in a GPS contested environment.

· WPS GPS jamming analysis shall support long range multi-waypoint and salvo weapons.

2.2.4.2 Weather Common Component

· WPS shall allow the user to retrieve required wind, temperature and other weather data for input into each weapons fly-out calculation as supported by the FOM when such data is available through Weather CC.

2.2.4.3 Timeline Tool

· The Timeline Tool shall provide a visual depiction of mission data as a function of time to aide in weapon planning and de-confliction. As a minimum, critical weapon events such as release, impact and action points shall be depicted.

2.2.5 Table 1 shows the SRD new features to be used as a basis for initial proposal evaluation. At the post award conference through collaboration, the Government and awardee will review the product backlog and establish the initial priority list for this effort within the awarded cost and Table 1 will be updated based on the agreement. This list may further be reprioritized throughout performance through collaboration between the PO and awardee, with final authority remaining with the Government. It is not the intent to modify this DO SOW each time reprioritization occurs.

Table 1-- WPS new features planned for WPS v2.2 (per Technical Requirement Document (TRD) and SRD v1.2.1)

Weather CC Integration

WPS Timeline Tool

2.6 Legacy Enhancements for WPS v2.1.X: This DO SOW invokes the basic contract SOW paragraphs 2.2.1 Engineering Release (ER), 2.2.2 Beta Release, and 2.2.3 FQT. Release of the Legacy WPS v2.1.X baseline is to provide a functional and complete WPS v2.1.X for MPE developers and test organizations to evaluate. CRs and SRD references in Table 2 shall be used to investigate and implement changes to WPS software for v2.1.X to resolve defects, provide enhancements, or comply with changes in the FW, aircraft UPC, other JMPS CCs, and the Air Force Standard Desktop Configuration (SDC). All prioritized WPS v2.1.X CR fixes are expected to be incorporated into the final WPS FQT product (tested under this CLIN). (Applicable CDRLs: A001, A002, A004, A007, A008, A009, A010, A015, A016, A017, A018)

2.6.1 The JMPS Common Time Playback Tool permits planners to conduct mission rehearsal on the JMPS graphical display. The tool currently only supports JMPS aircraft routes. The contractor shall provide a method to display weapon routes as part of the JMPS Common Time Playback Tool.

2.6.2 WPS v1.6 provides integration with the Laser Line of Sight – Planning Tool (LOS-PT) CC to meet the SRD 1.2.1 requirements in paragraph 3.2.2.5.7 (Bullets 1, 2, 4-6, and 9 only). The contractor shall integrate WPS v2.1.x with the CAF MPE 4.0 version of LOS-PT (when available) to meet the same requirements.

2.6.3 The existing WPS v2.0 vertical Launch Acceptable Region (LAR) (see Table 4 GFI item 10) shall be enhanced to provide weapon flight path display and interactive controls that allow the user to select a new release point and see an updated flight path. The user shall have the option to update the current weapon plan from the vertical LAR Tool.

2.6.4 Table 2 shows the CRs and SRD deferred requirements to be used as a basis for initial proposal evaluation. At the post award conference through collaboration, the Government and awardee will review the product backlog and establish the initial priority list for this effort within the awarded cost and Table 2 will be updated based on the agreement. This list may further be reprioritized throughout performance through collaboration between the PO and awardee with final authority remaining with the Government. It is not the intent to modify this DO SOW each time reprioritization occurs.

Table 2 -- Existing Legacy WPS 2.1.x CRs/DR’s & SRD Deferred Requirements

2.7 Travel: This SOW invokes the basic contract SOW para 2.5 Travel. The contractor shall travel to provide technical support as directed by the WPS PO to assist in the development and testing for WPS CR and DR prioritized fixes and integration for this DO capabilities. Trips required to support this effort are listed in Table 3. (Applicable CDRL: A017) Table 3-- Meetings requiring travel

(Days)

Miscellaneous travel for TIMS, training and/or working groups (China Lake, CA)

Miscellaneous travel for TIMs, training and/or conferences (Tinker AFB, OK)

Miscellaneous travel for TIMs, training and/or conferences (St Louis, MO)

Miscellaneous travel for TIMs, training and/or conferences (Nellis AFB, CA)

Miscellaneous travel for TIMs, training and/or conferences (Orlando, FL)

Miscellaneous travel for TIMs, training and/or conferences (Eglin AFB, FL)

Weapons Planning TIM (Eglin AFB, FL)

JTAF

(Fairfax, VA)

JMPS Integration (Orlando, FL)

ICWG

(Eglin AFB, FL)

ICWG

(Hanscom AFB, MA)

SJICWG

(Dayton, OH)

SJICWG

(Sandestin, FL)

Requirements Review Board (RRB) (Nellis AFB, NV)

UAI MP3 IPT Support (Dayton, OH)

Miscellaneous JMPS Training

CAF Dev Evaluations

2.8 Materials: This SOW invokes the basic contract SOW para 2.6 Materials. Appendix B identifies the seven (7) computer systems required to be purchased within the first 3 months of award by the contractor for this effort. The contractor shall provide supporting documentation and price analysis to the PO and PCO for approval prior to purchasing these items. The contractor shall notify the PO and PCO within 3 days of receipt so the basic contract GFP listing in Section J can be updated accordingly.

2.9 Time and Material: This SOW invokes the basic contract SOW para 2.7 Time and Material (T&M)/Labor Hour (LH). This allows for additional software development, testing, and validation should unplanned issues arise and are determined as critical, need to be included in this DO, however are too complex to incorporate via reprioritizing within already agreed upon priorities. At award of this DO, the Government will provide a Not-To-Exceed (NTE) amount as the overall ceiling for this. No performance shall be accomplished on this CLIN without the written approval by the PCO for specific tasks. (CDRLs: will be determined upon execution of need).

2.9.1 Task Request Process: Upon identification of the need for T&M, the contractor shall complete the Section J, Attachment 8 - T&M Request and Approval Form, and submit to the PCO. The PCO will coordinate with the Government PO to determine validity of requirement and the reasonableness of the requested hours and NTE amount (ceiling) for subject task. The amount shall be calculated by the number of hours per labor category multiplied by the approved rates in Attachment 7 in Section J. The sum of calculations will form an estimated total cost for the specific effort. The PCO will provide the contractor approval/disapproval via signed form for which the contractor must manage the approved ceiling for the specific task in accordance with FAR 52.232-7 Payments Under Time-and-Materials and Labor-Hour Contract. The contractor shall not proceed with any performance on this CLIN without written approval from the PCO.

3. General Requirements:

3.1 Resources: This section invokes the basic contract SOW Section 3. The contractor shall provide all necessary resources identified within section 3 of the basic contract SOW to meet these DO requirements. All efforts and costs associated with section 3 shall be captured within each CLIN as it pertains.

3.2 Meetings: The contractor shall host informal design telecoms and Technical Interchange Meetings (TIMs) as required that will not require travel. The contractor will provide telephone and e-mail support for the following specific meetings:

· Two (2) three-day Design/Sprint Reviews at contractor facility

· Participate in 26 Bi-weekly technical discussions with stakeholders

· Support In-Progress Reviews (IPRs) both on site and by video/telecom

· Participation in ICWGs, conferences, training and other similar meetings. This includes: preparing for meetings, organizing/conducting meetings, or providing inputs/responses as needed, i.e., in response to Interface Change Notices (ICNs).

3.3 Government Information: This SOW invokes the basic SOW para 3.10 for Government Furnished Information (GFI). The contractor shall maintain required due dates, track items received and overdue, and inform the Program Office and PCO of late/missing/unacceptable GFI. GFI common to this entire SOW is listed Table 4.

Table 4 Government Furnished Information

Item No.

Nomenclature

Planning Tool IDD

4. Contractor Performance: This section invokes the basic contract SOW Section 4. The Contractor shall provide all necessary resources to ensure compliance with all requirements within the section. The contractor shall host the initial Integrated Baseline Review within 90 days of contract award. (Applicable CDRLs: A002, A015, A016, A018 )

5. Contract Data and Contract Data Requirements List (CDRL)/Deliverables: This SOW invokes the basic contract SOW paragraph 2.9. Data submissions are considered Not Separately Priced. Below is a summary of this DO’s required Deliverables and CDRLs.

Table 5: Deliverables & CDRL due dates:

CDRLs (Contract Data Requirements List) Description

APPENDIX A: Notional WPS 2.X Build Plan

Appendix B Contractor Acquired Equipment WPS Specifications for the GETAC S410

Requirement #2: 3 systems - Configuration shown below:

Same as Configuration 1 above, with Wifi card installed

FA8681-18-R-0006

Section J – Atch 15 Initial Deliver Order Package image1.jpeg