PWS BE360ER Full Flight Simulator_Draft 20241011.pdf

FEDERAL AVIATION ADMINISTRATION

FLIGHT PROGRAM OPERATIONS (AJF)

BE360ER FULL FLIGHT SIMULATOR

PERFORMANCE WORK STATEMENT (PWS)

The Contractor is to use this document to submit a proposed Contractor Statement of

Work

October 11, 2024

PWS_BE360ER Full Flight Simulator October 11, 2024

TABLE OF CONTENTS

1.0 PURPOSE………………………………………………………………………………………… 3

2.0 CONSTRAINTS…………………………………………………………………………………... 3

3.0 PROGRAM MANAGEMENT OBJECTIVES…………………………………………………... 3

3.1 Program Manager………………………………………………………………………… 3

3.2 Meetings…………………………………………………………………………………… 4

3.3 Post Award Conference…………………………………………………………………. 4

3.4 Program Management Status Reports………………………………………………… 4

4.0 QUALITY ASSURANCE OBJECTIVES……………………………………………………….. 4

4.1 Quality Assurance Surveillance Plan (QASP)………………………………………… 4

5.0 SIMULATOR PLANNING AND DEVELOPMENT…………………………………………….. 4

5.1 Master Integrated Schedule Plan (MISP)……………………………………………… 4

5.2 Preliminary Design Review (PDR)……………………………………………………… 4

5.3 Critical Design Review (CDR)…………………………………………………………... 5

6.0 SIMULATOR PHYSICAL ATTRIBUTES………………………………………………………. 5

6.1 Base Simulator Requirements………………………………………………………….. 5

6.2 Flight Inspection Requirements…………………………………………………………. 5

6.3 Mission Specialist Requirements……………………………………………………….. 5

7.0 SIMULATOR HARDWARE OBJECTIVES…………………………………………………….. 5

8.0 SIMULATOR SOFTWARE OBJECTIVES…………………………………………………….. 6

8.1 System Software Design………………………………………………………………… 6

8.2 Required Simulator Software……………………………………………………………. 6

8.3 Software Manuals………………………………………………………………………… 7

9.0 SIMULATOR SITE INSTALLATION……………………………………………………………. 7

9.1 Site Plan…………………………………………………………………………………… 7

9.2 Initial Location of Equipment/Scale Drawing 7

9.3 Installation Drawings……………………………………………………………………... 7

9.4 Installation Site Survey…………………………………………………………………... 8

9.5 Site Readiness Review and Report…………………………………………………….. 8

9.6 Simulator Installation…………………………………………………………………….. 8

10.0 INSPECTION AND ACCEPTANCE……………………………………………………………. 8

10.1 Simulator Validation……………………………………………………………………… 8

10.2 Contractor Validation…………………………………………………………………….. 8

10.3 In Plant Acceptance……………………………………………………………………… 8

10.4 On Site Acceptance 9

11.0 LOGISTICS OBJECTIVES……………………………………………………………………… 9

11.1 Maintenance Support…………………………………………………………………….. 9

11.2 Technical Support………………………………………………………………………… 9

11.3 Technical Publications…………………………………………………………………… 9

11.4 Training……………………………………………………………………………………. 9

11.5 Engineering Support……………………………………………………………………... 9

11.6 Configuration Management……………………………………………………………… 9

12.0 DATA DELIVERABLES………………………………………………………………………….. 10

PWS_BE360ER Full Flight Simulator

1.0 PURPOSE

The Federal Aviation Administration (FAA) requires the capability of an advanced Level

D aircraft full flight simulator (FFS). This simulator will be used to conduct training and qualification required under Part 135 for Flight Program Operations (AJF) pilots. It will also be available for Aviation Safety (AVS) participants in the FAA Flight Program for

Aviation Safety Inspector (ASI) currency/proficiency and training, as well as and Aircraft

Certification Service Flight Test Crew Resource Management programs. The simulator will also be available for research and support sustainment initiatives for the evolving national aerospace environment. The simulator must be representative of the

