Appendix_A_PWS_Gulfstream_Exec_Aircraft_ESCFollowOn_09MAR20.docx

PERFORMANCE WORK STATEMENT

FOR

GULFSTREAM EXECUTIVE AIRCRAFT ENGINEERING SERVICES CONTRACT

PREPARATION DATE: 20 December 2019

VERSION 1

SOLICITATION NUMBER: FA8134-20-R-0001

CONTRACT NUMBER: TBD

PREPARING ORGANIZATION: AFLCMC/WVV

3001 Staff Drive Suite 1AE1-103C Tinker AFB, OK 73145-3018

TABLE OF CONTENTS

FA8134-20-R-0001, Attachment 1, Basic Issue

FOR OFFICIAL USE ONLY

AFFECTED

DATE

Acronyms

Explanation of Terms Aircraft service change (ASC) – An ASC is a Federal Aviation Administration (FAA) approved method used to modify and/or amend aircraft type design of a standard production aircraft (commonly referred to as a “green” aircraft). The ASC kit/data package consists of parts, materials and instructions required for a one-time alteration to the aircraft. Most ASCs are optional and are offered as a means to enhance aircraft capabilities to meet individual operator requirements. The only time an ASC is not optional is when it is “forced” by a Customer Bulletin (CB), an Alert Customer Bulletin (ACB), or an FAA Airworthiness Directive (AD). ASCs can be priced or no charge. The impact of an ASC on spares, support equipment, training, special publications, etc., is not included in the price of an ASC. Therefore, the incorporation of a priced or no charge ASC could require additional funds for changes to these support areas.

Airframe – The structural components of an airplane, including the framework and skin of such parts as the fuselage, empennage, wings, and engine mounts (does not include landing gear or engines).

Airworthiness Directive (AD) – Mandatory, regulatory bulletin issued by the FAA that requires compliance in order to maintain the aircraft airworthiness certificate.

Alert Customer Bulletin (ACB) – An ACB is a safety related Customer Bulletin (see Customer Bulletin below) that is considered urgent and requires a one–time inspection (may require incorporation of an ASC to address the condition). Compliance times are usually less than 25 flight hours or 50 landings.

Customer Bulletin (CB) – A document requiring a one–time inspection for a specific condition within an appropriate compliance period (may require incorporation of an ASC to address the condition). Compliance times are usually greater than 25 flight hours or 50 landings. Calendar times can also be used.

Data – Management, scientific, engineering and logistics information, reports and documentation.

Maintenance & Operations Letter (MOL) – This document communicates information that will enhance operations or safety, improve a maintenance practice, provide information regarding service events, or provide advance information on pending changes to the Aircraft Maintenance Manual or Illustrated Parts Catalog. They also may be used to notify operators when a Notice of Proposed Rule Making (NPRM) will be issued by the FAA or as a cover document to a forwarded vendor service bulletin. An operator’s response to an MOL is not recorded for tracking purposes and is not required for continued airworthiness. MOLs are distributed via facsimile and electronic mail and are available on the Gulfstream Internet site.

Modification – A change in the physical or functional configuration or in the functional characteristics of a system or equipment (form, fit, function, interface).

Service Bulletin (SB) – Manufacturer’s document which requires inspection for a specific condition or to modify and/or amend the type design of an aircraft or component. Gulfstream does not issue Service Bulletins, however some Gulfstream suppliers utilize Service Bulletins for their components.

Software Assurance – The justified confidence that the software functions as intended and is free of exploitable vulnerabilities, either intentionally or unintentionally designed or inserted as part of the system at any time during the lifecycle. The main objective of software assurance is to ensure that the processes, procedures, and products used to produce and sustain the software conform to all requirements and standards specified to govern those processes, procedures, and products. A secondary objective of Software assurance is to insure that the software-intensive systems we produce are more secure.

1.0 Scope

This performance work statement (PWS) outlines the contractor actions, responsibilities, and work efforts necessary to comply with Government requirements for engineering services in support of Gulfstream Executive Aircraft (GEA) under an Indefinite Delivery/Indefinite Quantity (IDIQ) contract managed by the United States Air Force (USAF). Engineering and data services are divided into two categories with some items being accomplished on a recurring basis and others on a non-recurring basis as directed by the Government’s Procurement Contracting Officer (PCO). This is a services contract with embedded supplies.

This Engineering Services Contract (ESC) PWS addresses the GEA fleet as identified in Addendum 1. Gulfstream Aerospace Corporation (GAC) aircraft owned by the USAF, United States Army (USA) United States Navy (USN), United States Marine Corps (USMC), United States Coast Guard (USCG), and other Government Agencies may use this contract, at the discretion of the PCO.

