Method and system for monitoring the health status of power cable accessories based on machine learning

By integrating sensors and computing systems in electrical equipment and using supervised training models to predict faults, the problem of time-consuming and expensive positioning of electrical equipment in the prior art is solved, and the safety and reliability of power facilities are improved.

CN112673265BActive Publication Date: 2024-12-033M INNOVATIVE PROPERTIES CO
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980058331.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-09-10
Filing Date
2019-09-06
Publication Date
2024-12-03
Estimated Expiration
2039-09-06

AI Technical Summary

Technical Problem

The prior art is difficult to quickly and accurately identify potential faults of electrical equipment in power facilities, resulting in fault location being time-consuming and expensive, and may pose a risk to public safety.

Method used

Using electrical equipment that includes sensor data output to the computing system, the equipment health status and fault events are predicted by supervising the training model, the operating characteristics of cable accessories are monitored in real time, and the data is transmitted using embedded monitoring devices and communication units to realize the closed loop of electrical equipment. Training and prediction.

Benefits of technology

It realizes rapid and accurate fault identification and prediction of electrical equipment, reduces the time and cost of fault location and repair, and improves the safety and reliability of power facilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112673265B_ABST
    Figure CN112673265B_ABST
Patent Text Reader

Abstract

The present invention describes techniques, systems, and articles for monitoring electrical equipment of an electrical grid and predicting possible failure events of such electrical equipment. In one example, a system includes an electrical equipment article, at least one processor, and a storage device. The electrical equipment article includes one or more sensors configured to generate sensor data indicating one or more conditions of the electrical equipment article. The storage device includes instructions that, when executed by the at least one processor, cause the at least one processor to: receive the sensor data; determine a health state of the electrical equipment article based at least in part on the sensor data; and perform an operation in response to determining the health state of the electrical equipment article.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of electrical equipment for use in electric power utilities, including power cables and accessories. Background Art

[0002] The electric power grid includes many components that operate in a variety of different locations and conditions, such as above ground, underground, cold climates, hot climates, etc. When a fault occurs in the power grid, it may be difficult to determine the cause of the fault. For example, the power grid may include hundreds or thousands of discrete components, such as transformers, cables, cable joints, etc., and the fault in the power grid may be caused by a fault in any single component or a collection of components. The root cause of such a fault may include reasons such as human installation error, manufacturing defects, or wear and tear on the components. Although replacing electronic components can be expensive, simply finding the fault can also be time-consuming and expensive. If a component fails in use, the total cost can include customer operation downtime, liability, safety or regulatory review, in addition to the actual cost incurred to locate and replace the faulty component. In addition, the faulty component may pose a safety risk to utility workers, people, homes, buildings, or other infrastructure. Summary of the invention

[0003] The present disclosure provides techniques for monitoring electrical equipment of a power grid and predicting possible failure events of such electrical equipment. For example, various electrical equipment products are described that include one or more sensors that output sensor data to a computing system. The computing system can apply one or more models to the sensor data, for example in real time, to predict failure events of the electrical equipment product and / or determine the health state of the electrical equipment product, such as predicting the remaining life of the electrical equipment product. Examples of such sensors include temperature sensors, partial discharge sensors, smoke sensors, gas sensors, acoustic sensors, etc.

[0004] According to aspects of the present disclosure, a computing system may implement supervised training to train a model using a set of training examples, wherein each training example includes sensor data associated with a known (i.e., previously identified / labeled) corresponding fault event. Furthermore, in operation, the computing system model may update the one or more models based on newly received sensor data and event data to provide closed-loop training of the model, thereby, in some examples, achieving a more accurate prediction of the health state of the equipment article when the model is applied to subsequent sensor data.

[0005] In this way, when the system receives sensor data from electrical equipment articles operating in a work environment, the system can more quickly and accurately identify potential fault events that may affect power distribution throughout the power grid or worker and / or civilian safety, etc. By determining the health status of electrical equipment and predicting fault events before they occur, the computing system can proactively and preemptively generate notifications and / or change the operation of the power grid before a fault event occurs.

[0006] In addition, various implementations of power grid cable accessories are described that are attached to a high voltage power cable and include a sensor that generates sensor data indicative of an operational characteristic of the corresponding cable accessory. For example, the cable accessory may include an internal temperature sensor located within the cable accessory and / or an external temperature monitor for monitoring a temperature on the exterior or surface of the cable accessory. The cable accessory may be, for example, a cable connector configured to electrically and physically couple a cable, and may include an embedded monitoring device having a sensor and a communication unit for sensing sensed data and transmitting the sensed data to a remote computing system and / or for applying local analysis to the sensed data.

[0007] In some examples, a system includes one or more sensors coupled to an electrical equipment product, at least one processor, and a storage device. The one or more sensors are configured to generate sensor data indicating one or more conditions of the electrical equipment product. The storage device includes instructions that, when executed by the at least one processor, cause the at least one processor to: receive the sensor data; determine a health state of the electrical equipment product based at least in part on the sensor data; and, in response to determining the health state of the electrical equipment product, perform an operation.

[0008] In some examples, a method includes receiving, by at least one processor of a computing system and from at least one sensor, sensor data indicating one or more conditions of an electrical equipment article. The method includes determining, by the at least one processor, a health state of the electrical equipment article based at least in part on the sensor data. The method also includes performing, by the at least one processor, at least one operation based on the health state of the electrical equipment article.

[0009] The details of one or more examples of the disclosure are shown in the accompanying drawings and the description below. Other features, objects, and advantages of the disclosure will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1is a block diagram illustrating an example system in which electrical utility equipment, such as power lines, with embedded sensors and communication capabilities are utilized within many operating environments and managed by an electrical equipment management system (EEMS), in accordance with various techniques of the present disclosure.

[0011] Figure 2 is a diagram showing various techniques according to the present disclosure Figure 1 A block diagram of an electrical equipment management system from an operational perspective is shown.

[0012] Figure 3 is a conceptual diagram of an example cable accessory configured to electrically and physically couple two cables in accordance with various techniques of the present disclosure.

[0013] Figure 4 is a block diagram illustrating an example gateway configured to communicate with cable accessories and an EEMS, in accordance with various techniques of this disclosure.

[0014] Figure 5 is an exemplary graphical user interface of an electrical device management system according to the techniques of this disclosure.

[0015] Figure 6 is a flow diagram illustrating example operations performed by one or more computing devices configured to monitor electrical utility equipment, in accordance with various techniques of this disclosure.

[0016] Figure 7 is a graph illustrating an example partial discharge event detected by a monitoring device and associated with a known fault event in accordance with various techniques of the present disclosure.

[0017] Figure 8 Includes illustrations of various techniques according to the present disclosure Figure 7 Additional details of the partial discharge event are plotted in FIG.

[0018] 9A to 9C Included are graphs showing sensor data associated with known fault events in accordance with various techniques of the present disclosure.

[0019] Fig.10 is a conceptual diagram illustrating an exemplary cable accessory that couples two cables according to one or more aspects of the present disclosure.

[0020] Fig.11 is a conceptual diagram illustrating an exemplary cable accessory that couples two cables according to one or more aspects of the present disclosure.

[0021] Fig.12 is a conceptual diagram illustrating an example cable accessory coupled to an example cable according to one or more aspects of the present disclosure.

[0022] Fig.13is a conceptual diagram illustrating an example cable accessory coupled to an example cable according to one or more aspects of the present disclosure.

[0023] It should be understood that the embodiments may be utilized and their structures may be modified without departing from the scope of the invention. The figures are not necessarily drawn to scale. Like numbers used in the figures refer to like components. However, it should be understood that the use of numbers to refer to components in a given figure is not intended to limit the components labeled with the same number in another figure. DETAILED DESCRIPTION

[0024] Figure 1 is a block diagram illustrating an exemplary computing system 2 including an electrical equipment management system (EEMS) 6 for monitoring power cables of an electric power grid. As described herein, the EEMS 6 may allow authorized users to manage inspection, maintenance, and replacement of electrical equipment of the grid, and adjust the operation of the grid.

[0025] Generally speaking, the EEMS 6 provides data collection, monitoring, activity logging, data storage, reporting, predictive analysis, and alert generation. For example, the EEMS 6 may include a basic analysis engine and alert system for predicting fault events of electrical equipment products according to various examples described herein. Generally speaking, a fault event may refer to an interruption in power delivery between a power source and a power consumer, for example, caused by degradation or breakage of an electrical equipment product (e.g., a cable connector).

[0026] As further described below, EEMS 6 provides an integrated set of electrical equipment management tools and implements various techniques of the present disclosure. That is, EEMS 6 provides a system for managing electrical equipment (e.g., cables, connectors, transformers, etc.) within one or more physical environments 8, which may be cities, communities, buildings, construction sites, or any physical environment. The techniques of the present disclosure may be implemented within various parts of system 2.

[0027] like Figure 1 As shown in the example of , system 2 represents a computing environment in which computing devices within multiple physical environments 8A, 8B (collectively referred to as environments 8) electronically communicate with EEMS 6 via one or more computer networks 4. Each physical environment 8 represents a physical environment in which one or more power lines 24A-24D (collectively referred to as power lines 24) provide power from a power source (e.g., a power plant) to one or more consumers (e.g., businesses, homes, government facilities, etc.).

[0028] In this example, environment 8A is generally shown with electrical device 20, while environment 8B is shown in expanded form to provide a more detailed example. Figure 1In the example, multiple electrical equipment products 20 are included, such as one or more power delivery nodes 22A-22N (collectively referred to as power delivery nodes 22), one or more power lines 24, one or more communication hubs 26A-26D (collectively referred to as communication hubs 26) and one or more gateways 28.

[0029] exist Figure 1 In the example of , environment 8B includes a wireless communication hub 26 and / or one or more gateways 28. Generally speaking, the communication hub 26 and the gateway 28 operate as communication devices for relaying communications between the EEMS 6 and the monitoring devices 33 that monitor the corresponding electrical equipment products 20 (e.g., cable accessories 34). The communication hub 26 and the gateway 28 can each be communicatively coupled to the EEMS 6 via wired communication and / or wireless communication. For example, the wireless communication hub 26 and / or the gateway 28 may include a cellular radio component (e.g., GSM, CDMA, LTE, etc.), Radio components, Radio components, low power wide area networks (LPWAN), etc. As another example, the wireless communication hub 26 and / or the gateway 28 may include a wired connection, such as a network interface card (e.g., an Ethernet card), an optical transceiver, or any other type of device that can send and / or receive data. According to some examples, the communication hub 26 and / or the gateway 28 may communicate with other devices using power line communication technology. In other words, in some examples, the gateway 28 may communicate with the monitoring device 33 via the power line 24. In some examples, the wireless communication hub 26 and the gateway 28 are capable of buffering data in the event of a loss of communication with the EEMS 6. In addition, the communication hub 26 and the gateway 28 may be programmed via the EEMS 6 so that local alert rules can be installed and executed without the need to connect to the cloud. Therefore, the communication hub 26 and the gateway 28 can provide a relay of event data streams from the monitoring device 33, and provide a local computing environment for local alerts based on event streams.

[0030] The power delivery node 22 may include one or more input lines for receiving power (e.g., directly from a power source or indirectly via another power delivery node 22) and one or more output lines for distributing power to consumers (e.g., homes, businesses, etc.) directly or indirectly (e.g., via another power delivery node 22). The power delivery node 22 may include a transformer to step up or down the voltage. In some examples, the power delivery node 22A may be a relatively small node, such as an electrical control cabinet, a pole transformer, or a pad transformer, for distributing power to homes within a community. As another example, the power delivery node 22N may be a relatively large node (e.g., a transmission substation) that distributes power to other power delivery nodes (e.g., distribution substations) so that the other power delivery nodes further distribute the power to consumers (e.g., homes, businesses, etc.).

[0031] Power lines 24 can transmit electricity from a power source (e.g., a power plant) to power consumers, such as businesses or homes. Power lines 24 can be underground, underwater, or overhead (e.g., by wooden poles, metal structures, etc.). Power lines 24 can be used to transmit electricity at relatively high voltages (e.g., compared to cables used in homes, which can transmit electricity between about 12 volts and about 240 volts depending on the specific application and geographic area). For example, power lines 24 can transmit electricity higher than about 600 volts (e.g., between about 600 volts and about 1,000 volts). However, it should be understood that power lines 24 can transmit electricity within any voltage and / or frequency range. For example, lines 24 can transmit electricity within different voltage ranges. In some examples, a first type of line 24 can transmit a voltage greater than about 1,000 volts, such as to distribute electricity between residential or small commercial customers and power sources (e.g., power utilities). For another example, a second type of line 24 can transmit a voltage between about 1 kV and about 69 kV, such as to distribute electricity to urban and rural communities. A third type of line 24 may transmit voltages greater than about 69 kV, such as for sub-transmission and transmission of large quantities of electricity and connection to very large consumers.

[0032] The power line 24 includes a cable 32 and one or more cable accessories 34A-34J. Each cable 32 includes a conductor that may be radially surrounded by one or more insulation layers. In some examples, the cable 32 includes a plurality of twisted conductors (e.g., a three-phase or multi-conductor cable). Exemplary cable accessories 34 may include connectors, separable connectors, terminals, connectors, etc. In some examples, the cable accessories 34 may include a cable connector configured to couple (e.g., electrically and physically) two or more cables 32. For example, as shown in FIG. Figure 1As shown, cable accessory 34A electrically and physically couples cable 32A to cable 32B, cable accessory 34B electrically and physically couples cable 32B to cable 32C, and so on. In some examples, the terminal can be configured to couple (e.g., electrically and physically couple) cable 32 to additional electrical equipment, such as a transformer, switchgear, power substation, business, home, or other structure. For example, Figure 1 As shown, cable accessory 34C electrically and physically couples cable 32C to power delivery node 22A (eg, to a transformer coupled to power delivery node 22A).

