CN107578153A

CN107578153A - Machine operates the workshop configuring management method of monitor system

Info

Publication number: CN107578153A
Application number: CN201710742622.5A
Authority: CN
Inventors: 徐泽明; 付自福; 杨佳杰; 夏国淼; 吴宇轩
Original assignee: Shenzhen Augmented Reality Technology Co Ltd
Current assignee: Shenzhen Augmented Reality Technology Co Ltd
Priority date: 2017-08-25
Filing date: 2017-08-25
Publication date: 2018-01-12

Abstract

The application provides the workshop configuring management method of machine operation supervision MOM systems, and the MOM systems include client and server, and methods described includes：The user end to server sends workshop configuration management request；And server asks to return to workshop configuration management successful respond message or workshop configuration management failure response message to the client according to the workshop configuration management, the successful respond message includes workshop configuration information corresponding with the workshop configuration management request, and the failure response message includes error code.

Description

Workshop configuration management method of machine operation monitoring system

Technical Field

The invention relates to the technical field of machine operation.

Background

With the advent of industry 4.0, automation and information sharing in industrial manufacturing processes have become an urgent need. At present, the core of industrial production and manufacturing is still human, and for a novice, it usually takes a long time to learn and become familiar with a new industrial field and grasp a new skill. Moreover, the worker may miss and lose the work.

Disclosure of Invention

The method is used for guiding and/or monitoring the operation of a robot on the machine, and can simply and uniformly carry out configuration management on related machines, equipment, personnel and the like related to the work of an MOM system.

The application provides a workshop configuration management method of a machine operation supervision (MOM) system, wherein the MOM system comprises a client and a server, and the method comprises the following steps:

the client sends a workshop configuration management request to the server; and

and the server returns a work field configuration management success response message or a work field configuration management failure response message to the client according to the work field configuration management request, wherein the success response message comprises work field configuration information corresponding to the work field configuration management request, and the failure response message comprises an error code.

Preferably, the work yard configuration is a work yard, a work yard machine, an MOM device, a worker or a tool, and the work yard configuration management is work yard configuration registration management, work yard configuration cancellation management, work yard configuration update management or work yard configuration query management.

Preferably, the yard configuration management is yard information management, wherein:

the work station configuration management request is a work station information registration request which comprises a work station number, a work station name and a work station address, and the work station configuration information comprises the work station number; or,

the work station configuration management request is a work station information logout request which comprises a work station number, and the work station configuration information comprises a work station number; or

The work station configuration management request is a work station information updating request which comprises a work station number, a work station name and a work station address, and the work station configuration information comprises a work station number; or

The work station configuration management request is a work station information query request which comprises a work station number, and the work station configuration information comprises the work station number, a work station name and a work station address.

Preferably, the plant configuration management is machine information management, wherein:

the workshop configuration management request is a machine information registration request which comprises a machine number and a machine name, and the workshop configuration information comprises the machine number; or,

the workshop configuration management request is a machine information logout request which comprises a machine number, and the workshop configuration information comprises the machine number; or

The workshop configuration management request is a machine information updating request which comprises a machine number and a machine name, and the workshop configuration information comprises the machine number; or

The workshop configuration management request is a machine information query request, wherein the workshop configuration management request comprises a machine number, and the workshop configuration information comprises the machine number and a machine name.

Preferably, the yard configuration management is MOM device information management, wherein:

the work field configuration management request is an MOM equipment information registration request which comprises an equipment number, an equipment role and an equipment name, and the work field configuration information comprises the equipment number; or,

the work station configuration management request is an MOM equipment information logout request which comprises an equipment number, and the work station configuration information comprises the equipment number; or

The work field configuration management request is an MOM equipment information updating request which comprises an equipment number, an equipment role and an equipment name, and the work field configuration information comprises the equipment number; or

The work area configuration management request is an MOM equipment information query request, wherein the MOM equipment information query request comprises an equipment number, and the work area configuration information comprises the equipment number, an equipment role and an equipment name.

Preferably, the yard configuration management is worker information management, wherein:

the work place configuration management request is a worker information registration request which comprises a worker number, and the work place configuration information comprises the worker number; or,

the work station configuration management request is a worker information logout request which comprises an equipment number, and the work station configuration information comprises the equipment number; or

The workshop configuration management request is a worker information updating request which comprises a worker number and a worker name, and the workshop configuration information comprises an equipment number; or

The workshop configuration management request is a worker information query request, wherein the worker information query request comprises a worker number, and the workshop configuration information comprises the worker number and a worker name.

Preferably, the client is an MOM client, the MOM client is a wearable intelligent device, and the server is an MOM root server, a state modeling server, a state supervision server, an operation modeling server or an operation supervision server.

Preferably, the client is an MOM root server, a state modeling server, a state supervision server, an operation modeling server or an operation supervision server, and the server is an MOM database server or a cloud server.

Preferably, the client is a wearable intelligent device and is used for receiving a machine operation specification and prompting a three-dimensional model or animation generated according to the machine operation specification to a user.

Preferably, the wearable smart device is virtual reality/augmented reality glasses.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only 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 inventive exercise.

Fig. 1 illustrates a plant configuration management method according to an embodiment of the present application;

FIG. 2 illustrates a machine operation guidance system of an embodiment of the present application;

FIG. 3 is a block diagram illustrating a machine operation model used to describe machine operation specifications in one embodiment of the present application.

Detailed Description

Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar components or components having the same or similar functions throughout. The embodiments described below with reference to the drawings are illustrative and intended to be illustrative of the invention and are not to be construed as limiting the invention.

In the description of the present invention, it is to be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", and the like, indicate orientations and positional relationships based on those shown in the drawings, and are used only for convenience of description and simplicity of description, and do not indicate or imply that the device or component in question must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be considered as limiting the present invention.

Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present invention, "a plurality" means two or more unless specifically defined otherwise.

In the present invention, unless otherwise expressly specified or limited, the terms "mounted," "connected," "secured," and the like are to be construed broadly and can, for example, be fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; the two components can be directly connected or indirectly connected through an intermediate medium, and the two components can be communicated with each other. The specific meanings of the above terms in the present invention can be understood by those skilled in the art according to specific situations.

In the present invention, unless otherwise expressly stated or limited, "above" or "below" a first feature means that the first and second features are in direct contact, or that the first and second features are not in direct contact but are in contact with each other via another feature therebetween. Also, the first feature being "on," "above" and "over" the second feature includes the first feature being directly on and obliquely above the second feature, or merely indicating that the first feature is at a higher level than the second feature. A first feature being "under," "below," and "beneath" a second feature includes the first feature being directly under and obliquely below the second feature, or simply meaning that the first feature is at a lesser elevation than the second feature.

The present invention will be described in further detail with reference to the following detailed description and accompanying drawings.

The application provides a Machine Operation Monitoring (MOM) system, which can be widely applied to the Operation of Machine equipment in the industries of production, manufacturing, aviation, automobile, energy and the like. In this application, the machine operation site is referred to as a work yard. Operations on the machine include, but are not limited to, running, disassembling, assembling, repairing, inspecting, etc. the machine.

Referring to fig. 1, an embodiment of the present application provides a method for factory configuration management of a machine operation supervision MOM system, where the MOM system includes a client and a server, and the method includes:

s1, the client sends a workshop configuration management request to the server; and

and S2, the server returns a work field configuration management success response message or a work field configuration management failure response message to the client according to the work field configuration management request, wherein the success response message comprises work field configuration information corresponding to the work field configuration management request, and the failure response message comprises an error code.

Preferably, the work yard configuration is a work yard, a work yard machine, an MOM device, a worker or a tool, and the work yard configuration management is work yard configuration registration management, work yard configuration cancellation management, work yard configuration update management or work yard configuration query management. Wherein, the worker refers to a person using the MOM device, and comprises an operation worker and a coach. The coach refers to a worker who performs demonstration of machine operation or who calibrates a normal and abnormal state of the equipment. MOM device refers to an IP device that communicates in compliance with the MOM protocol, which is an application layer protocol in the OSI seven layer protocol model of the internet.

In this application, a client and a server are relative terms, for example, the client is an MOM client, and the server is an MOM root server, a state modeling server, a state supervision server, an operation modeling server, or an operation supervision server. Or the client is an MOM root server, a state modeling server, a state monitoring server, an operation modeling server or an operation monitoring server, and the server is an MOM database server or a cloud server.

FIG. 2 illustrates a machine operation guidance system according to another embodiment of the present invention. The system comprises a client device 10, a function server 12, a database server 14 and a root server 16. The function server 12 may include an operation modeling server 122, an operation supervision server 124, a state modeling server 126, and a state supervision server 128, among others. Database server 14 may deploy an operation specification database 142, an operation records database 144, a state reference database 146, and a state records database 148. It is to be understood that the above servers are functionally distinct and may all be deployed on the same physical server. In practice, the servers may be implemented as different physical servers, wherein the function server 12 is a computation-intensive server and the database server 14 is an input-output-intensive server. The function server 12 and the database server 14 register their own functions with the root server 16.

Preferably, in the present application, the function server 12, the database server 14 and the root server 16 are all fog servers, and in the same factory, the MOM client 102 communicates with the fog servers and with different fog servers through a local area network (e.g., an IP network). Multiple clients 102 and multiple fog servers are allowed to coexist in the same local area network. A client 102 communicates with only one fixed fog server for a period of time.

