Intelligent network

FIELD: physics, computer engineering.

SUBSTANCE: invention relates to a system and method of collecting data at different portions of an industrial network and analysis of the collected data. The system infrastructure comprises a plurality of fixed sensors, at least one infrastructure analysis unit, an operational bus connected to the plurality of sensors and components of the industrial network, wherein the operational bus is configured to receive operational data and transmit the operational data to a central organisation, wherein the operational data contain real-time measurement results for at least one sensor or component of the industrial network; an event bus connected to the plurality of sensors and components of the industrial network, wherein the event bus is configured to receive event data and transmit event data of the central station, wherein the data bus is separated from the operational bus; the event data are different from the real-time measurement results, are output therefrom and contain at least one analytical determination, based on at least one real-time measurement result and a network core, wherein transmission of operational data is carried out through the operational bus, but not through the event bus, and transmission of event data is carried out through the event bus, but not through the operational bus.

EFFECT: improved control of an industrial system.

33 cl, 30 dwg, 4 tbl

 

The level of technology

1. The technical field to which the invention relates

The invention in General, relates to a system and method of management of the branch network and more specifically to a system and method of data collection in different parts of the industry network and the analysis of the collected data for purposes of management of the branch network.

2. Prior art

Different industries have their associated networks. Industry may include electricity, telecommunications, transportation (such as air transportation, rail transportation, road transportation, bus transportation, etc.), and exploration of energy resources (such as oil wells, gas wells, etc.).

One such branch is the branch of public use, which manages the grid. The grid may contain any or all of the following: electricity generation, electricity transmission and distribution of electricity. Electricity can be produced using a plant such as thermal power plant, nuclear power plant etc. In the interests of efficiency, the generated electricity is increased to very high voltage (such as 345 kV) and transmitted via the transmission lines. Transmission lines can transmit power over long distances, crossing borders of States and�and international borders until it reaches its wholesale customer, who may be the company that owns the local distribution network. Transmission lines can end on a transmission substation, which can reduce a very high voltage to the intermediate voltage (such as 138 kV). From transmission substation more than low voltage transmission lines (such as lines subbareddy) transmit intermediate voltage at the distribution substation. At the distribution substations, the intermediate voltage may again be lowered to "medium" voltage (such as from 4 to 23 kV). With distribution substations may extend one or more feeders. For example, distribution substation can go from four to ten feeders. The feeder is constructed by a 3-phase scheme that contains 4 wires (three wires for each of the 3 phases and one wire for neutral). The feeders may be installed above ground (on poles) or underground. The voltage on the feeders may occasionally be reduced by using distribution transformers that reduce the voltage from the "average" voltage to consumer voltages (such as 120 volts). Consumer voltage can then be used by the consumer.

The grid can control one or more energy companies administered�eat removal of damage maintenance and updates related to the grid. However, the control grid is often inefficient and costly. For example, the energy company that manages a local distribution network, can control the removal of damage that can happen in the feeders or in the schemes, schemes called branches, otvetvlenii from feeders. Managing local distribution network often relies on phone calls from consumers when there is a malfunction of, or is based on field work, analyzing the local distribution network.

Energy companies have tried to update the grid using digital technology, sometimes called "smart network". For example, more smart meters (sometimes called "smart counters") are a type of advanced meter that identifies consumption more accurately than the traditional counter. The smart meter may then transmit this information via some network back to the local public service for the purpose of monitoring and billing purposes (telemetry). Although this recent progress in the upgrading of energy systems benefits, more progress is needed. It was reported that in the United States alone, half of the generating capacity is not used, half powerful�opportunities in the networks of energy transfer over large distances is not used and two-thirds of its local distribution is not used. So clearly there is a need to improve the management of the grid.

Another such industry is the industry of transportation. The transportation industry is usually associated with control of movement of one or more types of means of transport such as plane, train, car, bus, etc. for Example, the railway sector includes Railways, trains, travel on Railways, the Central office and the network to manage the Railways/trains. The network may include sensors to sense various data elements Railways, the means by which you can contact the Central office, and means that you can control the Railways. Normally, network in the railway industry is primitive. Specifically, the network limits the type of sensors used, the means by which you can communicate with the Central management, and the ability to manage the Railways. So clearly there is a need to improve the management of Railways.

Disclosure of the invention

Provides intelligent network to improve the management of the branch system. The intelligent network may be established under requirements of the customer and be applied to one or more industries. Examples are the use in the public sector Paul�hardware and industry transport transport, as a network, the network railway transport network road transport network of bus transportation, etc.). Intelligent network can also be generated under the customer's requirements and applied to the network of long-distance communication and exploration of energy resources.

Intelligent network can contain one or more system endpoints. System endpoint can contain one or more endpoint sensors to monitor a variety of sectoral systems and create data for the specified state. System endpoint can contain a means of analytical analysis of endpoints to process the data system endpoints and to make any appropriate decisions based on data.

Smart grid can contain system infrastructure containing one or more sensor elements of the infrastructure to control the different States of the sectoral system of infrastructure and creation of data characterizing the state. The system infrastructure can include means of analytical analysis of the infrastructure to process the data and create any appropriate decisions based on data. The system infrastructure may also receive data from system endpoints to create the corresponding�following solution.

System endpoint and system infrastructure can create event data indicating the occurrence of the need for attention within the branch system. System endpoint and system infrastructure can also create operating and non-operating data relating to the industry's system. Intelligent network can contain one or more tires to provide event data and operating/non-operating data core network of the smart grid. The network core may contain system tools analytical analysis to analyze the received data and create solutions that can be localized or global within the branch system. The network core may also contain a means of accumulating data that is used to store received data and retrieve them for later review and analysis. The network core may also include system management tools used to control various aspects of system industry. System management tools can be put into effect when adopted different solutions, and may require manipulation of the system. Intelligent network can also contain a system of enterprise-level, connected to the network core.

Other systems, methods, prism�Ki and advantages will be or will become apparent to experts in the art after studying the following drawings and detailed description. It is implied that all those additional systems, methods, features and advantages contained in the present description, must fall within the limits of the invention, and be protected below by the claims.

Brief description of the drawings

Fig.1A-C is a block diagram of one example of the overall architecture of the power system.

Fig.2 is a block diagram of the core Intelligent Network Data Enterprise (INDE), shown in Fig.1.

Fig.3A-C is a block diagram of another example of the overall architecture of the grid.

Fig.4 is a block diagram of the INDE substation shown in Fig.1 and 3.

Fig.5A-B - a block diagram of the device INDE shown in Fig.1A-C and 3A-C.

Fig.6A-B - a block diagram of another example of the overall architecture of the grid.

Fig.7 is a block diagram of another example of the overall architecture of the grid.

Fig.8 is a block diagram containing the list of some examples of processes observability.

Fig.9A-B - a block diagram of the execution sequence of the processes of state management and network operations.

Fig.10 is a block diagram of the sequence of operations processes non-operating data.

Fig.11 is a block diagram of the sequence of operations processes event management.

Fig.12A-C is a flowchart of the sequence of operations processes in the signaling response to the request (DR).

Fig.13A-B - a block diagram of the sequence you�of olnine operations processes of gathering information during disruption.

Fig.14A-C is a flowchart of the sequence of operations of the processes of collecting information in case of failure.

Fig.15A-B - a block diagram of the sequence of operations management processes metadata.

Fig.16 is a block diagram of the sequence of operations processes the notification.

Fig.17 is a block diagram of the sequence of operations of the processes of data collection meters (AMI).

Fig.18A-D is an example of the relationships of an object that can be used to represent the data source connectivity.

Fig.19A-B - example of graphical representation of progress through the project development process.

Fig.20 is a block diagram of an example of the smart grid.

Fig.21A-C is a block diagram of one example of the overall architecture for architecture INDE.

Fig.22 is a block diagram of the INDE core shown in Fig.21.

Fig.23A-C is a block diagram of another example of the overall architecture INDE.

Fig.24A-C is a block diagram of example architecture INDE implemented in the railway network.

Fig.25 is a block diagram of an example of a train in the architecture INDE shown in Fig.24A-24C.

Fig.26A-C is a block diagram of example architecture INDE implemented in the network of electric railway.

Fig.27A-C is a block diagram of example architecture INDE implemented in the network in the trucking industry.

Fig.28A-C is a block diagram of example architecture INDE, d�implemented in the automotive network.

Fig.29 - example of a block diagram of the sequence of operations architecture INDE shown in Fig.20.

Fig.30 is a block diagram of an example multiple architectures INDE, used in conjunction with each other.

Detailed description of drawings and preferred in the present embodiments;

In a brief review of preferred options for implementation, described below, associated with the method and system of management of the branch network. The applicants submit further examples related to various industry networks, such as networks of public utilities and transportation (such as freight network, network railway transport network road transport network of bus transportation, etc.). However can be used and other industry networks, including long-distance communication network and network intelligence energy resources (such as a network of oil wells, a network of gas wells, etc.).

As discussed in more detail below, certain aspects associated with the network system public use, such as the grid itself (including hardware and software for transmission and/or distribution of electricity) or network transport. Additionally, some aspects related to possible functional�authorities Central network management system public use such as the Central management of the power grid and the Central management of the network transport. These functionalities can be grouped in two categories, operation and application. Management services allow the system to public use to monitor and manage the network infrastructure of the system of public use (such as applications, network, servers, sensors, etc.).

In one of the examples discussed below, the use may be associated with the measurement and management of the network system public use (such as a grid or network of transportation). Specifically, the service application provide functionality that may be important for the network system public use and may include: (1) data gathering; (2) the preservation and classification of data; and (3) the monitoring processes. As discussed in greater detail below, the use of these processes allows you to "watch" for the network of public use, to analyze data and retrieve information on the network system public use.

Fig.20 is a block diagram showing as an example the architecture of the Intelligent Network Data Enterprise (INDE) 2000, which can be used for sectoral systems in various industries. In one example Architek�ur INDE may contain the network core 2002. The network core 2002 may receive various types of information and/or data based on the specific industry in which it is used. Data and information for a particular industry can arise in a system endpoint, 2006, which may represent different points in the sectoral system. Each system endpoint 2006 can contain many sensors 2014 endpoint that can detect various States associated with the industry system. For example, sensors 2014 endpoint may be designed to specifically detect the flow of electricity in transmission lines in the grid or data arrival/departure on airlines. Each system endpoints 2006 may include one or more processors and storage devices, allowing you to perform analytical analysis on the ground. In one example of analytical analysis 2016 endpoint may detect a variety of events based on data received from sensors 2006 endpoint.

Architecture INDE 2000 may also include system infrastructure 2008, is able to maintain the system endpoint 2006 throughout the branch system. System infrastructure 2008 may contain sensors 2002 2022 infrastructure, distributed throughout the branch system to detect a condition associated with otraslevoj� system. In one example, the system infrastructure 2008 may contain Analytics 2020 infrastructure system infrastructure to analyze the data received from the sensors 2022 infrastructure.

The network core 2002 may accept information from the system end-points, 2006 and system infrastructure 2008. In one example architecture INDE 2000 may comprise a plurality of buses, such as operating/non-operating bus 2010 bus 2012 events. Operating/non-operating bus 2010 may be used to transfer operating and non-operating data. In one example, operational data may refer to data associated with various operations of specific sectoral system implementing the architecture INDE 2000. Non-operating data may refer to data in industry-related aspects directly related to specific sectoral system. The 2012 event bus can receive data associated with various events taking place in the sectoral system. Events may refer to any appearance of interest in the sectoral system. Thus, the events may contain undesirable or abnormal condition occurring in the sectoral system.

Architecture INDE 2000 can implement distributed intelligence in these various components of the architecture�URS, which can be used to process the data and determine the appropriate result. In one example, the analytical analysis 2006 endpoint may contain one or more processors, storage devices and communication modules to allow to perform processing based on data received by the sensors 2006 endpoint. For example, analytical analysis, 2016 at the endpoint can receive data from sensors 2014 endpoint associated with the event, and based on the data, may determine that a particular event occurs. Analytical analysis in 2016 endpoint may generate an appropriate response, depending on the event.

Analytical analysis 2020 infrastructure may likewise contain one or more processors, storage devices and communication modules to allow execution of processing based on data received by the sensors 2022 infrastructure. System infrastructure 2008 may communicate with the system endpoints of 2006, allowing the system infrastructure 2008 to use Analytics 2020 infrastructure for the evaluation and processing of events, as well as operating/non-operating data from the system endpoints, 2014 and sensors 2022 infrastructure.

Data can also be evaluated by the network core 2002, fitted with tyres in 2010 and 2012. In one� example, the network core 2002 may contain systematic analytical analysis 2024, containing analytical analysis 2026 sensors and analytical analysis 2028 events. Analytical tests 2026 and 2028 may include one or more processors and storage devices, allowing to analyze event data and operating/non-operating data. In one example, the analytical analysis 2024 sensors can assess the sensor data received from sensors 2014 endpoint and sensors 2022 infrastructure. In the case of events analytical analysis 2028 can be used for processing and evaluation of event data.

The network core 2002 may also include collecting 2030 data. Collecting 2030 data may contain various storage 2032 data used to store raw data and processed data, giving the ability to restore archived data as needed and to allow for future analytical analysis based on archival data.

The network core 2002 may also include system 2034 funds management. System tools 2034 management may be responsible for actions taken within the branch system. For example, system tools 2002 management can include means 2036 automatic controls that automatically control various aspects of the branch system, based on event data and/or operational/not�xploitation data. The network core 2002 may also contain custom tools 2038 control allows a person to manage the branch system, which may or may not be based on event data and/or operating/non-operating the data bus.

2004 system of the enterprise can include a variety of large-scale software packages for the industry. 2004 system of the enterprise can receive and transmit data to the network core 2002 for its distinctive attributes such as information technology (IT), or other aspects associated with the industry. In alternative examples, the tires 2010 and 2012 can be integrated into a single bus, or may contain additional tires. Alternative examples may also include system infrastructure 2008, having various subsystems.

Fig.29 shows an example of the working of the scheme architecture INDE 2000. In one example of a system endpoint (SE1) 2006 may detect the occurrence of event E1. Another system endpoint (SE2) 2006 may detect the occurrence of event E2. Each system endpoint may 2006 to inform the system infrastructure 2008 about the events E1 and E2 via the event data. System infrastructure 2008 may analyze the event data and create decision D1 that can be passed to a system endpoints SE1 and SE2,�will of system endpoints to implement a response action.

In another example, event E3 may be determined by the system end point SE1. These events reporting event E3 may be transmitted to the network core 2002 allows a network core 2002 to carry out a systematic analytical analysis 2024 and create a solution to D2 using system tools 2034 management. Decision D2 may be provided to the system end point SE1.

In another example, a system endpoint SE1 may determine the occurrence of event E4 and notify the core network 2002 event E4 via the event data. The network core 2002 may create a solution D3 and provide it to system endpoint SE1 for implementation, at the same time providing information about the decision of the D3 system 2004 of the company.

In another example, a system endpoint SE1 may determine the occurrence of the event E5. System endpoint SE1 can carry out analytical analysis of 2016 at the end point to determine in the future to implement a solution D4. Decision D4 may be provided to the system infrastructure 2008 and the network core 2002 for the purpose storage and notifications. The examples shown in Fig.29, are illustrative and through the INDE 2002 can be transferred to other events, operational data and non-operating data.

Description of the high level architecture INDE

General architecture

In the drawings, wherein similar �sulochna position refer to similar elements Fig.1A-C presents one example of the overall architecture for INDE. This architecture can serve as a reference model, which provides a successive collection, transportation, storage and data management public network (such as a smart network); it can also provide analytical analysis and management, analytical analysis, as well as the integration in the above processes and systems for public use. Therefore, it can be viewed as the architecture is applicable to the enterprise level. Certain elements, such as operational management and aspects directly to the public network, are discussed in more detail below.

The architecture shown in Fig.1A-C, may contain up to four data bus and integration: (1) high speed bus 146 sensor data (which in the example power system may include operating and non-operating data); (2) a dedicated bus 147 event processing (which can include event data); (3) bus 130 operational services (which in the example power system can serve to provide information used in additional operational Department); and (4) service bus for enterprise IT systems operations Department (shown in Fig.1A-C as bus 114 environment and�of tarirovanija for the enterprise to service service 115 IT companies). Separate data bus can be implemented in one or more ways. For example, two or more data buses, such as high speed bus 146 sensor data and bus 147 event handling may be different segments of a single data bus. Specifically, the tires may have a segmented structure or platform. As discussed in greater detail below, the hardware and/or software, such as one or more switches may be used to route data to different segments of the data bus.

As another example, two or more data bus can be a separate tire such as a separate physical bus from the point of view of hardware implementation, necessary for transportation of the data for individual tire. Specifically, each of the tire may include a cable network, separate from each other. Additionally, some or all of the individual tires may have the same type. For example, one or more tires may include a local area network (LAN) such as Ethernet®, a cable network in the form of unshielded twisted pair and Wi-Fi. As discussed in greater detail below, the hardware and the software and/or software, such as a router, may be used to route data on a single rail from a number of different physical buses.

In �the quality of one other example, two or more tires may be in different segments in a single bus structure, and one or more of the tires can be on a separate physical buses. Specifically, high-speed bus 146 sensor data and bus 147 event handling can be different segments of a single data bus, while the bus 114 environment integration of the enterprise may be located on a physically separate bus.

Although in Fig.1A IS shown WITH four tires, to transfer four types of data can be used more or fewer tires. For example, a single non-segmented bus can be used to transmit sensor data and processing data event (bringing the total number of tires to three), as discussed below. And the system can operate without service bus 130 and/or bus 114 environment of enterprise integration.

Wednesday IT can be compatible with SOA. Service-oriented architecture (SOA) is an architectural style of computer systems for creating and using business processes, designed as services, throughout their lifetime. SOA also defines and provides the IT infrastructure to allow different applications to exchange data and participate in business processes. At the same time, the use of SOA and service bus enterprise is optional.

In the example power system, naturtejo shows the different elements within the overall architecture, such as the following: (1) the Core 120 120 INDE; (2) Substation 180 INDE 180; and (3) the Device 188 INDE. This division of elements within the overall architecture serves for illustration purposes. Can be used and other division elements. Moreover, the division of the elements may vary in different industries. Architecture INDE can be used to support both distributed and centralized approaches to network intelligence, and to provide the framework for dealing with large-scale implementations.