Beechcraft 360ER aircraft and fulfill the design requirement of the recent FAA Flight

Program purchased Textron BE360ER aircraft. The 360ER simulator will provide all levels of pilot training including initial aircraft qualification training, recurrent qualification training, instrument refresher training, landing and instrument approach re-currency training, emergency procedure training and crew standardization training. It will be used to simulate validation of flight procedures, verification of the accuracy of procedure databases, and evaluation of the flyability and safety of new and amended procedures.

An additional training objective will be to provide mission training capability for various

AJF missions and tasks including possible integration of the Modular Mission System

(MMS) operation into crew training.

The simulator must be qualified as a Level D Full Flight Simulator (FFS), in accordance with 14 CFR part 60 and the Qualification Test Guide (QTG) for Airplane Simulator

Qualification. The simulator must also be qualified to meet 14 CFR part 60, Change 2 to include qualification standards for extended envelope and adverse event weather training tasks. Additional requirements include product support, training, and optional contractor maintenance support after installation.

The anticipated period of performance for this requirement will begin at contract award for a period not to exceed two years for production and installation of the simulator and five (5) one-year option periods.

2.0 CONSTRAINTS

The contractor’s solution must comply with all applicable standards and government regulations, which include:

• 14 CFR part 60 – Flight Simulation Training Device Initial and Continuing Qualification and Use. 14 CFR part 60, Change 2 to include qualification standards for extended envelope and adverse event weather training tasks.

• All applicable National Simulator Program (NSP) Flight Simulation Training Devices

(FSTD) Information Bulletins

• 14 CFR Part 135, Appendix H

• Qualification Test Guide (QTG) as defined by International Civil Aviation Organization

(ICAO) Manual of Criteria for the Qualification of Flight Simulation Training Devices (Doc

9625), 4th edition, 2015.

• American National Standards Institute (ANSI) ASQC-Q- 9001-1994 and ISO 9000-3

• ANSI/ASQC Q9002-1994 (International Standards Organization (ISO) 9902).

3.0 PROGRAM MANAGEMENT OBJECTIVES

3.1 Program Manager - The contractor must assign a dedicated Program Manager (PM) to organize, plan, schedule, implement, control, analyze, and report on all objectives of the contract, from initial planning stages through Government acceptance and completion of the contracted deliverable(s). The PM must have sufficient corporate authority to direct, execute, and control all elements of the program.

3.2 Meetings - Conduct and document meetings such as Program Management Reviews

(PMR), Preliminary Design Review (PDR), Critical Design Review (CDR) and

Technical Interchange Meetings (TIM)

3.3 Post Award Conference – Support a Post Award Conference to be held at the contractor facility within thirty (30)-calendar days after contract award.

3.4 Program Management Status Reports (PMSR) – Provide a monthly PMSR which must outline milestones, open action items, risks, mitigations and costing information.

4.0 QUALITY ASSURANCE OBJECTIVES

4.1 Quality Assurance Surveillance Plan (QASP) – The contractor must submit a QASP with its proposal. The QASP must define the quality requirements of the contract and the methods to ensure that these requirements are met and routinely audited and documented. The QASP must address the manufacturing process, hardware, software, installation and continued support. The QASP objective is to ensure that the quality, performance, and reliability of all products and services meet the specification requirements.

5.0 SIMULATOR PLANNING AND DEVELOPMENT

5.1 Master Integrated Schedule Plan (MISP) - The following overarching planning, documentation and reporting is required in the MISP:

• Plan for the design, development, installation, test, and qualification of the simulator system that outlines the key deliverables, milestones, and timelines.

• MISP must be updated regularly with Project Management Status Reports

(PMSR).

• MISP must discuss procedures for changes or delays and be coordinated with the contracting officer (CO) or designated FAA official.

