High-energy management system

Abstract

To provide methods, apparatuses and systems for managing a high-energy system (HEMS) in an aircraft.SOLUTION: Techniques comprise receiving sensor data from a plurality of HE systems. Each of the HE systems is located in an aircraft. A high-energy management system for an aircraft is controlled by: determining a present state of each of the HE systems based on the received sensor data; determining a target state of each of the HE systems based on the present state of each of the HE systems and a set of HE system rules; and automatically generating one or more control actions for control of one or more of the HE systems based on the target state of each of the HE systems. Further, a schedule of tasks to be performed on the aircraft is received, and the target state is determined based thereon.SELECTED DRAWING: Figure 1A

Description

[Technical field]

[0001] The present disclosure relates to techniques for managing high energy (HE) systems for aircraft. In particular, the present disclosure relates to a control system for controlling a high energy system of an aircraft based on a current state of the HE system and HE system rules. [Background technology]

[0002]

[0002] During the manufacture, testing, or maintenance of an aircraft, workers may be exposed to high energy systems, such as electrical systems, hydraulic systems, propulsion systems, cockpit power systems, fuel systems, and the like. These systems may be activated or deactivated in unexpected and / or conflicting ways during the manufacture, testing, or maintenance operations, resulting in worker injuries, equipment or device damage, and / or flight delays associated with inadvertent exposure to the high energy systems. Currently, the only mechanism to prevent inadvertent exposure to high energy systems is through geo-fencing. Geo-fencing creates a physical barrier or boundary around the perimeter to isolate people from certain areas of the aircraft that are at risk of exposure to the high energy systems. However, such an approach has drawbacks, as critical employees who are required to work with the high energy systems (e.g., within the perimeter) are still at risk of exposure. Furthermore, geo-fencing does not protect equipment (e.g., within the perimeter) from damage due to exposure. Summary of the Invention

[0003]

[0003] Disclosed herein are methods, devices, and systems for managing high energy systems in an aircraft (A / C) by determining a target state of the high energy system based on the current state of the high energy system and a set of high energy system rules, and generating control actions for controlling the high energy system based on the target state. The target state is set to avoid simultaneous activation of incompatible systems. In some embodiments, the target state is further determined based on a schedule of operations (e.g., high energy system operations) to be performed on the aircraft. Additionally, the status and mode of each high energy system on the aircraft are communicated in real time to key personnel to inform them of the status of the high energy systems and activation of potentially conflicting systems.

[0004]

[0004] According to one or more embodiments, a method for controlling a high energy management system includes receiving sensor data from a plurality of high energy (HE) systems, each of the plurality of HE systems being disposed within an aircraft, determining a current state of each of the plurality of HE systems based on the sensor data, determining a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules, and automatically generating one or more control actions for controlling one or more of the plurality of HE systems based on the target state of each of the plurality of HE systems.

[0005]

[0005] In accordance with one or more embodiments, a high energy management system controller includes a processor and a memory coupled to the processor, the memory including instructions that, when executed by the processor, cause the high energy management system controller to: receive sensor data from a plurality of high energy (HE) systems, each of the plurality of HE systems being disposed within the aircraft; determine a current state of each of the plurality of HE systems based on the sensor data; determine a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and automatically generate one or more control actions for controlling one or more of the plurality of HE systems based on the target state of each of the plurality of HE systems.

[0006]

[0006] According to one or more embodiments, at least one computer-readable storage medium includes instructions that, when executed by a processor, cause a high energy management system controller to receive sensor data from a plurality of high energy (HE) systems, each of the plurality of HE systems being disposed within an aircraft; determine a current state of each of the plurality of HE systems based on the sensor data; determine a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and automatically generate one or more control actions for controlling one or more of the plurality of HE systems based on the target state of each of the plurality of HE systems.

[0007]

[0007] The above-described features, functions, and advantages may be realized individually in various embodiments or may be combined in yet another embodiment, further details of which may be understood by reference to the following description and drawings.

[0008]

[0008] Various advantages of the embodiments will become apparent to those skilled in the art upon reading the following specification and appended claims and upon reference to the drawings in which: [Brief description of the drawings]

[0009] [Figure 1A] 1A-1B provide a block diagram illustrating one embodiment of an advanced energy management system according to one or more embodiments. [Figure 1B] 1A-1B provide a block diagram illustrating one embodiment of an advanced energy management system according to one or more embodiments. [Figure 2A]

[0010] 2A-2B provide a block diagram illustrating another embodiment of an advanced energy management system according to one or more embodiments. [Figure 2B] 2A-2B provide a block diagram illustrating another embodiment of an advanced energy management system according to one or more embodiments. [Diagram 3]

[0011] 1 provides a block diagram illustrating an embodiment of an advanced energy management system controller in accordance with one or more embodiments. [Figure 4A]

[0012] 4A-4B provide a flow diagram illustrating an example method for controlling an advanced energy management system according to one or more embodiments. [Figure 4B] 4A-4B provide a flow diagram illustrating an example method of controlling an advanced energy management system according to one or more embodiments. [Diagram 5]

[0013] 1 provides a block diagram illustrating an example computing system for use in controlling an advanced energy management system according to one or more embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010]

[0014] Thus, it should be understood that the embodiments described herein are merely illustrative of the application of the disclosed principles, and references herein to details of the illustrated embodiments are not intended to limit the scope of the claims, which in themselves recite features regarded as essential to the disclosure.

[0011]

[0015] Disclosed are methods, apparatus, and systems for managing high energy systems (HEMS) onboard aircraft. High energy systems are necessary for the safe operation of an aircraft, but exposure to high energy systems (HE systems) during manufacture, testing, or maintenance can result in injury to personnel and damage to equipment or devices. "High energy" systems for aircraft are those that present a risk of personal injury and / or equipment damage from exposure to one or more of the following types of energy: electrical (e.g., via voltage, current, charge, etc.), thermal (e.g., via liquids, airframe, material surfaces, etc.), gas pressure (e.g., air under pressure), hydraulic (e.g., liquids under pressure), mechanical / kinetic (e.g., via motion of objects), mechanical / potential (e.g., via stored position or gravity), weapons (e.g., via explosives), and / or radiation (e.g., via radio frequency, electric and magnetic field radiation, etc.).

[0012]

[0016] Examples of high energy systems include one or more of electrical systems, hydraulic systems, propulsion systems, cockpit power systems, payload and weapons systems, and / or fuel systems. As one example, hydraulic systems may present a risk of personal injury and / or equipment damage not only due to liquid under pressure, but also due to movement of devices (e.g., wing flaps) caused by changes in hydraulic pressure. Other examples of high energy systems for aircraft may include one or more of radar systems, oxygen tank (or bottle) systems, gas pressure systems, door spring systems, etc.

[0013]

[0017] Thus, there is a need for proper control of high energy systems to avoid exposure that could otherwise result in injury or damage. The technology described herein fills this need by actively and continuously controlling the activation and deactivation of high energy systems to mitigate, reduce, or avoid system conflicts, such as inadvertent simultaneous exposure to conflicting types of high energy that can not only be dangerous, but also result in schedule delays, as well as quality issues (e.g., due to damage to equipment on the aircraft). This capability supports personnel not only during manufacturing processes, but also during testing or maintenance activities.

[0014]

[0018] 1A-1B provide a block diagram illustrating an embodiment of a high energy management system 100 according to one or more embodiments, with reference to components and features described herein, including, but not limited to, the drawings and related description. As shown in FIG. 1A, the high energy management system 100 includes a high energy management system controller 110, a number of high energy (HE) systems 120, and a number of user devices 140. The high energy management system controller 110 communicates with each of the HE systems 120 and each of the user devices 140. Communications are typically exchanged between the high energy management system controller 110 and the individual systems or devices (e.g., individual ones of the HE systems 120 and / or user devices 140) via wireless and / or wired connections. In some embodiments, the high energy management system 100 includes or interacts with an operations system 145 that provides overall control or oversight of the aircraft, including oversight over the high energy management system controller 110, via one or more operational managers and / or team leaders. Further details regarding the high energy management system controller 110 are provided herein with reference to FIG. 3.

[0015]