The contractor shall accomplish efforts under this contract to Federal Aviation Administration (FAA) Type Certification (TC) standards and applicable Code of Federal Regulation Title 14, Federal Aviation Regulations, and by the use of FAA approved designs and parts. The contractor shall maintain and keep current its Manufacturer’s Maintenance Facility and FAA Air Agency Repair Station Certificate.

1.1 Mission Area

World events will at times require senior United States Government officials (SECDEF, SECSTATE, CJCS, MEMBERS of CONGRESS and WHITE HOUSE STAFF) to immediately deploy by air transportation on matters of national security or national interest. Mission requirements could dictate operation into civil as well as military airfields both during peacetime and wartime. High levels of physical as well as communications security are required to protect national interests. The USAF and Department of Defense (DoD) entities require a fleet of intercontinental range jet aircraft to accomplish this, as well as other required missions.

2.0 Applicable Documents

The documents referenced in this PWS are only applicable to the extent specified. Documents referenced within the documents cited herein shall not be applicable to this PWS solely because of such reference. They must be referenced directly in this PWS in order to apply. The version/revision of the document current as of the award date shall apply.

a) Addendum 1: List of Aircraft, Tail Numbers, Serial Numbers and Main Operating Bases (MOBs)

b) Addendum 2: Vendor List, List of Parts to be Monitored for Service Literature

c) Addendum 3: Commercial and Unique Manuals

d) Addendum 4: JBA Services and Facilities for FSRs

e) Any other applicable document specific to each Task Order

3.0 Recurring Engineering and Data Services

The contractor shall provide the engineering and data support on a recurring basis for all GEA for the duration of the contract as detailed in the subsequent paragraphs. Addendum 1 contains a list of the GEA aircraft including identifying the Mission Design Series (MDS) and owning service, as well as other specific identifying information. Please note, the inventory of aircraft and locations are subject to change during the duration of the contract. The PCO will inform the contractor of fleet changes, as necessary, and accomplish any correlated negotiations or contract changes. The contractor shall maintain the fleet list and supply an update to the Government Program Office when fleet structure changes occur. (CDRL A001)

3.1 Point of Contact

The contractor shall provide a point of contact (POC) who will be available to the Government Program Office to provide support on a twenty-four (24) hours per day, seven (7) days per week basis.

3.2 Service Literature

Contractor shall perform Service Literature (SL) reviews accurately and on time. SL includes vendor Service Bulletins (SBs), Service Information Letters, Aircraft Service Changes (ASCs), Customer Bulletins (CBs), Alert Customer Bulletins (ACBs), FAA Notices of Proposed Rule Making (NPRMs), Airworthiness Directives (ADs), and other similar publications or notices by Original Equipment Manufacturers (OEMs)/Vendors and other Airworthiness authorities, such as European Aviation Safety Agency. The contractor shall review, evaluate, determine specific applicability to the individual GEA, and provide recommendations for new and revised SL pertinent to the GEA and Government owned spares, including parts, firmware and software. The Vendor and Parts Lists, Addendum 2, are the most recent list available from the preceding ESC at the time of award of this contract.

Note: When an AD requires verification and/or return of a task card, even if the aircraft does not contain the parts in question, an SL Review will be submitted identifying the actions required.

3.2.1 Vendor List and Parts List

The Vendor and Parts List found in Addendum 2 is a living document and as such, subject to change. The contractor shall update these lists annually based on configuration changes made to the GEA and review the changes with the Government Program office. The contractor will be notified by the Government Program Office of any configuration changes performed by a third party. Please note, not all vendor items are identified on the listing. Items which are likely subject to SL are added to the listing. (CDRL A001)

3.2.2 Service Literature Classification

There are three classifications for mandatory SL and one for non-mandatory SL. The due dates for the SL reviews are based upon the amount of time the Government Program Office has to direct action. All GAC CBs and FAA ADs require owner/operator compliance and are mandatory SL. The mandatory SL reviews must be accomplished and delivered to the Government Program Office within three (3) business days for Immediate, five (5) business days for Urgent and ten (10) business days for Routine. The Non-mandatory SL review must be accomplished and delivered within thirty (30) calendar days. Mandatory immediate SL reviews can be delivered via e-mail notification and/or phone call notification as preliminary reviews, if the FAA has issued an AD that would require action in less than one week or prior to further flight. Please see the below Reference Table:

3.2.3 Service Literature Review Reports

The contractor’s SL review reports shall include impacts to the aircraft and Government owned spares. The following information shall be included: (CDRL A002)

a. Individual aircraft impacts, such as, identifying part numbers or software that will have to be updated

