AMDS PWS Draft 27 Jan 2023.pdf

PWS DRAFT 1

Performance Work Statement for

Aircraft Maintenance Debrief System (AMDS)

DRAFT

27 Jan 2023

PWS DRAFT 2

1.0 Description of Services

1.1 Objective(s): This Performance Work Statement (PWS) describes the services required to provide Aircraft Maintenance Debrief System (AMDS) administrative and support services to the Royal Saudi Air Force (RSAF) in AMDS facilities at locations throughout the Kingdom of Saudi Arabia. This effort includes providing Aircraft Maintenance Debriefing System (AMDS) administrative and technical support services to the Royal Saudi Air Force (RSAF) for maintaining their F-15C, D, S and SA operating squadrons at up to six (6) locations throughout the Kingdom of Saudi Arabia.

The RSAF requires contractor support to assess, install new equipment when required, maintain hardware and software, provide trained Saudi AMDS administrators, and provide familiarization training to other Saudi nationals that will enable the RSAF to safely and efficiently operate all AMDS equipment at all AMDS operating locations. AMDS technical services personnel are needed to manage and maintain AMDS equipment to carry out day-to-day reporting of F-15 post flight fault data in support of the RSAF flight operations. Most of the contractor's support shall be conducted in the Kingdom of Saudi Arabia except for Red/Green Flag training exercise support or other deployments. Software development will be accomplished by Boeing within the Continental United States. Other services include producing documents to meet RSAF requirements in the correct format and on time.

Services to be acquired under this effort include, but are not limited to, providing fully-trained AMDS engineers to maintain AMDS and provide AMDS familiarization training to RSAF members that will enable them to safely and efficiently operate all AMDS equipment. Other services include producing documents to meet RSAF requirements in the correct format and on time to include GOLDesp information integration. The Contractor shall employ sufficient quantities of AMDS engineers to meet contractual requirements. The Contractor team should become an integral part of the RSAF team with the overall mission of maintaining safe and efficient F-15C, D, S and SA flying and maintenance operations.

AMDS administrative and engineer personnel shall be required to manage and maintain AMDS activities including, but not limited to, acquiring supplies and equipment in support of AMDS, facilitating day-to-day post mission debriefing and fault reporting of F-15 flight operations and distributing post mission AMDS reports, and integration of AMDS information to the RSAF GOLDesp system throughout the Kingdom of Saudi Arabia as directed by the RSAF.

AMDS technical engineers shall be required to manage and maintain AMDS equipment, including printers and client workstations, and to ensure that all AMDS equipment is functioning properly. Duties shall include, but not be limited to, assessing existing equipment, diagnosing

PWS DRAFT 3

equipment failures, recommending new and or replacement equipment, installing new and or replacement equipment, maintaining hardware and developing, implementing software and system updates and providing training to the RSAF personnel on a recurring or as-needed basis.

This effort shall consist of a basic contract period of performance of thirty-six (36) months with two (2) one (1)-year option periods and one (1) six-month extension of services option. AMDS administrative and support services shall be provided in-Kingdom, except software development, Red/Green Flag support or other exceptional deployments.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States Air Force (USAF) by insuring the continued readiness of the Royal Saudi Air Force F-15 fleet.

The Kingdom of Saudi Arabia is an ally to the United States. www.airforce.com/mission.

1.3 Background:The effort is a continuation of existing support provided to the RSAF by contract FA8505-19-C-0001, to collect and analyze in-flight data from RSAF F-15 C/D/S/SA aircraft. There are minimal changes to level of support of this and the previous contract. This effort continues to collect aircraft systems/fault information during flight, which is then downloaded and evaluated to determine possible required maintenance actions. Historical AMDS data is analyzed to assist in determining possible changes in the RSAF F-15 fleet periodic inspection programs. These tasks and programs are essential in maintaining the structural health of the aging RSAF F-15 fleet and assuring operational safety.

2.0 Services Summary

Performance Objective

PWS

Reference

Performance Threshold Method of Surveillance

Develop Bi-annual Software Updates for AMDS

4.3.1 Develop two (2) scheduled

AMDS updates, including software and technical data updates, per contract year.

Contractor shall provide a list of candidate updates. Contractor candidate list shall include resolutions to all problems identified to AFLCMC/WWQIA within 60 days prior to release.

Surveillance will be conducted monthly by the COR reviewing Monthly Reports and customer complaints.

Surveillance will be documented quarterly by the COR(s) in the

PAR.

PWS DRAFT 4

Saudi National

AMDS

Administrators

4.4.4 The Contractor shall install the

AMDS update within seven (7) business days after receipt in- Kingdom from a USG or RSAF representative. The Contractor AMDS engineers shall be responsible for completing all actions required that facilitate AMDS installation, operations and update of the AMDS system in support of daily post mission operations. The Contractor AMDS Engineers shall download all AFTO-239 and Signal Flight Data Recorder (SFDR) data monthly from each squadron’s AMDS database and upload the data to Boeing WebSafe System.

The Contractor shall provide a statement of verification that data was downloaded/uploaded along with any deficiencies in this process in each monthly CDRL report.