Reference architecture INDE is one example of a technical architecture that can be implemented. For example, it may be an example of mitarchitecture used to provide a starting point for the development of a certain number of specific technical architectures, one for each industry-specific solutions (e.g., different solutions for different industries) or one for each application within the industry (for example, the first solution to the first public network and the second solution to the second public network), as discussed below. Thus, a particular solution for a particular industry or specific application within the industry (such as used in a particular grid) can contain one, several or all elements of the INDE reference architecture. Moreover, reference architect�the texture INDE can provide a standardized starting point for developing solutions. Discussed below is the methodology for determining the specific technical architecture for a particular industry or specific application within the industry (such as concrete grid).

The reference architecture may be INDE architecture, distributed enterprise. Its purpose may be to provide structure for continuous data management and analytical analysis, such as continuous management of network data and analytical analysis and integrating them into the systems and processes of public utilities. Since progressive networking technology (such as smart technology-networks) affects every aspect of business processes of public utilities, should be mindful not only of the influences on the level of networks (such as the energy system), operations and premises of the consumer, but also at the levels of the enterprise and the operations Department. Consequently, the INDE reference architecture may indeed creates a SOA reference level of the enterprise, for example, to support the SOA environment for the purpose of mates. Should not be construed as a requirement that the industry, such as electricity, have transformed its existing IT environment in an SOA, before they can be built and used promising network, such as a smart network. Service bus the enterprise a str�Xia useful mechanism to facilitate the integration of IT, but it is not required to implement the rest of the solution. The following discussion focuses on the various components of the elements of the smart grid INDE for solutions in the supply; however, one, several or all components INDE can be applicable in different industries such as communications, transportation, and exploration of energy resources.

Group component INDE

As discussed above, various components in the INDE reference architecture may include, for example: (1) the Core 120 INDE; (2) Substation 180 INDE; and (3) the Device 188 INDE. The following sections discuss these three groups of elements as examples INDE reference architecture and provide descriptions of each component of the group.

The core of INDE

Fig.2 shows the Core 120 INDE, which is part of the INDE reference architecture that can reside in the control center operations, as shown in Fig.1A-C. the Core 120 may contain INDE unified architecture data storage network data and schema integration for Analytics to work with these data. The data architecture may use the common information model (CIM) International electrotechnical Commission (International Commission Advisor, IEC) schematic of a high level. CIM IEC is a standard developed by the power sector, which was the official�exponentially adopted IEC to allow application software to exchange information about the configuration and status of the electrical network.

In addition, this architecture can use data middleware 134 of Association, to merge other types of public utilities (such as, for example, data meters, operational and archival data, log files and event files) and files connectivity and metadata in a unified data architecture that can have a single point of entry to access high level apps, including applications for the enterprise. Real-time systems can also access the storage key data through a high speed data bus and several data warehouse can receive data in real time. Different types of data can be transported within one or more tires in a smart network. As discussed below in the section on Substation 180 INDE, Substation data can be collected and stored locally at the Substation. Specifically, the database, which may be associated with the Substation and to be nearest to the Substation, can store the data of the Substation. Analytical analysis related to the level of the Substation may also be performed at the Substation computers and stored in the database of the Substation, and all or part of the data can be transported to the control center.

Types of transported data may include operational and nexp�atalonia data events, data connectivity, connection and location information of the network. Operational data may include, in particular, the status of the switches, the state of the feeders, the condition of the capacitors, the state of the sections, the condition of the gauges, the status of the FCI, the state of the linear sensors, voltage, current, active power, reactive power, etc. non-operating data can include, in particular, power quality, reliability of power supply system, the health state assets, data loads, etc. Operating and non-operating data can be transported using bus 146 operating/non-operating data. Application software for the collection of data during transmission and/or distribution of electricity of a power system may be responsible for sending some or all of the data on bus 146 operating/non-operating data. Thus, application programs that need this information, you may be able to receive data by subscribing to the information or invoking services that can make these data available.

Events can contain messages and/or alarms generated by the various devices and sensors that are part of smart grid, as discussed below. Events can be created directly device�you and the smart sensors network as well as created various application programs analytical analysis based on the data of the measurement results of these sensors and devices. Examples of events may include failure of the meter, the alarm meter, Converter failure, etc Network components, such as network devices (smart power sensors (such as sensor with integrated processor that can be programmed for digital processing), temperature sensors, etc.), components of the energy system that contains more built-in processing (RTU, etc.), network smart meter operability of the meter, the meter reading data, etc.), and mobile field force unit (the event of downtime the closing of the assignment, etc.) may generate event data, operating and non-operating data. The event data generated within a smart network that can be transmitted via bus 147 events.

Connectivity data connections, the network can determine the network location of the power system. Possible base location, which determines the physical location of the network component (substation, segments, feeders, transformers, switches, automatic reclosing, meters, gauges, pillars, public, etc.) and their interconnection to install. Based on with�the events within the network (component failures, service activities, etc.), the connectivity of the network may change on a continuous basis. As discussed in greater detail below, the structure of how data is stored, and the combination of data allows archive recovery plan network at various earlier times. Data connectivity can be extracted from geographic information system (Geographic Information System, GIS) on a periodic basis as changes in the electrical supply network and this information is updated in the GIS application.

Data on the location of the network may contain information about network component in the communication network. This information can be used to send messages and information to a specific component of the grid. The data on the network location can be entered manually into the database of the smart grid as they install new component of the smart grid or extracted from the asset management system, if this information is stored externally.

As discussed in more detail below, data can be sent from various components in the grid (such as Substation 180 INDE and/or Device 188 INDE). Data can be sent to the Core 120 INDE using wireless technologies, wired technologies, or combinations thereof. Data can be accepted by the networks 160 connection of the power supply system, which can send data to the device 190 m�cruciali. The device 190 routing may include software and/or hardware and software to control the routing of data on the bus segment (when the bus is segmented bus structure) or on a separate bus. The routing device can include one or more switches or router. The device 190 routing may include a network device, hardware and software which creates routes and/or routes data to one or more tires. For example, the device 190 routing can direct the operating and non-operating data on bus 146 operating/non-operating data. The router may also send event data to the bus 147 events.

The device 190 routing can determine how to send data based on one or more ways. For example, the device 190 routing may examine one or more headers in the transmitted data to determine whether to send data to the segment for bus 146 operating/non-operating data or to the bus 147 events. Specifically, one or more headers in the data can indicate whether the data operating/non-operating data (the data that the device then 190 routing sends to the bus 146 operating/non-operating d�abilities) or they are event data (which are then the device 190 routing sends to the bus 147 events). Alternatively, the device 190 routing can examine the payload data to determine the data type (for example, the device 190 routing can examine the format of the data to determine whether the data operating/non-operating data or event data).

One of the repositories, such as repository operational data 137 that stores operating data, can be implemented as a truly distributed database. Another from the vaults, archive (identified as archived data 136 of Fig.1 and 2) may be implemented as a distributed database. Other "ends" of these two databases can be located in the group Substation 180 INDE (discussed below). Additionally, events can be directly stored in any of multiple repositories of data via the bus, complex event processing. Specifically, the events may be stored in the journal 135 event registration, which can be a repository for all events that are published on the bus 147 events. The event log can store one or more or all of the following: event ID; event type; event source; the priority of the event; and the creation time of the event. Bus 147 events should not store the events for a long period of time, providing persistence for all events.

Storing the data� can be so that data could be close to the source as possible or real. In one possible implementation, for example, that the data stored in substation substation 180 INDE. But these data can also be requested at the level 116 of the operation control centre to create different types of solutions that consider the grid at a significantly fragmented. In combination with the distributed intelligence approach, an approach with distributed data can be adopted to facilitate the accessibility of data at all levels of decision-making through the use of links databases and data services, depending on the circumstances. Thus, the solution for storage of archival data (which may be available at the level 116 of the operation control centre) can be similar to the solution for the storage of operational data. Data can be stored locally at the substation and connection database configured on the repository instance in the control center, provide access to data at the individual substations. Analytical analysis of the substation can be performed locally at the substation, using the local datastore. Archive/collective analytical analysis can be performed at the level of the center 116 of the control operations by accessing data on the local copies of the substation, IP�alsoa database relationships. Alternatively, data can be stored centrally in the Core 120 INDE. However, given the amount of data that may be necessary to transfer from Devices 188 INDE, data storage Devices 188 INDE may be preferable. Specifically, if there are thousands or tens of thousands of substations that may appear in the power system), the amount of data that must be passed to the Kernel 120 INDE, can create a bottleneck for communication.

Finally, the core 120 INDE can program or control one or several or all substations 180 or INDE device 188 INDE in the grid (discussed below). For example, the core 120 INDE can modify the programming (such as downloading an updated program) or provide a management team to manage every aspect of the Substation 180 or INDE Device 188 INDE (such as the management of the sensors or analytical analysis). Other elements, not shown in Fig.2, can contain different elements of integration, to support this logical architecture.

Table 1 describes some of the elements of the kernel 120 INDE shown in Fig.2.

td align="left"> Bus 146 operating/non-operating data
Table 1
The core elements INDE
The core element of INDEDescription
Services SER 144Provides high speed processing of the event stream with low latency, event filtering and event correlation multi-flow atomizer.
Centralized application program 139 intelligence networksCan consist of any number of commercial or custom application programs analytical analysis, which are not used in real-time, working primarily from data stores in the kernel.
Services 140 visualization/notificationSupport data visualization, and flow of events and automatic notifications based switching of events.
141 management applicationsServices (such as services 142 support application programs and distributed support 143 computing), support the launching and running applications, web services and support distributed computing and automated remote program load (e.g. OSGi).
Services 145 network managementAutomated monitoring of networks, applications and databases; control system health, root cause analysis OTK�call (brick and mortar).
The service metadata 126 gridServices (such as services 127 communication, translation 128 names and service 129 TEDS) for storing, retrieving and updating metadata of the system, including the connectivity of the power grid and communication networks/sensors, point lists, calibration of sensors, protocols, installation point devices, etc.
Services 123 intelligence/data gridServices (such as services sensor data 124 and 125 rooms management analytical analysis) to maintain access to the data grid and analytic network analysis; management of analytical analysis.
System 121 data management measurersFunctions of the data management system of gauges (e.g., Lodestar).
The services of these gauges AMOSCm. the discussion below.
Bus 147 complex event processing in real timeThe message bus allocated to the processing flow of events - the appointment of a dedicated bus is to provide a wide bandwidth and extremely low latency streams of event messages with high ripple. The event message may be in the form of XML messages. Possible �other
the message types. Events can be separated from the operating/non-operating data and may be transmitted over a separate or dedicated bus. Events usually have a higher priority, since they usually require some immediate action from the point of view of operation of the system (messages from faulty meters, transformers, etc.). Bus event processing (and related events processing service for event correlation, shown in Fig.1) can filter event streams, giving them an interpretation which can better perceive other devices.
In addition, the tire event handling can get a set of event streams, detect various patterns that occur among the multiple flows of events, and to provide interpretation of the numerous streams of events. Thus, the bus event processing can not just analyze event data from a single device, but instead to consider multiple devices (including many classes of devices that, at first glance, may not be connected) to detect correlation. Analysis of single or multiple event streams can be based on rules.
Operational data may include data reflecting the current state of the grid that can be used in the management of the grid (e.g., currents, voltages, active power, reactive power, etc.). Non-operating data can include data that reflects the condition or state of the device. Operating data previously transmitted directly to a specific device (creating, thus, a potential problem of "drive", when data are not available to other devices or other applications).
For example, operational data previously transmitted to the SCADA system (Supervisory control and data) to guide the grid (control grid). However, using the structure of the tire, such data can also be used for load-balancing, use/optimize assets, planning systems, etc., as discussed, for example, Fig.10-19. Non-operating data previously received, sending the man into the field to collect operational data (instead of automatically send non-operating data in a Central repository). Typically, operational unexploitative data is created in various devices in the grid at set times. This is different from the event data, which are typically created packages, as discussed below.

The message bus can be allocated to the processing of flows operating and non-operating data from substations and grid devices. The purpose of a dedicated bus may be providing constant low latency through the organization of coordination of data flows; as discussed elsewhere, a single bus may be used to convey both operating and non-operating data and event handling in some circumstances (effectively combining bus operating/non-operating data bus event processing).
Bus 130 maintenance operationsThe message bus that supports the integration of typical application programs operations of EMS (energy management system), DMS (distribution management), OMS (management system downtime), GIS (geographic information system), Manager) with more new features of smart networks and systems (DRMS management system (response to demand), external Analytics, CEP, visualization). The various buses, including bus 146 exploitation�x/non-operating data bus 147 event data and bus 130 maintenance operations can get unprotected from the weather, the food, etc. through the structure 117 protection. Bus 130 maintenance operations can serve as a provider of information about smart network for application programs of the operations Department's public areas, as shown in Fig.1. Application program analytical analysis can convert the raw data from sensors and devices in the grid, with actionable information that will be available to application programs of the power system to perform actions for managing the power grid. Although most interactions between the application programs of the operations Department and the Core 120 INDE is expected to occur via this bus, the application program of the power system will have access to the other two tires and also use the data from these tires (for example, the reading of the meter from bus 146 operating/non-operating data, events idle bus 147 idle events).
Store data 132 CIMData warehouse top-level organization of the data grid; uses the schema of the data IEC CIM; provides the primary access point to the data grid from operating systems and systems before�the sector. Intermediate teaming software allows you to communicate with different databases.
Storage 131 connectivityStorage 131 connectivity may contain information about the electrical connectivity of the grid component. This information can be derived from Geographic information system (GIS) software tools, which stores the geographical position at the time of construction component, forming a grid. Storage data 131 connectivity can describe hierarchical information about all
components of the grid (substation, feeder, section, segment, branch, t-section, switch, automatic reclosing, switch, etc. - mainly all of the assets). Storage 131 connectivity may have information about the assets and connectivity at the time of construction. Thus, the storage 131 connectivity may contain assets database that contains all the devices and sensors associated with the components of the grid.
Storage 133 data metersStorage 133 of these gauges can provide quick access to data, use of measuring instruments for analytical analysis. This repository can� to store all the information about the meter, received from the meters in the premises of the customer. The data collected from the meters that can be stored in the storage 133 of measures and data to be provided to other applications of public use for billing (or other operations of the operations Department) and also for other analysis.
Magazines 135 event registrationMeeting registration files relating to the work of the various systems of public use. Magazines 135 event registration can be used for analysis after the event and to retrieve data.
Archival data 136Telemetry data are archived in the form of standard data archive. Archival data 136 may store a temporal sequence non-operating data, as well as archival performance data. Analytical analysis related to items such as power quality, reliability, serviceability of the assets, etc., can be performed using the data contained in the archived data 136. Additionally, as discussed below, the historical data 136 may be used to obtain the topology of the grid at any time, using archived operational data in this repository in combination with the topology of the grid on �the date you place buildings, stored in the data store connectivity. Additionally, data can be saved as a simple record, as discussed below.
Operational data 137Operational data 137 may include operational database the grid in real time. Operational data 137 can be built in a truly distributed form with elements in substations (indicating linkages to operational data 137), and also at the center of operations. Specifically, operational data 137 may store the measurement results data received from the sensors and devices that are related to the components of the grid. Archive the results of the measurement data is not stored in the data store, instead they are stored in archival data 136. Database tables in the operational data 137 may be updated with the most recent results of the measurements obtained from these sensors and devices.
Files 138 DFR/SERThe digital files of the Registrar of the failure and the Registrar of consecutive events; used for event analysis and data analysis; files are usually created on the substation auxiliary systems and equipment.

As discussed in table 1, the tire 146 real-time data (which predetermination and non-operating data) and bus 147 complex event processing in real time (which transmits the data event processing) are combined into a single bus 346. An example of this is shown in the flowchart 300 of Fig.3A-C.

As shown in Fig.1A-C, bus for work purposes are separate. To handle low latency CEP may be important for specific applications, which are subjected to very large batches of messages. Most data streams to the grid, on the other hand, are more or less constant, with the exception of files of digital recorders bounce, but they can usually recover on a managed basis, whereas packages events are asynchronous and random.

Fig.1 further shows additional elements in the center 116 of operations management, separate from the Core 120 INDE. Specifically, Fig.1 further shows a system 153 input for data collection measuring instruments (Meter Data Collection Head End(s)) responsible for communication with the measuring devices to collect data from the meters and providing the collected data ancillary to the program). System 154 management response to the demand (Demand Response Management System) is a system performing communication with equipment in one or more compartments, which can be controlled by an auxiliary program. System 155 management downtime (Outage Management System) is a system enabling the auxiliary program in the management of the downtime, watching swapped idle, driving of which are accepted by the decision�Oia, and the way they are implemented. System 156 energy management (Energy Management System) is a system-level management of the transmission system that controls the devices in substations (for example) to the transmission grid. Management system distribution 157 (Distribution Management System) is a management system at the distribution level, which controls the devices in substations and feeders (for example) for grid distribution. Services 158 IP networks (IP Network Services) are the set of services running on one or more servers that support the IP communication-type (such as DHCP and FTP). System 159 sending mobile data Dispatch Mobile Data System) is a system that sends/receives messages at the mobile data terminals in the field. Circuit &Load Flow Analysis, Planning, Lightning Grid Analysis and Simulation Tools 152 is a set of tools used by an auxiliary program in the design, analysis and planning of power systems. IVR (integrated voice response) and Call Management (call management) 151 are systems for handling user calls (automated or by operators). Incoming phone calls regarding stops can automatically or manually be entered and transmitted to the system Outage Management System 155 management downtime. The system 150 Work Management System is a system, rear�stimulating and administering outfits to work. Geographic information system Geographic Information System 149 is a database that contains information about where assets are located geographically and how the assets are connected together. If the environment has focused on services architecture Services Oriented Architecture (SOA), SOA Operations Support 148 (support operations SOA) is a set of services to support SOA environment.

One or more systems in the center 116 of the control operations, which are outside the Kernel 120 INDE, are systems derived products that may be of utility. Examples of such systems products are inherited system 148 operations support system 149 geographic information system 150 management of the organization works, the system 151 demand management, a set of 152 tools for design, analysis, planning and modeling of networks, the system 153 input for data collection of meters, the system 154 management response to the demand, the system 155 downtime management, system 156 energy management system 155 downtime management, IP services 158 and the system 159 sending mobile data. However, these systems are inherited products are unable to handle or manipulate data, which are taken from the smart network. The core 120 INDE may be able to receive data from the smart network, processing data, smart grid and to transmit processed data� one or more systems inherited by products in the form you can use system derived products (such as private details of the formatting inherent in the product system of inheritance). Thus, the Core 120 INDE can be considered as middleware.

