CN112183991A

CN112183991A - Power plant data management method and system, electronic equipment and storage medium

Info

Publication number: CN112183991A
Application number: CN202011002046.9A
Authority: CN
Inventors: 叶兆渠; 司徒友; 苏俊妮; 周娟
Original assignee: Guangdong Power Grid Co Ltd; Dongguan Power Supply Bureau of Guangdong Power Grid Co Ltd
Current assignee: Guangdong Power Grid Co Ltd; Dongguan Power Supply Bureau of Guangdong Power Grid Co Ltd
Priority date: 2020-09-22
Filing date: 2020-09-22
Publication date: 2021-01-05

Abstract

The embodiment of the invention discloses a power plant data management method, a traffic control terminal, a central platform and a power plant data management system, wherein the method comprises the following steps: determining target business of a local power plant to be processed currently; and carrying out standardized management on the data of the target service based on a preset standardized processing flow corresponding to the target service. After the target service to be processed is determined, the target service data is managed according to the standardized flow corresponding to the target service, and compared with the prior art that the target service is processed in an offline mode such as a mail mode, a WeChat mode and a telephone mode, the service data is processed according to the standardized flow in an online mode, the purpose of managing the power plant service data in a standardized mode is achieved, and meanwhile the efficiency of service processing is improved.

Description

Power plant data management method and system, electronic equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of data processing, in particular to a power plant data management method, a power plant data management system, electronic equipment and a storage medium.

Background

At present, effective information system support is lacked between a local power grid and a local power plant, and offline modes such as mails, WeChat files, QQ files and telephone contact are mostly adopted during business exchange. However, as the services of the local power grid and the local power plant increase, the offline mode brings great inconvenience to the work, so that the work efficiency is low, meanwhile, various service data are not effectively standardized and are relatively disordered, the management, statistics and analysis of various service data are lack of an effective unified processing mechanism, and the unified standardized management of the power plant by the power grid cannot be achieved.

Disclosure of Invention

The embodiment of the invention provides a power plant data management method, a power plant data management system, electronic equipment and a storage medium, and aims to achieve unified and standardized management of a power plant by a power grid.

In a first aspect, an embodiment of the present invention provides a power plant data management method, which is executed by a traffic control terminal, where the traffic control terminal includes an image acquisition module, a signal lamp module, and a processor module; the method comprises the following steps:

determining target business of a local power plant to be processed currently;

based on the preset standardized processing flow corresponding to the target service, standardized management is carried out on the data of the target service

In a second aspect, an embodiment of the present invention further provides a power plant data management system, including:

the service determining module is used for determining the target service of the local power plant to be processed currently;

and the management module is used for carrying out standardized management on the data of the target service based on a preset standardized processing flow corresponding to the target service.

In a third aspect, an embodiment of the present invention further provides an electronic device, including:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement a plant data management method according to any embodiment of the invention.

In a fourth aspect, embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements a power plant data management method according to any of the embodiments of the present invention.

In the embodiment of the invention, after the target service to be processed is determined, the target service data is managed according to the standardized flow corresponding to the target service, and compared with the prior art that the target service is processed in an offline mode such as mail, WeChat, telephone and the like, the service data is processed according to the standardized flow in an online mode, the purpose of managing the power plant service data in a standardized manner is achieved, and meanwhile, the efficiency of service processing is improved.

Drawings

FIG. 1a is a schematic diagram of a three-level deployment of a plant data management system according to a first embodiment of the present invention;

FIG. 1b is a schematic diagram of a hierarchical architecture of a power plant data management system according to a first embodiment of the present invention;

FIG. 1c is a schematic diagram of a hierarchical development of a power plant data management system according to a first embodiment of the present invention;

FIG. 2a is a flow chart of a power plant data management method according to a second embodiment of the present invention;

fig. 2b is an effect diagram of a risk management and control task book entry interface in the second embodiment of the present invention;

FIG. 2c is a diagram illustrating the effect of the feedback risk implementation according to the second embodiment of the present invention;

FIG. 3 is a schematic diagram of a power plant data management system according to a third embodiment of the present invention;

fig. 4 is a schematic structural diagram of an electronic device in a fourth embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

Example one

In the embodiment of the invention, a power plant data management system is designed, referring to fig. 1a, the system adopts an application mode of three-level deployment and multi-level application, and the system is deployed at three levels of a network company, a provincial company and a regional company and applied at four levels of a network, a province, a region and a county. And the two-stage system realizes the longitudinal exchange of information through the service bus. And part of the intermediate calls can adopt an application mode of two-stage deployment and multi-stage application according to actual service requirements.

When the bottom layer of the system is realized, the following scheme is adopted:

the method adopts a B/S structure (Browser/Server, Browser/Server mode), a Service-Oriented Architecture (SOA) design and Architecture idea, an object-Oriented program development idea and an MVC standard multi-layer Architecture mode to complete the construction of the system background by a Java SSH framework which completely accords with the J2EE standard. In the aspect of a database, Oracle11g is adopted, Javascript is adopted as a client interaction language, and for the aspects of graphics and media, a large number of storage media in SVG technology and streaming media technology are adopted. Therefore, the expandability and the portability of the platform are high, and meanwhile, the system has a very good human-computer interaction interface and humanized experience.