• Technical Interchange Meetings (TIM), Preliminary Design Review (PDR), and Critical Design Review (CDR), will be critical to outline the specialized requirements for the 360ER simulator and facilitate program decisions that must be addressed in the MISP and documentation thereto.

• Key Performance Parameters (KPPs)

• Technical Performance Measures (TPMs).

5.2 Preliminary Design Review (PDR)-The contractor must conduct and support a PDR at its facility within three (3)-months after contract award and provide the MISP.

Information reviewed at the PDR must be provide 10 working-days prior to the PDR date and consist of the following documents: engineering plans, schematics and drawings, visual software plan, and logistics requirements. PDR review will include:

o Aircraft Avionics Data o Aircraft Configuration Data o Aircraft Performance Data o Aircraft Performance Checkout Data o Aircraft System Design Data o Aircraft System Checkout Data o Aircraft Wiring Data

5.3 Critical Design Review (CDR) - The contractor must conduct and support a CDR at its facility six (6) months after award. The discussion items from the PDR will be included a design baseline will be established. CDR must also include:

o Color Scheme o Instructor Software o IOS Pages o IOS Configuration o Malfunction Definition o Simulator Configuration o Ground Station

6.0 SIMULATOR PHYSICAL ATTRIBUTES OBJECTIVES

6.1 Base Simulator Requirements - Base 360ER advanced Level D aircraft simulator requirements must include dimensions and configurations for the baseline simulator.

6.2 Flight Inspection Requirements- Additional FAA 360ER simulator requirements to mimic FAA owned aircraft include at a minimum the following:

6.2.1 Ipad Mount with power source Ipad Mount with USB power source

6.2.2 ILS Offset Functionality

6.3 Mission Specialist Requirements - Potential incorporation of a Modular Mission

System (MMS) and Mission Specialist station in the back of the simulator or an off-board solution. This optional requirement may include the following:

6.3.1 Multiple observer seats available. (2 pilots, 1 instructor plus 1 or 2 observer stations minimum).

6.3.2 Customizable control screens, accessible from inside the cab and in the ‘ground station’ (control room), that can be program/office specific.

6.3.3 On board camera(s) and screen repeaters for display in the ground station (control room) that includes recording capability.

6.3.5 Two-way communication from the cab with the ground station (control room).

7.0 SIMULATOR HARDWARE OBJECTIVES

7.1 Hardware manuals must be provided using the International Air Transport

Association (IATA) Simulator Documentation Requirements ISBN 92-9035-783-5 and

Air Transport Association (ATA) Specification 100 as guidelines.

7.2 Collins Aerospace BCU-4000 and a set of five push button annunciators to allow offset ILS operations.

7.3 Level D Device

7.4 Mission Specialist Workstation

7.5 Proline Fusion Avionics Package

7.6 Autothrottle

7.7 Electric motion actuators in place of older hydraulic style

7.8 Minimum of four seats in simulator (2 in addition to the 2 pilot seats and mission specialist seat if on-board solution)

7.9 Potentially additional hardware that aligns with the FAA aircraft installed STCs.

7.10 Headset communication available at all seating positions within the FSTD.

8.0 SIMULATOR SOFTWARE OBJECTIVES

8.1 System Software Design: Where requirements cannot be met by using commercially offered software packages, the Contractor must develop the required computer software. Firmware (software that resides on programmable memory) must be treated as software. Software must be in accordance with the operating system and

COTS application manufacturer recommendations and applicable industry standards to assure compatibility with future releases of the operating system and related

COTS software applications. The Contractor must implement updates and revisions as they occur until the CDR. Data input/output capabilities must be addressed.

8.2 Required Simulator Software:

8.2.1 Upset Prevention and Recovery Training capable.

8.2.2 Installation of VN Diagram Viewer at Instructor Operating Station (IOS)

8.2.3 FMS includes flight inspection custom database.

8.2.4 Full Stall

8.2.5 Simulated navigation facility signals.

8.2.6 MMS interface with the simulator host computer providing data such as, navigation, position, and other situation data. This interface would be defined and controlled in an Interface Control Document (ICD)

