PWS.pdf

11 Feb 2025

Performance Work Statement (PWS)

F-16 TECHNICAL SUPPORT SERVICES

FOR F-16 RADAR SYSTEMS AN/APG-66/68

Prepared by:

Steve LeFevre, F-16 Radar Lead Engineer

416 SCMS/GUEAA

6070 Gum Lane Hill Air Force Base, Utah 84056

Table of Contents

Contents

1.0 SCOPE AND PURPOSE

1.1 Scope

1.2 Background

1.3 Purpose

2.0 MANAGEMENT

3.0 CONTRACT

3.1 Summary

3.2 Data System Content

3.3 Data System Access

3.4 Data Configuration Control

3.4.1 Government Generated Engineering Drawing Changes

3.4.2 Contractor Generated Engineering Drawing Changes

3.5 Data System Maintenance

3.6 Data System Configuration/Performance Requirements

3.6.1 Data Access

3.6.2 Data Viewing

3.6.4 Hardware and Software at Contractor

3.6.5 Operating Instructions

3.7 Government Furnished Property (GFP)

3.8 Data System Security

4.0 PERFORMANCE AND REPORTING

4.1 Period of Performance

4.2 Status Reports

5.0 SERVICES SUMMARY

1.0 SCOPE AND PURPOSE

1.1 Scope

This Performance Work Statement (PWS) describes tasks to be performed in support of the Air Force Sustainment Center (AFSC) for performing its assigned responsibilities for the F-16 Weapon System. Specific support will be for the F-16 radar systems AN/APG- 66/68 except for the AN/APG-68(V)9 unique drawings. The tasks include maintaining the F-16 Radar ED On-Line database for a period of 12 months (29 Sep 25 – 28 Sep 26.).

No future changes to the server hosting nor the software/application solution for the ED- Online system are identified during the POP.

1.2 Background

The F-16 radar system engineering team has a continual requirement to access the latest engineering and related radar data and configuration information for the AN/APG-66/68 F-16 radar except for the AN/APG-68(V)9 unique drawings. Currently, Northrop Grumman maintains the engineering technical data and ensures the data is current for the F-16 aircraft radar systems. This period of performance includes the necessary tasks for support of maintaining the Ed On-Line databases.

1.3 Purpose

This PWS will be incorporated into a contract to maintain support of the on-line engineering data and configuration control management system known as F-16 Radar Configuration Management System. The purpose of the contract is to continue to assist F-16 radar system sustainment engineering at AFSC by providing electronic access to radar system engineering and technical data.

2.0 MANAGEMENT

The AFSC Operations Division (416 SCMS/GUEAA & GUMAD) is responsible for management of the F-16 Radar program. The GUEAA & GUMAD program control team will have administrative management responsibility to include controlling access and ensuring appropriate distribution of data. The Contracting Officer (AFSC OL:H/PZABB) will be responsible for contract management.

3.0 CONTRACT

3.1 Summary

The Contractor shall maintain and operate the engineering/technical/configuration control data system at the contractor’s facility developed under contract F42620-94-D-0213, delivery order 10, providing personal computer access to radar system engineering drawings and associated technical documentation by U.S. Government personnel and other personnel as authorized by the 416 SCMS/GUEAA Lead Engineer. Specific requirements for this level of effort are defined in the following paragraphs of this section.

3.2 Data System Content

The data content shall consist of, as a minimum, all engineering drawings relating to the current configurations including those engineering drawings presently on the Northrop Grumman CADSTAR and MPLM data system for past configurations of the AN/APG- 66/68 F-16 Radar systems and the B1 common items; except for the AN/APG-68(V)9 unique drawings.

This group includes drawings that have been contractually bound for delivery in the past or current contract delivery requirements. Engineering drawings are defined as selected items drawings, vendor item drawings, altered item drawings, source control drawings, parts lists, process specifications, manufacturing specifications, test specifications, revision notices, top-down breakdown, etc.

The data shall also include all F-16 Radar applicable Technical Orders (TO), System Test Specifications (STSs), and Engineering Change Proposals (ECPs) except for the AN/APG-68(V)9 unique data. This definition is not intended to be a limiting set of parameters; it is intended as a clarification only. Other types of drawings fitting the above descriptions are also required, even though not specifically mentioned.

All data shall be properly marked with distribution statement ‘Statement D.’

3.3 Data System Access

The data in the system shall be capable of being accessed in an “on-line” fashion from a “PC” based government owned computer at any location that has direct internet access.

The system shall be capable of supporting up to twenty (20) sessions at any one time.

Data access shall be available 24 hours a day, except for short periods of planned maintenance or other activities requiring system shutdown.

System non-availability periods shall be limited to occur outside of normal working hours and then shall be announced ten days prior to shut down.

3.4 Data Configuration Control

The data contained in the system, extracted from the CADSTAR, ISE, and MPLM databases, shall be updated as required on at least a monthly basis with a target goal of twice per month.

Other data sources such as Technical Orders (T.O.s), System Test Specification (STS), Engineering Change Proposal (ECPs), etc. shall be updated in a timely manner, at least yearly, or as changes are made by other processes and systems.