[0019] The HE systems 120 may include any number of HE systems for an aircraft, including HE system A (120-A), HE system B (120-B), HE system C (120-A) through HE system N (120-N). For example, the HE systems 120 may include one or more of an electrical system, a hydraulic system, a propulsion system, a cockpit power system, a payload and weapons system, and / or a fuel system. In some embodiments, any of these HE systems may include multiple systems or subsystems (e.g., to include partitioned, distributed, and / or redundant system functions). Other embodiments of HE systems for an aircraft may include one or more of a radar system, an oxygen tank (or bottle) system, a gas pressure system, a door spring system, and the like. Any given HE system of the HE systems 120 is typically coupled (e.g., connected) to the high energy management system controller 110 via a wired and / or wireless connection, including via a network (not shown in FIG. 1A ). Further details regarding the architecture of the advanced energy management system 100 are provided herein with reference to FIG. 1B.

[0016]

[0020] The plurality of user devices 140 includes user device A (140-A), user device B (140-B), user device C (140-C) through user device M (140-M). For example, the plurality of user devices 140 may include one or more of a desktop computer, a laptop computer, a tablet computer, a smartphone, a smart watch, etc. Any given user device of the plurality of user devices 140 is typically coupled (e.g., connected) to the high energy management system controller 110 via a wired and / or wireless connection, including via a network (not shown in FIG. 1A ).

[0017]

[0021] Optionally, in combination with the embodiments described above (or below), in some embodiments, the high energy management system controller 110 further receives as an input an A / C ground reference 125 (labeled “A / C ground reference” in FIGS. 1A, 2A, and 3). The A / C ground reference 125 provides information to enable the high energy management system controller 110 to verify that the aircraft is on the ground and not flying. In such embodiments, the high energy management system controller 110 actively controls the HE system 120 only if the aircraft is verified to be in a ground state (i.e., on the ground). The high energy management system controller 110 evaluates information from the A / C ground reference 125 to determine whether the aircraft is on the ground. In some embodiments, the A / C ground reference is evaluated by another module (e.g., a maintenance module or a production test module, not shown in FIG. 1A), and the result of the evaluation (e.g., an indication that the aircraft is in a ground state or that the aircraft is not on the ground) is provided to the high energy management system controller 110 as the A / C ground reference 125.

[0018]

[0022] Optionally, in combination with the embodiments described above (or below), in some embodiments, the high energy management system controller 110 further receives as an input a work schedule 130. The work schedule 130 provides information regarding operations (e.g., manufacturing operations, testing operations, or maintenance operations) for the high energy system to be performed on the aircraft, along with the timing and / or sequence for the execution of the operations. The work schedule may be provided, for example, via a scheduling tool. The operations (and their timing / sequence) will affect the control actions taken by the high energy management system controller 110 with respect to any one or more of the HE systems 120 based at least on the HE system rules.

[0019]

[0023] 1B, which illustrates details regarding the architecture of the high energy management system 100, in particular the components of the HE systems 120 and the communication paths between the high energy management system controller 110 and any one or more of the HE systems 120. Any given HE system of the multiple HE systems 120 typically has at least one sensor and at least one actuator. For example, as shown in FIG. 1B, HE system A (120-A) has at least one sensor 122-A and at least one actuator 124-A, and similarly, HE system N (120-N) has at least one sensor 122-N and at least one actuator 124-N. The sensors and actuators are distributed throughout the aircraft and are typically located in the vicinity or within range of each HE system of the aircraft.

[0020]

[0024] In a given HE system, the sensor(s) provide information about the state of the HE system, and the actuator(s) provide a control mechanism for activating (turning on) or deactivating (turning off) the HE system (or a part or component thereof). The state of the HE system relates to the operational state of the HE system, including whether the HE system is on (e.g., active, energized, etc.) or off (e.g., inactive, unenergized, etc.). One skilled in the art would know the types of sensors used with any HE system and would understand how to determine the current state of any given HE system from the sensor data for that HE system. Based on the sensor data, the high energy management system controller 110 determines the current state of each of the HE systems 120. That is, the high energy management system controller 110 is configured to interpret the sensor data for a given HE system to determine the current state of the HE system for that HE system based on the sensor data. The high energy management system controller 110 then determines a target state for each of the HE systems 120 based on its current state and based on the HE system rules, and generates control actions for controlling the HE systems 120.

[0021]

[0025] In some cases, a given HE system has multiple sensors and / or multiple actuators. As an example, in an HE system related to a hydraulic system for setting and adjusting wing flaps, the hydraulic system includes multiple sensors related to the wing flaps (e.g., each wing has a wing flap, each wing flap has a sensor, etc.). Similarly, the hydraulic system includes multiple actuators related to the wing flaps (e.g., each wing has a wing flap, each wing flap has an actuator, etc.). As another example, a given HE system may have multiple sensors for redundancy purposes (e.g., redundant sensors to protect the HE system and the aircraft in the event of a sensor failure).

[0022]

[0026] As shown in FIG. 1B, typically there are one or more communication paths (e.g., wired and / or wireless connections) between the high energy management system controller 110 and each given HE system. For example, there may be one communication path for data from the sensor(s) for a given HE system and another communication path for commands to the actuator(s) for that HE system. Typically, each HE system has a sub-controller (not shown in FIG. 1B) through which data and / or commands flow between the high energy management system controller 110 and the sensor(s) and actuator(s) for that HE system. As an example, in a hydraulic system, an exemplary HE system includes a hydraulic sub-controller that obtains sensor data (e.g., data from a pressure transducer that measures hydraulic pressure) and provides the sensor data to the high energy management system controller 110.

[0023]

[0027] In the detailed example architecture shown in FIG. 1B, there is a first communication path between the high energy management system controller 110 and HE system A (120-A) for data from the sensor(s) 122-A, a second communication path between the high energy management system controller 110 and HE system A (120-A) for commands to the actuator 124-A, a third communication path between the high energy management system controller 110 and HE system N (120-N) for data from the sensor(s) 122-N, and a fourth communication path between the high energy management system controller 110 and HE system N (120-N) for commands to the actuator 124-N. These communication paths may be separate or shared, or may partially overlap. Thus, in some embodiments, the communication paths between the high energy management system controller 110 and a given HE system are shared and / or overlapping.

[0024]

[0028] In some embodiments, the high energy management system controller 110 of the high energy management system 100 is installed / embedded in the aircraft and can be located almost anywhere on the aircraft. Alternatively, in other embodiments, the high energy management system controller 110 is located outside the aircraft (e.g., as part of a mobile physical unit while the aircraft is being manufactured or under test) and communicates with the HE system via wired and / or wireless connections. For example, in some of the other embodiments, the high energy management system controller 110 is integrated with a test or maintenance module (not shown). The high energy management system controller 110 is adapted to interact with any individual HE system (e.g., via separate communication paths or via shared or overlapping paths, as described above). As an example, the high energy management system controller 110 is adapted to issue commands for actuators of a given HE system to activate or deactivate the HE system (or a portion thereof) and then receive sensor data (e.g., data providing a status for the given HE system). From the sensor data, the high energy management system controller 110 verifies that the command was executed successfully.

[0025]

[0029] Some or all of the components in the high energy management system 100 may be implemented using one or more of a central processing unit (CPU), a graphic processing unit (GPU), an artificial intelligence (AI) accelerator, a field programmable gate array (FPGA) accelerator, an application specific integrated circuit (ASIC), and / or via a processor with software, or in a combination of a processor with software and an FPGA or an ASIC. In particular, the components of the high energy management system 100 may be implemented in one or more modules, as a set of programs or logic instructions stored in a machine or computer readable storage medium, such as a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), firmware, flash memory, etc., as hardware, or a combination thereof. For example, a hardware implementation may include configurable logic, fixed function logic, or any combination thereof. Examples of configurable logic include appropriately configured programmable logic arrays (PLAs), FPGAs, complex programmable logic devices (CPLDs), and general purpose microprocessors. Examples of fixed-function logic include appropriately configured ASICs, combinational logic circuits, and sequential logic circuits. Configurable or fixed-function logic may be implemented in complementary metal-oxide semiconductor (CMOS) logic circuits, transistor-transistor logic (TTL) logic circuits, or other circuits.

[0026]

[0030] For example, computer program code for executing operations by the high energy management system 100 may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, JavaScript, Python, C#, C++, Perl, Smalltalk, and conventional procedural programming languages, such as the "C" programming language or a similar programming language. Furthermore, the program or logic instructions may include assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, configurable data for integrated circuits, state information to personalize electronic circuits, and / or other structural components native to the hardware (e.g., a host processor, a central processing unit / CPU, a microcontroller, etc.).

[0027]