A plant may comprise a plurality of customer premises devices 10. The customer premises device 10 is used for human-computer interaction with the user. From a product form perspective, the wearable smart device may include, but is not limited to, MOM glasses (which may be virtual reality/augmented reality glasses, for example), MOM gloves, MOM watches, MOM bracelets, or other MOM wearable devices. Functionally, the client device 10 may include, but is not limited to, an image input device, an image output device, a voice input device, a voice output device, a text input device, a text output device, a head tracking device, a gesture tracking device, an eye tracking device, a bone tracking device, and other functional modules. The image input device is used for acquiring images, and can be a camera of MOM glasses, for example. The image output device is used for displaying graphics and images, and can be an augmented reality screen of MOM glasses. The voice input device is used for voice acquisition, and may be, for example, a miniature microphone (microphone) of MOM glasses. The voice output device is used for outputting voice, and can be a loudspeaker of MOM glasses. The text input device may be a virtual keyboard or a physical man-machine interaction device, for example, command text may be input through a bracelet. The text output device is used for outputting text, and can be an augmented reality screen of MOM glasses. The head gesture tracking device is used for recognizing and tracking the head gesture and inputting the head gesture information to the MOM client 102. The gesture tracking device is used for recognizing and tracking gesture actions and inputting gesture information to the MOM client 102. The eyeball tracking device is used for identifying and tracking eyeball action and inputting eyeball action information to the MOM client 102. The bone tracking device identifies and tracks bone motion and inputs bone motion information to the MOM client 102. The functional module can be arranged in each wearable device.

Each customer premises device 10 comprises all wearable smart devices with which a worker is equipped, which may be referred to as MOM configuration of the worker. A worker may be equipped with multiple wearable devices, such as a pair of glasses, two gloves, a watch. If there are multiple MOM wearable devices in a worker's MOM configuration, one of them will act as a MOM client 102 (also called client 102) as the hub for information aggregation and information distribution for the communication between the client device 10 and the server, and the other wearable smart devices 104 are connected to the client 102. Preferably, the MOM glasses may serve as the client 102. Other wearable smart devices 104 and client 102 may communicate via bluetooth or near field communication protocols.

Preferably, the system of the present application may further include a cloud server 40. The cloud server 40 and the root server 16 of each workshop can communicate through the wide area network, collect the working data of the client 102 in real time, and perform related analysis by using a big data technology. In a wide area network, where multiple cloud servers 40 are allowed to exist, the root server 16 is in a many-to-one relationship with the cloud servers 40.

The MOM system of this embodiment can be implemented by a MOM protocol: collecting state information of a machine, and generating a machine state reference; monitoring the current state of the machine, and alarming when the equipment is abnormal; collecting machine operation information of workers to generate a machine operation specification; outputting machine operation specification information, and supervising the machine operation of workers; inquiring tool information; managing machine operating specifications; managing machine operation records.

The MOM system of this embodiment can also be implemented by a MOM protocol: MOM protocol information is transmitted among MOM devices to realize self-organization of the MOM devices and management of workshop configuration information. Preferably, the work yard configuration is a work yard, a work yard machine, an MOM device, a worker or a tool, and the work yard configuration management is work yard configuration registration management, work yard configuration cancellation management, work yard configuration update management or work yard configuration query management. The following is described by way of a specific example.

Preferably, the MOM yard can be managed on the cloud server 40, including registering, deregistering, updating, or querying yard information.

When registering new work yard information, the root server 16 sends a work yard information registration request to the cloud server 40, and the information may include a work yard number, a work yard name, and a work yard address. The cloud server 40 sends a work place information registration success or failure response message to the root server 16, where a work place number is returned in the success response message, and a work place number and an error code are returned in the failure response message.

When logging off the work place information, the root server 16 sends a work place information logging-off request to the cloud server 40, and the work place number may be included in the message. The cloud server 40 sends a work field information logout success or failure response message to the root server 16, where a work field number is returned in the success response message and a work field number and an error code are returned in the failure response message.

When the work place information is updated or modified, the root server 16 sends a work place information update request to the cloud server 40, and the information may include a work place number, a work place name, and a work place address. The cloud server 40 sends a work field information update success or failure response message to the root server 16, where a work field number is returned in the success response message, and a work field number and an error code are returned in the failure response message.

When the work place information is queried, the root server 16 sends a work place information query request to the cloud server 40, where the information may include a work place number. The cloud server 40 sends a work area information query success or failure response message to the root server 16, where a work area number, a work area name, and a work area address may be returned in the success response message, and a work area number and an error code may be returned in the failure response message.

Preferably, machine information may also be managed on root server 16, including registering, deregistering, updating, or querying machine information.

When registering a new machine, client 102 sends a machine information registration request to root server 16, which may include a machine number and a machine name. The root server 16 sends a machine information registration success or failure response message to the client 102, which may return a machine number in the success response message and a machine number and an error code in the failure response message.

When logging off machine information, the client 102 sends a machine information log-off request to the root server 16, which may include a machine number. The root server 16 sends a machine information logoff success or failure reply message to the client 102, where the machine number may be returned in the success reply message and the machine number and error code in the failure reply message.

When updating machine information, the client 102 sends a machine information update request to the root server 16, which may include a machine number and a machine name. The root server 16 sends a machine information update success or failure response message to the client 102, where the machine number may be returned in the success response message and the machine number and error code in the failure response message.

When querying for machine information, the client 102 sends a machine information query request to the root server 16, which may include a machine number. The root server 16 sends a machine information query success or failure response message to the client 102, where the machine number and machine name may be returned in the success response message and the machine number and error code in the failure response message.

Preferably, the MOM devices are also managed on the root server 16, including registering, deregistering, updating, or querying MOM device information.

When registering new MOM device information, the client 102 sends a device information registration request to the root server 16, which may include a device number, a device role, and a device name. The root server 16 sends a device information registration success or failure response message to the client 102, where the device number may be returned in the success response message and the device number and error code in the failure response message.

