Attach_1_FINAL_PWS_08_Jun_2016_Engineering_Technical_Analysis.pdf

PR: FD2060-16-95043 PWS REVISION: 1 1

Performance-Based Work Statement

For

F-15 ENGINEERING TECHNICAL ANALYSIS

FD2060-16-95043

08 June 2016

1. Description of Services

1.1. Objective(s): This Performance-based Work Statement (PWS) describes the engineering services required sustain the F-15 Technical Assistance Data System (TADS), analyze engineering assistance requests to identify adverse trends and recommended technical data updates, sustain the F-15 configuration management program to assure continued airworthiness, analyze and validate PDM structural inspections and component replacements to ensure continued structural integrity of the F-15 fleet, sustain the F-15 first article test and defense logistics agency source approval database, and conduct F-15 avionics reliability and maintainability investigations. Detailed requirements are documented in Section 4.0.

1.2. Benefit to United States Air Force (USAF): This acquisition will benefit the USAF by sustaining the ability to provide timely engineering dispositions to the F-15 fleet, assure configuration management and airworthiness of the F-15 fleet, and provide responsive investigations into avionics issues driving aircraft downtime. The overall goal of this effort is to optimize engineering efforts to identify and resolve reliability and maintainability issues while directly impacting the ability to sustain the Operational Safety, Suitability, and Effectiveness ultimately reduce USAF cost, and maximize aircraft availability and war fighter impact.

2. Services Summary

Performance Objective PWS

Reference Performance Threshold

Sustain TADS C&A

4.2.1.5

The Contractor shall perform Information Assurance Manager (IAM) efforts to sustain TADS in the EITDR and eMASS systems. The Contractor shall update the EITDR and eMASS to reflect any upgrades or changes in application functionality within 3 business days of completion of software changes but prior to fielding.

The Contractor shall maintain TADS online availability. 4.2.1.6

The Contractor shall sustain a 97% online availability for TADS over a 12-month period of performance with no more than 11 days of total downtime allowed per calendar year due to causes from the Contractor.

Twenty-four hours of downtime must be followed by forty-eight hours of uptime.

PR: FD2060-16-95043 PWS REVISION: 1 2

ETAR Analysis/Reporting

4.2.1.8

There shall be no more than 1 late metric report submission accepted per calendar year. There shall be no more than 2 late daily status reports per month.

Late daily reports submitted shall be followed by at least 3 on time daily reports.

TADS PDM Schedule Sustainment

4.2.1.9

4.2.1.9. The Contractor shall maintain Programmed

Periodic Depot Maintenance (PDM) Schedule Updates and Aircraft Possession Updates into F-15 TADS weekly or as required to provide the most current information to date. Data must be input accurately 99% of the time. Inaccurate data must be corrected no later than 5 business days of identification.

Provide Timely Updates and maintain configuration data documentation.

4.2.3.1

The Contractor shall update and maintain configuration data documentation. The Contractor shall update Configuration data systems and documentation files within 2 weeks of each CCB approved change.

Quality of the data requirements of the ASIP

Manager.

4.2.6.1

Data must be input accurately 99% of the time.

Inaccurate data must be corrected no later than 5 business days of identification.

Provide timely review and processing of PDM ASIP data (AFTO 95 and AFTO 3 Data) 4.2.6.1

Within 2 business days after receipt of the AFTO 95, a report detailing any AFTO 95 and AFTO 3 discrepancies and updates required shall be delivered via email to the appropriate government PDM point of contact for corrections. Once all corrections are completed, the AFTO 95 and AFTO 3 forms shall be submitted to Boeing through the web-based WebSAFE program.

Provide timely review and processing of PDM ASIP data (AFTO 238 Data) 4.2.6.1

The AFTO 238 database shall be reviewed on a daily basis to identify newly submitted AFTO 238 forms.

Upon receipt of a new AFTO 238, the information shall be reviewed for accuracy and completeness within 3 business days. A report detailing any discrepancies shall be submitted to the appropriate government point of contact for corrections.

Provide timely delivery of monthly Engineering