[0031] 2A-2B provide a block diagram illustrating another embodiment of a high energy management system 200 according to one or more embodiments, with reference to the components and features described herein, including but not limited to the drawings and related description. The high energy management system 200 includes the same or similar components and features as those in the high energy management system 100 (FIGS. 1A-1B, already described), which will not be repeated unless appropriate to describe the components and features of the high energy management system 200. As shown in the embodiment of FIG. 2A, the high energy management system 200 includes an aircraft interface module 210 in addition to the components of the high energy management system 100 (FIGS. 1A-1B). The aircraft interface module 210 is located between the high energy management system controller 110 and the multiple HE systems 120 from a logical point of view. The aircraft interface module 210 provides a communication interface between the high energy management system controller 110 and the multiple HE systems 120. Requests, commands, data, etc. flowing between the high energy management system controller 110 and the multiple HE systems 120 are thereby routed through the aircraft interface module 210 .

[0028]

[0032] In effect, the aircraft interface module 210 is a pass-through device for commands and data flowing between the high energy management system controller 110 and the multiple HE systems 120, and the aircraft interface module 210 does not, itself, provide HE system control functionality as described herein. Further details regarding the architecture of the high energy management system 200 are provided herein with reference to FIG. 2B.

[0029]

[0033] In some embodiments, aircraft interface module 210 is a module provided as part of a manufacturing or maintenance system used in the manufacture, testing, or maintenance of aircraft HE systems. In some embodiments, a hybrid architecture is used, where communications between high energy management system controller 110 and some of the HE systems 120 are routed through aircraft interface module 210, while communications between high energy management system controller 110 and others of the HE systems 120 are performed through paths, such as the communication paths shown in FIGS. 1A-1B, and are not routed through aircraft interface module 210. In some embodiments, A / C ground reference 125 and / or work schedule 130 are routed to high energy management system controller 110 through aircraft interface module 210.

[0030]

[0034] 2B, which illustrates the architecture of the high energy management system 200, in particular the components of the HE system 120 and details regarding the communication paths between the high energy management system controller 110 and any one or more of the HE systems 120 via the aircraft interface module 210. As illustrated in FIG. 2B, similar to the architectural details illustrated in FIG. 1B, typically there are one or more communication paths (e.g., wired and / or wireless connections) between the aircraft interface module 210 and each given HE system. For example, there may be one communication path for data from the sensor(s) for a given HE system and another communication path for commands to the actuator(s) for that HE system. These communication paths may be separate or shared or may overlap. There are communication paths (wired and / or wireless connections) between the high energy management system controller 110 and the aircraft interface module 210, allowing communications (e.g., requests, commands, data) between the high energy management system controller 110 and the HE systems to be routed through the aircraft interface module 210 (e.g., acting as a pass-through device).

[0031]

[0035] In some embodiments, the high energy management system controller 110 of the high energy management system 200 is installed / embedded in the aircraft and can be located almost anywhere on the aircraft. Alternatively, in other embodiments, the high energy management system controller 110 is located outside the aircraft (e.g., as part of a mobile physical unit while the aircraft is being manufactured or under test) and communicates with the aircraft interface module 210 via a wired and / or wireless connection. For example, in some of the other embodiments, the high energy management system controller 110 is integrated with the aircraft interface module 210 or a test or maintenance module (not shown). Through the communication paths between the high energy management system controller 110 and the aircraft interface module 210, together with the communication paths between the aircraft interface module 210 and the HE systems, the high energy management system controller 110 is adapted to interact with any individual HE system. As an example, the high energy management system controller 110 is adapted to issue commands for actuators of a given HE system to activate or deactivate the HE system, and then receive sensor data (e.g., data providing a status for a given HE system). From the sensor data, the high energy management system controller 110 verifies that the command was executed successfully.

[0032]

[0036] Some or all of the components in the high energy management system 200 may be implemented using one or more of a central processing unit (CPU), a graphic processing unit (GPU), an artificial intelligence (AI) accelerator, a field programmable gate array (FPGA) accelerator, an application specific integrated circuit (ASIC), and / or via a processor with software, or in a combination of a processor with software and an FPGA or an ASIC. In particular, the components of the high energy management system 200 may be implemented in one or more modules, as a set of programs or logic instructions stored in a machine or computer readable storage medium, such as a random access memory (RAM), a read only memory (ROM), a programmable ROM (PROM), firmware, flash memory, etc., as hardware, or a combination thereof. For example, a hardware implementation may include configurable logic, fixed function logic, or any combination thereof. Examples of configurable logic include appropriately configured programmable logic arrays (PLAs), FPGAs, complex programmable logic devices (CPLDs), and general purpose microprocessors. Examples of fixed-function logic include appropriately configured ASICs, combinational logic circuits, and sequential logic circuits. Configurable or fixed-function logic may be implemented in complementary metal-oxide semiconductor (CMOS) logic circuits, transistor-transistor logic (TTL) logic circuits, or other circuits.

[0033]

[0037] For example, computer program code for executing operations by the high energy management system 200 may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, JavaScript, Python, C#, C++, Perl, Smalltalk, and conventional procedural programming languages, such as the "C" programming language or a similar programming language. Furthermore, the program or logic instructions may include assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, configurable data for integrated circuits, state information to personalize electronic circuits, and / or other structural components native to the hardware (e.g., a host processor, a central processing unit / CPU, a microcontroller, etc.).

[0034]

[0038] FIG. 3 provides a block diagram illustrating an embodiment of a high energy management system controller 300 according to one or more embodiments, with reference to components and features described herein, including, but not limited to, the drawings and related description. The high energy management system controller 300 corresponds to the high energy management system controller 110 (FIGS. 1A-1B and 2A-2B, previously described). As shown in FIG. 3, the high energy management system controller 300 includes a process module 310 and a control module 320 including HE system rules 330. The high energy management system controller 300 receives data 305 obtained from sensors of the HE system, for example, via a communication path between the high energy management system controller 300 and the HE system 120 (e.g., as described herein with respect to FIGS. 1A-1B) or via the aircraft interface module 210 (e.g., as described herein with respect to FIGS. 2A-2B). In some embodiments, the high energy management system controller 300 also receives the A / C ground reference 125 and / or the work schedule 130 as inputs.

[0035]

[0039] The high energy management system controller 300 issues (e.g., sends) status reports 312 and alerts 314 to user devices (e.g., user device 140, FIGS. 1A and 2A) and, when present, to an operational system (e.g., operational system 145, FIGS. 1A and 2A, labeled “Ops” in FIG. 3). The high energy management system controller 300 receives selection(s) / command(s) 322 from authorized users via the user devices and / or operational systems, when present. The high energy management system controller 300 also issues control actions 340 for actuators of the HE system 120, for example, via a communication path between the high energy management system controller 300 and the HE system 120 (e.g., as described herein with respect to FIGS. 1A-1B) or via the aircraft interface module 210 (e.g., as described herein with respect to FIGS. 2A-2B).

[0036]

[0040] The process module 310 receives and analyzes sensor data 305 collected from sensors of the HE systems 120 in real time. The sensor data includes feedback data regarding the status (including, for example, state, mode, and / or condition) for each particular HE system. One skilled in the art would know the types of sensors used with any of the HE systems and would understand how to determine the current state of any given HE system from the sensor data for that HE system. The process module 310 is configured to interpret the sensor data for a given HE system to determine the current state of that HE system based on the sensor data. Based on the sensor data, the process module 310 determines the current (e.g., recent) state of each of the HE systems 120. For example, the current state may include an on state (e.g., a particular HE system is on, energized, activated / activated, etc.) or an off state (e.g., a particular HE system is off, locked off / out, not energized, not activated / deactivated, etc.). The process module 310 then sends information about the current state of the HE system to the control module 320 in real time.

[0037]

[0041] In some embodiments, the process module 310 receives and analyzes the work schedule 130 in real time. The work schedule 130 provides information regarding the operations (e.g., including manufacturing operations, testing operations, or maintenance operations, along with details about the operations) for the high energy system to be performed on the aircraft along with the timing and / or sequence for the execution of the operations. The process module 310 determines the current (e.g., recent) status of the scheduled operations for the aircraft, including, for example, any delays in starting or completing a particular operation, and sends information regarding the current status of the scheduled operations for the aircraft to the control module 320. The process module 310 also sends updates regarding the operations (e.g., based on control actions determined by the control module 320 or overrides issued by an authorized user), which may include changes to the schedule.

[0038]

[0042] In some embodiments, the process module 310 receives and evaluates the A / C ground reference 125. The A / C ground reference 125 provides information to verify that the aircraft is on the ground and not flying. In some embodiments, the A / C ground reference 125 includes information about one or more conditions that indicate that the aircraft is on the ground and not flying, including conditions such as weight on wheels, gear locked, engines off, etc. In some embodiments, these conditions are evaluated by another module (e.g., a maintenance module, not shown), and the result of that evaluation (e.g., an indication that the aircraft is on the ground or that the aircraft is not on the ground) is provided to the process module 310 as the A / C ground reference 125.