b. Spares affected

c. Recommendations

d. Kit requirements/recommendations

e. Current kit prices and lead times, if included in the reviewed SL. If pricing and lead time are immediately available in the vendor’s literature, any pricing provided as a part of the review will be non-binding to the contractor

f. Labor hours

g. Copies of SL, when available[footnoteRef:1] or provide information on how Government Personnel can obtain the publication (web address or vendor POC information) [1: Dependent on vendor data rights/control.]

h. Mandatory/Optional/Informational/Recommended

i. Effectivity

j. Recurring/One Time Inspection

k. Field/Depot Determination

l. Drawing Changes (Y/N)

m. Technical Manuals Affected – If possible, the recommended changes

n. Impact to the Program Protection Plan to include Critical Component/Critical Program Information (Y/N)

o. Impact to Cybersecurity (e.g. Cybersecurity Strategy, Platform IT [PIT] documentation, Mission Systems) (Y/N)

p. Impact to Supply Chain (e.g. counterfeit parts, alternative vendor) (Y/N)

q. Impact to Software Assurance (e.g. where and how software is obtained, scanning, patching) (Y/N)

3.3 Unique Drawings and Documents File

The contractor shall maintain a historical file of applicable engineering data generated by the contractor.

The contractor shall maintain a file that contains Government unique documentation applicable to the GEA programs generated by a vendor or another contractor at the direction of the Government. The contractor shall maintain a file content list summarizing unique data generated by other contractors or vendors. The content list shall be delivered to the Government in accordance with (IAW) CDRL A001.

3.4 Configuration Status Accounting Reports

The contractor shall accurately maintain three Configuration Status Accounting Reports (CSARs) for the GEA aircraft by branch and MDS at each location:

1) Software CSAR

2) Airframe CSAR

3) Engine CSAR The CSARs are not to be used as an augmentation or substitution for established FAA or other USAF aircraft maintenance records.

New aircraft that require CSARs will have an initial non-recurring task accomplished for the first edition of their CSAR and then be subject to annual fee to be negotiated and placed on contract.

The contractor shall maintain the CSARs to reflect the current aircraft configuration. Each item in the CSAR(s) shall include a reference to the applicable Air Transport Association (ATA) two-digit number. These reports shall include the following: CBs, ACBs, ASCs, Time-Compliance Technical Orders (TCTOs), Supplemental Type Certificates (STCs), ADs, miscellaneous modifications, and work change requests. In addition, the Software CSAR shall include a list of parts which have modification levels and/or software revision levels. This list shall include information regarding all software revisions or modifications available to each particular part, as well as compliance information.

The CSARs described above shall include cross references to related, concurrent, or superseded bulletins and shall be delivered in Microsoft Excel or Access format. The Government will provide copies of Government source data (e.g. TCTOs with data codes, drawings, etc.) as it is generated for review by the contractor and incorporated into the CSARs, as applicable. Government supplied source data is not to include any third party proprietary rights restrictions. If proprietary restrictions are present without relief, the contractor shall immediately notify the PCO and promptly return such data to the Government. (CDRL A003) CSAR reporting shall include, at a minimum, the following data:

Each report shall, at a minimum consist of the following: Cover page, data notes, acronyms and abbreviations, change status sheet, and detailed report.

3.5 Computerized Maintenance Program

The contractor shall provide Computerized Maintenance Program (CMP) read-only access to the Government to allow for review, tracking, report generation, and all other associated tasks required for maintaining and managing Government aircraft. The contractor shall also make inputs and changes required for maintaining and managing the accuracy of the data in CMP as requested by the Government.

3.5.1 CMP Reports

The contractor shall provide the Government with access to CMP reports for each GEA.

3.5.2 USAF TCTO Codes

Upon receipt of a TCTO containing a data code from the Government, the contractor shall accomplish the following:

1) Develop a unique CMP code for each TCTO.

2) Enter the TCTO into CMP using the unique CMP code.

3) Upload/attach the entire TCTO package to this unique code in CMP.

4) Identify related CB, ASC or AD numbers in the notes section of the CMP card for ease of cross-reference.

3.5.3 USN CMP Analyst Support (Applicable to USN/USMC GEA Only) A full-time CMP Analyst shall be assigned to perform dedicated CMP support for the USN and USMC GEA aircraft. This paragraph only applies to the USN and USMC GEA. The dedicated CMP Analyst assigned to this effort shall support the USN Program Office. All CDRL items listed below shall be maintained on the website for the USN and USMC to see. The CMP Analyst shall be responsible for the following:

