CN112383580B - Ship remote fault alarm system based on body - Google Patents
Ship remote fault alarm system based on body Download PDFInfo
- Publication number
- CN112383580B CN112383580B CN202010927891.0A CN202010927891A CN112383580B CN 112383580 B CN112383580 B CN 112383580B CN 202010927891 A CN202010927891 A CN 202010927891A CN 112383580 B CN112383580 B CN 112383580B
- Authority
- CN
- China
- Prior art keywords
- ship
- alarm
- working condition
- data
- condition management
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
- G01D21/00—Measuring or testing not otherwise provided for
- G01D21/02—Measuring two or more variables by means not covered by a single other subclass
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Administration; Management
- G06Q10/20—Administration of product repair or maintenance
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/006—Indicating maintenance
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
-
- G—PHYSICS
- G08—SIGNALLING
- G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G08B21/00—Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
- G08B21/18—Status alarms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
Landscapes
- Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Software Systems (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Databases & Information Systems (AREA)
- Human Resources & Organizations (AREA)
- General Engineering & Computer Science (AREA)
- Operations Research (AREA)
- Health & Medical Sciences (AREA)
- Tourism & Hospitality (AREA)
- Emergency Management (AREA)
- Strategic Management (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- General Business, Economics & Management (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Marketing (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Computer Interaction (AREA)
- Economics (AREA)
- Alarm Systems (AREA)
Abstract
The invention discloses a body-based ship remote fault alarm system, which comprises a working condition management subsystem and a remote maintenance service subsystem, wherein the working condition management subsystem is used for acquiring monitoring data of a heterogeneous ship-borne sensor, converting the acquired monitoring data into body instance data, storing and reasoning the body instance data, and sending a reasoning result to the remote maintenance service subsystem, and the remote maintenance service subsystem is used for sending the reasoning result to ship-borne and shore-based remote technicians to provide ship maintenance auxiliary decision and working condition knowledge services. The system not only can monitor the ship condition in real time and automatically generate fault alarm, but also supports information sharing and ship information query of ships and shore-based technicians.
Description
Technical Field
The invention relates to the technical field of ship remote technical support, in particular to a ship remote fault alarm system based on a body.
Background
In recent years, China pays more and more attention to the state monitoring technology of integration of ships and shore-based guarantee, but current research mainly focuses on data reading, display and storage of ship equipment, and on-board technicians are required to judge possible faults or problems from instrument display according to experience.
The inventor of the present application finds that the method of the prior art has at least the following technical problems in the process of implementing the present invention:
(1) the operation mode of the current ship fault guarantee alarm system is mainly a single framework, so that the expandability and the reliability are poor;
(2) the expression of knowledge is not uniform, and knowledge reasoning ability is lacked;
(3) remote data transmission and information inquiry are not supported.
Therefore, the prior art is inconsistent in knowledge expression and lacks knowledge reasoning. Resulting in a poor warning effect.
Disclosure of Invention
In view of the above, the invention provides a body-based ship remote fault alarm system and method, which are used for solving or at least partially solving the technical problem of poor alarm effect caused by non-uniform guarantee knowledge expression and lack of knowledge reasoning in the prior art.
In order to solve the above technical problem, a first aspect of the present invention provides a body-based remote ship fault alarm system, including:
the working condition management subsystem is used for acquiring monitoring data of the heterogeneous shipborne sensor, converting the acquired monitoring data into body example data, storing and reasoning the body example data and sending a reasoning result to the remote maintenance service subsystem, the working condition management subsystem specifically comprises a ship-side working condition management middleware and a central working condition management middleware, wherein the working condition management middleware and the central working condition management middleware comprise a data collector module, a body manager module and a working condition agent module, the data collector module is used for collecting the monitoring data of the heterogeneous shipborne sensor, the body manager module is used for storing a body model and an example thereof in a database, a reasoning machine and a rule file based on rules and reasoning the monitoring data according to the body model, the reasoning machine and the rule file to obtain a reasoning result, and the working condition agent module is used for managing the interaction between the middleware and the remote maintenance service subsystem, sending the inference result to a remote maintenance service subsystem;
and the remote maintenance service subsystem is used for sending the inference result to shipborne and shore-based remote technicians to provide ship maintenance auxiliary decision-making and working condition knowledge service, and specifically comprises a rear end layer, a middle layer and a front end layer, wherein the rear end layer is used for storing information resources, the middle layer is used for realizing various service business logics of the remote maintenance service subsystem, and the front end layer is used for generating a user interaction interface.
In one embodiment, the data collector module of the central working condition management middleware comprises an alarm management unit and a ship working condition management unit, wherein the ship working condition management unit establishes a message queue for each ship working condition management middleware managed by the ship working condition management unit, and messages sent from the remote maintenance service subsystem are all routed to the message queue of a target ship; and the alarm management unit is used for routing the alarm to the body manager after receiving the alarm sent by the ship working condition management middleware and creating a fault notification strategy.
In one embodiment, the condition management middleware further includes a condition client configured to periodically poll the ship condition management module of the central condition management middleware to query whether there is a new message.
In one embodiment, the data acquisition module of the condition management middleware includes a data fusion unit and a data acquisition scheduling unit, wherein the data acquisition scheduling unit is configured to execute a timer event and allocate a corresponding timing trigger according to a monitoring scheme in a timer event object to control a frequency of acquiring data from the sensor, and the data fusion unit is configured to fuse and forward the acquired data.
In one embodiment, the ontology model stored by the ontology manager module comprises an equipment domain ontology, a ship domain ontology, an alarm management ontology and a security strength ontology, wherein the equipment domain ontology comprises equipment monitoring data and measurement parameters, the ship domain ontology comprises internal environment parameters of monitoring ships, including temperature, humidity, smoke and fire, the alarm management ontology comprises a maintenance application strategy when the ship equipment fails, and the security strength ontology comprises ship equipment technicians belonging to different organizations.
In one embodiment, the inference engine in the ontology manager module is configured to determine whether to issue an alarm and determine an alarm level according to the device domain ontology and the ship domain ontology, and the inference engine is further configured to determine a notification policy according to the alarm management ontology, the guaranteed strength ontology, and the determined alarm level.
In one embodiment, the service business logic implemented by the middle tier of the remote service subsystem includes service documentation management, notification management, expert basic information, messaging, and proactive service applications.
In one embodiment, the condition management middleware is specifically configured to:
generating an equipment field ontology example and a ship field ontology example according to the collected monitoring data;
generating an alarm notification by using an inference machine and an inference rule according to the domain ontology example and the ship domain ontology example, and determining an alarm level;
and sending the alarm notification and the alarm level to the central working condition management middleware.
In one embodiment, the central condition management middleware is specifically configured to:
detecting the ship fault condition contained in the alarm message and the busy and idle state of the current support personnel stored in the database;
according to the fault state of the ship, the busy and idle states of current support personnel and the triggered alarm level, establishing a related alarm management body example and a related force support body example;
generating a notification strategy by using an inference machine and an inference rule according to the alarm management ontology example and the guarantee strength ontology example;
and send the generated notification policy to the remote service subsystem.
Based on the same inventive concept, the second aspect of the invention provides a body-based ship remote fault alarm method, which comprises the following steps:
sending a control command through a remote maintenance service subsystem interface, wherein the control command comprises accessing or modifying equipment information, and the equipment information comprises an alarm threshold value and data acquisition parameter configuration;
the remote maintenance service subsystem sends the control command to the central working condition management middleware, and the control command is forwarded to the ship working condition management middleware through the central working condition management middleware;
the ship working condition management middleware controls the ship equipment and the internal environment detection sensor to acquire the data of the ship equipment and the data of the internal environment according to the control command;
the ship working condition management middleware forwards the acquired data to the remote maintenance service subsystem to update equipment record information, and simultaneously sends the acquired data to the body manager module for modifying the equipment field body example and the ship field body example;
the ship working condition management middleware adopts a rule-based inference machine to carry out inference according to the equipment field body example and the ship field body example, and sends a trigger alarm notification to the central working condition management middleware;
the central working condition management middleware generates an alarm management body and a guarantee force body example according to the alarm notification, adopts a rule-based inference machine to carry out inference according to the alarm management body and the guarantee force body example, generates an alarm strategy and sends the alarm strategy to the remote maintenance service subsystem;
the remote maintenance service subsystem system sends maintenance applications to target objects in an expert list according to an alarm strategy, wherein the expert list is contained in an alarm management body, the alarm management body comprises a notification strategy model, the notification strategy model is an expert queue set, and each expert queue contains an expert list corresponding to members in a ship support network.
One or more technical solutions in the embodiments of the present application have at least one or more of the following technical effects:
the invention provides a ship remote fault alarm system based on a body, which comprises a working condition management subsystem and a remote maintenance service subsystem, wherein the working condition management subsystem specifically comprises a ship end working condition management middleware and a central working condition management middleware, wherein the working condition management middleware and the central working condition management middleware comprise a data collector module, a body manager module and a working condition agent module, the data collector module is used for collecting monitoring data of the heterogeneous shipborne sensor, the body manager module is used for storing a body model and an example thereof in a database, an inference engine based on rules and a rule file, the monitoring data is inferred according to the ontology model, the inference engine and the rule file to obtain an inference result, and the working condition agent module is used for managing interaction between the middleware and the remote maintenance service subsystem and sending the inference result to the remote maintenance service subsystem; the remote maintenance service subsystem specifically comprises a rear end layer, a middle layer and a front end layer, wherein the rear end layer is used for storing information resources, the middle layer is used for realizing various service business logics of the remote maintenance service subsystem, and the front end layer is used for generating a user interaction interface.
According to the remote ship fault alarm system, in the aspect of data transmission and storage, the semantic Web technology is adopted to support the development of personalized Web services, the ship guarantee knowledge is expressed in a body paradigm form through the Web technology, and a body rule engine is used for reasoning, so that the final maintenance scheme is generated. The system not only can monitor the ship condition in real time and automatically generate fault alarm, but also supports information sharing and ship information query of ships and shore-based technicians, improves the alarm effect, and solves the problem of poor alarm effect caused by non-uniform guarantee knowledge expression and lack of knowledge reasoning in the prior art.
Drawings
In order to more clearly illustrate the embodiments or technical solutions of the present invention, the drawings used in the embodiments or technical solutions in the prior art are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a diagram of a ship condition management structure in an embodiment of the invention;
FIG. 2 is a schematic diagram of an apparatus domain ontology according to an embodiment of the present invention;
FIG. 3 is a schematic illustration of a ship domain ontology according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating an alarm management entity in an embodiment of the present invention;
FIG. 5 is a schematic diagram of a body for securing strength according to an embodiment of the present disclosure;
FIG. 6 is a schematic diagram of the overall system structure according to an embodiment of the present invention;
FIG. 7 is a detailed structural diagram of a condition management subsystem in the embodiment of the present invention;
FIG. 8 is a flowchart of fault detection and alarm management in an embodiment of the present invention.
Detailed Description
In order to overcome the defects of the prior art and solve the problem of lacking knowledge reasoning of ship fault alarming, the invention provides a ship remote fault alarming system based on a body. The system is composed of three types of organization units, the working condition information provider is composed of a distributed sensor network and is responsible for transmitting ship equipment state data, the working condition information management middleware is responsible for information processing, and a working condition information user adjusts fault processing behaviors according to working condition information contents and comprises various alarm processing application software.
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
The embodiment provides a long-range fault alarm system of boats and ships based on body, includes:
the working condition management subsystem is used for acquiring monitoring data of the heterogeneous shipborne sensor, converting the acquired monitoring data into body example data, storing and reasoning the body example data and sending a reasoning result to the remote maintenance service subsystem, and the working condition management subsystem specifically comprises a ship-side working condition management middleware and a central working condition management middleware, wherein the working condition management middleware and the central working condition management middleware comprise a data acquisition module, a body manager module and a working condition agent module, the data acquisition module is used for acquiring the monitoring data of the heterogeneous shipborne sensor, the body manager module is used for storing a body model, an example thereof, a rule-based reasoning machine and a rule file in a database and reasoning the monitoring data according to the body model, the reasoning machine and the rule file to obtain a reasoning result, and the working condition agent module is used for managing the interaction between the middleware and the remote maintenance service subsystem, sending the inference result to a remote maintenance service subsystem;
and the remote maintenance service subsystem is used for sending the inference result to shipborne and shore-based remote technicians to provide ship maintenance auxiliary decision-making and working condition knowledge service, and specifically comprises a rear end layer, a middle layer and a front end layer, wherein the rear end layer is used for storing information resources, the middle layer is used for realizing various service business logics of the remote maintenance service subsystem, and the front end layer is used for generating a user interaction interface.
Specifically as shown in fig. 1. The working condition information provider is a distributed sensor which is responsible for collecting data, the working condition information management middleware is responsible for information processing, and a working condition information user adjusts fault processing behaviors according to the content of the working condition information.
The system comprises a working condition management middleware and a central working condition management middleware, wherein the working condition management middleware is a ship working condition manager, the central working condition management middleware is a shore-based working condition manager, the working condition information management middleware is composed of ship working condition management nodes, the nodes acquire data from a working condition information provider, and the working condition information management middleware comprises a data acquisition module, a body manager module and a working condition agent module, (1) the data acquisition module receives data from a sensor network supporting Web service through SOAP (simple object access protocol) information; if the sensor does not support Web service, the sensor is connected with the sensor by additionally installing a sensing adapter, and the adapter is responsible for converting the received data into SOAP message and then sending the SOAP message to the data collector. (2) The body manager module (i.e. the working condition knowledge base) is responsible for managing the knowledge base, and stores the working condition model and the example data through the database, and in addition, the working condition knowledge base also comprises an inference engine and a rule file. (3) The working condition agent module is responsible for interaction between the working condition management node and external application software, and the specific working process comprises the following steps: when the application software (remote maintenance service subsystem) needs to inquire the working condition data, the working condition agent module carries out format conversion on the inquiry command, delivers the working condition knowledge base for execution and returns the execution result to the application software; and when the working condition changes, transmitting the changed data to application software subscribing the event, wherein communication among all the distributed components adopts a SOAP Web service interface and HTTP notification service based on XML messages.
It should be noted that (1) the first data collection method is to receive data through SOAP messages, but the data sources of the two types of condition managers (the condition management middleware and the central condition management middleware) are different, the ship condition management middleware receives data from a sensor supporting Web services, and the central condition management middleware receives data from SOAP messages sent by the ship condition management middleware. The second mode is to collect data through a sensing adapter, and is mainly applied to collecting data from a sensor which does not support Web service by the ship working condition management middleware. (2) Working condition knowledge base based on knowledge base: the system comprises an ontology model and an instance thereof stored in a database, a rule-based inference engine and a rule file, wherein a working condition knowledge base can be realized based on a Jena platform. (3) Working condition agent: and distributing the working condition data to an external service, and submitting the changed data to application software which subscribes to the type of data when the monitoring data is changed. Meanwhile, the condition agent also supports a request/response mode, and both the notification/subscription mode and the request/response mode can be realized in a SOAP message exchange mode.
The remote fault alarm system comprises a remote maintenance service subsystem and a remote fault alarm system, wherein the remote fault alarm system comprises a working condition management subsystem (comprising a shipborne middleware and a central middleware) and a remote maintenance service subsystem, the working condition management subsystem is used for collecting monitoring data of heterogeneous shipborne sensors, converting the monitoring data into body example data, storing and reasoning the body example data, and sending a final result to upper ship guarantee application software (such as a remote maintenance service subsystem) and provides ship maintenance auxiliary decision and working condition knowledge service for shipborne and shore-based remote technicians, and the remote maintenance service subsystem and the working condition management subsystem are communicated by using a standard Web service interface.
In one embodiment, the data collector module of the central working condition management middleware comprises an alarm management unit and a ship working condition management unit, wherein the ship working condition management unit establishes a message queue for each ship working condition management middleware managed by the ship working condition management unit, and messages sent from the remote maintenance service subsystem are all routed to the message queue of a target ship; and the alarm management unit is used for routing the alarm to the body manager after receiving the alarm sent by the ship working condition management middleware and creating a fault notification strategy.
Specifically, in order to be able to interactively acquire frequency or alarm threshold and other messages with external software such as a remote maintenance service subsystem, a ship condition management unit of a central condition management middleware provides a Web service interface which can be called by the remote maintenance service subsystem, the ship condition management unit establishes a message queue for each ship condition management middleware managed by the ship condition management unit, and messages sent from the remote maintenance service subsystem are all routed to the message queue of a target ship.
In one embodiment, the condition management middleware further includes a condition client configured to periodically poll the ship condition management module of the central condition management middleware to query whether there is a new message.
Specifically, the working condition client module of the ship working condition management middleware periodically polls the ship working condition management unit of the central working condition management middleware to inquire whether a new message exists, and the periodic polling can monitor the operation of the ship working condition management middleware and diagnose whether the connection between the shore-based working condition management middleware and the ship working condition management middleware is normal. When the periodical polling of a certain ship is not received for a period of time, which indicates that software failure or communication interruption possibly occurs, a corresponding alarm needs to be triggered immediately, and the emergency resource group starts to solve after receiving the alarm notification.
In one embodiment, the data acquisition module of the condition management middleware includes a data fusion unit and a data acquisition scheduling unit, wherein the data acquisition scheduling unit is configured to execute a timer event and allocate a corresponding timing trigger according to a monitoring scheme in a timer event object to control a frequency of acquiring data from the sensor, and the data fusion unit is configured to fuse and forward the acquired data.
Specifically, the condition client of the ship condition management middleware analyzes the received message content and generates a corresponding event. And the data acquisition and scheduling module of the ship working condition management middleware is responsible for executing a new timer event, and allocates a corresponding timing trigger to control the frequency of data acquisition from the sensor according to a monitoring scheme in a timer event object.
The data fusion module of the ship condition management middleware provides a Web service interface for function calling, the sensor network sends newly acquired collected data by calling the Web service interface, then the data are transferred to the data distribution unit of the condition agent module, the data distribution unit forwards the data to the remote maintenance service subsystem so as to update equipment record information, and simultaneously sends a message to the body manager module so as to modify equipment and ship environment body examples, and a rule-based inference engine utilizes a knowledge base to perform inference in order to detect possible faults and generate alarm events.
In one embodiment, the ontology model stored by the ontology manager module comprises an equipment domain ontology, a ship domain ontology, an alarm management ontology and a security strength ontology, wherein the equipment domain ontology comprises equipment monitoring data and measurement parameters, the ship domain ontology comprises internal environment parameters of monitoring ships, including temperature, humidity, smoke and fire, the alarm management ontology comprises a maintenance application strategy when the ship equipment fails, and the security strength ontology comprises ship equipment technicians belonging to different organizations.
Specifically, the knowledge base of the ontology manager module specifically includes the following 4 types of ontologies: equipment field body, boats and ships field body, alarm management body and guarantee strength body. The device domain body comprises device monitoring data and measurement parameters, for example, the monitoring parameters represent indexes (temperature, humidity and the like) to be monitored, the monitoring data are collected data values of the indexes, the data can be used by the system for judging the working condition of the device, and whether an alarm should be sent out or not is judged by comparing the collected data with a set threshold value. The system describes the device ontology model by using an OWL Web ontology language, a UML class diagram is used in FIG. 2 to express an OWL class, attributes in the UML class diagram represent data type attributes of the OWL class, and connecting lines in the UML class diagram represent object attributes of the OWL class. Fig. 2 is an example of a device domain body, in which an example of a lubricating oil parameter class is added to a device, measured values are compared with standard ranges for judging the working state of the device, each standard range includes an upper limit value, a lower limit value and an alarm level, when the measured values exceed the upper limit value or are lower than the lower limit value, an alarm of the corresponding level is activated, the alarm level of the system can be divided into 4 levels, which are respectively very low, medium and high, and the alarm level can be further refined. When 1 or more measured parameters are not in the standard range, the working state of the equipment will be changed according to the 'abnormal parameter class' and the corresponding alarm level, and the rule reasoner will also generate an alarm event according to the changed working state, wherein an alarm event message comprises the emergency level of the current state of the equipment, the basic attribute of the equipment and the parameter generating the abnormal condition.
The internal environmental parameters of the ship can also trigger warnings, which the ship domain ontology represents. The ship domain body is similar to the equipment domain body, but is mainly used for monitoring internal environment parameters of the ship, including temperature, humidity, smoke, fire and the like, as shown in fig. 3.
When the system finds abnormal equipment parameter values or ship environment parameter values, indicating that a fault occurs, an alarm is needed. When technicians receive an alarm and need to organize maintenance, maintenance application strategies need to be set for the maintenance application strategies so as to collect proper professionals, and the problems to be solved by the application strategies include: (1) it is necessary to inform which professionals (2) in what way (3) at what time the maintenance notification is sent is more appropriate (4) and whether an immediate response message is required. The alarm management body indicates how to notify technicians to implement technical support when the ship equipment fails, that is, to set a maintenance application policy, as shown in fig. 4. The notification strategy model is expressed as a set of expert queues in the alarm management body, each expert queue comprises an expert list corresponding to members in the ship support network, whether response messages and notification modes (EMAIL, short messages, WeChat and the like) are defined in the body, each expert corresponds to a serial number, and the priority of contact with different expert members in the same expert queue is defined. For example, when a medium alarm occurs, the system behavior may be: (1) the technician is notified via a short message or EMAIL. Firstly, a maintenance application notice is sent to a fault equipment manufacturer, if no response message is received within preset time, personnel of the maintenance manufacturer are notified according to a predefined sequence until the response message is received. If all experts finish informing, no answer message is received, and the system informs the emergency rescue organization. (2) Meanwhile, at least one ship carrier attendant must be notified and no response message is required. To ensure that action (1) is implemented, the following approach may be taken: the attribute of the expert queue to be answered is set to true and each member of the expert queue is flagged as an equipment manufacturer technician or a service manufacturer technician and assigned a different serial number. In order to implement action (2), the "response required" flag in the 2 nd expert queue is set to false, and the company to which the ship belongs is pointed to guarantee the person on duty.
After the system receives the alarm, a specialist notification strategy is started, appropriate personnel are selected from the security specialist network and put into a specialist queue, a security specialist network model is shown in a security force body shown in fig. 5, and the security force body represents ship equipment technicians belonging to different organizations and can belong to universities, research institutes, manufacturers, maintenance manufacturers and the like. The expert can be inherited into the following three subclasses, on-board technicians, remote security personnel and nearby ship technicians.
In one embodiment, the inference engine in the ontology manager module is configured to determine whether to issue an alarm and determine an alarm level according to the device domain ontology and the ship domain ontology, and the inference engine is further configured to determine a notification policy according to the alarm management ontology, the guaranteed strength ontology, and the determined alarm level.
Specifically, the method adopts an inference engine based on the ontology to realize two functions according to the monitoring value and the corresponding threshold value defined in the ontology, wherein the first generation of the alarm notification specifically comprises the steps of (1) judging whether to send an alarm or not, (2) determining the alarm level, and the second generation of a notification strategy according to the alarm notification. The first function may specifically be that, for a certain marine diesel engine, when the cylinder pressure is higher than 40 kgf/cm and the rotation speed is less than 500 rpm, a top level alarm is issued, and the rule may be defined as follows: (parameter 1rdf: type rotational speed) (parameter 1 measurement v1) le (v1,500) (parameter 2rdf: type cylinder pressure) (parameter 2 measurement v2) ge (v2,500) - > (operating condition alarm level 'high').
When the alarm is given, the second function is realized: the inference engine calculates an expert notification strategy, for example, when a medium level alarm is received, a ship maintenance manufacturer technician who is not on duty is required to participate in the maintenance according to the alarm notification strategy, and the rule can be defined as follows. (service specialist rdf: type service factory technician) (service specialist idle status 'idle') (rdf: type alarm) - > (q rdf: type contact service factory technician) (q contact specialist service specialist).
The system comprises at least two types of working condition management middleware, wherein one working condition management middleware is arranged on a ship (namely the working condition management middleware at the ship end), and when a local technician of the ship cannot solve a fault, the working condition management middleware is communicated with the central working condition management middleware arranged in a shore-based remote guarantee unit. The other one is arranged in a shore-based remote guarantee unit (central working condition management middleware), is mainly responsible for integration and message distribution of remote resource services, and is cooperated with the shipborne working condition management middleware, and the shipborne working condition management middleware and the central working condition management middleware jointly form a working condition management subsystem. The remote fault alarm system comprises a remote maintenance service subsystem besides a working condition management subsystem, the remote fault alarm system is formed together, the working condition management subsystem is used for collecting monitoring data of heterogeneous shipborne sensors, converting the monitoring data into body example data, storing and reasoning the body example data, and sending a final result to upper ship support application software (such as a remote maintenance service subsystem) and the like, the remote maintenance service subsystem provides ship maintenance auxiliary decision and working condition knowledge service for shipborne and shore-based remote technicians, the remote maintenance service subsystem and the working condition management subsystem are communicated through a standard Web service interface, and the overall structure of the remote fault alarm system is shown in figure 6.
In one embodiment, the service business logic implemented by the middle tier of the remote service subsystem includes service documentation management, notification management, expert basic information, messaging, and proactive service applications.
Specifically, the remote maintenance service subsystem is implemented by using J2EE JSP/servlet technology as Web application software, and the design mode is MVC. The back-end tier is represented in fig. 6 as an information management database, storing mainly the following information resources: basic equipment data, equipment maintenance records, equipment maintenance plans, signal thresholds, equipment guarantee logs, expert basic information, current busy and idle states of experts, a ship maintenance guarantee expert resource library and the like.
The front-end layer is mainly realized by a front-end interface generation service, and renders a corresponding user interaction interface according to different equipment characteristics (including resolution, memory, CPU processing capacity, an operating system and the like) used by a system user, and the supported equipment can be a PC (personal computer), a tablet computer, a mobile phone or a special PDA (personal digital assistant) and the like.
The middle layer realizes various service business logics of the remote maintenance service subsystem, including maintenance document management, notification management, expert basic information, message sending, active maintenance application and the like. The main functional modules are as follows: (1) device document management: the system is used by shore-based and ship technicians, the technicians can access and modify equipment maintenance record documents through the system, and the read-write permission is specified by a user role; (2) maintenance notification manager: when the central server receives the alarm message, the alarm message can be automatically triggered by the working condition management subsystem or triggered by maintenance application actively sent by shipborne technicians, and contacts ship maintenance support personnel to participate in fault treatment through various communication means including e-mail short messages, WeChat or telephone and the like according to a notification strategy appointed by the central working condition management middleware; (3) managing the expert resume: not only the basic information such as the expertise and maintenance experience of ship maintenance support personnel is saved, but also the current busy and idle states of experts are recorded, and the knowledge inference machine can avoid the experts without idle time when using a notification strategy to contact the experts; (4) service is sent to the maintenance scheme: the shore-based expert sends maintenance support suggestions to ship technicians through the shore-based expert; (5) active maintenance application: when a ship-borne technician encounters a problem, the ship-borne technician can actively send a maintenance application to a shore security center through the ship-borne technician; (6) communication management service: the remote maintenance service subsystem adopts Web service standards (SOAP and WSDL) to interact with external components such as a working condition management subsystem and the like, a bottom database is Mysql, and a short message gateway and an SMTP protocol are needed to be realized for communication management service in order to support means of notifying support personnel such as short message e-mails and the like.
In one embodiment, the condition management middleware is specifically configured to:
generating an equipment field ontology example and a ship field ontology example according to the collected monitoring data;
generating an alarm notification by using an inference machine and an inference rule according to the domain ontology example and the ship domain ontology example, and determining an alarm level;
and sending the alarm notification and the alarm level to the central working condition management middleware.
Specifically, the working condition management subsystem is deployed on a class 2 node and is divided into a working condition management middleware and a central working condition management middleware, wherein the working condition management middleware is installed on a ship state monitoring server, equipment and ship environment data are acquired through monitoring sensors deployed at different measuring point positions of a ship, the acquired data are preprocessed, whether an abnormal condition occurs or not is detected, and the preprocessing process of the working condition management middleware mainly comprises the following steps: step 1: adding the collected data into the device and ship body example, and the step 2: the rule inference machine deduces by using the ontology case, and if an abnormal condition is found, an alarm is given out, and the step 3: the shore based remote condition manager (central condition management middleware) is notified.
In one embodiment, the central condition management middleware is specifically configured to:
detecting the ship fault condition contained in the alarm message and the busy and idle state of the current support personnel stored in the database;
according to the fault state of the ship, the busy and idle states of current support personnel and the triggered alarm level, establishing a related alarm management body example and a related force support body example;
generating a notification strategy by using an inference machine and an inference rule according to the alarm management ontology example and the guarantee strength ontology example;
and send the generated notification policy to the remote service subsystem.
Specifically, the central working condition management middleware is arranged in a ship remote guarantee center, and after receiving an alarm message sent by the ship working condition management middleware, the working process of the central working condition management middleware is as follows in order to form a proper professional support staff team. Step 1: detecting the ship fault condition sent from the alarm message, the busy and idle states of current support personnel stored in a database and the like; step 2: establishing related alarm management and expert management body strength according to the equipment fault state, the expert busy and idle condition and the triggered alarm level; and 3, step 3: making a proper notification strategy by using an inference rule, and a 4 th step: and sending the generated notification strategy to the remote maintenance service subsystem, and completing the subsequent specific notification work by the remote maintenance service subsystem.
Inside the working condition management subsystem, information interaction among all modules is realized in an Observer (Observer) design mode, namely, in an event/interception mode, and the realization mode can ensure loose coupling of the modules inside the system. The central and ship condition management middleware can be realized by means of J2EE Web application programs, and the external interface also adopts Web services.
Example two
Based on the same inventive concept, the second embodiment of the invention provides a ship remote fault alarm method based on a body, which comprises the following steps:
s1: sending a control command through a remote maintenance service subsystem interface, wherein the control command comprises accessing or modifying equipment information, and the equipment information comprises an alarm threshold value and data acquisition parameter configuration;
s2: the remote maintenance service subsystem sends the control command to the central working condition management middleware and forwards the control command to the ship working condition management middleware through the central working condition management middleware;
s3: the ship working condition management middleware controls the ship equipment and the internal environment detection sensor to acquire the data of the ship equipment and the data of the internal environment according to the control command;
s4: the ship working condition management middleware forwards the acquired data to the remote maintenance service subsystem to update equipment record information, and simultaneously sends the acquired data to the body manager module for modifying the equipment field body example and the ship field body example;
s5: the ship working condition management middleware adopts a rule-based inference machine to carry out inference according to the equipment field body example and the ship field body example, and sends a trigger alarm notification to the central working condition management middleware;
s6: the central working condition management middleware generates an alarm management body and a guarantee force body example according to the alarm notice, adopts a rule-based inference machine to carry out inference according to the alarm management body and the guarantee force body example to generate an alarm strategy, and then sends the alarm strategy to the remote maintenance service subsystem
S7: the remote maintenance service subsystem system sends maintenance applications to target objects in an expert list according to the alarm strategy, wherein the expert list is contained in an alarm management body, the alarm management body comprises a notification strategy model, the notification strategy model is an expert queue set, and each expert queue contains an expert list corresponding to members in the ship support network.
Specifically, fig. 7 illustrates a detailed structure of the condition management subsystem, and fig. 8 illustrates a system fault detection and alarm management process.
At S1, the service support technician may access or modify the equipment information via the remote service subsystem interface, and in particular, the technician may modify a monitoring configuration parameter of a ship, such as a scheduling frequency of data collection or an associated alarm threshold. For example, the technician may specify that the monitoring device collect data every 10 minutes. In S2, when the cabin temperature exceeds 45 ℃, a middle-level alarm is triggered, and the remote maintenance service subsystem sends a control command (a command for updating the alarm threshold value and the data acquisition parameter configuration) to the central working condition management middleware, and then the central working condition management middleware forwards the control command to the ship working condition management middleware.
In order to be capable of interactively acquiring information such as frequency or alarm threshold value and the like with external software such as a remote maintenance service subsystem and the like, a Web service interface is provided for a ship working condition management unit of a central working condition management middleware, the Web service interface can be called by the remote maintenance service subsystem, the central working condition management middleware establishes a message queue for each ship working condition management middleware managed by the central working condition management middleware, messages sent from the remote maintenance service subsystem are all routed to the message queue of a target ship, a central working condition client of the ship working condition management middleware periodically polls the ship working condition management unit of the central working condition management middleware to inquire whether new messages exist, and the periodic polling can monitor the operation of the ship working condition management middleware and diagnose whether the connection of a shore base and the ship working condition management middleware is normal. When the periodic polling of a certain ship is not received for a period of time, which indicates that software failure or communication interruption possibly occurs, a corresponding alarm needs to be triggered immediately, and the emergency resource group starts to solve after receiving the alarm notification.
At S3, the central condition client of the ship condition management middleware analyzes the received message content (i.e., control command) and generates a corresponding event, such as a timer event for adjusting the acquisition frequency. And the data acquisition and scheduling module of the ship working condition management middleware is responsible for executing a new timer event, and allocates a corresponding timing trigger to control the frequency of data acquisition from the sensor according to a monitoring scheme in a timer event object.
In S4, the data fusion unit of the ship condition management middleware provides a Web service interface for function invocation, the sensor network invokes it to send newly acquired collected data, and then the data are forwarded to the data distribution unit of the condition agent, and the data distribution unit forwards the data to the remote maintenance service subsystem so as to update the equipment record information and send a message to the condition knowledge base (ontology manager module) so as to modify the equipment and ship environment ontology examples.
At S5, to detect possible faults and generate alarm events, the rule-based inference engine uses the knowledge base to reason, for example if cabin temperature is found to exceed 45 degrees, a medium level alarm automatically triggers an alarm notification module of the ship condition management middleware, and the central condition management middleware is notified of a new alarm event by invoking the alarm management module of the central condition management middleware.
In S6, after receiving the alarm sent by the ship condition management middleware, the alarm management module of the central condition management middleware routes the alarm to the body manager, and creates a fault notification policy. First, newly received instance data, such as attribute values of alarm events (including device codes and alarm levels) and update information of experts (current busy and idle status), is inserted into a knowledge base (consisting of an alarm management ontology and a security force ontology), and then a rule inference engine generates an alarm policy. And the strategy notification module of the central working condition management middleware sends the alarm strategy to the remote maintenance service subsystem.
S7, the remote maintenance service subsystem sends maintenance application to the appropriate object in the expert list according to the alarm strategy.
The main advantages of the invention include:
the system provided by the invention is based on modularization and Web service-oriented system design, and has the main advantages that: (1) the open standardized data format and communication protocol are adopted, so that the system has high expandability and reliability; (2) in the aspect of platform design, Web service standards are adopted to define basic function modules and the mutual relations of the basic function modules; (3) in the aspect of data transmission and storage, a semantic Web technology is adopted to support the development of personalized Web services; (4) and the Web technology can also express ship guarantee knowledge in an ontology paradigm mode, and an ontology rule engine is used for reasoning, so that a final maintenance scheme is generated. The system not only can monitor the ship condition in real time and automatically generate fault alarm, but also supports information sharing and ship information query of ships and shore-based technicians.
Since the method described in the second embodiment of the present invention is a method implemented by the body-based ship remote fault alarm system in the first embodiment of the present invention, a specific implementation form of the method can be known by those skilled in the art based on the system described in the first embodiment of the present invention, and thus, details are not described herein. All the methods implemented by the system according to the first embodiment of the present invention belong to the protection scope of the present invention.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all changes and modifications that fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.
Claims (9)
1. A body-based remote failure alarm system for a ship, comprising:
the working condition management subsystem is used for acquiring monitoring data of the heterogeneous shipborne sensor, converting the acquired monitoring data into body example data, storing and reasoning the body example data and sending a reasoning result to the remote maintenance service subsystem, and specifically comprises a ship end working condition management middleware and a central working condition management middleware, wherein the ship working condition management middleware is a ship working condition manager, the central working condition management middleware is a shore-based working condition manager, the working condition management middleware and the central working condition management middleware comprise a data collector module, a body manager module and a working condition agent module, the data collector module is used for collecting monitoring data of the heterogeneous shipborne sensor, the body manager module is used for storing a body model and an example thereof in a database, a reasoning machine and a rule file based on rules, and the data are stored and inferred according to the body model, The inference engine and the rule file reason the monitoring data to obtain an inference result, and the working condition agent module is used for managing the interaction between the middleware and the remote maintenance service subsystem and sending the inference result to the remote maintenance service subsystem;
the remote maintenance service subsystem is used for sending the inference result to shipborne and shore-based remote technicians and providing ship maintenance auxiliary decision-making and working condition knowledge service, and specifically comprises a rear end layer, a middle layer and a front end layer, wherein the rear end layer is used for storing information resources, the middle layer is used for realizing various service business logics of the remote maintenance service subsystem, and the front end layer is used for generating a user interaction interface;
the body model stored by the body manager module comprises an equipment field body, a ship field body, an alarm management body and a force guaranteeing body;
the inference machine in the body manager module is used for judging whether to send out an alarm or not and determining an alarm level according to the equipment field body and the ship field body, and is also used for determining an informing strategy according to the alarm management body, the guarantee strength body and the determined alarm level;
the ship working condition management middleware controls the ship equipment and the internal environment detection sensor to acquire the data of the ship equipment and the data of the internal environment according to the control command;
the ship working condition management middleware forwards the acquired data to the remote maintenance service subsystem to update equipment record information, and simultaneously sends the acquired data to the body manager module for modifying the equipment field body example and the ship field body example;
the ship working condition management middleware adopts a rule-based inference machine to carry out inference according to the equipment field body example and the ship field body example, and sends a trigger alarm notification to the central working condition management middleware;
the central working condition management middleware generates an alarm management body and a guarantee force body example according to the alarm notification, adopts a rule-based inference machine to carry out inference according to the alarm management body and the guarantee force body example, generates an alarm strategy and sends the alarm strategy to the remote maintenance service subsystem;
and the remote maintenance service subsystem sends maintenance applications to target objects in an expert list according to the alarm strategy, wherein the expert list is contained in an alarm management body, the alarm management body comprises a notification strategy model, the notification strategy model is an expert queue set, and each expert queue contains an expert list corresponding to members in the ship support network.
2. The system of claim 1, wherein the data collector module of the central operations management middleware comprises an alarm management unit and a vessel operations management unit, the vessel operations management unit establishes a message queue for each vessel operations management middleware managed by the vessel operations management unit, and messages sent from the remote maintenance service subsystem are all routed to the message queue of the target vessel; and the alarm management unit is used for routing the alarm to the body manager after receiving the alarm sent by the ship working condition management middleware and creating a fault notification strategy.
3. The system of claim 2, wherein the condition management middleware further comprises a condition client for periodically polling the vessel condition management module of the central condition management middleware for new messages.
4. The system of claim 3, wherein the data collector module of the behavior management middleware comprises a data fusion unit and a data collection scheduling unit, wherein the data collection scheduling unit is configured to execute a timer event and allocate a corresponding timing trigger according to a monitoring scheme in a timer event object to control a frequency of collecting data from the sensor, and the data fusion unit is configured to fuse and forward the collected data.
5. The system of claim 1, wherein the equipment domain ontology includes equipment monitoring data and measurement parameters, the ship domain ontology includes monitoring internal ship environmental parameters including temperature, humidity, smoke, and fire, the alarm management ontology includes maintenance application strategies for ship equipment failure, and the security force ontology includes ship equipment technicians belonging to different organizations.
6. The system of claim 1, wherein the service business logic implemented by the middle tier of the remote service subsystem includes service documentation management, notification management, expert basic information, messaging, and proactive service applications.
7. The system of claim 5, wherein the condition management middleware is specifically configured to:
generating an equipment field ontology example and a ship field ontology example according to the collected monitoring data;
generating an alarm notification by using an inference machine and an inference rule according to the domain ontology example and the ship domain ontology example, and determining an alarm level;
and sending the alarm notification and the alarm level to a central working condition management middleware.
8. The system of claim 7, wherein the central regime management middleware is specifically to:
detecting the ship fault condition contained in the alarm message and the busy and idle state of the current support personnel stored in the database;
according to the fault state of the ship, the busy and idle states of current support personnel and the triggered alarm level, establishing a related alarm management body example and a related force support body example;
generating a notification strategy by using an inference machine and an inference rule according to the alarm management ontology example and the guarantee strength ontology example;
and send the generated notification policy to the remote service subsystem.
9. A ship remote fault alarm method based on a body is characterized by comprising the following steps:
sending a control command through a remote maintenance service subsystem interface, wherein the control command comprises accessing or modifying equipment information, and the equipment information comprises an alarm threshold value and data acquisition parameter configuration;
the remote maintenance service subsystem sends the control command to the central working condition management middleware and forwards the control command to the ship working condition management middleware through the central working condition management middleware;
the ship working condition management middleware controls the ship equipment and the internal environment detection sensor to acquire the data of the ship equipment and the data of the internal environment according to the control command;
the ship working condition management middleware forwards the acquired data to the remote maintenance service subsystem to update equipment record information, and simultaneously sends the acquired data to the body manager module for modifying the equipment field body example and the ship field body example;
the ship working condition management middleware adopts a rule-based inference machine to carry out inference according to the equipment field body example and the ship field body example, and sends a trigger alarm notification to the central working condition management middleware;
the central working condition management middleware generates an alarm management body and a guarantee force body example according to the alarm notification, adopts a rule-based inference machine to perform inference according to the alarm management body and the guarantee force body example to generate an alarm strategy, and then sends the alarm strategy to the remote maintenance service subsystem, wherein the ship working condition management middleware is a ship working condition manager, and the central working condition management middleware is a shore-based working condition manager;
and the remote maintenance service subsystem sends maintenance applications to target objects in an expert list according to the alarm strategy, wherein the expert list is contained in an alarm management body, the alarm management body comprises a notification strategy model, the notification strategy model is an expert queue set, and each expert queue contains an expert list corresponding to members in the ship support network.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010927891.0A CN112383580B (en) | 2020-09-07 | 2020-09-07 | Ship remote fault alarm system based on body |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010927891.0A CN112383580B (en) | 2020-09-07 | 2020-09-07 | Ship remote fault alarm system based on body |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112383580A CN112383580A (en) | 2021-02-19 |
| CN112383580B true CN112383580B (en) | 2022-08-16 |
Family
ID=74586118
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010927891.0A Active CN112383580B (en) | 2020-09-07 | 2020-09-07 | Ship remote fault alarm system based on body |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112383580B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113158335A (en) * | 2021-04-07 | 2021-07-23 | 广东交通职业技术学院 | Ship electric control cylinder oil injection visualization method, system and device and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6446058B1 (en) * | 1999-04-26 | 2002-09-03 | At&T Corp. | Computer platform alarm and control system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105045933B (en) * | 2015-09-08 | 2018-04-24 | 中国人民解放军海军工程大学 | Mapping method between apparel maintenance support information relationship database schema and body |
| CN106875320B (en) * | 2017-02-10 | 2021-01-26 | 武汉理工大学 | Efficient visual analysis method for ship navigation data in cloud environment |
| CN108459574A (en) * | 2018-03-27 | 2018-08-28 | 重庆邮电大学 | It is a kind of that system is managed based on the semantic field device information with OPC UA |
| CN111026046A (en) * | 2019-11-06 | 2020-04-17 | 重庆邮电大学 | Production line equipment fault diagnosis system and method based on semantics |
| CN111178603A (en) * | 2019-12-19 | 2020-05-19 | 重庆邮电大学 | Semantic-based industrial production equipment predictive maintenance system |
-
2020
- 2020-09-07 CN CN202010927891.0A patent/CN112383580B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6446058B1 (en) * | 1999-04-26 | 2002-09-03 | At&T Corp. | Computer platform alarm and control system |
Non-Patent Citations (3)
| Title |
|---|
| 基于PDA与IETM的航空保障辅助维修系统研究;王云翔等;《设备管理与维修》;20170106(第01期);全文 * |
| 王俊龙等.舶装备远程维修技术支援知识库系统研究.《软件导刊》.2018,(第10期), * |
| 舶装备远程维修技术支援知识库系统研究;王俊龙等;《软件导刊》;20181015(第10期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112383580A (en) | 2021-02-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11315024B2 (en) | Cognitive computing systems and services utilizing internet of things environment | |
| CN102652410B (en) | Cloud computing supervision and management system | |
| US9588504B2 (en) | Modular control system | |
| CN111629043B (en) | Cross-platform health management system based on cloud mode | |
| CN110601876A (en) | Intelligent Internet of things platform | |
| CN106961352A (en) | Monitoring system and monitoring method | |
| CA2272609A1 (en) | Software fault management system | |
| US10877867B1 (en) | Monitoring user experience for cloud-based services | |
| KR100720284B1 (en) | Ubiquitous sensor network system and method of event request and response performing in the system | |
| US11606270B2 (en) | Monitoring user experience using data blocks for secure data access | |
| CN112383580B (en) | Ship remote fault alarm system based on body | |
| CN113596150A (en) | Message pushing method and device, computer equipment and storage medium | |
| CN114996085A (en) | Prometheus-based real-time service monitoring method and system | |
| CN114124649B (en) | Gateway communication method, system and gateway equipment based on MQTT and message contract | |
| Abid et al. | A framework for quality of context management | |
| Natalino et al. | Flexible and scalable ML-based diagnosis module for optical networks: a security use case | |
| CN117151669A (en) | Reminding method and device based on workflow engine execution time and electronic equipment | |
| CN101305389A (en) | Independent message stores and message transport agents | |
| CN114866606A (en) | Micro-service management system | |
| Alhosban et al. | Bottom-up fault management in service-based systems | |
| CN113419925A (en) | Monitoring method and system for monitoring and alarming multiple distributed MPP clusters | |
| CN117573907B (en) | Mobile robot data storage method and system | |
| CN114785722B (en) | Monitoring data processing method and device and computer readable storage medium | |
| Guizani et al. | Model-driven architecture for self-adaptive context-aware message routing in pervasive environments | |
| Shah et al. | A QoS Perspective on Exception Diagnosis in Service-Oriented Computing. |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |