CN112053134A - B/S architecture-based power equipment information management system - Google Patents

B/S architecture-based power equipment information management system Download PDF

Info

Publication number
CN112053134A
CN112053134A CN202010936377.3A CN202010936377A CN112053134A CN 112053134 A CN112053134 A CN 112053134A CN 202010936377 A CN202010936377 A CN 202010936377A CN 112053134 A CN112053134 A CN 112053134A
Authority
CN
China
Prior art keywords
layer
information
defect
management module
equipment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010936377.3A
Other languages
Chinese (zh)
Inventor
尚德华
贾葳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Aopu Shanghai New Energy Co Ltd
Original Assignee
Aopu Shanghai New Energy Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Aopu Shanghai New Energy Co Ltd filed Critical Aopu Shanghai New Energy Co Ltd
Priority to CN202010936377.3A priority Critical patent/CN112053134A/en
Publication of CN112053134A publication Critical patent/CN112053134A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/103Workflow collaboration or project management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23Updating
    • G06F16/2379Updates performed during online database operations; commit processing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2455Query execution
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25Integrating or interfacing systems involving database management systems
    • G06F16/252Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/20Software design
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/38Creation or generation of source code for implementing user interfaces
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/20Administration of product repair or maintenance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/06Energy or water supply

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Data Mining & Analysis (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Tourism & Hospitality (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • General Health & Medical Sciences (AREA)
  • Water Supply & Treatment (AREA)
  • Primary Health Care (AREA)
  • Computational Linguistics (AREA)
  • Public Health (AREA)
  • Human Computer Interaction (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention relates to a power equipment information management system based on a B/S architecture. The system comprises an equipment defect information management module, a workflow management module and an equipment defect record management module, wherein each module realizes the information management of the power equipment through the data processing and transmission among a user layer, a page code layer, a service logic layer and a data connection layer; the equipment defect information management module is used for providing corresponding operation for the management and maintenance of the equipment information for the data maintainer; the workflow management module is used for monitoring and managing the equipment defect elimination process; the device defect record management module is used for managing and maintaining defect record, defect elimination record and defect acceptance record. The invention realizes the management of unification, centralization, standardization, scientification, controllability and synergy of the power equipment so as to improve a series of existing equipment management problems.

Description

B/S architecture-based power equipment information management system
Technical Field
The invention relates to the technical field of power management systems, in particular to a power equipment information management system based on a B/S framework.
Background
The existing power information management system is mainly designed from two directions of C/S architecture and EAM mode.
The power equipment information management system designed on the basis of the C/S architecture uniformly and normatively manages the used power equipment, reduces the workload of workers and realizes resource sharing. The C/S structure needs to be installed and deployed not only on the server side but also on the client side, and for a large-scale user group, it is difficult to perform abnormal installation and deployment upgrading, and a large amount of manpower and material resources are consumed. And the C/S needs to develop a special client, the hardware configuration requirement is high, the development and deployment are relatively difficult, and the later maintenance cost is high. The C/S has the problems of low program running and information sharing rates, poor information consistency in device management, and incompatibility in more systems.
And the equipment management system is designed based on the EAM mode. The system processes the operation and maintenance data of the power equipment by using cloud computing, virtualization technology and workflow technology from two aspects of asset management and equipment maintenance.
Disclosure of Invention
Aiming at the defects in the prior art, the technical problem to be solved by the invention is to provide the power equipment information management system based on the B/S architecture.
The technical scheme adopted by the invention for realizing the purpose is as follows: a power equipment information management system based on a B/S framework comprises an equipment defect information management module, a workflow management module and an equipment defect record management module, wherein each module realizes power equipment information management through data processing and transmission among a user layer, a page code layer, a service logic layer and a data connection layer;
the equipment defect information management module is used for providing corresponding operation for the management and maintenance of the equipment information for the data maintainer;
the workflow management module is used for monitoring and managing the equipment defect elimination process;
the device defect record management module is used for managing and maintaining defect record, defect elimination record and defect acceptance record.
The device defect information management module comprises a device information management module and a defect information management module;
the device information management module is used for providing operations of adding, modifying and deleting device information and inquiring the device information for data maintenance personnel, and specifically comprises the following steps: receiving newly-added, modified, deleted or inquired trigger information through a user layer, receiving filled-in equipment information through a page layer, constructing an entity object through the page code layer, transmitting related parameter information to a service logic layer, sending an operation request of newly-added, modified, deleted or inquired data by the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, and displaying the feedback information by the page layer;
the defect information management module is used for providing defect information query and export operation for equipment information for data maintenance personnel, and specifically comprises the following steps: receiving inquiry or derivation trigger information through a user layer, receiving inquiry or derivation conditions through a page layer, constructing an entity object through a page code layer, transmitting related parameter information to a service logic layer, sending an inquiry or derivation data operation request by the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, and displaying an inquiry or derivation result by the page layer.
The workflow management module comprises a flow generation module and a flow management module;
the flow generation module is used for providing a flow generation function, and specifically comprises: receiving and generating flow trigger information through a user layer, receiving and filling in flow information through a page layer, constructing an entity object through a page code layer, transmitting related parameter information to a service logic layer, sending a flow adding operation request by the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, and displaying the feedback information by the page layer;
the process management module is used for providing functions of inquiring, selecting users and executing processes, and specifically comprises the following steps: the method comprises the steps of receiving inquiry, user selection or flow execution triggering information through a user layer, receiving filled inquiry mediation information, user selection or flow execution information through a page layer, constructing an entity object through a page code layer, transmitting related parameter information to a service logic layer, sending inquiry, user selection and flow execution operation requests through the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, analyzing the entity object through the page code layer and displaying the feedback information through the page layer.
The device defect record management module comprises a defect record input management module and a device defect counting module;
the defect record entry management module is used for providing functions of adding, modifying, deleting and inquiring defect record entry, and specifically comprises the following steps: receiving newly-added, modified, deleted or inquired trigger information of a defect record through a user layer, receiving filled inquiry conditions, modified items, deleted items and newly-added item information through a page layer, constructing an entity object through a page code layer, transmitting related parameter information to a service logic layer, sending an operation request of newly-added, modified, deleted or inquired data by the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, and displaying the feedback information by the page layer;
the equipment defect statistical module is used for providing functions of inquiring, deriving and generating a chart of equipment defects, and specifically comprises the following steps: receiving query, export or graph generation trigger information through a user layer, receiving filled query mediation information, export information or graph generation information through a page layer, constructing an entity object through a page code layer, transmitting related parameter information to a service logic layer, sending query, export and graph generation operation requests by the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, analyzing the entity object by the page code layer and displaying the feedback information by the page layer.
The invention has the following advantages and beneficial effects:
1. the invention realizes the management of unification, centralization, standardization, scientification, controllability and synergy of the power equipment so as to improve a series of existing equipment management problems.
2. The power equipment information management system is based on the B/S architecture, is easy to maintain, simple to develop and simple to deploy. The software technology is fast to update, and the B/S framework is easy to realize the upgrading, maintenance and deployment of the software. Only the upgrading server part needs to be deployed, and the client can access the system through the browser. The B/S does not need a special network environment and can be established on a wide area network.
3. NET realizes separation of page and service logic when writing codes, and separates program codes from display contents, so that the webpage contents are easy to write, and the program codes are simpler. The reusability of the layered design codes is good, the code reuse is well realized according to the layered structure design in the code development process, and the code redundancy is avoided.
Drawings
FIG. 1 is a block diagram of the overall structure of the present invention;
fig. 2 is a sequence diagram of device information management of device information addition according to an embodiment of the present invention;
FIG. 3 is a timing diagram of defect information management for querying according to an embodiment of the present invention;
FIG. 4 is a functional timing diagram of a generation flow according to an embodiment of the present invention;
FIG. 5 is a timing diagram of a process management query in accordance with an embodiment of the present invention;
FIG. 6 is a timing diagram of a defect entry according to an embodiment of the present invention;
FIG. 7 is a timing diagram illustrating an apparatus defect statistics query according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples.
As shown in fig. 1, an electrical equipment information management system based on a B/S architecture includes an equipment defect information management module, a workflow management module, and an equipment defect record management module.
The device defect information management module mainly comprises two submodules of device information management and defect information management, and management and maintenance of the device information and the defect information are realized through a device defect management function.
The equipment information management module provides operations of adding, modifying, deleting, inquiring and the like for the management and maintenance of the equipment information by data maintenance personnel. Taking the device information addition as an example, the device information management sequence diagram is shown in fig. 2: 1. and the user logs in the system to enter the equipment defect management module and enters the equipment information management interface. 2. And clicking the newly added function of the equipment by the user, and receiving a request by the system to jump the newly added interface of the equipment. 3. The user adds an information page on the device, fills in the device related information and submits, constructs the device information into an entity object through an entity class, and transmits the entity object to the service logic layer DeviceBLL. And 4, the DeviceBLL sends a request for newly adding data to the DeviceDAL, and the DeviceDAL receives the request to analyze the entity object and store the information in the database. 5. A message is returned to the user that the device addition was successful.
The defect information management module provides query and export functions for data maintainers, and a defect information management sequence chart taking query as an example is shown in fig. 3: 1. and the user logs in an equipment defect management module of the equipment management system and enters a defect information management page. 2. The user inputs the query condition and clicks the query button. And 3.defct. aspx.cs encapsulates the query condition into an entity object and transmits the entity object to the DefctBLL. The DefctBLL sends a query data request to the DefctDAL. And 5, the DefctDAL receives a request for analyzing the entity object to perform data operation. DefctDAL returns the query-to-data to defct. And 7, calling the entity class by defct.aspx.cs to analyze the returned entity object and transmitting the data to a defct.aspx display information list.
The workflow management module is set by monitoring and managing the defect eliminating flow of the whole equipment by the scheduling communicator, and the defect eliminating of the equipment forms a uniform and standard flow through workflow management, so that each link of the defect eliminating of the equipment can be monitored and managed in real time, the scheduling communicator can master the progress of the defect eliminating, and the defect eliminating progress can be commanded and scheduled in real time. The workflow management module is divided into two submodules of a generation flow and a flow management.
The working sequence diagram of the generation flow module is shown in fig. 4: 1. the user logs into the system and enters the workflow management module. 2. And clicking the generation flow by the user, and receiving a request by the system to jump the flow to generate a page. 3. And filling relevant information of the flow and submitting the relevant information of the flow by a user on a flow page, constructing the flow information into an entity object through an entity class, and transmitting the entity object to a business logic layer flowBLL by flow. And 4, the flowBLL sends a request for newly adding data to the flowDAL, the flowDAL receives the request to analyze the entity object, and the information is stored in the database. 5. And returning a message that the process generation is successful to the user.
The process management module provides functions of inquiring, selecting users and executing processes for users. When the user inquires about the progress of the flow through the function, the operation is performed according to the following flow (as shown in fig. 5): 1. and logging in a workflow management module of the power equipment management system by a user, and entering a process management page. 2. The user inputs the query condition and clicks the query button. Aspx.cs encapsulates query conditions into entity objects, passing to flowMg BLL. 4.flowMg BLL sends query data request to flowMgDAL. And 5, receiving the request to analyze the entity object to perform data operation by the flowMgDAL. flowMgDAL returns query-to-data to flowmg. And 7, invoking the entity class by using flowMg.
The equipment defect record management module manages and maintains defect records, defect eliminating records and defect acceptance records, and records of main participators in the defect eliminating process are managed and maintained through the function, so that people can be responsible in the defect eliminating process, workers can be supervised conveniently, and the management module comprises defect record input management and two sub-modules.
The defect record entry management module provides functions of adding, deleting, modifying, inquiring and the like for a user, and a defect record entry sequence diagram is shown in fig. 6: 1. and a user logs in an equipment defect record management module of the power equipment management system and enters a defect record entry management page. 2. And clicking the function of adding the defect record by the user, and accepting the request of the system to jump to the equipment adding record interface. 3. And a user adds a record page in the defect, fills in related information of the defect record and submits, constructs equipment information into an entity object through an entity class, and transmits the entity object to a business logic layer devRecordBLL. And 4, sending a request for adding a record operation to the devRecord DAL by the devRecord BLL, analyzing the entity object by the devRecord DAL after receiving the request, and storing the information in the database. 5. And returning a message that the record addition is successful to the user.
The device defect statistical module provides functions of query, export, chart and the like for a user, and a device defect statistical query sequence chart is shown in fig. 7: 1. and a user logs in an equipment defect record management module of the power equipment management system and enters an equipment defect counting page. 2. The user inputs the query condition and clicks the query button. And 3.defctReport. aspx. cs encapsulates the query condition into an entity object and transmits the entity object to the defctReportBLL. And 4. the DefctReportBLL sends a query data request to the DefctReportDAL. And 5, receiving the request for analyzing the entity object by the DefctReportDAL to perform data operation. Defctreport dal returns the query-to-data to defctreport. aspx. cs. And 7, calling the entity class by the defctreport. aspx. cs to analyze the returned entity object and transmit the data to a defctreport. aspx display information list.

Claims (4)

1. A power equipment information management system based on a B/S framework is characterized by comprising an equipment defect information management module, a workflow management module and an equipment defect record management module, wherein each module realizes the information management of power equipment through the data processing and transmission among a user layer, a page code layer, a service logic layer and a data connection layer;
the equipment defect information management module is used for providing corresponding operation for the management and maintenance of the equipment information for the data maintainer;
the workflow management module is used for monitoring and managing the equipment defect elimination process;
the device defect record management module is used for managing and maintaining defect record, defect elimination record and defect acceptance record.
2. The electrical equipment information management system based on the B/S architecture as claimed in claim 1, wherein the equipment defect information management module comprises an equipment information management module and a defect information management module;
the device information management module is used for providing operations of adding, modifying and deleting device information and inquiring the device information for data maintenance personnel, and specifically comprises the following steps: receiving newly-added, modified, deleted or inquired trigger information through a user layer, receiving filled-in equipment information through a page layer, constructing an entity object through the page code layer, transmitting related parameter information to a service logic layer, sending an operation request of newly-added, modified, deleted or inquired data by the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, and displaying the feedback information by the page layer;
the defect information management module is used for providing defect information query and export operation for equipment information for data maintenance personnel, and specifically comprises the following steps: receiving inquiry or derivation trigger information through a user layer, receiving inquiry or derivation conditions through a page layer, constructing an entity object through a page code layer, transmitting related parameter information to a service logic layer, sending an inquiry or derivation data operation request by the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, and displaying an inquiry or derivation result by the page layer.
3. The B/S architecture-based power equipment information management system according to claim 1, wherein the workflow management module comprises a generation flow module and a flow management module;
the flow generation module is used for providing a flow generation function, and specifically comprises: receiving and generating flow trigger information through a user layer, receiving and filling in flow information through a page layer, constructing an entity object through a page code layer, transmitting related parameter information to a service logic layer, sending a flow adding operation request by the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, and displaying the feedback information by the page layer;
the process management module is used for providing functions of inquiring, selecting users and executing processes, and specifically comprises the following steps: the method comprises the steps of receiving inquiry, user selection or flow execution triggering information through a user layer, receiving filled inquiry mediation information, user selection or flow execution information through a page layer, constructing an entity object through a page code layer, transmitting related parameter information to a service logic layer, sending inquiry, user selection and flow execution operation requests through the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, analyzing the entity object through the page code layer and displaying the feedback information through the page layer.
4. The electrical equipment information management system based on the B/S architecture as claimed in claim 1, wherein the equipment defect record management module comprises a defect record entry management module and an equipment defect statistics module;
the defect record entry management module is used for providing functions of adding, modifying, deleting and inquiring defect record entry, and specifically comprises the following steps: receiving newly-added, modified, deleted or inquired trigger information of a defect record through a user layer, receiving filled inquiry conditions, modified items, deleted items and newly-added item information through a page layer, constructing an entity object through a page code layer, transmitting related parameter information to a service logic layer, sending an operation request of newly-added, modified, deleted or inquired data by the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, and displaying the feedback information by the page layer;
the equipment defect statistical module is used for providing functions of inquiring, deriving and generating a chart of equipment defects, and specifically comprises the following steps: receiving query, export or graph generation trigger information through a user layer, receiving filled query mediation information, export information or graph generation information through a page layer, constructing an entity object through a page code layer, transmitting related parameter information to a service logic layer, sending query, export and graph generation operation requests by the service logic layer, analyzing the entity object through a data connection layer, returning feedback information to the service logic layer and the page code layer by layer, analyzing the entity object by the page code layer and displaying the feedback information by the page layer.
CN202010936377.3A 2020-09-08 2020-09-08 B/S architecture-based power equipment information management system Pending CN112053134A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010936377.3A CN112053134A (en) 2020-09-08 2020-09-08 B/S architecture-based power equipment information management system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010936377.3A CN112053134A (en) 2020-09-08 2020-09-08 B/S architecture-based power equipment information management system

Publications (1)

Publication Number Publication Date
CN112053134A true CN112053134A (en) 2020-12-08

Family

ID=73609820

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010936377.3A Pending CN112053134A (en) 2020-09-08 2020-09-08 B/S architecture-based power equipment information management system

Country Status (1)

Country Link
CN (1) CN112053134A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113742554A (en) * 2021-09-06 2021-12-03 广东电网有限责任公司 Management method and device of power equipment, computer equipment and medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101770612A (en) * 2009-09-17 2010-07-07 宁波北电源兴电力工程有限公司 Device defect management module of EAM (Enterprise Asset Management) system in power plant
US20140222493A1 (en) * 2013-02-04 2014-08-07 Uni-B Solutions Llc Process management system, method, and computer-readable medium
CN106503927A (en) * 2016-11-14 2017-03-15 南京三方化工设备监理有限公司 A kind of petrochemical industry project equipment Monitoring information management system
CN106647586A (en) * 2017-01-20 2017-05-10 重庆邮电大学 Virtual machine room visualization monitoring management system based on B/S architecture and realization method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101770612A (en) * 2009-09-17 2010-07-07 宁波北电源兴电力工程有限公司 Device defect management module of EAM (Enterprise Asset Management) system in power plant
US20140222493A1 (en) * 2013-02-04 2014-08-07 Uni-B Solutions Llc Process management system, method, and computer-readable medium
CN106503927A (en) * 2016-11-14 2017-03-15 南京三方化工设备监理有限公司 A kind of petrochemical industry project equipment Monitoring information management system
CN106647586A (en) * 2017-01-20 2017-05-10 重庆邮电大学 Virtual machine room visualization monitoring management system based on B/S architecture and realization method

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113742554A (en) * 2021-09-06 2021-12-03 广东电网有限责任公司 Management method and device of power equipment, computer equipment and medium

Similar Documents

Publication Publication Date Title
Simmhan et al. A framework for collecting provenance in data-centric scientific workflows
CN102880503B (en) Data analysis system and data analysis method
CN105809356A (en) Information system resource management method based on application integrated cloud platform
CN112600891B (en) Information physical fusion-based edge cloud cooperative system and working method
US20130166490A1 (en) Pneuron distributed analytics
CN107317724A (en) Data collecting system and method based on cloud computing technology
Sun et al. A cost-effective approach to delivering analytics as a service
CN109192248A (en) Biological information analysis system, method and cloud computing platform system based on cloud platform
CN110716832A (en) Service operation monitoring and alarming method, system, electronic equipment and storage medium
CN107798037A (en) The acquisition methods and server of user characteristic data
CN110377595A (en) A kind of vehicle data management system
CN102169562A (en) Method and system for processing project plans
CN104508625A (en) Abstraction models for monitoring of cloud resources
CN109885624A (en) Data processing method, device, computer equipment and storage medium
CN110175822A (en) A kind of equipment account management method and system
CN111143391A (en) Data sharing exchange method and system
CN105338045A (en) Cloud computing resource processing device, method and cloud computing system
CN115081913A (en) Supply chain risk assessment and prevention and control system
CN107222575B (en) The method that OPC is communicated between realization industrial control equipment
CN116433198A (en) Intelligent supply chain management platform system based on cloud computing
CN114816591A (en) Service interface processing method and device, computer equipment and storage medium
CN112053134A (en) B/S architecture-based power equipment information management system
CN112214236B (en) Method for building management system of application architecture of software rapid development platform
KR102523699B1 (en) Federated learning system for manufacturing environment
Babar et al. Toward a framework for capturing and using architecture design knowledge

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20201208