Center 116 operations management, containing the Core 120 INDE, can realize the communication unit 115 of the information technology enterprise. Generally speaking, the functionality of the unit 115 information technology enterprises hold the operations of the operations Department. Specifically, unit 115 information technology enterprises can use the bus 114 environment of enterprise integration to send data to different systems within the organizational unit 115 information technology enterprises, including in the storage 104 of the business data, the system 105 applications for gathering business data, the system 106 enterprise resource planning, financial systems 107, the system 108 information consumers 108, the system 109 human resources system 110 asset management system 111 support SOA in the enterprise system 112 network management and service 113 messaging company. System 115 information technology enterprises may further contain a portal 103 for communication with the Internet 101 through the firewall 102.

Substation INDE

Fig.4 pre�manifests itself in the example of the architecture of the high level group 180 INDE Substation. This group may contain elements that are actually on the main substation 170 in the control room of the substation on one or more servers located in conjunction with electronics substations and systems.

The following table 2 lists and describes certain elements of the group 180 INDE Substation. Service 171 data security can be part of a substation environment; alternatively, they can be integrated in a group of 180 INDE Substation.

Table 2
Elements of a Substation INDE
Elements of a Substation INDEDescription
Repository 181 non-operating dataPerformance and health data; it is a distributed archival data component.
Store operational data 182State data of the power grid in real time; it's part of a true distributed database.
The stack 187 interface/connectivityCommunications support, including TCP/IP, SNMP, DHCP, SFTP, IGMP, ICMP, DNP3, IEC 61850, etc.
System 186 support raspredelenie�x/remote computing Support for remote distribution of programs, the relationships between processes, etc. (e.g., DCE, JINI, OSGi).
System 185 signal processingSupport for digital signal processing in real time; data normalization; convert engineering units.
System 184 processing on detection/classificationSupport the processing of event streams in real-time detectors and classifiers events/signals (ESP, ANN, SVM, etc.).
Means 183 analytical analysis substationSupport for programmable applications of analytic real-time analysis; the master scan DNP3; Means of analytical analysis of the substation may allow the analysis of operating and non-operating real-time data to determine whether there had been an "event". The definition of "event" can be based on the rules that determine whether one of the possible events based on the data. The analytical tool of the analysis of the substation.
can also to take into account the automatic change of operation of the substation based on detected�Genesis. Thus, the grid (including the different parts of the grid) can be "self-healing". This aspect of "self-healing" eliminates the requirement that the data was transferred to the Central organization, so data were analyzed in the Central organization and the Central organization to the grid command was sent before the problem in the grid is fixed. In addition to the definition of "event" means an analytical analysis of the substation may also issue a work order for transmission to the Central organization. A work order can be used, for example, to schedule a repair device, such as a substation.
LAN 172 substationLocal area network inside the station to various parts of the substation, such as relay 173 microprocessor, instrumentation 174 substations, registrars 175 of file events and remote terminal RTU 176 station.
Service 171 securityThe station can implement external communications with various networks of public use through the level of the security services.

As discussed above, the various elements within the smart network may contain additional functionality, including up to�additional processing capabilities/analytical analysis and database resources. The use of these additional features within the various elements in the smart network allows you to have a distributed architecture with centralized management and application management and network performance. For functional reasons, but also for reasons of performance and expandability, the smart network containing thousands and tens of thousands of Substations 180 INDE and from tens of thousands to millions of devices grid can include distributed processing, data management and communication between processes.

Substation 180 INDE may contain one or more processors and one or more storage devices (such as storage 181 non-operating substation data and store operational data 182 substation). Repository 181 non-operating data and store operational data 182 may be associated with substation and is situated near the substation, as those located at the Substation 180 INDE. Substation 180 INDE may further contain components smart network responsible for the observability smart grid at the substation level. Components of the Substation 180 INDE can provide three primary functions: the collection of operational data and storing them in the distributed storage of field data collection non-operating data and storing them in the archive; and the locale�th processing of the results of the analytical analysis based on real-time (such as seconds). Processing may include digital signal processing of voltage and current, the process of detection and classification, including the processing of the event stream; and communication of results of processing with on-premises systems and devices and also systems in the center 116 of the management of operations. The connection between the Substation 180 INDE and other devices in the network may be wired, wireless or combination of wired and wireless communications. For example, data transmission from the Substation 180 INDE to the center 116 of operations management can be wired. Substation 180 INDE can transfer data, such as operating/non-operating data or event data, the center 116 of operations management. The device 190 routing can direct the transmitted data on bus 146 operating/non-operating data or on the bus 147 events.

Here may also be run optimization response to the demand for managing distributed losses. This architecture corresponds to the previously described principle of the architecture of distributed applications.

For example, connectivity data may be duplicated at the substation 170 and center 116 operations management, allowing, thus, substation 170 to operate independently, even if the data network 116 to the center management operations is not functioning. Using this information (connectivity, stored locally, analytical analysis at the substation can be performed locally, even if the line connection with the operation control centre is not operational.

Similarly, the operational data may be duplicated in the center 116 of operations management and 170 substations. Data from sensors and devices associated with a particular substation may be assembled and the most recent measurement result can be saved in the data store at the substation. The data structure for the storage of operational data may be the same and hence the connection of the database can be used to provide direct access to your data, ever-present at the substations, through the request store operating data in the control center. This gives many advantages, including facilitating data replication and resolution analytical data analysis substation switching, which is more susceptible to time to be made locally and without confidence in the availability of communication outside the substation. Analytical data analysis center 116 operations management may be less time-sensitive (because the center 116 of operations management can usually examine the historical data to reveal the models that are more predictive, not reactive), and may be able to work with Seth�trolled problems if they do occur.

Finally, archival data can be stored locally at the substation and a copy of the data can be stored in the control center. Or database connection can be configured on request to the storage center 116 operations management, providing the operation control centre access to data at the individual substations. Analytical analysis at the substation can be performed locally at the substation 170, using the local datastore. Specifically, the use of additional opportunities for obtaining and storing data at the substation allows the substation to review and adjust themselves independently, without input from the Central organization. Alternative, archival/collective analytical analysis can also be performed at the level of the center 116 of the control operations by accessing data on the local substation, using database links.

The device INDE

Group Device 188 INDE may contain a large variety of devices within the smart network, including various sensors within the smart network, such as various devices 189 distribution grid (e.g., line sensors on the power rails), 163 meters in the premises of the customer, etc. the Group Device 188 may contain INDE device added to the grid, with specific functional�bubbled access (this, as a smart remote terminal units (RTU), containing specialized programming) or may contain existing inside the grid device with added functionality (such as a RTU device mounted on the top of a pole, in an existing open architecture that is already present in the grid and which can be programmed to create a smart linear sensor or device smart network). The device 188 INDE may further comprise one or more processors and one or more storage devices.

Existing devices the grid may not be open from the point of view of the software, and in most cases, may be unable to use modern network or service software. Existing devices the grid can be designed to receive and store data for accidental discharge on some other device such as a laptop computer, or to transfer a batch of files via PSTN line to a distant host computer upon request. These devices may not be designed to work in the digital network environment in real time. In these cases, the device data grid can be obtained at the substation level 170 or at the center 116 of the management of operations, depending on how developed existing�I network connection. In the case of networks of gauges will be normal practice for which the data are obtained from the data collection engine gauges, as the network of gauges are usually closed and the meter cannot be addressed directly. As these networks of gauges and other devices for the grid can be individually addressed so that data can be transported directly to where they are needed, and this will not necessarily be the center 116 of the control operations, and can be anywhere in the grid.

Devices such as indicators of defective circuits may be combined with wireless network interfaces for communicating over wireless networks at a moderate speed (100 Kbps). These devices can report status by making exceptions to established pre-programmed functions. Intelligence many devices the grid can be increased when using a local smart RTU. Instead of RTU have installed on the mast support, which are designed to work as devices with a fixed function and have a closed architecture, RTU can be used as devices open architecture that can be programmed by third parties and to serve as a Device 188 in INDE INDE reference architecture. In addition, the meters in the premises of the consumer� can be used as sensors. For example, meters can measure the consumption (i.e., how much energy is consumed for billing purposes) and can measure the voltage (to be used in optimization/VA reactive power).

Fig.5A-C shows an example architecture of a Device group 188 INDE. Table 3 describes some of the elements of the Device 188 INDE. The smart device network may include an embedded processor, so it is unlikely that the processing elements are SOA services, rather they are library programs for programs running in real time, as the group of Devices is implemented on a dedicated DSP, real-time, or on the microprocessor.

Table 3
The elements of the Device INDE
The elements of the Device INDEDescription
Circular buffers 502Local circular buffer storage device for digital signals sampling analog converters (for example, voltage and current) that can be used to store data for signals in different time periods, so that, if the event is detected, the data signal, leading to event,�e could be saved.
Buffers 504 device stateBuffer data storage state of the external device and the transition state.
Device 506 monitoring frequency three-phaseThe calculation of current estimates of the incidence of energy on all three phases; use to adjust the frequency in other data, and as a measure of the stability dimension of the grid and power quality (especially DG).
Block 508 Fourier transformTransformation of signals in time domain into frequency domain to allow analytical analysis in the frequency domain.
Analytical analysis 510 of the signal in the time domainSignal processing in the time interval; extracting measures of the behavior of the transition process and behavior of the envelope.
Analytical 512 signal analysis in the frequency domainSignal processing in the frequency domain; extracting RMS (RMS) and power settings.
Secondary analytical analysis signal 514Calculation and payment.�resonant amplitudes; calculation of selected measures of measurement error/fault.
Tertiary analytical analysis signal 516The simultaneous calculation of complex amplitudes based on GPS synchronization and a reference angle of the system.
Analysis of events and launches 518Processing of all analytical tests for the detection of events and start receiving the file. Various types of Devices INDE may contain different possibilities for the analytical analysis of events. For example, a linear sensor can explore ITIC events, exploring the emissions in the form of a signal. If the emission occurs (or occurs a series of emissions), the linear sensor with the analytical analysis of the event may decide that "event" has occurred, and may also provide a recommendation as to the cause of the event. The ability of the analytical analysis of the events can be based on rules, and different rules are used for different Devices INDE and different applications.
File storage - receipt/formatting/transmission 520Receiving data from the ring buffers, based on the starts of the event.
Service 522 stream of signalsSupport thread� transmit signals to a remote client display.
The communication stackSupports network connections and remote software loading.
Sync 524GPSProvides synchronization of high-resolution applications that require coordinates, and synchronizes the collection of data across a wide geographic area. Created data may contain the mark of 526 time frame of the GPS data.
Analytical analysis 528 StatesReceiving data for status messages.

Fig.1A shows the room 179 of the consumer, which may contain one or more smart meters 163, one built-in display 165, one or more sensors 166 and one or more funds 167 management. In practice, the sensors 166 can record data in one or more devices in the premises 179 consumer. For example, the sensor 166 can record data in a variety of major facilities in room 179 of the consumer, such as a furnace, boiler, air conditioning, etc., Data from one or more sensors 166 may be sent to a smart meter 163, which may package the data for transmission to the center 116 of the management operations through a network communication system 160 160 power supply. Built-in display 165 may provide the user in �ameenah user output device, to view real-time data collected from the smart meter 163 and one or more sensors 166. In addition, an input device (such as keyboard) can be connected with built-in display 165, so that the client can communicate with the center 116 of operations management. In one embodiment, the implementation of the integrated display 165 may include a computer, present in the premises of the customer.

Space 165 the consumer may further comprise a means 167 management, which can manage one or more devices in the premises 179 consumer. Through the center 116 of the control operations can be controlled by various devices, such as heater, air conditioning, etc., depending on the command.

As shown in Fig.1A, premises 169 user can communicate in various ways, such as via the Internet 168, the public switched telephone network (PSTN) 169 or via a dedicated line (such as through a manifold 164). Through any of these channels of communication data can be sent from one or more premises 179 user. As shown in Fig.1, one or more premises 179 user can contain a network of 178 smart meter contains a selection of smart meters 163), which forwards the data collector 164 for transmission to the center 116 of the management operaciones network 160 management. Additionally, various distributed sources of production/ storage 162 (such as solar panels, etc.) can send data to the tool 161 control using the monitor for communication with the center 116 of the management operations through a network of 160 management system for public use.