Surveillance will be conducted monthly by the COR reviewing Monthly Reports and customer complaints.

Surveillance will be documented quarterly by the COR(s) in the

PAR.

Provide Reports for Any AMDS Problems

4.3.2 Provide interim report for any

problem encountered within two

(2) business days of problem discovery.

Survelliance will be conducted monthly by the PM/COR evaluating problems with AMDS fucnctionality using logs, monthly reports, email and telephone reports, and customer complaints.

Survelliance will be documented quarterly by the COR(s) in the

PAR.

Maintain Operational Availability for

AMDS

4.3.3 The Contractor shall maintain

96% AMDS workstation availability status per contract month with exceptions noted.

Surveillance will be conducted quarterly by the COR by reviewing the data provided by the

PWS DRAFT 5

AMDS workstation availability is defined as the workstation will be running Windows 7.

Program metrics shall be calculated based on the system health status documented in the AMDS Daily Status Log and shall be attached to the monthly report.

Contractor during the quarterly review meetings.

Surveillance will be documented quarterly by the COR(s) in the

PAR.

Contribute to and report on meetings

4.4.2

5.12

Attend AMDS meetings and provide meeting minutes within ten (10) business days of any AMDS meeting.

The Contractor shall provide preliminary meeting agenda and briefing outline at minimum thirty (30) days prior to the PMR for USG and RSAF review. The briefing materials will be provided fourteen (14) days prior to the PMR for the USG and RSAF review. The Contractor shall be responsible for providing meeting minutes.

Surveillance will be conducted as needed by the COR.

Surveillance will be documented quarterly by the COR in the PAR.

AMDS/GOLDesp Integration

4.8.2 The Contractor shall have

AMDS/GOLDesp integration accomplished by the end of the second year of this contract.

Survelliance will be conducted monthly by the COR.

Survellance will be documented quarterly by the COR(s) in the

PAR.

Adherence to Contractor Quality Management System (QMS)

5.9 100% compliance with the QMS is required.

Surveillance will be conducted by the COR reviewing the contractor’s QMS to ensure that it is effective in bringing the desired results (performance is equal to or greater than the SS metrics).

Surveillance will be documented quarterly by the COR in the PAR.

PWS DRAFT 6

3.0 Government Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 Government Property to be Provided: Government property to be provided includes but not limited to:

3.2.1 RSAF Property: All property furnished by the RSAF shall remain the property of the RSAF and be returned to the RSAF upon completion of the contract. When conducting activities related to warranty or over and above repairs of existing RSAF AMDS equipment, the Contractor shall ensure the equipment is repackaged sufficiently for safe shipment to the Kingdom of Saudi Arabia. Any additional AMDS equipment procured under this contract shall become the property of the RSAF upon acceptance at origin. The RSAF will make available the facility, materials, office supplies, furniture, equipment, office space, communications capability and information required to successfully accomplish contractual requirements for the entire period of performance of the contract including any options or extensions. Once Government property is provided, the contractor shall provide an initial inventory of all AMDS material, including the condition of each piece of equipment at each location, within 90 calendar days after contract award. The Contractor shall provide a final annual inventory and status assessment of all AMDS equipment at each location not later than 45 days prior to the end of the current basic or option year. (Status of USG Furnished Equipment (GFE) Report)

3.2.2 Manage Hardware Warranty Program for AMDS

The Contractor will administer the equipment warranty provided by the equipment manufacturer as follows:

The Contractor shall respond to AMDS equipment abnormalities, and when required, pack and ship equipment under warranty back to the manufacturer and receive and reinstall repaired or new equipment from the manufacturer. If the AMDS Administrator determines that a piece of equipment requires a return shipment to the manufacturer the USG will provide the shipping account (FedEx, DHL) for any warranty items that do not have shipping covered under the warranty agreement. The Contractor shall request this shipping account from the USG when applicable. Items shipped will be tracked using a carrier tracking number. When an item is returned from a manufacturer, the Contractor shall reinstall the status of the item in the Monthly AMDS status log. Each AMDS Administrator will have a separate warranty shipping log to record carrier tracking numbers for returned items. Equipment status shall be documented in the monthly status reports using the Attachment 1: Sample as a guide. Equipment failures and the corrective action required shall be documented using a Failure Analysis and Corrective Action Report as necessary.

The Contractor shall provide the USG in the monthly status report warranty items that have been removed from the RSAF Base/Squadron for warranty repair that includes, Item Nomenclature, Part Number, and Estimated Delivery Date.

The Contractor shall be responsible for replacing warranty items that have been deemed

PWS DRAFT 7

beyond economical or physical repair (BER/BPR). The Contractor shall report to the USG items that were scrapped along with the part number and serial number of the replacement item in the monthly status report. (Status Report), (Failure Analysis and Corrective Action Report)

3.3 Base Support: The RSAF will make available the facility, materials, office supplies, furniture, equipment, office space, communications capability and information required to successfully accomplish contractual requirements for the entire period of performance of the contract including any options or extensions.

3.4 Reporting of Government Property: The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7002. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