The Server part of the whole set of system is deployed in main stream Server operating systems such as Windows Server 2003/2008, Red Hat Enterprise Linux, Unix and FreeBSD in a cross-platform manner; the client of the whole system can cross-platform operate on mainstream browsers such as Internet Explorer, Google Chrome, Mozilla Firefox and the like.

The system developed by the method enables users to easily complete various information processing through the browser, is simple and easy to use, is easy to deploy, greatly shortens the implementation period of the information system, saves the management cost, performs centralized management, unified maintenance and classified and ordered storage of information data, enables the system to be more convenient to maintain, upgrade and expand, can rapidly make corresponding system adjustment and change aiming at group enterprise combination and expansion, and greatly adapts to the requirements of the users under different environments and conditions.

For the service-oriented SOA architecture, the service-oriented architecture (SOA) is a component model, which connects different functional units (called services) of an application through well-defined interfaces and contracts between the services. The interface is defined in a neutral manner and should be independent of the hardware platform, operating system and programming language in which the service is implemented. This allows services built into various such systems to interact in a uniform and versatile manner.

With the wave of global informatization, the informatization industry is continuously developed and extended, a plurality of enterprises and individuals are deeply penetrated, and the SOA system architecture brings a new revolution to the informatization. The system developed according to the SOA idea has the following advantages:

balance initial old system investment (legacy initial investment): organizing the systems, software and hardware that have invested in the past, and if they can be reused equals to give them new value, it also reduces the cost and increases competitiveness for the organization. The SOA is independent of the platform, and the limitation of service application implementation is reduced. To integrate business partners of an enterprise into the "big" business system of the enterprise, there is no limitation on what technology is specifically adopted by its business partners.

Fast time-to-market: the reuse of services shortens the past organizational processes and provides services more quickly to approach the market. The SOA has the characteristic of low coupling, and business partners have low influence on the whole business system. Under the condition that the relationship between the enterprise and each business partner is changed continuously, the saved cost is more and more.

Reduction of expenditure (Reduce Cost): the repeated use of the service can reduce the development cost. Because of the cost of developing a new system, it is in large part more expensive than updating an old system. SOA has the advantage of being implementable in stages, in modules. The next step can be successfully carried out in one step, and the impact of implementation on enterprises is reduced to the minimum.

Reduced Risk (Risk identification): by means of SOA technology, the functions of the old system can be utilized to a great extent. With future developments it is not uncommon for systems to need to be upgraded or replaced.

The system developed by the SOA technology can extract functions and directly use the functions as service components for service calling for a new system. It should be noted that, in a system not developed by the SOA technology, development or data sharing can be performed again only, and in any way, the risk is extremely high. Therefore, the system developed by the SOA idea and technology can greatly reduce the risk of later expansion, upgrade and even generation.

Designing a database: oracle11g is the first database specifically designed for grid computing, and is the most flexible and cost-effective to manage enterprise information, and the key objective of using Oracle11g is to reduce management overhead and improve performance. Enhancement of Oracle11g includes enhancement of high availability, new Flashback capability, and support of rollback update operation; the security is enhanced, and a large number of users can be managed conveniently; enhancements in BI, including improved SQL capabilities, analytics, OLAP, data mining capabilities, etc.; the ability to store non-relational data is improved; the capabilities of the XML; enhancement of support for development ability, support for Bioinformatics (Bioinformatics).

Application development framework of SSH architecture:

the system is based on the SSH framework of the J2EE software which is most widely and stably used in the industry, is formed by integrating Struts, Spring and Hibernate according to respective application characteristics, and selects a framework combination which takes a Spring framework as a core and integrates the Struts and the Hibernate. The SSH composition framework is shown as including a presentation layer, a business logic layer, and a data persistence layer. The system can construct a robust, reusable, extensible and easily maintained Web application program by adopting a reusable, mature and stable SSH framework.

The Struts framework is a Web framework based on the MVC pattern. The MVC design Model is composed of 3 parts of a Model (Model), a View (View) and a Controller (Controller), and Struts is a free open source Web layer application framework and has high configurability. The Spring framework provides a lightweight enterprise business solution for building 'fast-assembly enterprise components'. On this basis, Spring also provides a solution that includes declarative transaction management, RMI or Web Services remote access service logic, and a persistent database that can be implemented in a variety of ways. The Hibernate framework is an excellent JAVA object persistence layer lightweight framework for open source code. The working principle of the method is that a mapping relation is established between JAVA domain objects and a database table through a configuration file, so that the aim of operating the database is achieved only by operating the domain objects.

The system layered decoupling is realized through the optimized combination of the 3 frames, on one hand, the clear division of the roles of the project group is facilitated, the development efficiency is improved, and the system development cycle is shortened; on the other hand, the system has good expansion capability and maintainability.

Page representation layer: the page layer is implemented by Struts, which is a framework based on the MVC model. The MVC Model divides a Web application into three components, namely a Model (Model), a View (View) and a Controller (Controller), the three components are independent and can work cooperatively, a universal control component ActionServlet receives an HTTP request from a client, the request is forwarded to a corresponding Action object according to a Struts-config

And a service logic layer: association and management of the assembly of business components is accomplished by Spring, a popular lightweight container that is an open-sourced and universally compatible, non-mandatory framework. The method reduces the coupling degree between service components to the maximum extent by using IoC (Inversion of Control, also called DI) and AOP (Aspect-Oriented Programming) applications and interface-Oriented Programming, and enhances the compatibility and extensibility of the system.