[0039]

[0043] The process module 310 evaluates the A / C ground reference 125 to determine whether the aircraft is in a ground state (i.e., on the ground). If the process module 310 determines from the A / C ground reference 125 that the aircraft is in a ground state (i.e., on the ground), the high energy management system controller 300 (via the control module 320) actively controls the HE system 120 via a control action 340; otherwise, if the aircraft is not determined to be in a ground state, the high energy management system controller 300 does not issue a control action 340 to control the HE system 120. In this manner, active control of the HE system by the control module 320 is conditioned on a determination that the aircraft is in a ground state.

[0040]

[0044] Control module 320 receives information regarding the current state of the HE systems from process module 310 in real time. In some embodiments, control module 320 also receives information regarding the current state of scheduled operations for the aircraft from process module 310 in real time. Control module 320 uses HE system rules 330 to evaluate the information received from process module 310 (i.e., including the current state of the HE systems and, when provided, the current state of the scheduled operations) and determine a target state for each of multiple HE systems 120. The target states for the HE systems are states that are permitted by HE system rules 330 to prevent or eliminate conflicts between activation and / or deactivation of the individual HE systems.

[0041]

[0045] Based on the target state for each of the HE systems 120, the control module 320 automatically generates one or more control actions 340 to control one or more of the multiple HE systems 120. For example, the control module 320 generates a control action 340 to be sent to actuators of a particular HE system when it is necessary to place the HE system in a target state, e.g., when the current state of the HE system does not match the target state for that HE system. The control action 340 includes one or more commands issued to one or more actuators for a given HE system to place the HE system in the target state determined by the control module 320. For example, the commands may include a command to turn on or off a particular HE system. In some embodiments, the commands are issued as a sequence to control the activation or deactivation of the HE system according to an order (e.g., a control order established by the HE system rules 330 for a given task). In some embodiments, when the current state of the HE system matches the target state for the HE system, no control action is needed and therefore is not generated for that HE system at that time.

[0042]

[0046] Thus, by generating control actions 340 in real time, control module 320 ensures that each respective HE system of multiple HE systems 120 is placed (or maintained) in a target state for that HE system until it is necessary or appropriate to change the target state for that HE system based on the current state of the HE system at that time, changes in the current state of the task, etc. As an example, if control module 320 determines that a hydraulic system is currently active and based on HE system rules that the current task involves a task near a wing flap on an aircraft, control module 320 issues control actions to one or more actuators for the hydraulic system as needed to keep the hydraulic system active (e.g., prevent deactivation of the hydraulic system) for the duration of the task to prevent the flap from dropping and potentially causing injury. Additionally, based on HE system rules 330, control module 320 issues control actions to deactivate or keep deactivated any HE systems that may conflict with the hydraulic system being active for a particular task (e.g., prevent activation of any conflicting HE systems during the task).

[0043]

[0047] The HE system rules 330 may be stored, for example, in a memory included in the high energy management system controller 300 or accessible to the high energy management system controller 300. The HE system rules 330 define which HE systems may be activated (e.g., turned on) or deactivated (e.g., turned off) at the same time. In some embodiments, the HE system rules 330 include one or more of: (a) rules that specify which of the multiple HE systems may be active with each other (e.g., a rule that specifies that HE system A may be active when HE system B is active, etc.); (b) rules that specify which of the multiple HE systems should be active with another one of the multiple HE systems (e.g., a rule that specifies that HE system C should be active when HE system D is active, etc.); and / or (C) rules that specify which of the multiple HE systems may not be active with each other (e.g., a rule that specifies that HE system E should be inactive when HE system F is active, etc.).

[0044]

[0048] In some embodiments, the HE system rules 330 also specify conditions for activating or deactivating each of the HE systems to avoid an unsafe condition. For example, in some embodiments, the rules specifying conditions for activating or deactivating each of the HE systems include one or more of: a rule specifying an order for activating or deactivating a subset of the HE systems (e.g., various ones of the HE systems) and / or a rule specifying timing requirements associated with activating or deactivating each of the HE systems. In some embodiments, the rules are defined based at least in part on the type or nature of the operation (e.g., a manufacturing operation, a test operation, or a maintenance operation). As an example, for a test or maintenance operation for an electrical system, the HE system rules 330 may specify that two adjacent electrical systems (i.e., two systems or components thereof in close proximity to each other) are not activated at the same time to avoid inadvertent or accidental contact with nearby systems.

[0045]

[0049] For example, the timing / sequence defined by HE system rules 330 ensures that a particular HE system is not turned on or off too early or too late. In some examples, HE system rules 330 include rules that are dependent on the operation being performed (or to be performed next). As one example, if a maintenance operation is being performed that includes activation of a hydraulic system, HE system rules 330 may specify that the electrical system that provides power to the hydraulic system (e.g., a complementary system to the hydraulic system) is not to be deactivated prior to completion of the hydraulic operation. Power thereby maintains that the hydraulic system has pressure to hold aircraft components in place for the duration of the operation.

[0046]

[0050] The control module 320 sends information identifying conflicts or potential conflicts between HE systems (e.g., conflicting or potentially conflicting activation and / or deactivation of HE systems) to the process module 310. Such conflicts may be caused by work scheduling, including delays in initiating or completing certain tasks, or inadvertent human error, or system failures, etc.

[0047]

[0051] The control module 320 also communicates with the user devices 140. The control module 320 sends status reports 312 to one or more of the user devices 140 for display. The user devices 140 may be assigned to and / or operated by personnel involved in the manufacturing, testing, or maintenance of various aircraft systems, components, and the like. In some embodiments, the status reports 312 are sent to all personnel involved in the manufacturing, testing, or maintenance, or to key personnel (e.g., having primary or supervisory responsibility), while in other embodiments, the status reports 312 are sent to personnel on a project or task basis (e.g., personnel involved in projects or tasks involving interaction with or exposure to a particular HE system). The status reports 312 provide information regarding the current state of one or more of the HE systems 120. For example, the status reports 312 indicate which HE systems are in an on state and which HE systems are in an off state. In some embodiments, the status reports also provide information regarding the current state of scheduled tasks, including, for example, any delays in the initiation or completion of a particular task.

[0048]

[0052] The real-time status information in status report 312 may be displayed on any digital client device, such as (without limitation) a smart watch, a smart phone, a tablet, a laptop, a desktop computer, etc. Additionally, in some embodiments, the real-time status information in status report 312 is provided via a database, where a user can log in to view or read the status information, allowing all key personnel to know in real-time which systems are on / active and which systems are off / deactivated / locked out.

[0049]

[0053] Additionally, the control module 320 can send an alert 314 to one or more of the user devices 140. In some embodiments, the alert 314 is sent to all personnel involved in manufacturing, testing, or maintenance, while in other embodiments, the alert 314 is sent to key personnel (e.g., with primary or supervisory responsibility) or personnel on a project or task basis (e.g., personnel involved in a project or task involving interaction with or exposure to a particular HE system). The alert 314 provides information of higher priority or urgency than the status report 312, such as, for example, information regarding the target state of one or more of the HE systems, or one or more control actions, work scheduling changes, or conflicting activation and / or deactivation of an HE system (e.g., potentially related to work scheduling or delays). Such conflicts may include potential conflicts (e.g., conflicts that have not yet occurred) and may result from work scheduling, including delays in starting or completing a particular task, or inadvertent human error, or system failure, etc.

[0050]

[0054] As one example, key personnel may be alerted by sending an alert 314 when two conflicting HE systems are about to be activated simultaneously. In such a case, the control module 320 will issue one or more control actions 340 to deactivate (or prevent activation of) at least one of the conflicting HE systems according to the HE system rules 330. Information identifying the conflict (including potential conflicts) is provided by the control module 320 to the process module 310. As another example, the alert 314 will be issued (e.g., sent) when the work of one HE system is delayed and then conflicts with the work of another HE system. In some examples, the alert also provides information regarding missing sensor data (e.g., data that was expected but not received from any particular sensor).

[0051]

[0055] The control module 320 receives one or more selections / commands 322 from one or more user devices. Although the status reports 312 and alerts 314 may be sent to any personnel (e.g., based on proximity to one of the HE systems), issuance of the one or more selections / commands 322 is typically limited to only certain authorized personnel, such as an operations manager or team leader with supervisory responsibilities. The selections / commands 322 may be issued by an authorized user via a user device in response to the status reports 312 and / or alerts 314. For example, an authorized user may issue a command 322 to cancel or reschedule an operation. This results in the control module applying the HE system rules 330 to issue a control action 340 to effect the scheduling change. As another example, an authorized user may issue a command 322 to override a control module decision to activate or deactivate a particular HE system, such as an emergency shutdown command to deactivate an HE system.