Disposition data (107's and 202’s)

4.2.6.1

By the 15th of each month, all engineering technical assistance requests (107’s and 202’s) completed in the previous month shall be submitted to Boeing through electronic means.

Complete review of all repairs/findings for F-15 wings and fuselages inducted into Robins Depot Maintenance.

4.2.6.4

The Contractor shall deliver a PDM Repairs/Findings report for each tail number within 10 business days following the final functional check flight.

Documentation of all repairs/findings for F-15 wings and fuselages inducted into Robins Depot Maintenance.

4.2.6.5

The Contractor shall enter all wing/fuselage repair and part replacement data into the NLign database within 10 business days following the final functional check flight for each aircraft.

PR: FD2060-16-95043 PWS REVISION: 1 3

Provide monthly sustainment review metric reports.

4.2.1.8 There shall be no more than 1 late monthly metric report submission accepted per calendar year.

Provide daily 107/202 status reports. 4.2.1.8

There shall be no more than 2 late daily status reports per month. Late daily report submitted shall be followed up by at least 3 on time daily reports submitted.

Ensure 339s are routed in a timely manner as required. 4.2.7.1

The Contractor shall ensure that 90% of 339’s are routed within the 2 business day requirement, not to exceed 5 business days for a given 12-month period of performance.

Ensure First Articles are routed in a timely manner as required. 4.2.7.2

The Contractor shall ensure that 90% of First Article Test requests are routed within the 2 business day requirement, not to exceed 5 business days for a given 12-month period of performance.

3. Government Property and Services

3.1. Government Property to be Provided: Government Property/Services is authorized IAW Appendix B to the contract. Contractors shall report any type of loss of Government property IAW all applicable Government property terms and conditions provided in the contract.

Government property shall be dispositional in accordance with the Government property plan or at the direction of the cognizant Government property administrator.

3.2. Reporting of Government Property:

3.2.1The Contractor shall create and maintain records of all Government property accountable to the contract, including Government-Furnished Property (GFP) in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

3.2.2 Reporting Loss of Government Property, the Contractor shall use the Defense Contract Management Agency (DCMA) eTools software application to report loss of Government property at the site below in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract/order. http://www.dcma.mil/aboutetools.cfm

3.3. Return/Retention of Government Property: All Government-Furnished Property (GFP) remains the property of the Government and shall be returned to the Government upon completion of the contract/order. All GFP shall be returned to the Government in the condition provided unless approved in advance by the Procuring Contracting Officer (PCO). All property acquired or otherwise provided by the Contractor for accomplishment of contract/order requirements becomes the property of the Government and shall be returned to the Government upon completion of the contract/order. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government upon completion of the http://www.dcma.mil/aboutetools.cfm

PR: FD2060-16-95043 PWS REVISION: 1 4

contract/order. All Department of Defense (DD) Form 1423, Contract Data Requirements List (CDRL), and deliverables become the property of the Government upon receipt.

3.4. Government System(s): The Government will provide Contractor personnel access to systems necessary to perform tasks under the contract to include but not limited to the following:

JEDMICS, Auto202/TADS, ETIMS, JRAMS, REMIS, ROCIT, and PDMSS. The Contractor shall ensure Contractor personnel who require access to a Government Automated Information System (AIS) have a Department of Defense National Agency Check Plus Written Inquiries (DNACI) conducted in accordance with Department of Defense (DoD) 5200.2-R, Personnel Security Program. The Government will provide system access subject to approval of the DD Form 2875, System Authorization Access Request (SAAR). Upon completion/termination of the contract/order or transfer/termination of Contractor personnel, the system account(s) will be closed.

4. 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 extends 5 years after receipt of order assuming all options are exercised with one 12 month basic period and four 12 month option periods.

4.1.2. Place of Performance: These services shall be performed at the Contractor’s facility as well as at Robins AFB, GA. On-site Contractors shall be present in the office of AFLCMC/WWQE to provide direct representation and support for TADS, Engineering configuration management analysis, PDM documentation analysis, and 339/First Article Test database related issues, analysis, and reporting.

4.2. Detailed Requirements

4.2.1. F-15 Technical Assistance Data System (TADS): F-15 TADS is a government owned contractor sustained software system and database utilized to manage and disposition F-15 field requests for engineering assistance (107’s). The software/database is currently hosted within the Robins enclave with an active Authority to Operate and Authority to Connect (ATO/ATC) with an expiration date of 11 Jan 2018.

4.2.1.1. Computer Security (COMPUSEC) Administration: The contractor shall provide engineering support to satisfy the requirement for Government Unit COMPUSEC Manager (UCM) functions as related to TADS and the Robins enclave hosting environment. This task includes implementing Air Force certifications and maintaining the TADS software inventory.

The contractor shall be required to meet appropriate certification levels and meet milestones identified in DoD 8570.01-M, Information Assurance Workforce Improvement Program, based on position descriptions. (CDRL A001, MONTHLY STATUS REPORT; DI-MISC-81384)

4.2.1.2. Application Updates: The contractor shall provide support for the installation of software sustainment updates to TADS. The contractor shall coordinate with and obtain approval from the

PR: FD2060-16-95043 PWS REVISION: 1 5

Government TADS PM and the Configuration Control Board (CCB) before any application changes/updates are accomplished. The contractor shall update, as required, the existing TADS documentation in accordance with each existing document data item description. (CDRL A001, MONTHLY STATUS REPORT; DI-MISC-81384, CDRL A003, SOFTWARE DESIGN

DESCRIPTION; DI-IPSC-81435/T)

4.2.1.3. Interface Control Documents (ICD): The contractor shall provide ICD updates as required in support of application updates. The contractor shall coordinate with and obtain approval from the Government before any change/update to an ICD is accomplished. (CDRL

A005, INTERFACE DESIGN DESCRIPTION; DI-IPSC-81436/T)

4.2.1.4. User Setup, Training, and Support:

a. The contractor shall perform user setup training and support as needed. User accounts shall be setup, for individuals desiring access to the system and as approved by the Government via a System Authorization Access Request (SAAR) 2875.

b. Work with users shall be performed to automate desired analyses and reports, on-going analysis support and reporting support shall be provided.

c. The contractor shall update the TADS User’s Guide as needed when updates to TADS are made. The User’s Guide is to be accessible via TADS.

4.2.1.5. Certification and Accreditation (C&A): The Contractor shall perform Information Assurance Manager (IAM) efforts to sustain TADS in the EITDR and eMASS systems. The Contractor shall update the EITDR and eMASS to reflect any upgrades or changes in application functionality within 3 business days of completion of software changes but prior to fielding. The Contractor shall ensure that TADS remains compliant with C&A guidelines. The Contractor shall establish supporting documentation and provide application configuration details in the support of the DoD Information Assurance (IA) Risk Management Framework (RMF) and/or the latest C&A process to assure maintenance and renewal of ATO/ATC as required. (A004, DI-

MISC-80508B/T)

4.2.1.6. Continued Functionality: The Contractor shall coordinate TADS updates and scheduled down time with the Robins hosting enclave to minimize the impact to the government users. The Contractor shall sustain a 97% online availability for TADS over a 12-month period of performance with no more than 11 days of total downtime allowed per calendar year due to causes from the Contractor. Twenty-four hours of downtime must be followed by forty-eight hours of uptime. Government holidays are not included in the required uptime.

4.2.1.7. Data Requests: The Contractor shall interface with government personnel to obtain data from the processing and tracking of field level nonconforming technical assistance request and reply 00-25-107 requests and engineering projects to ensure all data points are being captured and analyzed. These data requests will ensure that development and sustainment government personnel are receiving current and accurate information on which to base strategic decisions.

4.2.1.8. Engineering Technical Assistance Requests (ETARs) Analysis: The Contractor shall provide monthly sustainment review metric reports and daily 107/202 status reports. The Contractor shall utilize the TADS and Auto 202 systems to collect and report metrics and status.

PR: FD2060-16-95043 PWS REVISION: 1 6

There shall be no more than 1 late metric report submission accepted per calendar year. There shall be no more than 2 late daily status reports per month. Late daily reports submitted shall be followed by at least 3 on time daily reports. (A004, DI-MISC-80508B/T)

4.2.1.9. The Contractor shall maintain Programmed Periodic Depot Maintenance (PDM) Schedule Updates and Aircraft Possession Updates into F-15 TADS weekly or as required to provide the most current information to date. Data must be input accurately 99% of the time.

Inaccurate data must be corrected no later than 5 business days of identification. The Contractor shall ensure old Field Level Nonconforming Technical Assistance Request and Reply 00-25-107 requests are in database.

4.2.1.10. Continuous Improvements: The Contractor shall review, develop, and recommend process improvements on storage, tracking, and organization of data to allow for accurate analysis of technical assistance data. The recommendations and solutions shall include what search capabilities are required to provide historical data on engineering dispositions, and as a minimum, shall include tail number or problem description. The Contractor shall reconcile repair reporting to resolve data errors in data in F-15 TADS and the Auto 202 system to be used by ASIP, Structural, and Systems Engineering. Data scrub the 202 system monthly and work with organic IT staff to update known errors in Serial Number, Tail Number, Work Order Number, and Model Number inputs.

4.2.1.11. Minimum Qualifications: The primary technical Contractor personnel fulfilling TADS software sustainment services shall possess either a computer science degree at the bachelor’s level or a degree closely related in an Information Technology discipline at the bachelor’s level.

Prior experience in SQL Server Management Studio, MS Excel, MS Access, MS PowerPoint, Adobe, Classic ASP, and Javascript is required.

4.2.2. Engineering Analyses

4.2.2.1. Trend Analysis: The Contractor shall utilize TADS to retrieve data from Maintenance Assistance Requests (MARs) and Technical Assistance Requests (TARs) governed by the Technical Order 00-25-107 and conduct trend analysis. The Contractor shall analyze engineering repair dispositions for both field and depot engineering technical assistance requests (107’s and 202’s) down to the part number level to identify top problem areas. Recurring repairs, those occurring 3 or more times, will be evaluated for inclusion in the technical order system.

Data shall be presented by aircraft serial number, base, part number and/or damage area. It may also need to be presented to MAJCOM. The Contractor shall also include data retrieved from the Nonconforming Technical Assistance Request and Reply, AFMC Form 202 Database, in this analysis. The Contractor shall evaluate both the data from TADS and Automated AFMC Form 202 systems and highlight repetitive failures by part number. The Contractor shall make solution recommendations to resolve the root cause problems. The initial trend analysis shall encompass the most recent 5 years of 107/202 disposition data. Follow-on trend analysis shall incorporate

(A004, DI-MISC-80508B/T)

4.2.3. Engineering Configuration Management: The Contractor shall analyze all recommended configuration changes to the F-15 operational baseline to assure all developmental

PR: FD2060-16-95043 PWS REVISION: 1 7

and operational testing has been completed, impacts to airworthiness is accurately portrayed, and the required documentation is complete in accordance with processes defined in the F-15 Systems Engineering Plan (SEP). These services will ensure that the F-15 remains operationally safe, suitable, and effective.

4.2.3.1. Configuration Control Board: The Contractor shall establish and sustain an F-15 Configuration Control Board (CCB) process. The Contractor shall ensure that all change proposal documents are complete, technically accurate, and properly validated by the using/lead command prior to initiating coordination and approval processes. The Contractor shall work closely with the F-15 Chief Engineer to determine the proper routing and review authorities for each change package. The Contractor shall establish the review/approval timeline and data requirements for each package in accordance with the F 15 SEP. The Contractor shall schedule a CCB meeting for final approval of each change request, publish the CCB agenda, and ensure that all permanent/auxiliary board members as well as personnel are responsible for briefing, supporting the proposal, providing notification of the meeting time/date/location. The Contractor shall monitor and track the review/coordination status and report technical or programmatic issues to the Chief Engineer. The Contractor shall review final briefing slides and data package to ensure it meets F-15 SEP requirements prior to meeting the CCB. The Contractor shall document and publish the CCB discussion and action items in the meeting minutes, track and ensure that all open items are closed to satisfactorily support the CCB decision. The Contractor shall update and maintain configuration data documentation. The Contractor shall update Configuration data systems and documentation files within 2 weeks of each CCB approved change.

4.2.3.2. Configuration Database: The Contractor shall ensure modifications are documented in accordance with prescribed AF regulatory guidance. The Contractor shall maintain configuration baselines documentation for the F-15 through disciplined tracking of all proposed configuration changes. The Contractor shall update existing configuration management databases, such as Eagle Modification and Planning System (EMAPS) to reflect current status of all proposed configuration changes, to include temporary modifications. The Contractor shall maintain all supporting documentation for each change proposal in an approved government data system (currently AFMC SharePoint site).

4.2.3.3. Technical Reviews: The Contractor shall ensure configuration management requirements are properly applied to new projects and programs as necessary. The Contractor shall participate in formal technical reviews such as Preliminary Design Reviews (PDRs), Critical Design Reviews (CDRs), Functional Configuration Audits (FCAs), and Physical Configuration Audits (PCAs) as directed. The Contractor shall evaluate AF Form 1067 (Modification Proposal), Engineering Change Proposals (ECP), Requests for Deviation/Waivers, Contract Change Proposals (CCP), and Advance Change Study/Notices for adequacy, completeness, and compliance with directives. The Contractor shall interpret and integrate comments; e.g.

technical, financial, contractual, etc., resulting from review of proposed change.

4.2.3.4. Configuration Process Sustainment: The Contractor shall maintain the requirement and configuration process documentation referenced by the F-15 SEP. The Contractor shall recommend changes and draft new procedures to improve the configuration management process

PR: FD2060-16-95043 PWS REVISION: 1 8

or meet new/unique program requirements. The Contractor shall participate in engineering process improvement initiatives as required. The Contractor shall update process documentation and ensure conformance to any changes that are implemented.

4.2.3.5. The Contractor shall maintain currency on DoD/USAF instructions, directives, military standards and specifications, data item descriptions, Acquisition Management System and Data Requirements Control List, and other information applicable to configuration data management.

The Contractor shall ensure compliance with DoD, AF, and local configuration management policy and procedures.

4.2.3.6. Upon approval by the government, the Contractor shall attend and participate in meetings and conferences with the organization, using and supporting commands, and other Contractor representatives to resolve issues regarding configuration, data, and engineering data management.

4.2.3.7. The Contractor shall ensure that interactions with internal and external officials and/or customers at conferences and meetings are diplomatic, convincing, professional, and promote effective working relationships.

4.2.3.8. Minimum Qualifications: Personnel fulfilling configuration management services are required to be proficient in USAF configuration management processes and requirements.

4.2.4. Avionics Reliability and Maintainability Investigations: The Contractor shall perform detailed technical and analytical investigations in support of identified operational reliability and maintainability (R&M) drivers directly F-15 operational availability.

4.2.4.1. Preventative Maintenance Optimization Analysis: The Contractor shall perform a study of the F-15C/D and F-15E avionics subsystems and components to identify adverse reliability trends and recommended maintenance requirement changes (i.e.- additional inspections, inspection updates, deletion of ineffective inspections, or inspection interval changes). The technical data of interest in the analysis that shall be reviewed are the 1F-15A/E-6 (including work cards), PDM Work Specification, 1F-15A-06, and respective job guides, fault isolation, and general system technical orders. The Contractor shall review 20% of the avionics related subsystems, or Work Unit Codes (WUC) to include: Instruments (51), Autopilot (52), Malfunction Analysis and Recording Equipment (55), Integrated Guidance and Flight Control (57), Communications (63), Identification Friend or Foe (IFF) (65), Radio Navigation (71), Radar Navigation (72), Fire Control (74), Electronic Countermeasures (76), and Computer and Data Displays (82). The schedule of WUC’s to be reviewed during each period of performance will be approved by the government no later than the initial quarterly program management review. (A004, DI-MISC-80508B/T)

4.2.4.2. Obsolescence Studies: The Contractor shall investigate component obsolescence issues to avoid imminent force structure reduction. This analysis shall be conducted in conjunction with the Preventative Maintenance Optimization Analysis (paragraph 4.2.4.1) and delivered as an appendix or subsection to the annual 20% WUC analysis reports. The Contractor shall coordinate with the Air Force Sustainment Center (AFSC) commodity engineering and logistics support

PR: FD2060-16-95043 PWS REVISION: 1 9

group to identify obsolescence drivers and determine recommended actions. The Contractor shall utilize the LDMS system to analyze/report obsolescence issues. (A004, DI-MISC-80508B/T)

4.2.4.3. Quick Reaction Maintainability Investigations: The Contractor shall perform investigations into Organizational, Intermediate, and Depot level maintenance issues requiring investigation and disposition outside of routine technical data. The Contractor shall have the ability to interact and investigate avionics related systems issues remotely utilizing the TADS and Auto 202 systems to manage requests for technical assistance. For planning purposes, over the last 2 years, on average 2 dispositions per week were required requiring disposition within 2 business days. Further, the Contractor shall be capable of providing on-site support for any operational F-15 location as needed. The Contractor shall be capable of responding to on-site support requests within 3-business days and as required travel allows. Travel must be approved in advance by the PCO. For planning purposes, over the last 2 years, on average 4 on-site support trips per year were required to several locations (to potentially include OCONUS travel) covering 5 business days each on average. The Contractor shall deliver a Maintainability Investigation report within 14 business days upon returning from any on-site support. (A004, DI-

MISC-80508B/T)

4.2.4.4. Functional Systems Integrity Program (FSIP) Support: The Contractor shall provide expert analysis and advice related to ongoing Government Reliability Centered Maintenance (RCM) and Maintenance Steering Group 3 (MSG-3) efforts. The Contractor shall be capable of reviewing and developing failure modes, identifying appropriate inspection intervals and levels, and developing new and novel inspection processes and technical data. Details of the FSIP Support provided shall be reported and updated in conjunction with the monthly status reports.

(CDRL A001, MONTHLY STATUS REPORT; DI-MGMT-80368)

4.2.4.5. The Contractor shall provide integration, design and/or re-design engineering support for avionics modification efforts currently ongoing and planned, to include the Advanced Core Display Processor II (ADCP II), the Passive Attack Sensor System (PASS), F-15 C/D SATCOM, the Active Electronically Scanned Array (AESA) radar and IFF upgrades. Support, analysis, and investigations shall leverage expert F-15 avionics integration knowledge to sustain an operational baseline for the F-15 fleet.

4.2.4.6. Minimum Qualifications: The Contractor shall possess in-depth knowledge of crypto modernization, also known as VACM, which will soon be impacting every avionics system on the aircraft containing keyed cryptographic codes. Further, personnel fulfilling the Avionics Reliability and Maintainability support are required to be proficient in F-15 peculiar and common avionics integration and sustainment.

4.2.5. Airworthiness Engineering Analysis: The Airworthiness process is utilized to obtain USAF Technical Airworthiness Authority (TAA) approval of an aircraft modification for operations. Successful completion of the rigorous Airworthiness process is required to obtain a Flight Authorization (Military Flight Release (MFR) or Military Type Certificate (MTC)). The Engineering Services described herein are concerned with the technical reviews and analysis required to develop an Airworthiness Plan and Certification Basis among other supporting documentation.

PR: FD2060-16-95043 PWS REVISION: 1 10

4.2.5.1. Initial Airworthiness Determination Form (ADF): Upon notification of a new sustainment modification program, the Contractor shall coordinate with the appropriate Government technical POCs to develop an initial ADF. Key attributes of the ADF include an evaluation of the Airworthiness impact, an evaluation of the reportability determination to assess impacted MIL-HDBK-516 sections and hazards, and an overall recommended Airworthiness approach to meeting Airworthiness requirements/standards. Refer to the ADF and Modification Airworthiness Certification Criteria (MACC) templates as well as Airworthiness Bulletin 002 (AWB-002), AWB-007, and MIL-HDBK-516C for further information. The Contractor shall complete on average 23 ADF evaluations per 12-month period of performance. (A004, DI-

MISC-80508B/T)

4.2.5.2. Modification Airworthiness Analyses with Impact: Upon completion of the ADF, should the modification be verified to have no impact to Airworthiness, additional analysis and documentation will not be required. For those modifications that are determined to have an Airworthiness impact, further analysis and reporting to include a detailed certification basis, first flight basis, first flight compliance report, MFR or MTC processing, and final compliance report will be required throughout the process of validating and fielding a modification.

4.2.5.2.1. Detailed Certification Basis: As required and following approvals of ADF’s, the Contractor shall coordinate with the appropriate Government technical POCs to develop a detailed Airworthiness Certification Basis. The certification basis shall identify the impacted MIL-HDBK-516 Sections and subsections, detail the method of compliance for each criterion, and cite any applicable standards or policy documents. Refer to an example Certification Basis in the Appendix as well as MIL-HDBK-516 for further information. The Contractor shall complete up to 6 Certification Basis analyses per 12-month period of performance. (A004, DI-

MISC-80508B/T)

4.2.5.2.2. First Flight Basis: Following the approval of the Certification Basis and as required for pending flight testing, the Contractor shall coordinate with the appropriate Government technical POCs to develop a detailed First Flight Basis. The First Flight Basis shall identify the subset of criteria from the Certification Basis which will be evaluated during flight test as well as a more detailed method of compliance for each. Refer to an example First Flight Basis in the Appendix as well as MIL-HDBK-516 for further information. The Contractor shall complete up to 6 First flight basis analyses per 12-month period of performance. (A004, DI-MISC-80508B/T)

4.2.5.2.3. First Flight Compliance Report: Following (or in conjunction with) the approval of the First Flight Basis, the Contractor shall coordinate with the various Government technical POCs to develop a detailed First Flight Compliance Report. The First Flight Compliance Report shall identify the status of compliance for those criteria that must be satisfied prior to flight test.

Any technical reports shall be referenced and for any non-compliant criteria, a credible hazard(s) shall be identified along as well as the Airworthiness Hazard Index for each. Finally, the Contractor shall provide an approval recommendation for flight test. Refer to an example First Flight Compliance Report in the Appendix as well as MIL-HDBK-516 for further information.

The Contractor shall complete up to 6 First Flight Compliance Reports per 12-month period of performance. (A004, DI-MISC-80508B/T)

PR: FD2060-16-95043 PWS REVISION: 1 11

4.2.5.2.4. Military Flight Release Processing: Upon Chief Engineer approval of the First Flight Compliance Report, the Contractor shall coordinate processing of the Military Flight Release approving modification flight test.

4.2.5.2.5. Military Type Certificate Processing: Upon Chief Engineer approval of the Final Compliance Report, the Contractor shall coordinate processing of the Military Type Certificate approving the modification for use on the F-15 fleet.

4.2.5.2.6. Final Compliance Report: Upon completion of all impacted MIL-HDBK-516 criteria, the Contractor shall coordinate with appropriate Government POCs to complete the Final Compliance Report documenting the final status of all impacted criteria, referencing applicable technical reports, identifying credible hazards for non-compliances and applicable Airworthiness Hazard indexes. Refer to an example Final Compliance Report in the Appendix as well as MIL- HDBK-516 for further information. The Contractor shall complete up to 6 Final Compliance reports per 12-month period of performance. (A004, DI-MISC-80508B/T)

4.2.5.3. Airworthiness Program Tracking: Upon the initiation of an Airworthiness assessment project, the Contractor shall track the progress of the efforts in comparison to the required milestone dates. The Contractor shall sustain a tracking database to document the status of each airworthiness assessment and systematically coordinate actions required. Refer to the AFLCMC Standard Process for Reportable Airworthiness Flight Authorization for a detailed process.

4.2.5.4. Airworthiness Program Reviews: The Contractor shall convene Airworthiness reviews as required in efforts to track progress, identify issues, make decisions, and assure proper coordination. Reviews will be conducted with the F-15 Program Office and will require on-site support.

4.2.5.4.1. In conjunction with the submission of the First Flight Basis and First Flight Compliance Report, the Contractor shall convene an Experimental Flight Release Board on site at Robins AFB with the F-15 Chief Engineer and applicable subject matter experts.

4.2.5.4.2. In conjunction with the submission of the Airworthiness Compliance Report, the Contractor shall convene an Airworthiness Board on site at Robins AFB with the F-15 Chief Engineer and applicable subject matter experts.

4.2.5.5. Training: As requested by the government, the Contractor shall provide on-site training to new government engineers with respect to the Airworthiness process, actions required to complete an Airworthiness plan, required Airworthiness activities, reference documents and policies, and insight into lessons learned from previous efforts.

4.2.6. PDM Maintenance Data Analysis and Review

4.2.6.1. PDM Documentation: The Contractor shall review and process documentation generated by the F-15 PDM line. Upon receipt of an AFTO 95 form, all data shall be reviewed for errors.

Further, all required IAT inspection AFTO 3 documentation shall be verified to be present

PR: FD2060-16-95043 PWS REVISION: 1 12

(either as a pdf or electronic submittal within the Boeing WebSAFE program), accurate, and with any prior identified corrections required verified to be complete. Within 2 business days after receipt of the AFTO 95, a report detailing any AFTO 95 and AFTO 3 discrepancies and updates required shall be delivered via email to the appropriate government PDM point of contact for corrections. Once all corrections are completed, the AFTO 95 and AFTO 3 forms shall be submitted to Boeing through the web-based WebSAFE program. In addition to AFTO 95 and AFTO 3 forms, the AFTO 238: F-15 Component Serialization Records shall be reviewed for accuracy and consistency with respect to the respective AFTO 95. The AFTO 238 database shall be reviewed on a daily basis to identify newly submitted AFTO 238 forms. Upon receipt of a new AFTO 238, the information shall be reviewed for accuracy and completeness within 3 business days. A report detailing any discrepancies shall be submitted to the appropriate government point of contact for corrections. A monthly report of ongoing AFTO 95, AFTO 3, and AFTO 238 efforts to include those forms awaiting correction and/or missing from the PDM organization shall be submitted to the ASIP manager. Data must be input accurately 99% of the time. Inaccurate data must be corrected no later than 5 business days of identification. (CDRL A001, MONTHLY STATUS REPORT; DI-MGMT-80368)

Contractor personnel shall work with the ASIP Manager to complete the following tasks as needed: answer questions from the ASIP manager, other F-15 engineers, and/or other WEB SAFE users concerning data they have entered into the WEB SAFE database; relay any response from field units and/or Major Commands to the F-15 ASIP Manager. Additionally, by the 15th of each month, all engineering technical assistance requests (107’s and 202’s) completed in the previous month shall be submitted to Boeing through electronic means.

4.2.6.2. PDM Incoming Inspections: The Contractor shall visually inspect all incoming Robins AFB PDM F-15 aircraft and document 100% of the incoming repairs for both the fuselage and wings. All incoming repairs shall be documented by wing or aircraft serial number as applicable.

The repair location shall be documented to include wing or fuselage station, water line, butt line, hole numbers, and part number of the repaired component(s). Pictures shall be taken to help identify the location and repair. The pictures shall be easily retrievable from the wing and fuselage database.

4.2.6.3. PDM Repairs/Findings Review: The Contractor shall verify all Robins AFB PDM F-15 repairs and structural damage findings occurring during the inspection and repair phases of PDM. All repairs and findings shall be documented by wing or aircraft serial number as applicable. The repair location shall be documented to include wing or fuselage station, water line, butt line, hole numbers, and part number of the repaired component(s). Pictures shall be taken to help identify the location and repair. The pictures shall be easily retrievable from the wing and fuselage database.

4.2.6.4. PDM Repairs/Findings Analysis: The Contractor shall analyze all Robins AFB PDM F- 15 incoming and implemented repairs as well as findings (4.2.4.2 and 4.2.4.3) for each tail number (100%) to identify any adverse impacts to safety of flight structure, recommendations for further engineering investigations, highlight areas of concern, and identify any adverse trends.

The Contractor shall deliver a PDM Repairs/Findings report for each tail number within 10 business days following the final functional check flight. (A004, DI-MISC-80508B/T)

PR: FD2060-16-95043 PWS REVISION: 1 13

4.2.6.5. The Contractor shall utilize the developed detailed F-15 wing/fuselage inspection data collection form and F-15 wing/fuselage flow chart to act as an F-15 template and ensure inspectors follow a step by step process as they review/inspect over hundreds of aircraft parts for incoming repairs and defects. Forms include several data entries including part number, aircraft flying hours, technical order reference, repair disposition, area of damage, deficiency, defect dimensions, orientation and hole numbering. The Contractor shall enter all wing/fuselage repair and part replacement data into the NLign database within 10 business days following the final functional check flight for each aircraft.

4.2.6.6. The Contractor shall ensure all repair and damage finding photos and data are overlaid onto the NLign F-15 model. The Contractor shall coordinate with Etegent to discuss issues regarding the NLign software. The Etegent point of contact will be provided by the government.

4.2.6.7. Minimum Qualifications: Personnel fulfilling the wing/fuselage repair and findings inspection and analysis services are required to be proficient in military aircraft repair and inspection processes.

4.2.7. Logistics Engineering Support Requests and First Article Test

4.2.7.1. The Contractor shall sustain the Defense Logistics Agency (DLA) engineering support request (also known as 339s) database and routing process. The database and tracking shall ensure that all 339’s are routed and completed in a timely manner. All incoming 339 requests shall be reviewed for accuracy and completeness prior to initiating routing for engineering review. All incoming 339’s shall be reviewed and routed to the appropriate F-15 Program Office engineer or demote the 339 back to 409 SCMS/GUEA office for screening within 2 business days of receipt. The Contractor shall ensure that 90% of 339’s are routed within the 2 business day requirement, not to exceed 5 business days for a given 12-month period of performance. See paragraphs below for 339 routing and review process.

4.2.7.1.1. Initial review and routing: The 409 SCMS/GUEA office will initiate a 339 requiring F-15 Program Office engineering review through the Integrated Engineering Support (IES) system. Upon receipt of the 339 package, the Contractor shall validate the requirement, assure the package is complete, determine if a Screening Analysis Worksheet (SAW) has been completed or is required to be completed, and identify the details of the part with respect to location on the aircraft and functionality. If the 339 package is complete with no issues, the Contractor shall route the 339 package to the appropriate F-15 Program Office engineer within the IES system. However, if a SAW has been determined to be required and not completed, the 339 package shall be demoted back to the 409 SCMS/GUEA within the IES system.

4.2.7.1.2. Final review and routing: Upon completion, the F-15 Program Office engineer will notify the Contractor via a tracking folder. The Contractor will review and verify all attachments within the 339 package to include the SAW, Engineering Data List, Form 260, First Article Cost Estimate, and First Article Test Plan as required. Upon the approval of an authorized F-15 Program Office engineering section or branch chief, if the attachments are determined to be complete with no issues identified, the Contractor shall promote the 339 package to the 409

PR: FD2060-16-95043 PWS REVISION: 1 14

SCMS/GUEA within the IES system. The First Article Test Plan shall be processed as detailed in section 4.2.5.2.

4.2.7.2. The Contractor shall sustain the First Article Test engineering support request database and routing process. The database and tracking shall ensure that all First Article Test requests and reports are routed and completed in a timely manner. All incoming First Article Test requests shall be reviewed for accuracy and completeness prior to initiating routing for engineering review. All incoming First Article Test requests shall be reviewed and routed to the appropriate F-15 Program Office engineer within 2 business days of receipt. The Contractor shall ensure that 90% of First Article Test requests are routed within the 2 business day requirement, not to exceed 5 business days for a given 12-month period of performance. See paragraphs below for First Article Test request routing and review process.

4.2.7.2.1. Initial review and routing: The 409 SCMS/GUEA office will initiate a First Article Test request or provide First Article Test results requiring F-15 Program Office engineering review through the Test Management and Control for First Articles (TMACS) system. Upon receipt of the First Article Test package, the Contractor shall validate the requirement, determine if an accompanying 339 is present and reviewed, and identify the details of the part with respect to location on the aircraft and functionality. If the First Article Test package is complete with no issues, the Contractor shall route the package to the appropriate F- 15 Program Office engineer within the TMACS system.

4.2.7.2.2. Final review and routing: Upon completion, the F-15 Program Office engineer will notify the Contractor via a tracking folder. The Contractor will review and verify all attachments within the First Article Test package as required. Upon the approval of an authorized F-15 Program Office engineering section or branch chief, if the attachments are determined to be complete with no issues identified, the Contractor shall promote the First Article Test package to the 409 SCMS/GUEA within the TMACS system.

4.2.8. Reports and Technical Data: The Contractor shall submit the following reports and technical data. Data submittals shall be provided electronically whenever possible. Data requirements shall be as specified in Contract Data Requirements Lists (CDRLs), DD Form 1423. Specific data requirements will be determined by the Air Force.

4.2.8.1. Monthly Status Report: The Contractor shall submit a monthly status report to include a brief summary of work accomplished during the time period, work planned for the next month, and documentation of any decisions reached jointly by the Air Force and the Contractor during the month in question. The monthly report is due on or before the 15th of each month to cover the month prior. The initial monthly report will be due no sooner than 45 business days after contract award and will include all efforts to date. (CDRL A001, MONTHLY STATUS REPORT; DI-

MGMT-80368)

4.2.8.2. Funds and Man-Hours Expenditure Report: The Contractor shall submit a monthly funds and man-hour expenditure report detailing the actual funding and man-hours expended as well as a comparison to the estimated, or planned funding and man-hour expenditure. The report shall include details of the previous month as well as the total to date. The data shall be reported by

PR: FD2060-16-95043 PWS REVISION: 1 15

Contract Line Item Number in addition to the overall contract status. The monthly report is due on or before the 15th of each month to cover the month prior. The initial monthly report will be due no sooner than 45 business days after contract award and will include all efforts to date. The report shall be included as an attachment to the monthly status report (4.2.6.1). (A002, DI-

MGMT-81468/T)

4.2.8.3. Technical Reports – Investigations/Studies: The Contractor shall deliver the following Contract Data Requirements List (CDRL) items:

CDRL

No.

PWS

Para Delivery Date CDRL Description

A001

4.2.1.1 4.2.1.2 4.2.6.1 4.5 4.6 4.7

Monthly (No later than the 15th of the month and complete as of the end of the previous month.)

Status Report

A003

4.2.1.2

60 days after contract award and as required based on software changes after.

Software Design Description

A005 4.2.1.3 60 days after contract award and as required based on software changes after.

Interface Design Description

A004 4.2.1.5 As required in support of achieving and sustaining ATO/ATC.

Technical Report (TR) - C&A Supporting Documentation

A004 4.2.1.8

Daily (business day) and Monthly (No later than the 15th of the month and complete as of the end of the previous month)

TR - ETAR Status/Metrics Report

A004 4.2.2.1 180 days after contract award and Quarterly thereafter.

TR - ETAR Trend Analysis Report

A004 4.2.4.1 4.2.4.2

Annual (330 days after beginning of period of performance) TR - Avionics R&M Studies

A004 4.2.4.3 As required (14 business days after completion of investigations)

TR - Avionics Quick Reaction Investigations

A004 4.2.5.1 As required (up to 9 per 12 month period of performance)

TR - Airworthiness Determination Forms

A004 4.2.5.2.1 As required (up to 6 per 12 month period of performance)

TR - Airworthiness Certification Basis

A004 4.2.6.4 As required for each aircraft (10 business days after final functional check flight)

TR - PDM Repairs/Findings Report

A002 4.2.8.2 Monthly (No later than the 15th of the month and complete as of the end of the previous month.)

Funds and Man-Hours Expenditure Report

A006 4.6 Quarterly (4 total per 12-month period Quarterly Program Management

PR: FD2060-16-95043 PWS REVISION: 1 16

of performance) Review Minutes

A007 5.5.4.1 30 days after contract award and as required after

Programmatic Environmental Safety and Health Evaluation

Plan

4.2.8.4. There shall be no more than one rejection of report per quarter. There shall be no more than one rejection of each report. The Government will reject the submitted report if one or more technical errors or one or more minor errors are found within the report. 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 defined as a typographical or grammatical error. The rejected data/document shall be corrected and resubmitted within 5 business days of notification of Government rejection.

4.2.8.5. There shall be no more than one late submission of the final report. The Contractor shall notify the Government if the delivery of any report will not meet the scheduled delivery date and negotiate a revised delivery date. The report shall be delivered by a revised delivery date acceptable to the Government.

4.3. Packaging: The Contractor shall package and mark material in accordance with the contract (basic or order, as applicable) Air Force Materiel Command (AFMC) Form 158, Packaging Requirements; MIL-STD-129P, Department of Defense Standard Practice / Military Marking for Shipment and Storage; MIL-STD-130N, Department of Defense Standard Practice / Identification Marking of U.S. Military Property; and MIL-STD-2073-1D, Standard Practice for Military Packaging. 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.4. Deleted.

4.5. Travel: Requests for travel by Contractor personnel shall be submitted for approval to the PCO a minimum of ten business days in advance of departure for routine travel and no less than 1 business day for Quick Reaction Maintainability Investigations (IAW 4.2.4.2). Travel by Contractor personnel shall be conducted in accordance with FAR 31.205-46, Travel costs.

Travel by DoD civilian personnel will be conducted in accordance with The Joint Travel Regulations (JTR), Volume 2, Department of Defense Civilian Personnel. (A001 DI-MGMT- 81468/T) (Cost Reimbursable Based on Need)

4…