A plurality of protocol roles can be set in the system, and each protocol role has a corresponding protocol role number. In one particular example, the protocol roles may include, for example, an MOM cloud server, an MOM root fog server, an operation modeling server, an operation monitoring server, a state modeling server, a state monitoring server, a database fog server, an MOM client, an image input terminal, a voice input terminal, a text input terminal, an image output terminal, a voice output terminal, a text output terminal, a head tracking terminal, a gesture tracking terminal, an eye tracking terminal, a bone tracking terminal, and the like. Multiple protocol roles may be deployed on the same physical device. For example, a pair of glasses can simultaneously act as an MOM client, an image input terminal, a voice input terminal, a text input terminal, an image output terminal, a voice output terminal, a text output terminal, and a physical server can simultaneously act as an MOM root fog server, an operation modeling server, an operation supervision server, a state modeling server, a state supervision server, and a database fog server.

When the MOM device information is logged off, the client 102 sends a device information logout request to the root server 16, where the message may include a device number. The root server 16 sends a device information logoff success or failure response message to the client 102, where the device number may be returned in the success response message and the device number and error code in the failure response message.

When updating MOM device information, the client 102 sends a device information update request to the root server 16, where the message may include a device number, a device role, and a device name. The root server 16 sends a device information update success or failure response message to the client 102, where the device number may be returned in the success response message and the device number and error code in the failure response message.

When inquiring MOM device information, the client 102 sends a device information inquiry request to the root server 16, where the message may include a device number. The root server 16 sends a device information query success or failure response message to the client 102, where the device number, device role, and device name may be returned in the success response message and the device number and error code may be returned in the failure response message.

Preferably, worker information may also be managed on root server 16, including registering, deregistering, updating, or querying worker information.

When registering new worker information, client 102 sends a worker information registration request to root server 16, which may include a worker number and a worker name. Root server 16 sends a worker information registration success or failure response message to client 102, where the worker work number may be returned in the success response message and the worker work number and error code may be returned in the failure response message.

When logging out worker information, client 102 sends a worker information log-out request to root server 16, which may include a worker job number. The root server 16 sends a worker information logout success or failure response message to the client 102, where a worker work number may be returned in the success response message and a worker work number and an error code may be returned in the failure response message.

When updating worker information, client 102 sends a worker information update request to root server 16, which may include a worker job number and a worker name. Root server 16 sends a worker information update success or failure response message to client 102, where the worker work number may be returned in the success response message and the worker work number and error code may be returned in the failure response message.

When querying worker information, client 102 sends a worker information query request to root server 16, which may include a worker number. Root server 16 sends a worker information query success or failure response message to client 102, where the worker work number and worker name may be returned in the success response message and the worker work number and error code may be returned in the failure response message.

In the application, self-organization of the MOM equipment can be realized through information interaction among the MOM equipment, and the self-organization comprises MOM equipment broadcasting, MOM equipment online, MOM equipment offline, server online information query and server online list query.

Before the clients (including the MOM client 102, the state modeling server 126, the state monitoring server 128, the operation modeling server 122 or the operation monitoring server 124) are online, the clients broadcast notification messages in the local area network of the workplace to inform the roles and IP addresses of the clients, and the notification messages comprise device numbers, device roles and device IPs. After receiving the broadcast notification message, the root server 16 stores the corresponding work field MOM device information or writes the device information into a local memory database or work field MOM device database, where the device information includes the protocol role of the device, whether the device is on-line, the IP address, etc., and sends a client broadcast notification success or failure response message to the work field MOM device, returns the device number and the device IP of the root server in the success response message, and returns the device number and the error code in the failure response message.

When a client (including the MOM client 102, the state modeling server 126, the state supervision server 128, the operation modeling server 122 or the operation supervision server 124) is online, a client online notification message is sent to the root server 16, wherein the message includes a device number, a device role and a device IP. After receiving the client online notification message, the root server 16 stores the corresponding work field MOM device information or writes the information into a local memory database or work field MOM device database, sends a client online notification success or failure response message to the work field MOM device, returns a device number and a device IP of the root server in the success response message, and returns a device number and an error code in the failure response message.

When a client (including the MOM client 102, the state modeling server 126, the state supervision server 128, the operation modeling server 122, or the operation supervision server 124) goes offline, a client offline notification message is sent to the root server 16, where the message includes a device number. After receiving the offline notification message from the client, the root server 16 stores the corresponding work field MOM device information or writes the information into a local memory database or work field MOM device database, sends an offline notification success or failure response message from the client to the work field MOM device, returns a device number in the success response message, and returns a device number and an error code in the failure response message. If the client does not receive the reply message of the root server 16, the client offline notification message is retransmitted.

Client 102 may also query root server 16 whether a certain yard server is online. In specific implementation, the client 102 sends a factory server online information query request to the root server 16, where the request includes a server number, and the root server 16 sends a server online information query success or failure response message to the client 102, where the device number, the device role, and the device IP of the queried server may be returned in the success response message, and the device number and the error code of the queried server may be returned in the failure response message.