3.5 Loss of Government Property

3.5.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.5.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

3.6 Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

https://piee.eb.mil/ https://dodprocurementtoolbox.com/ https://piee.eb.mil/piee-landing/

PWS DRAFT 8

3.7 Contractor Acquired Material

When required, and procured via contract modification to this contract, new AMDS material shall be shipped from in-Kingdom vendors to the Depot Supply at Dhahran for inspection and acceptance by DCMA. AMDS equipment shall then be prepared for AMDS software installation.

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: The period of performance for the contract/order will extend five years from award.

4.1.2 Place of Performance: These services will be performed on RSAF installations or facilities within the Kingdom of Saudi Arabia with the exception of infrequent meetings conducted at other locations to be determined and when supporting Red and or Green Flag or other exceptional deployments.

Contractor personnel shall provide eight (8) hours per day of AMDS support as coordinated with the assigned base/squadron commander based on the local flying schedule daily from Sunday through Thursday. Work hours shall be determined by the RSAF, but shall not exceed eight (8) hours per day. All RSAF holidays shall be observed by Contractor personnel unless a requirement for AMDS support arises. Exceptions shall be identified to the PCO and USG program manager in writing at least seven (7) calendar days prior to the time AMDS support will be required to work. Services provided under this contract are in support of multiple RSAF sites [including Programmed Depot Maintenance (PDM) and F-15 S Conversion Facility when and if required] throughout the Kingdom of Saudi Arabia. It is the Contractor's responsibility to arrive at required facilities at the appropriate time to perform work under the contract. All Contractor personnel are required to adhere to all RSAF rules, regulations and policies at each location.

Locations supported under this contract include:

• RSAF Headquarters, Riyadh, Saudi Arabia

• King Khalid International Airport (KKIA) F-15 Facilities, Riyadh, Saudi Arabia

• King Khalid Air Base, Khamis Mushayt, Saudi Arabia

• King Abdul Aziz Air Base, Dhahran, Saudi Arabia

• King Fahad Air Base, Taif, Saudi Arabia

• King Faisal Airbase, Tabuk, Saudi Arabia Prince

The following locations may be supported with AMDS when site activation is complete to support F-15 aircraft (to be negotiated at a later date):

• King Saud Airbase, Hafr al Batin, Saudi Arabia

• Al Jouf AB, Al Jouf Airbase, Saudi Arabia

4.2 Contract Data Requirements List(s) (CDRL)

Document Identifier

Option Year

Option Year

Option Year

Option Year

DID Title PWS Reference(s)

PWS DRAFT 9

Base Year 1 2 3 4 A001 B001 C001 D001 E001 DI-ADMN-81250B Conference Minutes 4.4.2, 5.

A002

B002 C002 D002 E002 DI-MGMT-

80368A/T

Monthly Reports 3.2.2, 4.3.2, 4.3.3, 4.4.1, 4.4.3, 4.4.5, 4.8.2, 4.9, 5.12, 5.13.3, 5.13.4

A003 B003 C003 D003 E003 DI-MGMT-80269 Status of USG Furnished Equipment (GFE) Report

3.2.1, 4.3.3

A004 B004 C004 D004 E004 DI-SESS-80255A/T Failure Analysis and Corrective Action Report

3.2.2

A005 B005 C005 D005 E005 TM-86-01Q(T) Technical Manual Contract Requirement

4.3.1

A006 B006 C006 D006 E006 DI-MISC-80508B Technical Report – Study/Services

4.10

A007 B007 C007 D007 E007 DI-ADMN-81249B Program Management Review Agenda and Briefing Materials

4.4.2

A008 B008 C008 D008 E008 DI-QCIC-81722 Quality Program Plan 5.9 A009 B009 C009 D009 E009 DI-SAFT-81626/T System Safety Program Plan 5.5.4

4.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable. There shall be no more than two (2) total rejection(s) of deliverables per contract year. The Government will reject a deliverable if two (2) or more technical errors or three (3) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within seven (7) business days of notification of Government rejection.

4.2.2 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Wide Area WorkFlow (WAWF) and submitted directly to the MFT member identified on the CDRL. There shall be no more than 2 late submission(s) of deliverables per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.3 Service Requirements Operate and Maintain AMDS Equipment

4.3.1 AMDS Updates: The Contractor shall develop two (2) scheduled AMDS (SR1F-15C-2- 00FR-CD-1) Fault Reporting (F-15C/D/S/SA) updates per twelve (12) month period of performance, including software and technical data updates, per contract year. Contractor shall provide a list of candidate software and data updates with recommended resolutions to AFLCMC/WWQIA and RSAF HQ for review and approval not later than sixty (60) days prior to the scheduled release. The United States Government (USG) will review and approve the list with or without changes within 10 business days of receipt. Contractor shall proceed with the list of candidate changes as written or with changes submitted by the USG within 60 days prior to the scheduled release. A Pre-Publication On-line Review Meeting will be held between the

PWS DRAFT 10