As discussed above, the devices in the grid beyond the center 116 of the control operations may include processing and/or storage. The device may contain a Substation 180 and INDE Device 188 INDE. In addition to individual devices on the grid, with additional intelligence, individual devices can communicate with other devices in the network to exchange information (including data sensors and/or analytical data (such as event data) to examine the state of the grid (such as the determination of damages) and to change the state of the grid (for example, to repair the damage). Specifically, individual devices can use the following: (1) intelligence (such as processing capabilities); (2) storage (such as distributed storage, discussed above); and (3) communication (such as using one or more of the tires, as discussed above). Thus, the individual devices in the grid can communicate with�to Radicati with each other without supervision from the center 116 of the management of operations.

For example, architecture INDE, disclosed above, may include a device that reads at least one parameter in the chain feeder. The device may further comprise a processor that controls the read option in the chain feeder, and it analyzes the read parameter to determine the condition of the chain feeder. For example, analysis of the read parameter may include comparing the read parameter with a specified threshold and/or may contain trend analysis. This reading may include reading the waveform and such analysis may include determining whether the received signals at the damage in the chain feeder. The apparatus may further communicate with one or more substations. For example, a particular substation may be supplying power to a specific circuit feeder. The device can read the status of a specific circuit diagram of the feeder and to determine whether damage to a particular feeder. The device can communicate with the substation. The station can analyze the damage, a certain device, and take measures on liquidation of consequences depending on the damage (such as reducing the power supplied to the feeder). In the example of a device that sends data indicating damage (based on analysis of the waveform), the substation can modify electro�ITALIE, supplied to the feeder, without signal from the center 116 of operations management. Or, the station can combine data indicating damage, with information from other sensors to further Refine the analysis of the damage. The substation may additionally contact the center 116 of operations management, using such application software as intellectual program to stop (such as shown in Fig.13A-B) and/or intellectual program for damage (such as shown in Fig.14A-C). Thus, the center 116 of operations management can determine the damage and to determine the extent of downtime (such as the number of houses affected by the damage). Thus, a device that reads the state of the chain feeder, can be used in conjunction with the substation to eliminate potential damage, requiring or not requiring intervention center 116 operations management.

In another example, a linear transducer containing additional processing capabilities with the use of intelligence and/or memory, can create a state data grid to the plot grid (such as a feeder). State data grid can be used together with the system 155 management response to the demand in the center 116 of operations management. System 155 management response to the demand may control one or �more devices in the locations of consumers, located the chains of feeders, in response to state data from the grid of the linear sensor. In particular, the system 155 management response to the demand to submit the command to the system 156 power management and/or system 157 control the distribution, to reduce the load on the feeder, disabling devices in the locations of consumers who receive power from the feeder, in response to the signal of the linear sensor indicating a simple chain feeder. Thus, the linear sensor in conjunction with the system 155 management response to the demand can automatically take the load from the faulty feeder and then to localize the damage.

As another example, one or more relays in the power grid may have an associated microprocessor. These relays can communicate with other devices and/or databases that are constantly present in the grid to determine the damage and/or to manage the grid.

The concept and architecture INDS

The model with external data smart network/analytical services

One of the applications architecture of the smart grid allows electricity to subscribe to the services grid data management and Analytics, while maintaining the traditional management system and supporting its own operating system. In this model, the system of General�public use can set your own grid sensors and devices (as described above) and can either have their own communication system to transfer data and use it, or get external data. The data grid can leave the power supply system in the remote location of service placement information system remote Intelligent Network Data Services (INDS), where data can be managed, store and analyze. The power supply system may then subscribe to data and analytical services in accordance with the relevant financial service model. The power supply system can avoid the initial investment associated with the investment and ongoing management costs, support and update infrastructure data/Analytics, smart grid, in exchange for contributions. Reference architecture INDE, described above, is described here external structure.

Architecture INDS services for smart grid

To implement the model of services INDS, INDE reference architecture may be divided into a group of items that can be hosted remotely, and the group of items that may remain in the supply system. Fig.6A-C shows how you can look like the architecture of power supply system, when the Kernel 120 120 INDE made by the remote. The server may be part of the Core 120 INDE, which can act as an interface to remote systems. In systems of public use it may look like a virtual Core 602 INDE.

As shown in the overall block diagram 600 �a of Fig.6A-C, group Substation 180 and groups INDE Device 188 INDE not differ from that shown in Fig.1A-S. Multilinea structure may also continue to be used in the power supply system.

The core 120 INDE can be controlled remotely, as shown in the flowchart 700 of Fig.7. In the place of hosting the Kernel 120 INDE can be installed as needed to support subscribers of the system energy INDS (shown as the North American Center 702 hosting INDS). Each Core 120 may be a block system, so that adding a new subscriber was a routine activity. Side, separated from the system for public use that can manage and maintain the software of one, some or all of the Cores 120 INDE, as well as apps that are downloaded from the location hosting INDS, each Substation 180 and INDE Device 188 INDE power systems.

To facilitate communication, communication services with a wide bandwidth, and low latency, such that are provided through a network 704 (e.g., MPLS or other WAN), can be used to be able to reach the subscriber's centers of operations in the supply system, as well as places hosting INDS. As shown in Fig.7, we can serve various areas, such as California, Florida and Ohio. This unit principle of operation allows not only EF� - objective management of all kinds of power networks. It also allows better control between the grid. There are examples, when there is a failure in one network can affect operations in the adjacent grid. For example, a failure in the power grid in Ohio can have a cascading effect on operations in the adjacent grid, such as the mid-Atlantic grid. The use of block structure shown in Fig.7, allows control of individual energy systems and to manage the transactions between utilities. Specifically, the overall system INDS (containing the processor and memory) may control communication between the various Cores 120 INDE. This may reduce the likelihood of catastrophic failure that propagates from one grid to another. For example, a failure in the power grid Ohio may spread to the neighboring grid, such as the mid-Atlantic grid. The core 120 120 INDE assigned to the control grid of Ohio, you may try to fix the failure in the grid in Ohio. And the whole system INDS may attempt to reduce the likelihood of cascading failure occurring in the neighboring grids.

Specific examples of the functionality of the Kernel INDE

As shown in Fig.1, 6 and 7, the Core 120 INDE contains various functionality (represented by blocks), two of which are shown and the services of meter data management(MDM) 121 and analytical analysis of measures and services 122. The modular design principle of architecture, may have different functional capabilities such as MDM 121 and analytical analysis of measurements and services 122.

Observability of processes

As discussed above, one of the features of the services according to the application may be able to monitor the processes. Monitoring processes may allow the supply system to "observe" for the grid. These processes may be responsible for the interpretation of raw data taken from all sensors and devices in the grid, and making them available for processing information. Fig.8 presents a list of some examples of the possibilities of monitoring processes.

Fig.9A-represented IN the block diagram 900 of a sequence of operations, operational processes and measurement of the state of the grid. As shown in the drawing, the scanner data may request meter data, as shown in block 902. The request can be sent to one or more devices of the power grid, the substation computers and RTU linear sensors. In response to the request, the device can collect performance data, as shown in blocks 904, 908, 912, and can send data (such as a single, some or all of the operating data such as voltage, current, active power and reactive power), as shown in block� 906, 910, 914. Scanner data may collect operational data, as shown in block 926, and can send data in operational data store, as shown in block 928. Repository operational data store operational data, as shown in block 938. Storage of operational data may further send a brief description of the data in the archive, as shown in block 940, and the archive can store a brief description of the data, as shown in block 942.

App, connected with the state of the meter, may send a request for the data meter on DCE meter, as shown in block 924, which, in turn, sends a request to one or more meters for data collection of meters, as shown in block 920. In response to the request one or more gauges gauges collect data, as shown in block 916, and send data to the DCE voltage meter, as shown in block 918. DCE meter can collect data voltage, as shown in block 922, and send the data to the requestor of the data, as shown in block 928. App, connected with the state of the meters that can accept data from the meters, as shown in block 930, and determine whether they are a single process of determining the value or profile of the voltage characterizing the state of the grid, as shown in block 932. If� they are a single process of determining the values the data of the meter are transmitted to the requesting process, as shown in block 936. If meter data intended for storage to determine the state of the grid in the future, the data of the meter are stored in the repository of operational data, as shown in block 938. Store operational data further sends a brief description of the data in the archive, as shown in block 940, and the archive keeps a brief description, as shown in block 942.

Fig.9A IS further shown IN actions related to response to the demand response (DR). Reaction to demand refers to the dynamic mechanisms of demand to control the energy consumption of the consumer in response to the provision of the conditions, for example, at reducing consumer electricity consumption at critical times or in response to market prices. This could also be actually used reduce power or running local means of energy production that can be joined or not joined in parallel to the grid. It may not be related to energy efficiency, which means using less power to perform the same tasks on a continuous basis or whenever this task is performed. In response to the demand of consumers using one or more control systems can destroy them�AMB load in response to a request from the grid or market price conditions. The provision of services (lights, machines, air conditioning) may be reduced in accordance with pre-planned scheme of prioritization of workload during critical periods. Alternative load shedding is the local generation of electricity at the consumer to refill the grid. The lack of supply response to demand can significantly reduce peak price and, in General, the volatility of electricity prices.

Reaction to demand can generally be used to refer to mechanisms used to encourage consumers to reduce peak demand for electricity. Since electrical systems are usually built to meet the maximum demand (plus tolerance for accounting errors and unforeseen events), the reduction in peak demand can reduce the overall operational requirements and capital expenditures. Depending on the configuration of reserves in power generation reaction to demand, however, can also be used to increase demand (load) at times of high production and low demand. Some systems can, therefore, stimulate the accumulation of energy to allow a compromise between periods of low and high demand (or low and high prices). As the proportion of intermittent and�of energy-mix, such as wind energy, in the system grows, the response to the demand may become more and more important for effective management of the grid.

App, connected with the state of DR, may request the available reserves DR, as shown in block 954. Management system DR can then query the available reserves in one or more of its own devices DR, as shown in block 948. One or more devices may collect the available reserves DR in response to the request, as shown in block 944, and send the DR and reserves data in response to the control system of DR, as shown in block 946. Management system DR can collect resources and DR these reactions, as shown in block 950, and sends resource data DR and the reaction of the application, the communications with the state of the DR, as shown in block 952. App, connected with the state of the DR, can take these resources and DR reactions, as shown in block 956, and send the resource data and the reaction in the storage of operational data, as shown in block 958. The operational data store can store data resources DR and reactions, as shown in block 938. Storage of operational data may further send a brief description to the archive, as shown in block 940, and the archive can store brief description of the data, as shown in block 942.

The substation computer can request�'it application data from the application of the substation, as shown in block 974. In response to the application of the substation may request an application from the substation, as shown in block 964. The unit substation may collect application data, as shown in block 960, and send the application data unit substation (which may contain a single, some or all of the data of voltage, current, active power and reactive power), as shown in block 962. The application of the substation may collect application data, as shown in block 966, and send the application data to the requestor (which may be a computer substation), as shown in block 968. The substation computer can receive the application data, as shown in block 970, and send the application data in the storage of operational data, as shown in block 972.

The process of measuring the state of the grid and operating data may include receiving the status of the grid and the grid topology at a given time, and providing such information to another system and the data stores. Components of the process may include: (1) measuring and obtaining information about the state of the grid (this applies to operational data, discussed previously); (2) sending information about the state of the power system to other applications of the analytical analysis (which allows other applications, such as �of relojeria analytical to access the data state of the power system); (3) a brief description of the state of the grid to save the data connectivity/performance data (which allow the update of the information state of the grid to save the data connectivity/performance data in the appropriate format, and transfer this information to the archive for preservation, so that in the subsequent moments of time could be obtained point in time, corresponding to the topology of the power system); (4) retrieving the grid topology at a given time, based on the connectivity of the default and the current state of the grid (this ensures that the topology of the grid at a given time, applying a brief characterization of point-in-time state of the grid in the archive to basic connectivity to the data store connectivity, as discussed in more detail below); and (5) providing information about the topology of grid applications on request.

As for the subprocess (4), the topology of the grid can be obtained for a specified time, such as real-time, 30 seconds ago, 1 month ago, etc. to recreate the topology of the grid can be used numerous databases and program access to data in multiple databases, to recreate the topology of the grid. One base �data may include a relational database, which stores basic data connectivity ("database connectivity"). Database connectivity can store information about the topology of the grid at the time of creation to determine the basic connectivity model. Information about topology and assets can be updated in the database on a periodic basis, depending on the updates in the grid, such as adding or modifying circuits in the grid (for example, additional feeder circuit that is added to the grid). Database connectivity can be considered "static" because it does not change. Database connectivity may change if there are changes in the structure of the grid. For example, if there is a change to chains of feeders, such as adding a feeder circuit, the database connectivity may change.

One example of the structure 1800 database connectivity can be obtained from the hierarchical model shown in Fig.18A-D. Structure 1800 is divided into four sections and in Fig.18A shows a top left section of Fig.18V is the upper right section of Fig.18C - lower left section, and Fig.18D shows the lower right section. Specifically, Fig.18A-D show an example of the overall relationship, which is an abstract way of representing the underlying database connection. The hierarchical model in Fig.18A-D may store metadata that describes energy�et and can describe the various components of the grid and dependencies between components.

The second database may be used to store dynamic data. The second database may include non-relational database. One example of a non-relational database may contain archival database that stores time-sequential non-operating data, as well as archival performance data. Archive database can store a sequence of "flat" records such as: (1) the time stamp; (2) the device identifier; (3) the value of the data; and (4) the status of the device. Additionally, the stored data can be compressed. Because of this, operating/non-operating data in the grid can be easily stored and can be controlled even in the presence of large amounts of data. For example, data regarding 5 Terabytes can be constantly available at any time for use to recover the topology of the grid. Because data is stored in a simple record (i.e., without any organizational approach), it creates efficiency in data storage. As discussed in more detail below, data can be accessed through a specific tag, such as a timestamp.

Different analytical analysis to the grid may require receiving as input the topology of the grid in specific moments� time. For example, analytical analysis associated with a quality of energy, reliability, serviceability of the assets, etc., can use the topology of the grid as input. To determine the topology of the grid, you can access the main model of connectivity, as it is determined by the data in the database connectivity. For example, if you want the topology of a particular feeder circuit, the basic connectivity model can identify different switches in a particular feeder scheme into the grid. You can then take the access to archival database (based on a specific time) to determine the values of the switches in a particular feeder circuit. Then the program can merge the data from the main model of connectivity and archive database to create a view on a particular feeder circuit at a certain time.

A more complex example to determine the topology of the grid can contain numerous feeder circuit (e.g., circuit And feeder circuit and the feeder) that have a switch between the power systems and panel switches. Depending on the switching States of certain switches (such as switch between power systems and/or sectionalizing switches), sections of chain feeders may belong to the circuit And feeder circuit or In the feeder. Program that determines the top�wise grid can access data from the main model of connectivity and from the archive database to determine connectivity at a particular time (for example, belong to which chain circuit And feeder circuit or feeder In).

Fig.10 shows a flowchart 1000 of a sequence of operations of the processes associated with non-operating data. The application of extraction of non-operating data may request non-operating data, as shown in block 1002. In response, the scanner data may collect non-operating data, as shown in block 1004, where through a variety of devices in the power grid such as the grid, the substation computers and RTU linear sensors can be collected non-operating data, as shown in blocks 1006, 1008, 1110. As discussed above, non-operating data can include temperature, power quality, etc. of Various devices in the power grid, such as devices of the power grid, the substation computers and RTU linear sensors can send data to the non-operating scanner data, as shown in blocks 1012, 1014, 1116. Scanner data may collect non-operating data, as shown in block 1018, and send non-operating data to the application of extraction of non-operating data, as shown in block 1020. The application of extraction of non-operating data mo�em to collect non-operating, as shown in block 1022, and send collected data to the non-operating archive, as shown in block 1024. The archive may accept non-operating data, as shown in block 1026, store non-operating data, as shown in block 1028, and send non-operating information to one or more analytical applications, as shown in block 1030.

Fig.11 shows a flowchart 1100 of a sequence of operations of the event management process. Data can be generated by various devices, based on various events in the power grid, and sent via bus 147 events. For example, the data collection instrument gauges can send information notice of violation filing /restore the supply of power to the event bus, as shown in block 1102. RTU linear sensors generate a fault message and can send a fault message on the event bus, as shown in block 1104. The station can carry out the analytical analysis, which can generate a fault signal and/or stop the supply of power to the event bus, as shown in block 1106. The archive can send the signal mode on the event bus, as shown in block 1108. Furthermore, via the bus 147 147 events can send various data processes. For example, the intellectual process of handling damage, which is discussed more� in detail in Fig.14A-C, can send the event of damage analysis via the event bus, as shown in block 1110. The intellectual process of treatment of loss of electrical power, which is discussed in more detail in Fig.13A-B, can send event of the termination of the supply of power via the event bus, as shown in block 1112. The event bus can collect a variety of events, as shown in block 1114. Furthermore, the events sent via the event bus, can handle service complex event processing (CEP), as shown in block 1120. The CEP service can handle requests from multiple simultaneous high-speed streams of events in real time. After processing services SER event data can be sent via the event bus, as shown in block 1118. In addition, the archive may accept via the event bus, one or more event logs for storage, as shown in block 1116. Also, event data can be received by one or more applications, such as control system impairments in the transmission of power (OMS), data collection on violations flow, analytical, failure analysis, etc., as shown in block 1122. Thus, the event bus may send event data to the application, avoiding, thus, the problem of "drive" with the failure to provide data to other devices or other applications.

Fig.12A-R�avlana a block diagram 1200 of a sequence of operations of the transfer of signals to respond to the demand response (DR). DR may require the application for distribution operations, as shown in block 1244. In response connectivity/state of the grid can collect data availability, DR, as shown in block 1202, and can send data, as shown in block 1204. Application for distribution operations can distribute the optimization of the availability of DR, as shown in block 1246, via the event bus (block 1254) one or more management systems DR. Management system DR can send information and DR signals in one or more areas of the user, as shown in block 1272. One or more user premises can receive signals DR, as shown in block 1266, and send the response to DR, as shown in block 1268. Management DR can take the reaction of DR, as shown in block 1274, and send response DR on one, a few or all tires 146 data operations database for billing and marketing database, as shown in block 1276. Database for billing and marketing database can take reactions, as shown in blocks 1284, 1288. Bus 146 of these transactions may also take the reactions, as shown in block 1226, and send response DR and available reserves in the collection of data DR, as shown in block 1228. The collection of data DR can handle reactions DR and available reserves as shown in the block 1291, and send danyana the data bus operations, as shown in block 1294. Data bus operations can receive data distance DR and the reaction, as shown in block 1230, and send them to the block connectivity/status of the grid. Block connectivity/state of the grid can receive data, as shown in block 1208. The received data can be used to determine state data network, which may be sent (block 1206) via data bus operations (block 1220). Application for distribution operations can receive data state of the grid (as message events to optimize DR), as shown in block 1248. Using data from the state grid and the response of DR, the application for distribution operations can optimize distribution to generate the distribution data, as shown in block 1250. The distribution information can be obtained through the data bus operations, as shown in block 1222, and can be sent by the application to retrieve the connectivity, as shown in a block 1240. Bus operating data can send data (block 1224) application for distribution operations, which may, in turn, send one or more signals of the one or more DR management systems DR (block 1252). The event bus can collect signals for each of one or more systems management DR (block 1260) and send signals DR each system control� DR (block 1262). Management system DR can then process the signals DR, as discussed above.

An archive of the communication can send data on the event bus, as shown in block 1214. Archive operations may also send the data of the portfolio of generation, as shown in block 1212. Or, device asset management, such as Ventyx®, may request information virtual power plant (VPP), as shown in block 1232. Bus operational data can be collected VPP, as shown in block 1216, and to send data to the device asset management, as shown in block 1218. Device asset management can collect data VPP, as shown in block 1234, optimize the system, as shown in block 1236, and to send signals VPP on the event bus, as shown in block 1238. The event bus can receive signals VPP, as shown in block 1256, and to send signals to the VPP application distribution operations, as shown in block 1258. The application operations of the distribution may then receive and process event messages, as discussed above.

App to extract compounds can retrieve new data about consumers, as shown in block 1278, which should go in database marketing, as shown in block 1290. New data on consumers can be sent to the system connectivity/state of the grid, as show�but in block 1280, so that the system connectivity/network status could get a new DR connectivity data, as shown in block 1210.

The operator may send one or more signals cancel, if required, as shown in block 1242. Signals of cancellation can be sent to the application for distribution operations. Cancellation signal can be sent to the energy management system, as shown in block 1264, database compilation, as shown in block 1282, and/or database marketing, as shown in block 1286.

Fig.13A-represented IN the block diagram 1300 of a sequence of operations to gather information about violations in the work. Various devices and applications to send notification of violations of electricity supply, as shown in blocks 1302, 1306, 1310, 1314, 1318. In the event of violations in the work can be collected by the event bus, as shown in block 1324, which can send event of violations in the system of complex event processing (CEP), as shown in block 1326. Additional different devices and applications can send data about the state of restoration of supply of electricity, as shown in block 1304, 1308, 1312, 1316, 1320. The CEP system may receive messages about the States of violations in the work and recovery (block 1330), to handle the events (block 1332) and to send event data (block 1334). The app collect information about broken�ies in work can receive event data (block 1335) and request data on the status of the grid and connectivity (block 1338). Bus operational data may be data about the state of the grid and connectivity (block 1344), and pass it into the operational data store and/or archive. In response, operational data store, and the archive can send data about the state of the grid and connectivity (blocks 1352, 1354) via the bus operating data (block 1346) application to gather information about violations in the work (block 1340). Is determined whether the information of the state of the grid and connectivity of whether such a state is instantaneous, as shown in block 1342. If Yes, then such snapshot data is sent via the bus operating data (block 1348) database snapshot data storage (block 1350). Otherwise,creates a breach in the work (block 1328) data and disruption in the work shall be stored and processed by the control system during disturbances in the operation (block 1322).

The process of gathering information about violations in the work can detect violations in the work, to classify and register immediate data to determine the degree of impairment in work, to identify the root cause (s) of violations in the work, to monitor the elimination of violations in the work; to create the event of violations in the work and update the indices performance of the system.

Fig.14A-C shows a block diagram 1400 of a sequence of operations of the SRB process�and information during disruption. Complex event processing may require data from one or more devices, as shown in block 1416. For example, status data grid and connectivity in response to the request can send the data state of the grid and connectivity for use in the process of complex event processing, as shown in block 1404. Similarly, the archive, in response to the request, may send the state of the switch in real time for use in the process of complex event processing, as shown in block 1410. In addition, the process of complex event processing can take data network status and connectivity and the condition of the switch as shown in block 1418. Analytical analysis of the substation may request data about damage, as shown in block 1428. Data corruption can be sent to multiple devices such as RTU linear sensor and the computers of the substation, as shown in block 1422, 1424. Various information about the damage state of the grid, the connectivity data and the status of the switches can be sent to the analytical process analysis substation for the detection and characterization of events, as shown in a block 1430. The event bus may also receive event messages (block 1434) and to send event messages to the analytical process analysis substation (block 1436). Process analytical analysis of the substation can� to determine the type of event as shown in block 1432. For events of protection and change management substation computers can take the message about the event of damage, as shown in block 1426. For all other event types, the event may be made by the event bus (block 1438) and sent for complex event processing (block 1440). The process of complex event processing can accept event data (block 1420) for additional processing. Similarly, the state of the grid and connectivity can send a data grid in the process of complex event processing, as shown in block 1406. In addition, storage of common information model (CIM) can send the metadata for complex event processing, as shown in block 1414.

The process of complex event processing can send a message about the event of damage, as shown in a block 1420. The event bus can accept the message (block 1442) and send the event message to the application to gather information about the damage (block 1444). The app collect information about the damage can take the event data (block 1432) and query the status of the grid, the connectivity data of the condition of the switch as shown in block 1456. In response to the request to the application, the state of the grid and connectivity sends state data to the grid and connectivity (block 1408), and the archive sends data to switch status (block 1412). Collection application Swed�tions about the damage receives data (block 1458), analyzes the data and sends the event data (block 1460). Event data can be received by the event bus (block 1446) and sent to the registration file damage (block 1448). The registration file damage can log event data (block 1402). Event data can also be taken by bus operating data (block 1462) and transmitted to one or more applications (block 1464). For example, an application to gather information about violations in the work can accept event data (block 1466), discussed above with reference to Fig.13A-V, System management operations can also accept event data in the form of attire to work, as shown in block 1468. In addition, these events can get other requesting application, as shown in block 1470.

The process of gathering information may be held responsible for the interpretation of the data grid to get information about the current and potential damage inside the grid. Specifically, damage can be detected using the process of gathering information about the damage. Damage is usually short circuit caused by the fault of a hardware failure or an alternative path for electric current, for example a faulty power supply line. These processes can be used to detect the typical damage (usually obrabatyvalis� traditional equipment damage detection and protection - relays, fuses, etc.), as well as damage associated with high impedance inside the grid, which cannot easily be detected using the currents flowing in case of damage.

The process of collecting information about the damage can also classify and distribute the damage categories. It allows you to categorize and define categories of damages. Currently there is no standard systematic organization and classification of damage. For all this, de facto, can be installed and implemented the standard. The process of collecting information about the damage can further characterize the damage.

The app collect information about the damage can also determine the location of damage. Determination of fault location in a distributed system can be a difficult task because of its high complexity and the difficulties caused by unique characteristics of the distribution system, such as unbalanced load, three-, two - and single-phase laterals, the lack of sensors/gauges, various types of damage, different causes short circuits by changing the load conditions, long feeders with numerous branches and network configurations that are not documented. This process allows the use of a variety of ways �ocalizatio damage with so great accuracy, as far as technology allows.

Gathering information about the damage can additionally trigger event of a fault. Specifically, this process can create and put in circulation the corruption event on the event bus, as soon as the damage was discovered, classified, categorized, characterized, and localized. This process may also be responsible for collecting, filtering, mapping and re-up damage, so you receive the individual event of damage, not an avalanche, based on the raw events that are typical during an outage. Finally, the application to gather information about the damage can log events damage to the database and event registration.

Fig.15A-represented IN the block diagram 1500 of a sequence of operations of the processes of metadata management. Management processes metadata may contain: managing the list of items; management of connection and communication Protocol; the appointment and transfer of titles; managing the calibration factor of the sensor; and the data management of the topology of the grid in real time. The application is extracting the main connectivity may require basic connectivity, as shown in block 1502. Geographic information systems (GIS) can receive the request (block 1510) and send data to the application and delicate�of basic connectivity (block 1512). The application is extracting the main connectivity can receive data (block 1504), to extract, transform and load data (block 1506) and send basic data connectivity to the data centre connectivity (block 1508). Data center connectivity may then receive data, as shown in block 1514.

Data center connectivity can contain a data store of the consumer, where the information about the electrical connectivity of the grid component. As shown in Fig.15A-B, this information can usually be obtained from a geographic information system (GIS) of the power system, which stores the geographical position of the components in a grid, as at the time of construction. The data in the data warehouse describe hierarchical information about all the components of the grid (substation, feeder, section, segment, branch, t-shaped section, circuit breaker, automatic reclosing, switch, etc. - basically, all the assets). This data store may have information about the assets and connectivity, as at the time of construction.

The application can retrieve metadata request metadata for the assets of the grid, as shown in block 1516. Database metadata can accept the request (block 1524) and send the metadata (block 1526). The application metadata extraction can be metada�nye (block 1518), to extract, transform and load metadata (block 1520), and send the metadata in the data warehouse CIM (block 1522).

The data warehouse CIM, common information model) may then store the data, as shown in block 1528. CIM may prescribe standard formats of the public to use for reporting system for public use. Smart network INDE can facilitate the availability of information from the smart network in the standard format of the system's public areas. In addition, the CIM data warehouse can facilitate the transformation of specific data INDE in one or more formats, such as a predetermined standard format for public use.