· Performing constant surveillance of CMP data input by personnel at the MOB and depot sites in CMP/CMP.net for the applicable aircraft.

· Reviewing/approving CMP data to ensure all documentation/attachments incorporated into CMP/CMP.net are accurate, current and complete.

· Ensuring the current CMP information supplied by maintenance sites and/or GAC are accurate concerning the configuration for each applicable GEA identified in CMP/CMP.net.

· Notifying the USN Program Office and the GAC ESC Program Manager of any CMP data issues that arise. CMP data that is reported incorrectly or incomplete by sites not managed by GAC shall be reported to the USN Program Office for resolution.

· Maintain constant vigilance over items that are maintained in CMP/CMP.net and inform the USN Program Office of any items that are close to being over flown.

· Ensure all engine and Auxiliary Power Unit (APU) changes are entered into CMP correctly after each occurrence. This shall include life-limited components associated with the engines and APUs.

· Create, upon request, custom codes, special inspections etc., as required by the USN Program Office.

· Conduct annual CMP database audits for each applicable aircraft and provide the results to the USN Program Office. If any discrepancies are discovered, notification to the USN Program Office is required. Findings of past due or due within one workweek maintenance requirements shall be reported to the USN Program Office within one workday. All other findings shall be reported in the summary report for the audit and in accordance with the applicable paragraph above. (CDRL A004)

· Review the aircraft logbooks (Airframe/Engine), when directed by the USN Program Office, to ensure all required CMP documentation has been incorporated.

· Provide CMP/CMP.net training to USN users when requested by the USN Program Office.

3.6 Technical Inquiries

The contractor shall respond to oral or written inquiries issued by the Government Program Office concerning aircraft and engine basic design information, maintenance and repair requirements, flight test data, performance, reliability, or other areas of concern. If an effort requires more than forty (40) man-hours, an Engineering Assignment (EA) shall be proposed with an estimated cost and schedule required for accomplishment. The contractor shall track all general inquires and post a monthly status report on the ESC website. Inquiries generated at the MOBs or depots are NOT to be acted upon unless authorized by the PCO. Inquiries generated by all activities outside the Government Program Office will be forwarded to the applicable service specific Program Office for determination of applicability and approval to work. (CDRL A005)

3.7 Contract Funds Status Report

The contractor shall maintain the Contract Funds Status Report (CFSR) to ensure total program funds visibility. The contractor shall maintain the CFSR, with the contractor’s obligation of funds, funds available and other required data current by the 10th calendar day of each month. (CDRL A006)

The contractor shall also provide written notice to the PCO when funding for any Contract Line Item Number (CLIN), other than Firm-Fixed Price (FFP), has reached seventy-five percent (75%) of the available amount per CLIN. The contractor shall provide written notice to the PCO when the over and above (O&A) CLIN’s have reached seventy-five percent (75%) of the approved funding. The notifications shall include the contractor’s assessment of whether or not the effort can be completed with the remaining funds.

3.8 Contract Monthly Status Report

The contractor shall deliver a monthly status report summarizing the recurring and non- recurring activities accomplished during the month. A section of the report shall cover all open EAs. The EA section of the report shall include EA number, title, status (open or complete), start date, due date, estimated completion date, and percentage of work/labor completed. (CDRL A007)

3.9 GEA Website

The contractor shall maintain a secured website for distribution of data only to the Government. The website shall use multifactor authentication to validate user access. When a data item is added or updated on the GEA website, the contractor shall notify, via e-mail, all recipients as specified by the Government Program Office. Data items include, but are not limited to, the following:

· CDRL Deliverables

· Tech Manual(s)

· Contract Data Status Reports

· EA Information

· List of Program POCs, both Government and contractor, including Government contacts for urgent SL distribution

· ESC scheduled telecoms, meetings or events Website postings shall be provided in an electronic format as directed by the appropriate CDRL instructions.

3.10 Field Service Representatives

The contractor shall provide FSRs at JBA to support GEA aircraft owned and operated by the USAF under the 89th Air Base Wing (ABW) at JBA. All of the FSR duties and responsibilities described in this paragraph and all of its subparagraphs are only applicable to USAF owned GEA operated at JBA. For the remainder of this paragraph and its subparagraph, the aircraft will be identified as the USAF GEA at JBA.

3.10.1 FSR Coverage

The FSR coverage shall be sixteen (16) hours per day (0600 – 2200), five (5) days per week. For holiday coverage and/or when the designated FSR is not readily available due to requirements outside normal duty hours, training, sick or vacation leave, the contractor shall ensure that a backup FSR is available telephonically. Upon mutual agreement between the contractor and local Contracting Officer Representative (COR), the FSR’s on-site hours of coverage may be adjusted to meet customer mission and support needs. FSRs shall be available for telephonic support during all off hours. When determined by the Government Program Office to be necessary, an FSR shall be available for one-hour recall.