No drawings or other data contained in this system shall be capable of being altered by an on-line user.

Online access shall be limited to read-only access.

Only approved contractor personnel at the contractor’s facility location shall change drawings and data. Any changes are to be developed by the contractor and approved by the government.

3.4.1 Government Generated Engineering Drawing Changes

The contractor shall review, accept or reject for submitted USAF ECOs and provide supporting rational for the decisions through their internal process.

3.4.1.1 Contractor Approval of ECO’s

When the contractor agrees with a government generated ECO, such that they decide they can adopt it as their own, the change shall be incorporated in the original drawing as a normal revision. When this is the case, the change shall appear as a contractor generated change on the original, or as-revised, drawing. These types of changes shall normally be limited to technical corrections or other changes in technical parameters. The contractor shall have complete control and authority regarding changes and updates that ultimately appear on the original or as-revised drawing document. These changes will not affect the distribution statements.

3.4.1.2 Government Data Attachment

If for any reason, the contractor does not agree with a change or does not wish to revise the configured drawing according to the change requirement, the change shall be placed on a separate document that is part of the data set and attached electronically to the applicable drawing.

The change shall be clearly identified as an Air Force generated requirement or change, clearly showing it as not being an integral part of the original or as-revised drawing developed and maintained by the contractor.

The government shall have complete authority regarding changes and additions to the data contained in the government data attachment.

Changes to the government data attachment will typically be additional supplier identification, alternate configurations approved by the Air Force, etc.

3.4.2 Contractor Generated Engineering Drawing Changes

The contractor shall submit changes through their internal process and then update the data in the system as required.

No contractor originated changes shall appear on the government data attachment described in paragraph 3.4.1.2, unless the government agrees to the change such that they decide they can adopt it as their own.

When the government agrees and adopts the engineering drawing changes, the change shall appear as an Air Force generated change on the government data attachment.

The government shall not have the ability to stop a properly processed contractor generated change that will ultimately appear on the original or as-revised drawing document.

3.5 Data System Maintenance

The database shall be operated and maintained by the contractor. This maintenance shall be in effect for the period of performance.

3.6 Data System Configuration/Performance Requirements

The exact configuration of software shall be maintained by the contractor to be compatible with the requirements stated in this document.

3.6.1 Data Access

Access to data shall be accomplished VIA Internet interface with “PC” based terminals using the following basic configuration:

• Pentium CPU

• 100 MHz minimum

• 16 to 32 megabytes of ram minimum

• 1 MB of video ram minimum

• 100 MB of available hard disk space

• Windows 2000 operating system or later

• Internet Browser – Internet Explorer A password protection system shall be implemented as referenced in section 3.7 Data System Security.

Data sets shall be available for viewing within an average of five (5) seconds of document file transfer. Batch downloading requested data for temporary storage via FTP or other similar method is preferred, unless other methods of rapidly moving from page to page within the five-second limitation are provided.

3.6.2 Data Viewing

Data viewing shall be accomplished using an industry common Windows(c) compatible viewer capable of displaying an entire page of any document at one time with zoom, rotation, panning, next page, previous page, local print, cut, paste and other features commonly available with viewers of this type.

Paging between pages of any data set shall be, on average, completed within 5 seconds.

3.6.3 Hardware and Software at Contractor

All software for storage, update, input, session management, source access, and general control shall be located at the contractor’s facility.

The selection of the actual required hardware and software shall be left to the discretion of the contractor in satisfying the requirements stated in this document.

3.6.4 Operating Instructions

The complete set of on-line operating instructions shall be maintained.

The instructions shall include detailed operating instructions covering the entire scope of how to use the system.

3.7 Government Furnished Property (GFP)

No GFP will be provided.

3.8 Data System Security

The contractor shall maintain a current plan, which addresses the security issues associated with allowing access to technical data via this system. As a minimum, the following security measures shall be kept up to date:

• TCP/IP address validation

• Encryption certificate

• User I.D. and password with validation

• Data encryption and decryption

• Common Access Card (CAC)

3.9 Configuration Data Delivery

A copy of the AN/APG-66 & AN/APG-68 Radar configuration data shall be provided to the government in spread sheet format annually.

A backup copy of the ED Online application and engineering database to include the engineering configuration, drawings, and drawing revisions.

Via CD/ROM Format in accordance with CDRL (A001).

4.0 PERFORMANCE AND REPORTING

4.1 Period of Performance

This level of effort as defined within this PWS shall not exceed the following periods of performance.

• ED Online continued maintenance performance from the date of award for a 12 month period,

4.2 Status Reports

The contractor shall provide a Monthly Status Report in accordance with CDRL (B001)

5.0 SERVICES SUMMARY

SDS # Performance Objective PWS Para. Performance Threshold Method of

Surveillance 1.1

1.2

Data System access is 24 Hours per day

Data Delivery is Accurate

3.3

4.2

System is unavailable three times per year, except for planned maintenance 3 Engineering data drawing faults and 2 configuration faults noted each year.

LMS will monitor system status

LMS inspection of content and collaboration with engineering team.

3.4.2 Contractor Generated Engineering Drawing Changes

5.0 SERVICES SUMMARY