System and method for adjusting engine power settings for minimum equipment list release

Abstract

This disclosure relates to systems and methods for adjusting engine power settings for minimum equipment list release. An aircraft includes one or more processors configured to receive input identifying a first equipment item as failed. The one or more processors are configured to select adjustment factors to be applied during engine performance calculations for a specific planned flight of the aircraft based on the input identifying the first equipment item as failed. The one or more processors are configured to determine a set of engine performance planning metrics for the specific planned flight based on the adjustment factors and environmental condition data associated with the aircraft. The one or more processors are configured to determine a weight penalty, fuel penalty, or both for the specific planned flight based on the set of engine performance planning metrics.

Description

Technical Field

[0001] This disclosure generally relates to aircraft engine control systems, and more specifically to systems and methods for automatically adjusting engine power settings during releases with failed equipment items. Background Technology

[0002] In aircraft operation, aircraft are often released even when certain equipment items fail. When operating with failed equipment items, the impact on engine performance must be considered through adjustments to engine power settings and performance calculations.

[0003] Traditional methods for managing failed device items associated with engine performance impacts rely on manually applied factors. These factors are used to modify nominal aircraft performance calculations to account for the effects of failed components on engine thrust output, fuel flow, and exhaust temperature. The manual application of these factors introduces operational complexity and can lead to overly conservative performance penalties applied at different stages of flight.

[0004] Current methods require flight crews to consult multiple operational documents to determine appropriate performance adjustments. These adjustments typically vary based on flight phase, environmental conditions, and failed components. The potential for multiple component failures (each with a significant impact on engine performance) further complicates the issue. Furthermore, existing methods may require mandatory power settings that reduce or increase the complexity of flight operations.

[0005] An improved method for managing such failed equipment items would enhance aircraft performance, improve crew effectiveness, or both. Summary of the Invention

[0006] According to one implementation of this disclosure, an aircraft includes: one or more processors configured to receive input identifying a first device item as faulty. The one or more processors are configured to select adjustment factors to be applied during engine performance calculations for a specific planned flight of the aircraft based on the input identifying the first device item as faulty. The one or more processors are configured to determine a set of engine performance planning metrics for the specific planned flight based on the adjustment factors and environmental condition data associated with the aircraft. The one or more processors are configured to determine a weight penalty, a fuel penalty, or both for the specific planned flight based on the set of engine performance planning metrics.

[0007] According to another implementation of this disclosure, an aircraft includes: one or more processors configured to receive input identifying a first device item as failed. The one or more processors are configured to: select an adjustment factor associated with the failure state of the first device item based on the input. The one or more processors are configured to calculate a set of engine performance planning metrics for the planned flight based on the adjustment factor and environmental condition data associated with a planned flight path. The one or more processors are configured to determine a weight penalty, a fuel penalty, or both for the planned flight based on the set of engine performance planning metrics.

[0008] According to another implementation of this disclosure, a method includes receiving input identifying a first equipment item as failed. The method further includes: selecting an adjustment factor associated with the failure state of the first equipment item based on the input. The method further includes: calculating a set of engine performance planning metrics for the planned flight based on the adjustment factor and based on environmental condition data associated with a planned flight path. The method further includes determining a weight penalty, a fuel penalty, or both for the planned flight based on the set of engine performance planning metrics.

[0009] The features, functions, and advantages described herein can be implemented independently in various ways or combined in other ways, further details of which can be found in the following description and figures. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating a system for generating adjusted engine power settings and performance calculations for aircraft operating with faulty equipment items.

[0011] Figure 2 To illustrate, as shown by Figure 1 The flowchart illustrates an example of the operation performed by the device, which is to generate engine power settings and performance calculations for the aircraft to utilize the failed device item operation.

[0012] Figure 3 It shows that, as Figure 1 The flowchart illustrates an example of an operation performed by a device in order to generate engine power settings and performance calculations for an aircraft that utilizes the failed device item operation.

[0013] Figure 4 It shows the result of Figure 1 The flowchart illustrates an example of an operation performed by a device in order to generate engine power settings and performance calculations for an aircraft that utilizes the failed device item operation.

[0014] Figure 5It is a flowchart of a method for generating engine power settings and performance calculations for aircraft operating with failed equipment items.

[0015] Figure 6 It shows including Figure 1 A flowchart illustrating an example of the lifecycle of an aircraft device; Figure 7 It shows including Figure 1 A block diagram illustrating aspects of the equipment used in the aircraft.

[0016] Figure 8 This is a schematic diagram of the electronic components of a system that generates adjusted engine power settings and performance calculations for aircraft operating with failed components. Detailed Implementation

[0017] As aircraft systems become increasingly complex, inefficiencies associated with aircraft performance and crew effectiveness are becoming more pronounced due to traditional methods used to manage the engine performance impacts associated with failed equipment items. These inefficiencies can be reduced or minimized by managing the sum of the engine performance impacts associated with failed equipment items. Such a method should be able to automatically calculate appropriate power setting adjustments while taking into account changes in flight conditions and aircraft configuration throughout the flight.

[0018] The aspects disclosed herein provide systems and methods for adjusting engine power settings when an aircraft with a failed equipment item is released for operation. This system achieves more efficient aircraft operation by calculating and implementing appropriate engine performance adjustments, rather than relying on manual calculations and conservative estimates.

[0019] The system operates by integrating Minimum Equipment List (MEL) related calculations across multiple aircraft computers and systems. When the crew identifies a failed equipment item, they can select it via a switch in the cockpit or through the aircraft's display screen. The system then automatically calculates how the failed equipment item affects engine performance. For example, it determines how much the engine power settings should be adjusted to accommodate changes in engine temperature and fuel consumption. These calculations take into account various factors such as altitude, temperature, and other environmental conditions that affect engine performance.

[0020] To effectively handle different phases of flight, the system adjusts its calculations throughout the flight. During takeoff, the system calculates a set of adjustments to ensure the aircraft has the appropriate performance for departure. During climb and cruise, the system automatically updates these calculations to match changing flight conditions. This provides appropriate engine performance settings without requiring manual adjustments by the crew or consulting multiple reference documents.

[0021] The system can also handle situations where multiple device items fail simultaneously. Instead of requiring separate calculations for each device item, the system combines these effects and determines the appropriate overall adjustments. This helps ensure accurate performance calculations, even in complex situations where traditional manual methods might be particularly challenging.