[0033] System 2 includes one or more cable monitoring devices 33A-33L (collectively referred to as monitoring devices 33) configured to monitor one or more conditions of electrical equipment products 20. For example, monitoring device 33 may be configured to monitor the condition of power delivery node 22, cable 32, cable accessories 34, or other types of electrical equipment 20. Monitoring device 33 may be configured to be attached or otherwise coupled to cable 32 and / or cable accessories 34. In some examples, monitoring device 33 may be integrated into another device, such as cable accessories 34, or may be a separate (e.g., independent) device. Figure 1 In the example of FIG. 2 , cable accessories 34A, 34B, 34C, 34D, 34E, 34F, 34G, 34H and 34I respectively include monitoring devices 33A, 33B, 33C, 33D, 33E, 33F, 33G, 33H and 33I, while monitoring device 33J is an independent monitoring device for monitoring power line 24D. Figure 1 In the example, cable accessory 34K does not include a monitoring device.

[0034] The monitoring device 33 includes a sensor that generates sensor data indicating the operating characteristics of one or more cables 32 and / or cable accessories 34 or the condition of the electrical device. The sensors of the monitoring device 33 may include temperature sensors (e.g., located inside and / or outside the cable accessories), partial discharge sensors, voltage and / or current sensors, etc. In some examples, the monitoring device 33A includes one or more temperature sensors. For example, the monitoring device 33A may include an internal temperature sensor for monitoring the temperature inside the cable 32 or cable accessories 34 and / or an external temperature monitor for monitoring the temperature on the outside or surface of the cable 32 or cable accessories 34. Exemplary details of the monitoring device are described in U.S. patent application 62 / 729,325, entitled "ELECTRICAL POWER CABLE MONITORING DEVICE USING LOW SIDE ELECTRODE AND EARTH GROUND SEPARATION" filed on September 10, 2018, which is hereby incorporated by reference in its entirety.

[0035] The monitoring device 33 may include a partial discharge sensor for detecting a partial discharge event (e.g., within the cable accessory 34A). As used herein, a partial discharge event refers to a current discharge that only partially bridges a gap between electrodes of a cable (e.g., this may be caused by a gas discharge in a void of the cable). Additional exemplary details of a monitoring device for sensing a partial discharge event are described in U.S. patent application 62 / 729,363, entitled "ELECRICAL POWER CABLE MONITORING DEVICE INCLUDING PARTIAL DISCHARGE SENSOR," filed on September 10, 2018, which is hereby incorporated by reference in its entirety. The monitoring device 33 may include a voltage and / or current sensor configured to measure the phase and / or magnitude of a voltage or current in the cable 32 or cable accessory 34.

[0036] The monitoring devices 33 each include a power source or receive power from a power source. For example, the monitoring device 33A may include a battery. As another example, the monitoring device 33A may be coupled to a solar cell, a wind turbine, or other renewable or non-renewable power source. Exemplary details of a monitoring device with a protective housing are described in U.S. patent application 62 / 729,320, entitled "SUPPORT STRUCTURE FOR CABLE AND CABLE ACCESSORY CONDITION MONITORING DEVICES," filed on September 10, 2018, which is hereby incorporated by reference in its entirety.

[0037] In some examples, monitoring device 33A may include a power acquisition device configured to acquire power from power line 24A. For example, the power acquisition device of monitoring device 33A may receive power via power carried by power line 24A, via a magnetic field generated by power line 24A, or via heat within power line 24A, cable accessories 34A, or other devices that generate heat when coupled to power line 24A.

[0038] Generally, the monitoring device 33 may be communicatively coupled to the EEMS 6. In some examples, the monitoring device 33 may include a transceiver for communicating with the EEMS 6 (e.g., via the network 4). In some examples, the monitoring device 33 communicates with the EEMS 6 via the communication hub 26 and / or the gateway 28. For example, the monitoring device 33 may output data to the gateway 28 and / or the communication hub 26 via power line communication. For another example, the monitoring device 33 may include a wireless communication device such as The monitoring device 33 may transmit event data indicating a health state or condition of the cable 32, the cable accessories 34. The event data may include data indicating sensor data generated by a sensor of the electrical device 20, device data of the electrical device 20, analysis data, or a combination thereof. For example, the data indicating the sensor data may include at least a portion of the sensor data generated by one or more sensors of the monitoring device 33A, a summary of the sensor data, a conclusion or result of an analysis performed on the sensor data, or a combination thereof. Device data (also referred to as equipment data) may include identification data (e.g., a unique identifier corresponding to a particular electrical equipment article 20), device type (e.g., transformer, connector, terminal connector, etc.), event timestamp, location data (e.g., GPS coordinates of a particular electrical equipment article 20), manufacturing data (e.g., manufacturer, batch number, serial number, date of manufacture, etc.), installation data (e.g., installation date, identity of the installer or installation team), customer data (e.g., data identifying the number and / or type of customers served by the line, the address served by the line, etc.), distribution data (e.g., line type, such as extra-high voltage, high voltage, medium voltage, etc.), or a combination thereof. In some examples, event data includes analytical data, such as data indicating whether the electrical device is predicted to fail (e.g., whether a failure event is predicted to occur), the predicted or estimated remaining life of the electrical device, a confidence interval for the prediction, etc. In some examples, the monitoring device 33 may receive data from the EEMS 6, the communication hub 26, the gateway 28, and / or the cable accessories 34. For example, the EEMS 6 may transmit a request for sensor data, firmware updates, or other data to the monitoring device 33.