A data persistence layer: and performing lightweight object encapsulation on the JDBC by using an open source framework Hibernate, and associating a database table with an object to realize the optimization of database access performance and the common operation CRUD interacting with the database. Hibernate encapsulates the work of database access, transaction management, data caching and the like, and can greatly improve the development efficiency.

The SSH technical framework constructed by organically combining the three technologies not only can effectively improve the system development efficiency, but also has good improvement on the system safety, stability and robustness. The domain objects move among the layers, provide required data sources for the presentation layer, and provide objects for the persistence layer, so that the layers interact with each other in a loose coupling mode without considering the technical details of the lower layers, and further, a complete Web development framework is constructed.

Further, with a layered architecture design, referring to fig. 1b, which shows a schematic diagram of a system layered architecture, in combination with the above analysis of the SSH-based layered architecture in the SOA and J2EE development, an SOA-SSH layered architecture is proposed. The architecture is based on SOA and J2EE, so the architecture has the characteristics of both. In the J2EE system, EJB components or springs are usually used to implement the business logic layer, and in the SOA system, the business is based on services, so in this architecture, the components of the business logic layer are packaged into Web Service, Web Service is used as the Service provider of the SOA, springs are used as the implementation of the services, and simultaneously Enterprise Service Bus (ESB) technology is used to implement the Service mediation in the SOA, and a Service agent layer is added below the business layer of the J2EE system to encapsulate the specific calling code for the Service. The architecture adopts the ESB to play the role of an SOA service registration center, and the integration of heterogeneous systems can be realized by using the ESB.

Description of relevant parts in the architecture:

presentation layer: JSP/Html/JavaApplet is the implementation technology of the presentation layer, and is used for generating the Web page. A user accesses a Web page through a browser. Servlet Control in Struts is a controller part and is responsible for the combination of page layers and internal services and switching between pages. Xml file configuration is common.

And the service agent layer: the request handler of the service, which is used to interact with the service to add, update and query information into the system, is typically composed of a set of java classes. When writing the service calling code, the WSDL description file of the service is acquired from the service bus, and then writing is carried out according to the file.

ESB Enterprise service bus: and the middle layer between the service requester and the service provider performs centralized management on the service. Specific work in ESB: when the client sends a request message to the service bus, the request message is sent to the proxy service, and after receiving the service request, the proxy service sends the request message to the service through a series of message processing, and the service is further transferred to an external service provider.

And (3) a service layer: web Service is a provider of services, generated by stateless session beans, usually coarse-grained, corresponding to the business logic of an enterprise.

And (3) service component layer: the J2EE component responsible for implementing the business logic. And completing the development of the service component by Spring or EJB.

A persistence component: middleware between enterprise applications and relational databases, an excellent ORM tool. The business data is represented as an object in the memory, and is represented as relational data in the relational database, and persisting the object in the relational database requires object-relational mapping (ORM).

Database layer: and the relational database stores the enterprise data. Further, the SSH architecture is realized in a layered mode:

1) building of data persistence layer

The Persistence layer Persistence mainly completes data access, operates a database table at the bottom layer, uses a DAO component to package specific operation details, provides an interface for a business layer, and enables business logic to be separated from data Persistence. In Hibernate, the "O/R mapping" relationship of objects to tables, object attributes to table fields is done by configuring the corresponding XML file (. hbm.xml). When Hibernate runs, the XML mapping file is automatically read, and then Java classes are dynamically constructed according to rules specified by the file, so that the conversion of management data between a database and a Java program is facilitated. The access of the persistence layer is accomplished by the DAO component, which is described below by way of example as a channel organizational structure information table (Dchngroupmsg).

SSH is a composition mode of Struts + Spring + Hibernate, Struts realizes the combination of MVC and Spring responsible architecture, and Hibernate carries out data persistence. Referring to FIG. 1c, a block diagram of a system development hierarchy is shown. The structure meets the general business requirements, but the current increasingly complicated WEB2.0 development has a plurality of problems, and the following defects are mainly caused by summary:

the DAO and Service layer are easy to have unknown responsibilities, because according to the MVC logic, the Service code should be written in the Struts Action, but the Service layer is provided for the transaction. In order to implement a logically complete group of data operation Service logic, two layers (Service, Action) need to be involved for writing, and under the condition of judgment, in order to ensure complete transaction operation, a Service code needs to be moved to a Service layer for completion, but it is customary to invoke multiple services in a Struts Action to generate multiple transactions, and the Service data of the Service transaction invoked before the operation is performed when an error occurs is not rolled back when an Exception occurs.

When the returned data is needed for AJAX use, heavy use of JSON or XML is operated on. It is laborious to develop, and a section of the same service code may need to be rewritten once to use AJAX and XML, or judged by a flag in the same ACTION, and constitutes a worse destruction to the hierarchical structure. If the design is not good, a large amount of configuration is additionally added for using JSON and XML, and the development efficiency is seriously reduced.

Therefore, to overcome these shortcomings, a new hierarchy is made for the SSH architecture, sharing the service code. The development is simplified, and the combination with AJAX technology and MXL technology is enhanced. A more efficient development mode is provided.