The client 102 may also query the root server 16 for a list of online servers for a device role. In a specific implementation, the client sends a server online list query request to the root server 16, where the request includes a device role. The root server 16 sends a server online list query success or failure response message to the client 102, where the online server list information of the queried device role may be returned in the success response message, the list information includes the device role, the device number and the device IP, and the queried device role and the error code may be returned in the failure response message.

The client 102 is configured to collect operation conditions of the machine by workers collected by the function modules and/or machine operation commands input by the collected workers, and the like, and send the collected operation conditions of the machine and/or the collected machine operation commands and the like to the outside after being collected as first machine operation information, so that the server can supervise the operation of the workers according to the first operation information, and after a request for operating the machine is sent, receive machine operation specifications from the server and prompt the workers through the corresponding function modules, so that the workers can operate the machine under the guidance of the operation specifications. Further, the client 102 may also be configured to collect and send out machine state information. Machine state information includes, for example, but is not limited to, a snapshot of the current state of the machine as it is being polled. Preferably, the machine operation specification includes a plurality of three-dimensional models or animations arranged according to a specific rule, which can be displayed to the user via VR/AR glasses, and can also include information such as voice, text, pictures, and the like.

In one example, the machine operation specification may be described by the machine operation model shown in FIG. 3. In the machine operation model, the assembly and the overhaul of the whole machine equipment are one operation, one-time assembly, overhaul or other complete functional operations of the machine equipment are one task, one operation consists of a series of tasks, and one task consists of a series of task steps. A task step includes actions taken by the foot, eyes, and hands of a worker completing a task. In this manner, machine operation specifications may include job specifications, task specifications, step specifications, and action specifications. One job specification corresponds to one MOM model file (. MOM file), and the system loads one MOM model file at a time. The machine operation model is described in more detail later herein.

In this embodiment, the client 102 sends an operation machine request, the root server 16 accesses the operation specification database 142 to obtain a machine operation specification according to the operation machine request, and the client 102 receives and prompts the machine operation specification to the user. Root server 16 may obtain the machine operation specification by sending a query machine operation specification instruction to operation specification database 142 and receiving a feedback message from operation specification database 142 indicating that the query machine operation specification was successful. Preferably, the instruction for querying the machine operation specification at least comprises an instruction for querying the action specification, the instruction for querying the action specification comprises a task specification number, a step specification number and an action specification number, and correspondingly, the feedback message indicating that the instruction for querying the machine operation specification is successful comprises a feedback message indicating that the instruction for querying the action specification is successful, the feedback message comprises action specification information, and the action specification information comprises an action name, an action starting position, an action ending position, a geometric motion and an operation tool. The operation specification instruction for inquiring the machine may further include an operation specification inquiry instruction, a task specification inquiry instruction, and an action specification inquiry instruction, and before the action specification inquiry instruction, a task specification inquiry list instruction, a task specification inquiry instruction, a step specification inquiry list instruction, a step specification inquiry instruction list inquiry, and an action specification inquiry instruction list may be used to obtain a task specification number, a step specification number, and an action specification number required in the action specification inquiry instruction. These query instructions and corresponding feedback instructions can be implemented in the same way with reference to the relevant content of the later operational modeling server part, and are not repeated here.

A modeling terminal 20 may also be configured in the system. The modeling terminal 20 can be used by a coach, can be a remote terminal having the same or similar configuration as the client device 10, or can be served by a client device 10 in the system. The coach conducts demonstration operation through the modeling terminal 20, and the modeling terminal 20 collects collected operation conditions of the coach and/or input operation commands and the like into second machine operation information and sends the second machine operation information to the outside; meanwhile, the modeling terminal 20 is also used for collecting and sending out machine state reference information. The operating condition of the trainer includes, for example, but not limited to, a snapshot of the operation of the trainer. Machine state reference information includes, for example and without limitation, a machine state normal snapshot and/or a machine state abnormal snapshot.

The operation modeling server 122 is configured to generate a machine operation specification from the second machine operation information. For example, image features in a snapshot of the operation of the trainer can be extracted to generate machine operation specifications. The machine operation specifications generated by operation modeling server 122 may be stored in operation specification database 142.

In one embodiment, the machine operation specification may be described by a machine operation model. Referring also to fig. 3, according to an embodiment, in the machine operation model, the assembling and the overhauling of the whole machine equipment are performed as one operation, and one-time assembling, overhauling or other complete operation of the machine equipment is performed as one task, wherein one operation is composed of a series of tasks and one task is composed of a series of task steps. A task step includes actions taken by the foot, eyes, and hands of a worker completing a task. In this manner, machine operation specifications may include job specifications, task specifications, step specifications, and action specifications. One job specification corresponds to one MOM model file (. MOM file), and the system loads one MOM model file at a time.

The action taken by the foot may be described in terms of a travel route. The action taken by the eye can be described in terms of viewing angle and operational viewport. If the robot is used for replacing a human to carry out machine operation and inspection, under the condition that no obstacle exists, the traveling route can be the translational motion of the robot, and the observation angle can be changed along with the rotational motion of the robot.