[0052]

[0056] In some embodiments, authorized personnel may issue commands to activate or deactivate any HE system on the aircraft. In some embodiments, the selection / command(s) 322 are issued by an authorized user via an operational system (e.g., operational system 145 of FIGS. 1A and 2A ). For example, based on receipt of the command 322, the control module 320 issues new or modified control actions 340 to one or more of the HE systems 120. In this manner, the control module 320 modifies one of the one or more control actions 340 based on the command 322.

[0053]

[0057] The process module 310 and the control module 320 operate continuously in a coordinated manner, enabling the high energy management system controller 300, via the process module 310, to actively monitor all HE systems on the aircraft, and, via the control module 320, to provide continuous real-time status reporting and alerts, and to actively provide real-time control to avoid conflicts in the activation of the HE systems.

[0054]

[0058] Some or all of the components in the high energy management system controller 300 may be implemented using one or more of a CPU, a GPU, an AI accelerator, an FPGA accelerator, an ASIC, and / or via a processor with software, or in a combination of a processor with software and an FPGA or an ASIC. In particular, the components of the high energy management system controller 300 may be implemented in one or more modules, as a set of program or logic instructions stored in a machine or computer readable storage medium, such as a RAM, a ROM, a PROM, firmware, a flash memory, or the like, as hardware, or a combination thereof. For example, a hardware implementation may include configurable logic, fixed function logic, or any combination thereof. Examples of configurable logic include appropriately configured PLAs, FPGAs, CPLDs, and general purpose microprocessors. Examples of fixed function logic include appropriately configured ASICs, combinational logic circuits, and sequential logic circuits. Configurable or fixed function logic may be implemented in CMOS logic circuits, TTL logic circuits, or other circuits.

[0055]

[0059] For example, computer program code for executing operations by the high energy management system controller 300 may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, JavaScript, Python, C#, C++, Perl, Smalltalk, and conventional procedural programming languages, such as the "C" programming language or a similar programming language. Furthermore, the program or logic instructions may include assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, configurable data for integrated circuits, state information to personalize electronic circuits, and / or other structural components native to the hardware (e.g., a host processor, central processing unit / CPU, microcontroller, etc.).

[0056]

[0060] 4A-4B provide a flow diagram illustrating an exemplary method 400 (including process components 400A and 400B) of controlling a high energy management system according to one or more embodiments, with reference to components and features described herein, including but not limited to the drawings and related descriptions. The method 400 may generally be implemented in the high energy management system 100 (FIGS. 1A-1B, previously described), the high energy management system 200 (FIGS. 2A-2B, previously described), and / or performed via the high energy management system controller 300 (FIG. 3, previously described) or components thereof. In particular, the method 400 may be implemented in one or more modules, as a set of logical instructions stored in a machine or computer readable storage medium, such as RAM, ROM, PROM, firmware, flash memory, etc., as hardware, or a combination thereof. For example, a hardware implementation may include configurable logic, fixed function logic, or any combination thereof. Examples of configurable logic include appropriately configured PLAs, FPGAs, CPLDs, and general purpose microprocessors. Examples of fixed-function logic include appropriately configured ASICs, combinatorial logic circuits, and sequential logic circuits. Configurable or fixed-function logic may be implemented in CMOS logic circuits, TTL logic circuits, or other circuits.

[0057]

[0061] For example, computer program code for performing the acts illustrated in method 400 and / or functions associated therewith may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, JavaScript, Python, C#, C++, Perl, Smalltalk, etc., and conventional procedural programming languages, such as the "C" programming language or a similar programming language. Furthermore, the program or logic instructions may include assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, state setting data, configurable data for integrated circuits, state information for personalizing electronic circuits, and / or other structural components native to hardware (e.g., a host processor, a central processing unit / CPU, a microcontroller, etc.).

[0058]

[0062] 4A, illustrated process block 410a provides for receiving sensor data from a plurality of high energy (HE) systems, where each of the plurality of HE systems is disposed within the aircraft, at block 410b. Illustrated process block 420 provides for determining a current state of each of the plurality of HE systems based on the sensor data. Illustrated process block 430 provides for determining a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules. Illustrated process block 440 provides for automatically generating one or more control actions for controlling one or more of the plurality of HE systems based on the target state of each of the plurality of HE systems.

[0059]

[0063] In some embodiments, the set of HE system rules includes rules for identifying conditions for activating or deactivating each one of the multiple HE systems and one or more of rules specifying which of the multiple HE systems may be active with each other, which HE systems must be active with another one of the multiple HE systems, or which HE systems may not be active with each other. In some embodiments, the rules specifying conditions for activating or deactivating each one of the multiple HE systems include one or more of rules specifying an order for activating or deactivating a subset of the multiple HE systems or rules specifying timing requirements associated with activating or deactivating each one of the multiple HE systems. In some embodiments, active control of the multiple HE systems is conditioned on a determination that the aircraft is in a ground state. In some embodiments, the multiple HE systems include one or more HE systems selected from the group including an electrical system, a hydraulic system, a propulsion system, a cockpit power system, a payload and weapons system, or a fuel system.

[0060]

[0064] 4B , in some embodiments, illustrated process block 450a provides for receiving a schedule of actions (e.g., actions for a high energy system) to be performed on the aircraft. Then, in block 450b, determining a target state of each of the plurality of HE systems is further based on the schedule of actions. In some embodiments, rules specifying conditions for activating or deactivating each one of the plurality of HE systems are based on the one or more identified actions. In some embodiments, illustrated process block 460a provides for sending an alert to a user device. Then, in block 460b, the alert is based on one or more of a target state of one or more of the plurality of HE systems, one or more control actions, or conflicting activation or deactivation of an HE system.

[0061]

[0065] In some embodiments, illustrated process block 470 provides for receiving a command associated with one of the plurality of HE systems from a user device. Illustrated process block 475 provides for modifying one of the one or more control operations based on the command. In some embodiments, the command is received from a user device of a user authorized to issue the command. In some embodiments, illustrated process block 480 includes providing information regarding a current state of the plurality of HE systems for display on the user device.

[0062]

[0066] 5 provides a block diagram illustrating one embodiment of a computing system 10 used to control an advanced energy management system according to one or more embodiments, with reference to the components and features described herein, including but not limited to the drawings and related description. In some embodiments, the computing system 10 corresponds to or implements all or part of the advanced energy management system 100 (FIGS. 1A-1B, previously described), the advanced energy management system controller 110 (FIGS. 1A-1B, previously described), all or part of the advanced energy management system 200 (FIGS. 2A-2B, previously described), and / or the advanced energy management system 300 (FIG. 3, previously described). Although FIG. 5 illustrates certain components, the computing system 10 may include additional or multiple components connected in various ways. It is understood that not all embodiments need include all components illustrated in FIG. 5. The computing system 10 includes one or more processors 22. In some embodiments, computing system 10 also includes an input / output (I / O) subsystem 24, a network interface 26, memory 28, data storage 30, a user interface 32, and / or a sensor interface 34. Computer system 10 may also include a display 38. These components are coupled, connected, or otherwise in data communication via an interconnect 36. In some embodiments, computing system 10 may interact with a separate display, such as, for example, a display installed as original equipment in an aircraft.

[0063]

[0067] The processor 22 includes one or more processing devices, such as a microprocessor, a fixed application specific integrated circuit (ASIC) processor, a reduced instruction set computer (RISC) processor, a complex instruction set computing (CISC) processor, a field programmable gate array (FPGA), a digital signal processor (DSP), etc., along with associated circuits, logic, and / or interfaces. The processor 22 may include or be connected to a memory (e.g., memory 28, etc.) that stores executable instructions and / or data, as necessary or appropriate. The processor 22 executes such instructions to implement the high energy management system 100, the high energy management system controller 110, the high energy management system 200, and / or the high energy management system 300, and / or any of the devices, features, or methods described herein with reference to Figures 1A-1B, 2A-2B, 3, and / or 4A-4B. Processor 22 may communicate or send / receive messages, requests, notifications, data, etc. to / from other devices, such as the devices shown in Figures 1A-1B, 2A-2B, and / or 3. Processor 22 may be embodied as any type of processor capable of performing the functions described herein. For example, processor 22 may be embodied as a single or multi-core processor(s), digital signal processor, microcontroller, or other processor or processing / control circuitry. Processor 22 may include embedded instructions (e.g., processor code).