3.10.2 FSR Experience and Duties

The FSRs shall be experienced in all GEA and systems supported under this contract throughout its Period of Performance (PoP). This experience does not include systems supported by third parties. However, FSRs shall provide coordinated technical support, as necessary where 3rd Party Contractors’ installations or modifications integrate with OEM Production/Completion Outfitting.

Each FSR shall have a SECRET security clearance. The FSRs shall provide technical guidance in the resolution of field problems related to installed equipment/systems for maintenance and servicing of the USAF GEA at JBA. FSR shall provide “over the shoulder” instruction, informal on-the-job training and technical support for maintenance or servicing. As required, FSRs shall participate in functional check flights, operational flights, and travel worldwide to assist in troubleshooting aircraft problems. FSRs will be authorized as Mission Essential Ground Personnel. The FSRs shall submit a monthly Field Service Report with an itemized list of significant issues/problems and equipment availability. (CDRL A005) FSRs will be afforded access, on a noninterference basis, to the GEA applicable Contractor Operated and Maintained Base Supply (COMBS), parts inventory, parts repair/overhaul history, and third party vendors for technical inquiries. The contractor shall provide and maintain, at no additional charge to the Government, all applicable GAC commercial publications for use by FSRs in support of applicable aircraft owned and operated by the USAF at JBA. The contractor shall maintain currently available data, not of GAC (OEM) origin, to include applicable 3rd party or vendor publications, drawings or other data needed to maintain USAF GEA at JBA. Initial procurement and follow-on subscription service for all non-GAC publications shall be funded on an O&A basis.

3.10.3 Primary Point of Contact

The contractor shall provide an on-site lead Primary Point of Contact (PPOC) for USAF GEA at JBA for technical support issues to the 89th. Contractor’s PPOC services includes significant back-office effort providing oversight for the contractor’s on-site FSR team and activities, coordination of technical inquiry responses, support liaison with vendors, engineering, 3rd parties, depot facilities, attendance at short-notice briefing meetings with 89th leadership and support groups. Management interface with 89th ABW Operations & Maintenance management on issues, support plans and program topics. PPOC services shall be provided separately and are additional to the provision of daily FSR technical support at Flight Line level.

3.10.4 Provide Vendor POCs

The contractor shall accomplish necessary communication with vendors, such as Rolls Royce, Honeywell, Rockwell-Collins, DPI, EMS, etc., to resolve aircraft issues. Also, act as escorts when vendors are at JBA to support maintenance activities on USAF GEA at JBA or site visits at the Government’s request. If escort duties are outside the normal work schedule, an O&A shall be requested.

3.10.5 FSR Attendance

FSR representation shall be provided in the following meetings: Daily Morning Flight Schedule and Plan of the Day, Daily Afternoon Aircraft Status/Maintenance Planning, Aircraft return “Debrief”, and Periodic 89th/99th Operations & Maintenance Liaison Effectiveness Team.

3.10.6 Additional FSR Duties

Additional FSR duties include, but are not limited to, the following:

· Provide sparing recommendation inputs during fleet additions and/or modification programs tailored to the 89th use of the appropriate Mission Essential List (MEL).

· Provide initial limited research and recommendations relative to newly-discovered obsolescence issues found to be impacting the 89th Fleet.

· Determine, coordinate and assist the 89th Maintenance Wing (MXW) with maintenance- planning activities and recommendations to implement procedures and methodologies that minimize downtime and man-hour impact.

· Provide OEM interpretation to 89th MXW and assist in their determination of their potential capacity/capability to accomplish new inspection/repair/modification tasks.

· Provide suggestions to 89th MXW management on ways to reduce the potential impact to dispatch ability or reliability.

· Coordinate with the COMBS groups to facilitate research, where needed, to support local 89th MXW needs.

· Monitor and coordinate 89th MXW suggestions for publication change revision requests to OEM manuals in support of flight line and Isochronal Inspection activities.

· Provide "over the shoulder" technical support to achieve rapid resolution for 89th declared Partial Mission Capable (PMC) or Not Mission Capable (NMC) situations noncompliant with the appropriate MEL. Assist with identification of items outside the scope of the contract.

· Provide interpretation of commercial data against the requirements within CMP/CAMS/TCTO processes.

3.10.7 Over and Above Requests

