Patent Description:
Large scale electrical systems such as an electrical system in an aircraft, ship, building, factory, town and city may change significantly over a life of the electrical system. Components may be added, deleted, and changed over the life of the electrical system. Such changes to the electrical system may increase or decrease a load on various parts of the electrical system, may require changes in electrical system architecture, and may necessitate changes in other components of the electrical system.

"<NPL>) describes the use of an ELA software tool to model and visualize electrical loads within an aircraft.

"<NPL>) describes military specification for analysis of electric load and power source capacity for aircraft.

"<NPL>) describes guidance for electrical load and power source capacity analysis as required by Civil Aviation Requirements.

An electrical load life-cycle management and analysis system and method are disclosed. In the system and method, a database module stores electrical system configuration data and electrical system requirements, and an electrical system analysis module determines electrical system performance characteristics as a function of and based on the electrical system configuration data. In addition, an electrical system configuration management module manages at least one change to the electrical system configuration data, and compares the electrical system performance characteristics to the electrical system requirements to enable optimal performance and to provide compliance information.

In this manner, embodiments of the disclosure provide a system and method to allow users/operators to easily and efficiently manage and analyze an electrical loading on a power distribution system from design to retirement of an electrical system such as an airframe, and minimizing cost of electrical load analysis while meeting total system safety constraints. For example, the operators can use communication interfaces to manage electrical loading during the design, manufacturing, delivery, and post delivery to ensure adequate electrical load is provided for certain operation thereby preventing non-optimal operation, and the like.

In an embodiment, an electrical load life-cycle management and analysis system comprises a database module operable to store electrical system configuration data and electrical system requirements. The system further comprises an electrical system analysis module operable to determine electrical system performance characteristics as a function of the electrical system configuration data. The system further comprises an electrical system configuration management module which manages at least one change to the electrical system configuration data, and compares the electrical system performance characteristics to the electrical system requirements to enable optimal performance.

In another embodiment, a method for electrical load life-cycle management and analysis comprises stores electrical system configuration data and electrical system requirements in a database. The method further determines electrical system performance characteristics as a function of and based on the electrical system configuration data, and compares the electrical system performance characteristics to the electrical system requirements to provide compliance information.

In yet another embodiment, a method for operating an electrical load life-cycle management and analysis system stores electrical system configuration data and electrical system requirements in a database. The method further provides a communication interface to an operator of an electrical system corresponding to the electrical system configuration data, and receives a configuration change to the electrical system from the operator via the communication interface. The method then updates the electrical system configuration data for the configuration change, and simulates electrical system performance characteristics as a function of and based on the electrical system configuration data. The method further compares the electrical system performance characteristics to the electrical system requirements to provide compliance information, and provides compliance information to the operator of the electrical system via the communication interface.

In yet another embodiment, a computer readable storage medium comprises computer-executable instructions for electrical load life-cycle management and analysis. The computer-executable instructions stores electrical system configuration data and electrical system requirements in a database. The computer-executable instructions further determines electrical system performance characteristics as a function of and based on the electrical system configuration data, and compares the electrical system performance characteristics to the electrical system requirements to provide compliance information.

A more complete understanding of embodiments of the present disclosure may be derived by referring to the detailed description and claims when considered in conjunction with the following figures, wherein like reference numbers refer to similar elements throughout the figures. The figures are provided to facilitate understanding of the disclosure without limiting the breadth, scope, scale, or applicability of the disclosure. The drawings are not necessarily made to scale.

The following detailed description is exemplary in nature and is not intended to limit the disclosure or the application and uses of the embodiments of the disclosure. Descriptions of specific devices, techniques, and applications are provided only as examples. Modifications to the examples described herein will be readily apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other examples and applications without departing from the spirit and scope of the disclosure. The present disclosure should be accorded scope consistent with the claims, and not limited to the examples described and shown herein.

Embodiments of the disclosure may be described herein in terms of functional and/or logical block components and various processing steps. For the sake of brevity, conventional techniques and components related to, power distribution systems, electrical systems, aircraft control systems, aircraft electrical systems, and other functional aspects of the systems (and the individual operating components of the systems) may not be described in detail herein. In addition, those skilled in the art will appreciate that embodiments of the present disclosure may be practiced in conjunction with a variety of circuits, and that the embodiments described herein are merely example embodiments of the disclosure.

Embodiments of the disclosure are described herein in the context of a practical non-limiting application, namely, managing an aircraft electrical system. Embodiments of the disclosure, however, are not limited to such aircraft electrical systems, and the techniques described herein may also be utilized in other applications. For example but without limitation, embodiments may be applicable to automotive vehicles, ships, buildings, hospitals, factories, spacecraft, submarines, and the like.

As would be apparent to one of ordinary skill in the art after reading this description, the following are examples and embodiments of the disclosure and are not limited to operating in accordance with these examples. Other embodiments may be utilized and structural changes may be made without departing from the scope of the exemplary embodiments of the present disclosure.

Ever increasing use of electricity to control aircraft and other complex vehicles and electrical systems, in place of prior use of mechanical and pneumatic equipment, and hydraulics requires enhanced diligence to accurately manage power distribution system loading. This requirement is especially pronounced in electrical systems that are supplied with standalone power sources, such as but without limitation, aircraft, automobiles, other mobile vehicles, and the like. Embodiments of the disclosure comprise a system and method to manage and analyze an electrical loading on a power distribution system from design to retirement of an electrical system such as an airframe. The system manages electrical loading during the design, manufacturing and delivery phases of manufacture of the electrical system. The system and method also manages electrical load changes after delivery of the electrical system (e.g., an airframe). In this manner, the system and method facilitate ownership transfer for electrical loading related elements.