Contractor, USG, and RSAF (if requested) thirty (30) days prior to the final release to review the updates that will be incorporated into the scheduled release. Details of the SR1F-15C-2-00FR- CD-1 update and release process shall be included in TM-86-01, Technical Manual Contract Requirements (TMCR) (A005, TM-86-01Q (T)).

The initial AMDS 3.0 release of 2021 will deliver no later than 31 May 2021 to support debrief for RSAF F-15 SA aircraft. A final AMDS 3.0 release to support debriefing C/D/S aircraft will be released by 31 October 2021.

Installation of AMDS 3.0, in a centralized and virtualized environment, is contingent upon the availability of pre-production and production equipment in the RSAF Data and Disaster Recovery Centers. The pre-production environment will be used for testing, integration, and familiarization training. The production environment will be used to ensure high availability and disaster recovery of the AMDS 3.0 software. A contract modification, with appropriate funding, is required to procure the equipment. Any delay to the delivery of the pre-production or production equipment could cause a delay to the transition and release of AMDS 3.0.

The contractor will produce additional releases depending on the criticality and impact of AMDS issues as determined by the contractor, USAF and RSAF.

4.3.2 Provide Reports for Any AMDS Problems

The Contractor shall document any problem impacting the day-to-day post mission debriefing and fault reporting of F-15 flight operations and the generation and distributing post mission AMDS reports. Identified problems shall be documented in the AMDS Monthly Status Log (sample included in Attachment 1 of the contract) and provide an email detailed interim report to AFLCMC/WWQIA within two (2) business days of problem discovery. The Contractor shall include a copy of each squadron's AMDS Daily Status Log as an attachment to the Monthly Report. (Status Report).

4.3.3 Maintain Operational Availability for AMDS Workstations

The Contractor shall maintain a ninety-six (96%) percent AMDS workstation availability status per base per contract month. AMDS workstation availability applies to:

• Equipment that is in warranty.

• Equipment that is out of warranty until it fails. Failed out of warranty equipment will not be subject to this metric while it is being repaired or replaced.

AMDS workstation availability is defined as the workstation will be running Windows 7 or a later version. For AMDS to operate and be available for any debrief operations the AMDS workstation must be always be able to communicate at all times to the AMDS server for all AMDS functions.

Therefore; because the Contractor does not have control over the network and direct access to the AMDS server, overall AMDS availability cannot be guaranteed.

PWS DRAFT 11

Program metrics shall be calculated based on the system health status documented in the monthly AMDS equipment status log and shall be attached to the monthly report. The Contractor shall provide system operation reports indicating any time AMDS workstations are not available, if any workstation is in awaiting parts (AWP) status, what parts are required, and the estimated delivery date for parts as well as a work-round solution to be implemented until the AMDS workstation is returned running Windows 7 (or Windows 10).

The installation of the all sustainment releases will not be included in operational readiness calculations. (Status of USG Furnished Equipment (GFE) Report), (Status Report)

4.4 Logistics Support Services

4.4.1 Provide Familiarization Training on Operating AMDS

The Contractor shall provide annual AMDS familiarization training as required, to ensure all debriefers, operators, planners, schedulers, maintenance control and analysis office can operate equipment safely and independently. Trained individuals will be able to identify various AMDS parts and equipment and be able to turn the equipment on and off safely and independently be able to perform the specified task as it relates to AMDS and debrief. In the Status Report, the Contractor shall provide details (number of personnel and the unit of assignment) of any AMDS familiarization training conducted during the period of performance of that report. The Contractor shall train a minimum of one (1) RSAF Debriefer at each squadron to have administrative rights and capability to conduct AMDS operations in the absence of a Contractor engineer. (Status Report).

4.4.2 Attend Meetings in Support of AMDS

The Contractor shall host, conduct, or support up to one (1) CONUS and one (1) OCONUS based Program Management Reviews (PMR) and/or Technical Interchange Meetings (TIMs) per year in support of the AMDS Support contract. RSAF will participate in all meetings. The Contractor shall provide preliminary meeting agenda and briefing outline at minimum thirty (30) days prior to the PMR for USG and RSAF review. The briefing materials will be provided fourteen (14) days prior to the PMR for the USG and RSAF review. The Contractor shall be responsible for providing meeting minutes within 10 business days. (PMR Agenda and Briefing Materials) and (Conference Minutes)

4.4.3 In-Kingdom AMDS Technical Representative

The Contractor shall provide an AMDS Program Technical Representative that will be assigned to RSAF HQ Directorate of Aircraft Maintenance to support all AMDS locations. The AMDS Program Technical Representative shall train up to six (6) Saudi national AMDS administrators as required to update, ensure operation of AMDS and provide the RSAF with familiarization training on the AMDS system. The AMDS Program Technical Representative shall contribute to the status reports delivered to the USG detailing the performance of the overall AMDS system.

The AMDS Program Technical Representative’s responsibilities are the operation, maintenance of AMDS systems, and training of RSAF debriefers. The AMDS Program Technical

PWS DRAFT 12

Representative shall interface with the RSAF HQ for AMDS daily status, AMDS system readiness and liaison with Contractor AMDS engineers throughout the Kingdom. (Status Report)