App retrieve assets may request information about new assets, as shown in a block 1530. The asset register can accept a request (block 1538) and to send information about new assets (block 1540). The application extract the assets can be information about the new asset (block 1532), to extract, transform and load data (block 1534), and to send information about new assets in CIM data repository (block 1536).

The application of extracting connectivity DR may request connectivity data DR, as shown in block 1542. Bus operational data may send a request for data connectivity DR marketing database, as shown in block 1548. Marche�ingawa the database can accept the request (block 1554), to extract, transform, load DR connectivity data (block 1556) and send DR connectivity data (block 1558). Bus operating data can send data connectivity DR app retrieve connectivity DR (block 1550). The application of extracting connectivity DR can take DR connectivity data (block 1544) and send DR connectivity data (block 1546) through the bus operating data (block 1552) on the application of state of the grid and connectivity of DM, which stores DR connectivity data (block 1560).

Fig.16 shows a flowchart 1600 of a sequence of operations processes the notification. The subscriber notification may be logged on the web page, as shown in block 1602. The subscriber notification can create/modify/erase the settings of the watch list scenario, as shown in block 1604. The web page can store the created/modified/ erasable watch list scenario, as shown in block 1608, and CIM data repository may create a list of data tags, as shown in block 1612. The translation service names may convert the data tags for archive (block 1614) and send the tag data (block 1616). The web page can send a list of tag data (block 1610) via the bus operating data, which takes a list of data tags (block 1622) and transmits it to the means of notification (block 1624). A means of alerting�tion takes a list (block 1626), confirms and consolidates the lists (block 1628) and checks the archive of notifications according to the script (block 1630). If the detected exceptions, consistent with scenarios (block 1632), the notification is sent (block 1634). The event bus receives the notification (block 1618) and sends it to the subscriber notification (block 1620). The subscriber notification can receive notification via your preferred media, such as text, email, phone call, etc., as shown in block 1606.

Fig.17 shows a flowchart 1700 of the processes of data collection meters (AMI). The current collector may request data resident gauges, as shown in block 1706. One or more resident Parking meters can gather data resident gauges in response to the request (block 1702) and send the data resident gauges (block 1704). The current collector can receive data resident gauges (block 1708) and send them on the bus operating data (block 1710). The data collection mechanism of the meter may request data from the commercial and industrial meters, as shown in block 1722. One or more commercial and industrial meters can gather data for commercial and industrial meters in response to the request (block 1728) and send data to commercial and industrial gauges (block 1730). The data collection mechanism of�of aricela can accept data from the commercial and industrial gauges (block 1724) and send them on the bus operating data (block 1726).

Bus operating data can receive data resident, commercial, and industrial meters (block 1712) and send data (block 1714). Data can be taken from the database of the data warehouse gauges (block 1716) or may be taken by a billing processor (block 1718), which may, in turn, send them to one or more systems, such as CRM (management of relations with clients).

The monitoring processes may further comprise the process of remote monitoring of assets. Control of assets within the grid can be justifiably difficult. There may be different sections of the grid, some of which are very expensive. For example, a substation may contain power transformers (worth over 1 million US dollars) and the interrupters. Often the electricity system, in any case, have done little to analyze the assets and maximise the use of assets. Instead, the focus of the power system usually focuses on the guarantee of maintaining the supply of power to the consumer. Specifically, the power supply system focuses on planned inspections (which usually must be performed at specified intervals) or "managed events" service (which should be held, if at a section of the grid about�coming off injury).

Instead of typical, routine inspections or "event-driven" service processes remote monitoring of assets, may focus on maintenance based on condition. Specifically, if one area (or all areas) the grid can be evaluated (on a periodic or continuous basis), the maintenance of operational condition of the power grid can be improved.

As discussed above, data can be generated on different parts of the grid and transmitted (or to be available). The data can then be used by the Central organization to determine the state of health of the grid. In addition to analyzing the health of the power grid, the Central organization can perform control use. Generally, the equipment in the power grid is operated using significant reserves of reliability. One reason for this is that supply companies are conservative by nature and strive to maintain supplied to the consumer energy within a wide field of tolerances. Another reason is that public utilities that control the grid, may not know the size of the item of equipment used in the power grid. For example, if the power company transmits energy to the specific feeder TSE�and, energy company may not have the means to her to know how much transmitted power is close to the limit settings of feeder circuit (for example, the feeder circuit may overheat). Because of this, the public utilities can Nedospasov one or more sections of the grid.

Energy companies also typically spend a significant amount of money to enhance the power grid, as the load on the grid increases (i.e., increases the amount of power used). Due to the lack of power companies knowledge, those companies without you having to update the grid. For example, a feeder circuit which are not operated when the power close to the limit may, however, be updated by reconductoring (i.e., strip of thicker conductors in the feeder circuit) or may be installed additional feeder circuit. The cost, in itself, significant.

Remote process control assets can control various aspects of the grid such as: (1) analysis of the current health status of the assets for one or more sections of the grid; (2) analysis of the future health status of the assets for one or more sections of the grid; and (3) an analysis of the use of one or more sections of the grid. First of all�x, one or more sensors can measure and transmit data for use by remote processes control of assets, to determine the current health state for the particular section of the grid. For example, a sensor on the power transformer can provide indication of serviceability by measuring the scattered gases in the transformer. Remote process control assets can then use analytical tools to determine if a specific area of the grid (such as a power transformer) defective or faulty. If a particular section of the grid is faulty, this particular part of the grid can be identified.

In addition, remote control of assets can analyze data generated by the sections of the grid to predict future serviceability of the asset sections of the grid. There are issues that create tension in the work of an electrical component. Factors creating tension may not necessarily be permanent, they can be intermittent. The sensors can provide an indication of tension in each section of the grid. Remote process control assets can record the results of strength measurements, indicated by the sensor data, and can analyze the results of strength measurements to PR�to anticipate the future state of the health of the grid. For example, remote monitoring of assets can use trend analysis to predict when a particular section of the grid can fail, and can schedule maintenance in advance (or simultaneously) the time when a specific area of the grid may fail. Thus, remote control of assets can predict the lifetime of a given section of the grid and, thus, to determine when the life of this section of the grid becomes too short (that is, which portion of the grid will be too fast to draw closer to failure).

Additionally, remote control of assets can analyze use of the site grid to better manage the grid. For example, remote monitoring of assets can analyze feeder circuit to determine what is working load capacity. In this example, a feeder circuit of the remote control processes of assets can determine what feeder chain currently operates at 70%. Remote process control assets can additionally recommend that the particular feeder circuit can be operated with a higher percentage (such as 90%), still retaining reasonable reserves secure. Distancionarie control of assets, thus, to effectively increase productivity simply by usage analysis.

The methodology for determining the specific technical architecture

There are various methodologies specific technical architecture, which can use one, several or all elements of the INDE reference architecture. The methodology may include multiple stages. First of all, can be made basic step to create a documentation on the current status of public use and assessment of readiness for transition to smart grid. Secondly, there may be performed the step of creating the requirements for determining the future status and detailed requirements for the transition to this state. Thirdly, can be performed in the stage of development solutions to create a solution component architectures that contain smart network, including measurement, monitoring and control. For architecture INDE this may include measuring instruments, communication system for transferring data from devices to applications Kernel 120 INDE, and these applications Core 120 INDE, which should save the data and respond to data Analytics applications to interpret the data, the data architecture for modeling measured and interpreted data integration architecture for the exchange of data and information IU�INDE du and systems of public use, technology infrastructure for use by various applications, databases and standards that you can follow to allow you to obtain industry standard mobile and effective solution. Fourthly, the simulation values can be performed when creating key performance indicators and success factors for smart grid and implement ways to measure and evaluate the performance of the system depending on the desired characteristics factors. The above disclosure relates to the aspect of the development of architecture stage 3.

Fig.19A-b presents an example of the graphical representation through the process of detailed design. Specifically, Fig.19A-presented IN a sequence of steps that can be taken to determine the requirements for smart grid, and steps that can be performed for implementation of smart grid. The process of developing a smart network may begin with the formulation of the vision of a smart network, but in General outline the General goals of the project, can lead to the process of drafting the operational plan. The process of drafting the operational plan can lead to a detailed plan and modeling values.

Preparation of detailed project can provide a methodological approach to the definition of the smart grid in the context of the entire energy�climate enterprise. Preparation of detailed project may include General operating plan, which may lead to basic and system evaluation (BASE) and to the definition of requirements and choice of analytical assays (RDAS). The process RDAS can create a detailed definition of the specific smart energy network of the company.

Process BASE can set the starting point for the power system from the point of view of systems, networks, devices and applications to support features smart network. The first part of the process is to develop a systematic inventory of the grid, which can include: the structure of the grid (such as generation, transmission lines, transmission substations, podlinee transmission, distribution substations, distribution feeders, voltage classes); devices for the grid (such as switches, automatic reclosing, capacitors, regulators, compensators of the voltage drop, feeder); automation of the substation (such as IED, substation LAN, instrumentation, RTU/computer stations); automation of allocation (such that as management of capacitors and switches; damage localization and dynamic management tool load; the system of coordination of LTC; DMS; control system response to the demand); and grid sensors (such as dates�IKI types, quantity, and use the counters on the distribution grid, transmission lines and substations); etc. as soon As material and production reserves all agreed, can be created evaluation system for public use in relation to the model of readiness smart grid high-level. Can also be created to model data flow and system diagram.

The configuration process architecture (ARC) to develop advanced technical architecture of the smart grid for energy supply systems by combining information from the process BASE, requirements and constraints from the process of the RDAS and INDE reference architecture to create a technical architecture that meets the specific needs of the power system, which uses the inherited advantages of the respective systems and which meets all the constraints existing in the supply system. The use of the INDE reference architecture may help to avoid the need to invent customized architecture and ensures that the development of the solution involves the experiences and best practice. It can also ensure that the solution will be able to extract reusable assets smart networks.

The process configuration of the architecture of sensor networks (SNARC) can provide structure�tour to create a series of decisions define the architecture of distributed sensor networks to support smart grid. The structure may be formed as a series of decision trees, each of which focuses on a specific aspect of the architecture of sensor networks. When decisions are made, can be created an architectural diagram of a sensor network.

The distribution of sensors by means of the recursion process of the T-section (SATSECTR) can provide a framework for determining how many sensors should be placed on the distribution grid, to obtain a given level of observability, subject to the restrictions on the price. This process can also define the sensor types and locations.

The evaluation process is part of the solution and the template components (SELECT) can provide a framework for assessing the types of the solution components and provides a project template for each class component. The template can contain the reference model specifications for each of the elements of the solution. These templates can then be used to request quotations of suppliers and maintain supplier evaluation/products.

The process of planning updates for applications and networks (UPLAN) can provide a plan to upgrade existing energy supply systems, applications and networks, to be ready for integration into the smart solution network. The process of risk assessment and planning�ing management (RAMP) can provide risk assessment, associated with specific elements of the solution for smart network that is created in the ARC process. The process UPLAN can assess the level or degree of risk for identified risk elements and provides an action plan for risk reduction before the system's public areas will undergo expansion. The planning process change analysis and management (CHAMP) can analyze the process and organizational changes that may be needed for the energy supply system to realize the value of investments in smart network, and can provide control plan high level to execute these changes in a way that is synchronized with the deployment of the smart grid. The CHAMP process can lead to the creation of a detailed project.

Operational plan in the modeling process values can lead to the metric values, which then can lead to estimation of cost and profit. The assessment may lead to the creation of one or more cases, such as case ratios and business case, which, in turn, can lead to the closure of the case. The results of the detailed plan and the simulation values can be sent to the energy company for approval, which may lead to updates of the system's public areas, the deployment of smart networks and actions for reduced� risk. After all the above, the grid can be designed, built and tested and then put into operation.

Description alternative architecture INDE high level

In one example, the General architecture INDE can be applicable to the industry, containing both mobile and stationary sensors. Architecture INDE can be implemented to receive sensor data and react appropriately distributed through, or through a centralized intellectual center. Fig.21-28 explains examples of architecture INDE implemented in various fields of transportation.

General architecture

Referring to the drawings, in which similar reference position refer to similar elements, Fig.21A-C presents one example of the overall architecture for INDE. This architecture can serve as a reference model, which provides a consistent collection, transmission, storage and management of network data associated with one or more specific industries. It can also provide analytical analysis and management, analytical analysis, and the integration in the above processes and systems. Therefore, it can be considered as the architecture of the entire enterprise. Some elements, such as operational management and aspects of the network itself, are discussed below more on�follows.

The architecture shown in Fig.21A-C may contain up to four data bus and integration: (1) high speed bus 2146 data speed sensors (which can include operating and non-operating data); (2) a dedicated bus 2147 event processing (which can include event data); (3) 2130 bus service operations (which can serve to provide information to operational units); and (4) service bus for enterprise IT systems operating unit (shown in Fig.1A-C as bus 2114 environment of enterprise integration to service IT-service enterprise 2115). Separate data bus can be implemented in one or more ways. For example, two or more data buses, such as high speed bus 2146 sensor data and bus 2147 event handling, can be different segments of a single data bus. Specifically, the tires may have a segmented structure or platform. As discussed more below, the hardware and software and/or software, such as one or more switches may be used to route data to different segments of the data bus.

As another example, two or more data bus can be a separate tire such as a separate physical bus, from the point of view of hardware implementation, the required DL� data on individual tires. Specifically, each of the tires may contain cabling, separated from each other. Additionally, some or all of the individual tires may have the same type. For example, one or more tires may include a local area network (LAN) such as Ethernet®, unshielded wiring of twisted pair and Wi-Fi. As discussed in greater detail below, the hardware and the software and/or software, such as a router, may be used for sending data on one of the tires of the various physical tires.

As another example, two or more of the tires can be at different segments in the structure of a single bus, and one or more of the tires can be on a separate physical buses. Specifically, high-speed bus 2146 sensor data and bus 2147 event handling can be different segments of a single data bus, while the bus 2114 environment of enterprise integration can be on physically separate bus.

Although in Fig.21A-C shows the four tires may be used more or fewer tires to pass four enumerated data type. For example, a single non-segmented bus can be used to transmit sensor data and processing data event (bringing the total number of tires to three), as discussed below. In addition, the system can operate bessini 2130 maintenance operations and/or bus 2114 environment of enterprise integration.

Wednesday IT can be SOA-compliant. Service-oriented architecture (SOA) is an architectural style of computing systems for creating and using business processes that are composed of the services throughout the lifespan. SOA also defines and establishes the IT infrastructure to allow different applications to exchange data and participate in business processes. Although the use of SOA and service bus enterprise is optional.

In the example of the generalized industry the drawings show the various elements inherent in a common architecture, such as: (1) the Core 120 INDE; and (2) the Device 2188 INDE. This division of elements within the overall architecture serves for illustration purposes. Can be used other division elements. In addition, the division of the elements may vary in different industries. Architecture INDE can be used to support both distributed and centralized approaches to intelligence, and providing mechanisms to work with in large scale implementations.