8.2.7 Geo-position output for iPads.

8.2.8 Capability for integrating Electronic Flight Bag (EFB) used to display simulator position onto EFB displays.

8.2.9 Ensure ILS Offset functions properly with generated navigation signals.

8.2.10 Gusting Crosswinds NSP GB 16-02

8.2.11 Windshear NSB GB 09-04

8.2.12 Bounced Landing NSB GB17-01

8.2.13 Airframe Icing NSB GB 11-04

8.2.14 SMGCS NSB GB 12-01

8.2.15 Objective Motion Cue Test NSB GB 16-03

8.2.16 LAHSO NSB GB 18-02

8.2.17 Key airport sites representing high elevation, congested airports, US

Focus 40 airports, international airports in Europe, Middle East, and Far

East Asia, and the ability to design unique airports as needed for testing and training.

8.2.18 Ability to change airport weather, to include ceiling and visibility, rain, snow, runway contamination, braking action, and lighting associated with an airfield in daytime, dusk, and night.

8.3 Software Manuals – Software manuals must include user's guides and provide interface design specifications, software design documents, any contractor's utilities documentation, and contractor-supplied software manuals. For purposes of defining the software documentation supplied with the simulator, the software should be divided into three categories: contractor-supplied software, standard utilities software, and simulation software.

8.3.1 Contractor-Supplied Software - Contractor diagnostics applicable to the supplied computer and peripherals, the computer operating systems and any other contractor software, to include modifications thereto must be provided.

8.3.2 Standard Utilities Software - Configuring and controlling the simulator software documentation must be provided, which may include software configuration management utilities, instructor facilities compilers, radio aids station compilers, and off-line software test programs.

8.3.3 Simulation Software – Manual may include current Manual configurations in accordance with any changes to the aircraft certification: specific aircraft systems, IOS software, and foreground subroutines, equipment add-ons, engine changes, aerodynamic changes, gross weight changes and other identified configurations. Simulator computer software components must be documented in software design documents to ensure sufficient information for maintenance and modification of the software.

Malfunctions or other instructor-controlled inputs must be described.

Module interface input and output descriptions; may be higher-level meaningful descriptions indicating source, destination, and units.

Limitations imposed by system hardware, performance capabilities, etc.

9.0 SIMULATOR SITE INSTALLATION

9.1 Site Plan - The site plan will be incorporated into the contract and must document, at minimum, the government and contractor’s responsibilities, arrangements for hours of work, access to work areas, and supporting workshop facilities. After Government approval of the Site Plan, the contractor must perform site preparations in accordance with the government approved plan.

9.2 Initial Location of Equipment/Scale Drawing - A preliminary installation drawing must be submitted with the contractor's proposal. This drawing must illustrate where the contractor proposes to locate major pieces of equipment and the equipment room.

9.3 Installation Drawings - The contractor must provide installation data for Government approval. The data must include plans showing equipment layout and weight distribution data, dimensions, power distribution, grounding, floor loading, cooling water supply points and requirements, breathing air supply points and requirements, and air-conditioning recommendations. The drawings or supporting documentation should address operating envelope, and safety margins.

9.4 Installation Site Survey - Contractor must conduct a site survey of the Government's simulator building prior to the commencement of installation and may perform a site survey prior to completion of installation drawings. The contractor is to provide any necessary advice to the government on the final preparation of the simulator building, and to discuss and confirm arrangements for the installation program.

9.5 Site Readiness Review and Report - The contractor must conduct Site Readiness

Review (SRR) at least 20 working days prior to equipment installation to ensure that the site has been prepared in accordance with the Site Plan for equipment installation and checkout. At the conclusion of the SRR, the contractor must submit a

SRR report documenting remaining and new action items that need to be completed before system installation.

9.6 Simulator Installation - The Contractor must perform all activities necessary to package, ship, deliver, install, and test the simulator. In addition, the Contractor must ensure that the installation activities are coordinated with the Contracting Officer's