4.4.4 Saudi National AMDS Administrators

The Contractor shall initially train five (5) Saudi national AMDS administrators stationed at AMDS operational installations throughout the Kingdom of Saudi Arabia. Based on the F- 15SA site activation plan, additional AMDS engineers may be employed and trained to support additional installations as needed (to be negotiated). The engineers shall be fully trained to install, update, operate the AMDS system, and to train RSAF personnel per paragraph 4.4.1.

The Contractor shall install the AMDS update within seven (7) business days after receipt in- Kingdom from a USG or RSAF representative. The Contractor AMDS engineers shall be responsible for completing all actions required that facilitate AMDS installation, operations and update of the AMDS system in support of daily post mission operations. The Contractor AMDS Engineers shall download all AFTO-239, Signal Flight Data Recorder (SFDR), Processor Removable Memory Module (PRMM) Data Record Function (DRF) and Flight Log data monthly from each squadron’s AMDS database and provide the data to the Aeronautical Engineering Squadron (AES). The Contractor AMDS Engineers shall provide data and interact regularly with the ASIP program, including participation in ASIP PMRs and support to the AES.

The Contractor shall provide a statement of verification that data was downloaded/uploaded along with any deficiencies in this process in the monthly report. (Status Report)

4.4.5 Deployment Support for AMDS Activities

The Contractor shall provide technical support to the RSAF, prior to and during their participation in Red/Green Flag exercises at Nellis Air Force Base (AFB), NV up to once a year.

Support shall include verifying that AMDS required data for each aircraft deploying was prepared properly and completely, verifying proper operation of the deployed AMDS workstations, processor removable memory module (PRMM), and AMDS data transfer module (DTM) readers. Additional support shall include providing AMDS refresher training for the debrief administrators, maintenance personnel and aircrew members, ensuring all software security/anti-virus profiles are current, establishing regular backup sessions, and providing over-the-shoulder AMDS support if required. For the duration of a deployment, the Contractor shall provide daily reports on the status of AMDS activities. At the conclusion of the deployment, the daily reports will be consolidated and included in the next available Monthly Status Report.

The Contractor shall provide phone engineering support for other RSAF deployments in and out of Saudi Arabia. The Contractor shall prepare all deployable AMDS equipment and ensure all software updates are current and equipment is fully operational prior to being deployed. (Status Report)

4.5 AMDS Systems

AMDS Version 2.0 is the replacement system for Computerized Fault Reporting Systems (CFRS) that supports F-15 C/D/S/SA model aircraft. Any CFRS hardware upgraded under the F- 15SA production contract and this contract will be turned in to the RSAF for disposition.

PWS DRAFT 13

RSAF has authorized the Contractor to transition to AMDS 3.0. AMDS 3.0 is being developed to address the ever-changing technological advances in the industry. By utilizing a modern architectural approach, AMDS 3.0 will meet industry trends in supporting virtualized and cloud environments. Additionally, AMDS 3.0 will support a centralized environment in which one server can support all squadrons.

4.6 AMDS Software

There are two updates per contract year for AMDS that include software and technical data changes per paragraph 4.3.1.

Software changes are determined by:

• Feedback from the RSAF directly through in-Kingdom visits or through the Contractor’s in-Kingdom engineers and program technical representatives.

• The Contractor input from testing.

• Technical Data changes.

• USG directed changes.

• Publication Change Requests (PCRs) approved by the RSAF and verified by the

Contractor.

The Contractor will prioritize and select changes to be implemented. The selection will be based on impact, cost, budget and available schedule. This list of changes will be handled per paragraph 4.3.1.

The AMDS software will be English language based (input, display, etc.) and will run using English versions of Windows 10 on the AMDS workstations and a Linux-based OS on the AMDS server. Updates to a newer Windows will have to be analyzed and prioritized with other software changes.

Prior to any operating system change the Contractor shall coordinate with RSAF HQ to ensure system compatibility and IT security classification requirements as defined by the RSAF.

Any enhancement for AMDS 3.0 above and beyond the current capabilities in AMDS 2.13, such as leadership dashboard, analytics or support for portable devices, will need to be funded under a separate contract.

4.7 AMDS Hardware, Network and Environment

4.7.1 RSAF Mandated AMDS Hardware Configuration

The Contractor will support the following AMDS hardware in this configuration. The RSAF will be responsible for initially supplying the hardware to host AMDS 3.0. The hardware needed to support the RSAF network infrastructure, after the initial AMDS 3.0 deployment, will be procured when requirements are defined/approved, and funding is added to the contract. Out of warranty hardware support is covered in section 4.7.2.

PWS DRAFT 14

Figure 1AMDS 3.0 Hardware Configuration

Metrics from paragraph 4.3.3 apply to this configuration. At the request of the RSAF, the Contractor will upgrade the AMDS end of life equipment funded through a separate CLIN to be negotiated at a later date. Refer to paragraph 4.7.2 regarding handling of out of warranty hardware.