When requested by the Government Program Office, FSRs shall prepare an O&A request or proposal for coordination through the designated 89th COR to facilitate the contractor’s engineering dispositions, drawings, extensions, ferry permits, additional on- site support, etc. that are not otherwise covered in the GAC commercial or unique repair manuals. Payment for engineering disposition services will be IAW the contractor’s commercial practices as described in the then current annual rate letter. FSRs shall maintain a file of engineering dispositions processed by them at JBA to include disposition instructions and drawings, which may be provided. The contractor shall maintain a tracking proposal log for FSR and O&A activities, if applicable.

3.10.8 FSR Travel

FSRs shall be prepared to dispatch worldwide, as required, within twenty-four (24) hours of notification to support Aircraft on Ground (AOG) situations. FSRs may, as reasonably determined, and IAW the contractor’s corporate guidelines, decline final destinations hostile to US interests, personnel or where international conflicts/concerns exist. FSRs shall possess current passports. FSR travel expenses will be reimbursed IAW contract requirements.

3.10.9 Facilities at JBA for FSRs

Addendum 4 outlines the facilities, services, access, and privileges to be provided to the FSRs.

3.11 Technical/Maintenance Manuals

3.11.1 GAC Commercial Manual Services

The contractor shall provide subscription services for GAC commercial aircraft manuals applicable to the aircraft identified in Addendum 1 and make distribution IAW CDRL A012 and Addendum 3.

Pursuant to the commercial publication access terms and conditions, the contractor shall provide managed and controlled access to GAC’s proprietary commercial manuals applicable to these platforms to the owner/operator via the company website. Access to the company website must be approved by the Government Program Office.

3.11.2 Commercial Data

The publications, data, drawings, or other information described, but not limited to, the Production Specification and/or Manuals are proprietary to the OEM. The contractor shall have access to OEM proprietary information.

3.11.3 Publication Change Request Report

The contractor shall provide and maintain a quarterly Publication Change Request (PCR) Report with the applicable technical manual services in work and completed. The report shall include, as a minimum, technical manual type (Unique, Government), PCR control number, purpose, name of initiator, status (in work, complete, pending Government approval, disapproved, etc.), age (in days), initiation date, and estimated completion date, if applicable. (CDRL A008)

3.11.4 Master Copy File

The contractor shall maintain a current master copy of all unique manuals listed in Addendum 3 for publication purposes, revisions or supplements. The contractor shall deliver the current master copy file to the Government when requested by the PCO. The contractor shall transfer all technical library contents to subsequent contractor at the conclusion of this contract.

3.12 Reserved

3.13 Meeting(s) and Minutes

The contractor shall prepare meeting agendas with the assistance of the appropriate Government personnel for meetings which require participation by multiple services and or vendors, are significant in nature, and the Government Program Office has notified the contractor that minutes will be required. If possible, all required agenda and presentation materials shall be delivered electronically to the Government Program Office no later than (NLT) ten (10) business days prior to meeting for proper review and approval. A subsequent Government Program Office approved finalized agenda shall then be submitted, when possible, at least five (5) business days prior to the scheduled meeting. (CDRL A009)

The contractor shall ensure that accurate meeting minutes are taken. A draft copy of the meeting minutes shall be submitted to the Government Program Office within ten (10) business days of the meeting date for Government Program Office approval. A subsequent finalized copy shall then be submitted NLT five (5) business days after receipt of Government Program Office approval. (CDRL A010)

Meeting agendas and minutes produced in support of non-recurring engineering (Section 3.0) shall follow the requirements found in CDRLs A009 and A010, but be delivered under CDRL A011 with all of the other non-recurring engineering deliverables.

3.14 Performance Review Status Meeting

The contractor shall conduct a review of the management system at planned intervals (at least quarterly) to ensure continuing suitability, adequacy and effectiveness. The contractor shall be responsible for scheduling and hosting this telecon. The review shall include, but is not limited to, assessing the following:

· Recurring Engineering Activities, such as:

· Service Information

· Aircraft Airworthiness Management

· Vendor/Parts List Revisions

· Unique Drawings and Document Status

· Configuration Status Accounting Reports

· TCTO Codes/Compliance

· FSR Activity

· Non-Recurring Engineering Activities, such as:

· Proposal Status

· Contract Funds Status

· EA Status

· Aircraft/System Modification Status

· Publication Change Activity When requested by the Government Program Office, the contractor shall provide support and participation at the annual Contractor Logistics Support Program Management Review in the event topics supported by this PWS are discussed.

4.0 Non-Recurring Engineering and Data Services

The contractor shall perform the engineering and data services on a non-recurring basis for all GEA as detailed in the subsequent paragraphs. The contractor shall use its own standard practices to ensure new drawings and/or technical data prepared under this contract are of production quality, unless otherwise specified by the PCO. The contractor shall update, revise and maintain engineering data/drawings developed under this contract IAW standard commercial practices. The contractor shall afford data rights to the Government IAW Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7015 and 252.227-7037.