Further, the system and method comprise a comprehensive electrical load management system that follows the electrical system lifecycle from design to retirement. Data, algorithms and methodologies that are used for load analysis during manufacturing and certification seamlessly follow the electrical system after delivery.

The embodiments also provide an electrical load analysis tool (eLAT). The eLAT comprises various interface pages allowing manufacturers as well as a new owner of the electrical system easily and efficiently manage the electrical load on the electrical system and, for example but without limitation, determine "what if" sceneries, add/delete electrical components to ensure adequate load is provided for certain operation thereby preventing non-optimal operation, and the like. Additionally, regulatory agencies, such as but without limitations, Federal Aviation Administration (FAA), automotive regulatory agencies, building and factory regulatory agencies, and the like, can easily and efficiently obtain and use results of the eLAT analysis for purpose of certification, compliance monitoring, and the like.

Referring more particularly to the drawings, embodiments of the disclosure may be described in the context of an aircraft manufacturing and maintenance method <NUM> (method <NUM>) as shown in <FIG> and an aircraft <NUM> as shown in <FIG>. During pre-production, the exemplary method <NUM> may include specification and design <NUM> of the aircraft <NUM> and material procurement <NUM>. During production, component and subassembly manufacturing <NUM> and system integration <NUM> of the aircraft <NUM> takes place. Thereafter, the aircraft <NUM> may go through certification and delivery <NUM> in order to be placed in service <NUM>. While in service by a customer, the aircraft <NUM> is scheduled for routine maintenance and service <NUM> (which may also include modification, reconfiguration, refurbishment, and so on).

Each of the processes of the method <NUM> may be performed or carried out by a system integrator, a third party, and/or an operator (e.g., a customer). For the purposes of this description, a system integrator may include without limitation any number of aircraft manufacturers and major-system subcontractors; a third party may include without limitation any number of vendors, subcontractors, and suppliers; and an operator may be without limitation an airline, leasing company, military entity, service organization, and the like.

As shown in <FIG>, the aircraft <NUM> produced by the exemplary method <NUM> may include an airframe <NUM> with a plurality of systems <NUM> and an interior <NUM>. Examples of high-level systems <NUM> include one or more of a propulsion system <NUM>, an electrical system <NUM>, a hydraulic system <NUM>, and an environmental system <NUM>. Any number of other systems may also be included. Although an aerospace example is shown, the embodiments of the disclosure may be applied to other industries, such as the automotive industry.

Apparatus and methods embodied herein may be employed during any one or more of the stages of the method <NUM>. For example, components or subassemblies corresponding to production process <NUM> may be fabricated or manufactured in a manner similar to components or subassemblies produced while the aircraft <NUM> is in service. Also, one or more apparatus embodiments, method embodiments, or a combination thereof may be utilized during the production stages <NUM> and <NUM>, for example, by substantially expediting assembly of or reducing the cost of an aircraft <NUM>. Similarly, one or more of apparatus embodiments, method embodiments, or a combination thereof may be utilized while the aircraft <NUM> is in service, for example and without limitation, to maintenance and service <NUM>.

<FIG> is an illustration of an electrical system <NUM> of an aircraft showing exemplary locations of power generators, power distribution lines, and power loads. The electrical system <NUM> may comprise a plurality of power generators such as a first right engine generator <NUM>, a second right engine generator <NUM>, a first left engine generator <NUM>, a second left engine generator <NUM>, a left auxiliary power unit (APU) <NUM>, and a right APU <NUM>.

The electrical system <NUM> may also comprise a high voltage AC bus <NUM> (e.g., 230V) coupled to the power generators <NUM>-<NUM>. The electrical system <NUM> may also comprise at least one auto transformer unit (ATU) <NUM> operable to transform an AC current from the high voltage AC bus <NUM> to a low voltage AC bus <NUM> (e.g., 115V). The electrical system <NUM> may also comprise at least one transformer rectifier unit (TRU) <NUM> operable to transform an AC current from the high voltage AC bus <NUM> to a low voltage DC bus <NUM> (e.g., 28V).