The framework has the advantages that the Service codes uniformly realize the Ibusinessservice interface, so that the work can be finished only by calling a Service layer method through a plurality of relatively fixed Struts Action classes. The method comprises JSON format output, and XML output and WebService output call a Service layer method to complete functions. This allows separation of the service code and a great decoupling from the front-end framework.

Enterprise service bus ESB: is a set of infrastructure functions of a Service Oriented Architecture (SOA) implemented and supported by middleware technology, supports services, messages and event-based interactions in heterogeneous environments, and has manageability at an appropriate service level.

The ESB has a lightweight distributed deployment model, provides a service warehouse through a series of management of registration, release, flow and the like of the service, can organically combine the service from each system in the service warehouse according to business requirements, can eliminate technical difference among different applications, enables different application servers to operate in a coordinated mode, and achieves communication and integration among different services. With ESB, the SOA can only release its maximum value.

The ESB provides intelligent message brokering, dynamic delivery and translation, all of which support heterogeneous service endpoints ALSB integrated with service lifecycle management functions (including Service Level Agreement (SLA) enforcement for service registration, monitoring and definition of closed values) to provide an ideal SOA foundation for IT, which can achieve the following goals: time is saved by dynamically configuring integration between heterogeneous shared services; maintenance efforts are reduced by simple centralized service registration; cost is reduced by cost-effective service deployment and automatic configuration.

Through the bottom layer technology, a power plant data management system is finally constructed, and the power plant data management system provides an interface, a personal desktop management function, an alarm information function, a system management function, a log management function and a data management function.

Wherein, the interface comprises a horizontal interface and a vertical interface. And the transverse interface is used for realizing interconnection between applications in the transverse direction of the company and cooperation of business processes through interconnection between a general service bus based on the SOA architecture and an Enterprise Service Bus (ESB) of the company. The horizontal interconnection includes interconnection of the dispatch logs with the enterprise service bus of the company. And the vertical interface is used for service exchange between vertical interfaces, including 'data interaction' and 'process interaction'. The service interaction content comprises transfer report, power grid fault, equipment defect, equipment starting, log record query, duty query and the like. And designing a service interface provided by the system according to the business coordination requirement and the service requirement, and providing a basis for service realization and examination. Because the interface methods need to be called mutually when the interfaces are jointly dispatched, the access authorities of the corresponding ports of the servers of the two parties need to be opened before the joint dispatching.

In the desktop of the person, the upper right corner of the head navigation bar is highlighted, so that the instant reminding of to-do matters, system notifications and announcements is realized, the omission of related work is avoided, and the efficiency is improved. Specifically, personal desktop management: the method has the advantages that contents such as various notifications, backlog items and risk management and control measures related to users of individual users are expanded in a list form, types and numbers of various backlog tasks (mainly backlog information) are clearly displayed to the users, shortcuts of power plants are realized, and the users can quickly know the current individual work conditions of the power plants. And (4) warning information function: the device is mainly used for expiration reminding, for example, the device is checked for expiration and sends a short message to a related responsible person, or the device has a self-defined reminding function.

The log management system is mainly used for recording daily operation records of a power plant, is designed according to the principles of 'structured editing and narrative display', and consists of a background form and a display module. The background form only has an editing function and is not displayed to the outside; the display module automatically generates display sentences according to the background form information, and the display sentences cannot be edited.

Specifically, log management is divided into two functions of intelligent configuration and intelligent application. The system classifies each log, performs variable mapping one by one on the input elements presented on the HTML form, provides a configuration interface, and enables a user to freely configure log statements by clicking and dragging. The intelligent application function is provided for power plant workers recording logs, and is mainly completed by automatically generating JavaScript code segments contained in HTML through intelligently configured parameters, binding events such as OnChange, OnClick and OnKeyPress of HTML components and replacing and generating final log statements by utilizing an Eval mechanism of Javascript.

The system management is the management of user data, password modification, system notification, user role authority and the like. And whether the user can configure the authority of each module and process role according to the own authority or not can customize the own personalized system. Wherein the user roles include: office workers, system managers, allotment workers, relay protection and inter-distribution, transportation party branches and power plant personnel.

The data management function includes different functional units for implementing the power plant data management method provided in the present invention, and the specific method is as follows.

Example two

Fig. 2a is a flowchart of a power plant data management method according to a second embodiment of the present invention, where this embodiment is applicable to a power plant and a case of performing standardized management, and the method may be executed by the power plant data management system, and the power plant data management system may be implemented in a software and/or hardware manner and may be integrated on an electronic device. As shown in fig. 2a, the power plant data management method specifically includes the following steps:

s101, determining target business of the local power plant to be processed currently.

The service of the power plant is determined by classification of a local power grid, and illustratively, the service is a power plant ledger management service, a power plant risk management and control service, a power plant evaluation service, an operation order function management service and the like. The target service may be any one of the above, and after the target service to be processed is determined, S102 is executed to manage data of the target service.

S102, carrying out standardized management on the data of the target service based on a preset standardized processing flow corresponding to the target service.

In this embodiment, when the target service is a power plant ledger management service, a power plant risk management and control service, a power plant evaluation service, and an operation ticket function management service, the process of standardized management of target service data is detailed respectively.