Reference architecture INDE is one example of a technical architecture that can be implemented. For example, this may be an example of mitarchitecture used to provide the starting point for the development of any number of specific technical architectures, one DL� each industry solution {e.g., different solutions for different industries) or one for each application within the industry (for example, the first solution to the first network transport and the second solution to a second network transport), as discussed below. Thus, a particular solution for a particular industry or specific application within the industry (such as applying to a particular company) may contain one, some or all of the elements of the INDE reference architecture. Moreover, the INDE reference architecture may provide a standardized starting point for developing solutions. Discussed below is the methodology for determining the specific technical architecture for a particular industry or specific application within the industry.

Reference architecture INDE can be a common enterprise architecture. Its purpose may be to provide continuous patterns data management and analytical analysis, and their integration into systems and processes. As advanced technology networks can affect every aspect of a business process, you need to remember about actions not only at the network, operations and premises of the user, but also at the enterprise and operating unit. Therefore, INDE reference architecture can and should be a benchmark enterprise-level SOA, for example, to keep the fry�the SOA for the purpose of mates. This should not be construed as a requirement that the industry, as such, must convert their existing environment IT is in SOA before advanced network can be built and used. Service bus enterprise is a useful mechanism to facilitate the integration of IT, but it is not required to carry out the rest of the solution. The following discussion focuses on the various components of elements INDE for transportation; however, one, several or all components of elements INDE can be applied to various industries, such as telecommunications and exploration of energy sources.

Group component INDE

As discussed above, various components in the INDE reference architecture may include, for example: (1) the Core 2120 INDE; and (2) the Device 2188 INDE. The following sections discuss these examples of groups of elements INDE reference architecture and provide descriptions of the component in each group.

The core of INDE

Fig.22 presents the Core 2120 INDE, which is part of the INDE reference architecture, which can be located in the control center operations, as shown in Fig.21A-C. Core 2120 INDE may contain a unified data architecture for data storage and schema integration for Analytics to manage these data.

In addition, the data architecture can�t use a middleware 2134 Association, to connect other types of data (such as, for example, sensor data, operational and archival data, files, reception and events) and the connectivity files and metadata in a unified data architecture that can have a single point of entry for access to the high level apps, including apps for the enterprise. Real-time systems can also access the storage key data through a high speed data bus and several data warehouse can receive data in real time. In architecture INDE different types of data can be transported within one or more of the tires.

Types of transported data may include operating and non-operating data, event, data connectivity and data network location. Operating and non-operating data can be transported using bus 2146 operating/non-operating data. Data collection applications may be responsible for sending some or all of the data on the bus 2146 operating/non-operating data. Thus, applications that need this information, you may be able to receive data by subscribing to the information or invoking services that can make these data available.

Events can contain messages and/or alarms originating on� various devices and sensors which is part of the industry network, as discussed below. Events can directly be generated by devices and sensors, as well as created various applications of analytical analysis based on data measurements from these sensors and devices.

As discussed in more detail below, data can be sent from a different component (such as a Device 2188 INDE). Data can be sent to Core 2120 INDE with the help of wireless and wired technologies or combinations of them both. These can be networks 2160 communications services, which can send data to the device routing 2189. The device routing 2189 may contain software and/or hardware and software to control the direction of data on the bus segment (when the tire has a segmented structure), or on a separate bus. The routing device can include one or more switches or router. The device routing 2189 may include a network device whose software and hardware guides and/or transmits data on one or more tires. For example, the device 2189 routing can direct the operating and non-operating data onto the bus 2146 operating/non-operating data. The device 2189 routing direction may also�th event data onto the bus 2147 event.

The device 2189 routing can determine how to send data based on one or more ways. For example, the device routing 2189 may examine one or more headers in the transmitted data to determine whether to send data to the segment operating/non-operating bus 2146 or data on the bus segment 2147 event. Specifically, one or more headers of the data can specify whether the data operating/non-operating data (so that the device 2189 routing data sent on the bus 2146 operating/non-operating data) or whether the data is the event data (so that the device 2189 routing data sent on the bus 2147 events). Alternatively, the device 2189 routing can examine the payload data to determine the data type (for example, a device 2189 routing can examine the format of the data to determine whether the data operating/non-operating data or event data).

One of the storage, such as storage of operational data 2137, operational data stores, can be implemented as a truly distributed database. Another from the vaults, archive (specified as the archive data 2136 in Fig.21 and 22) may be implemented as a distributed database. Supplementary�additional, events can be saved in any of several data warehouses via bus complex event processing. Specifically, the events may be stored in magazines 2135 events that can be a repository of all the events that are sent on the bus 2147 event. The event log can store one, some or all of the following event data: event ID; event type; event source; the priority of an event and the create event. Bus 2147 event should not store the events for a long period of time, ensuring conservation for all events.

Storage of data may be such that the data can be close to the source as possible or real. In one embodiment, the implementation of this might apply, for example, substation data stored in the Device 2188 INDE. But this data can also be queried at the level of 2116 control center operations for making different types of decisions that consider the network at a significantly fragmented. In connection with the approach of distributed intelligence approach with distributed data can be adopted to facilitate the availability of data at all levels of decision making through communication database and information services, depending on the situation. Thus, the solution for storage of archival data (which can be accessed at the level of 2116 control center OPE�publications) may be similar to the solution for the storage of operational data. Archive/joint analytical analysis can be conducted at a level of 2116 control center operations, gaining access to data at the Device level INDE. Alternatively, data can be stored centrally in the Nucleus 2120 INDE. However, given the amount of data that may need to be transferred among Devices 2188 INDE, data storage Devices 2188 INDE may be preferable. Specifically, if you have thousands or tens of thousands of sensors, the amount of data that must be passed to the Kernel 2120 INDE, may form a bottleneck for communication.

Finally, the Core 2120 INDE can program or to manage one, several, or all Devices 2188 INDE in the network. For example, the Core 2120 INDE can modify the programming (such as software downloads or updates) or to provide a management team to manage every aspect of the Device 2188 INDE (such as the management of the sensors or analytical analysis). Other elements, not shown in Fig.2, can contain different elements of integration, to support this logical architecture.

Table 4 describes some elements of the Kernel 2120 INDE, as shown in Fig.21.

Table 4
The Core elements INDE
Elements�t KERNEL INDE Description
Services 2144 CEPProvide high-speed, low-latency processing of the event stream, event filtering and event correlation of Multiprotocol.
Centralized application 2139 analytical analysisCan consist of any number of commercial or custom applications analytical analysis, which are not used in real time, working primarily with data from data warehouses Kernel INDE.
Services 2140 visualization/notificationSupport for visualization of data flows, States and events, and automatic notifications based on the starts of the event.
Services 2141 application managementServices (such as services 2142 support applications and services 2143 support distributed computing) that support the launch and implementation of applications, web services, and support for distributed computing and automated loading of remote programs (e.g. OSGi).
Services 2145 network managementAutomatic control communication systems, applications and databases; monitoring of �item, root cause analysis of failures.
Services 2126 metadataServices (such as services 2127 connectivity services 2128 translation of titles and services 2129 TEDS) for storage, retrieval and update system metadata, including the connectivity of sensor networks/links, lists, paragraphs, calibration of sensors, protocols, fixing devices, etc.
Services 2123 analytical analysisServices (such as services 2124 sensor data and services 2125 management analytical analysis) to support access to sensor data and analytical analysis sensors; management of analytical data.
System 2121 data management sensorsFunctions of the data management system of sensors.
Bus 2147 complex event processing in real timeThe message bus that is dedicated to the treatment of flows of events - the purpose of a dedicated bus is to provide a wide bandwidth and extremely low latency for highly pulsating flow of event messages. The event message may be in the form of XML messages. Can be used and other types of messages. The events can be separated from operational/ exploitation� data and can be transmitted on a separate or dedicated bus. Events usually have a higher priority, since they usually require immediate action from the operational point of view (defective equipment). Bus event processing (and related services correlation and event processing shown in Fig.21) can filter out the flow of events, interpreting, what events are better able to influence other devices. In addition, the tire event handling can take many event streams, detect various models, having many streams of events, and to provide interpretation of the numerous streams of events. Thus, the bus event processing can not only study event data from a single device, instead, it may consider numerous devices (including many classes of devices that may seem unrelated) to discover correlations. Flow analysis for single or multiple events may be based on rules.
Bus 2146 operating/non-operating real-time dataOperational data may include data reflecting a current state of a particular branch of the network. Non-operating data can include data �tragoudia "condition" or state of the device. Operating data previously transmitted directly to a specific device (creating, thus, a potential problem of "congestion" when data is not available to other devices or other applications). However, using the bus structure, the operational data can also be applied to the use/optimization of assets, system planning, etc. non-operating data previously received, sending the man into the field to collect operational data (instead of automatically send non-operating data in a Central repository). Typically, operating and non-operating data is created in various devices in the network at the specified times. They differ from these events, which are typically created packages, as discussed below. The message bus can be allocated for treatment of flows operating and non-operating data from substations and grid devices. A dedicated bus may be designed to provide a constant low-delay by coordinating with the data flow; as discussed elsewhere, a single bus may be used to convey both operating and non-operating data processing events under certain circumstances (effectively combining bus operating/exploitation�x data bus event processing).
Bus 2130 service operationsThe message bus that supports the integration of standard applications for industrial operations. Bus 2130 maintenance operations can serve as a provider of information about smart grid applications operating unit of the system of public use, as shown in Fig.21. Application of the analytical analysis can convert the raw data from sensors and devices in the grid, with operational information that will be available to the application system of public use, to perform actions on the control grid. Although most interactions between applications operating unit of the system of public use and Core 2120 INDE is expected to pass the bus system application public will have access to the other two tires and also use the data from these tires (for example,
the meter reading data from the bus 2146 operating/non-operating data, events, violations in the work with the tires 2147 events).
Storage 2133 sensor dataStorage 2133 sensor data can provide quick access to the data used�hardware sensors for analytical analysis. This repository can contain all the information read from the sensors obtained from the sensors. Data collected from sensors can be stored in the storage 2133 sensor data and be shared with other applications, as well as other tests.
Magazines 2135 event registrationMeeting registration files relating to the work of different sectoral systems. Magazines 2135 event registration can be used for analysis after the event and to analyze the data.
Archival data 2136Archive telemetry data in the form of standard data archive. Archived data can store 2136 temporal sequence non-operating data, as well as archival performance data. Analytical analysis related to such areas as reliability, serviceability of the assets, etc., can be performed using data from 2136 archival data.
Performance data 2137Performance data 2137 may contain operational database in real time. Performance data 2137 may line up in a truly distributed form. Specifically, operational data 2137 can store the measured data are obtained from d�of tchekov and devices. Archive the measured data are not stored in the data store, instead they are stored in archival data 2136. Database tables in the operational data 2137 can be updated with the most recent results of the measurements obtained from these sensors and devices.

As discussed in table 4, bus 2146 real-time data (which reports the operating and non-operating data) and bus 2147 complex event processing in real time (which transmits the data event processing) are combined into a single bus 2346. An example of this is shown in the flowchart 2300 of Fig.23A-C.

As shown in Fig.21A-C, tires are divided according to work characteristics. When processing low latency CEP can be important for certain applications that work with very large batches of messages. Most data streams to the grid, on the other hand, are more or less constant, with the exception of files of digital fault recorders, but they can usually recover on a managed basis, whereas packages events are asynchronous and random.