[0039] In some examples, monitoring device 33 includes a device configured to communicate with the user via a wireless network (e.g., For example, Figure 1 As shown, monitoring devices 33A and 33B may be communicatively coupled to wireless communication hubs 26A and 26B, respectively. In this way, monitoring devices 33A and 33B may communicate with EEMS 6 via wireless communication hubs 26A, 26B. In some examples, monitoring devices 33A-33C may communicate with EEMS 6 via gateway 28. For example, monitoring device 33A may transmit data to monitoring device 33B, and monitoring device 33B may transmit data to monitoring device 33C (e.g., some or all of the monitoring devices 33 may form a mesh network). Monitoring device 33C may transmit data from monitoring devices 33A-33C to gateway 28, which may forward data from monitoring devices 33A-33C to EEMS 6.

[0040] The monitoring device 33 may include a wired transceiver. For example, the monitoring device 33 may be configured to communicate with the cable accessories 34, the communication hub 26, the gateway 28, and / or the EEMS 6 via power line communications or with each other over copper or fiber optic communication lines. In other words, in some examples, the monitoring device 33 may include a transceiver configured to communicate over the power line 24. In this way, the power line 24 can transmit power from the power source to the power consumer, as well as transmit data between the EEMS 6 and the monitoring device 33. For additional details on the monitoring device 33, refer to Figure 3 Give a description.

[0041] One or more electrical equipment articles 20 may be configured to perform analysis locally. In some examples, the monitoring device 33A may analyze sensor data generated by sensors of the monitoring device 33A to determine the health state of the cable accessory 34A. The monitoring device 33A may determine the health state of the cable accessory 34A by determining whether the cable accessory 34A is predicted to fail (e.g., experience a failure event) within a threshold amount of time, determining an estimated remaining life, etc. The monitoring device 33A may output analysis data based on the analysis results. For example, the analysis data may include data indicating the health state of the cable accessory 34A. The monitoring device 33A may output event data including analysis data to the EEMS 6 (e.g., via the communication hub 26A, via the monitoring device 33B and the communication hub 26B, and / or via the communication hubs 26B, 26C, and the gateway 28).

[0042] System 2 includes computing devices 16 through which users 18A-18N (collectively, users 18) can interact with EEMS 6 via network 4. For purposes of example, end-user computing devices 16 may be laptops, desktop computers, mobile devices such as tablets, smart phones, and the like.

[0043] The user 18 interacts with the EEMS 6 to control and actively manage many aspects of the electrical equipment 20, such as accessing and viewing event logs, analysis, and reports. For example, the user 18 can review event data collected and stored by the EEMS 6. In addition, the user 18 can interact with the EEMS 6 to perform asset tracking and schedule maintenance or replacement for various pieces of electrical equipment 20 (e.g., monitoring devices 33, cables 32, and / or cable accessories 34). The EEMS 6 can allow the user 18 to create and complete digital checklists with respect to maintenance and / or replacement procedures and synchronize any results of these procedures from the computing device 16 to the EEMS 6.

[0044] In addition, as described herein, the EEMS 6 integrates an event processing platform that is configured to process hundreds, thousands, or even millions of concurrent event streams from monitoring devices 33 that monitor corresponding electrical equipment products 20 (e.g., cable accessories 34). The underlying analytics engine of the EEMS 6 applies historical data and models to the inbound streams to compute assertions, such as anomalies or predicted fault event occurrences identified based on data from sensors of the electrical equipment 20. In addition, the EEMS 6 provides real-time alerts and reports to notify the user 18 of any predicted events, anomalies, trends, etc.

[0045] The analysis engine of the EEMS 6 may, in some examples, apply analysis to identify relationships or correlations between sensor data, environmental conditions, geographic regions, or other factors, and analyze the impact on a fault event. In some examples, the EEMS 6 may determine the health status of one or more cable accessories 34 or other electrical devices. For example, the EEMS 6 may determine conditions that lead to a fault event or predict a fault event based on data collected across a population of electrical devices 20.

[0046] In some examples, the EEMS 6 can determine whether the electrical equipment article 20 should be repaired or replaced, prioritize maintenance (e.g., repair or replacement) procedures, create work orders, assign individuals or teams to perform maintenance procedures, etc. According to some examples, the EEMS 6 can recommend rewiring the power or automatically rewire the power based on the analysis results.

[0047] EEMS 6 may process data for one or more entities, such as electric utilities. For example, EEMS 6 may receive event data from electrical equipment of a single electric utility, and may provide analysis and reporting for the single electric utility. As another example, EEMS 6 may receive event data from multiple electric utilities, and provide analysis and reporting for each of the electric utilities. By receiving data from multiple electric utilities, EEMS 6 may provide more robust predictive capabilities, for example, by training a machine learning model with a larger data set than each electric utility that utilizes a separate EEMS 6.

[0048] In this way, the EEMS 6 integrates a comprehensive tool for managing the electrical devices 20 through the underlying analysis engine and communication system to provide data collection, monitoring, activity logging, reporting, and alert generation. In addition, the EEMS 6 provides a communication system between the various elements of the system 2 that is operated and utilized by these elements. The user 18 can access the EEMS 6 to view the results of any analysis performed by the EEMS 6 on the data collected from the monitoring device 33. In some examples, the EEMS 6 can present a web-based interface via a web server (e.g., an HTTP server), or a client application can be deployed for the computing device 16 used by the user 18.

[0049] In some examples, the EEMS 6 may provide a database query engine for directly querying the EEMS 6 to view the collected event (e.g., sensor) data and any results of the analysis engine, such as through dashboards, alert notifications, reports, etc. That is, a user 18 or software executing on a computing device 16 may submit a query to the EEMS 6 and receive data corresponding to the query for presentation in the form of one or more reports or dashboards. Such dashboards may provide various insights about the system 2, such as baseline ("normal") operation across the environment 8, identification of any abnormal environments and / or electrical devices 20, identification of any geographic areas within the environment 2 where abnormal activity (e.g., failure events) has occurred or is predicted to occur, etc.

[0050] As described in detail below, the EEMS 6 can simplify workflow for individuals responsible for monitoring physical or environmental electrical devices 20. That is, the techniques of the present disclosure can enable proactive electrical device management and allow organizations to take preventive or corrective action with respect to specific pieces of electrical equipment.

[0051] As one example, the underlying analytics engine of the EEMS 6 may be configured to compute and present metrics for electrical devices within a given environment 8 or across multiple environments to an organization. For example, the EEMS 6 may be configured to collect data and provide aggregated failure metrics and predictive failure analysis across one or more environments 8. In addition, the user 18 may set a baseline for any failure event to occur, and the EEMS 6 may track actual failure events relative to the baseline.

[0052] As another example, if certain combinations of conditions exist, the EEMS 6 can further trigger an alert, for example, to expedite inspection or repair of one or more electrical equipment articles 20, such as one of the cable accessories 34. In this way, the EEMS 6 can identify individual electrical equipment articles 20 that are predicted to fail, and prompt the user 18 to inspect and / or replace the article before the electrical equipment article fails.

[0053] Although the EEMS 6 is described as including an analysis engine, in some examples, the communication unit 26, the gateway 28, and / or the monitoring device 33 may perform some or all of the functions of the EEMS 6. For example, the monitoring device 33A may analyze sensor data generated by sensors of one or more monitoring devices 33 (e.g., from the monitoring device 33A itself, other monitoring devices, or a combination thereof). The monitoring device 33 may output (e.g., via the communication unit 26) a conclusion, assertion, or result of the analysis to the EEMS 6. Similarly, the gateway 28 may receive data from multiple monitoring devices 33, analyze the data, and send messages to the EEMS 6 and / or one or more monitoring devices 33.

[0054] In this way, the EEMS can monitor event data from the monitoring device to determine the health status of the electrical equipment product and / or predict whether the electrical equipment product will fail. By determining the health status or predicting whether the electrical equipment product will fail, the EEMS can enable the power utility to more effectively determine the location where the failure has occurred or is likely to fail, and manage or prioritize the repair or replacement of the electrical equipment, which can prevent or reduce failure events in the power grid.

[0055] Figure 2 is a block diagram that provides an operational perspective of an EEMS 6 that, when hosted as a cloud-based platform, is capable of supporting multiple different environments 8 each having multiple electrical equipment articles 20. Figure 2 In the example of FIG. 5 , the components of EEMS 6 are arranged according to multiple logical layers that implement the technology of the present disclosure. Each layer can be implemented by one or more modules including hardware, software, or a combination of hardware and software.

[0056] exist Figure 2 In the embodiment, the monitoring device 33 (directly or the communication hub 26 and / or the gateway 28) and the computing device 60 operate as a client 63, which communicates with the EEMS 6 via the interface layer 64. The computing device 60 typically executes a client software application, such as a desktop application, a mobile application, and a web application. The computing device 60 may represent Figure 1 Any computing device in computing device 16. Examples of computing device 60 may include, but are not limited to, portable or mobile computing devices (e.g., smart phones, wearable computing devices, tablet computers), laptop computers, desktop computers, smart TV platforms, servers, and the like.

[0057] As further described in the present disclosure, the monitoring device 33 communicates with the EEMS 6 (directly or via the communication hub 26 and / or the gateway 28) to provide a data stream collected from embedded sensors and other monitoring circuits, and to receive alerts, configuration data, and other communications from the EEMS 6. Client applications executing on the computing device 60 can communicate with the EEMS 6 to send and receive data retrieved, stored, generated, and / or otherwise processed by the services 68A-68H (collectively referred to as services 68). For example, a client application can request and edit event data, which includes analytical data stored at and / or managed by the EEMS 6. In some examples, the client application can request and display aggregated event data that summarizes or otherwise aggregates numerous individual instances of fault events and corresponding data collected from the monitoring device 33 and / or generated by the EEMS 6. The client application can interact with the EEMS 6 to query analytical data about past and predicted fault events. In some examples, the client application may output (e.g., display) data received from EEMS 6 to visualize such data to a user of client 63. As further illustrated and described below, EEMS 6 may provide data to a client application, which outputs the data for display in a user interface.

[0058] The client application executed on the computing device 60 may be implemented for different platforms, but includes similar or identical functionality. For example, the client application may be a desktop application compiled to run on a desktop operating system, or may be a mobile application compiled to run on a mobile operating system. As another example, the client application may be a web application, such as a web browser that displays a web page received from the EEMS 6. In the example of a web application, the EEMS 6 may receive a request from a web application (e.g., a web browser), process the request, and send one or more responses back to the web application. In this way, the collection of web pages, the web application processed by the client, and the server-side processing performed by the EEMS 6 together provide functionality for executing the technology of the present disclosure. In this way, the client application uses various services of the EEMS 6 according to the technology of the present disclosure, and these applications may operate in a variety of different computing environments (e.g., embedded circuits or processors of a desktop operating system, a mobile operating system, or a web browser, etc.).

[0059] like Figure 2As shown, the EEMS 6 includes an interface layer 64, which represents an application programming interface (API) or a set of protocol interfaces presented and supported by the EEMS 6. The interface layer 64 initially receives a message from any one of the clients 63 for further processing at the EEMS 6. Therefore, the interface layer 64 may provide one or more interfaces available to the client application executing on the client 63. In some examples, the interface may be an application programming interface (API) accessed through a network. The interface layer 64 may be implemented with one or more web servers. One or more web servers may receive incoming requests, process and / or forward data from the request to the service 68, and provide one or more responses to the client application that initially sent the request based on the data received from the service 68. In some examples, the one or more web servers that implement the interface layer 64 may include a runtime environment to deploy program logic that provides the one or more interfaces. As further described below, each service may provide a set of one or more interfaces that can be accessed via the interface layer 64.

[0060] In some examples, the interface layer 64 may provide a representative state transfer (RESTful) interface that uses HTTP methods to interact with services and manipulate the resources of the EEMS 6. In such examples, the service 68 may generate a JavaScript ObjectNotation (JSON) message that the interface layer 64 sends back to the client application that submitted the initial request. In some examples, the interface layer 64 provides a web service that uses a simple object access protocol (SOAP) to handle requests from client applications. In other examples, the interface layer 64 may use a remote procedure call (RPC) to handle requests from the client 63. Upon receiving a request from a client application to use one or more services 68, the interface layer 64 sends data to the application layer 66 that includes the service 68.

[0061] The data layer 72 of the EEMS 6 represents a data repository that uses one or more data repositories 74 to provide persistence for data in the EEMS 6. A data repository can generally be any data structure or software that stores and / or manages data. Examples of data repositories include, but are not limited to, relational databases, multidimensional databases, maps, and hash tables, to name a few. The data layer 72 can be implemented using relational database management system (RDBMS) software to manage data in the data repository 74. The RDBMS software can manage one or more data repositories 74, which can be accessed using structured query language (SQL). The data in one or more databases can be stored, retrieved, and modified using RDBMS software. In some examples, the data layer 72 can be implemented using an object database management system (ODBMS), an online analytical processing (OLAP) database, or other suitable data management system.

[0062] The electrical device data 74A of the data repository 74 may include data corresponding to a plurality of electrical device articles, such as the cable accessories 34. In some examples, the electrical device data 74A may include device or equipment data, manufacturing data, installation data, customer data, power distribution data, etc. For example, for each cable accessory in the cable accessories 34, the electrical device data 74A may include data identifying a manufacturing date, an installation date, a location (e.g., GPS coordinates, a street address, etc.), an entity that installed the cable accessory, a unique identifier (e.g., a serial number), a type of cable accessory, etc. For example, in the case of Figure 1 Before engaging the cables 32A and 32B with the cable accessory 34A, the installer may scan (e.g., using one of the computing devices 16, such as a mobile phone) a barcode on the cable accessory 34A, which includes device data representing a unique identifier, a manufacturing date, etc., and may upload the device data to the EEMS 6. In some cases, the mobile device may append data such as the current date and GPS coordinates as the installation date to the device data, and may send the device data to the EEMS 6 so that the EEMS 6 may store the device data for the cable accessory 34A in the electrical equipment data 74A.

[0063] like Figure 2As shown, the EEMS 6 also includes an application layer 66, which represents a collection of services 68 for implementing most of the basic operations of the EEMS 6. The application layer 66 receives data included in the requests received from the client devices 63, and further processes the data according to one or more of the services 68 called by these requests. The application layer 66 can be implemented as one or more discrete software services executed on one or more application servers (e.g., physical or virtual machines). That is, the application server provides an operating environment for executing the services 68. In some examples, the functions of the functional interface layer 64 and the application layer 66 as described above can be implemented at the same server.

[0064] As an example, the application layer 66 may include one or more separate software services 68 (e.g., processes) that communicate with each other (e.g., via a logical service bus 70). The service bus 70 generally represents a logical interconnection or a set of interfaces that allow different services to send messages to other services, such as through a publish / subscribe communication model. For example, each of the services 68 may subscribe to a specific type of message based on a standard set for the corresponding service. When a service publishes a message of a specific type on the service bus 70, other services that subscribe to that type of message will receive the message. In this way, each of the services 68 can communicate data with each other. As another example, the services 68 can communicate in a point-to-point manner using sockets or other communication mechanisms.

[0065] like Figure 2 As shown, each of the services 68 is implemented in a modular form within the EEMS 6. Although shown as a separate module for each service, in some examples, the functionality of two or more services may be combined into a single module or component. Each of the services 68 may be implemented in software, hardware, or a combination of hardware and software. In addition, the services 68 may be implemented as independent devices, separate virtual machines or containers, processes, threads, or software instructions typically for execution on one or more physical processors. In some examples, one or more of the services 68 may each provide one or more interfaces exposed through the interface layer 64. Therefore, a client application of the computing device 60 may call one or more interfaces of one or more of the services 68 to perform the techniques of the present disclosure.

[0066] According to the techniques of the present disclosure, service 68 may include an event processing platform including an event endpoint front end 68A, an event selector 68B, and an event processor 68C. Event endpoint front end 68A operates as a front end interface for receiving communications and sending communications to monitoring device 33 (e.g., directly or via communication hub 26 and / or gateway 28). In other words, event endpoint front end 68A operates as a front end interface deployed on Figure 1The event endpoint front end 68A operates as a front-line interface of a monitoring device 33 within the environment 8. In some cases, the event endpoint front end 68A may be implemented as a plurality of derived tasks or jobs to receive individual inbound communications of an event stream 69 carrying data sensed and captured by sensors of the monitoring device 33 from a monitoring device 33 (e.g., integrated within a cable accessory 34). For example, when receiving an event stream 69, the event endpoint front end 68A may derive tasks to quickly enqueue inbound communications (referred to as an event) and close communication sessions, thereby providing high-speed processing and scalability. Each incoming communication may, for example, carry recently captured data representing sensed conditions, motion, temperature, operation, or other data (commonly referred to as events). Communications exchanged between the event endpoint front end 68A and the cable accessory 34 may be real-time or pseudo-real-time, depending on communication latency and continuity.

[0067] The event selector 68B operates on the event stream 69 received from the monitoring device 33, the communication hub 26, and / or the gateway 28 via the front end 68A and determines the priority associated with the incoming events based on rules or classifications. Based on the priority, the event selector 68B queues the events for subsequent processing by the event processor 68C or the high priority (HP) event processor 68D. Additional computing resources and objects may be dedicated to the HP event processor 68D to ensure response to critical events, such as actual failures or predicted impending failures of the cable accessories 34. In response to processing high priority events, the HP event processor 68D may immediately call the notification service 68E to generate an alert, instruction, warning, or other similar message for output to the monitoring device 33 or the user 18 of the computing device 60. Events that are not classified as high priority are consumed and processed by the event processor 68C.

[0068] Generally, the event processor 68C or the high priority (HP) event processor 68D operates on the incoming event stream to update the event data 74B in the data repository 74. Generally, the event data 74B includes information indicating sensor data obtained from the monitoring device 33 (e.g., integrated with the cable accessory 34), Figure 1 The event data 74B may include device data, analysis data, or a combination thereof of the electrical device 20 of the monitoring device 33. For example, in some cases, the event data 74B may include the entire data sample stream obtained from the sensor of the monitoring device 33. In other cases, the event data 74B may include a subset of such data, for example, associated with a specific time period. For another example, the event data 74B may include analysis data indicating the results of the sensor data analysis performed by one or more of the monitoring device 33, the communication hub 26, and / or the gateway 28.

[0069] Event handlers 68C, 68D may create, read, update, and delete event data stored in event data 74B. Event data may be stored in corresponding database records as a structure of name / value pairs including data, such as a data table specified in a row / column format. For example, the name of a column may be "Attachment ID" and the value may be a column corresponding to an attachment ID. Figure 1 The event record may include data such as, but not limited to, a device identification, a data collection timestamp, and data indicating one or more sensed parameters.

[0070] The event selector 68B can direct the incoming event stream to the stream analysis service 68F, which is configured to perform deep processing of the incoming event stream to perform real-time analysis. The stream analysis service 68F can be configured, for example, to process multiple streams of the event data 74B in real time when the event data 74B is received, and compare the multiple streams of the event data with the historical data and the model 74C. In this way, the stream analysis service 68F can be configured to detect anomalies, transform the incoming event data value, or trigger an alert when predicting a possible failure event (e.g., a failure of the electrical equipment product 20). The historical data and model 74C may include, for example, one or more trained models configured to predict whether a failure event will occur, the expected remaining life of one or more electrical equipment products 20, and / or prioritize the maintenance of the electrical equipment product (e.g., repair or replacement). In addition, the stream analysis service 68F can generate outputs to be transmitted to the cable accessories 34 (e.g., via the notification service 68E) or the computing device 60 (e.g., via the notification service 68G or the record management and reporting service 68G).

[0071] In this way, the analysis service 68F processes the inbound event streams (which may be hundreds or thousands of event streams) from the monitoring devices 33 within the environment 8 to apply historical data and models 74C to calculate assertions, such as identified anomalies or predicted occurrences of impending failure events, based on the conditions sensed by the sensors of the monitoring devices 33. The stream analysis service 68F can publish the assertions to the notification service 68F and / or record management via the service bus 70 for output to any of the clients 63.

[0072] In this manner, the analysis service 68F may be configured as an active electrical equipment management system that predicts failure events (e.g., failures that may be imminent or that may occur within a threshold amount of time) and provides real-time alerts and reports. Additionally, the analysis service 68F may be a decision support system that provides technology for processing an inbound stream of event data to generate assertions in the form of statistics, conclusions, and / or recommendations for electrical equipment 20 for facilities, workers, and other remote users. For example, the analysis service 68F may apply historical data and models 74C to determine the probability of failure of one or more electrical equipment articles 20 (e.g., cable accessories 34), prioritize repair and / or replacement of electrical equipment articles, and the like. Thus, the analysis service 68F may maintain or otherwise use one or more models that provide risk metrics to predict failure events.

[0073] In some examples, the analysis service 68F may generate a user interface based on the processed data stored by the EEMS 6 to provide actionable data to any of the clients 63. For example, the analysis service 68F may generate dashboards, warning notifications, reports, etc. for output at any of the clients 63. Such data may provide various insights into baseline ("normal") operation across the environment 8 or electrical devices 20 (e.g., cable accessories 34), identification of any abnormal characteristics of the electrical devices 20 that may cause at least a portion of the electrical grid within the environment 8 to fail, and the like.

[0074] As described above, according to aspects of the present disclosure, the EEMS 6 may apply analysis to predict the likelihood of a fault event. Although other techniques may be used, in one exemplary implementation, the analysis service 68F utilizes machine learning when operating on the event stream in order to perform real-time analysis. That is, the analysis service 68F may include executable code generated by applying machine learning to training event stream data and known fault events to detect patterns. The executable code may take the form of software instructions or a set of rules, and is generally referred to as a model, which may then be applied to the event stream 69 to detect similar patterns and predict upcoming events. For example, the analysis service 68F may determine the condition or health state (e.g., the predicted remaining life) of a corresponding equipment product 20 (e.g., a cable accessory 34A), or predict whether / when a corresponding electrical equipment product 20 will experience a fault event. That is, the EEMS 6 may determine the likelihood or probability of a fault event based on applying historical data and the model 74C to event data received from the electrical device 20. For example, EEMS 6 may apply historical data and models 74C to event data from monitoring devices 33 to compute assertions, such as predicted occurrences of abnormal or impending fault events, based on sensor data, environmental conditions, and / or other event data corresponding to electrical equipment 20 monitored by monitoring devices 33 .

[0075] The EEMS 6 may apply analysis to identify relationships or correlations between sensed data from sensors of the monitoring devices 33 that monitor the electrical devices 20, environmental conditions of the environment in which the electrical devices 20 are located, the geographic region in which the electrical devices 20 are located, the types of electrical devices 20, the manufacturers and / or installers of the electrical devices, and the like. The EEMS 6 may determine conditions that may cause or predict an abnormally high occurrence of failure events in a certain environment or geographic region based on data collected across a population of electrical devices 20. The EEMS 6 may generate alert data based on analysis of the event data and transmit the alert data to the computing device 16 and / or the monitoring device 33. Thus, according to aspects of the present disclosure, the EEMS 6 may determine event data for the monitoring device 33, generate status indications, determine performance analysis, and / or perform anticipatory / preemptive actions (e.g., schedule maintenance or replacement) based on the likelihood of a failure event.

[0076] In some examples, the analysis service 68F may generate separate models for different environments, geographic regions, types of electrical equipment, or a combination thereof. The analysis service 68F may update the model based on event data received from the monitoring device 33. For example, the analysis service 68F may update the model for a specific geographic region, a specific type of electrical equipment, a specific environment, or a combination thereof based on event data received from the monitoring device 33. Alternatively or in addition, the analysis service 68F may transmit all or part of the generated code and / or machine learning model to the monitoring device 33, the communication hub 26, and / or the gateway 28 for execution thereon to provide local alerts in near real time.

[0077] Exemplary machine learning techniques that can be used to generate model 74C may include various learning methods such as supervised learning, unsupervised learning, and semi-supervised learning. Exemplary types of algorithms include Bayesian algorithms, clustering algorithms, decision tree algorithms, regularization algorithms, regression algorithms, instance-based algorithms, artificial neural network algorithms, deep learning algorithms, dimensionality reduction algorithms, etc. Various examples of specific algorithms include Bayesian linear regression, boosted decision tree regression and neural network regression, back propagation neural network, Apriori algorithm, K-means clustering, k-nearest neighbor (kNN), learning vector quantization (LVQ), self-organizing map (SOM), local weighted learning (LWL), ridge regression, least absolute shrinkage and selection operator (LASSO), elastic network and least angle regression (LARS), principal component analysis (PCA) and principal component regression (PCR).

[0078] The EEMS 6 may initially train the model 74C based on a training set of event data and, in some examples, based on data corresponding to a fault event. As a further exemplary description, the EEMS 6 may select a training set that includes a set of training instances, each of which includes an association between event data and a fault event. For each training instance in the training set, the EEMS 6 may modify one or more models 74C based on specific event data and specific fault events in the training instance, thereby changing the likelihood of a specific fault event predicted by the model in response to subsequent event data applied to the model 74C. In some examples, the training instances may be based on real-time or periodic data generated when the EEMS 6 manages data of one or more electrical equipment products and / or working environments. Therefore, one or more training instances in the set of training instances may be generated by using one or more electrical equipment products 20 after the EEMS 6 performs operations related to detecting or predicting fault events of the electrical equipment products 20.

[0079] By training the model based on the training set, the analysis service 68F can apply the model to the event data and generate a higher probability or score for a fault event corresponding to a training feature set that is more similar to the specific feature set. In the same manner, the analysis service 68F can apply the model to the event data and generate a lower probability or score for a fault event corresponding to a training feature set that is less similar to the specific feature set. Thus, the analysis service 68F can train one or more models 74C, receive event data from one or more monitoring devices 33 that monitor the corresponding electrical equipment article 20, and output one or more probabilities or scores indicating the likelihood of a fault event based on the received event data vector.

[0080] In some examples, the analysis service 68F may train one or more models 74C based on sensor data generated by sensors of the monitoring device 33. For example, the analysis service 68F may determine based on the training data that temperature predicts an impending failure. For example, arcing, partial discharge, increased connector resistance, tracking, and other processes may cause temperature increases, leading to a fault event. As another example, the analysis service 68F may determine based on the training data that acoustic emissions (e.g., arcing, partial discharge, and gas release) are associated with a fault event. As another example, the analysis service 68F may determine that electromagnetic emissions (e.g., generated by partial discharge and arcing) and / or current and / or voltage on the line may also provide an indication of a fault event. As another example, the analysis service 68F may determine based on the training data that temperature alone does not indicate a fault unless the damage progresses to a near complete failure (e.g., because the high temperature may be caused by high current). In contrast, the analysis service 68F determines based on the training data that the expected life and failure of the electrical device 20 are based at least in part on the line current of the cable 32 and the temperature of the cable accessories 34. In some examples, analysis service 68F may determine, based on DC measurements (e.g., by a power acquisition coil, an inductive communication coil, or a separate inductive coil of cable accessory 34), a relationship between a line current of cable 32 and a temperature of cable accessory 34. For another example, analysis service 68F may determine, based on training data, that a difference between a temperature of a cable (e.g., cable 32A) and a temperature of a corresponding cable accessory (e.g., accessory 34A) to which the cable is directly coupled indicates damage to cable accessory 34A, a lifespan of cable accessory 34A, and / or whether or when cable accessory 34A is predicted to experience a failure event.

[0081] In some examples, the analysis service 68F trains one or more models 74C based on fault events of electrical equipment products 20 and / or working environments with similar characteristics (e.g., the same type). In some examples, "same type" may refer to identical but separate instances of electrical equipment products. In other examples, "same type" may not refer to identical electrical equipment instances. For example, although not identical, the same type may refer to electrical equipment products in the same level or category of electrical equipment, electrical equipment of the same model, or one or more shared functions or physical characteristics of the same group, etc. Similarly, the same type of environment may refer to an instance of an identical but separate working environment type. In other examples, although not identical, the same type may refer to an environment in the same level or category of environment, such as "underground cable", "underwater cable", a specific state in the United States, climate, etc.

[0082] In some examples, analysis service 68F may predict a failure event based at least in part on applying model 74C to event data 69, such as sensor data generated by monitoring device 33 monitoring electrical equipment article 20. For example, analysis service 68F may apply one or more models 74C to sensor data indicating temperature, acoustic emissions, electromagnetic emissions, current, voltage, or any combination thereof to determine a state of health (e.g., a predicted remaining life) of electrical equipment 20 and / or predict a failure event of electrical equipment 20. In some examples, analysis service 68F may train model 74C based on data from multiple sensors, and may apply one or more models 74C to sensor data from multiple different sensors to more accurately predict the state of health of a given electrical equipment article and whether or when an electrical equipment article 20 will fail.

[0083] The analysis service 68F may apply one or more models 74C to the sensor data and other event data to determine the health state of the electrical equipment product 20 and / or whether or when the electrical equipment product will fail. In some examples, the analysis service 68F may apply one or more models 74C to the sensor data and device data to predict the health state and / or failure events. For example, the analysis service 68F may predict whether the cable accessory 34A will fail based on the sensor data and the type of cable accessory 34A. For example, the analysis service 68F may determine that a first type of cable accessory (e.g., a joint performed via "heat shrink") has a different failure mode than a second type of cable accessory (e.g., a joint performed via "cold shrink"). As another example, the analysis service 68F may determine that a cable accessory 34 installed by one installer or in one geographic location has a different failure mode than a cable accessory 34 installed by a different installer or geographic location.

[0084] According to aspects of the present disclosure, the EEMS 6 can schedule maintenance (e.g., repair or replacement) operations for the electrical device 20 based on the event data. For example, the analysis service 68F can predict the remaining life of the cable accessory 34A, determine that the predicted remaining life of the cable accessory 34A is less than a threshold life, and schedule a replacement operation for the cable accessory 34A based on such data. For another example, the analysis service 68F can rank the maintenance operations for multiple electrical equipment products, for example, based on the predicted remaining life, the confidence of the prediction, the importance of various electrical equipment products (e.g., the number of customers served by each product), etc. In some examples, the analysis service 68F can automatically order replacement electrical equipment 20 based on one or more models 74C.

[0085] Additionally or alternatively, according to aspects of the present disclosure, event data from the monitoring device 33 may be used to determine alerts and / or actively control the operation of the electrical device 20. For example, the EEMS 6 may respond to an event along a particular line (e.g., Figure 1 24A) to predict an impending failure of an electrical device and reconfigure or reroute the power to pass through another wire (e.g., Figure 1 24B) transmits power. As another example, analysis service 68F may output a notification (e.g., to computing device 16) in response to determining a health state or predicting a failure event of electrical device 20. For example, analysis service 68F may output a notification to one or more computing devices 16 via notification service 68E.

[0086] Likewise, EEMS 6 can determine the above-described performance characteristics and / or generate alert data based on applying the event data to model 74C. However, while these determinations are described with respect to EEMS 6, as described in greater detail herein, one or more other computing devices such as cable accessories 34, communication hub 26, and / or gateway 28 can be configured to perform all or a subset of such functions.

[0087] The record management and reporting service 68G processes and responds to messages and queries received from the computing device 60 via the interface layer 64. For example, the record management and reporting service 68G may receive a request for event data related to individual electrical equipment products 20, groups of electrical equipment products (e.g., product types), geographic areas of the environment 8, or the entire environment 8 from a client computing device. In response, the record management and reporting service 68G accesses the event data based on the request. When retrieving the event data, the record management and reporting service 68G constructs an output response to the client application that initially requested the data. In some examples, the data may be included in a document, such as an HTML document, or the data may be encoded in JSON format or presented by a dashboard application executed on the requesting client computing device. For example, as further described in the present disclosure, an exemplary user interface including event data is depicted in the accompanying drawings.

[0088] As an additional example, the records management and reporting service 68G may receive requests for discovery, analysis, and correlation of event data (e.g., event data of one or more monitoring devices 33 monitoring corresponding electrical equipment articles 20). For example, the records management and reporting service 68G may receive a query request for event data 74B from a client application within a historical time frame, such as a user may view event data over a period of time and / or a computing device may analyze event data over a period of time.

[0089] In an exemplary implementation, the service 68 may also include a security service 68H that authenticates and authorizes users and requests using the EEMS 6. Specifically, the security service 68H may receive authentication requests from client applications and / or other services 68 to access data in the data layer 72 and / or perform processing in the application layer 66. The authentication request may include credentials such as a username and password. The security service 68H may query the security data 74E to determine whether the username and password combination is valid. The security data 74E may include security data in the form of authorization credentials, policies, and any other data used to control access to the EEMS 6. As described above, the security data 74E may include authorization credentials, such as a combination of a valid username and password for an authorized user of the EEMS 6. Other credentials may include a device identifier or device profile that allows access to the EEMS 6.

[0090] The security service 68H may provide auditing and logging functionality for operations performed at the EEMS 6. For example, the security service 68H may record operations performed by the service 68 and / or data entered by the service 68 in the data layer 72. The security service 68H may store audit data such as recorded operations, accessed data, and rule processing results in audit data 74D. In some examples, in response to satisfying one or more rules, the security service 68H may generate events. The security service 68H may store data indicating these events in audit data 74D.

[0091] In general, although certain techniques or functions described herein are performed by certain components (e.g., EEMS 6 or monitoring device 33), it should be understood that the technology of the present disclosure is not limited in this manner. That is, certain techniques described herein may be performed by one or more of the components of the described system. For example, in some cases, the monitoring device 33 may have a relatively limited set of sensors and / or processing capabilities. In such cases, the gateway 28 and / or EEMS 6 may be responsible for processing most or all of the event data, determining the possibility of a fault event, etc. In other examples, the monitoring device 33, the communication hub 26, and / or the gateway 28 may have additional sensors, additional processing capabilities, and / or additional memory, thereby allowing such devices to perform additional technologies. The determination of which components are responsible for executing the technology may be based on, for example, processing costs, financial costs, power consumption, etc.

[0092] Figure 3 3 is a conceptual diagram of a cable accessory 340 configured to electrically and physically couple two cables 350A and 350B (collectively, cables 350) according to various techniques of the present disclosure. Cable accessory 340 can electrically and physically couple cable 350A and cable 350B. Cable accessory 340 can be Figure 1An example of a cable accessory 34, and cables 350A, 350B may be Figure 1 Example of cable 350.

[0093] exist Figure 3 In the example of , cable 350A includes multiple concentric (e.g., cylindrical) layers, such as center conductor 352, conductor shield 354, insulator 356, insulator shield 358, protective member 360 (also referred to as sheath 360) and jacket 362. However, in some examples, cable 350 may include more or fewer layers. Cable 350B may include similar multiple layers. It should be understood that the layers of cable 350 are not necessarily drawn to scale. Cable 350 may be configured for AC and / or DC power transmission.

[0094] The cable 350 may transmit voltages of 11 kV, 33 kV, 66 kV, 360 kV, and the like. In some cases, the cable 350 that transmits power between a power source and a substation may transmit a voltage of 360 kV or greater, which may be considered a "transmission-grade voltage". In some examples, the cable 350 transmits a voltage between 33 kV and 360 kV, such as 66 kV or 33 kV, which may be considered a "sub-transmission-grade voltage", and may provide power from the power source to an end user or customer (e.g., a customer utilizing a relatively large amount of power). As another example, the cable 350 that transmits power between a distribution substation and a distribution transformer may transmit a voltage less than 33 kV, which may be considered a "distribution-grade voltage". The cable 350 may also transmit power between a distribution substation or a distribution transformer (e.g., a pad transformer or a pole transformer) and an end user or consumer (e.g., a home and business), and may transmit a voltage between 360 volts and 240 volts, at which voltage the cable 350 may be referred to as a "secondary distribution line".

[0095] The center conductor 352 comprises a conductive material, such as copper or aluminum. In some examples, the center conductor 352 includes a single solid conductor or a plurality of stranded conductors. The diameter or thickness of the center conductor 352 is based on the current that the cable 350 is designed to transmit or conduct. In other words, the cross-section of the center conductor 352 is based on the current that the cable 350 is designed to transmit. For example, the center conductor 352 can be configured to transmit a current of 1,000 amperes or more.

[0096] Conductor shield 354 may include a semiconductive polymer, such as a carbon black loaded polymer. The semiconductive polymer may have a bulk resistivity in the range of about 5 Ω-cm to about 100 Ω-cm. Conductor shield 354 may be physically and electrically coupled to center conductor 352. Figure 3In the example of FIG. 3 , the conductor shield 354 is disposed between the center conductor 352 and the insulator 356 . The conductor shield 354 can provide a continuous conductive surface around the outside of the center conductor 352 , which can reduce or eliminate sparks that might otherwise be formed by the center conductor 352 .

[0097] In some examples, insulation 356 includes polyethylene, such as cross-linked polyethylene (which may be abbreviated as PEX, XPE, or XLPE) or ethylene propylene rubber (which may be abbreviated as EPR). The diameter or thickness of insulation 356 is based on the voltage that cable 350 is designed to transmit or conduct.

[0098] The insulating shield 358 may comprise a semiconductive polymer similar to the conductive shield 354. Figure 3 In some examples, the insulating shield 358 is disposed between the insulating member 356 and the protective member 360. The insulating shield 358 can be coupled to the insulating member 356. In some examples, the insulating shield 358 is electrically coupled to the protective member 360.

[0099] The shield 360 may include a conductive material, such as a metal foil or film or a wire. In some examples, the shield 360 may be referred to as a "ground conductor."

[0100] like Figure 3 As shown, jacket 362 (also referred to as a "sheath") is the outer layer of cable 350. Jacket 362 may be a plastic or rubber polymer, such as polyvinyl chloride (PVC), polyethylene (PE), or ethylene propylene diene monomer (EPDM).

[0101] The cable 350 may include additional layers, such as swellable or water blocking materials placed within the conductor strands (eg, strand fillers) or between various layers within the cable 350 .

[0102] According to aspects of the present disclosure, the cable accessory 340 includes a monitoring device 300 configured to monitor the health of the cable accessory 340, the cable, and / or an electrical device (e.g., a device near the accessory 340). The monitoring device 300 may be Figure 1 In some examples, the monitoring device 300 includes at least one processor 302, a communication unit 304, a power supply 306, one or more sensors 308, and a storage device 310. Figure 3 One example of a cable accessory 340 is shown. Many other examples of cable accessories 340 may be used in other instances and may include a subset of the components included in the exemplary cable accessory 340, or may include Figure 3 Additional components not shown in the exemplary cable accessory 340 in FIG.

[0103] The cable accessory 340 includes one or more power sources 306 to provide power to the components shown in the cable accessory 340. In some examples, the power source 306 includes a main power source for providing power and an auxiliary backup power source for providing power when the main power source is unavailable (e.g., fails or otherwise does not provide power). In some examples, the power source 306 includes a battery, such as a lithium-ion battery. As another example, the power source 306 may include a power acquisition device or circuit configured to obtain power from an external source. The power source 306 may include a power acquisition circuit configured to obtain power from the cable 350. For example, when current flows through the cable 302, the cable 302 generates a magnetic field. The power source 306 may include a circuit that generates current based on the magnetic field, so that the current generated by the power source 306 can provide power to the monitoring device 300. In some examples, the power source 306 may include a piezoelectric power acquisition device, a thermoelectric power acquisition device, a photovoltaic acquisition device, or any other power acquisition device.

[0104] One or more processors 302 may implement functionality and / or execute instructions within cable accessory 340. For example, processor 302 may receive and execute instructions stored by storage device 310. These instructions executed by processor 302 may cause cable accessory 340 to store and / or modify information within storage device 310 during program execution. Processor 302 may execute instructions of component analysis engine 318 to perform one or more operations in accordance with the techniques of this disclosure. That is, analysis engine 318 may be operated by processor 302 to perform the various functions described herein.

[0105] One or more communication units 304 of cable accessory 340 can communicate with external devices by transmitting and / or receiving data. For example, cable accessory 340 can use communication unit 304 to transmit and / or receive radio signals over a radio network, such as a cellular radio network. Examples of communication unit 304 include a network interface card (e.g., an Ethernet card), an optical transceiver, a radio frequency transceiver, a GPS receiver, or any other type of device that can send and / or receive information. Other examples of communication unit 304 may include GPS, Cellular (e.g., 3G, 4G), LPWAN, and Radio component. As another example, the communication unit 304 may communicate with an external device by transmitting and / or receiving data via wired communication.

[0106] The communication unit 304 may be configured to send and receive data via the cable 350 using power line communication (PLC) technology. The communication unit 304 may implement power line communication via narrowband frequencies (e.g., approximately 500 kHz or less) or wideband frequencies (e.g., approximately 1 MHz or more). Rather than utilizing inductive coupling (which may be expensive, cumbersome, and challenging to install), the communication unit 304 may include capacitive coupling circuitry to inject data into the cable 350 and extract data from the cable.

[0107] The monitoring device 300 includes one or more sensors 308 configured to generate sensor data indicating one or more conditions of the cable accessory 340. Examples of the sensor 308 include a temperature sensor (e.g., located inside and / or outside the cable accessory), a partial discharge sensor, a voltage and / or current sensor, etc. The sensor 308 may be attached on, inside, or near the cable accessory 340. In some examples, the sensor 308 includes one or more temperature sensors, such as an internal temperature sensor for monitoring the temperature inside the cable accessory 340 and / or an external temperature monitor for monitoring the temperature on the outside or surface of the cable accessory 340. The sensor 308 may include a partial discharge sensor for detecting partial discharge within the cable accessory 340. As another example, the sensor 308 may include a voltage and / or current sensor configured to measure the phase and / or magnitude of a voltage or current in the cable accessory 340.

[0108] One or more storage devices 310 can store information for processing by processor 302. In some examples, storage device 310 is a temporary memory, which means that the primary purpose of storage device 310 is not long-term storage. Storage device 310 can be configured for short-term storage of information as volatile memory, and therefore does not retain stored content when deactivated. Examples of volatile memory include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), and other forms of volatile memory known in the art.

