Statement_of_Work_SPT_Modification_REVISED.pdf

Statement of Work

For

Search Pattern Tool Update

1.0 Scope

The Scope of this effort is to modify Search Pattern Tool (SPT) to provide interface(s) to allow Aircraft

Weapons and Equipment (AWE) application to generate Search Patterns in a route. This is typically used when reading back information from the aircraft.

2.0 Government Furnished Information

The following will be provided to the Contractor.

a. Portable Flight Planning Software (PFPS) V4.2.1

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

c. Portable Flight Planning Software (PFPS) V4.2.2

3.0 Requirements

The Contractor shall modify the SPT to:

3.1.1 Add functionality so that the AWE can create a route file with search patterns from an avionic flight plan when the AWE reads from an avionic loaded card.

3.1.2 The SPT shall be able to receive from the AWE the IRouteData object from of the corresponding route that contains the route points to add search patterns to the route.

(Note: The reason for passing the IRouteData object versus the route file path is to allow the AWE to create search patterns WHILE it is creating the route file instead of having to wait until the route file has been saved to a disk.)

3.1.3 The SPT shall be able to receive the desired CSP’s route point index from the AWE.

3.1.4 The SPT shall be able to receive the PatternData object from the AWE that contains the specific search pattern data for creation (same object that is returned when the AWE utilizes the GetPatternData) method from the interface).

3.1.5 The SPT shall be able to receive the enPatternType enumeration from the AWE to indicate what kind of search pattern to create.

3.1.6 The SPT shall insert the ESP after the specified CSP based on the provided search pattern data provided.

3.2 Performance Requirements

SPT shall perform the following:

3.2.1 Generate a Search pattern in the route with the data provided.

3.1.2 The PFPS route server will display the Search Pattern as generated.

3.1.3 The SPT shall save the data as a route block so the following can be accomplished:

a. The user can use SPT to modify the search pattern

b. An AWE can read the SPT data to be loaded to a data load.

3.3 Common Mission Data Load

3.3.1 Testing CMDL with Windows 7 and PFPS 4.2.2

JTE shall test compatibility and functionality of CDML on Windows 7 and PFPS 4.2.2.

JTW shall perform the Functional Qualification Test (FQT) procedures.

JTE shall develop and provide a FQT Test Report.

3.3.2 Testing CMDL with DAFIF 8.1

JTE shall validate that DAFIF data transfers a properly with PFPS 4.2.2 using DAFIF 8.0 and DAFIF 8.1.

JTE shall validate that DAFIF update works properly with PFPS 4.2.2 using DAFIF 8.0 and DAFIF 8.1.

3.4 Support for AWE FQT

JTE shall provide engineering services support for any questions or modifications to SPT to provide proper transfer of data from SPT to the MH-60T AWE and from the MH-60T to SPT.

3.5 Engineering Releases

JTE shall provide two (2) engineering releases to the USCG and US Army AMRDEC developers for review.

5.0 Travel

No travel is anticipated for this effort. Any travel required or requested by the customer will be directly reimbursable by the Government IAW the Joint Travel

Regulations.

6.0 Period of Performance

The Period of Performance is from contract award through November 2014.

4.0 Deliverables

The CDRLs in the following table will be updated and delivered in the Software Product Specification

(SPS) at completion of the project with the exception of the Monthly Status Report, which is delivered monthly.

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)

A010 CMDL Test Report (STR)