[0022] By using the technologies and systems described herein, aircraft can achieve more precise and efficient engine operation. The automated system can calculate performance adjustments in seconds, rather than requiring time-consuming manual calculations. The adjustments are more accurate because the system continuously updates its calculations based on actual flight conditions, unlike manual methods that typically use simplified assumptions. The system also reduces operational complexity by automating these adjustments instead of requiring the crew to follow multiple manual procedures. These improvements enhance aircraft performance and reduce crew workload while ensuring safe operation throughout the flight.

[0023] The accompanying drawings and the following description illustrate specific exemplary embodiments. It should be understood that those skilled in the art will be able to design various arrangements, although not explicitly described or shown herein, that embody the principles described herein and are included within the scope of the claims following this description. Furthermore, any examples described herein are intended to aid in understanding the principles of this disclosure and are not to be construed as limiting. Therefore, this disclosure is not limited to the specific embodiments or examples described below, but is defined by the claims and their equivalents.

[0024] The specific implementation is described herein with reference to the accompanying drawings. Throughout the description, common features are indicated by common reference numerals. In some drawings, multiple instances of a particular type of feature are used. Although these features are physically and / or logically different, the same reference numerals are used for each feature, and different instances are distinguished by the addition of letters to the reference numerals. When a feature is referred to herein as a group or type (e.g., when a specific feature within a group of features is not mentioned), reference numerals are used without distinguishing letters. However, when referring herein to a specific feature among multiple features of the same type, reference numerals are used along with distinguishing letters.