[0109] In some examples, storage device 310 may also include one or more computer-readable storage media. Storage device 310 may be configured to store a larger amount of information than volatile memory. Storage device 310 may also be configured to perform long-term storage of information as non-volatile storage space and retain information after activation / deactivation cycles. Examples of non-volatile memory include flash memory or electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). Storage device 830 may store program instructions and / or data associated with a component such as analysis engine 318.

[0110] exist Figure 3In the example of FIG. 3 , storage device 310 includes electrical device data repository 312, event data repository 314, model repository 316, and analysis engine 318. Data repository 312, 314, and 316 may include relational databases, multidimensional databases, maps, and hash tables, or any data structure that stores data. In some examples, electrical device data repository 312 may be similar to Figure 2 The electrical device data repository 74A may be similar to the electrical device data repository 74A and may contain data similar to the electrical device data repository. Similarly, the event data repository 314 may be similar to the electrical device data repository 74A. Figure 2 The event data 74B described above may include data similar to the event data.

[0111] According to aspects of the present disclosure, the analysis engine 318 may be operated by the one or more processors 302 to perform one or more actions based on the sensor data generated by the sensor 308. The analysis engine 318 may be similar to Figure 2 The stream analysis engine 68F may include all or a subset of the functionality of the stream analysis engine.