Optionally, when the target service is a power plant ledger management service, based on a preset standardized processing flow corresponding to the target service, standardized management is performed on data of the target service, where the standardized management includes S01-S02:

and S01, acquiring the ledger information input by the personnel at the side of the power plant, and sending the ledger information to the corresponding power grid auditor for auditing.

The standing book information refers to information related to standing book equipment, for example, information of a power plant bus and a main transformer is included, and specifically, detailed information of a unit, the main transformer, the bus and protection can be included. Exemplarily, taking a main transformer ledger as an example, the entered ledger information at least includes: equipment type, name, model, voltage class, manufacturer, release date, etc. After the standing book information input by the power plant side personnel is obtained, the standing book information is sent to a power grid auditing personnel for auditing through a transverse interface of a power plant data management system, wherein the power grid auditing personnel can be selected as relay protection accountability. It should be noted that, because the power plant data management system is deployed at a point of a power grid company, and because the power grid company and the power plant use different local area networks, a file transmission and sharing channel is designed in advance, and a power plant worker can log in the system based on the file transmission and sharing channel and enter account information, that is, the account information is sent to the power plant data management system through the file transmission and sharing channel. Optionally, the file transmission and sharing channel is a VPN data channel, and a specific process of the power plant user accessing the system through the VPN channel is as follows: a power plant side user installs a VPNSSL component suitable for IE; a user at the power plant side opens a VPN login website and logins through a pre-distributed VPN account and a password; after logging in successfully, sending a short message verification code to the user account; after the verification of the short message verification code of the mobile phone is successful, the mobile phone enters a VPN workbench and then enters the system. It should be noted that, data interaction between plant-side personnel and grid personnel in the plant data management system is performed based on file transfer and a shared channel.

And S02, generating a scheduled inspection list plan based on the audited standing book information, and prompting corresponding authority personnel on the power plant side to complete scheduled inspection tasks based on the scheduled inspection list plan.

Wherein the scheduled inspection list plan at least comprises the following scheduled inspection tasks: the system comprises a scheduled check ledger task, a secondary valuing task, a scheduled check plan, a scheduled check report task, an equipment defect detection task, an equipment inspection task, an equipment scrap detection task, an equipment valuing management task and the like. After a scheduled inspection list plan is generated, prompting corresponding authority personnel on the side of the power plant to complete a scheduled inspection task based on the scheduled inspection list plan, and automatically reminding the next scheduled inspection of the equipment according to a scheduled inspection period of equipment classification based on the scheduled inspection list plan of the equipment and historical scheduled inspection conditions of the equipment in an optional real-time mode; and automatically generating a red-yellow-green light scheduled inspection alarm diagram of the equipment based on the comparison between the current time and the next scheduled inspection time of the equipment, for example, marking unexpired and expired by a yellow light or a red light respectively.

And the personnel on the side of the power plant executes corresponding scheduled inspection operation based on the scheduled inspection task in the scheduled inspection list plan. It should be noted that after each power plant side worker completes one vertex task, the detection result is recorded into the system based on the template corresponding to the scheduled inspection task. Illustratively, on the basis of the scheduled check ledger task, the staff of the power plant detects the ledger equipment, and inputs the detection result into the data management system of the power plant on the basis of the preset scheduled check ledger template. For another example, a person on the side of the power plant may perform various defect detections on the ledger equipment according to the equipment defect detection task, and enter various defect contents based on the defect detection template, for example, enter defect detection results according to indexes such as "belonging power plant", "defect number", "source", "level", "appearance", "location", "category", "cause", "status", and "elimination time".

It should be noted that the power plant data management system further provides an interface attachment transmission technical scheme, attachments are uniformly transmitted in a file stream mode, attachment names are sent in attachment nodes, and file streams are sent in attachment content nodes. In the case of multiple attachments, the attachment names are separated by semicolons, and no semicolon is added after the last attachment name. Each attachment content node comprises two nodes of attachment name and attachment flow. The 'attachment name' node stores attachment names, and the 'attachment stream' stores character strings of the Byte [ ] arrays of the attachments after being encrypted by base 64. For example, if a repair order application attachment needs to be sent, the attachment node is a repair order application attachment, and the node content includes a plurality of required attachments. The specific content of the attachment needs an attachment node + content composition, such as < repair order application attachment content >, a plurality of attachments have a plurality of < repair order application attachment content >, and each node contains corresponding < attachment name > and < attachment stream > content. Therefore, in an alternative embodiment, the plant-side personnel can also upload the scheduled inspection result to the system by uploading the attachment through the interface attachment transmission scheme.

Furthermore, for the existing ledger information, in order to facilitate later visual viewing and standardized management, a statistical chart is generated based on the ledger information, for example, the number of transformers, the capacity, the circuit breakers, the knob-type disconnecting switches, the power transmission lines and the like are counted, and the chart is generated according to unit, month and type multidimensional counting. Meanwhile, the icon export function provided by the power plant data management system exports the request to the application, and the system exports and stores the statistical chart to the local.

In the embodiment, standardized management of the power plant ledger data is realized through operations of S01-S02.

Optionally, when the target service is a power plant risk management and control service, based on a preset standardized processing flow corresponding to the target service, standardized management is performed on data of the target service, where the standardized management includes S11 and S12:

s11, issuing the risk control task book and the power generation plan recorded by the power grid operator to the power plant, enabling corresponding authority personnel on the power plant side to perform appointed operation based on the standard risk control task book and the standard power generation plan, and receiving the risk control measures and abnormal conditions fed back by the corresponding authority personnel on the power plant side.

The risk management and control task book is input by power grid transport personnel, and is specifically input according to a risk management and control task book template. Optionally, the entered information includes a risk name, a risk number, a risk level, a risk starting time, a risk removing time, an issuer, an issuing date, a required feedback deadline, blackout work content, and an attachment, and for example, referring to fig. 2b, an effect diagram of a risk management and control task book entry interface is shown. After the power plant is selected by the carrier, the task book is sent to the power plant. After the power plant signs for the condition, the risk implementation situation is fed back by the power plant. Specifically, the feedback information includes: action summary, attachment, feedback person, feedback time, contact phone, power plant name, responsible person. Exemplarily, see fig. 2c, which shows an effect diagram of a feedback risk implementation.

Further, the personnel at the side of the power plant also detect the abnormal conditions and feed the abnormal conditions back to the power grid side. Specifically, the content of the feedback includes: time of delivery, person of delivery, contact phone, etc.

Further, the power generation plan includes a daily power generation plan and a monthly power generation plan. Aiming at the daily power generation plan, after the daily power generation plan is input by a power grid operator, the system directly issues the power generation plan to the power plant, and personnel with corresponding authority at the side of the power plant can see the power generation plan. Specifically, the power generation plan is entered by the carrier based on a power generation plan template, and the entered information includes: the power plant name, the number, the execution date, the power factor, the voltage range, the daily on-line electricity quantity, the output number of every 15 minutes in 24 hours, the leader of a manager and the staff for compiling. The system provides a 'issuing' control, and responds to the trigger operation of the operator on the 'issuing' control to send out a power generation plan. After several persons with corresponding authority at the power plant side arrive at the power generation plan, the control of 'confirmation' provided by the trigger system is used for indicating that the power generation plan is received, and meanwhile, the person and the time for confirmation are fed back to the power grid side.

Further, a power generation curve is generated according to the time point and the output number in the power generation schedule data table. Wherein, the horizontal coordinate is: time point scales, 0-23.45, each 4 scales displaying a time mark (i.e., an hour). Longitudinal coordinates: the output number is divided into two types according to the integral output number, wherein the output number is 0-1 and 10-40, and the unit of the output number is 0.1 or 5. A data table is attached below the curve.

The monthly power generation plan is a set of daily power generation plans, and is convenient for inquiry and statistical analysis. Aiming at the monthly power generation plan, the system also provides a function of searching according to the name, the execution date and the like of the power plant and a function of issuing a power generation plan in batches.

S12, sending the received maintenance plan generated by the power plant side based on the maintenance template to relevant personnel for checking, and sending a checking result to the power plant side so that corresponding authority personnel of the power plant side can execute maintenance tasks according to the maintenance plan, wherein the maintenance plan comprises annual inspection, monthly inspection and temporary inspection.

Aiming at equipment maintenance management, the equipment maintenance management comprises a year maintenance plan, a month maintenance plan and a temporary maintenance plan. Specifically, a power plant initiates an equipment maintenance plan, and a transport party and related departments reply the plan; if the construction period changes, a series of business processes such as power plant application and scheduling approval are required.

Optionally, the annual maintenance schedule is imported into the year by the power plant based on a preset template. The imported information includes: the system comprises a serial number, a plan year, an execution scheduling unit, an application unit, a device subclass, a voltage grade, a power failure device, a construction period, a work type, work content, application work starting time, application work finishing time, a power grid risk grade, mode adjustment, influence evaluation and an applicant.

The monthly maintenance schedule is imported by the power plant based on a preset template. The imported information includes: the system comprises a serial number, a plan month, an execution schedule, an application unit, an equipment subclass, a voltage grade, a power failure equipment, a construction period, a work type, work content, an application work starting time, an application work finishing time, a power grid risk grade, mode adjustment, influence evaluation, an important user, a power protection measure, a risk control measure, a control section, switching operation, an equipment state, a pre-test expiration time, a scheduled inspection expiration time, a power failure equipment, remarks and an applicant.

The provisional maintenance schedule is entered by the power plant based on a preset template. The entered information includes: the system comprises an application unit, application time, contacts, a contact telephone, equipment names, overhaul contents, system requirements, an application period, an applicant, a unit person in charge and remarks.

The specific process is as follows: the side personnel of power plant select the fortune party, send the maintenance plan to by the fortune party after the repeated maintenance plan of wholesale, send back the power plant, send for the power plant, the information includes: power failure time, approval construction period, call receivers, reply time, mode requirements, special responsibility of a transport party and leadership of a dispatching center. Further, if the other people are required to fill in the reply opinions, the carrier selects the relevant people and sends the comments. And after filling in the wholesale advice, other personnel send back to the shipper so that the shipper can send the shipper to the power plant side.

Further, responding to a request for applying for the change of the construction period sent by a personnel on the side of the power plant during the maintenance period, and sending the request for the change of the construction period to a carrier personnel for auditing, wherein the request for the change of the construction period comprises the changed construction period, reasons and applicant. And the personnel of the transport party approve after receiving the construction period change request and feed back approval information to the power plant for filing, wherein the approval information comprises an approver, a dispatcher, a call receiver, remarks and the like. It should be noted that if the carrier personnel do not approve, the system will feed back the disapproved information to the power plant side.