<FIG> is an illustration of an exemplary functional diagram of an electrical architecture <NUM> of the electrical system <NUM> of <FIG> according to an embodiment of the disclosure. The electrical architecture <NUM> comprises the power generators <NUM>-<NUM>, the high voltage AC bus <NUM>, the at least one ATU <NUM>, the at least one TRU <NUM>, the low voltage AC bus <NUM>, and the low voltage DC bus <NUM>. The electrical architecture <NUM> comprises an auto transformer rectifier unit (ATRU) <NUM> coupled to a high voltage DC bus <NUM>. The high voltage AC bus <NUM>, the low voltage DC bus <NUM>, and the high voltage DC bus <NUM> may be coupled to a plurality of loads <NUM>. The high voltage AC bus <NUM>, the low voltage DC bus <NUM> may also be coupled to one or more Remote Power Distribution Units (RPDUs) (e.g., RPDU#<NUM>,. RPDU#<NUM>) that are in turn coupled to the loads <NUM>. In practical embodiments, various loads and parts may be used.

A part may comprise, for example but without limitation, an electrical component, a fuse, a switch, a power line, an actuator, an effector, a power supply, a replacement part, a Nitrogen Generation System (NGS), and the like.

The loads <NUM> may be distributed as follows. The high voltage DC bus <NUM> may be coupled, for example but without limitation, to adjustment speed motors comprising: hydraulic Electric Motor Pump (EMP), NGS, Environmental Control System (ECS) compressors, ECS fans, engine start, and the like.

The low voltage AC bus <NUM> may be coupled to large loads (e.g., <<NUM> amps) comprising, for example but without limitation, ECS lavatory/galley fans, equipment cooling, fans, window and the like.

Similarly, the low voltage DC bus <NUM> may be coupled to large loads (e.g., > <NUM> amps) comprising, for example but without limitation, DC fuel pumps, igniters, flight deck displays, Bus Power Control Unit·(BPCUs)/ Galley Cooling Unit (GCUs), and the like.

The high voltage AC bus <NUM> may also be coupled to large loads, for example but without limitation, wing ice protection, hydraulic AC, motor pump, fuel pumps, galley ovens, cargo heaters, ECS recreation fans, and the like.

<FIG> is an illustration of an exemplary hierarchical breakdown of a hierarchical extraction <NUM> of the electrical architecture <NUM> of <FIG> according to an embodiment of the disclosure. The hierarchical extraction <NUM> (hierarchy <NUM>) may comprise a generator node <NUM> corresponding to the first right engine generator <NUM>, and coupled to a high voltage AC bus node <NUM>. The high voltage AC bus node <NUM> corresponds to the high voltage AC bus <NUM>, and is designated a parent in the hierarchy <NUM> of a high voltage DC bus node <NUM> corresponding to the high voltage DC bus <NUM>.

The high voltage AC bus node <NUM> is also designated a parent in the hierarchy <NUM> of a low voltage AC bus node <NUM> corresponding to the low voltage AC bus <NUM>. The high voltage DC bus node <NUM> is designated as a child of the high voltage AC bus node <NUM> in the hierarchy <NUM>. The low voltage AC bus node <NUM> is designated as a child of the high voltage AC bus node <NUM> in the hierarchy <NUM>. A motor controller node <NUM> corresponding to one of the loads <NUM> (<FIG>) is designated as a child of the high voltage DC bus node <NUM> and parent of none. A remote power distribution unit node <NUM> corresponding to one of the loads <NUM> is designated as a child of the low voltage AC bus node <NUM> and parent of none.

<FIG> is an illustration of an exemplary tabular database extraction <NUM> of the hierarchical extraction <NUM> of <FIG> according to an embodiment of the disclosure. The tabular database extraction <NUM> comprises the nodes <NUM>-<NUM> of the hierarchical extraction <NUM> in a tabular form <NUM>-<NUM>.

<FIG> is an illustration of an exemplary functional block diagram of a electrical load life-cycle management and analysis system <NUM> (system <NUM>) according to an embodiment of the disclosure. The system <NUM> significantly simplifies electrical load analysis of large scale system such as aircraft system, allowing users/operators to easily and efficiently manage and analyze an electrical loading on a power distribution system from design to retirement of an electrical system and minimizing cost of electrical load analysis while meeting total system safety constraints.

The system <NUM> may comprise a computer system such as, for example but without limitation, a desktop, a laptop or notebook computer, a hand-held computing device (PDA, cell phone, palmtop, etc.), a mainframe, a server, a client, or any other type of special or general purpose computing device as may be desirable or appropriate for a given application or environment. The system <NUM> generally comprises a physical housing (not shown), a processor module <NUM>, a memory module <NUM>, a database module <NUM>, an electrical system analysis module <NUM>, an electrical system configuration management module <NUM> (electrical system management module <NUM>), an interface module <NUM>, a report generation module <NUM>, and a network bus <NUM>.

The processor module <NUM> comprises processing logic that is configured to carry out the functions, techniques, and processing tasks associated with the operation of the system <NUM>. In particular, the processing logic is configured to support the electrical system management of the system <NUM> described herein. For example, the processor module controls the interface module <NUM> to present an interface thereon to present tabular and graphical information thereon.

The processor module <NUM> also accesses electrical system configuration data and electrical system requirements stored in the database module <NUM> to support functions of the system <NUM>. Further, the processor module <NUM> controls operations of electrical system management module <NUM>, and the electrical system analysis module <NUM> to enable management of the electrical system as well as to provide compliance information, whereby the system <NUM> manages the electrical system lifecycle from design to retirement.

In this manner, the processor module <NUM> enables users and operators of the eLAT to easily and efficiently manage and analyze an electrical loading on a power distribution system to optimize operation and prevent unexpected overloading of the electrical system.

The electrical system configuration data may comprise, for example but without limitation, part location data, electrical system organization data, electrical system hierarchy data, electrical system connection data, electrical system structure data, circuit diagrams, part maximum load data, part maximum current data part maximum voltage data, part service life data, and part manufacturer data.

The compliance information may comprise, for example but without limitation, data related to and or identifying: a) a part in non-compliance, b) a part drawing an excessive electrical load in an electrical system, c) a non-standard part, d) a non-recommended part, e) a part nearing an end of service life, f) a part exceeding a service life, g) all parts in compliance, and similar types of information.

The processor module <NUM> may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.

The memory module <NUM> may be a data storage area with memory formatted to support the operation of the system <NUM>. The memory module <NUM> is configured to store, maintain, and provide data as needed to support the functionality of the system <NUM> in the manner described below. In practical embodiments, the memory module <NUM> may comprise, for example but without limitation, a non-volatile storage device (non-volatile semiconductor memory, hard disk device, optical disk device, and the like), a random access storage device (for example, SRAM, DRAM), or any other form of storage medium known in the art.