4.1 Proposals for Non-Recurring Efforts

The contractor shall provide an acknowledgement of receipt to the PCO within two (2) business days of receiving the official request for the proposal or rough order of magnitude (ROM). The contractor shall provide the requested proposal or ROM within thirty (30) calendar days of receipt of request from the PCO. If additional time is needed to prepare a response, the contractor shall request an extension from the PCO. If an extension is granted, the response will not be considered late as long as it is submitted by the new date. An official request for a proposal or ROM is ONLY a request sent directly by the PCO and is the only request of this nature that will be acted upon. (A005)

Proposals with FFP estimates are required for EAs to be placed on contract. Proposals and ROMs shall include an estimated price broken out with enough detail to allow the Government to evaluate the proposal and an estimated schedule for the effort. The contractor shall maintain a list of all proposals/ROMs by Service and MDS as well as joint efforts to include disposition (i.e. accepted, declined, etc.) and track status of the effort. The proposal/ROM log shall include a descriptive name, MDS, Service, Official Request Date, estimated delivery date, actual proposal delivery date, validity date and final status date as well as a note field for final status. The “Note” field shall identify either Government declined, cross-reference EA number, or contract modification number.

Direct charge for proposal preparation is not authorized on this contract.

4.2 Engineering Assessments

The contractor shall accomplish the engineering, data management, and technical order development services required by EAs. The contractor shall be notified of these requirements by the PCO in writing, electronic mail, or telephone. EAs will be authorized and funded by issuance of a task order by the PCO. The assignment(s) will be defined on an AFLCMC/WVV H-200 Form and will be an attachment to the task order. The formal work authorizations against the contract will identify or define the problem, task objectives, and required completion dates necessary.

The contractor shall either accept the task as identified by the EA, or submit an alternate approach to the PCO within five (5) working days from receipt of the EA. The contractor shall notify the PCO if the assigned task cannot be accomplished within the allotted time and man-hours, and provide an estimate of time and man-hours that are anticipated. When directed by the PCO, a change of allotted time and man-hours or priorities shall be accomplished on the individual project. During the performance of tasks assigned pursuant to the schedule, the contractor shall not be entitled to payment for overtime premiums except to the extent that the overtime request(s) has been approved by the PCO. The contractor shall submit engineering reports/data as specified in each EA.

The labor rate utilized for each EA shall be in accordance with Appendix B. All material purchases incidental to the EA shall be purchased IAW GAC’s list price for new parts.

The contractor shall provide an EA status report on a monthly basis until completion of task. The contractor shall deliver the report NLT fifteen (15) calendar days following the end of each month. (CDRL A011)

4.3 Unique Engineering Data

The contractor shall provide applicable engineering data and drawings developed under this contract to describe all GEA peculiar items. The contractor shall update, revise, and maintain GEA engineering data/drawings developed under this contract in accordance with standard commercial practices. All data developed under this contract may be available to the Government with data rights to be used by the Government or the Government’s contractors in support of Government owned and/or operated aircraft. However, any data found to contain proprietary information which if distributed outside of GAC could cause competitive business impact, will not be considered. (CDRL A011)

4.4 Commercial Engineering Data

On a case by case basis, provide copies of the OEM’s design data and drawings, which are normally sold commercially, for use by the customer or by the customer’s designated agent for accomplishing specific repair of an aircraft.

4.5 Systems Engineering

The contractor shall incorporate systems engineering (SE) to include system security engineering practices into all applicable efforts. Such practices include, but are not limited to, technical reviews, identifying and defining requirements, and ensuring requirements are met as the effort progresses from start to finish. When specified, the contractor shall generate, maintain, and provide a Requirements Breakdown Matrix for engineering efforts approved/funded by this contract. For more information on SE practices, reference the FAA System Engineering Manual.

4.6 Engineering/Technical Support

The contractor shall provide engineering/technical or FAA Organization Designation Authorization or Designated Engineering Representative support, as appropriate, for accomplishment of repairs, modifications, or investigations, upon request. In some cases, it may be required to dispatch personnel to a designated location for a period of time. (CDRL A011)

4.7 Safety Risk Assessment

The contractor shall respond to oral and/or written requests issued by the Government concerning risk assessment assistance. Contractor assistance will be requested, as needed, to ensure accurate risk assessments are completed to support aircraft program maintenance, repair, modification and sustainment issues. Contractor assistance will vary, but may include providing safety assessment expert/facilitator, subject matter expert(s), relevant data, and other resources needed to identify, analyze and mitigate hazards. All requests shall be answered in a timely manner where response time will be specifically identified by the Government when the request is made. (CDRL A011)