The Contractor shall wherever commercially viable, use Commercial Off the Shelf (COTS) equipment, which is supportable in Saudi Arabia. Any AMDS software changes/upgrades required to support this configuration will be funded through a separate CLIN to be negotiated at a later date.

Non-AMDS software upgrades will be funded through a separate CLIN to be negotiated at a later date. Only AMDS software and other Boeing required software will be installed and run on the AMDS server and workstation computers.

4.7.2 Out of Warranty Hardware

The Contractor will provide recommendations for upgrades to out of warranty equipment and software. The Contractor will provide equipment upgrades if requested by the RSAF on a separate CLIN to be negotiated later.

Windows 7 or 10 Windows 7 or 10

AMDS 2.0

Virtual Machine(s) GOLDesp

Note: AMDS 3.0 supports container scalability whereby the application can handle increased loads of work. This can be achieved by reconfiguring the existing architecture of a single machine to increase available resources or by provisioning additional containers within a cluster of distributed machines

DTM Windows 7 or 10 Windows 7 or 10

PWS DRAFT 15

For all hardware that is out of warranty, the RSAF may:

• Reallocate the hardware for other purposes.

• Continue to use the hardware for AMDS.

• Designate some of the hardware as spare equipment to be used for parts in maintaining the other out of warranty hardware still in use.

The Contractor will continue to support AMDS operations on all out of warranty hardware with the following limitations:

1. The Contractor will not be responsible for meeting the operation availability of AMDS as specified in paragraph 4.3.3 for failed equipment

2. The Contractor will not modify AMDS to enable operation on out of warranty hardware.

3. The Contractor will repair out of warranty equipment if provided the replacement parts by the

RSAF.

4. The Contractor is not responsible for the cost of replacement parts for out of warranty equipment.

4.7.3 Network

The RSAF network configuration (see paragraph 4.7.1) will be supported and the metrics as defined in paragraph 4.3.3 will apply.

The RSAF will provide remote access to the AMDS server computer in the RSAF Data Center to the contractor’s base AMDS administrators and in-Kingdom technical representative.

The diagrams below display the high-level design of AMDS 3.0 deployed within the RSAF IT product and pre-production environments.

PWS DRAFT 16

Figure 2 AMDS 3.0 Production Architecture

PWS DRAFT 17

Figure 3 AMDS 3.0 Pre-Production Architecture

PWS DRAFT 18

4.7.4 AMDS Environment

The facilities where the AMDS hardware is located shall conform to the environmental (temperature, humidity) requirements as specified by the original equipment manufacturer’s specifications.

The Contractor will provide the original equipment manufacturer’s specifications at least ninety

(90) days prior to equipment procurement to the USG and RSAF to give RSAF enough time to ensure facility requirements meet proper specifications.

4.7.5 Hardware Upgrades

Through the F-15SA Production contract, the following squadrons will have their computer hardware (servers, workstations) upgraded or installed:

• 6th Squadron at Khamis

• 29th Squadron a Tabuk

• 55th Squadron at Khamis (server only)

• 92th Squadron at Dhahran

• Two additional squadrons, locations to be determined

F-15 C/D squadrons will be upgraded at the request of the RSAF and funded through a separate CLIN to be negotiated at a later date.

• 5th Squadron at Taif

• 34th Squadron at Taif

• 2nd Squadron at Tabuk

• 13th Squadron at Dhahran

All AMDS hardware will conform to DCIT’s requirements at the time of purchase.

4.7.6 Other Hardware

The hardware required to support additional installations will be funded through a separate CLIN to be negotiated at a later date.

The Contractor will procure two (2) maintenance Processor Removable Memory Modules (PRMM), two (2) Small Computer System Interface Data Transfer Module Readers (SDTM-R) and two (2) Data Transfer Modules (DTM) per maintenance squadron debrief section that will be used for maintenance and testing of the AMDS system.

These are to be the property of the RSAF and the RSAF will be responsible for the maintenance, repair and replacement of the contractor procured PRMMs, SDTMR and DTMs. Additional hardware will be funded through a separate CLIN to be negotiated at a later date.

4.8 AMDS Integration with GOLDesp

PWS DRAFT 19

4.8.1 GOLDesp Background

The RSAF uses an Integrated Logistics Management System as part of a modernization program that has the GOLDesp application at its core. AMDS will be integrated with GOLDesp only.

AMDS is designed to identify aircraft faults, determine the need for maintenance, and to recommend the maintenance to be performed in accordance with Country Standard Technical Order procedures. GOLDesp manages both scheduled and unscheduled maintenance through the complete maintenance process.

4.8.2 AMDS/GOLDesp Integration Support

The Contractor AMDS Support Team and GOLDesp development teams will ensure all of the necessary debrief functionality and data collection requirements currently available in AMDS. AMDS integration is highly dependent on GOLDesp functionality and its availability at the RSAF. Currently the integration features supported is shown below:

Web Service (GOLDesp)

Source of Data Status Notes

Aircraft List GOLDesp Functional Future Enhancements:

• Add flight Hours

(recorded in tenths of an hour)

• Add CDU Serial number

• Aircraft configuration, specifically the configuration code used specifically by GOLDesp for weapons stores.