Fig.21 further shows additional elements in the center 2116 operations management, separate from the Core 2120 INDE. Specifically, Fig.21 further shows the system 2153 input (s) for data collection, which is responsible�NPA for communicating with the meter to collect data from them and provide the collected data public use). IP network services 2158 are a set of services operating on one or more servers that support standard IP connection (such as DHCP and FTP). System 2159 sending mobile data is a system that sends/receives messages to and from mobile data terminals in the field. System 2150 management of the organization works is the system that controls and manages the outfits to work. Geographic information system (Geographic Information System) 2149 is a database that contains information about where assets are located geographically and how the assets are connected together. If the environment has a service oriented architecture (Services Oriented Architecture (SOA), the system 2148 operations support SOA is a collection of services to support SOA environment.

One or more systems in the center 2116 management of the operations outside Core 2120 INDE, are systems derived products that may be of public use. Examples of such systems inherited products contain system 2148 operations support SOA, system 2153 input (s) to collect sensor data, IP network services 2158 system and 2159 sending mobile data. However, these systems are inherited products may be unable to process or manipulate data received from the smart network. Core 2120 INDE may be able to take �data from the smart network to process the data from the smart network and transmit the processed data to one or more systems inherited by products in the form of a system of inherited products can use (such as specific formatting for the private system derived products). Thus, the Core 2120 INDE can be considered as middleware.

Center 2116 operations management 2116, including the Core 2120 INDE, may contact the system 2115 IT companies. Generally speaking, the functionality of the system 2115 enterprise IT contain operations operating unit. Specifically, the system 2115 enterprise IT can use the bus 2114 environment of enterprise integration to send data to different systems within systems 2115 IT companies, including storage 2104 business data, applications, 2105 to collect business data, the system 2106 enterprise resource planning, financial systems 2107, system 2108 information of consumers, the system 2109 human resources system 2110 asset management system 2111 support enterprise SOA, system 2112 network management and service 2113 messaging company. System 2115 enterprise IT may further contain a portal 2103 for Internet connection 2101 through the firewall 2102.

The device INDE

Group Device 2188 may contain INDE l�fight a variety of devices to provide data, associated with a specific device. In one example, the group 2188 devices may include stationary units 2190 sensors and mobile units 2192 sensors. Each stationary unit 2190 sensors and mobile 2192 sensor unit may include one or more sensors, processors, storage devices, communication modules and/or power supply modules that allow you to receive any data from the sensors, and sequentially process and/or transmit the raw data or processed sensor data. Raw data or processed sensor data from inpatient units 2190 sensors and mobile units 2192 sensors can be processed by one or more firewall interfaces 2194. In one example, each gateway 2194 may be one or more devices capable of encoding and transmitting data to the center 2116 operations management. Raw data or processed sensor data from inpatient units 2190 sensors and mobile 2192 units of sensors can also be provided to the collector 2196 data. Collector 2196 data may include one or more processors, storage devices, communication modules and power supply units. Collector 2196 data may be a storage device by the processor, configured to collect, store and transfer data. Collector 2196 data about�usestat connection with stationary blocks 2190 sensors and mobile units 2192 sensors, to gather data and to transmit the collected data to one or more firewall interfaces 2194.

In one example, the stationary blocks 2190 sensors can detect conditions associated with one or more mobile units 2192 sensors or other stationary blocks 2190 sensors. Mobile units 2192 sensors can detect conditions associated with stationary blocks 2190 sensors, or may detect other conditions associated with other mobile units 2192 sensors. During operation, the event data can be created by stationary blocks 2190 sensors and mobile units 2192 sensors. These events can be a sign of abnormal or undesired States of the network transport. Such event data may be transmitted from the stationary blocks 2190 sensors and mobile units 2192 sensors through the firewall interfaces 2194 Central organization. In one example, event data may be received by the device routing 2189. The event data can be provided on the bus 2147 event device routing 2189. Accepted event data may be processed by the center 2116 operations management to allow you to create an appropriate response.

Fig.24A-C shows the block diagram of the architecture INDE to work with network rail. The system INDE shown in Fig.24A-Wcan to accept event data from inpatient units 2190 sensors and mobile units 2192 sensors, placed on a platform 2400, as shown in Fig.25. In one example of the stationary blocks 2190 sensors and mobile units 2192 sensors may be such as disclosed in patent publication U.S. No. 2009/0173840 herein by reference.

As shown in Fig.25, in one example, a freight train 2500 may include platform 2400 different types, such as box wagons, utility wagons, platforms for transportation of coal, motor cars and any other motor means, arranged to travel on rails. Motor car 2502 may be driven by diesel engine, battery, flywheel, fuel tank or any combination of these. Each motor car 2400 can include one or more mobile units 2192 sensors. Mobile units 2192 sensors can communicate with each other, giving the opportunity to communicate among mobile units 2192 sensors the same wagon 2400 of 2400 cars, attached to the same chain of 2400 cars or other cars 2400 (not shown), separated from the chain, such as those in railway depot. Each mobile unit 2192 sensors may be a unique identifier (ID) and each individual car 2400 may have a unique ID that is stored for each mobile unit 2192 sensors associated with a particular �the AGON 2400. ID may be provided, for example, via RFID.

In one example, the stationary blocks A sensors can be configured to act as a detector of "hot" boxes, is arranged to control the heating associated with wheels, axles platform, etc. the Term "hot" buksa, known in the art may refer to test overheating axle boxes of the platform in one or more axial bearings and/or other, associated with the wheel component parts of railway rolling stock. Stationary blocks A sensors can be placed along the tracks 2501. Each stationary unit A sensors can be equipped with one or more infrared sensors (IR) to determine heating patterns bearings/axles/wheels of 2400 cars as the cars pass through the reading zone of stationary concrete block A sensors. Abnormal heating can indicate various problems, such as instability of the load on the platform, structural problems of the car, the problems of railway tracks, etc. If it detects the overheated bearing, may include the specific type of alarm to warn the engineer to stop the train and eliminate potentially hazardous situation which, if let her continue, may lead to cruceni� trains. An example of a detector hot axle box is disclosed in U.S. patent No. 4659043, which contains real here by reference. Stationary blocks A sensors can be performed with the data processing capabilities of the IR sensors to generate event data based on the alarm, such as event messages, which should be taken by bus 2147 event for later processing.

Stationary blocks 2192 In detectors can also be used as a fault detector. The fault detector can be a device used on railroads to detect problems with the axles and from passing trains. The fault detectors can be integrated into the railway track, and may include sensors to detect one or more kinds of problems that may arise. The fault detectors enable the Railways to exclude utility wagon at the tail of the train station and various means are placed along the path for detecting dangerous conditions. The fault detector may be integrated or connected with a wired or wireless transmitter. As the trains pass by the fault detectors, the detector can output the name of the railroad, the column showing the number of miles or the place of its location, the number of ways (depending on the situation), the number of axes in �the bus, held, and indication of "no fault" to indicate that the trains were not detected no problems. Additionally can be inferred ambient temperature in a given location and the speed of the train. When a problem is found, the detector may output an indication of the problem, followed by a description of the problem the task and the location of the axis in the train, for which the problem occurred.

Stationary blocks S sensors may also be configured to act as a "silver" boxes, as is known in the art, is arranged to receive raw or processed data taken by one or more stationary units A and B sensors. Stationary blocks S sensors can receive data from the respective group of stationary blocks A sensors, based on various General factors, such as, for example, a geographic location. In this respect, the stationary blocks S sensors can act as the collector 2196 data, as shown in Fig.21A-21C.

In the operation of the train 2500, having a chain of 2400 cars, can move along the tracks 2502. As the train 2500 stationary blocks A sensors can detect information relating to each wagon 2400, such as bearing temperatures. Each hospital�block A sensors can also communicate with each unit 2192 sensors. The connection may allow each fixed block A sensors to check the health of each car 2400 and associated mobile units 2192. Any indication of abnormal or undesired conditions associated with a particular platform 2400 may be transferred to inpatient units S sensors. The detected condition may relate to the design of the car, medium car operation (e.g., temperature), cargo carriage (for example, weight, distribution, quantity, etc.), movement of the carriage, the provisions of the car or for any other parameter relating to the carriage of 2400. The detected condition may also be a security concern, for example, when you open the door of the car, which may indicate an attempted robbery or vandalism. Data 2508 events can be used to prevent a particular organization, which may belong to a certain car. Thus, the center 2116 operations management can monitor entire railway network, but the company, having individual cars 2400, can be prevented when data is transmitted events in relation to the particular car 2400 owned by a particular company. Warning messages may be provided via the interface, a subscription service, e-mail, text message and/or any other communication method, �utility to provide such warnings.

In one example, one of 2400 cars, such as motor car 2502 may have a mobile unit 2192 sensors serving as the main mobile unit 2504 sensors, to receive data from each mobile stationary unit 2192 associated with cars 2400 current chain of cars. When the 2400 cars are joined to form a specific train, each mobile unit 2192 sensors may be logged main mobile unit 2504 sensors. Main cell block 2504 sensors may take a batch or continuous streams of raw data or processed data from mobile units 2192 sensors. This allows the engineer in the operation to determine the serviceability of each car 2400.

In one example, each mobile unit 2190 sensors can contain a block of global positioning system (GPS), allowing each individual mobile unit 2192 sensors to determine the corresponding geographic location. Each mobile unit 2190 sensors can receive GPS signals 2506 to determine the geographic location. This information can be transmitted to the stationary blocks A sensors when the car is close to allow the transmission of such information. Each mobile unit 2192 sensors can automatically or on demand to transmit GE�graphical position of the main cell block 2504 sensors, which can then be broadcast through the built-in firewall interface 2194 in the center 2116 operations management. In one example, gateway 2194 may be such as described in patent publication U.S. No. 2009/0173840. Each mobile unit A sensors may also use wireless technology to transmit the GPS signal, allowing you to monitor every car 2400 individually. Such a construction may allow to follow the whole train when only one car has a clear access to GPS satellites, as in the case when the train moves through the tunnel.

Each of the stationary blocks 2190 sensors and mobile units 2192 sensors may be at least part of the sensor data to create an "event". The event may contain a minor event or a major event. Insignificant event may indicate that there has been no incident (such as damage) to tell about it. A significant event may indicate that there occurred or occurs an incident, such as damage that occurred or occurs on the section of track the train.

Stationary units 2190 sensors and mobile units 2192 sensors can contain one of the following or both: (1) collecting information to determine whether the accident; and (2) the ability to do one or more d�isti, based on the determination of whether an incident. In particular, the memory in one or more stationary units 2190 sensors and mobile units 2192 sensors may include one or more rules define various types of accidents, based on data produced from one or more sensors. Or, the memory in the stationary blocks 2190 sensors and mobile units 2192 sensors may include one or more lookup tables to determine the different types of accidents, based on data produced from one or more sensors. Additionally, inpatient units 2190 sensors and mobile units 2192 sensors may have the ability to take one or more actions based on the determination of whether an incident.

In addition to stand-alone operation, the electronic components on the network rail transportation can work together as part of a distributed intelligence network rail. For example, inpatient units 2190 sensors and mobile units 2192 sensors can share data or share computing power, in order to determine whether the incident, and to undertake one or more measures based on the determination of whether an incident.

Operation, in particular, contain: (1) the event to be dispatched to the incident on the bus 2147 �event; (2) the event to be dispatched to the incident, along with any recommended action on the bus 2147 events; and (3) the adoption of measures to change the status of one or more sections of the network rail transportation or one or more vehicles that transport goods by network rail. For example, inpatient units 2190 sensor can control one or more arrows in the network rail (as in the case of redirection graph on a separate track, opening the way with one-way traffic to travel in different directions, etc.). Or, inpatient units 2190 sensors can modify the parameters of one or more sensors on the network rail (for example, sensors to increase the sensitivity of their testimony, the sensors team to conduct more frequent reading, etc.). As another example, the stationary blocks 2190 sensors and mobile units 2192 sensor can control one or more means of transport manufacturing transport by rail perevodom. For example, the locomotive may be able to remote command control, whereby the locomotive may be able to receive the wirelessly transmitted commands to control one or more functions of the locomotive. One or more �ucciani, which may contain a command control can be, in particular, the speed of the locomotive, the alarm (or other type of noise), and the inclusion of light (or other type of visual indication). The receiver of the locomotive may take the command, and the processor of the locomotive can control one or more functions of the locomotive based on the command (such as a change in engine operation).

Network rail transport may include distributed intelligence. As discussed above, various inpatient units 2190 sensors and mobile units 2192 sensors within the network rail transportation may contain further functionality, including the possibility of additional processing/analytical analysis and database resources. The use of this additional functionality within the various mounted units 2190 sensors and mobile units 2192 sensor network rail transportation allows you to have a distributed architecture with centralized management and application management and network performance. For reasons of functionality, performance and scalability, network rail, containing thousands of mounted units 2190 sensors and mobile units 2192 sensors can include distributed processing, manage�data governance and communication between processes.

Non-operating data and operating data may be directly associated with the stationary units 2190 and mobile data units 2192 data. Stationary units 2190 and mobile data blocks 2192 data may additionally contain components of network rail, responsible for the ability to monitor network rail transport at different sites. Stationary units 2190 sensors and mobile units 2192 sensors can provide three primary functions: the collection of operational data and stored in the distributed storage of field data collection non-operating data and their archiving; and local analytical processing based on real-time (e.g. half a second). Processing may include digital signal processing, detection and classification, including the processing of the event stream; and transmitting the results of local processing systems and devices, and systems at the center 2116 operations management. The connection between stationary units 2190 sensors and mobile units 2192 sensors and other devices in the network rail transportation may be wired, wireless or combination of wired and wireless connections. The electronic element can transfer data, such as operating/non-operating data or d�record of events, in the center 2116 operations management. The routing device may transmit the transmitted data for bus operating/non-operating data or on the event bus.

One or more types of data may be duplicated in the electronic element and the center 2116 operations management, allowing, thus, the electronic element to operate independently, even if the data network to the center 2116 operations management is not functioning. Using this information (connectivity) stored locally, analytical analysis can be done locally, even if the communication line with the center 2116 management of the operations is not valid.

Similarly, operational data may be duplicated in the center 2116 management operations and electronic elements. These sensors and devices related to a specific electronic element, can be collected and the most recent measurement results can be stored in this data store in electronic element. The structure of the data warehouse operational data can be the same and hence the connection of the database can be used to provide direct access to data that resides on the electronic element, through the operational data store in the center 2116 operations management. This provides many advantages, including to facilitate�their replication data and provide analytical data analysis, which is more sensitive to time to occur locally and without confidence in the availability of communication outside of the electronic element. Analytical analysis level data center 2116 operations management may be less time-sensitive (because the center 2116 operations management can usually explore archival data to discern patterns that are more of predictive than reactive), and may be able to work on problems of a network, if available.

Finally, archival data can be stored locally in the electronic item and a copy of the data can be stored in the center 2116 operations management. Or, database connection can be configured on the repository instance in the center 2116 operations management, providing management center operations access to data in individual electronic elements. Analytical analysis of electronic elements can be performed locally in the electronic element using the local datastore. Specifically, the use of additional intelligence and storage capacity of the electronic element electronic element to analyze and update themselves without input from the Central organization.

Alternative, archival/joint analytical analysis can also be done at the level of the center 2116 management of the operational�s, by accessing data on the local electronic copies of elements using database links.

Additionally, for data analysis and/or events can be used different analytical analysis. One type of analytical analysis may include spatial visualization. The spatial visualization ability or visual-spatial ability are ability to manipulate two-dimensional and three-dimensional figures. Spatial visualization can be performed using one or more electronic components, or may be performed by a Central organization. Additionally, spatial visualization can be used with the set industry networks, including enterprise networks energy networks and transport.

In one example, during operation of the data 2508 events can be created for each mobile unit 2192 sensors. Data 2508 events can be transmitted to the main cell block 2504 sensors. Main cell block 2504 sensors may transmit event data using wireless technology from the gateway to the center 2116 management of the operations for processing through a gateway 2194. In alternative examples, each car is 2400 may include a corresponding gateway 2194, allowing the front�AMB data directly from mobile sensors unit wagon 2400. This allows the 2400 cars to communicate if they are not connected with motor car 2502, such as those that are in the train depot to transfer data 2508 events that should be taken by center 2116 operations management. In other alternative examples, each railroad depot may have one or more stationary units 2190 sensors and gateway 2194 to connect with there cars 2400 and transmit any data 2508 events. Similarly, the stationary blocks A and 2190 In sensors can convert the sensor data into the data stationary sensors and events through such inter-network interface (s) 2194 to broadcast such information to the center 2116 management of operations.

As described above, the network shown in Fig.24A-C, may also allow for a distributed analysis so that the data 2508 events were processed in stationary blocks A and B sensors and the home mobile unit 2504 sensors. Such processing may allow to analyze any problem and provide a solution or action plan. This solution can be transferred and can be used for automatic train control 2500 all capacities, since the train 2500 is arranged to permit or prevent operators-people�th, to control train 2500. The solution can also be transferred to the center 2116 operations management to allow you to remotely perform actions on the confirmation of the solution and, accordingly, to implement the solution.

Fig.26A-C shows the block diagram of the implemented architecture INDE associated with a network of trains, such as the commuter train. The network of electric trains can contain one or more trains that can be powered by overhead electric lines or third rail. In one example, the train 2600 may contain one or more cars of 2602. Each car can be powered individually from an external source (e.g. from the third rail or overhead line) or from internal sources (e.g., battery or fuel cell). Each car can have one or more mobile units 2192 sensors. Each mobile unit 2192 sensors can detect various States associated with different preset parameters of the train 2600.

In the example shown in Fig.26A-C, electric 2600 can be powered by the contact rail 2604. Conductor rail 2604 may be connected to one or more stationary units 2192 sensors that can monitor the power flowing through the conductor rail 2604. Stationary modules 2190 sensors can determine the ISP�javnosti railway system and pass any events associated with abnormal, undesirable condition or status tests in the form of event messages. Event messages can be transmitted to the gateway the 2194, so they took center 2116 management of operations.

Every electric car 2602 may include one or more mobile units 2192 sensors. One of the mobile units 2192 sensors can serve as the main mobile unit sensors, such as the main cell block 2504 sensors. Mobile units 2192 sensors can collect information related to the respective carriage in a form similar to that discussed with reference to Fig.25A-V. Main mobile unit with sensors for electric 2600 can transmit event messages created by other mobile units 2192 sensors, Central organisation through inter-network interface 2120.

Fig.27A-C shows a block diagram of the architecture INDE applied to the network of road transport, highways, such as that used in the industry of transportation. In one example, one or more mobile units 2192 sensors may be contained in the cargo containers 2700, such as those that are transported by trucks 2704 with a diesel engine. Each mobile unit 2192 sensors may be similar to those mobile units 2192 sensors discussed with reference to Fig.2A-C. Each mobile unit 2192 sensors can detect different condition of cargo containers 2700 and pass them through the built-in firewall interface 2194 in the center 2116 operations management. Stationary units 2190 sensors can be distributed by means of production of the consumer, allowing you to check the load, using the connection between stationary units 2190 sensors and mobile units 2192 sensors. Mobile units 2192 sensors can be used for tracking cargo, cargo containers, detection of theft/vandalism and any other appropriate use, as described with reference to Fig.24A-25.

Fig.28A-C shows the block diagram of the implementation of the complete architecture INDE applied to a network of cars that can be fueled with gasoline, electricity, hybrid fuel, biofuel or fuel by any other suitable means. In one example, the vehicle 2800 may include one or more mobile modules 2192 sensors, allowing you to control various modes of the vehicle 2800. Each vehicle may contain gateway 2194 or to communicate via external gateway 2194 to transmit event data directly to the engine 120 INDE or other mobile units 2192 sensors. �Adobe other examples discussed, mobile units 2192 sensors can include distributed intelligence that can perform analytical analysis associated with the vehicle, or may do so through interaction with Core 2120 INDE. Stationary units 2190 sensors may be used for communication with mobile units 2192 sensors, making it possible to estimate the vehicle 800 having a nearby mobile unit 2192 sensors for communication with stationary blocks 190 sensors. Stationary units 2190 sensors may include or share gateway 194, allowing you to transfer event data to the Kernel 2120 INDE, or can transfer them directly to the engine 120 INDE. Stationary units 2190 sensors can be implemented by companies renting vehicles, companies which sell lots of cars, or individual owners to receive event data associated with the status and/or location of the vehicle 2800.

Fig.30 presents an example of a system 2000 INDE, which can be controlled remotely, as shown in the block diagram. In place of 3000 administration 2002 core network can be installed as needed to support subscribers INDS for a particular industry. In one example, the subscriber 3002 may request the use of a variety of industries, such as railway, auto�air and air traffic. The system 2000 may be INDE block, allowing the adding of a large number of types of industries, or, in alternative examples, new subscribers. The party not connected with electric power, can manage and maintain the software for one, some, or all systems 2000 INDE, as well as apps that are downloaded from the management of INDS that should be used for system end-points, 2006 and system infrastructure 2008. To facilitate communication, can be used services with high bandwidth and low latency, such as the network communication 3004 (e.g., MPLS or other WAN), which can reach a subscriber centers operations of public service companies and also places control INDS.

Although the present invention has been shown and described in relation to preferred variants of implementation, it is obvious that in addition to those mentioned above can be made certain changes and modifications based on the basic features of the present invention. In addition, there are many different types of software and hardware implementation that may be used in the practical implementation of the invention and the invention is not limited to these examples. The invention has been described with reference to acts and symbolic p�of zestawienie operations performed by one or more electronic devices. Also it should be understood that such acts and operations include the manipulation by the processing unit of the electronic device for electrical signals representing data in a structured form. This manipulation transforms the data or maintains them in the cells of a memory system of the electronic device, which re-configures or otherwise alters the operation of the electronic device by a way that is well understood by specialists in this field of technology. Data structures that store the data are physical memory locations that have particular properties defined by the data format. Although the invention described in the foregoing context, it does not mean that it should be limited, as specialists in the art should understand that the steps and operations may also be implemented by hardware components. Accordingly, the intention of the Applicants is to protect all variations and modifications within the valid scope of this invention. It is understood that the invention is defined by the following formula of the invention containing all of the equivalents.

1. The architecture of the intelligent network to facilitate communication with a Central org�the organization, the management of the branch network that contains:
a plurality of sensors and components industry network, configured to generate operational data and event data in the branch network;
operating the bus associated with the plurality of sensors and components industry network, while operating the bus is configured to receive operational data and transmitting operational data from the Central organization, and operational data contains the measurement results in real time at least one of the sensor or component industrial networks; and
event bus associated with the plurality of sensors and components industry network, wherein the event bus configured to receive data events and data events in the Central organization, and the data bus is separated from performance tyres, event data differ from the results of measurements in real time, are derived from them and contain at least one analytical definition based on at least one measurement result in real time
the architecture of the smart grid is capable of
transmission of operational data through the service bus, but not via the event bus, and
send the event data via the event bus, but not through exploitation�ion bus.

2. The architecture of the intelligent network according to claim 1, in which the branch network contains a network of transportation.

3. The architecture of the intelligent network according to claim 2, in which the transport network contains a network of rail traffic.

4. The architecture of the intelligent network according to claim 1, in which the transport network contains a network of road freight transport.

5. The architecture of the intelligent network according to claim 1, further comprising a router for the analysis of at least part of the received data and data direction in operating the bus, or in the event bus.

6. The architecture of the intelligent network according to claim 1, in which the router is configured to analyze at least one header in the data to determine whether to send data in operating the bus, or in the event bus.

7. The architecture of the intelligent network to facilitate communication with a Central entity managing a branch network that contains:
the system infrastructure that contains:
many stationary sensors, configured to detect at least one aspect relating to the branch network and generation infrastructure data characterizing said at least one dimension;
at least one unit of analysis of the infrastructure, made with who�agnosto receive data infrastructure and receive data endpoint from one or more mobile sensors, attached to a mobile unit in the branch network, and the unit of analysis of the infrastructure being configured to generate event data based on the data infrastructure and data endpoint;
operating the tire associated with multiple stationary sensors and the analysis module infrastructure, and operational bus configured to receive data infrastructure and data endpoints and data infrastructure, and data endpoint of the Central organization, the data infrastructure and data endpoints contain at least one measurement result in real time at least for part of the branch network; and
event bus associated with the analysis module of the infrastructure, and the event bus configured to receive data events and data events in the Central organization, and the event bus is separated from performance tyres, event data differ from the results of measurements in real time, are derived from them and contain at least one analytical determination in respect of activities of the branch network, based at least on the designated one measurement result in real time;
the network core is arranged to receive data events exclusively through the event bus and generating commands for DOS�ve data events, the events included in the event data contain undesired or abnormal conditions arising in the sectoral system;
the architecture of the intelligent network is arranged to send a command to the endpoint containing at least one of the mobile sensors that generate data endpoint, the execution of which causes the mobile unit branch network in response to an undesirable or abnormal condition.

8. The architecture of the intelligent network according to claim 5, in which the router is located in the Central organization.

9. The architecture of the intelligent network according to claim 1, in which operating the tire is further configured to transmit non-operating data containing operating parameters, and/or health status of assets, and/or data loading.

10. The architecture of the intelligent network according to claim 1, wherein the plurality of sensors includes:
mobile sensors attached to mobile units of the branch network and is arranged to generate data of the endpoint; and
stationary sensors is arranged to detect at least one aspect in terms of infrastructure industry network and generate data infrastructure that characterize the mentioned at least one aspect.

11. Architecture and�tellectually network according to claim 10, in which the stationary sensors include the memory and the rules stored in the memory, wherein the stationary sensor is additionally configured to receive data endpoint and run rules to determine event data based on the data infrastructure and data endpoint.

12. The architecture of the intelligent network according to claim 1, in which operating the tire is capable of:
filter the set of event streams for interpreting the plurality of event streams in accordance with at least one event; and
to send a interpretation of a plurality of event streams at least in the Central organization.

13. The architecture of the intelligent network according to claim 1, further comprising:
a server associated with a service bus and an event bus and is arranged to receive and store operational data, wherein the server is arranged to:
analyze operational data in respect of at least one rule;
to generate at least one event based on the mentioned analysis; and
to send the mentioned at least one event by at least one of the sensors and components industry network "self-healing" within at least one segment of the industry network.

14. Architecture with intellectual�ti p. 13, in which the server is located in the Central control center, and mentioned at least one event triggers a change in the work of the Central control center.

15. The architecture of the intelligent network according to claim 13, in which the server further configured to generate a work order for transmission to the Central organization.

16. The architecture of the intelligent network according to claim 7, in which the event includes a message that is also sent to organizations that have mobile units.

17. The architecture of the intelligent network according to claim 16, wherein the alert includes a security message, which notifies you of attempted theft or vandalism.

18. The architecture of the intelligent network according to claim 7, in which the stationary sensors include memory and rules stored in the memory, wherein the stationary sensors made with the possibility of implementation of rules for determining events based on the data infrastructure and data endpoint.

19. The architecture of the intelligent network according to claim 7, in which the branch network is the railway network, and the mobile units contain separate railway cars.

20. The architecture of the intelligent network according to claim 19, in which the stationary sensor is additionally configured to control one or more arrows on the section of railway CoE�I.

21. The architecture of the intelligent network according to claim 19, in which the stationary sensors made with the possibility of modifying one or more parameters of one or more other sensors of the railway network.

22. The architecture of the intelligent network according to claim 19, in which at least one of stationary sensors or mobile sensors being configured to control one or more cars moving within the rail network.

23. The architecture of the intelligent network according to claim 19, in which at least some of the stationary sensors include detectors of faults, made with the ability to detect potentially unsafe condition of the car.

24. The architecture of the intelligent network according to claim 7, in which the branch network is a network of road freight transport, and mobile sensors attached to cargo containers for tracking cargo containers.

25. The architecture of the intelligent network according to claim 24, in which the stationary sensors distributed over the production means of the user and configured to receive event data from stationary sensors.

26. The architecture of the intelligent network according to claim 18, in which the event bus is additionally made with the possibility of communication with stationary sensors for receiving event data from with�ationary sensors.

27. A method of transmitting data to a Central organization that manages the branch network, the method contains the stages at which:
transmit at least partly wirelessly to a Central organization operational data for operating the bus, and operational data received from various sensors and components industry networks and contain at least one measurement result in real time at least one sensor or component industry networks; and
transmit at least partly wirelessly to the Central organization of the event data on the event bus, the event bus is separated from performance tyres, event data taken from at least some of the plurality of sensors and components industry networks and different from the measurement results in real time, wherein the event data further comprise at least one analytical determination in respect of activities of the branch network, based on the said at least one measurement result;
while operational data are transmitted by operating the bus and do not pass on the event bus; and
event data is passed via the event bus and are not passed on operating the bus.

28. A method according to claim 27, further comprising stages on which:
analyze when POM�soup of the router for at least a portion of received data; and
sent using the router mentioned operational data in the tire or in the event bus on the basis of the analysis referred to at least part of the received data.

29. A method according to claim 27, in which operating the tire is further configured to transmit non-operating data, and non-operating data contains at least performance and/or health status of assets, and/or data loading.

30. A method according to claim 27, further comprising stages on which:
perform using the event bus filtering to many threads for interpreting the plurality of event streams in accordance with at least one event; and
sending by the event bus, the interpretation of a plurality of event streams in at least one of a plurality of sensors and components industry network.

31. A method according to claim 27, further comprising stages on which:
accept and store operational data through a server associated with a service bus and an event bus.
analyze with the server performance data against at least one rule;
generating with the server at least one event based on the mentioned analysis; and
send with the server mentioned at least one event at �'ere one of the sensors and components industry network "self-healing" within at least one segment of the industry network.

32. A method according to claim 31, in which the server is located in the Central control center, wherein the method further comprises a stage on which
start with the server change work center Central office on the basis of the mentioned at least one event.

33. A method according to claim 31, further comprising a stage at which generate a work order for transmission to the Central organization.



 

Same patents:

FIELD: radio engineering, communication.

SUBSTANCE: group of inventions relates to communication and can be used for terminal buffer state reporting (BSR). A terminal includes buffer state report table; at least another extended buffer state report table; a table selector unit configured to select a table from a buffer state report table and an extended buffer state report table; an index determination unit configured to obtain an index from a table in accordance with the amount of data in the terminal buffer; and an index sender configured to send an index to a base station, wherein the table selector unit is configured to select a table in accordance with the indication in signalling for establishing a radio resource control (RRC) connection received from the base station.

EFFECT: extending a BSR table for adaptation to a new maximum buffer size.

10 cl, 14 dwg

FIELD: electricity.

SUBSTANCE: invention relates to the field of electrical engineering and may be used in electric power systems. Smart electric power system intended for improvement of control for utility system includes sensors at different sections of the above utility system with use of data transfer technologies and computer technology such as auxiliary bus structures in order to modernise the electric power system so that it operates effectively and reliably and to support additional services for consumers. The smart electric power system can include a smart distributing device in the utility system (separate from the control centre smart tools) that consists of units generating data at different sections of the electric power system, analyse generated data and modify operation of the respective section automatically.

EFFECT: improved control of the power supply networks.

46 cl, 37 dwg

FIELD: radio engineering, communication.

SUBSTANCE: system for transmitting a file from multiple sources in instant messaging (IM) comprises a sender IM terminal and a receiver IM terminal connected to each other through a network to exchange data; wherein the receiver IM terminal is configured to search for replicas of a file according to file information sent by the sender IM terminal, and when at least one replica is found, to receive the file from at least two file sources by using a multi-source transmission mode, wherein the at least two file sources comprise the sender IM terminal and a file source of the at least one replica.

EFFECT: faster file transmission and high degree of bandwidth utilisation.

16 cl, 8 dwg

FIELD: information technology.

SUBSTANCE: method involves receiving and caching streaming media data carried by real-time transport protocol (RTP) packets through a streaming media session; sorting and framing the cached RTP packets; generating a file and writing framed data frames into the generated file. A system for downloading streaming media data has a streaming media server and a client terminal. The streaming media server is used for transmitting streaming media data carried by RTP packets in streaming media sessions; the client terminal is used for receiving and caching the RTP packets, sorting and framing the cached RTP packets, and generating a file and writing framed data frames in the generated file.

EFFECT: high quality of displayed information.

12 cl, 3 dwg

FIELD: radio engineering, communication.

SUBSTANCE: coupled communication lines, which include multiple communication line components which are coupled together, are connected to realise communication over coupled communication lines using a bandwidth which is available for communication line components. A cross-switching functionality determines if the received communication traffic should be directed to one or more of the local area communication network and connected coupled communication lines. The received communication traffic is redirected according to said determination. Local area communication networks can include ring networks, linear networks or both. In some versions, coupled communication lines and communication lines between nodes in a local area communication network are coupled with a DSL line.

EFFECT: wider coverage of DSL service while maintaining bandwidth.

48 cl, 9 dwg

FIELD: information technology.

SUBSTANCE: techniques for mapping availability management (AM) functions to software installation locations are described. An availability management function (AMF) can look up a component type and determine software associated with that component. For a selected AMF node, the AMF software entity can then determine a pathname prefix associated with that software. The pathname prefix can then be used for various AM functions, e.g., realisation of a new component or service unit.

EFFECT: realisation of a component on a remote node based on a software identifier.

26 cl, 7 dwg

FIELD: information technology.

SUBSTANCE: address is generated for information which must be transmitted and this address is sent through a transmitting unit to a receiving unit; and the receiving unit receives the information from the transmitting unit in accordance with the received address. The invention also discloses a system for rendering information transmission services and a terminal.

EFFECT: cheap information transmission services, high rate of successful attempts at transmitting information.

27 cl, 7 dwg

FIELD: information technologies.

SUBSTANCE: system comprises subsystem of services promotion arranged with the possibility to send information on service stored in subsystem of services promotion into client subsystem through instant messages. Besides client subsystem is arranged with the possibility to receive information on service sent by subsystem of services promotion and to display information on service. Besides subsystem of service promotion is available in the list of user contacts in client subsystem.

EFFECT: improved efficiency and effectiveness of services provision.

17 cl, 2 dwg

FIELD: information technologies.

SUBSTANCE: method of communication is proposed between client and server side applicable in communication system made of client, server side and coupling facility between client and server side; method includes the following stages: establishment of dedicated channel between client and server side through open port of coupling device; establishment (if the main applied subsystem of client interacts with target server on server side) of logical channel between the main applied subsystem and target server based on dedicated channel, and also execution of communication along logical channel.

EFFECT: simplified establishment of connection.

22 cl, 2 dwg, 3 tbl

FIELD: physics; communications.

SUBSTANCE: invention relates to a method and device for accessing message memory of a communication module in modes of entering data into message memory or extracting data therefrom. The method of accessing message memory of a communication module in the said modes involves entering data into the corresponding main buffer memory and switching between modes of accessing the main buffer memory and shadow memory with possibility of entering next data into the shadow memory and simultaneous extraction from the main buffer memory already entered data in a specified direction. The message memory is connected to a buffer memory unit. Data are transferred in the first direction - into the message memory, and in the second direction - from the message memory. For data transferred in the first direction, the buffer memory unit has an input buffer, and an output buffer for data transferred in the second direction. Each of the said buffers is divided into two parts: main buffer memory and the associated shadow memory.

EFFECT: optimisation of the process of transferring data between the processor of user equipment and message memory with relation to transfer rate and providing data integrity.

15 cl, 12 dwg

FIELD: electricity.

SUBSTANCE: invention is intended for successful automatic reclosure of the main circuit breaker (MCB) in the line without intermediate fault close-ins. Technical result lies in expansion of functionality by receipt of data on successful automatic reclosure of the MCB in the line without intermediate fault close-ins. According to the suggested method since occurrence of fault current surge the first countdown is started, which is equal to the delay time of the MCB protection actuation at that monitoring presence of fault current, when fault current disappears upon completion of the first countdown then the conclusion is made on the MCB closure; since the first countdown is over the second countdown is started, which is equal to the total delay time for all cycles of the MCB automatic reclosure, and sounding pulses are sent to all the line wires with a certain periodicity and the line parameters are defined upon disconnection of the fault current by identification of all reflection points and calculation of distances up to these points and by their comparison with parameters of the normal mode received in similar way in absence of the fault current; when the parameters do not coincide the signal is sent to the MCB automatic reclosure and the signal will be valid till the compared parameters are matched, and if it takes place before completion of the second countdown then delivery of sounding pulses is stopped, the prohibition is lifted and the signal is start foe automatic reclosure of the MCB.

EFFECT: when using the above method the data may be received on successful automatic reclosure of the main circuit breaker in the line without intermediate fault close-ins.

2 dwg

FIELD: electricity.

SUBSTANCE: when voltage and operating current disappears and no short circuit is available in the line of the main circuit breaker countdown is started for automatic reclosure delay time of the main circuit breaker (MCB). Voltage appearance and surge of the operating current is monitored and when its appears at ending of the delay time countdown the conclusion is made about spurious tripping and successful automatic reclosure of MCB. When using the suggested method data on spurious tripping and successful automatic reclosure of MCB may be obtained for the ring network line.

EFFECT: expansion of functionalities by receipt of data on the method of control of spurious tripping and successful automatic reclosure of MCB in the ring network line.

2 dwg

FIELD: electricity.

SUBSTANCE: invention is used in the field of power engineering. According to the method when the first surge of short-circuit current appears in the main source line time of its flow is measured, since the moment of short-circuit current switching off the countdown is started for delay time of the network reserve switching on, at that in the line of reserve power supply source the second current surge is controlled and if at the countdown ending a surge of operating current appears with value defined by load of the reserved section in the line of the main power supply source and time of the first surge flow is equal to the delay time of actuation for the main circuit breaker in the line of the main source then conclusion is made that the main and sectionalising circuit breakers are switched off and the network reserve is switched on successfully when the line section between switched off switches is damaged. When the second surge of short-circuit appears, which is cut off in delay time for actuation of the network reserve protection with speed-up and the time of the first surge flow is equal to the delay time for actuation of the sectionalising circuit breaker then conclusion is made about switching off of the sectionalising circuit breaker and unsuccessful switching on of the network reserve switch at damage of the line section of the main source placed adjacent to the network reserve switch.

EFFECT: enlarging functional capabilities of the method.

3 dwg

FIELD: electricity.

SUBSTANCE: since voltage supply to the line of the main power supply source a countdown is started, and it is equal to delay time for tripping of network station switch of automatic load transfer. In the line of the main power supply source increase of operating current is monitored, while in the line of the reserve power supply source its decrease is monitored, and these values are defined by reserved load in the line of the main power supply source; when it does not occur then conclusion is made about trip failure of network station switch of automatic load transfer at restoration of normal operation of the ring network.

EFFECT: enlarging functional capabilities of the method.

2 dwg

FIELD: electricity.

SUBSTANCE: reduction of working current is monitored in the line of the primary power source per a value defined by the sectional load in the line adjacent to the islanding system of the automatic switchover to reserve source (ARS). Upon the time required for actuation of the ARS islanding system it is expected that working current in the reserve power source is increased per the value it was decreased in the line of the primary power source; when this increase is observed the conclusion is made about automatic switchover of the mains reserve upon activation of sectionalising disconnector of the islanding system in the ring network line. The suggested method allows receiving data on switchover to the reserve source upon activation of sectionalising disconnector of the islanding system in the ring network line.

EFFECT: expanded operating performances.

2 dwg

FIELD: electricity.

SUBSTANCE: since occurrence of fault current surge the countdown is started, which is equal to the delay time of the MCB protection actuation at that monitoring presence of fault current, and when fault current disappears upon completion of the above countdown then the conclusion is made on the MCB closure; upon disconnection of fault current the parameters are measured in the line by sounding pulses sent to all the line wires, the time of signals passing to all reflection points and distances are measure and the parameters are compared with parameters of the normal mode received in similar way in normal operating conditions, and when upon disconnection of fault current till completion of the countdown the parameters are different from the parameters in normal mode, the conclusion is made that short circuit is not self-repaired, the prohibition is set for automatic reclosure of the MCB and measurement of the parameters in the line and their comparison with the normal mode parameters is continued, and when at any moment before ending of the protection operation delay time with speedup plus the MCB switchover delay time for the second cycle the compared parameters are similar, the conclusion is made that short circuit is self-repaired, the prohibition signal is lifted and when at the moment of completion of the MCB switchover delay time for the second cycle surge of operating current appears in the line, then conclusion is made about successful reclosure of the MCB in the line during the second cycle of automatic reclosure.

EFFECT: expanded functionalities due to prohibition of automatic reclosure of the MCB in the line during the first cycle with subsequent successful reclosure during the second cycle.

2 dwg

FIELD: electricity.

SUBSTANCE: according to the method since the moment of voltage appearance at transformer of the primary power source countdown is started of total time equal to delay time for switching of busbar disconnect switch on of the primary power source and delay time switching busbar sectionalising switch off at the substation, and when by the end of the total time countdown operating current consumed from the reserve power source is reduced per a value defined by the reserved load in the line of the primary power source, then the conclusion is made on switching of disconnect switch on and switching busbar sectionalising switch off at the double-transformer substation during recovery of normal power supply circuit of the ring network.

EFFECT: expanded operating performances.

2 dwg

FIELD: electricity.

SUBSTANCE: in case of emergency in the network pulse-time coded commands for switching off are set for non-essential consumers, the station operating in emergency mode to the isolated network section is selected, in switchgear with voltage 10(6)-20 kV at the transmitting end of the line passing from the selected station in case of emergency power circuit breakers are switched off for a short moment and switched on and power supply interruptions of different fixed duration are created at actuators related to this line of power consumers, in switchgear of a lower voltage level these interruptions are received as pulse-time coded commands and upon their identification power switches of non-essential consumers are switched off on a selective basis.

EFFECT: improved reliability of power supply for essential consumers.

2 dwg

FIELD: physics; control.

SUBSTANCE: invention relates to means of controlling an industrial network. A power system control centre designed for a power supply system maintains communication with multiple systems for collecting and processing metering data and multiple terminal systems. The power system control centre comprises a gateway layer and a kernel layer. The gateway layer includes multiple input connection procedures for communication with each of multiple source systems and multiple output connection procedures for communication with each of multiple target systems. The kernel layer comprises multiple kernel adapters, such that said kernel adapters perform one-to-one transmission of communication from the multiple systems for collecting and processing metering data, which generate commands, to the multiple terminal systems.

EFFECT: high reliability and operating speed when controlling a power system.

17 cl, 2 tbl, 8 dwg

FIELD: electricity.

SUBSTANCE: invention relates to electrical engineering, and namely to generation and distribution of electrical energy. The proposed electric power supply system implements a control method of different generation sources of electric energy, which are included in a local low voltage micro network, which use renewable and non-renewable energy sources with priority use of energy from renewable energy sources to provide a consumer with quality electric energy at minimum prime cost of electric energy generation.

EFFECT: proposed system of electric power supply to consumers includes an energy generation and distribution control system, local control modules, objects of generation on the basis of renewable and non-renewable energy sources, as well as a system of mutual exchange of electrical energy with the main electric networks of low, medium or high voltage.

1 dwg

FIELD: weapons and ammunition.

SUBSTANCE: method involves a computer unit and peripheral devices installed on a control object and interacting with each other via a communication channel by means of mutual exchange of control signals and a state in compliance with a protocol of exchange according to the software. The control object is made in the form of a movable combat robot-aided platform and provided with a control and matching unit that performs matching of levels of diagnostic signals of sensors of the movable platform and an on-board computer, as well as amplification of signals of the on-board computer, which in its turn is connected via the communication channel to a remotely located control unit of the computer, and their output to actuating devices of the platform.

EFFECT: improving platform control reliability.

9 dwg

Up!