[0064]

[0068] I / O subsystem 24 includes suitable circuits and / or components to facilitate input / output operations with processor 22, memory 28, and other components of computing system 10.

[0065]

[0069] Network interface 26 includes appropriate logic, circuitry, and / or interfaces to transmit and receive data over one or more communication networks using one or more communication network protocols. Network interface 26 may operate under the control of processor 22 and may transmit and receive various requests and messages to and from one or more other devices (e.g., any one or more of the devices shown in FIGS. 1A-1B, 2A-2B, and / or 3). Network interface 26 may include wired and / or wireless data communication capabilities that may support data communication with wired and / or wireless communication networks, such as network 27, as well as the Internet, a wide area network (WAN), a local area network (LAN), a wireless personal area network, a wide body area network, a cellular network, a telephone network, any other wired and / or wireless network for transmitting and receiving data signals, or any combination thereof (including, for example, a Wi-Fi network or a corporate LAN). Network interface 26 may support communication over short-range wireless communication fields, such as Bluetooth, Near Field Communication (NFC), or Radio Frequency Identification (RFID). Examples of network interface 26 include, but are not limited to, an antenna, a radio frequency transceiver, a wireless transceiver, a Bluetooth transceiver, an Ethernet port, a Universal Serial Bus (USB) port, or any other device configured to transmit and receive data.

[0066]

[0070] The memory 28 includes suitable logic, circuits, and / or interfaces for storing executable instructions and / or data necessary or suitable for, when executed, to implement, control, operate, or interact with any device or feature of the high energy management system 100, the high energy management system controller 110, the high energy management system 200, and / or the high energy management system 300, and / or any of the devices, features, or methods described herein with reference to Figures 1A-1B, 2A-2B, 3, and / or 4A-4B. The memory 28 may be embodied as any type of volatile or non-volatile memory or data storage capable of performing the functions described herein, and may include random access memory (RAM), read-only memory (ROM), write-once-read-many-time memory (e.g., electrically erasable programmable read-only memory (EEPROM), etc.), removable storage drive, hard disk drive (HDD), flash memory, solid-state memory, etc., including any combination thereof. In operation, memory 28 may store various data and software used during operation of computing system 10, such as an operating system, applications, programs, libraries, and drivers. Memory 28 may be communicatively coupled to processor 22 either directly or through I / O subsystem 24.

[0067]

[0071] Data storage 30 may include any type of one or more devices configured for short-term or long-term storage of data, such as, for example, memory devices and circuitry, memory cards, hard disk drives, solid state drives, non-volatile flash memory, or other data storage devices. Data storage 30 may include or be configured as a database, such as a relational or non-relational database, or a combination of two or more databases. In some embodiments, a database or other data storage may be physically separate and / or remote from computing system 10 and / or may be located within another computing device, a database server, a cloud-based platform, or any storage device in data communication with computing system 10.

[0068]

[0072] User interface 32 includes code for presenting information or screens for a user (e.g., a user using a user device) on a display and for receiving input (including commands) from a user via an input device (e.g., a touch screen device). User interface 32 may include a graphical user interface (GUI).

[0069]

[0073] The sensor interface 34 includes circuitry and / or components suitable for facilitating communication and / or exchange of data, commands, or signals between the computing device 10 and one or more sensors. The one or more sensors may include one or more of the sensors 122 and / or one or more of the actuators 124 (FIGS. 1B and 2B, previously described). The sensor interface 34 may act in coordination with the network interface 26 in establishing communication with the one or more sensors.

[0070]

[0074] Interconnect 36 may include any one or more separate physical buses, point-to-point connections, or both connected by appropriate bridges, adapters, or controllers. Interconnect 36 may include, for example, a system bus, a Peripheral Component Interconnect (PCI) bus, a HyperTransport or other industry standard architecture bus, a Small Computer System Interface (SCSI) bus, a Universal Serial Bus (USB), an Inter-Integrated Circuit (I2C) bus, or an Institute of Electrical and Electronics Engineers (IEEE) standard 694 bus (e.g., “Firewire”), or other interconnect suitable for coupling or connecting components of computing system 10.

[0071]

[0075] Display 38 may be any type of device for presenting visual information, such as a computer monitor, a flat panel display, or a mobile device screen, and may include a liquid crystal display (LCD), a light emitting diode (LED) display, a plasma panel, or a cathode ray tube display, etc. Display 38 may include a display interface for communicating with a display. In some embodiments, display 38 may include a display interface for communicating with a display external to computing system 10 (e.g., a user device).

[0072]

[0076] In some embodiments, one or more of the illustrative components of computing device 10 may be incorporated (in whole or in part) within or otherwise form a part of another component. For example, memory 28, or portions thereof, may be incorporated within processor 22. As another example, user interface 32 may be incorporated within code within processor 22 and / or memory 28. In some embodiments, computing system 10 may be embodied as, without limitation, a portable computing device, a smartphone, a wearable computing device, an Internet of Things device, a laptop computer, a tablet computer, a notebook computer, a computer, a workstation, a server, a multiprocessor system, and / or a consumer electronics device. In some embodiments, computing system 10, or portions thereof, are implemented in one or more modules as a set of logical instructions stored in at least one non-transitory machine- or computer-readable storage medium, such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), firmware, flash memory, etc.; in configurable logic, such as, for example, a programmable logic array (PLA), a field programmable gate array (FPGA), a complex programmable logic device (CPLD), etc.; in fixed-function logic hardware using circuit technology, such as, for example, application specific integrated circuit (ASIC), complementary metal oxide semiconductor (CMOS), or transistor-transistor (TTL) technology, or any combination thereof.

[0073]

[0077] The systems, devices, components, features, and / or methods described above, including the high energy management system 100, the high energy management system controller 110, the high energy management system 200, the aircraft interface module 210, the high energy management system 300, the method 400, and / or any other system components, may be implemented as hardware, software, or any other suitable combination thereof. For example, a hardware implementation may include configurable logic, fixed function logic, or any combination thereof. Examples of configurable logic include appropriately configured PLAs, FPGAs, CPLDs, and general purpose microprocessors. Examples of fixed function logic include appropriately configured ASICs, combinational logic circuits, and sequential logic circuits. The configurable or fixed function logic may be implemented in CMOS logic circuits, TTL logic circuits, or other circuits.

[0074]

[0078] Alternatively or in addition, all or portions of the aforementioned systems, devices, components, features, and / or methods may be implemented in one or more modules as a set of program or logical instructions stored in a machine or computer readable storage medium, such as a RAM, ROM, PROM, firmware, flash memory, etc., for execution by a processor or computing device. For example, computer program languages ​​for performing the operations of the components may be written in any combination of one or more operating system (OS) applicable / suitable programming languages, including object-oriented programming languages, such as Java, JavaScript, PYTHON, C#, C++, Perl, SMALLTALK, etc., and conventional procedural programming languages, such as the "C" programming language or similar programming languages.

[0075]

[0079] Further Notes and Examples

[0076]

[0080] Furthermore, the present disclosure includes further embodiments that are described in detail in the following sections.

[0077]

[0081] Article M1. 1. A method for controlling an advanced energy management system, comprising: receiving sensor data from a plurality of high energy (HE) systems, each of the plurality of HE systems being disposed within an aircraft; determining a current state of each of the plurality of HE systems based on the sensor data; determining a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and The method includes automatically generating one or more control actions for controlling one or more of the plurality of HE systems based on the target state of each of the plurality of HE systems.

[0078]

[0082] Article M2. The set of HE system rules comprises: rules specifying conditions for activating or deactivating each one of the plurality of HE systems; and rules that specify which of the plurality of HE systems may be active with each other; a rule specifying which of the plurality of HE systems should be active with another of the plurality of HE systems; or rules specifying which of the plurality of HE systems cannot be active with each other; The method of claim M1, comprising one or more of:

[0079]

[0083] Clause M3. rules specifying conditions for activating or deactivating each one of the plurality of HE systems; rules specifying an order for activating or deactivating a subset of the plurality of HE systems; or rules specifying timing requirements associated with activating or deactivating any one of the plurality of HE systems; The method of any one of clauses M1 or M2, comprising one or more of:

[0080]

[0084] Article M4. receiving a schedule of operations to be performed on the aircraft; The method of any one of clauses M1 to M3, wherein determining the target state of each of the plurality of HE systems is further based on a schedule of the operations.