The memory module <NUM> may be coupled to the processor module <NUM> and configured to store, for example but without limitation, the tabular database extraction <NUM>, in an electrical system database, such as the database module <NUM>, and the like. Additionally, the memory module <NUM> may represent a dynamically updating database containing a table for updating the database module <NUM>, and the like. The memory module <NUM> may also store, a computer program that is executed by the processor module <NUM>, an operating system, an application program, tentative data used in executing a program, and the like.

The memory module <NUM> may be coupled to the processor module <NUM> such that the processor module <NUM> can read information from and write information to the memory module <NUM>. As an example, the processor module <NUM> and memory module <NUM> may reside in respective application specific integrated circuits (ASICs). The memory module <NUM> may also be integrated into the processor module <NUM>. In an embodiment, the memory module <NUM> may comprise a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by the processor module <NUM>. The memory module comprises the database module <NUM>.

The database module <NUM> may comprise, for example but without limitation, a hierarchical database, a network database, a relational database, an object oriented database, and the like. The database module <NUM> is operable to store, for example but without limitation, the electrical system requirements, the electrical system configuration data, algorithms, methodologies, and the like, that may be used in the system <NUM>. The electrical system requirements may comprise authoritative requirements, such as but without limitation, minimum rated electrical capacities, maximum load levels, and the like. The algorithm may comprise for example but without limitation, an electrical system model and modeling, a load analysis, and the like. The methodologies may comprise for example but without limitation, part replacement information, wiring diagrams, and the like.

The configuration of the electrical system may be extracted into a data model in which the data is organized into a tree-like structure (<NUM> in <FIG>). The structure allows repeating information using parent/child relationships where each parent can have many children but each child only has one parent in a one to many ratio. Attributes of a specific record may be listed under an entity type in a tabular manner, where each individual record is represented as a row and an attribute as a column. The system <NUM>, at the time of an event, such as but without limitation, a sale, lease or transfer of an aircraft, and the like, transfers database module <NUM> comprising electrical load configuration data for one or more aircraft to a new operator identification.

The transferred electrical load configuration data may be referred to as a baseline, initial and/or delivery configuration, delivery load analysis document or other similarly identified initial data configuration. In one embodiment, the baseline electrical load configuration data may be tagged or labeled as "Delivery" to indicate that it is the delivery configuration that will be the baseline for future changes to the electrical loading for that identified aircraft. In one embodiment, the Delivery tagged data cannot be changed by future database users. In another embodiment, the Delivery tagged data can only be changed by future database users having appropriate permissions to alter, edit or otherwise change the Delivery tagged data.

The electrical system analysis module <NUM> is operable to determine electrical system performance characteristics as a function of and based on the electrical system configuration data. The electrical system performance characteristic may comprise, for example but without limitation, electrical system management data that may comprise, among other types of management information, a load on an AC bus, a load distribution analysis, a flight phase load analysis, a non-optimal condition load analysis, and a "what-if" load analysis. The "what-if" load analysis may also further comprise, for example but without limitation, simulating electrical system configuration changes, simulating part changes, simulating usage scenario changes, and the like.

The electrical system management module <NUM> is operable to manage at least one change to the electrical system configuration data, and compare the electrical system performance characteristics to the electrical system requirements to enable optimal electrical system management, and to enable optimal performance and to provide compliance information. In this manner an operator can input the at least one change using the interface module <NUM> as explained in more detail below. The electrical system management module <NUM> further provides compliance information, and generates a report based on the compliance information. The report may comprise, for example but without limitation an authoritative change, a service bulletin, a customer change, a third party change, an electrical load analysis, a compliance report, and the like, as explained in more detail below.

The interface module <NUM> is operable to communicate with an operator of an electrical system configured according to the electrical system configuration data. The interface module <NUM> may also be further operable to provide an internet webpage interface. The interface module <NUM> may comprise, for example but without limitation, a service bulletin, a compliance report, a circuit diagram, tabular information, graphical information, location information of a part, an electrical load analysis tool (eLAT) interface, a project management interface, a bus management worksheet interface, a load data input interface, a project report, a project report interface, an internet webpage interface, a local area network webpage interface, and the like, as explained in more detail below. The interface module <NUM> is further operable to communicate with the operator to report at least one authoritative change to the operator, and/or to receive at least one authoritative change from the operator.

The report generation module <NUM> is operable to provide user readable status of the electrical load analysis for a target airplane. The report generation module <NUM> generates, for example but without limitation, a paper report, a web delivered report, a screen display, an electronic data delivery report, and the like, as explained in more detail below.

<FIG> is an illustration of an exemplary flowchart showing an electrical load life-cycle management and analysis process <NUM> according to an embodiment of the disclosure. The various tasks performed in connection with process <NUM> may be performed mechanically, by software, hardware, firmware, a computer-readable medium having computer executable instructions for performing the process method, or any combination thereof. It should be appreciated that process <NUM> may include any number of additional or alternative tasks, the tasks shown in <FIG> need not be performed in the illustrated order, and process <NUM> may be incorporated into a more comprehensive procedure or process having additional functionality not described in detail herein.

For illustrative purposes, the following description of process <NUM> may refer to elements mentioned above in connection with <FIG>. In practical embodiments, portions of the process <NUM> may be performed by different elements of the system <NUM> such as: the processor module <NUM>, the memory module <NUM>, the database module <NUM>, the electrical system analysis module <NUM>, the electrical system management module <NUM>, the interface module <NUM>, and the network bus <NUM>. Process <NUM> may have functions, material, and structures that are similar to the embodiments shown in <FIG>. Therefore common features, functions, and elements may not be redundantly described here.