[0025] As used herein, different terms are used only for the purpose of describing a particular implementation and are not intended to be restrictive. For example, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are intended to also include the plural forms. Furthermore, some features described herein are singular in some implementations and plural in others. For illustration, Figure 8 It describes a system that includes one or more processors ( Figure 8The term "processor" (820) refers to a computing device 810, indicating that in some implementations, the computing device 810 includes a single processor 820, and in other implementations, the computing device 810 includes multiple processors 820. For ease of reference herein, this feature is generally introduced as "one or more" features and is subsequently referred to in the singular or optional plural form (as generally indicated by "(s)"), unless an aspect associated with multiple features is described.

[0026] The terms “comprise,” “comprises,” and “comprising” are used interchangeably with “include,” “includes,” or “including.” Furthermore, the term “wherein” is used interchangeably with the term “where.” As used herein, “exemplary” indicates an example, implementation, and / or aspect, and should not be construed as limiting or indicating a preference or preferred implementation. As used herein, ordinal terms used to modify elements (such as structures, components, operations, etc.) (e.g., “first,” “second,” “third,” etc.) do not themselves indicate any priority or order of that element relative to another element, but merely distinguish that element from another element with the same name (but for the use of ordinal terms). As used herein, the term “group / set” refers to a grouping of one or more elements, and the term “multiple” refers to multiple elements.

[0027] As used herein, the terms “generate,” “calculate,” “use,” “select,” “access,” and “determine” are interchangeable unless the context otherwise indicates. For example, “generate,” “calculate,” or “determine” a parameter (or signal) can refer to actively generating, calculating, or determining a parameter (or signal) or can refer to using, selecting, or accessing a parameter (or signal) that has already been generated, such as through another component or device. As used herein, “connection” can include “communication connection,” “electrical connection,” or “physical connection,” and may also (or alternatively) include any combination thereof. Two devices (or components) can be directly or indirectly connected (e.g., communication connection, electrical connection, or physical connection) via one or more other devices, components, wires, buses, networks (e.g., wired networks, wireless networks, or combinations thereof). Two electrically connected devices (or components) can be in the same or different devices and can be connected via electronics, one or more connectors, or inductive coupling, as illustrative and non-limiting examples. In some implementations, two devices (or components) connected in a communication manner (e.g., by electrical communication) may directly or indirectly send and receive electrical signals (digital or analog signals), for example, via one or more wires, buses, networks, etc. As used herein, "direct connection" is used to describe two devices connected (e.g., a communication connection, an electrical connection, or a physical connection) without any intermediate components.

[0028] Figure 1 This diagram illustrates a system 100 including an aircraft 138, which includes a device 102. Device 102 is configured to generate adjusted engine power settings and performance calculations (e.g., data 126) for the aircraft 138 operating with a failed device item. System 100 includes a memory 104 coupled to one or more processors (shown as processor 136). Memory 104 includes instructions 106 and several categories of data, including environmental condition data 108, normal operation data 110, MEL operation data 112, and multiplier data 114.

[0029] Environmental condition data 108 includes baseline aircraft performance data, such as engine thrust ratings, fuel flow characteristics, exhaust gas temperature limits, or combinations thereof. In some aspects, environmental condition data 108 further includes pressure altitude, temperature, airspeed, or barometric altitude, or combinations thereof. Environmental condition data 108 includes information used in performance calculations and represents the characteristics of aircraft 138 during normal operation.

[0030] Normal operating data 110 includes performance data for standard aircraft operation, including a basic power setting table, thrust management parameters, environmental correction factors, or combinations thereof. Normal operating data 110 may be provided to the power setting calculator 118 of processor 136 to establish a basic power setting before applying any adjustments required due to failed equipment items.

[0031] MEL Operation Data 112 includes reference data defining operating procedures, limitations, and adjustments associated with equipment items that may fail. MEL Operation Data 112 includes information defining which equipment items may fail, associated operating limitations, performance adjustments required for each failed equipment item, or combinations thereof. MEL Operation Data 112 may also include combined impact data for scenarios where multiple equipment items fail simultaneously.

[0032] Multiplier data 114 includes adjustment factors used to modify engine power settings and performance calculations when the aircraft 138 operates using failed equipment items. These adjustment factors correspond to adjustment factor indices from multiplier data 114. Furthermore, these adjustment factors are used to adjust the base power settings based on the impact of failed equipment items on engine performance under different flight phases and environmental conditions.

[0033] Processor 136 includes a Minimum Equipment List (MEL) status manager 116, a power setting calculator 118, and a performance calculator 120. These components work together to implement methods for adjusting engine power settings and calculating the performance impact caused by the aircraft 138 using faulty equipment.

[0034] System 100 also includes an input device 132 configured to send input data 134 to MEL Status Manager 116. For example, input data 134 may identify one or more device items as failed. Input device 132 may include a Control Display Unit (CDU), one or more switches on the aircraft's top panel, or both. MEL Status Manager 116 processes input data 134 and generates data 122 indicating which device items are currently failed. When multiple device items fail simultaneously, MEL Status Manager 116 determines an appropriate combination adjustment factor that takes into account the combined effects of the different failed device items. According to some embodiments, MEL Status Manager 116 is configured to control the operation of Power Setting Calculator 118 and Performance Calculator 120 to generate the resulting data 126, as further explained below.

[0035] The resulting data 126 is routed to device 128, such as a display device for crew interface or an electronic engine controller (EEC) for direct thrust management. For example, depending on whether device 128 is implemented as a display device or as an EEC for direct thrust management, the resulting data 126 may be routed to a display device functional unit or an engine control functional unit of device 128.

[0036] Power setting calculator 118 receives data 122 and is configured to calculate power setting adjustments. In this example, power setting calculator 118 first retrieves a base power setting from normal operating data 110, and then selects appropriate adjustment factors from multiplier data 114 using the current state of any failed device items (e.g., data 122). Power setting calculator 118 applies these adjustment factors to the base power setting to generate the adjusted power setting. In this example, at least a portion of the calculations performed by power setting calculator 118 incorporates environmental condition data 108, including pressure altitude, temperature, airspeed, barometric altitude, or combinations thereof. Power setting calculator 118 generates data 124, which contains the adjusted power setting and optional related performance parameters.

[0037] According to one aspect, the power setting calculator 118 performs power setting adjustments integrated with existing thrust management logic. When an equipment item becomes faulty and the MEL status manager 116 receives a corresponding input identifying the condition, the power setting calculator 118 determines adjustment factors for different flight phases. These adjustment factors enable enhanced engine performance compared to conventional factors that are not based on specific environmental conditions and therefore impose a more conservative margin. For example, when the MEL status manager 116 identifies a faulty equipment item in the propulsion system, the power setting calculator 118 selects an adjustment factor corresponding to that specific faulty equipment item. The power setting calculator 118 then integrates this adjustment factor into the thrust management calculation chain, modifying the base power setting in conjunction with environmental corrections to determine the final adjusted power setting.

[0038] Performance calculator 120 receives both the current status of the failed equipment item (e.g., data 122) and the adjusted power settings (e.g., data 124) to determine the performance impact at different stages of flight. Performance calculator 120 uses environmental condition data 108 and the adjusted power settings to calculate various performance metrics, including weight penalties and fuel penalties. Performance calculator 120 generates data 126 containing the final performance calculations.

[0039] System 100 also includes storage device 130 and device 128. Storage device 130 receives and stores data 126 for record-keeping purposes. Device 128 may be implemented as, for example, a display device for presenting adjusted performance parameters and associated operational restrictions on crew members, or as an EEC for implementing adjusted power settings. When implemented as a display device, device 128 may be configured to receive input from crew members to confirm the adjusted performance parameters. When implemented as an EEC, device 128 may be configured to automatically implement adjusted power settings without crew member confirmation.

[0040] During operation, when the crew identifies a failed equipment item during pre-flight checks, the crew inputs the status via input device 132, which may include a CDU interface or a dedicated MEL switch (e.g., on the overhead panel). The MEL status manager 116 receives the input data 134 and processes it to determine the appropriate performance adjustments to be applied to the failed equipment item.

[0041] Using multiplier data 114, the MEL Status Manager 116 selects adjustment factors based on the impact of the failed equipment item on engine performance. During each flight phase, the MEL Status Manager 116 provides the selected adjustment factors to the Power Setting Calculator 118, which applies these adjustment factors based on current flight conditions to determine an appropriate power setting. For example, during takeoff, the Power Setting Calculator 118 combines the adjustment factors with actual airport environmental conditions to determine an appropriate thrust setting that maintains safe operation under the failed equipment item. The MEL Status Manager 116 generates data 122 indicating the adjustment factors and sends data 122 to the Power Setting Calculator 118.

[0042] The power setting calculator 118 receives data 122 and applies these adjustment factors to the base power setting obtained from normal operating data 110, while incorporating real-time environmental condition data 108, including pressure altitude, temperature, airspeed, barometric altitude, or combinations thereof. These parameters ensure accurate power setting adjustments under various flight conditions. In an illustrative example, the power setting calculator 118 combines the adjustment factors with current airport environmental conditions to determine an appropriate thrust reduction based on the failed equipment and real-time environmental condition data 108. The power setting calculator 118 generates data 124, which contains the power setting adjusted to maintain engine operating margins while taking into account the state of the failed equipment.

[0043] Performance calculator 120 uses these adjusted power settings to calculate operational effects, including modified weight limits, adjusted thrust levels, updated fuel flow forecasts, and modified engine operating margins. For example, performance calculator 120 determines a weight penalty based on reduced thrust availability and calculates the increased fuel flow requirement due to reduced engine efficiency. Performance calculator 120 generates data 126 containing the parameters and limits of the entire set of adjustments. Data 126 can be sent to both storage device 130 for flight data recording and device 128 for display to the crew or for direct implementation via the engine controller.

[0044] In some implementations, when device 128 is implemented as an EEC (Electronic Control Center), the system incorporates an automatic mode for implementing performance parameter adjustments. In this mode, once a device item is identified as faulty and initial calculations are performed, device 102 continuously updates the power settings based on actual flight conditions. These real-time adjustments are automatically transmitted to device 128 for implementation during each flight phase, with the modified performance parameters being sent to the flight management computer. In other implementations, when device 128 is implemented as a display device, the system introduces a manual confirmation mode, where device 128 presents the adjusted parameters and requires crew confirmation before implementation. After confirmation, these parameters are sent for execution.

[0045] In the distributed computing implementation, different components of device 102 are implemented across multiple aircraft systems. Power setting calculations can be performed within the EEC, while performance calculations are handled by the Flight Management Computer (FMC). This architecture ensures robust system redundancy while enabling real-time parameter adjustments throughout the flight phase.

[0046] By using the techniques and systems described herein, device 102 provides the following technical advantages: automatic, accurate, and consistent power setting adjustment when operating with a failed equipment item. System 100 uses real-time calculations based on actual flight conditions and provides a significant improvement over existing manual adjustment methods by minimizing potential calculation errors and reducing operational complexity.

[0047] Furthermore, device 102 provides enhanced operational efficiency through its comprehensive multi-system approach. Device 102's ability to simultaneously handle multiple failed equipment items, combined with its automated implementation of adjustments across different flight phases, ensures proper performance calculations while reducing crew workload. This systematic approach eliminates the need for manual calculations and reduces the risk of incorrect performance adjustments.

[0048] Device 102 also offers the technical advantages of dynamic performance management through its continuous computing capabilities. By implementing a comprehensive calculation method that takes into account changing flight conditions, system 100 enables the aircraft and the airline to maintain consistent performance optimization throughout the entire flight envelope. The ability to automatically adjust calculations based on both the status of failed equipment items and environmental condition data 108 further ensures smooth aircraft operation while maintaining appropriate performance limits.

[0049] Figure 2 This is a flowchart 200 illustrating an example of an automatic engine power setting adjustment operation performed by device 102 to implement a Minimum Equipment List (MEL) release operation. Device 102... Figure 1 The various components described herein (including memory 104, processor 136, MEL status manager 116, power setting calculator 118, and performance calculator 120) perform these operations.

[0050] At box 202, the process begins upon receiving input data 134 that identifies a first device item as faulty. The crew can input this selection via multiple interfaces, including input device 132, which may include a control display unit (CDU) or a dedicated switch on the top panel of the aircraft 138. For example, if a device item affecting engine performance becomes faulty, the crew can select that first device item via any interface.

[0051] In box 204, the MEL state manager 116 determines, based on input data 134, whether two device items are identified as failed. This determination allows device 102 to handle scenarios where multiple device items may fail simultaneously, and this state is recorded in data 122. For example, device 102 can handle both a failed device item associated with the propulsion system and a failed device item associated with the environmental control system.

[0052] In box 206, if two equipment items are identified as failed, the power setting calculator 118 selects an adjustment factor from the multiplier data 114 corresponding to an adjustment factor index of 2. This adjustment factor represents a combined adjustment factor that considers the effects of multiple failed equipment items. The combined value specifically addresses the effects of two failed equipment items rather than simply combining individual adjustment factors.

[0053] In box 208, if two or more device items are not determined to be failed, the MEL status manager 116 checks whether a single device item is identified as failed. This check represents the basic situation for handling a single failed device item.

[0054] In box 210, if a device item is identified as failed, the power setting calculator 118 selects an adjustment factor from the multiplier data 114 corresponding to an adjustment factor index of 1. This selection indicates the adjustment factor that will be applied during engine performance calculations for a specific planned flight. For example, if a single device in the propulsion system fails, the adjustment factor value is selected based on the known effects of operating without that device in the propulsion system.

[0055] In box 212, if no device item is identified as faulty, the power setting calculator 118 selects an adjustment factor from the multiplier data 114 corresponding to adjustment factor index = 0. The selected adjustment factor represents normal operation that does not require adjustment.

[0056] In box 214, the power setting calculator 118 routes the selected adjustment factor as output as data 124. This routing enables device 102 to calculate engine performance planning metrics based on the selected value and current environmental condition data 108, including pressure altitude, temperature, airspeed, barometric altitude, or combinations thereof.

[0057] At box 216, the performance calculator 120 includes the adjustment factor value as part of data 126, as well as... Figure 1 The adjusted engine power settings and performance calculations described herein are output together. This output is fed into performance calculations that determine operational impacts. These impacts include modifications to operational weight limits at various flight phases, including adjustments to the maximum permissible takeoff weight, modifications to the route climb weight limit, and updates to the landing weight limit. Device 102 can also calculate fuel-related impacts, determining both baseline planned fuel requirements and any additional diversion fuel reserve requirements needed for failed equipment item conditions.

[0058] In box 218, device 102 sends an adjustment factor corresponding to a specific failed equipment item to the Electronic Engine Controller (EEC). This adjustment factor is selected from multiplier data 114 based on the impact of the specific failed equipment item on engine performance. During flight operations, the EEC implements this adjustment by modifying the base power setting according to both the adjustment factor and environmental conditions. This implementation ensures proper engine operation while taking into account any failed equipment items.

[0059] Flowchart 200 implements a systematic approach to address failed equipment items and calculate appropriate power setting adjustments. When the system receives additional environmental condition data 108, including pressure altitude, temperature, airspeed, barometric altitude, or combinations thereof, the system uses the additional environmental condition data 108 and adjustment factors from multiplier data 114 to determine a final set of engine performance planning metrics. The automated nature of these calculations and adjustments reduces operator workload while ensuring accurate performance impact at each stage of flight.

[0060] Device 102 is capable of calculating and implementing performance impacts when flight conditions change. For example, during takeoff, the system can automatically consider airport altitude and temperature from environmental condition data 108, while applying appropriate adjustments for any failed equipment items based on data from MEL operational data 112. During climb, the system continues to adjust performance calculations based on changing atmospheric conditions while maintaining necessary limits. The resulting data 126 can be stored in storage device 130 and processed by device 128, which, when implemented as a display device, provides a crew interface, or, when implemented as an electronic engine controller, directly implements thrust adjustments.

[0061] Figure 3 This is a flowchart 300 illustrating an example of an operation performed by device 102 to calculate and combine the power setting effects of normal operation and operation with failed device items. Device 102 via Figure 1 The various components described herein (including memory 104, processor 136, MEL status manager 116, power setting calculator 118, and performance calculator 120) perform these operations.

[0062] At frame 302, device 102 receives environmental condition data 108. Environmental condition data 108 includes environmental condition information such as pressure altitude, temperature, airspeed, barometric altitude, or combinations thereof, as well as current aircraft configuration parameters that affect engine performance calculations.

[0063] At box 304, device 102 accesses the normal operating power setting data table stored in normal operating data 110. This table includes baseline engine performance data representing standard aircraft operation under conditions of no equipment failures. Normal operating data 110 includes a basic power setting table, thrust management parameters, and environmental correction factors.

[0064] In box 306, the power setting calculator 118 calculates the normal operating power setting. This calculation combines the received environmental condition data 108 with baseline performance parameters to determine a standard thrust setting that will be applicable to the current flight conditions during normal operation.

[0065] In box 308, in parallel with normal operation calculations, device 102 accesses the MEL power setting data table from MEL operation data 112. This table includes adjustment factors and performance data associated with potentially malfunctioning device items. MEL operation data 112 provides the information needed to modify engine performance calculations when a device item is identified as malfunctioning.

[0066] In box 310, the power setting calculator 118 calculates the power setting effect based on any failed equipment item. Using data from MEL operating data 112 and multiplier data 114, the power setting calculator 118 determines the required performance adjustments. For example, if an equipment item in the propulsion system fails, the power setting calculator 118 calculates the appropriate thrust reduction based on the effect of operating without that equipment item.

[0067] In box 312, the power setting calculator 118 applies an adjustment factor from the multiplier data 114. This adjustment factor represents an adjustment that takes into account the impact of failed device items. As indicated by data 122 in the MEL status manager 116, the adjustment factor may reflect the impact of a single failed device item or the combined impact of multiple failed device items.

[0068] In box 314, the performance calculator 120 combines the power setting effects from two calculation paths. This combination integrates the baseline normal operating power setting with adjustments for any failed device items to generate data 124.

[0069] In box 316, performance calculator 120 outputs the final power setting as data 126. Performance calculator 120 sends data 126 to storage device 130 and device 128. The final setting represents the adjusted engine power setting to be implemented by the electronic engine controller (EEC). The final setting maintains appropriate operating margins while taking into account environmental conditions and failed equipment items.

[0070] Flowchart 300 implements a dual-path calculation method, which ensures accurate power settings when operating with the failed device item. Parallel processing of normal operation data 110 and MEL operation data 112 allows device 102 to maintain control of baseline performance capabilities while applying necessary adjustments. This automated calculation process eliminates the need for manual adjustments and reduces the possibility of human error in determining appropriate power settings.

[0071] Device 102 enables precise control of engine performance throughout all phases of flight through the coordinated operation of the MEL Status Manager 116, Power Setting Calculator 118, and Performance Calculator 120. For example, during takeoff, device 102 automatically integrates airport environmental conditions from Environmental Conditions Data 108 with necessary adjustments for any failed equipment items as defined in MEL Operational Data 112 to calculate appropriate thrust settings. During climb and cruise phases, device 102 continues to update these calculations to maintain performance while adhering to environmental and operational limitations. These updates are processed by device 128, which either displays the updated parameters to the crew or directly implements thrust adjustments, depending on whether it is implemented as a display device or an electronic engine controller.

[0072] Figure 4 This is a flowchart 400 illustrating an example of an operation performed by device 102 to calculate and combine the performance impact of both normal operation and Minimum Equipment List (MEL) release conditions. Device 102 via... Figure 1 The various components described herein (including memory 104, processor 136, MEL status manager 116, power setting calculator 118, and performance calculator 120) perform these operations.

[0073] At box 402, the power setting calculator 118 receives environmental condition data 108. The environmental condition data 108 includes information such as pressure altitude, temperature, airspeed, barometric altitude, or combinations thereof, as well as current aircraft configuration parameters that affect engine performance calculations.

[0074] In box 404, the power setting calculator 118 accesses the normal operating performance data table stored in normal operating data 110. This table includes baseline engine thrust and fuel flow data representing standard aircraft operation when all equipment items are running. Normal operating data 110 includes a basic performance table, thrust management parameters, and environmental correction factors.

[0075] In box 406, the power setting calculator 118 calculates normal operating performance. This calculation combines the received environmental condition data 108 with baseline performance parameters to determine the standard thrust and fuel flow settings applicable to the current flight conditions during normal operation.

[0076] In box 408, in parallel with normal operation calculations, the power setting calculator 118 accesses the MEL performance data table from the MEL operation data 112. This table includes adjustment factors and performance data associated with potentially failing equipment items. When an equipment item is identified as failing, multiplier data 114 provides information to modify the performance calculations.

[0077] At box 410, the power setting calculator 118 calculates the performance impact of any failed device item. Using data from MEL operating data 112 and multiplier data 114, the power setting calculator 118 determines the performance adjustment based on the status indicated by data 122 from MEL status manager 116.

[0078] In box 412, the power setting calculator 118 applies an adjustment factor from multiplier data 114. This adjustment factor represents an appropriate adjustment to account for the effects of operating with failed device items. As indicated by data 122 from MEL status manager 116, this adjustment factor can reflect the effect of a single failed device item or the combined effect of multiple failed device items.

[0079] In box 414, the performance calculator 120 combines the performance effects from two calculation paths. This combination integrates baseline normal operating performance with adjustments for any failed equipment items to produce a comprehensive thrust and fuel flow setting that takes into account both current flight conditions and equipment status to generate data 124.

[0080] At box 416, performance calculator 120 outputs the final thrust and fuel flow settings as data 126. Performance calculator 120 sends data 126 to storage device 130 and device 128. The final thrust and fuel flow settings represent engine performance parameters that can be adjusted by the electronic engine controller (EEC). This setting takes into account both environmental conditions and MEL limits.

[0081] Flowchart 400 implements a dual-path calculation method to determine thrust and fuel flow settings during operation using failed equipment items. For example... Figure 4 As shown, when the MEL status manager 116 identifies a failed device item, the power setting calculator 118 and performance calculator 120 process the adjustment via parallel paths. The first path processes the normal operating data 110 via the power setting calculator 118, while the second path processes the MEL operating data 112 to determine the appropriate adjustment. During thrust calculation, the power setting calculator 118 incorporates the adjustment factor after environmental correction but before calculating the final thrust setting limit, and this adjusted thrust setting is transmitted to the electronic engine controller (EEC).

[0082] Performance calculator 120 coordinates these adjustments with other thrust management functions to maintain engine operating limits. The coordinated operation of MEL Status Manager 116, Power Setting Calculator 118, and Performance Calculator 120 allows for continuous thrust and fuel flow calculations throughout all phases of flight. During takeoff, these components integrate airport environmental conditions from Environmental Conditions Data 108 with adjustments for any failed equipment items from MEL Operational Data 112. As the aircraft 138 climbs and cruises, Performance Calculator 120 updates these calculations based on changing atmospheric conditions while maintaining operating limits.

[0083] Figure 5 A method 500 is shown for generating adjusted engine power settings and performance calculations for operating an aircraft 138 using a failed device item. Method 500 includes, at block 502, receiving input (e.g., input data 134) that identifies a first device item as failed. For example, MEL status manager 116 receives input via input device 132, such as a selection on a control display unit (CDU) or activation of a switch on a top panel, thereby indicating a failed device item.

[0084] Method 500 includes: in block 504, selecting an adjustment factor associated with the failure state of a first device item based on the input. For example, power setting calculator 118 accesses multiplier data 114 to select an adjustment factor corresponding to the identified failed device item. When multiple device items fail, power setting calculator 118 selects a combined adjustment factor that takes into account the effects of interactions between the failed device items.

[0085] Method 500 includes, at block 506, calculating a set of planned engine performance metrics for the planned flight based on adjustment factors and environmental condition data associated with the planned flight path. For example, performance calculator 120 processes environmental condition data 108 and selected adjustment factors to determine adjusted thrust settings and fuel flow rates for different phases of flight. Environmental condition data includes temperature, pressure altitude, airspeed, barometric altitude, or combinations thereof. Performance calculator 120 generates data 124 containing performance parameters that incorporate these adjustments.

[0086] Method 500 includes: in block 508, determining a weight penalty, fuel penalty, or both, for the planned flight based on a set of engine performance planning metrics. For example, performance calculator 120 analyzes data 124 to calculate operational limitations, including: reduced takeoff weight limits under failed equipment items to maintain the required climb angle; increased fuel reserves to account for reduced engine efficiency; and modified landing weight limits. Performance calculator 120 generates data 126 containing these penalties and sends them to storage device 130 and device 128 for crew reference.

[0087] Figure 6 It shows including Figure 1 A flowchart of an exemplary method 600 for the lifecycle of the aircraft 102 is provided. In the pre-production process, at block 602, the exemplary method 600 includes the specifications and design of the aircraft. During the specification and design phase, method 600 may include the specifications and design of the equipment 102 and the location where the equipment 102 will be placed. At block 604, method 600 includes material procurement, which may include procuring materials for the equipment 102 or procuring pre-assembled equipment 102.

[0088] During production, method 600 includes: component and sub-component manufacturing at block 606, and system integration of the aircraft at block 608. For example, method 600 may include component and sub-component manufacturing of device 102, system integration of device 102 with the aircraft, or both. At block 610, method 600 includes aircraft certification and delivery, and at block 612, putting the aircraft into service. Certification and delivery may include certifying device 102 to put it into service. When used by a customer, routine maintenance and servicing of the aircraft may be scheduled (which may also include modification, reconfiguration, refurbishment, etc.). At block 614, method 600 includes performing maintenance and servicing on the aircraft, which may include performing maintenance and servicing on device 102. For example, maintenance and servicing may include replacing one or more computer components included in device 102.

[0089] Each process of method 600 may be performed or implemented by a system integrator, a third party, and / or an operator (e.g., a customer). For the purposes of this description, a system integrator may include, but is not limited to, any number of aircraft manufacturers and main system subcontractors; a third party may include, but is not limited to, any number of vendors, subcontractors, and suppliers; and an operator may be an airline, leasing company, military entity, service organization, etc.

[0090] The various aspects of this disclosure can be found in, for example Figure 7 The example of aircraft 700 is described in the context of [the example shown]. Figure 7 In the example, aircraft 700 includes a fuselage 718, an interior 722, and multiple systems 720. Examples of the multiple systems 720 include a propulsion system 724, an electrical system 726, an environmental system 728, a hydraulic system 730, and one or more of devices 102. Any number of other systems may be included. Figure 7 In the example, aircraft 700 includes, as in Figures 1-6 Device 102 is described in one or more aspects of this disclosure. Parts of device 102 are included in the fuselage 718 and the interior 722.

[0091] Figure 8This is a block diagram of a computing environment 800 comprising aspects of a computing device 810 configured to support computer-implemented methods and computer-executable program instructions (or code) according to this disclosure. For example, the computing device 810 or portions thereof is configured to execute instructions to initiate, execute, or control references. Figures 1-7 One or more operations described.

[0092] The computing device 810 includes one or more processors 820. In some aspects, the processor(s) 820 includes one or more processors 136, such as... Figure 1 As described herein, processor 820 is configured to communicate with system memory 830, one or more storage devices 840, one or more input / output interfaces 850, one or more communication interfaces 860, or any combination thereof. System memory 830 includes volatile memory devices (e.g., random access memory (RAM) devices), non-volatile memory devices (e.g., read-only memory (ROM) devices, programmable read-only memory, and flash memory) or both. System memory 830 stores operating system 832, which may include a basic input / output system for booting computing device 810 and a complete operating system enabling computing device 810 to interact with users, other programs, and other devices. System memory 830 stores system (program) data 836 and applications 834, such as MEL status manager 116, power setting calculator 118, performance calculator 120, or combinations thereof.

[0093] System memory 830 includes one or more operating systems 832 and / or one or more applications 834 (e.g., instruction sets) executable by processor 820. As an example, one or more applications 834 include those executable by processor 820 to initiate, control, or execute references. Figures 1-7 Instructions for one or more operations described, such as receiving input that identifies a first equipment item as failed, selecting an adjustment factor associated with the failure state of the first equipment item based on the input, calculating a set of engine performance planning metrics for the planned flight based on the adjustment factor and environmental condition data 108 associated with the flight path of the planned flight, and determining a weight penalty, fuel penalty, or both for the planned flight based on the set of engine performance planning metrics.

[0094] In a specific implementation, system memory 830 includes a non-transitory computer-readable medium storing instructions that, when executed by processor 820, cause processor 820 to initiate, execute, or control operations to help generate engine power settings and performance calculations for troublesome adjustments to aircraft 138 operating with a failed device item. The operations include: receiving input identifying a first device item as failed; selecting an adjustment factor associated with the failure state of the first device item based on the input; calculating a set of planned engine performance metrics for the planned flight based on the adjustment factor and environmental condition data 108 associated with the planned flight path; and determining a weight penalty, fuel penalty, or both for the planned flight based on the set of planned engine performance metrics.

[0095] One or more storage devices 840 include non-volatile storage devices, such as disks, optical disks, or flash memory devices. In a particular example, storage device 840 includes both removable and non-removable memory devices. Storage device 840 is configured to store an operating system, images of the operating system, applications (e.g., one or more applications 834), and program data (e.g., program data 836). In a particular aspect, system memory 830, storage device 840, or both contain tangible computer-readable media. In a particular aspect, one or more storage devices 840 are external to computing device 810.

[0096] One or more input / output interfaces 850 enable computing device 810 to communicate with one or more input / output devices 870 to facilitate user interaction. For example, one or more input / output interfaces 850, input interfaces, or both. For example, input / output interface 850 is adapted to receive input from a user, input from another computing device, or a combination thereof. In some implementations, input / output interface 850 conforms to one or more standard interface protocols, including serial interfaces (e.g., Universal Serial Bus (USB) interfaces or Institute of Electrical and Electronics Engineers (IEEE) interface standards), parallel interfaces, display adapters, audio adapters, or custom interfaces (“IEEE” is a registered trademark of the Institute of Electrical and Electronics Engineers, Piscateway, New Jersey). In some implementations, input / output device 870 includes one or more user interface devices and displays, including combinations of buttons, keyboards, pointing devices, displays, speakers, microphones, touchscreens, and other devices.

[0097] One or more processors 820 are configured to communicate with a device or controller 880 via one or more communication interfaces 860. For example, one or more communication interfaces 860 may include a network interface.

[0098] In some implementations, a non-transitory computer-readable medium stores instructions that, when executed by one or more processors, cause one or more processors to initiate, perform, or control operations to perform some or all of the functionality described above. For example, these instructions may be executable to implement Figures 1-7 One or more of the operations or methods. In some implementations, Figures 1-7 One or more of the operations or methods may be implemented by one or more processors executing instructions (e.g., one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more digital signal processors (DSPs)), by dedicated hardware circuitry, or any combination thereof.

[0099] Specific aspects of this disclosure are described in the following group of related embodiments: According to Embodiment 1, an aircraft includes: one or more processors configured to receive input identifying a first device item as faulty; based on the input identifying the first device item as faulty, selecting adjustment factors to be applied during engine performance calculations for a specific planned flight of the aircraft; determining a set of engine performance planning metrics for the specific planned flight based on the adjustment factors and environmental condition data associated with the aircraft; and determining a weight penalty, a fuel penalty, or both for the specific planned flight based on the set of engine performance planning metrics.

[0100] Embodiment 2 includes the aircraft of Embodiment 1, and further includes a control display unit (CDU), wherein one or more processors are configured to receive input via the CDU.

[0101] Example 3 includes the aircraft of Example 1 or Example 2, and also includes one or more switches on the aircraft's panel, wherein one or more processors are configured to receive input via one or more switches.

[0102] Example 4 includes an aircraft of any one of Examples 1 to 3, wherein, in order to determine a set of engine performance planning metrics, one or more processors are configured to calculate a base power setting; apply an adjustment factor to the base power setting to generate an adjusted power setting; and determine a set of engine performance planning metrics based on the adjusted power setting.

[0103] Example 5 includes the aircraft of Example 4, wherein one or more processors are configured to transmit adjusted power settings to the electronic engine controller (EEC) for implementation during a specific planned flight.

[0104] Example 6 includes an aircraft of any one of Examples 1 to 5, wherein, in order to determine a set of engine performance planning metrics, one or more processors are configured to receive environmental condition data including at least one of pressure altitude, temperature, airspeed, or barometric altitude; and to determine a set of engine performance planning metrics based on adjustment factors and environmental condition data.

[0105] Example 7 includes an aircraft of any one of Examples 1 to 6, wherein the weight penalty includes at least one of the following: takeoff weight limit; route climb weight limit; or landing weight limit.

[0106] Example 8 includes an aircraft of any one of Examples 1 to 7, wherein the fuel penalty includes at least one of the following: planned fuel demand; or alternate landing fuel reserve demand.

[0107] Example 9 includes an aircraft of any one of Examples 1 to 8, wherein one or more processors are configured to receive input identifying a second device item as failed; select a combined adjustment factor that takes into account the combined effect of the two failed items based on the fact that both the first and second device items are failed; and determine a set of engine performance planning metrics based on the combined adjustment factor.

[0108] According to Embodiment 10, an aircraft includes: one or more processors configured to receive input identifying a first device item as failed; based on the input, selecting an adjustment factor associated with the failure state of the first device item; calculating a set of engine performance planning metrics for the planned flight based on the adjustment factor and environmental condition data associated with a planned flight path; and determining a weight penalty, a fuel penalty, or both for the planned flight based on the set of engine performance planning metrics.

[0109] Example 11 includes the aircraft of Example 10, and further includes a control display unit (CDU), wherein one or more processors are configured to receive input via the CDU.

[0110] Example 12 includes the aircraft of Example 10 or Example 11, and also includes one or more switches on the panel of the aircraft, wherein one or more processors are configured to receive input via one or more switches.

[0111] Example 13 includes an aircraft of any one of Examples 10 to 12, wherein, in order to determine a set of engine performance planning metrics, one or more processors are configured to calculate a base power setting; apply an adjustment factor to the base power setting to generate an adjusted power setting; and determine a set of engine performance planning metrics based on the adjusted power setting.

[0112] Example 14 includes the aircraft of Example 13, wherein one or more processors are further configured to transmit adjusted power settings to the electronic engine controller (EEC); and to cause the EEC to implement the adjusted power settings during planned flight.

[0113] According to Embodiment 15, an aircraft comprising any one of Embodiments 10 to 14, wherein, in order to determine a set of engine performance planning metrics, one or more processors are configured to receive environmental condition data including at least one of pressure altitude, temperature, airspeed, or barometric altitude; and to determine the set of engine performance planning metrics based on adjustment factors and the environmental condition data.

[0114] According to Embodiment 16, an aircraft comprising any one of Embodiments 10 to 15 is provided, wherein the weight penalty includes at least one of the following: takeoff weight limit; route climb weight limit; or landing weight limit.

[0115] According to Embodiment 17, an aircraft comprising any one of Embodiments 10 to 16 is included, wherein the fuel penalty includes at least one of the following: planned fuel demand; or alternate landing fuel reserve demand.

[0116] Example 18 includes an aircraft of any one of Examples 10 to 17, wherein one or more processors are configured to receive input identifying a second device item as failed; select a combined adjustment factor associated with the failure state of the first device item and the failure state of the second device item based on the failure of both the first device item and the second device item; and calculate a set of engine performance planning metrics based on the combined adjustment factor.

[0117] According to embodiment 19, a method includes: receiving an input identifying a first equipment item as failed; selecting an adjustment factor associated with the failure state of the first equipment item based on the input; calculating a set of engine performance planning metrics for the planned flight based on the adjustment factor and environmental condition data associated with a flight path of the planned flight; and determining a weight penalty, a fuel penalty, or both for the planned flight based on the set of engine performance planning metrics.

[0118] Example 20 includes the method of Example 19, further comprising: receiving input identifying a second device item as failed; selecting a combined adjustment factor associated with the failure state of the first device item and the failure state of the second device item based on the fact that both the first device item and the second device item are failed; and calculating a set of engine performance planning metrics based on the combined adjustment factor.

[0119] The illustrations of the examples described herein are intended to provide a general understanding of the structure of various implementations. These illustrations are not intended to serve as a complete description of all elements and features of devices and systems utilizing the structures or methods described herein. Many other implementations will be apparent to those skilled in the art upon reading this disclosure. Other implementations may be utilized and derived from this disclosure, allowing for structural and logical substitutions and changes without departing from the scope of this disclosure. For example, method operations may be performed in a different order than those shown in the figures, or one or more method operations may be omitted. Therefore, this disclosure and the accompanying drawings are to be considered illustrative rather than restrictive.

[0120] Furthermore, while specific examples have been shown and described herein, it should be understood that any subsequent arrangements designed to achieve the same or similar results may replace the specific implementations shown. This disclosure is intended to cover any and all subsequent adaptations or variations of the various implementations. After reading this description, combinations of the above implementations, as well as other implementations not specifically described herein, will be apparent to those skilled in the art.

[0121] The abstract of this disclosure is provided to be understood not to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing specific embodiments, different features may be combined together or described in a single implementation for the purpose of simplification. The foregoing examples are illustrative but not limiting of this disclosure. It should also be understood that many modifications and variations are possible based on the principles of this disclosure. As reflected in the following claims, the claimed subject matter may involve fewer features than all features of any of the disclosed examples. Therefore, the scope of this disclosure is defined by the appended claims and their equivalents.

Claims

1. An aircraft comprising: One or more processors are configured as follows: Receive input that identifies the first device item as invalid; Based on the input that identifies the first device item as faulty, select the adjustment factor to be applied during engine performance calculations for a specific planned flight of the aircraft; A set of engine performance planning metrics is determined based on the adjustment factors and environmental condition data associated with the aircraft for the specific planned flight. as well as The weight penalty, fuel penalty, or both, for the specific planned flight is determined based on the set of engine performance planning metrics.

2. The aircraft according to claim 1, further comprising: A control display unit, wherein the one or more processors are configured to receive the input via the control display unit.

3. The aircraft according to claim 1, further comprising: One or more switches on the panel of the aircraft, wherein the one or more processors are configured to receive the input via the one or more switches.

4. The aircraft according to claim 1, wherein, To determine the set of engine performance plan metrics, the one or more processors are configured to: Calculate the base power setting; The adjustment factor is applied to the base power setting to generate the adjusted power setting; and The set of engine performance plan metrics is determined based on the adjusted power settings.

5. The aircraft according to claim 4, wherein, The one or more processors are configured to transmit the adjusted power settings to the electronic engine controller for implementation during the specific planned flight.

6. The aircraft according to claim 1, wherein, To determine the set of engine performance plan metrics, the one or more processors are configured to: Receive environmental condition data including at least one of pressure altitude, temperature, air velocity, and barometric altitude; and The set of engine performance planning metrics is determined based on the adjustment factors and the environmental condition data.

7. The aircraft according to claim 1, wherein, The weight penalty includes at least one of the following: Takeoff weight restrictions; Route climb weight limits; and Landing weight limits.

8. The aircraft according to claim 1, wherein, The fuel penalty includes at least one of the following: Planned fuel demand; and Diversion fuel reserve demand.

9. The aircraft according to claim 1, wherein, The one or more processors are further configured to: Receive input that identifies the second device item as invalid; Based on the fact that both the first equipment item and the second equipment item are failed, a combined adjustment factor that considers the combined effect of the two failed items is selected. as well as The set of engine performance plan metrics is determined based on the combined adjustment factors.

10. An aircraft comprising: One or more processors are configured as follows: Receive input that identifies the first device item as invalid; Based on the input, select an adjustment factor associated with the failure state of the first device item; A set of engine performance planning metrics for the planned flight is calculated based on the adjustment factors and environmental condition data associated with the flight path of the planned flight. as well as Based on the set of engine performance planning metrics, determine the weight penalty, fuel penalty, or both for the planned flight.

11. The aircraft according to claim 10, further comprising: A control display unit, wherein the one or more processors are configured to receive the input via the control display unit.

12. The aircraft according to claim 10, further comprising: One or more switches on the panel of the aircraft, wherein the one or more processors are configured to receive the input via the one or more switches.

13. The aircraft according to claim 10, wherein, To determine the set of engine performance plan metrics, the one or more processors are configured to: Calculate the base power setting; The adjustment factor is applied to the base power setting to generate the adjusted power setting; and The set of engine performance plan metrics is determined based on the adjusted power settings.

14. The aircraft according to claim 13, wherein, The one or more processors are further configured to: The adjusted power setting is transmitted to the electronic engine controller; and The electronic engine controller implements the adjusted power setting during the planned flight.

15. The aircraft according to claim 10, wherein, To determine the set of engine performance plan metrics, the one or more processors are configured to: Receive environmental condition data including at least one of pressure altitude, temperature, air speed, and barometric altitude.

16. The aircraft according to claim 10, wherein, The weight penalty includes at least one of the following: Takeoff weight restrictions; Route climb weight limits; and Landing weight limits.

17. The aircraft according to claim 10, wherein, The fuel penalty includes at least one of the following: Planned fuel demand; and Diversion fuel reserve demand.

18. The aircraft according to claim 10, wherein, The one or more processors are further configured to: Receive input that identifies the second device item as invalid; Based on the fact that both the first device item and the second device item have failed, a combined adjustment factor associated with the failure status of the first device item and the failure status of the second device item is selected; as well as The set of engine performance plan metrics is calculated based on the combined adjustment factors.

19. A method for adjusting engine power settings, comprising: Receive input that identifies the first device item as invalid; Based on the input, select an adjustment factor associated with the failure state of the first device item; A set of engine performance planning metrics for the planned flight is calculated based on the adjustment factors and environmental condition data associated with the flight path of the planned flight. as well as Based on the set of engine performance planning metrics, determine the weight penalty, fuel penalty, or both for the planned flight.

20. The method of claim 19, further comprising: Receive input that identifies the second device item as invalid; Based on the fact that both the first device item and the second device item have failed, a combined adjustment factor associated with the failure status of the first device item and the failure status of the second device item is selected; as well as The set of engine performance plan metrics is calculated based on the combined adjustment factors.

Images