[0112] In some examples, the analysis engine 318 may determine the health state of the cable accessory 340 based at least in part on sensor data generated by one or more of the sensors 308. For example, the analysis engine 318 may apply one or more rules (e.g., stored in the model repository 316) to the sensor data generated by one or more of the sensors 308 to determine the health state of the cable accessory 340. The rules may be pre-programmed or learned, for example, via machine learning. According to some examples, the model data storage device 316 contains rules that are trained based at least in part on event data and known fault events collected from multiple cable accessories 34. In such examples, the analysis engine 318 may train one or more models in the model repository 316 based on the event data in the event data repository 314. For another example, the monitoring device 300 may obtain information from Figure 1 and Figure 2 The EESR 6 receives data representing one or more models and may store the models in a model repository 316 .

[0113] The analysis engine 318 may determine the health state of the cable accessory 340 by predicting whether the cable accessory 340 will experience a fault event within a predetermined amount of time based at least in part on the rules and the sensor data. For example, the analysis engine 318 may predict whether the cable accessory 340 will fail within a predetermined amount of time by applying one or more models in the model repository 316 to the sensor data. As an example, the analysis engine 318 may apply the models in the model repository 316 to the sensor data stored in the event data repository 314. For example, the analysis engine 318 may receive temperature data indicating a temperature within the cable accessory 340 from a temperature sensor and apply the models in the model repository 316 to the temperature data. The analysis engine 318 may determine that the temperature is within a normal temperature range based on the temperature data and the models in the model repository 316, so that the analysis engine 318 may determine that the health state of the cable accessory 340 is nominal or normal. As another example, the analysis engine 318 may apply the models in the model repository 316 to the temperature data from the temperature sensor 308 and the current data from the current sensor 308. For example, temperature alone may not indicate a failure of the cable accessory 340 because temperature may increase as current increases. However, temperature and current may indicate a potential cable accessory failure, for example, if the measured temperature is relatively high even when the cable 350 is carrying a relatively small current. Therefore, in some examples, the analysis engine 308 may apply a model in the model repository 316 to the temperature data and the current data to determine the health status of the cable accessory 340.

[0114] In some examples, analysis engine 318 applies models in model repository 316 to event data repository 314 and other data, such as data within electrical device data repository 312. For example, analysis engine 318 can apply one or more models in model repository 316 to temperature data for cable accessories 340 stored in event data repository 314 and data indicating the type of cable accessories 340 stored in electrical device data repository 312 to predict whether cable accessories 340 will experience a fault event (e.g., fail to conduct power) within a predetermined amount of time.

[0115] The analysis engine 318 can perform various actions based on the health status of the cable accessory 340. For example, the analysis engine 318 can output a notification (e.g., to the EEMS 6) containing data indicating the health status of the cable accessory 340. For example, the notification can indicate that the cable accessory 340 is operating normally. As another example, the analysis engine 318 can output a notification indicating that the cable accessory 340 is predicted to fail within a predetermined amount of time or indicating the time at which the cable accessory 340 is predicted to fail.

[0116] Figure 4is a block diagram illustrating an example gateway 28 configured to communicate with a cable accessory 34A and an EEMS 6 in accordance with various techniques of the present disclosure. Figure 4 Only one specific example of a gateway 28 is shown. Many other examples of gateway 28 may be used in other instances and may include Figure 4 A subset of the components shown and / or may include Figure 4 Additional components not shown.

[0117] like Figure 4 As shown, the gateway 28 includes one or more processors 402, one or more communication units 404, one or more power supplies 406, and one or more storage devices 410. The processor 402, the communication unit 404, the power supply 406, and the storage component 410 may be similar to Figure 3 304, power supply 306 and storage component 310 of the embodiment of the present invention, and include functions similar to them. Therefore, for the sake of brevity, the description of the processor 402, the communication unit 404, the power supply 406 and the storage component 410 is omitted.

[0118] The gateway 28 may receive event data from a plurality of cable accessories 34 of one or more lines 24. The event data received by the gateway 28 may include data indicating sensor data generated by sensors of corresponding monitoring devices (e.g., monitoring cable accessories), such as all or part of the sensor data, a summary of the sensor data, and / or analysis results based on the sensor data. The gateway 28 may store all or a subset of the event data in the event data repository 414. In some examples, the gateway 28 may receive a notification from one or more cable accessories indicating the health status of the corresponding cable accessories 34.

[0119] The gateway 28 may act as an intermediary between the monitoring device 33 and the EEMS 6. For example, the gateway 28 may receive a notification from the monitoring device 33 and may send the notification to the EEMS 6. As another example, the gateway 28 may receive data from the EEMS 6. For example, the gateway 28 may receive a firmware update from the EEMS 6 and may send the firmware update from the EEMS 6 to the monitoring device 33. In some cases, the gateway 28 may receive (e.g., from the EEMS 6, the monitoring device 33, or both) device data, installation data, manufacturing data, etc. of a plurality of cable accessories 34, and may store the device data in the electrical device data repository 412.

[0120] In some examples, the analysis engine 418 determines the health status of the corresponding one or more electrical equipment products 20 (e.g., cable accessories 34) based at least in part on the event data in the event data repository 414. The analysis engine 418 may apply one or more rules to the event data to determine the health status of the corresponding cable accessories in the cable accessories 34. The rules may be pre-programmed or learned. The rules may be stored in the model repository 416. In some examples, the analysis engine 418 may train one or more machine learning models based on the event data and known fault events in the event data repository 414, and may store the trained models with the model repository 416. For another example, the gateway 28 may receive the rules from the monitoring device 33 or the EEMS 6.

[0121] The analysis engine 418 can apply rules to the event data to determine the health status of one or more electrical equipment articles 20, such as the cable accessories 34. For example, the analysis engine 418 can determine the health status of the cable accessory 34A by predicting whether the cable accessory 34A will fail within a predetermined amount of time or predicting the remaining life of the cable accessory 34A.

[0122] Gateway 28 may output data to EEMS 6. In some examples, gateway 28 sends all or a portion of the event data from monitoring device 33 to EEMS 6. As another example, gateway 28 may send a notification (e.g., generated by monitoring device 33 and / or gateway 28) to EEMS 6. For example, gateway 28 may output a notification indicating that the remaining life of a particular electrical equipment item (e.g., cable accessory 34A) is less than a threshold amount of time or indicating that a particular electrical equipment item is predicted to fail.