[0081]

[0085] Article M5. The method of any one of clauses M1 to M4, wherein the rules specifying conditions for activating or deactivating each one of the plurality of HE systems are based on one or more specified actions.

[0082]

[0086] Article M6. The method of any one of clauses M1 to M5, wherein active control of the plurality of HE systems is conditioned on determining that the aircraft is in a ground state.

[0083]

[0087] Article M7. The method of any one of clauses M1 to M6, further comprising sending an alert to a user device, the alert being based on one or more of the target states of one or more of the plurality of HE systems, the one or more control actions, or conflicting activation or deactivation of an HE system.

[0084]

[0088] Article M8. receiving a command associated with one of the plurality of HE systems from a user device; and The method of any one of clauses M1 to M7, further comprising modifying one of the one or more control actions based on the command.

[0085]

[0089] Article M9. The method of any one of clauses M1 to M8, further comprising providing information regarding the current state of the plurality of HE systems for display on a user device.

[0086]

[0090] Article M10. The method of any one of clauses M1 to M9, wherein the plurality of HE systems includes one or more HE systems selected from the group including electrical systems, hydraulic systems, propulsion systems, cockpit power systems, payload and weapons systems, or fuel systems.

[0087]

[0091] Article S1. A processor, 1. An advanced energy management system controller comprising a memory coupled to the processor, the memory including instructions that, when executed by the processor, cause the advanced energy management system controller to: receiving sensor data from a plurality of high energy (HE) systems, each of the plurality of HE systems being disposed within an aircraft; determining a current state of each of the plurality of HE systems based on the sensor data; determining a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and and automatically generating one or more control actions for controlling one or more of the plurality of HE systems based on the target state of each of the plurality of HE systems.

[0088]

[0092] Clause S2. The set of HE system rules comprises: rules specifying conditions for activating or deactivating each one of the plurality of HE systems; and rules that specify which of the plurality of HE systems may be active with each other; a rule specifying which of the plurality of HE systems should be active with another of the plurality of HE systems; or rules specifying which of the plurality of HE systems cannot be active with each other; The high energy management system controller of clause S1, including one or more of:

[0089]

[0093] Article S3. rules specifying conditions for activating or deactivating each one of the plurality of HE systems; rules specifying an order for activating or deactivating a subset of the plurality of HE systems; or rules specifying timing requirements associated with activating or deactivating any one of the plurality of HE systems; The high energy management system controller of clause S1 or S2, comprising one or more of:

[0090]

[0094] Article S4. The instructions, when executed, cause the advanced energy management system controller to: receiving a schedule of operations to be performed on the aircraft; The high energy management system controller of any one of clauses S1 to S3, wherein determining the target state of each of the plurality of HE systems is further based on a schedule of the operations.

[0091]

[0095] Article S5. The high energy management system controller of any one of clauses S1 to S4, wherein the rules specifying the conditions for activating or deactivating each one of the plurality of HE systems are based on one or more specified actions.

[0092]

[0096] Clause S6. The high energy management system controller of any one of clauses S1 to S5, wherein active control of the plurality of HE systems by the high energy management system controller is conditioned on a determination that the aircraft is in a ground state.

[0093]

[0097] Article S7. The instructions, when executed, cause the advanced energy management system controller to: The high energy management system controller of any one of clauses S1 to S6, further comprising: sending an alert to a user device, the alert being based on one or more of the target states of one or more of the plurality of HE systems, the one or more control actions, or conflicting activation or deactivation of an HE system.

[0094]

[0098] Article S8. The instructions, when executed, cause the advanced energy management system controller to: receiving a command associated with one of the plurality of HE systems from a user device; and The high energy management system controller of any one of clauses S1 to S7, further performing an action based on the command, including modifying one of the one or more control actions.

[0095]

[0099] Article S9. The instructions, when executed, cause the advanced energy management system controller to: The high energy management system controller of any one of clauses S1 to S8, further comprising: providing information regarding the current state of the plurality of HE systems for display on a user device.

[0096]

[0100] Article S10. The high energy management system controller of any one of clauses S1 to S9, wherein the plurality of HE systems includes one or more HE systems selected from the group including electrical systems, hydraulic systems, propulsion systems, cockpit power systems, payload and weapons systems, or fuel systems.

[0097]

[0101] Article C1. At least one computer-readable storage medium containing instructions that, when executed by a processor, cause a high energy management system to: receiving sensor data from a plurality of high energy (HE) systems, each of the plurality of HE systems being disposed within an aircraft; determining a current state of each of the plurality of HE systems based on the sensor data; determining a target state of each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and and automatically generating, based on the target state of each of the plurality of HE systems, one or more control actions for controlling one or more of the plurality of HE systems.

[0098]

[0102] Article C2. The set of HE system rules comprises: rules specifying conditions for activating or deactivating each one of the plurality of HE systems; and rules that specify which of the plurality of HE systems may be active with each other; a rule specifying which of the plurality of HE systems should be active with another of the plurality of HE systems; or rules specifying which of the plurality of HE systems cannot be active with each other; At least one computer-readable storage medium as described in clause C1, comprising one or more of:

[0099]

[0103] Article C3. rules specifying conditions for activating or deactivating each one of the plurality of HE systems; rules specifying an order for activating or deactivating a subset of the plurality of HE systems; or rules specifying timing requirements associated with activating or deactivating any one of the plurality of HE systems; At least one computer-readable storage medium according to clause C1 or C2, comprising one or more of:

[0100]

[0104] Article C4. The instructions, when executed, cause the high energy management system to: receiving a schedule of operations to be performed on the aircraft; At least one computer-readable storage medium according to any one of clauses C1 to C3, wherein determining the target state of each of the plurality of HE systems is further based on a schedule of the operations.

[0101]

[0105] Article C5. At least one computer-readable storage medium of any one of clauses C1 to C4, wherein the rules specifying conditions for activating or deactivating each one of the plurality of HE systems are based on one or more specified actions.

[0102]

[0106] Clause C6. At least one computer-readable storage medium of any one of clauses C1 to C5, wherein active control of the plurality of HE systems by the high energy management system controller is conditioned on a determination that the aircraft is in a ground state.

[0103]

[0107] Article C7. The instructions, when executed, cause the high energy management system to: At least one computer-readable storage medium of any one of clauses C1 to C6, further comprising: sending an alert to a user device, the alert being based on one or more of the target states of one or more of the plurality of HE systems, the one or more control actions, or conflicting activation or deactivation of an HE system.

[0104]

[0108] Article C8. The instructions, when executed, cause the high energy management system to: receiving a command associated with one of the plurality of HE systems from a user device; and At least one computer-readable storage medium of any one of clauses C1 to C7, further performing an action including modifying one of the one or more control actions based on the command.

[0105]

[0109] Article C9. The instructions, when executed, cause the high energy management system to: At least one computer-readable storage medium of any one of clauses C1 to C8, further comprising: providing information regarding the current state of the plurality of HE systems for display at a user device.

[0106]

[0110] Article C10. At least one computer-readable storage medium of any one of clauses C1 to C9, wherein the plurality of HE systems includes one or more HE systems selected from the group including electrical systems, hydraulic systems, propulsion systems, cockpit power systems, payload and weapons systems, or fuel systems.

[0107]

[0111] Article A1. Apparatus comprising means for carrying out the method according to any one of clauses M1 to M10.

[0108]

[0112] The embodiments are applicable for use with all kinds of semiconductor integrated circuit ("IC") chips. Examples of these IC chips include, but are not limited to, processors, controllers, chipset components, programmable logic arrays (PLAs), memory chips, network chips, systems on chips (SoCs), solid state drives (SSDs) / NAND controller ASICs, and the like. Additionally, in some of the figures, signal conductor lines are represented as lines. Some may differ to show more constituent signal paths, have number labels to indicate the number of constituent signal paths, and / or have arrows on one or more ends to indicate the direction of primary information flow. However, this should not be construed in a limiting manner. Rather, such additional details may be used in connection with one or more exemplary embodiments to facilitate easier understanding of the circuit. Any represented signal line may in fact include one or more signals that may travel in multiple directions, with or without further information. The signal lines may be implemented with any kind of suitable signaling scheme, for example, digital or analog lines implemented with differential pairs, fiber optic lines, and / or single-ended lines.

[0109]