Users GOLDesp Functional User Security GOLDesp Functional

Flight Schedule AMDS Functional Future Enhancements:

• Address web service errors. (AMDS to GOLDesp Transfer and GOLDesp to AMDS transfer)

• Add Sortie Line Number

• Add Mission Type

PWS DRAFT 20

The items listed below are candidates to implement to further for the AMDS/GOLDesp integration:

Web Service

(GOLDesp)

Source of Data

Status Notes

Mission Type GOLDesp The Contractor to implement in

AMDS

GOLDesp web service implemented.

Currently manual updates are required.

Work Unit Code GOLDesp Not implemented

GOLDesp web service needs to be implemented.

Then The Contractor can implement in AMDS.

Currently manual updates are required.

TCTO/EO

Compliance

GOLDesp Not implemented

Determination to be made if this is necessary.

If necessary, then manual updates will be required until implemented.

Severity Symbol

GOLDesp Not implemented

GOLDesp web service needs to be implemented.

Then The Contractor can implement in AMDS.

Currently, manual updates are required.

Deviation Code

GOLDesp Not implemented

GOLDesp web service needs to be implemented.

Then, the Contractor can implement in AMDS

Read Receipt

GOLDesp Not implemented

GOLDesp web service needs to be implemented.

Then, the Contractor can implement in AMDS.

The Contractor’s implementation of the above items is dependent on GOLDesp implementing the web services first. The Contractor will only be able to deliver the above functionality to AMDS if GOLDesp is updated, installed and configured correctly.

The Contractor shall deliver AMDS/GOLDesp integration by 31 May 2021 for all RSAF F-15 aircraft. AMDS 3.0 is dependent on GOLDesp V17.7 in the RSAF production environment along with RSAF provided hardware to support the AMDS 3.0 transition. Currently, GOLDesp is at V13 and there is no production environment to support the AMDS 3.0 transition. Any delays to upgrading the GOLDesp software and providing the production environment could impact the Go Live date of 31 October 2021.

PWS DRAFT 21

Additional integration implementation will require additional funding to be provided on a separate CLIN to be negotiated at a later date.

AMDS/GOLDesp Integration Support in-Kingdom is dependent on GOLDesp installation, configuration, and availability and is outside the Contractor’s control. The Contractor shall make every effort to support and work with the RSAF to make AMDS/GOLDesp integration successful. (Status Report)

4.9 Over and Above

The Contractor shall provide over and above effort defined as labor (to include overtime) and material for unscheduled AMDS equipment maintenance, repair or replenishment activities not to exceed $10,000 annually. This provision applies to all repairs of AMDS equipment not covered under OEM warranty. When the AMDS Administrator determines that a piece of non-warranted AMDS equipment requires a return shipment to the manufacturer the USG will provide the shipping account (FedEx, DHL). The Contractor shall request this shipping account from the USG when applicable. Items shipped will be tracked using a carrier tracking number.

The Contractor shall be responsible for the packing of the equipment and the reinstall of the repaired or replacement equipment from the manufacturer.

Required overtime shall be approved verbally and with a follow-up email by the Contractor technical representative and the USGPCO and Program Manager before actual overtime is worked whenever possible. If not possible, the Contractor technical representative may approve up to ten (10) hours of overtime per month. Justification for the overtime and why prior approval was not sought prior to accomplishing the work shall be contained in the monthly report.

Over and above efforts shall also include unscheduled software and technical data updates and, if required, deployments outside the Kingdom of Saudi Arabia (other than Red/Green Flag).

The Contractor shall determine and perform any over and above effort costing less than $1000 per instance without prior approval of the COR. For all over and above efforts greater than $1000, the Contractor shall obtain prior approval from the USGPCO and Program Manager.

Over and above efforts required for continued AMDS operation shall be accomplished until funds for the CLIN are exhausted and reported in the Monthly Status Report. (Status Report)

4.10 Information Technology (IT) Engineering Support

The Contractor shall provide IT engineering expertise to support the design, production, operations and deployment AMDS and all required IT infrastructure and IT technologies. The IT engineering support shall include development of system specification/interfaces, design, development, qualification, acceptance testing, verification, anomaly resolution, risk management, system analysis, cyber-security and the formation of trade studies and other technical papers. Analysis reports/special studies shall be prepared and submitted following an in-Kingdom trip or when specifically requested by the AMDS Program Manager.

(Technical Report - Study/Services)

4.11 Post-Production Contract Funding

PWS DRAFT 22

AMDS support of F-15SA is supported through the F-15SA production contract (FA8634- 12-C- 2651). This implies that all improvements to AMDS covered under this contract are for the F- 15C/D/S model aircraft only. When the F-15SA production support expires, AMDS support of F-15SA will be provided under this contract.

4.12 Packaging: The Contractor shall package and mark material in accordance with the contract/order Air Force Materiel Command (AFMC) Form 158, Packaging Requirements, and applicable USG regulations. The Contractor shall ensure that classified material is packaged, marked and delivered in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM).