[0123] Figure 5 According to the technology disclosed in this invention Figure 1 An exemplary graphical user interface on the computing device 16 of the electrical equipment management system 2 in FIG. Figure 5 References Figure 1 and Figure 2 The electrical equipment management system 6 is described.

[0124] EEMS 6 may output a graphical user interface 500 representing an environment, such as environment 8B, that includes a plurality of electrical equipment articles. Figure 5 In the example of FIG. 5 , the electrical equipment item shown by the graphical user interface 500 is described as a cable accessory, however the graphical user interface 500 may also represent different types of electrical equipment. Figure 5 In the example of FIG. 5 , the graphical user interface 500 includes graphical elements (e.g., icons, symbols, text, or other graphical elements) for each of the plurality of cable accessories within the environment. For example, the graphical user interface 500 includes graphical icons 534A-534C, each of which represents a Figure 1 The corresponding cable accessories in the cable accessories 34.

[0125] The graphical user interface 500 may output data indicating the health status of the corresponding cable accessories. For example, the graphical user interface 500 may include a legend 502 having different graphical elements representing different health levels. Figure 5 In the example of FIG. 5 , graphical elements 534A and 534B indicate that the health status of the cable accessory represented by the respective graphical elements 534A, 534B is “normal”. A normal health status may indicate that the respective cable accessory is not predicted to fail within a threshold amount of time or is operating within typical operating parameters (e.g., within an expected temperature range, experiencing a typical amount of partial discharge events, etc.). Figure 5 As shown in the example of FIG. 5 , graphic element 534C indicates a cable accessory (e.g., Figure 1 In some examples, the graphical element 534C may indicate that the cable accessory 34C is predicted to fail within a threshold amount of time.

[0126] In some examples, graphical user interface 500 may include additional data, such as a map indicating the location of one or more cable accessories. For example, graphical user interface 500 may include graphical elements 536A-536C indicating a plurality of customers (e.g., households) served by the cable accessories.

[0127] The graphical user interface 500 may enable a user 18 of a computing device 16 to select a graphical element to receive additional information for the graphical element. For example, one or more computing devices 18 may output the graphical user interface 500 and may receive user input selecting a graphical element 534C. In response to receiving data indicating a user-selected graphical element 534C, the EEMS 6 may output additional information for the corresponding cable accessory to the computing device 18, such as data indicating an installation date, location, type of cable accessory, number of customers served by the cable accessory, and the like. In addition, the EEMS 6 also enables a user 16 of a computing device 18 to schedule maintenance or replacement of a cable accessory 34C, order parts, rewire power, or otherwise adjust the operation of a power grid, and the like.

[0128] Figure 6 is a flow diagram illustrating example operations performed by one or more computing devices configured to monitor electrical utility equipment, in accordance with various techniques of this disclosure. Figure 6 refer to Figure 1 and Figure 2 The system described.

[0129] One or more computing devices, such as a computing device of the EEMS 6 and / or a processor of the gateway 28, the hub 26, or the monitoring device 33, may obtain a first set of event data, referred to as training event data, from a plurality of cable accessories 34 (600). For example, before deploying a model for use within the EEMS 6 and / or other devices, such as the gateway 28, the hub 26, or the monitoring device 33, the training event data may be obtained for use in training one or more learning models. The training data may, for example, include known (i.e., previously identified, also referred to as "marked") fault events and associated sensory data. For another example, a monitoring device 33A monitoring a cable accessory 34A may receive event data from sensors of a corresponding monitoring device 33 of a cable accessory 34 within the monitoring environment 8B to train and improve the model in real time. In some cases, the sensors of the corresponding monitoring device 33 include temperature sensors, voltage sensors, partial discharge sensors, and the like. According to some examples, each of the monitoring devices 33 may output the training event data to the gateway 28, the EEMS 6, or both. Training event data may include data indicative of sensor data (e.g., all or a subset of sensor data, analysis results based on sensor data, a summary of sensor data, etc.), equipment data, manufacturing data, installation data, consumer data, power distribution data, or a combination thereof.

[0130] In response to receiving the training event data, one or more computing devices may train a model based at least in part on the event data from the cable accessory 34 (602). For example, the monitoring device 33, the gateway 28, and / or the EEMS 6 may utilize machine learning techniques to train a model that receives the training event data as input and outputs a predicted health state of one or more electrical equipment articles 20 such as the cable 32, the cable accessory 34, or the power delivery node 22. The one or more computing devices may train the one or more models using supervised learning, unsupervised learning, or semi-supervised learning. According to some examples, the one or more computing devices may train the one or more models based on known fault events. For example, the EEMS 6 may apply a plurality of training event data corresponding to known fault events to generate one or more models for predicting future fault events of a particular cable accessory when the EEMS 6 subsequently receives event data for the particular cable accessory. In some examples, the EEMS 6 may output the one or more models to the one or more cable accessories 34 or the gateway 28. As another example, the monitoring device 33 and / or the gateway 28 may train the model and may output the model to other monitoring devices, the gateway 28, or the EEMS 6.

[0131] After training the one or more models, in some examples, the one or more computing devices may receive a second set of event data, referred to as operational event data, from a particular monitoring device, such as monitoring device 33A monitoring cable accessory 34A (604). For example, monitoring device 33A may receive operational event data, including sensor data from sensors of monitoring device 33A. As another example, monitoring device 33A may output the operational event data to another monitoring device, gateway 28, and / or EEMS 6.

[0132] The one or more computing devices determine a health state of the cable accessory 34A based at least in part on the operational event data (606). In some examples, the monitoring device 33A, 33B, or 33C, the gateway 28, the EEMS 6, or a combination thereof may apply one or more models to the operational event data from the monitoring device 33A to determine the health state of the cable accessory 34A. For example, the monitoring device 33A may determine the health state of the cable accessory 34A locally, or the EEMS 6 may determine the health state of the cable accessory 34.

[0133] In response to determining the health status of the cable accessory 34A, one or more computing devices perform at least one action (608). In some examples, the monitoring device 33A performs the action by outputting a notification indicating the health status of the cable accessory 34A to the EEMS 6. For example, the notification may include data indicating that the cable accessory 34A is predicted to fail within a predetermined amount of time. Similarly, the gateway 28 and / or the EEMS 6 may output a notification indicating the health status of the cable accessory 34A. As another example, the EEMS 6 may perform the action by outputting data corresponding to a graphical user interface indicating the health status of the cable accessory 34A to one of the computing devices 18, so that one of the computing devices 18 may display the graphical user interface. As another example, the EEMS 6 schedules maintenance or replacement of the cable accessory 34A.

[0134] In the specific description of the preferred embodiment, reference is made to the accompanying drawings, which illustrate specific embodiments that can practice the present invention. The illustrated embodiments are not intended to be exhaustive of all embodiments according to the present invention. It should be understood that other embodiments may be utilized without departing from the scope of the present invention, and structural or logical changes may be made. Therefore, the following detailed description should not be considered to have a limiting meaning, and the scope of the present invention is limited by the appended claims.

[0135] Figure 7 is a diagram illustrating example partial discharge events associated with known fault events in accordance with various techniques of the present disclosure. Figure 7 References as references Figures 1 to 3The monitoring device 33, 300 and EEMS 6 are described. For example, the sensor 308 of the monitoring device 300 may include one or more partial discharge sensors. The partial discharge sensor can detect partial discharge events over time. The x-axis of the graph 700 represents time, and the y-axis of the graph 700 represents the amount of partial discharge events per unit time (e.g., per hour).

[0136] In some examples, a computing device (eg, monitoring device 300 or EEMS 6) may train a model indicating the health status of a cable accessory or cable based on the partial discharge data and known fault events plotted in graph 700 (eg, Figure 2 History and Data Model 74C and / or Figure 3 316). Although diagram 700 shows a partial discharge event detected by a single monitoring device for a single fault event, the EEMS 6 or monitoring device 300 may receive event data indicating partial discharge events from multiple monitoring devices 300 each associated with a respective fault event, and may train a model based at least in part on the event data from the multiple monitoring devices. In other words, the EEMS 6 and / or monitoring device 300 (or any other computing device, such as Figure 1 The gateway 28) may train the model based on known fault events associated with the corresponding monitoring devices and event data (eg, including partial discharge data) from the corresponding monitoring devices.

[0137] For example, the EEMS 6 or monitoring device 300 may associate known fault events with signal amplitude, starting voltage, discharge phase angle (e.g., power delivery), frequency content, etc. For another example, the EEMS 6 or monitoring device 300 may associate known fault events based on groups or clusters of partial discharge events, the time between partial discharge events or clusters of partial discharge events, the amount of discharge events per time, the amount of discharge events per phase angle, the minimum or maximum starting voltage, or any other variable. In some cases, the EEMS 6 or monitoring device 300 may determine the actual distribution of events at various corresponding phase angles, determine a normal distribution of events and phase angles, and associate known fault events based on the deviation of the actual distribution from the normal distribution. In addition, the EEMS 6 or monitoring device 300 may associate known fault events with the time-dependent characteristics of the above statistical data.

[0138] Figure 8 Includes illustrations of various techniques according to the present disclosure Figure 7 The x-axis of graphs 800A to 800C (collectively, graph 800) represents the phase angle, and the y-axis of graphs 800A to 800C represents the amount of partial discharge events at different phase angles. Graph 800A shows Figure 7800B shows the partial discharge events per phase angle at the first hour of the data set shown. Figure 7 The partial discharge events per phase angle at the 19th hour of the data set shown, and Figure 800C shows Figure 7 Partial discharge events per phase angle at hour 37 of the data set shown.

[0139] As mentioned above Figure 7 As described above, the computing device (e.g., EEMS 6 and / or monitoring device 33, 300) can train a model indicating the health status of the cable accessories or cables based on the partial discharge data and known fault events plotted in the graph 800 (e.g., Figure 2 History and Data Model 74C and / or Figure 3 For example, the EEMS 6 may correlate known fault events with the amount and phase angle of partial discharge events over time.

[0140] 9A to 9C Included are graphs showing sensor data associated with known fault events in accordance with various techniques of the present disclosure. 9A to 9C References as references Figures 1 to 3 The monitoring device 33, 300 and EEMS 6 are described. For example, the sensor 308 of the monitoring device 300 may include a current sensor and one or more temperature sensors. The x-axis of the graphs 900, 902 and 904 represents time. The y-axis of the graph 900 represents the amount of current, the y-axis of the graph 902 represents the temperature of the connector (e.g., a connector coupling two cables), and the y-axis of the graph 904 represents the peak temperature of the connector.

[0141] Fig. 9A The current circulating through the cable accessory is shown, where the current is cycled on for 8 hours, then off for 16 hours, and then repeated in a similar manner for multiple cycles (eg, one cycle equals 24 hours). Fig. 9B Shown are the temperatures in the cable enclosure as the current is cycled on and off. Fig. 9C The peak temperature of the cable accessories is shown.

[0142] In some examples, a computing device (e.g., monitoring device 300 or EEMS 6) may train a model (e.g., a health status of a cable accessory or cable) based on current and temperature data generated by current and temperature sensors of monitoring device 300. Figure 2 History and Data Model 74C and / or Figure 3900 to 904 illustrate sensor data generated by a single monitoring device for a single fault event, the EEMS 6 or monitoring device 300 may receive event data indicative of sensor data from multiple monitoring devices 300 each associated with a respective fault event, and may train a model based at least in part on the event data from the multiple monitoring devices. In other words, the EEMS 6 and / or monitoring device 300 (or any other computing device, such as Figure 1 The gateway 28 of the monitoring device 300 can train the model based on known fault events associated with the corresponding monitoring device and event data (e.g., including current and / or temperature data) from the corresponding monitoring device. For example, the EEMS 6 or the monitoring device 300 can associate the known fault events with the current and the connector temperature.

[0143] The EEMS 6 and / or monitoring device 300 may correlate current and temperature and determine that at relatively low currents (e.g., approximately 740 amps), the maximum temperature in a cable accessory (e.g., a connector of a cable joint) remains stable (e.g., approximately 100 degrees Celsius). However, the EEMS 6 and / or monitoring device 300 may determine that when the current is higher (e.g., to approximately 865 amps), the temperature gradually increases (e.g., to approximately 150 degrees Celsius) even when the current is maintained at approximately 865 amps when the current is cycled on, and the peak current in the cable accessory increases rapidly after the current remains at the higher current for a threshold amount of time. For example, graph 904 indicates a failure of a cable accessory due to thermal runaway after approximately 4500 hours of cycling on / off, or after a near failure due to thermal runaway for 1000 hours after the current was increased from approximately 740 amps to approximately 865 amps. Thus, the EEMS 6 and / or the monitoring device 300 may train a model indicative of the health status of a cable accessory or cable by correlating known fault events with the temperature of the cable or cable accessory and the current in the cable or cable accessory.

[0144] As another example, the EEMS 6 and / or the monitoring device 300 may train a model based on current, temperature of cable accessories, ambient temperature (eg, soil temperature, air temperature), humidity, or other data such as equipment, manufacturing data, installation data, and the like.

[0145] Although Figure 7 9 show data sets of partial discharge data, voltage data, current data or temperature data shown in separate figures, respectively, but in Figure 79, the EEMS 6 and / or monitoring device 33, 300 may train a model indicating the health status of a cable accessory or cable based on any one data set or any combination of such data sets. In other words, the EEMS 6 may train one or more models stored in the model 74C based on partial discharge sensor data alone, or based on a combination of data from multiple sensors and / or other data sources such as event data, equipment data, installation data, manufacturing data, weather data, etc.

[0146] Fig.10 1000 according to one or more aspects of the present disclosure. The monitoring device 1000 can monitor one or more conditions of a component of a power line, such as a cable accessory 1034 that couples two cables 1032A-1032B. The cable accessory 1034 can be Figure 1 Cable accessories 34 or Figure 3 1032A-1032B (collectively, cables 1032) may be reference Figure 3 The monitoring device 1000 may be an example of a cable 350. Figure 1 Monitoring device 33 and / or Figure 3 An example of a monitoring device 300 is shown.

[0147] According to some examples, monitoring device 1000 includes housing 1002. In some examples, housing 1002 includes a rigid or semi-rigid structure configured to house and protect one or more components of monitoring device 1000, such as one or more processors, one or more communication units, one or more power supplies, one or more sensors, and / or one or more storage devices, as described in reference to Figure 3 The monitoring device 300 is shown and described. The housing 1002 may include one or more housing portions. Fig.13 In the example of FIG. 1 , housing 1002 includes a plurality of housing portions 1006A-1006B (collectively, housing portions 1006). According to some examples, housing portion 1006 may include one or more sensors, such as a temperature sensor, a voltage sensor, a current sensor, a partial discharge sensor, a humidity sensor, an acoustic sensor, or any other type of sensor that monitors the condition of a cable accessory or cable.

[0148] The monitoring device 1000 may include one or more attachment devices configured to attach the corresponding housing portion 1006 to a cable or cable accessory. Figure 1In the example of FIG. 1 , the monitoring device includes attachment devices 1008A- 1008D (collectively, attachment devices 1008 ). Attachment devices 1008A and 1008B may be configured to attach or couple housing portions 1006A- 1006B to cables 1032 and / or cable accessories 1034 .

[0149] As another example, monitoring device 1000 may include attachment devices 1008C and 1008D, which may include one or more components of monitoring device 1000. For example, attachment devices 1008C and 1008D may include a power acquisition device and a communication unit, respectively. In other words, in some examples, components of monitoring device 1000 may be integrated into attachment device 1008.

[0150] The attachment device 1008 may include mechanical fasteners (e.g., screws, straps, etc.), adhesives, or other devices to couple a component of the monitoring device 1000 (e.g., housing portion 1006) to a cable or cable accessory. For example, the attachment device 1008 may be a strap (e.g., a flexible strap) configured to surround the circumference of a cable or cable accessory.

[0151] In some examples, the monitoring device 1000 includes one or more external sensors 1010 configured to monitor conditions of the cable enclosure or external to the cable. For example, the sensor 1010 may monitor ambient or environmental characteristics (e.g., environmental conditions of the cable enclosure or external to the cable). For example, the sensor 1010 may include a temperature sensor configured to monitor air temperature or ground temperature.

[0152] Components within housing portion 1006A may be communicatively coupled to other components within other housing portions (e.g., 1006B) or components within attachment devices (e.g., attachment devices 1008C-1008D). For example, communication links 1012A, 1012B, 1012C, and 1012D (collectively, communication links 1012) may communicatively couple external sensor 1010, components within housing portion 1006B, components within attachment device 1008C, and components within attachment device 1008D to a processor and / or other electronic components housed within housing portion 1006A. Communication links 1012 may include fiber optic cables, conductive cables (e.g., copper or aluminum wires), metal traces, etc.

[0153] In operation, the monitoring device 1000 may include Figure 3 For example, the sensors of the monitoring device 1000 may generate sensor data indicating one or more conditions of the cable 1032 and / or the cable accessory 1034. The monitoring device 1000 may output the event data to another computing device (e.g., Figure 1 to Figure 2EEMS 6). In some examples, the event data may include all or part of the sensor data, analysis results based on the sensor data, or a combination thereof. According to some examples, the monitoring device 1000 may determine the health status of the cable 1032 and / or the cable accessory 1034 based at least in part on the sensor data, and may output event data indicating the health status. For another example, the monitoring device 1000 may output a summary of the sensor data, and the EEMS 6 may determine the health status of the cable 1032 and / or the cable accessory 1034.

[0154] Fig.11 1 is a conceptual diagram illustrating an exemplary cable accessory 1100 coupling two cables according to one or more aspects of the present disclosure. The monitoring device 1100 can monitor one or more conditions of a component of a power line, such as a cable accessory 1134 coupling two cables 1132A-1132B. The cable accessory 1134 can be Figure 1 Cable accessories 34 or Figure 3 1132B (collectively, cables 1132) may be reference Figure 3 The monitoring device 1100 may be an example of a cable 350. Figure 1 Monitoring device 33 and / or Figure 3 An example of a monitoring device 300 is shown.

[0155] According to some examples, monitoring device 1100 includes housing 1102. In some examples, housing 1102 includes a rigid or semi-rigid structure configured to house and protect one or more components of monitoring device 1100, such as one or more processors, one or more communication units, one or more power supplies, one or more sensors, and / or one or more storage devices, as described in reference to Figure 3 The monitoring device 300 is shown and described. Fig.11 In some examples, housing 1102 is a single unit that includes one or more sensors, such as a temperature sensor, a voltage sensor, a current sensor, a partial discharge sensor, a humidity sensor, an acoustic sensor, or any other type of sensor that monitors the condition of a cable accessory or cable.

[0156] The monitoring device 1100 may include an attachment device 1108 configured to attach the housing 1102 to a cable or a cable accessory. The attachment device 1108 may include a mechanical fastener (e.g., a screw, a strap, etc.), an adhesive, or other means of coupling the housing 1102 to the cable or cable accessory. For example, the attachment device 1108 may be a strap (e.g., a flexible strap) configured to surround the circumference of the cable or cable accessory.

[0157] In operation, the monitoring device 1100 may include Figure 3 For example, the sensors of the monitoring device 1100 may generate sensor data indicative of one or more conditions of the cable 1132 and / or the cable accessory 1134. The monitoring device 1100 may output the event data to another computing device (e.g., Figure 1 to Figure 2 EEMS 6). In some examples, the event data may include all or part of the sensor data, analysis results based on the sensor data, or a combination thereof. According to some examples, the monitoring device 1100 may determine the health status of the cable 1132 and / or the cable accessory 1134 based at least in part on the sensor data, and may output event data indicating the health status. For another example, the monitoring device 1100 may output a summary of the sensor data, and the EEMS 6 may determine the health status of the cable 1132 and / or the cable accessory 1134.

[0158] Fig.12 1 is a conceptual diagram illustrating an exemplary cable accessory 1200 coupled to an exemplary cable according to one or more aspects of the present disclosure. The monitoring device 1200 can monitor one or more conditions of a component of a power line such as a cable accessory 1234 that couples a cable 1232 to a terminal device 1236 (e.g., a terminal lug). The cable accessory 1234 can be Figure 1 Cable accessories 34 or Figure 3 An example of a cable accessory 340. Fig.12 In the example of FIG. 1 , the cable accessory 1234 is a cable terminal. The cable 1232 may be a reference Figure 3 The monitoring device 1200 may be an example of a cable 350. Figure 1 Monitoring device 33 and / or Figure 3 An example of a monitoring device 300 is shown.

[0159] According to some examples, monitoring device 1200 includes housing 1202. In some examples, housing 1202 includes a rigid or semi-rigid structure configured to house and protect one or more components of monitoring device 1200, such as one or more processors, one or more communication units, one or more power supplies, one or more sensors, and / or one or more storage devices, as described in reference to Figure 3 The monitoring device 300 is shown and described. The housing 1202 may include one or more housing portions. Fig.13In some examples, housing 1202 includes multiple housing portions 1206A-1206B (collectively, housing portions 1206). According to some examples, housing portion 1206 may include one or more sensors, such as temperature sensors, voltage sensors, current sensors, partial discharge sensors, humidity sensors, acoustic sensors, or any other type of sensor that monitors the condition of a cable accessory or cable.

[0160] The monitoring device 1200 may include one or more attachment devices configured to attach the corresponding housing portion 1206 to a cable or cable accessory. Figure 1 In an example of, the monitoring device includes attachment devices 1208A-1208D (collectively, attachment devices 1208). Attachment devices 1208A and 1208B may be configured to attach or couple housing portions 1206A-1206B to cables 1232 and / or cable accessories 1234. As another example, the monitoring device 1200 may include attachment devices 1208C and 1208D, which may include one or more components of the monitoring device 1200. For example, attachment devices 1208C and 1208D may include a power acquisition device and a communication unit, respectively. In other words, in some examples, components of the monitoring device 1200 may be integrated into the attachment device 1208.

[0161] The attachment device 1208 may include mechanical fasteners (e.g., screws, straps, etc.), adhesives, or other devices to couple a component of the monitoring device 1200 (e.g., housing portion 1206) to a cable or cable accessory. For example, the attachment device 1208 may be a strap (e.g., a flexible strap) configured to surround the circumference of a cable or cable accessory.

[0162] In some examples, the monitoring device 1200 includes one or more external sensors 1210 configured to monitor conditions of the cable enclosure or external to the cable. For example, the sensor 1210 may monitor ambient or environmental characteristics (e.g., environmental conditions of the cable enclosure or external to the cable). For example, the sensor 1210 may include a temperature sensor configured to monitor air temperature or ground temperature.

[0163] Components within housing portion 1206A may be communicatively coupled to other components within other housing portions (e.g., 1206B) or components within attachment devices (e.g., attachment devices 1208C-1208D). For example, communication links 1212A, 1212B, 1212C, and 1212D (collectively, communication links 1212) may communicatively couple external sensor 1210, components within housing portion 1206B, components within attachment device 1208C, and components within attachment device 1208D to a processor and / or other electronic components housed within housing portion 1206A. Communication links 1212 may include fiber optic cables, conductive cables (e.g., copper or aluminum wires), metal traces, etc.

[0164] In operation, the monitoring device 1200 may include Figure 3 For example, the sensors of the monitoring device 1200 may generate sensor data indicative of one or more conditions of the cable 1232 and / or the cable accessory 1234. The monitoring device 1200 may output the event data to another computing device (e.g., Figure 1 to Figure 2 EEMS 6). In some examples, the event data may include all or part of the sensor data, analysis results based on the sensor data, or a combination thereof. According to some examples, the monitoring device 1200 may determine the health status of the cable 1232 and / or the cable accessory 1234 based at least in part on the sensor data, and may output event data indicating the health status. For another example, the monitoring device 1200 may output a summary of the sensor data, and the EEMS 6 may determine the health status of the cable 1232 and / or the cable accessory 1234.

[0165] Fig.13 1 is a conceptual diagram illustrating an exemplary cable accessory 1300 coupled to an exemplary cable according to one or more aspects of the present disclosure. The monitoring device 1300 can monitor one or more conditions of a component of a power line such as a cable accessory 1334 that couples a cable 1332 to a terminal device 1336 (e.g., a terminal lug). The cable accessory 1334 can be Figure 1 Cable accessories 34 or Figure 3 An example of a cable accessory 340. Fig.12 In the example of FIG. 1 , the cable accessory 1334 is a cable terminal. The cable 1332 may be a reference Figure 3 The monitoring device 1300 may be an example of a cable 350. Figure 1 Monitoring device 33 and / or Figure 3 An example of a monitoring device 300 is shown.

[0166] According to some examples, monitoring device 1300 includes housing 1302. In some examples, housing 1302 includes a rigid or semi-rigid structure configured to house and protect one or more components of monitoring device 1300, such as one or more processors, one or more communication units, one or more power supplies, one or more sensors, and / or one or more storage devices, as described in reference to Figure 3 The monitoring device 300 is shown and described. Fig.13 In examples, housing 1302 is a single unit according to some examples, housing 1302 includes one or more sensors, such as a temperature sensor, a voltage sensor, a current sensor, a partial discharge sensor, a humidity sensor, an acoustic sensor, or any other type of sensor that monitors the condition of a cable accessory or cable.

[0167] The monitoring device 1300 may include an attachment device 1308 configured to attach the housing 1302 to a cable or cable accessory. The attachment device 1308 may include a mechanical fastener (e.g., a screw, a strap, etc.), an adhesive, or other means of coupling the housing 1302 to the cable or cable accessory. For example, the attachment device 1308 may be a strap (e.g., a flexible strap) configured to surround the circumference of the cable or cable accessory.

[0168] Attachment device 1308 may include mechanical fasteners (e.g., screws, straps, etc.), adhesives, or other devices to couple a component of monitoring device 1300 (e.g., housing portion 1306) to a cable or cable accessory. For example, attachment device 1308 may be a strap (e.g., a flexible strap) configured to surround the circumference of a cable or cable accessory.

[0169] In some examples, monitoring device 1300 includes one or more external sensors 1310 configured to monitor conditions of cable accessories or external to the cable. For example, sensor 1310 may monitor ambient or environmental characteristics (e.g., environmental conditions of cable accessories or external to the cable). For example, sensor 1310 may include a temperature sensor configured to monitor air temperature or ground temperature. Sensor 1310 may be communicatively coupled to components of monitoring device 1300 via communication link 1312.

[0170] In operation, monitoring device 1300 may include Figure 3 For example, the sensors of the monitoring device 1300 may generate sensor data indicating one or more conditions of the cable 1332 and / or the cable accessory 1334. The monitoring device 1300 may output the event data to another computing device (e.g., Figure 1 to Figure 2EEMS 6). In some examples, the event data may include all or part of the sensor data, analysis results based on the sensor data, or a combination thereof. According to some examples, the monitoring device 1300 may determine the health status of the cable 1332 and / or the cable accessory 1334 based at least in part on the sensor data, and may output event data indicating the health status. For another example, the monitoring device 1300 may output a summary of the sensor data, and the EEMS 6 may determine the health status of the cable 1332 and / or the cable accessory 1334.

[0171] In some examples, the present disclosure describes a device for monitoring a physical condition of a connection device on a shielded power cable, the shielded power cable having a center conductor and a first insulation layer surrounding the center conductor, the device comprising: a sensor for detecting data associated with a local characteristic of the connection device; an analog-to-digital converter for digitizing an analog signal from the sensor; a processor for controlling the monitoring device; and a communication unit for transmitting the digital signal out of the monitoring device, wherein the device is attached to the connection device. In some examples, the communication unit comprises a PLC protocol or a wireless protocol.

[0172] In some examples, the present disclosure describes a device for monitoring a physical condition of a connection device on a shielded power cable, the shielded power cable having a center conductor and a first insulation layer surrounding the center conductor, the device comprising: a sensor for detecting data associated with a local characteristic of the connection device; an analog-to-digital converter for digitizing an analog signal from the sensor; a processor for controlling the monitoring device; and a communication unit for transmitting the digital signal out of the monitoring device disposed in a housing, wherein the housing is attached to the connection device. In some examples, the housing includes a plurality of housing portions that can be connected together around at least a portion of the connection device. In some examples, the device includes a first set of electrodes and a second set of electrodes, the first set of electrodes being used to connect at least one of the sensor and the communication unit in contact with the power cable when the housing is attached to the cable, and the second set of electrodes being used to connect a power harvester to the power cable when the housing is attached to the connection device.

[0173] Unless otherwise indicated, all numbers expressing feature sizes, amounts, and physical properties used in the specification and claims are to be understood in all instances as modified by the term “about.” Accordingly, unless indicated to the contrary, the numerical parameters set forth in the foregoing specification and the appended claims are approximations that may vary depending upon the desired properties sought to be obtained by one skilled in the art utilizing the teachings disclosed herein.

[0174] Unless the content clearly dictates otherwise, as used in this specification and the appended claims, the singular forms "a / kind", "the" and "the" encompass embodiments having plural referents. Unless the content clearly dictates otherwise, as used in this specification and the appended claims, the term "or" is generally employed in its sense including "and / or".

[0175] If spatially relative terms are used herein, including but not limited to "proximal," "distal," "lower," "upper," "below," "below," "above," and "on top," they are used for convenience in describing the spatial relationship of one or more elements relative to another element. In addition to the specific orientations depicted in the drawings and described herein, such spatially relative terms encompass different orientations of the device when in use or operation. For example, if an object depicted in a figure is flipped or inverted, portions previously described as being below or under other elements should now be above or on top of these other elements.

[0176] As used herein, for example, when an element, component or layer is described as forming a "consistent interface" with another element, component or layer, or "on it", "connected to it", "coupled to it", "stacked on it" or "in contact with it", it may be directly on it, directly connected to it, directly coupled to it, directly stacked on it or directly in contact with it, or for example, an intervening element, component or layer may be on a specific element, component or layer, or connected to it, coupled to it or in contact with it. For example, when an element, component or layer is, for example, referred to as "directly on" another element, "directly connected to" another element, "directly coupled to" another element or "directly in contact with" another element, there are no intervening elements, components or layers. The technology of the present disclosure can be implemented in a variety of computer devices, such as servers, laptop computers, desktop computers, notebook computers, tablet computers, handheld computers, smart phones, etc. Any component, module or unit is described to emphasize the functional aspects, and does not necessarily need to be implemented by different hardware units. The technology described herein can also be implemented in hardware, software, firmware, or any combination thereof. Any features described as modules, units, or components may be implemented together in an integrated logic device or may be implemented independently as separate but cooperating logic devices. In some cases, various features may be implemented as an integrated circuit device, such as an integrated circuit chip or chipset. In addition, although a variety of different modules are described throughout this specification, many of which perform unique functions, all functions of all modules may be combined into a single module, or further split into other additional modules. The modules described herein are exemplary only and are described as such for ease of understanding.

[0177] If implemented in software, the technology may be implemented at least in part by a computer-readable medium including instructions that, when executed in a processor, perform one or more of the methods described above. The computer-readable medium may include a tangible computer-readable storage medium and may form part of a computer program product, which may include packaging materials. The computer-readable storage medium may include a random access memory (RAM) such as a synchronous dynamic random access memory (SDRAM), a read-only memory (ROM), a non-volatile random access memory (NVRAM), an electrically erasable programmable read-only memory (EEPROM), a flash (FLASH) memory, a magnetic or optical data storage medium, etc. The computer-readable storage medium may also include a non-volatile storage device, such as a hard disk, a magnetic tape, a compact disk (CD), a digital versatile disk (DVD), a Blu-ray disc, a holographic data storage medium, or other non-volatile storage devices.

[0178] The term "processor" as used herein may refer to any of the aforementioned structures or any other structure suitable for implementing the technology described herein. In addition, in some aspects, the functions described herein may be provided in a dedicated software module or hardware module configured to perform the technology of the present disclosure. Even if implemented in software, the technology may use hardware such as a processor for executing the software, and a memory for storing the software. In any such case, the computer described herein may define a specific machine capable of performing the specific functions described herein. In addition, the technology may be fully implemented in one or more circuits or logic elements that may also be considered as processors.

[0179] In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or codes and executed by a hardware-based processing unit. A computer-readable medium may include a computer-readable storage medium, which corresponds to a tangible medium such as a data storage medium, or a communication medium, which includes, for example, any medium that facilitates the transfer of a computer program from one place to another according to a communication protocol. In this manner, a computer-readable medium may generally correspond to (1) a non-transient tangible computer-readable storage medium or (2) a communication medium, such as a signal or carrier wave. A data storage medium may be any available medium that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in the present disclosure. A computer program product may include a computer-readable medium.

[0180] As an example and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, flash memory or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave are used to transmit instructions from a website, server or other remote source, then the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of the medium. However, it should be understood that computer-readable storage media and data storage media do not include connections, carriers, signals or other transient media, but are directed to non-transient tangible storage media. The disks and optical disks used include compact disks (CDs), laser optical disks, optical disks, digital versatile disks (DVDs), floppy disks and blue-ray disks, wherein the disks usually reproduce data magnetically, and the optical disks reproduce data optically by lasers. The above combination should also be included in the scope of computer-readable media.

[0181] Instructions may be executed by one or more processors such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuits. Thus, the term "processor" as used may refer to any of the foregoing structures or any other structure suitable for implementing the described techniques. Furthermore, in some aspects, the described functionality may be provided within dedicated hardware and / or software modules. Moreover, these techniques may be implemented entirely in one or more circuits or logic units.

[0182] The technology of the present disclosure may be implemented in a variety of devices or apparatuses including a wireless handset, an integrated circuit (IC), or a set of ICs (e.g., a chipset). Various components, modules, or units are described in the present disclosure to emphasize the functional aspects of the device configured to perform the disclosed technology, but do not necessarily need to be implemented by different hardware units. Instead, as described above, various unit combinations may be combined in hardware units or provided by a collection of interoperable hardware units including one or more processors as described above, in combination with appropriate software and / or firmware.

[0183] It should be appreciated that, according to this example, certain actions or events in any of the methods described herein may be performed in a different order, may be added, combined, or omitted together (e.g., not all described actions or events are necessary for the practice of the method). In addition, in some examples, actions or events may be performed simultaneously rather than sequentially, such as by multithreading, interrupt processing, or multiple processors.

[0184] In some examples, computer-readable storage media include non-transitory media. In some examples, the term "non-transitory" indicates that the storage medium is not embodied in a carrier wave or propagating signal. In some examples, non-transitory storage media stores data that can change over time (e.g., in RAM or cache).

Claims

1. A system for monitoring the health status of electrical equipment products, include: one or more sensors coupled to the article of electrical equipment, the one or more sensors configured to generate sensor data indicative of one or more conditions of the article of electrical equipment; and at least one processor; as well as a storage device comprising instructions that, when executed by the at least one processor, cause the at least one processor to: receiving the sensor data; determining a health state of the article of electrical equipment based at least in part on the sensor data; as well as In response to determining the health state of the electrical equipment article, performing operations, wherein execution of the instructions causes the at least one processor to determine the health state of the electrical equipment article by at least causing the at least one processor to predict whether the electrical equipment article will fail within a predetermined amount of time, and wherein execution of the instructions causes the at least one processor to perform the operations in response to predicting that the electrical equipment article will fail within the predetermined amount of time, wherein the electrical equipment article includes at least one of a cable terminal configured to couple a cable to another object and a cable connector configured to couple a first cable to a second cable, wherein the electrical equipment article comprises a communication unit configured to output the sensor data, and Wherein, the communication unit is configured to output the sensor data via the cable, the first cable, or the second cable using power line communication.

2. The system of claim 1 , wherein execution of the instructions causes the at least one processor to perform the operations by at least one of: causing the at least one processor to output a notification indicative of the health status of the article of electrical equipment, causing the at least one processor to output data representing a user interface for display, the user interface indicating the health status of the article of electrical equipment, causing the at least one processor to output commands to adjust components of an electrical network including the article of electrical equipment, and The at least one processor is caused to schedule maintenance or replacement of the article of electrical equipment.

3. The system of claim 1, wherein execution of the instructions further causes the at least one processor to determine the health state of the electrical equipment article by at least causing the at least one processor to: A model is applied to at least the sensor data generated by the one or more sensors of the article of electrical equipment to determine an operational health of the article of electrical equipment.

4. The system of claim 3, wherein the model is based at least in part on historical data of known failure events from a plurality of electrical equipment articles having one or more characteristics corresponding to one or more characteristics of the electrical equipment articles.

5. The system of claim 4, wherein the one or more characteristics of the electrical equipment article include one or more of the following: The location of the electrical equipment product, The manufacturer of the electrical equipment product, The installer of the electrical equipment product, or The type of the electrical equipment article.

6. The system of claim 3, wherein the sensor data includes data indicative of a temperature of the article of electrical equipment and a current in the article of electrical equipment, and wherein execution of the instructions causes the at least one processor to: applying the model to the data indicative of the temperature of the article of electrical equipment and the current in the article of electrical equipment to predict whether the article of electrical equipment will fail within the predetermined amount of time, The model is trained at least in part based on sensor data of each corresponding electrical equipment product among a plurality of electrical equipment products, the sensor data of each electrical equipment product including data indicating the temperature of the corresponding electrical equipment product and the amount of current in the corresponding electrical equipment product, wherein execution of the instructions causes the at least one processor to predict whether the electrical equipment product will fail by causing the at least one processor to identify abnormal behavior of the electrical equipment product.

7. The system of claim 3, wherein execution of the instructions causes the at least one processor to update the model based on the sensor data from the article of electrical equipment.

8. The system of claim 1, wherein the one or more sensors include one or more of: Temperature sensor, Current sensor, Voltage sensor, or Partial discharge sensor.

9. The system according to claim 1 further includes a communication unit independent of the electrical equipment product, the communication unit is configured to receive sensor data from a plurality of electrical equipment products including the electrical equipment product, wherein the communication unit includes the storage device and the at least one processor.

10. A method for monitoring the health status of an electrical equipment product, include: receiving, by at least one processor of the computing system, sensor data from at least one sensor indicative of one or more conditions of the article of electrical equipment; determining, by the at least one processor, a health status of the article of electrical equipment based at least in part on the sensor data; as well as performing, by the at least one processor, at least one operation based on the health state of the electrical equipment article, wherein determining the health state of the electrical equipment article comprises predicting, by the at least one processor, whether the electrical equipment article will fail within a predetermined amount of time, and wherein performing the operation comprises performing the operation in response to predicting that the article of electrical equipment will fail within the predetermined amount of time, wherein the electrical equipment article comprises at least one of a cable terminal configured to couple a cable to another object and a cable connector configured to couple a first cable to a second cable, The electrical equipment product includes a communication unit, the communication unit outputs the sensor data, and The communication unit outputs the sensor data via the cable, the first cable, or the second cable using power line communication.

11. The method of claim 10, wherein performing the operation comprises outputting, by the at least one processor, a notification indicative of the health status of the electrical equipment article.

12. The method of claim 10, wherein performing the operation comprises at least one of: At least one of the following is outputted by the at least one processor: data representing a user interface indicating the health status of the electrical equipment product for display, Commands for adjusting components of an electrical network including the article of electrical equipment, and scheduling, by the at least one processor, maintenance or replacement of the article of electrical equipment.

13. The method of claim 10, wherein determining the health status of the electrical equipment article include: Applying, by the at least one processor, a model to at least the sensor data generated by the one or more sensors of the article of electrical equipment to determine the health state of the article of electrical equipment, wherein the model is based at least in part on historical data of known failure events from a plurality of cable accessories having one or more characteristics corresponding to one or more characteristics of the article of electrical equipment, and wherein the one or more characteristics of the article of electrical equipment include one or more of the following: The location of the electrical equipment product, The manufacturer of the electrical equipment product, The installer of the electrical equipment product, or The type of the electrical equipment article.

14. The method according to claim 13, wherein the sensor data includes data indicative of a temperature of the article of electrical equipment and a current in the article of electrical equipment, wherein applying the model comprises applying the model to the data indicative of the temperature of the article of electrical equipment and the current in the article of electrical equipment to predict whether the article of electrical equipment will fail within the predetermined amount of time, and The model is trained based at least in part on sensor data for each respective article of electrical equipment of a plurality of cable accessories, the sensor data for each article of electrical equipment including data indicative of a temperature of the respective article of electrical equipment and an amount of current in the respective article of electrical equipment.

15. The method of claim 14, wherein predicting whether the electrical equipment article will fail comprises identifying, by the at least one processor, abnormal behavior of the electrical equipment article.

16. The method of claim 10, wherein the computing system comprises a first processor and a second processor, the first processor being included in the electrical article of equipment and the second processor being included in a remote computing system physically distinct from the electrical article of equipment, wherein determining the health state of the electrical article of equipment comprises determining, by the first processor, the health state of the electrical article of equipment, and Wherein executing the at least one operation includes executing the at least one operation by the second processor.

17. A computing device, include: at least one processor; A memory comprising instructions which, when executed by the at least one processor, cause the at least one processor to perform the method according to any one of claims 10 to 16.