[0113] Although example sizes / models / values / ranges may be given, the examples are not limited thereto. It is expected that smaller sized devices can be manufactured as manufacturing techniques (e.g., photolithography) mature over time. In addition, well-known power / ground connections to IC chips and other components may or may not be shown in the drawings for the sake of simplicity of illustration and explanation, and not to obscure certain aspects of the examples. Furthermore, layouts may be illustrated as block forms, in order to avoid obscuring the examples, and to take into account the fact that specific details regarding the implementation of such block diagram layouts are highly dependent on the platform on which the examples are implemented. That is, such specific details should be well within the purview of those skilled in the art. Where specific details (e.g., circuits) are described to explain the example examples, it should be apparent to one skilled in the art that the examples can be practiced without these specific details or with variations thereof. Thus, the description should be considered as illustrative and not restrictive.

[0110]

[0114] The term "coupled" may be used to refer to any type of direct or indirect relationship between the components in question, and may apply to electrical, mechanical, fluid, optical, electromagnetic, electromechanical, or other connections, including logical connections through intermediate components (e.g., device A may be coupled to device C through device B). Additionally, the terms "first," "second," etc. may be used for ease of description only and may not have any particular temporal or chronological significance unless otherwise indicated.

[0111]

[0115] As used in the specification and claims, a list of items joined by the term "one or more of" may mean any combination of the listed items. For example, the phrase "one or more of A, B, or C" may mean A, B, C, A and B, A and C, B and C, or A, B, and C.

[0112]

[0116] From the foregoing description, those skilled in the art will appreciate that the broad techniques of the embodiments can be implemented in a variety of forms. Thus, although the embodiments have been described in the context of specific embodiments thereof, the true scope of the embodiments should not be so limited, as other variations will be apparent to those skilled in the art upon review of the drawings, the specification, and the following claims.

Claims

1. A method (400) for controlling an advanced energy management system (100), comprising: receiving sensor data (305) from a plurality of high energy (HE) systems (120), each of the plurality of HE systems being disposed within an aircraft; determining a current state of each of the plurality of HE systems (120) based on the sensor data (305); determining a target state for each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and A method (400) comprising automatically generating one or more control actions (340) for controlling one or more of the plurality of HE systems (120) based on the target state of each of the plurality of HE systems (120).

2. The set of HE system rules (330) comprises: rules specifying conditions for activating or deactivating each one of the plurality of HE systems (120); and rules that specify which of the plurality of HE systems (120) may be active with one another; a rule specifying which of the plurality of HE systems (120) should be active with another one of the plurality of HE systems (120); or rules that specify which of the plurality of HE systems (120) cannot be active with each other; The method of claim 1 , comprising one or more of:

3. A rule specifying a condition for activating or deactivating the any one of the plurality of HE systems, a rule specifying an order for activating or deactivating a subset of the plurality of HE systems (120); or rules specifying timing requirements associated with activating or deactivating any one of the plurality of HE systems (120); The method of claim 2 , comprising one or more of:

4. receiving a schedule (130) of work to be performed on the aircraft; 4. The method of claim 3, wherein determining the target state for each of the plurality of HE systems is further based on a schedule of operations.

5. 5. The method of claim 4, wherein the rules specifying conditions for activating or deactivating the any one of the plurality of HE systems are based on one or more specified actions.

6. 2. The method (400) of claim 1, wherein active control of the plurality of HE systems (120) is conditioned on determining that the aircraft is in a ground state.

7. 2. The method (400) of claim 1, further comprising sending an alert (314) to a user device (140), the alert (314) being based on one or more of the target states of one or more of the plurality of HE systems (120), the one or more control actions (340), or conflicting activation or deactivation of an HE system (120).

8. receiving a command (322) associated with one of the plurality of HE systems (120) from a user device (140); and The method (400) of claim 1, further comprising modifying one of the one or more control actions (340) based on the command (322).

9. The method of claim 1 , further comprising providing information regarding the current state of the plurality of HE systems for display on a user device.

10. 2. The method of claim 1, wherein the plurality of HE systems comprises one or more HE systems selected from the group including electrical systems, hydraulic systems, propulsion systems, cockpit power systems, payload and weapons systems, or fuel systems.

11. A processor (22), and An advanced energy management system controller (300) comprising a memory (28) coupled to the processor (22), the memory including instructions that, when executed by the processor (22), cause the advanced energy management system controller (300) to: receiving sensor data (305) from a plurality of high energy (HE) systems (120), each of the plurality of HE systems being disposed within an aircraft; determining a current state of each of the plurality of HE systems (120) based on the sensor data (305); determining a target state for each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and and a high energy management system controller (300) that performs operations including automatically generating one or more control actions (340) for controlling one or more of the plurality of HE systems (120) based on the target state of each of the plurality of HE systems (120).

12. The set of HE system rules (330) comprises: rules specifying conditions for activating or deactivating each one of the plurality of HE systems (120); and rules that specify which of the plurality of HE systems (120) may be active with one another; a rule specifying which of the plurality of HE systems (120) should be active with another one of the plurality of HE systems (120); or rules that specify which of the plurality of HE systems (120) cannot be active with each other; and The rules specifying conditions for activating or deactivating the any one of the plurality of HE systems (120) include: a rule specifying an order for activating or deactivating a subset of the plurality of HE systems (120); or rules specifying timing requirements associated with activating or deactivating any one of the plurality of HE systems (120); The high energy management system controller (300) of claim 11, comprising one or more of:

13. The instructions, when executed, cause the advanced energy management system controller to: receiving a schedule of operations to be performed on the aircraft; determining the target state of each of the plurality of HE systems is further based on a schedule of operations; The high energy management system controller (300) of claim 12, wherein the rules specifying conditions for activating or deactivating the any one of the plurality of HE systems are based on one or more specified actions.

14. 12. The high energy management system controller (300) of claim 11, wherein active control of the plurality of HE systems (120) by the high energy management system controller (300) is conditioned on a determination that the aircraft is in a ground state.

15. The instructions, when executed, cause the advanced energy management system controller (300) to: sending an alert (314) to a user device (140), the alert (314) being based on one or more of the target states of one or more of the plurality of HE systems (120), the one or more control actions (340), or conflicting activation or deactivation of an HE system (120); receiving a command (322) from the user device (140) associated with one of the plurality of HE systems (120); modifying one of the one or more control actions (340) based on the command (322); and The high energy management system controller (300) of claim 11, further comprising: providing information regarding the current status of the plurality of HE systems (120) for display on the user device (140).

16. At least one computer readable storage medium (28) containing instructions that, when executed by the processor (22), cause the high energy management system controller (300) to: receiving sensor data (305) from a plurality of high energy (HE) systems (120), each of the plurality of HE systems being disposed within an aircraft; determining a current state of each of the plurality of HE systems (120) based on the sensor data (305); determining a target state for each of the plurality of HE systems based on the current state of each of the plurality of HE systems and a set of HE system rules; and and automatically generating, based on the target state of each of the plurality of HE systems, one or more control actions (340) for controlling one or more of the plurality of HE systems.

17. The set of HE system rules (330) comprises: rules specifying conditions for activating or deactivating each one of the plurality of HE systems (120); and rules that specify which of the plurality of HE systems (120) may be active with one another; a rule specifying which of the plurality of HE systems (120) should be active with another one of the plurality of HE systems (120); or rules that specify which of the plurality of HE systems (120) cannot be active with each other; and The rules specifying conditions for activating or deactivating the any one of the plurality of HE systems (120) include: a rule specifying an order for activating or deactivating a subset of the plurality of HE systems (120); or rules specifying timing requirements associated with activating or deactivating any one of the plurality of HE systems (120); 17. At least one computer readable storage medium (28) according to claim 16, comprising one or more of:

18. The instructions, when executed, cause the advanced energy management system controller to: receiving a schedule of operations to be performed on the aircraft; determining the target state of each of the plurality of HE systems is further based on a schedule of operations; 20. The at least one computer-readable storage medium (28) of claim 17, wherein the rules specifying conditions for activating or deactivating the any one of the plurality of HE systems are based on one or more specified actions.

19. 20. The at least one computer-readable storage medium of claim 16, wherein active control of the plurality of HE systems by the high energy management system controller is conditioned on a determination that the aircraft is in a ground state.

20. The instructions, when executed, cause the advanced energy management system controller (300) to: sending an alert (314) to a user device (140), the alert (314) being based on one or more of the target states of one or more of the plurality of HE systems (120), the one or more control actions (340), or conflicting activation or deactivation of an HE system (120); receiving a command (322) from the user device (140) associated with one of the plurality of HE systems (120); modifying one of the one or more control actions (340) based on the command (322); and 20. The at least one computer-readable storage medium (28) of claim 16, further comprising: providing information regarding the current status of the plurality of HE systems (120) for display on the user device (140).

Images