Therefore, through S11 and S12, data interaction, collection and the like between the power plant side and the power grid side are carried out according to preset templates, and the purpose of managing the power plant data in a standardized mode is achieved.

Optionally, when the target service is a power plant evaluation service, correspondingly, based on a preset normalized processing flow corresponding to the target service, performing normalized management on data of the target service, where the normalized management includes S21-S22:

s21, obtaining operation behavior data recorded by a scoring main body on the basis of a preset scoring standard and a power plant side, scoring a power plant, and displaying the scoring result, wherein the operation behavior data comprises field operation behavior data or daily operation behavior data.

The scoring main body can be exemplified by a main network scheduling subsection, an operation mode subsection, an automation subsection, a relay protection subsection, a communication subsection, a comprehensive subsection, a distribution network scheduling subsection, a safety subsection and the like in a power grid company. Optionally, the scoring main body can perform daily scoring and field scoring on the power plant by taking the quarter as a dimension according to the evaluation item, the scoring basis, the checking method and the scoring method of the corresponding power plant to be scored. Illustratively, the evaluation item is 'normal operation information reporting', the scoring basis is 'XX power system power grid dispatching regulation', the checking method is 'related record, telephone recording and the like', the scoring method is 'incorrect information reporting', and the item does not score; the information is reported untimely and incompletely deducts 50% of standard score ". The field scoring is to record the field operation behavior data of the power plant and evaluate the field operation behavior data by comparing with the field evaluation behavior specification, and the daily scoring is to evaluate the daily work record (and the daily operation behavior data) of the evaluated object according to the daily evaluation behavior specification of the power plant. It should be noted that, scoring is performed according to a fixed scoring item, so that the obtained scoring data is normalized, and aggregation management is facilitated.

Furthermore, the system also provides a power plant self-evaluation function, and power plant personnel can evaluate the site and daily behaviors of the power plant personnel by self, give correction measures and upload self-evaluation results to the system.

Furthermore, after the system achieves the grading result, the grading result is displayed so that personnel on the side of the power plant can conveniently check the grading result. Optionally, the display is performed in the form of a score comparison table.

And S22, responding to a grading result complaint request submitted by the power plant side, and sending the grading result to a professional auditor for auditing.

If the power plant side has doubt on the scoring result, complaints can be made to cancel the scoring. As an optional implementation manner, a person on the side of the power plant can make a complaint request through the system and upload the certification material, so that after the system receives the complaint request of the scoring result submitted by the side of the power plant, the scoring result and the certification material uploaded by the side of the power plant are sent to a professional evaluator for re-auditing. And (4) each professional evaluator audits the complaint request, if the complaint reason and the materials are accurate, the scoring can be cancelled, and if not, the scoring result is kept and the audit result is returned.

In the embodiment, the system provides a scoring function, power plant scheduling evaluation management can be strengthened through the scoring function, and the power plant management level is improved in an assisting manner.

Optionally, when the target service is a regulatory service, correspondingly, based on a preset normalized processing flow corresponding to the target service, performing normalized management on the data of the target service, where the normalized management includes S31:

s31, responding to a request of a power grid user for uploading a regulation and regulation management file, and storing the regulation and regulation management file into a target database, so that personnel on a power plant side can download learning chapter management contents.

In this embodiment, the regulatory management file includes power plant regulatory management, temporary regulatory management, and grid regulatory management, and the file defines the working standard of the power plant in grid-related safety management and guides implementation. Optionally, an uploading and downloading control is provided in the power plant data management system, and the uploading or downloading of the regulatory management file for learning is realized by clicking the uploading or downloading control.

Optionally, when the target service is an operation ticket function management, correspondingly, based on a preset normalized processing flow corresponding to the target service, performing normalized management on the data of the target service, where the normalized management includes S41:

s41, receiving a target operation order uploaded by the power plant side and sending the target operation order to a power grid person for auditing, wherein the target operation order is edited by the power plant side person according to a preset operation order template or based on an old operation order.

The operation order refers to written basis for performing electrical operation in the power system, and includes a scheduling instruction order and a transformation operation order. Wherein, include at least in the operation ticket: the method comprises the steps of operation ticket main keys, serial numbers, operation tasks, operation items, item flows, ticket filling persons, auditors, duty responsible persons, item numbers, page numbers, creation time, operation starting time, operation ending time, power plant ID (identity), remarks and operation ticket types.

Before operating the power plant equipment, a person on the side of the power plant can fill a target operation order according to a preset operation order template, or edit the target operation order again based on an old operation order to obtain the target operation order. It should be noted that, the efficiency of obtaining the target operation ticket can be improved by newly filling the old ticket.

Further, a personalized printing function is provided for the power plant data management system, and the target operation ticket is printed in response to the target operation ticket style and the printing request selected by the power plant personnel. The content style of the operation ticket comprises a font, a font size, a color and the like, and in addition, the operation ticket style can be customized.

Furthermore, in this embodiment, the power plant data management system further provides an OA function, and the power plant personnel report and communicate various tasks through the OA function of the system.

EXAMPLE III