The viewing angle may include three sets of content. The first group is the position of the camera in world coordinates, the second group is the position of the object at which the camera lens is aimed in world coordinates, and the third group is the direction of the camera up direction in world coordinates. If not specifically required, the viewing angle may not be described, but is assumed to be from a clear viewing angle. The best viewing angle can be chosen as the viewing angle.

A task step is performed for an operation viewport, which is the scene the operator sees when performing a snapshot of the action. One device component can correspond to a plurality of different operation view ports; an operation view port may contain a plurality of device components.

The actions taken by the hand are described in terms of a snapshot of the action. One task step may include a series of action snapshots. One action snapshot is carried out for one action position pair, and only one geometric motion is carried out; an action position pair includes a start position and an end position. If the action uses a tool, the position may be the position of the center of gravity of the tool; if no tool is used, the position may refer to the position of the center of gravity of the operated device part. The geometric movement may be a translation or a rotation. An action snapshot may also have time, tools, repetition times, etc. information. The action snapshot may not be assigned a time, which indicates that there is no time limit for the action; a time may also be specified for the action snapshot, which may refer to the longest duration of the action; two times may also be specified for the action snapshot, which may be the longest duration and the shortest duration of the action. Preferably, at most one tool is used in one action snapshot. If an operation is completed by using two tools simultaneously, one in the left hand and one in the right hand, the operation is described by decomposing into two action snapshots. The number of repetitions represents the number of repetitions of the motion with the motion position pair, geometric motion, time, tool remaining unchanged.

Preferably, the operational modeling server comprises a processor and a memory having stored therein computer program code configured to cause the operational modeling server to at least:

receiving an operation specification creating instruction; and

and creating a machine operation specification according to the operation specification instruction.

Wherein the machine operation specification comprises part or all of a job specification, a task specification, a step specification and an action specification, and the motion specification comprises a three-dimensional model and/or an animation.

Preferably, the receiving of the create operation specification instruction includes part or all of the following: receiving a job specification creating instruction, receiving a task specification creating instruction, receiving a creating step specification creating instruction, receiving an operation area creating instruction and receiving an action specification creating instruction.

Accordingly, the creating of the machine operation specification according to the operation specification instructions comprises some or all of the following: creating a job specification according to the job specification creating instruction, creating a task specification according to the task specification creating instruction, creating a step specification according to the creating step specification instruction, creating an operating area according to the operating area creating instruction, and creating an action specification according to the action specification creating instruction, wherein the action specification comprises the three-dimensional model and/or the animation.

The create job specification command may include a job name and a creator job number, and may also include a job specification number. When the job specification number is not included in the job specification creating instruction, the job specification number can be automatically generated by the system. The job specification created according to the create job specification instruction may include information such as a job specification number, a job name, a creator job number, and a creation time.

The creating task specification instruction can include a task name, and the operation modeling server can create the task specification under the currently loaded operation of the system according to the creating task specification instruction. The created task specification may include a task specification number and a task name.

The create step specification instruction may include a task specification number, a step specification name, and a viewport image. In the application, each step operates the components within a fixed machine view port range, and the operation view ports and the steps have a one-to-one correspondence relationship.

The instruction for creating the operation area may include a task specification number, a step specification number, and operation area information, and the operation area information may include a vertex x-axis coordinate, a vertex y-axis coordinate, a length, a width, and the like. The operation area is used for calibrating a positioning frame of the target position and is used for assisting the positioning and the identification of the target object.

The created action specification instruction may include a task specification number, a step specification number, and action specification information, and the action specification information may include an action name, an action start position, an action end position, a geometric motion, an operation tool, and the like.

Preferably, the computer program code is further configured to cause the operation modeling server to send a feedback message of success or failure in creating the machine operation specification.

The feedback message indicating the success of creating the machine operation specification may include the number of the corresponding operation specification. Error codes may be included in the feedback message indicating a failure to create a machine operating specification, and different error codes may indicate different causes of errors.

Preferably, the computer program code is further configured to cause the operational modeling server to: receiving an operation specification management instruction, managing the machine operation specification according to the operation specification management instruction, and sending a feedback message indicating success or failure of managing the machine operation specification. Preferably, the management machine operation specification may include some or all of the following: deleting the machine operation specification, modifying the machine operation specification and inquiring the machine operation specification.

In one embodiment, the delete job specification instruction may include a job specification number. The operation specification modification instruction may include an operation name and an operation specification number, optionally, the operation specification modification instruction may not include the operation specification name, and at this time, the operation specification number corresponding to the mom file currently loaded by the system may be defaulted. The query job specification instruction may include the job specification number, or optionally may not include the job specification number, and at this time, the default may be the job specification number corresponding to the mom file currently loaded by the system.

The delete task specification instruction may include a task specification number. The modification task specification instruction may include a task name and a task specification number. The query task specification instruction may include a task specification number.

The delete step specification instruction may include a task specification number and a step specification number. The modify step specification command may include a task specification number, a step name, and a viewport image. The query step specification instruction may include a task specification number and a step specification number.