Process <NUM> may begin by storing electrical system configuration data and electrical system requirements in a database (task <NUM>).

The process <NUM> may continue by the electrical system analysis module <NUM> determining electrical system performance characteristics as a function of and based on the electrical system configuration data (task <NUM>).

The process <NUM> may continue by the electrical system analysis module <NUM> comparing the electrical system performance characteristics to the electrical system requirements to provide compliance information (task <NUM>).

The process <NUM> may continue by the interface module <NUM> receiving at least one configuration change to the electrical system configured data (task <NUM>).

The process <NUM> may continue by the electrical system management module <NUM> updating the electrical system configuration data to provide updated electrical system configuration data (task <NUM>).

The process <NUM> may continue by the electrical system analysis module <NUM> comparing the updated electrical system performance characteristics to the electrical system requirements to identify optimal and non-optimal performance of the electrical system, and to provide the compliance information (task <NUM>).

<FIG> is an illustration of an exemplary flowchart showing a process <NUM> for operating an electrical load life-cycle management and analysis system according to an embodiment of the disclosure. The various tasks performed in connection with process <NUM> may be performed mechanically, by software, hardware, firmware, a computer-readable medium having computer executable instructions for performing the process method, or any combination thereof. It should be appreciated that process <NUM> may include any number of additional or alternative tasks, the tasks shown in <FIG> need not be performed in the illustrated order, and process <NUM> may be incorporated into a more comprehensive procedure or process having additional functionality not described in detail herein.

Process <NUM> may begin by the memory module <NUM> storing electrical system configuration data and electrical system requirements in the database module <NUM> (task <NUM>).

Process <NUM> may continue by the interface module <NUM> providing a communication interface to an operator of an electrical system corresponding to the electrical system configuration data (task <NUM>).

Process <NUM> may continue by the interface module <NUM> receiving a configuration change to the electrical system from the operator via the communication interface (task <NUM>).

Process <NUM> may continue by the electrical system management module <NUM> updating the electrical system configuration data for the configuration change (task <NUM>).

Process <NUM> may continue by the electrical system analysis module <NUM> simulating electrical system performance characteristics as a function of and based on the electrical system configuration data (task <NUM>).

Process <NUM> may continue by the electrical system analysis module <NUM> comparing the electrical system performance characteristics to the electrical system requirements to provide compliance information (task <NUM>).

Process <NUM> may continue by the interface module <NUM> providing the compliance information to the operator of the electrical system via the communication interface (task <NUM>).

Based on the compliance information and/or a load analysis, the operator may replace a part with a replacement part. For example, the compliance information may indicate the part is subject to an excessive load for its rated capability, and the replacement part may be operable to operate with a higher electrical load. In order to aid in replacing the part, the interface module <NUM> and/or external software using part identification from the interface module <NUM> may display graphical information about the part. The graphical information may comprise, for example but without limitation, location information for the part (e.g., <FIG>), a circuit diagram for the part, and the like.

In this way, an electrical system lifecycle from design to retirement is comprehensively managed to enable optimal performance of the electrical system. The electrical system lifecycle may comprise, for example but without limitation, production, post production, an as-operating or as-driving baseline configuration for a vehicle, an as-flying configuration for an aircraft, an as-sailing configuration for a boat or a ship, an as-operating configuration for: a building, a city, a town, and a factory, and the like. <FIG> are illustrations of the communication interfaces (interface pages) that can be used by an operator to analyze electrical loads of the electrical system via the system <NUM> during the electrical system lifecycle. The interface pages can be accessed by an operator, for example but without limitation, via an internet webpage interface, a local area network webpage interface, a local computer interface page, and the like.

In this manner, manufacturers as well as a new owner of the vehicle or structure having a complex electrical system can easily and efficiently manage the electrical load on the electrical system and, for example but without limitation, determine "what if" sceneries, add/delete electrical components to ensure adequate load is provided for certain operation thereby enabling optimal operation and avoiding non-optimal operation, and the like. Additionally, regulatory agencies, such as but without limitations, Federal Aviation Administration (FAA), automotive regulatory agencies, building and factory regulatory agencies, and the like, can easily and efficiently obtain and use results of the eLAT analysis for purpose of certification, and the like.

In the embodiments shown in <FIG> an aircraft electrical system is used as an example of the electrical system, however, as mentioned above, embodiments of the disclosure are not limited to such aircraft electrical system, and the eLAT and the interface pages thereof can also be used for analyzing loads on other electrical systems, such as but without limitation, ship electrical systems, building electrical systems, factory electrical systems, town and city electrical systems, and the like.

<FIG> is an illustration of an exemplary electrical load analysis tool (eLAT) interface page <NUM> (interface page <NUM>) according to an embodiment of the disclosure. The interface page <NUM> provides project identification. An operator can choose an aircraft by an aircraft identification in order to update, modify and/or calculate an electrical load analysis (ELA). For example, the operator chooses a project type in a choose project field <NUM>. The project type may comprise, a baseline configuration <NUM>, a released configuration <NUM>, or an in work configuration <NUM>. The aircraft identification may comprise, for example but without limitation, a model number, a project identifier, tail number, and the like.

To select the aircraft identification, the user may select a model number "<NUM>" in a select model filed <NUM>, select a sub model number "-<NUM>" in a select sub model field <NUM>, and/or enter a project identification number "ABC ZA001" in a select project field <NUM>. The operator may also choose at least one revision (e.g., latest, all) of the project type by selecting the desired revision in a revisions filed <NUM>. Upon choosing the project, the model number "<NUM>" and/or the project identification number "ABC ZA001", the operator can navigate various functions related the selected revision of the project as explained below.