Representative (COR) prior to installation to minimize the construction impact on the site. Prior to the installation of the simulator, the contractor's installation team must perform all necessary installation preparatory work unless it is agreed that it is a government responsibility as detailed in the approved SRR. The contractor must remove all debris from the site following site preparation and installation activities.

10.0 INSPECTION AND ACCEPTANCE

10.1 Simulator Validation -The simulator validation must be performed in three stages.

First, the contractor must validate the simulator at its plant; second, the simulator may be accepted at the contractor's plant (in-house acceptance) by a FAA designated official; and third, the simulator must be accepted at the FAA's site by a

FAA designated official.

The contractor must submit at proposal a draft Acceptance Test Procedures (ATPs) and a Malfunction Checkout Document (MCD) to be finalized at CDR. The ATPs must demonstrate how they satisfy assigned technical, functional, and operational requirements in the software/hardware integrated environment of the simulated aircraft. The MCD must consist of a series of tests specifying the cause, the injected failure, the effect, the setup steps, and confirmation test method for the individual malfunctions. These tests and other contractor identified tests must be documented.

10.2 Contractor Validation - The contractor must validate the simulator to thoroughly check each system. The integrated simulator performance is then verified using

ATPs, MCD or other contractor identified tests. All defects must be identified, and all corrective actions confirmed.

10.3 In-Plant Acceptance - Upon completion of the contractor validation, the simulator must be offered to the Government for in-plant acceptance testing. The simulator will be tested using the same methods as mentioned in the contractor validation and may include additional tests required by the Government acceptance official. The government acceptance official may provide the in-plant acceptance once acceptance testing is documented and satisfactory.

10.4 On-Site Acceptance - The Government may conduct independent operational evaluation and testing at the contractor's facilities and again following delivery and installation at the FAA facility. Any additional testing not included in the contractor's testing documentation may be added before simulator validation.

11.0 LOGISTICS OBJECTIVES

Logistics objectives consist of contractor services to maintain and update the installed simulator to industry and government continually evolving requirements. Logistics support must assist the

Government in achieving maximum operational benefits from the simulator and must consist of the following:

11.1 Maintenance Support - The contractor must provide ongoing and preventative maintenance support. The contractor must be capable of dispatching engineering and technical support personnel to the Mike Monroney Aeronautical Center, Oklahoma City, if there are maintenance issues to the simulator or supporting systems that require remedy. The contractor must have access to provide parts for maintenance events, including emergency support. The contractor is to provide any support equipment required for the ongoing maintenance support required.

11.2 Technical Support - The contractor must provide ongoing technical support. The contractor must provide troubleshooting support for simulator operations 365/24/7.

The contractor must provide support when updates to the simulator are required for updated regulatory requirements, OEM directives, new aircraft systems, and simulator modernization.

11.3 Technical Publications - The contractor is to provide any technical publications that the government needs to support daily operations of the simulator which may include the following: instructor operating manual, hardware manual, general operating manual, software manuals, maintenance operating manual, preventative maintenance manual, fault isolation manual, schematics, assembly documentation, specification documentation.

11.4 Training - The contractor must provide Government approved training for preventative maintenance and instructor personnel to enable the operation and preventative maintenance of the simulator.

11.5 Engineering Support - Engineering support must include support of the hardware and software whereby OEM directed update, regulatory guidance or government requirements dictate a change in the configuration of the simulator. This may include disciplines such as visual software modeling, source code changes, or any other support requiring engineering to update the simulator.

11.6 Configuration Management - The contractor may use an internal CM system for the control of all configuration documentation, software, physical media, and physical parts representing or comprising the simulator. Contractor must maintain liaison with the aircraft OEM to ensure the FSTD is updated on any configuration updates or airworthiness directives. The contractor must request a waiver for any deviation from the approved design baseline established at CDR.

12.0 DATA DELIVERABLES

CDRL # DESCRIPTION CDRL DUE

TBD