Fig. 3 is a schematic structural diagram of a power plant data management system according to a third embodiment of the present invention, where this embodiment is applicable to a case of performing normalized management on power plant data, and the system includes:

a service determining module 301, configured to determine a target service of a local power plant to be currently processed;

the management module 302 is configured to perform standardized management on the data of the target service based on a preset standardized processing procedure corresponding to the target service.

Optionally, the target service is power plant ledger management;

correspondingly, the management module comprises an account management unit, and the account management unit is used for:

acquiring the account information input by the personnel on the power plant side, and sending the account information to the corresponding power grid auditor for auditing;

and generating a scheduled inspection list plan based on the audited standing book information, and prompting corresponding authority personnel on the power plant side to complete scheduled inspection tasks based on the scheduled inspection list plan.

Optionally, the target service is risk management and control of the power plant;

correspondingly, the management module comprises a risk management and control unit, and the risk management and control unit is used for:

issuing a standard risk control task book and a standard power generation plan recorded by a power grid operator to a power plant, enabling corresponding authority personnel at the power plant side to perform specified operation based on the standard risk control task book and the standard power generation plan, and receiving risk control measures and abnormal conditions fed back by the corresponding authority personnel at the power plant side; or

And sending the received maintenance plan generated by the power plant side based on the maintenance template to relevant personnel for checking, and sending a checking result to the power plant side so that corresponding authority personnel on the power plant side can execute maintenance tasks according to the maintenance plan, wherein the maintenance plan comprises annual inspection, monthly inspection and temporary inspection.

Optionally, the target service is a power plant evaluation service;

correspondingly, the management module comprises an evaluation unit for:

the method comprises the steps that a grading result of a grading main body on the power plant based on a preset grading specification and operation behavior data input by the power plant side is obtained, and the grading result is displayed, wherein the operation behavior data comprise field operation behavior data or daily operation behavior data;

and responding to a grading result complaint request submitted by the power plant side, and sending the grading result to a professional auditor for auditing.

Optionally, the target service is a regulatory service;

accordingly, the management module regulates the regulatory administration unit and is used for:

and responding to a request of a power grid user for uploading a regulation and regulation management file, and storing the regulation and regulation management file into a target database, so that a power plant side worker downloads learning chapter and regulation management contents.

Optionally, the target service is operation ticket function management;

correspondingly, the management module comprises an operation ticket function management unit for:

and receiving a target operation order uploaded by the power plant side, and sending the target operation order to a power grid person for auditing, wherein the target operation order is edited by the power plant side person according to a preset operation order template or based on an old operation order.

Optionally, data recorded by the power plant side is received or data is sent to the power plant side based on a preset file transmission and sharing channel. The traffic control terminal provided by the embodiment of the invention can execute the power plant data management method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.

Example four

Fig. 4 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. FIG. 4 illustrates a block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention. The electronic device 12 shown in fig. 4 is only an example and should not bring any limitation to the function and the scope of use of the embodiment of the present invention.

As shown in FIG. 4, electronic device 12 is embodied in the form of a general purpose computing device. The components of electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Electronic device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.

The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 4, and commonly referred to as a "hard drive"). Although not shown in FIG. 4, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.

Electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with electronic device 12, and/or with any devices (e.g., network card, modem, etc.) that enable device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet) via the network adapter 20. As shown, the network adapter 20 communicates with the other modules of the device 12 via the bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, to implement a power plant data management method provided by an embodiment of the present invention, the method including: determining target business of a local power plant to be processed currently; and carrying out standardized management on the data of the target service based on a preset standardized processing flow corresponding to the target service.

EXAMPLE five

An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a power plant data management method according to an embodiment of the present invention, where the method includes:

determining target business of a local power plant to be processed currently; and carrying out standardized management on the data of the target service based on a preset standardized processing flow corresponding to the target service.

Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method of power plant data management, the method comprising:

determining target business of a local power plant to be processed currently;

and carrying out standardized management on the data of the target service based on a preset standardized processing flow corresponding to the target service.

2. The method of claim 1, wherein the target business is power plant ledger management;

correspondingly, based on the preset normalized processing flow corresponding to the target service, performing normalized management on the data of the target service includes:

3. The method of claim 1, wherein the target business is a plant risk management;

issuing the risk control task book and the power generation plan recorded by the power grid operator to the power plant, enabling corresponding authority personnel on the power plant side to perform specified operation based on the standard risk control task book and the standard power generation plan, and receiving the risk control measures and abnormal conditions fed back by the corresponding authority personnel on the power plant side; or

4. The method of claim 1, wherein the target business is a plant evaluation business;

the method comprises the steps that a scoring main body is obtained, scoring results of a power plant are obtained based on preset scoring specifications and operation behavior data input by the power plant side, and the scoring results are displayed, wherein the operation behavior data comprise field operation behavior data or daily operation behavior data;

5. The method of claim 1, wherein the target service is regulatory service;

6. The method of claim 1, wherein the target service is operation ticket function management;

7. The method according to any one of claims 1 to 6, wherein the data entered at the plant side are received or the data are transmitted to the plant side based on a preset file transfer and sharing channel.

8. A power plant data management system, comprising:

9. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the plant data management method of any of claims 1-7.

10. A computer-readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, carries out a plant data management method according to any one of the claims 1-7.