<FIG> is an illustration of an exemplary project management interface page <NUM> (interface page <NUM>) according to an embodiment of the disclosure. The interface page <NUM> provides project function navigation. The interface page <NUM> may comprise, for example but without limitation, a calculation and reports area <NUM>, a galley functions area <NUM>, an options and diagnostic area <NUM> and an administration area <NUM>. The administration area <NUM> may require elevated permission for access. The operator may perform any number of load changes or modifications associated with the model number <NUM> and the project identification number ABC ZA001 selected in the interface page <NUM> discussed in <FIG> above. For example but without limitation, the operator can activate/press a bus management button <NUM> to: add/delete a bus, add/delete a circuit breaker (CB), perform "What If" scenarios, select a CB and enter a new or changed load data value(s), and the like, as explained in more detail in the context of discussion of <FIG> below. The operator may also generate various reports, as explained in more detail below, by activating/pressing reports button <NUM>. Additionally, the operator can also activate the report manager button <NUM> to select various report options as discussed in more detail in the context of discussion of <FIG> below.

The galley functions area <NUM> comprises a galley builder button <NUM>. The operator can press/activate the galley builder button <NUM> to access a galley builder user interface that allow him/her to configure galley components (e.g., coffee pots, ovens, etc.) and electrical loads thereof.

The administration area <NUM> is an area requiring elevated permission for access that controls aspects of the project. For example but without limitation, the administration area <NUM> controls who accesses some or all of the project, and the like.

<FIG> is an illustration of an exemplary electrical system and bus management interface page <NUM> (interface page <NUM>) that can be activated by pressing the bus management button <NUM> of the interface page <NUM> (<FIG>) according to an embodiment of the disclosure. The interface page <NUM> provides project bus navigation and usage profile. The operator may choose a bus type in a bus type field <NUM>, a flight condition in a flight condition field <NUM>, a parent bus <NUM>, whether to calculate inoperative (INOP) breakers in Calculate INOP breakers field <NUM>, and the like. Alternatively, the operator may navigate down the bus hierarchy shown in <FIG> by selecting a child bus (<NUM>-<NUM> in <FIG>) such as items of a child list <NUM> indicated to be a bus by selecting a Distribution ("Dist. ") Bus <NUM> identifier equal to "Yes". The operator may also navigate up the bus hierarchy shown in <FIG> by selecting the parent bus <NUM> (<NUM> in <FIG>) by activating a parent bus link <NUM>. By pressing/activating a preview report button <NUM>, a bus specific report may then be generated for the parent bus <NUM> comprising the child CBs <NUM> and resultant values. A bus specific display <NUM> may then be generated showing the resultant values for the parent bus <NUM> comprising the child CBs <NUM>. The bus specific display <NUM> comprises, for example but without limitation, percentage ("%") usage <NUM>, resultant load <NUM>, resultant power factor (PF) <NUM>, and the like, for various flight conditions <NUM>, indicating safe level <NUM>, warning level <NUM>, and non-optimal level <NUM> of electrical loadings. In this manner, the operator can determine whether to rearrange circuits and parts and components to increase or decrease load capacity of a specific bus such as the parent bus <NUM> for a given flight condition <NUM>.

<FIG> is an illustration of an exemplary electrical system and bus management interface page <NUM> (interface page <NUM>) according to an embodiment of the disclosure. The interface page <NUM> allows the operator to update and transfer CB related information to another bus. For example, the operator can update and transfer at least one of the child CBs <NUM> such as the CB <NUM> (CK2531302) related to the parent bus <NUM>, having the bus type selected in the bus type field <NUM> in the interface page <NUM> above, to a different bus by activating a "transfer CB to different bus button" <NUM>. The operator can select the CB <NUM> by activating/pressing/double-clicking the corresponding Dist Bus <NUM> identifier on the interface page <NUM>.

In response to activating/pressing the "transfer a CB to a different bus button" <NUM> an interface page opens to provide access to "What If" scenarios creation as shown below in the context of discussion of <FIG>. The operator can also select to update load data sheet as shown below in the context of discussion of <FIG> by activating/pressing an update load data sheet button <NUM>.

<FIG> is an illustration of an exemplary electrical system and bus management interface page <NUM> (interface page <NUM>) that enables "What If" requirements to be given according to an embodiment of the disclosure. The interface page <NUM> provides access to the "What If" scenarios creation. The operator may activate/press a transfer button <NUM> to transfer a selected CB load <NUM> (<FIG>) of the parent bus <NUM> having the bus type <NUM> to another selected bus <NUM> of the same type in a "What If" scenario.

<FIG> is an illustration of an exemplary load data input interface page <NUM> (interface page <NUM>) according to an embodiment of the disclosure. The interface page <NUM> provides power requirements for a given CB and enables "What If" requirements to be given. For example, the operator can input a nomenclature in a nomenclature input field <NUM>, a part number in a part number field <NUM>, a CB identifier in a CB information field <NUM>, a bus identifier in a bus information field <NUM>. Additionally, the operator can provide a system wire diagram number in a system wire diagram field <NUM>, a system schematic number in a system schematic field <NUM>, and /or a system power diagram number in a system power diagram field filed <NUM>. The operator can also select an Inop field <NUM> (i.e., indicating an inoperative part), whether the C/B is changed <NUM>, and/or the bus is changed <NUM>.