4.13 Holidays and Facility Closings: Contractor/subcontractor personnel shall observe all Kingdom of Saudi Arabia holidays and facility closings as authorized or required by Kingdom of Saudi Arabia Government personnel. Contractor/subcontractor personnel shall only be permitted access to Kingdom of Saudi Arabia Government facilities when Kingdom of Saudi Arabia Government personnel are present.

4.14 Travel: Travel requests for contractor/subcontractor personnel shall be submitted for approval in advance to the Contracting Officer prior to costs being incurred and a minimum of

(60) business days in advance of departure. Receipts must be presented with the invoice for reimbursement of actual travel costs. The reimbursement of all travel costs and per diem are to be IAW the Department of Defense Joint Travel Regulation (JTR).

Travel requests for Contractor personnel beyond the travel authorized in this contract, shall be submitted for approval to the USG PCO and Program Manager prior to costs being incurred and a minimum of five (5) business days in advance of departure. Travel to RSAF or USG facilities or other Contractor facilities may be required and will be specified at the appropriate time. For each twelve (12) month period, AMDS Technical Representative travel OCONUS is approved for up to twelve (12) routine in-Kingdom trips based on up to three (3) trips per quarter for each four (4) quarter period. Travel is also approved for the technical representative for up to ten (10) out of cycle trips in-Kingdom in each twelve (12) month period are approved. A schedule of planned trips will be provided to the RSAF Directorate of Aircraft Maintenance DoAM at RSAF HQ in advance.

For critical AMDS situations (those that affect availability or functionality of AMDS installation), unplanned trips are authorized and notification of unplanned trips will be provided as soon as possible to the RSAF Directorate of Aircraft Maintenance DoAM at RSAF HQ.

Additionally, for each twelve (12) month period, one (1) Contractor Program Manager from St.

Louis, MO, prior approval is required for up to two (2) trips in-Kingdom for up to fourteen (14) days each to conduct kick-off, employee administration, and customer relations duties.

The Contractor is also authorized travel for the Information Technology (IT) Engineer, from St Louis, MO, up to two (2) trips in-Kingdom for up to fourteen (14) days each to attend meetings, conduct site surveys, and to perform research in support of efforts detailed in paragraph 4.10 for each twelve 12-month period. Further trips are approved based on the following criteria;

PWS DRAFT 23

a. One (1) round trip from St. Louis, MO to Las Vegas, NV to support AMDS Red/Green Flag operations each year the RSAF participates.

b. Up to three (3) round trips per year for one (1) person from St. Louis, MO to Warner Robins, GA for up to five (5) days in order to support AMDS program reviews.

c. Travel by Contractor personnel shall be conducted in accordance with FAR 31.205-46, Travel costs

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Commander or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2 Security Requirements

5.2.1 Security Regulations: The Contractor shall ensure personnel, information, system, property, facility and, if applicable, international security requirements are met. The Contractor shall ensure contractor/subcontractor personnel who perform work on a Kingdom of Saudi Arabia USG facility comply with the security requirements of the facility.

5.2.2 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall comply with DoDD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.)

Government interests. The Contractor shall ensure Contractor personnel who perform work on a Kingdom of Saudi Arabia Government facility comply with the OPSEC procedures of the facility.

5.2.3 Communications Security (COMSEC): The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified information and/or Controlled Unclassified Information (CUI) in accordance with DoD 5220.22- M. Applicable equipment shall be safeguarded, maintained and operated in accordance with DoD 5220.22-M.

5.2.4 Security Clearance: It is not expected contractor/subcontractor personnel will require security clearances for proper accomplishment of contract/order requirements.

Contractor/subcontractor personnel shall not be authorized access to classified information and/or Controlled Unclassified Information (CUI) and classified items or be permitted to work on classified projects and/or programs without an appropriate security clearance and a need-to-know.

5.2.5 Access to Government System(s): Access to USG system(s) will not be required to perform tasks under the contract/order.

PWS DRAFT 24

5.2.6 Access to Government Facility or Military Installation: The Contractor shall ensure contractor/subcontractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation.

5.3 Environmental Management System (EMS): These services shall not be performed at a USG facility; therefore, the EMS requirement does not apply. Work shall be performed on RSAF bases or in RSAF AMDS facilities except when supporting Red/Green Flag or other exceptional deployments. The prime Contractor shall ensure any sub-Contractors comply with EMS requirements. Contractor personnel who perform work at Nellis AFB, NV, or at another U.S.

Government facility shall comply with the EMS requirements established by those installations.

5.4 Agency Affirmative Procurement Programs (formerly Green Procurement Program (GPP)):

This acquisition does not require the purchase of Environmental Protection Agency (EPA)-designated products or United States Department of Agriculture (USDA)-designated products;

therefore, the requirement does not apply.

5.5 Safety Requirements

5.5.1 Contractor Compliance: The Contractor shall comply with USG Safety and Health regulations including, Public Law 91-596 as amended by Public Law 101-552 [Occupational Safety and Health Act of 1970 (OSHA)] and DoDD 4715.1E, Environment, Safety, and Occupational Health (ESOH).