The delete operating region instruction may include a task specification number, a step specification number, and an operating region number. The operation area modifying instruction can comprise a task specification number, a step specification number, an operation area number and operation area information, wherein the operation area information comprises a vertex x-axis coordinate, a vertex y-axis coordinate, a length and a width. The query step specification instruction may include a task specification number, a step specification number, and an operation area number.

The delete action specification instruction may include a task specification number, a step specification number, and an action specification number. The modified action specification instruction can include a task specification number, a step specification number, an action specification name and action specification information, and the action specification information includes part or all of an action name, an action starting position, an action ending position, a geometric motion and a used tool. The query action specification instruction may include a task specification number, a step specification number, and an action specification number.

Further, the feedback message indicating the success of managing the machine operation specification may include a corresponding operation specification number. The feedback message indicating the failure of managing the machine operation specification may include a corresponding operation specification number and error codes, and different error codes may indicate different error reasons.

Preferably, a job specification list, a step view port image list, an operation area list or an action specification list can be queried.

The operation supervision server 124 is configured to supervise the actual operation of the machine by the worker in accordance with the machine operation specifications, for example, the first machine operation information issued by the client 102 may be compared to the machine operation specifications stored in the operation specification database 142. More specifically, the image features in the worker's snapshot of operation may be compared to the image features in the trainer's snapshot of operation in the machine operation specification to obtain the operation supervision result. For the operation supervision result, the system may respond accordingly, for example, if the operation is found out to be out of specification, a reminder may be given to the user, and the like. The first machine operation information issued by the client 102 or the result of supervision by the operation supervision server 124 may be stored in the operation record database 144. The first machine operation information may be converted into a create operation record instruction to generate a corresponding operation record for storage.

The preferred operation monitoring server 124 comprises a processor and a memory having stored therein computer program code configured to cause the operation monitoring server to at least:

receiving an operation record creating instruction; and

and creating a machine operation record according to the operation record instruction, wherein the machine operation record comprises a finished image. Machine operation records may be created in the operation records repository 144.

Wherein, the instruction for creating the machine operation record can be from a client or a root server. The machine operation record comprises part or all of a job record, a task record, a step record and an action record, and the job record, the task record, the step record and the action record respectively have corresponding completion images or videos.

Preferably, the receiving of the instruction for creating the machine operation record includes the following part or all: receiving a job record creating instruction, receiving a task record creating instruction, receiving a step record creating instruction and receiving an action record creating instruction.

Accordingly, the creating of the machine operation record according to the create machine operation record instruction includes part or all of the following: creating a job record according to the job record creating instruction, creating a task record according to the task record creating instruction, creating a step record according to the step record creating instruction, and creating an action record according to the action record creating instruction.

The creating operation record instruction can comprise a worker number, an operation number and operation record information, wherein the operation record information comprises an operation name, a start time, an end time, a duration, a finished image and the number of errors. The number of the job may not be included, and at this time, the number of the job corresponding to the mom file currently loaded by the system may be defaulted.

The task record creating instruction can comprise a worker number, a job number, a task number and task record information, wherein the task record information comprises a task name, start time, end time, duration, a finished image and error number. The job number corresponding to the mom file can be defaulted at this time, and the operation supervision server can create a task specification under the job currently loaded by the system.

The creating step task instruction can comprise a worker number, a job number, a task number, a step number and step record information, wherein the step record information comprises a step name, a start time, an end time, a duration, a finishing image and error information. The number of the job may not be included, and at this time, the number of the job corresponding to the mom file currently loaded by the system may be defaulted. The error information includes the number of errors and an error list, and the error list includes error descriptions and images.

The created action record instruction can comprise a worker number, a job number, a task number, a step number, an action number and action record information, wherein the action record information comprises an action name, a starting time, an ending time, a duration, a completion image and error information. The number of the job may not be included, and at this time, the number of the job corresponding to the mom file currently loaded by the system may be defaulted. The error information includes the number of errors and an error list, and the error list includes error descriptions and images.

Preferably, the computer program code is further configured to cause the operation supervision server to send a feedback message of success or failure in creating the machine operation record to inform the client of success or failure in creating the record.

The feedback message indicating that the creation of the machine operation record is successful may include the number of the corresponding operation record. Error codes may be included in the feedback message indicating failure to create a machine operation record, and different error codes may indicate different causes of errors.

Preferably, the computer program code is further configured to cause the operation supervision server to: receiving an operation record management instruction, managing the machine operation record according to the operation record management instruction, and sending a feedback message indicating success or failure of managing the machine operation record. Preferably, the management machine operation record may include some or all of the following: deleting the machine operation record and inquiring the details of the machine operation record.

In one embodiment, the delete job record command and the query job record details command may include a job record number. The task record number can be included in the task record deleting instruction and the task record detail inquiring instruction. The step record number may be included in the delete step record instruction and the query step record details instruction. The delete action record instruction and the query action record details instruction may include an action record number.

The portion of the protocol data in the feedback message indicating that the deletion of the job, task, step, or action record was successful may be null. The feedback message indicating the failure to delete the machine operation record may include an operation record number and an error code, for example, the feedback message indicating the failure to delete the job record may include a job record number and an error code. The feedback message indicating the failure to delete the task record may include a task record number and an error code. The feedback message indicating the failure of deleting the step record may include a step record number and an error code. The feedback message indicating the failure to delete the action record may include an action record number and an error code.