The operator may provide power requirements table <NUM> related to the CB information for various aircraft operation phases. The table <NUM> comprises, a load characteristics column <NUM>, flight phase loading column <NUM>, and standby loads column <NUM>. For example, the flight phase loading <NUM> for cruise phase <NUM> indicates load characteristics <NUM> is an AC type CB with an electrical loading of <NUM> Kilovolt-amperes (KVA), and a power factor (PF) of <NUM> (i.e., a PF of <NUM> indicates a very efficient electrical loading, as PF decreases toward <NUM> power efficiency decreases accordingly). In this manner, the operator can provide an updated load capacity of the cruise phase <NUM>.

The operator may specify an aircraft that the electrical load data changes are applicable to in an "Effectivity From" field <NUM> and an "Effectivity To" field <NUM>. For example, many aircraft identifiers such as tail numbers may be sequential (e.g., ZA001, ZA002,. Thus a range of aircraft may be specified by a starting number such as ZA002 in the "Effectivity From" field <NUM>, and an ending number such as ZA009 in the "Effectivity To" field <NUM>. A single aircraft may be specified by a single number such as ZA001 in both the "Effectivity From" field <NUM> and the "Effectivity To" field <NUM>.

<FIG> is an illustration of an exemplary project report interface page <NUM> (interface page <NUM>) according to an embodiment of the disclosure. The interface page <NUM> provides various load reports in various formats. For example, an operator can generate a full electrical load analysis (Full-ELA) report in portable document format (pdf) format by activating/pressing a Full-ELA button <NUM>. An operator may generate individual report sections <NUM>, spread sheet formats, text formats, and the like. A text editor can be used by pressing/activating a text edit button <NUM>. Alternatively, reports can also be generated graphically by using, for example and without limitation, bar charts, Visio™ format, and the like.

<FIG> is an illustration of an exemplary electrical load analysis report <NUM> according to an embodiment of the disclosure. The electrical load analysis report <NUM> comprises an example of a cover page of the Full-ELA report that can be obtained by activation/pressing the <NUM> button on the interface page <NUM>. The electrical load analysis report <NUM> comprises a title <NUM>, a document control number <NUM>, a release version <NUM>, and a release revision date <NUM>. The electrical load analysis report comprises report sections, charts, graphs, text and the like, required for demonstration of electrical system loading requirements, configuration and compliance.

<FIG> is an illustration of an exemplary output page showing an ATRU operating histogram report <NUM> (histogram report <NUM>) according to an embodiment of the disclosure. The histogram report <NUM> shows generator load in KVA by four auto transformer rectifier units L1 ATRU <NUM>, L2 ATRU <NUM>, R1 ATRU <NUM>, and R2 ATRU <NUM> respectively, for various aircraft operation such as ground <NUM>, Main Engine Start (MES) <NUM>, taxi <NUM>, takeoff and climb <NUM>, cruise <NUM>, descent <NUM>, and approach and landing <NUM>. For example, for descent <NUM>, the L1 ATRU <NUM>, L2 ATRU <NUM>, R1 ATRU <NUM>, and R2 ATRU <NUM>, can provide <NUM> KVA, <NUM> KVA, <NUM>, and <NUM> KVA respectively. Therefore, the operator can decide whether to increase or decrease the generator load for the decent <NUM>, for example.

<FIG> is an illustration of an exemplary report page <NUM> according to an embodiment of the disclosure. The report page <NUM> can be generated by activating the reports button <NUM> of the interface page <NUM> as explained above. In the embodiment shown in <FIG>, the report page <NUM> comprises C/B data <NUM>, nomenclature <NUM>, load data <NUM> comprising power factor (PF) and load (KVA) for: ground <NUM>, engine start <NUM>, taxi-out <NUM>, and climb <NUM> aircraft operations. A total load <NUM> for the specified bus (e.g., L1235VAC-A) is also shown on the report <NUM>. In this manner, the operator can determine whether the load on the specified bus is excessive, not enough, or adequate for a given aircraft operation <NUM>-<NUM>.

<FIG> is an illustration of an exemplary project diagnostic interface page <NUM> (interface page <NUM>) according to an embodiment of the disclosure. The operator can perform diagnostic functions on the aircraft electrical data comprising but not limited to a margin and capacity report. The operator can activate the margin and capacity report as shown below by activating/pressing the margin and capacity button <NUM>.

<FIG> is an illustration of an exemplary margin and capacity report <NUM> according to an embodiment of the disclosure. In the embodiment shown in <FIG>, the margin and capacity report <NUM> comprises a type column <NUM>, a bus column <NUM>, a bus name column <NUM>, a plurality of normal load data columns <NUM>, a C/B identification (ID) column <NUM>, a C/B capacity column <NUM>, an Amps column <NUM>, a margin column <NUM>, a % of capacity column <NUM>, and a load level column <NUM>.

For example, a row <NUM> of the margin and capacity report <NUM> indicates that a bus GENL2-A (column <NUM>) with a type AC (column <NUM>) and a C/B ID M2421002 (column <NUM>) has a non-optimal load level (column <NUM>) as specified by load capacity parameters <NUM> and a load threshold level interface page <NUM> discussed below in the context of <FIG>. The row <NUM> also indicates, the C/B capacity of <NUM> amps (column <NUM>), margin of <NUM> amps (column <NUM>), and % capacity of <NUM> (column <NUM>). The operator can determine appropriate action for operating the bus GENL2-A in various aircraft operation.

<FIG> is an illustration of an exemplary load threshold level interface page <NUM> (interface page <NUM>) according to an embodiment of the disclosure. The interface page <NUM> comprises an adjustable warning indicator threshold <NUM>, a warning indicator <NUM>, an adjustable non-optimal indicator threshold <NUM>, and a non-optimal indicator <NUM>. The interface page <NUM> may be used in conjunction with various interface pages to set alert indicators on load analysis results.

For another example, the load capacity parameters <NUM> of the margin and capacity report <NUM> of <FIG> is indicated to be "safe", "warning", and "Non-optimal" in the load level column <NUM> according to the adjustable warning indicator threshold <NUM> and the adjustable non-optimal indicator threshold <NUM>. For yet another example, the % usage <NUM> of the bus management interface page <NUM> of <FIG> is indicated to be "warning level" <NUM>, and "Non-optimal level" <NUM> in the % usage <NUM> column by highlighting according to the adjustable warning indicator threshold <NUM> and the adjustable non-optimal indicator threshold <NUM>. The interface page <NUM> may be accessed by activation of the preferences button <NUM> of the project management interface page <NUM> of <FIG>.

The adjustable warning indicator threshold <NUM> may comprise, for example but without limitation, a percentage of a maximum value, an absolute threshold level of a parameter of interest, and the like.

The warning indicator <NUM> may comprise, for example but without limitation, a color, a hatching pattern, a pattern, a color and hatching pattern, a blinking illumination, an illumination effect, and the like.

The adjustable non-optimal indicator threshold <NUM> may comprise, for example but without limitation, a percentage of a maximum value, an absolute threshold level of a parameter of interest, and the like.

The non-optimal indicator <NUM> may comprise, for example but without limitation, a color, a hatching pattern, a pattern, a color and hatching pattern, a blinking illumination, an illumination effect, and the like.

<FIG> is an illustration of an exemplary change interface page <NUM> (interface page <NUM>) according to an embodiment of the disclosure. The operator can use the interface page <NUM> to determine authoritative changes to the electrical system. For example, at a post delivery phase, the operator can determine the authoritative changes, such as but without limitation, customer originated changes (COC), a service bulletin (SB) change, a supplemental type certificate (STC) change, a customer change, a third party change, and the like. For example, as shown in the interface page <NUM>, the COC <NUM> indicates status of "installation of seat group 38A and 39A with upgrades seat back monitors" for the aircraft ABC ZA001 is open as of date <NUM>/<NUM>/<NUM>.

In this way, embodiments of the disclosure provide a system and method to allow users/operators to easily and efficiently manage and analyze an electrical loading on a power distribution system from design to retirement of an electrical system, whereby minimizing cost of electrical load analysis while meeting total system safety constraints.

In this document, the terms "computer program product", "computer-readable medium", "computer readable storage medium", and the like may be used generally to refer to media such as, for example, memory, storage devices, or storage unit. These and other forms of computer-readable media may be involved in storing one or more instructions for use by the processor module <NUM> to cause the processor module <NUM> to perform specified operations. Such instructions, generally referred to as "computer program code" or "program code" (which may be grouped in the form of computer programs or other groupings), when executed, enable electrical load analysis of the system <NUM>.

The above description refers to elements or nodes or features being "connected" or "coupled" together. As used herein, unless expressly stated otherwise, "connected" means that one element/node/feature is directly joined to (or directly communicates with) another element/node/feature, and not necessarily mechanically. Likewise, unless expressly stated otherwise, "coupled" means that one element/node/feature is directly or indirectly joined to (or directly or indirectly communicates with) another element/node/feature, and not necessarily mechanically. Thus, although <FIG> depict example arrangements of elements, additional intervening elements, devices, features, or components may be present in an embodiment of the disclosure.

Terms and phrases used in this document, and variations thereof, unless otherwise expressly stated, should be construed as open ended as opposed to limiting. As examples of the foregoing: the term "including" should be read as mean "including, without limitation" or the like; the term "example" is used to provide exemplary instances of the item in discussion, not an exhaustive or limiting list thereof; and adjectives such as "conventional," "traditional," "normal," "standard," "known" and terms of similar meaning should not be construed as limiting the item described to a given time period or to an item available as of a given time, but instead should be read to encompass conventional, traditional, normal, or standard technologies that may be available or known now or at any time in the future.

Claim 1:
A method implemented on a computer system, the computer system for electrical load life-cycle management and analysis of a complex vehicle, the method comprising:
storing (<NUM>), in a database, electrical system configuration data and electrical system requirements of a complex vehicle that is in service, the electrical system configuration data comprising electrical system organization data, electrical system hierarchy data, electrical system connection data, circuit diagrams, electrical system structure data, and part service life data;
receiving (<NUM>) a configuration change to the electrical system configuration data from an operator of an electrical system for the complex vehicle via a communication interface, the configuration change comprising one of adding or deleting electrical components from the electrical system configuration data;
determining (<NUM>) electrical system performance characteristics of the vehicle based on the electrical system configuration data of the vehicle by simulating electrical system performance characteristics based on the electrical system configuration data, the electrical system performance characteristics comprising a load distribution analysis and a flight phase load analysis; and
comparing (<NUM>) the electrical system performance characteristics to the electrical system requirements to provide compliance information for the vehicle;
updating (<NUM>) the electrical system configuration data to provide updated electrical system configuration data of the vehicle;
determining updated electrical system performance characteristics of the vehicle based on the updated electrical system configuration data; and
comparing (<NUM>) the updated electrical system performance characteristics to the electrical system requirements to provide the compliance information for the vehicle to the operator of the electrical system via the communication interface.