4.8 Travel

The contractor shall attend technical order reviews, PMRs, conferences, technical interchange meetings (TIMs), and other meetings or events when authorized by the PCO. The PCO authorization will specify the required skills, number of personnel and duration of the conference or event. The PCO authorization will include contractor preparation, travel costs and travel days to and from the conference or event. Contract personnel who travel in support of this contract are required to submit a Trip Report summarizing what was accomplished, significant findings and open issues which require additional investigation, if applicable. (CDRL A011)

4.9 Aircraft Maintenance

The contractor shall perform incidental aircraft maintenance, repairs, inspections, AOG support, etc., when requested by the PCO. No Flight/Mission Critical Post maintenance failures or findings.

4.9.1 Maintenance Records

The contractor shall record all maintenance or repairs performed under the authority of this contract in CMP and annotate applicable aircraft records (e.g. AFTO Form 95, AFTO Form 781, log books, etc.), as appropriate. The Government will be responsible for any special training, support or certification required for the contractor to fill out, process or approve Government forms (AFTO Form 95, AFTO Form 781, etc.).

4.10 Unique Manuals

The contractor shall maintain all Government aircraft unique manuals and technical orders listed in Addendum 3. The contractor shall provide paper or electronic copies as requested by the PCO. The contractor shall also develop new Government aircraft unique manuals upon request by the Government. (A012) The contractor shall revise Government aircraft unique manuals; and submit to the Government for review and approval upon completion. Upon the Government’s approval, the contractor shall incorporate and publish changes/revisions. Depending on the magnitude of the unique publication change, the contractor shall propose In Process Reviews (IPRs) with the Government, as required, prior to final publication. The contractor shall accomplish all research and source data acquisition needed to develop text, tables, figures, illustrations, etc. required for changes and supplements. The contractor shall provide paper or electronic copies as requested by the PCO. Using Commercial Off-The-Shelf software, the contractor shall track and retain electronic data, document all transmittals, archive files annually and create a CD/DVD for record retention purposes.

When a change is identified that affects another manual or an unidentified portion within the same manual, the contractor shall notify the Government and provide a recommendation and proposal for approval. Upon the Government’s approval, the contractor shall incorporate the changes and make distribution as directed.

4.11 Government Manuals (Technical Orders)

Development of new engineering data for new or revised technical orders shall be accomplished under an EA.

4.12 Government Furnished Property

The contractor shall properly document and track all Government Furnished Property (GFP) IAW Federal Aviation Regulation Part 45; however, the UID requirement is to be performed only at the aircraft level. All aircraft shall be tracked by Serial Number and Tail Number.

Upon departure of a GEA aircraft from a contractor service center, any serviceable/repairable items removed from the aircraft and not replaced with a same form/fit/function part shall be returned to the home station COMBS. When possible, the GFP shall be loaded on the returning aircraft. If this is not possible, the GFP shall be properly packaged and shipped to the COMBS for disposition or restocking, with shipping charges covered as O&A.

Upon departure of a GEA aircraft from a contractor service center, any unserviceable/unrepairable GFP that is removed from the aircraft and not replaced with a same form/fit/function part shall be returned to the home base on the aircraft. Alternatively, the customer may direct the PCO to abandon the GFP in place at the contractor facility and the contractor shall dispose of it using standard commercial practices.

The respective Program Office will be the final authority regarding disposition of parts removed, replaced or scrapped following maintenance/modification at the service center.

4.13 Service Summary

The contractor shall be aware that the absence of any contract requirement from the Service Summary does not detract from its enforceability nor does it limit the rights or remedies of the Government under any other provision of the contract.

The contractor shall ensure the following critical requirements are accomplished in accordance with the Service Summary table below:

4.13.1 Service Summary Requirements

The Service Summary requirements as noted in the table above shall be utilized and implemented as follows:

a) The contractor shall achieve performance thresholds identified in the Service Summary Table above. The performance thresholds are designed to:

a. Align contractor performance with objectives

b. Focus on critical success factors in meeting the performance objectives

c. Reflect performance goals

d. Promote continuous improvement in contractor performance

b) The appropriate Quality Assurance Representatives (QARs), Program Engineers, PCO, and the Program Managers will exercise surveillance over the performance thresholds.

c) The contractor shall support the Government’s surveillance methods as follows:

a. Inspection of recurring and non-recurring output

b. Inspection of the process output

d) The Government may use a combination of surveillance methods,…