The feedback message indicating that the query of the details of the machine operation record is successful may include an operation record number and operation record information.

The feedback message indicating failure to query the machine operation record details may include an operation record number and an error code.

Preferably, the operation record list can be inquired.

The operation supervision server can also receive a query task record list instruction from the client or the root server to query a task record list of a certain job record. The query task record list instruction may include a job record number. The operation supervision server may send a feedback message indicating success or failure of querying the task record list. The message indicating the success of the query may include a task record list, where the task record list includes a task record number, a task name, a start time, an end time, a duration, and a number of errors. The message indicating the query failure may include a job record number and an error code.

The operation supervision server may also receive a query step record list instruction from the client or the root server to query a step record list of a certain task record. The query step record list instruction may include a task record number. The operation supervision server may send a feedback message indicating success or failure of the query step record list. The message indicating the query success may include a step record list, where the step record list includes a step record number, a step name, a start time, an end time, a duration, and an error number. The message indicating the query failure may include a task record number and an error code.

The operation supervision server can also receive an instruction of inquiring the action record list from the client or the root server so as to inquire the action record list recorded in a certain step. The inquiry action record list instruction can include a step record number. The operation supervision server may send a feedback message indicating success or failure of querying the action record list. The message indicating the success of the query may include a step record number and an action record information list, where the action record information includes an action record number, an action name, a start time, an end time, a duration, and an error number. The message indicating the query failure may include a step record number and an error code.

The state modeling server 126 is configured to generate a machine state reference file according to the machine state reference information sent by the modeling terminal 20, for example, the image features of the machine state normal snapshot and/or the machine state abnormal snapshot may be extracted to generate the machine state reference file. The machine state reference file may be stored in a state reference database 146.

The state supervisor server 128 is configured to supervise the current state of the machine operated by the worker in accordance with a machine state reference file, for example, machine state information sent by the client 102 may be compared to a machine state reference file stored in the state reference database 146. More specifically, the image characteristics in the machine current normal state snapshot can be compared with the image characteristics in the machine state normal/abnormal snapshot to obtain the state supervision result. For the status supervision result, the system may respond accordingly, for example, if the machine status is found to be abnormal, alert the user, etc. Machine state information issued by the client 102 or the results of state supervision by the state supervision server 128 may be stored in the state record database 148.

A recording terminal 30 may also be provided in the system and may be in communication with the operation supervision server 124 and/or the status supervision server 128. The trainer can query the worker for machine operation and/or machine equipment status records via the recording terminal 30.

Each workplace has a root server 16, and the root server 16 is the core of the workplace and has a caching function and a load balancing function. In order to respond to the client 102 in a timely manner, the root server 16 caches data read in from other servers. When the root server 16 finds a server overloaded, it will distribute the requests of the tasks to other homogeneous servers. Root server 16 is configured to access operation specification database 142 to obtain machine operation specifications, which are provided to clients 102; receiving the first machine operation information sent by the client 102, providing the first machine operation information to the operation monitoring server 124, and storing the first machine operation information in the operation record database 144; machine state information sent by the client 102 is received, provided to the state supervision server 128, and may be stored to the state record database 148.

The machine operation monitoring system in the embodiment of the application can assist the machine operation of workers, improve the production efficiency and reduce the operation error rate. In addition, the operation of the worker can be supervised and fed back.

In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples" or the like, mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

The foregoing is a more detailed description of the present invention that is presented in conjunction with specific embodiments, and the practice of the invention is not to be considered limited to those descriptions. It will be apparent to those skilled in the art that a number of simple derivations or substitutions can be made without departing from the inventive concept.

Claims

1. A method for factory configuration management of a machine operation supervision, MOM, system, the MOM system including a client and a server, the method comprising:

the client sends a workshop configuration management request to the server; and

2. The method of claim 1, wherein the yard configuration is a yard, a yard machine, a MOM device, a worker, or a tool, and the yard configuration management is a yard configuration registration management, a yard configuration logout management, a yard configuration update management, or a yard configuration query management.

3. The method of claim 1, wherein the yard configuration management is yard information management, wherein:

4. The method of claim 1, wherein the plant configuration management is machine information management, wherein:

5. The method of claim 1, wherein the yard configuration management is MOM device information management, wherein:

6. The method of claim 1, wherein the yard configuration management is worker information management, wherein:

7. The method of any of claims 1 to 6, wherein the client is a MOM client, the MOM client is a wearable smart device, and the server is a MOM root server, a state modeling server, a state supervision server, an operation modeling server, or an operation supervision server.

8. The method of any of claims 1 to 6, wherein the client is a MOM root server, a state modeling server, a state supervision server, an operation modeling server, or an operation supervision server, and the server is a MOM database server or a cloud server.

9. The method of any one of claims 1 to 6, wherein the client is a wearable smart device for receiving machine operation specifications and prompting a user for a three-dimensional model or animation generated in accordance with the machine operation specifications.

10. The method of claim 9, wherein the wearable smart device is virtual reality/augmented reality glasses.