Search_Pattern_Tool__STATEMENT_OF_WORK_06.21.2013.pdf

STATEMENT OF WORK (SOW)

FOR

SEARCH PATTERN TOOL UPDATE

1.0 Scope

This Statement of Work covers the anticipated technical and management expectations associated with the modification of the Portable Flight Planning Software (PFPS) Search Pattern Tool (SPT), hereafter referred to SPT. The purpose of this effort is to modify SPT and upgrade the software to work on Microsoft Windows 7 32 bit and 64 bit.

2.0 Background

The FPS software application development is being developed under the H-60 Conversion/Sustainment Projects Discrete Segment (DS1), Avionics Upgrade. The H-60 DS1 provided for the avionics upgrades to the H-60 aircraft. As part of the DS1 effort the project is also developing the Flight Planning Suite (FPS) to support the avionics upgrades. The FPS combines and integrates the flight planning tools, such as the Aircraft Weight and Balance System (AWBS), the Stores Loading and Balance (SLAB), and the Performance Planning Calculator (PPC) together with mission planning tools such as Avionics, Weapons, Electronics (AWE) and Personnel Flight Planning Suite (PFPS).

The SPT supports PFPS as it provides the ability by aircrews to plan airborne searches using a variety of search patterns such as the Circle pattern, Creeping Line pattern, Expanding Square pattern, and Sector pattern. The SPT will create search patterns using the PFPS route structure and read/write search pattern data to the associated route point in the PFPS route and import search patterns through the use of a compact flash card into the PFPS which is integrated into the comprehensive FPS.

3.0 Requirements

3.1 SPT shall be modified to operate on PFPS 4.2.X to include operating on Window XP, Vista, Windows 7 32-bit, and Windows 7 64-bit WoW64 mode. In addition, the following enhancements shall be accomplished:

3.1.1 Installation Program

The InstallShield project shall be upgraded to InstallShield 2012 and modifications to support the ability to run in the Windows 32-bit on Windows 64-bit environment.

3.1.2 Modification of Patterns

The following changes to the patterns shall be accomplished:

3.1.2.1 Rename of “Creeping Line” to “Ladder”

The current “Creeping Line” pattern shall be renamed to “Ladder” to match the aircraft nomenclature.

3.1.2.2 Add “Creeping Line (CS)” and “Parallel” (PS) to the Ladder Pattern

A toggle shall be added to the “Ladder Pattern” tab to allow the user to select either a CS or PS variant of the ladder pattern.

3.1.2.3 Redesign of Pattern Tabs

The different pattern tabs shall be redesigned to closer resemble the layout on the

CDU.

3.1.2.4 Assigning a Lead in Point

The SPT shall be modified so the user can designate a “Lead in Point”. This point will used to align the initial heading prior to the Commence Search Point (CSP) point as to define the heading when hitting the CSP.

3.1.3 Location Tab Modifications

The location tab shall modified so that the user can select the point type to be used such as the Commence Search Point (CSP), Center Point (CP), or the Anchor Point (AP). The pattern shall be generated using the point type the user entered.

3.1.4 Import Function Modification

The import function shall be modified so that when the user imports a pattern from an external tool (SAROPS, AUXAR, etc.) the pattern will be locked and cannot be changed without deliberately unlocking the pattern. When the pattern is locked, pressing the “OK” button will give a warning that the pattern is locked and then close the dialog. Pressing the “Apply” button will only give a warning that the pattern is locked.

3.1.5 GPS Export

The SPT shall be modified to include the capability to export a GPX file with the search pattern to GPS equipment that can import such a file.

3.1.6 Context Sensitive Help

Context Sensitive Help shall be updated to include the new enhancements.

4.1 User Events

The contractor shall host two (2) user events during the development process to demonstrate prototypes of the different modifications which will allow the user to give inputs to nomenclature and layout of the different user interfaces (UI). Any changes to this SOW and/or changes to or approvals of prototypes will be made in writing by a signed bilateral modification issued by the Contracting Officer.

5.1 Government Furnished Information

Portable Flight Planning Software (PFPS) V4.2 sp1 Portable Flight Planning Software (PFPS) V4.2.2

6.1 Deliverables

The CDRLs in the following table shall be updated and delivered in the Software Product Specification (SPS) at the completion of the project. Except the SPT Monthly Status

Report which is to be delivered at the end of each month.

CDRL # Title A001 SPT Monthly Status Report A002 SPT for PFPS Software Requirements Specification (SRS) A003 SPT for PFPS Requirements Traceability Matrix (RTM) A004 SPT for PFPS Software Test Description (STD) A005 SPT for PFPS Software Test Report (STR) A006 SPT for PFPS User Guide (UG) A007 SPT for PFPS Software Version Description (SVD) A008 Executable Code A009 SPT for PFPS Software Product Specification (SPS)

7.0 Travel

No contractor travel is anticipated for this effort.

8.0 Period of Performance

Six (6) months after contract award.