Method and system for collecting via a MES system time-stamps of working-statuses

Abstract

A method and a system collect via a MES, time-stamps of working-statuses of machines and operators, called also actors, for a calculation of a time-dependant component of OLE and OEE indicators in a manufacturing task. The method includes providing a token for assigning to an actor the responsibility of data provision, and defining two meta-statuses for a machine in a task, called operating and booked meta-status respectively. Each meta-status groups a set of machine statuses. A machine is defined to be in an operating meta-status when the machine is in a status engaged in the task and it is able to know and notify its own status. A machine is defined to be in a booked meta-status when the machine is in a status engaged in the task and it is unable to notify its own status.

Claims

1. A method of collecting via a manufacturing execution system (MES) time-stamps of working statuses of machines and operators for a calculation of a time-dependant component of overall labor effectiveness (OLE) and overall equipment effectiveness (OEE) indicators in a manufacturing task, wherein an operator and a machine are assigned to a task, the operator and the machine being hereinafter called actors, which method comprises performing the following steps with a processor: a) assigning to an actor, an entity, defining responsibility of data provision, the entity herein-after being called a token; b) defining two meta-statuses for the machine in the task, each of the meta-statuses grouping a set of machine statuses: the meta-statuses including a first meta-status hereinafter called an operating meta-status and a second meta-status hereinafter called a booked meta-status, wherein the two meta-status being defined as follows: the machine is defined to be in the operating meta-status when the machine is in a status engaged in the task and the machine is able to know and notify its own status; the machine is defined to be in the booked meta-status when the machine is in a status engaged in the task and the machine is unable to notify its own status; c) collecting, via the MES system, the time stamps of the statuses of the machine and/or of the operator in a given manufacturing task, which collecting step further includes the steps of: c1) assigning the token to the actor at a start of the given manufacturing task via the MES system; c2) during the given manufacturing task being in progress, c21) collecting from the actor owning the token, the time stamps of the statuses via the MES system; c22) if a status transition event took place and such event implies also a meta-status transition event: notifying the MES system that an event of meta-status transition took place via the operator; assigning the token ownership to the machine upon determining that the meta-status switched from the booked meta-status to the operating meta-status via the MES system, or assigning the token ownership to the operator upon determining that the meta-status switched from the operating meta-status to the booked meta-status.

2. The method according to claim 1, wherein the token is a programmable logic controller flag.

3. The method according to claim 1, wherein the token is an internal variable or a flag of the MES system.

4. The method according to claim 1, wherein in sub-step c21) the time stamps of the statuses are triggered by events of status transitions or are polled by the MES system.

5. The method according to claim 1, wherein in step c1) creating a new logging session.

6. The method according to claim 1, which further comprises implementing the method via software.

7. A system for collecting via a manufacturing execution system (MES) time-stamps of working statuses of machines and operators for a calculation of a time-dependant component of overall labor effectiveness (OLE) and overall equipment effectiveness (OEE) indicators in a manufacturing task, wherein an operator and a machine are assigned to a task, the operator and the machine being hereinafter called actors, the system comprising: a) means for assigning an entity to the actor for defining responsibility of data provision, the entity herein-after called a token; b) means for defining two meta-statuses for the machine in the task, each of the meta-statuses grouping a set of machine statuses, the meta-statuses including a first meta-status hereinafter called an operating meta-status and a second meta-status hereinafter called a booked meta-status, the two machine meta-status are defined as follows: the machine is defined to be in the operating meta-status when the machine is in a status engaged in the task and the machine is able to know and notify its own status; the machine is defined to be in the booked meta-status when the machine is in a status engaged in the task and the machine is unable to notify its own status; c) means for collecting via the MES system the time stamps of the statuses of the machine and/or of the operator in a given manufacturing task as follows: c1) at a start of the given manufacturing task, means for assigning via the MES system the token to the actor; c2) while the given manufacturing task is in progress: c21) means for collecting, by the MES system, from the actor owning the token, the time stamps of the statuses; c22) if a status transition event took place and the status transition event implies also a meta-status transition event: means for notifying, by the operator, to the MES system that an event of meta-status transition took place; means for assigning, by the MES system, a token ownership to the machine upon determining that the meta-status switched from the booked meta-status to the operating meta-status or, alternatively, means for assigning, by the MES system, the token ownership to the operator upon determining that the meta-status switched from the operating meta-status to the booked meta-status.

Description

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING

(1) FIG. 1 is a diagram schematically representing an exemplary embodiment of meta-status model containing an operating meta-status and a booked meta-status according to the invention; and

(2) FIG. 2 is a block diagram schematically representing an exemplary embodiment of a state machine with status transitions.

DETAILED DESCRIPTION OF THE INVENTION

(3) At least some embodiments of the present invention addresses the above described issue in which, in a given manufacturing task, a MES system is collecting time logs/stamps of statuses of machines and operators for the calculation of the time-dependant component of OLE and OEE indicators. In general, with the term time-dependant component it is meant the component of the indicator which is depending on the time of permanence in some predefined working statuses such as, for example, time of permanence in statuses that are of run type, statuses which belong to operating and/or booked meta-statuses: the time of permanence in a status may be calculated as a difference between final and initial time stamps or logs.

(4) Examples of the time-dependent component of the above given examples of OLE and OEE indicator formulas may be given by the availability component or the performance component.

(5) In the given manufacturing task, the machine and the operator are assigned to a task, and they are herein called actors.

(6) In order to assign to an actor the ownership and/or responsibility of data provision, it is provided an entity called a token. In invention embodiments, the token may preferably be a programmable logic controller (PLC) flag or an internal variable or a flag of the MES.

(7) Token ownership rules are conveniently provided with the meta-status model of the proposed invention, in which two meta-statuses are defined for a machine in a task, where each meta-status groups a set of machine statuses.

(8) In the operating meta-status, the machine is in a status engaged in the task and it is able to know and notify its own status.

(9) In the booked meta-status, the machine is in a status engaged in the task and it is unable to notify its own working status.

(10) Ownership rules are now described.

(11) A token is owned by the operator when the machine is in the booked meta-status, i.e. meaning that the process is focusing on manual operation (with or without machine involvement).

(12) The token is owned by the machine when the machine is in the operating meta-status, i.e. meaning that the process is focusing on automatic machining operation.

(13) The MES system collects the time stamps or logs of the statuses of the machine and/or of the operator in a given manufacturing task in order to provide input data for calculating the time component of the OEE and OLE indicators.

(14) According to the proposed invention, the time stamp collection for OEE and OLE calculation is performed in a synchronized manner, so that advantageously:

(15) no overlapping input data are collected;

(16) no double or redundant input data entry is required;

(17) no garbage data are collected, e.g. when a machine is in an idle status belonging to the booked meta-status all input data coming from machines are ignored); and

(18) no corrective actions are required.

(19) When the task starts, usually by an operator, the MES system assigns the token to one of the two actors. Then, while the given task is in progress, the MES collects from the actor owning the token the relevant time stamps of the working statuses of machine and operator. The MES time stamps data collection may preferably be triggered by events of status transitions or may be polled by the MES at certain time intervals.

(20) In case there is a status transition event which imply also a meta-status transition event, the operator notifies the MES that an event of meta-status transition took place so that the MES can assign the token ownership to the relevant actor as follows: to the machine if the meta-status switched from booked to operating or, alternatively, to the operator if the meta-status switched from operating to booked.

(21) At the start of a machine task a new logging session may advantageously be created and the collected time stamps may be saved by the MES at the end of the task, but if necessary they may be saved also during the task.

(22) In inventive embodiments, the time stamp collection may conveniently be performed for more than one manufacturing task active in the factory, if desired also simultaneously.

(23) The collected time stamps and logs are used by the MES system to calculate the time component for the OEE and OLE indicators.

(24) Furthermore, a computer program element can be provided, containing computer program code for performing steps according to the above mentioned method when loaded in a digital processor of a computing device.

(25) Additionally, a computer program product stored on a computer usable medium can be provided, containing computer readable program code for causing a computing device to perform the mentioned method.

(26) Only the actor owning the token provides input data for OEE and OLE calculation, while the other actor without token passively inherit the OEE and OLE relevant input data from the actor owning the token.

(27) When a machine is used for manual assisted activities, e.g. the machine is getting ready for main tasks, it is in the booked meta-status and it does not own the token. When the machine is performing the main productive tasks, it is in the operating meta-status and it owns the token.

(28) Once the task owner is the machine, labor time counting for the operator does not stop even if the task owner is the machine. This is because we assume that the operator attends a machine that owns the task at least for a percentage of its execution time.

(29) In fact, the OLE of the assisting operator is considered 100% or a declared allocated part-time, e.g. 50% if operator is supervising 2 machines simultaneously, considering that the super visioning activity cannot cause losses.

(30) The machines have an automatic control system and are able to notify their status when running in operating mode.

(31) FIG. 1 is a diagram showing an exemplary embodiment of meta-status time model containing an operating meta-status and a booked meta-status.

(32) FIG. 1 is aimed at representing graphically the OEE machine time model with the introduction of the meta-status model MSM according to an exemplary embodiment of the present invention. The horizontal axis of the diagram of FIG. 1 represents time. In the upper part of the FIG. 1 there is a total machine time TMT and in the lower part, there are times WST spent in the machine OEE working statuses, already known in the art.

(33) The meta-status model MSM, according to an exemplary embodiment of the present invention, is represented in the middle part of the drawing and contains the time spent by the machine in the operating meta-status OMST and the time spent by the machine in the booked meta-status BMST.

(34) It should be noted that the introduction of the meta-status model MSM does not affect the level of accuracy of the OEE data acquisition, since the machine working statuses can be defined with the highest desired granularity, as for example: Run, Setup, Pause, Lost, Waiting etc.

(35) The operating meta-status is grouping a set of working statuses in which the machine is engaged in the task and it is able to know and notify its own working status. A machine in an operating meta-status may either be attended or unattended. FIG. 1 shows, on the left side, some examples of working status which belong to the operating meta-status OMST such as:

(36) Run: the machine is performing the task, e.g. progressing the given program or routines;

(37) Waiting: the machine is waiting for an attended action (e.g. confirmation to run next section of machine programs or routines);

(38) Finished: the machine completed the current task (e.g. last program or routine completed);

(39) Pause: the machine is on pause (e.g. because cooling-down is necessary); and

(40) Lost: the machine is stopped due to unexpected machine caused events (e.g. machine hydraulic failure, safety alarm, etc.).

(41) The booked meta-status is grouping a set of working statuses in which the machine is engaged in the task (and hence not available for other tasks) and it is not able to notify its own working status. The machine may be under control of an operator for preparation, cleaning and other activities linked to the task, before and after operation. FIG. 1 shows, on the right side, some examples of working status which belong to the booked meta-status BMST such as:

(42) Ready: machine is ready and can accept a new program/routine start signal;

(43) Lost: machine is stopped due to unexpected process caused events (e.g. missing tool, unclear work instruction, etc.)

(44) As one skilled in the art knows, additional or other working statuses may be defined according to the types of tasks, to the types of machines and/or to the desired customer requirements.

(45) FIG. 2 is a block diagram schematically representing an exemplary embodiment of a state machine with states and their transitions, starting with operator clocking in IN and finishing with operator clocking out OUT.

(46) In the state machine of FIG. 2 each block is a working status identified by a couple including: an operator working status and a machine working status.

(47) Machine working statuses may be grouped under the operating or booked meta-status.

(48) Here follows a short description of each state block shown in FIG. 2.

(49) States Highlighted by the Dashed Oval ST1:

(50) state 11: operator in Idle status/machine not applicable;

(51) state 12: operator Active on Indirect Activities status/machine not applicable;

(52) state 13: operator in Pause status/machine not applicable;

(53) state 14: operator in Lost status/machine not applicable; and

(54) state 15: operator in Active status/machine not applicable.

(55) All such states ST1 are states in which the token is owned by the operator who is not using a machine. The time logs or times of permanency of such states ST1 are relevant only for the calculation of the OLE indicator.

(56) States Highlighted by the Dashed Oval ST2:

(57) state 21: operator in Active status/machine in Ready status (Booked meta-status);

(58) state 22: operator in Pause status/machine in Ready status (Booked meta-status); and

(59) state 23: operator in Lost status/machine in Ready status (Booked meta-status).

(60) All such states ST2 are states in which the token is owned by the operator who is using a machine. The time logs or times of permanency of such states ST2 may be relevant for calculation of both the OEE and OLE indicators.

(61) States Highlighted by the Dashed Oval ST3:

(62) state 31: operator in Attend status/machine in Run status (Operating meta-status);

(63) state 32: operator in Attend status/machine in Waiting status (Operating meta-status); and

(64) state 33: operator in Attend status/machine in Finished status (Operating meta-status).

(65) All such states ST3 are states in which the token is owned by the machine which is assisted by the operator. The time logs or times of permanency of such states ST3 is relevant only for calculation of the OEE indicator.

(66) In each state, only one actor owns the token, either the operator or the machine. More in particular, in the highlighted states ST1 the token is owned by the operator, in the in the highlighted states ST2 the token is owned by the operator being the machine in statuses which are booked meta-status, in the highlighted states ST3 the token is owned by the machine being the machine in statuses which are operating meta-status.

(67) The arrow represents the switching from one state to another state and they are called transitions. The event that causes the transition is called the triggering event. For each state, only the token owner can trigger the event. In each transition it indicated which is the triggering actor, e.g. transitions indicated as O.<transition name> are triggered by the operator and transitions indicated as M.<transition name> are triggered by the machine.

(68) Every output transitions from one state where the machine is in operating meta-status is triggered by the same actor; e.g. in state 31 both output transitions, M.exception and M.finish, are triggered by the machine.

(69) The transition allowing the operator to move from state 32 to operator attending may advantageously allow specifying the load factor that is the percentage of machine work that needs to be attended by operator, e.g. with the transition O.activateMachine(load_factor). According to the shown state diagram, once the operator is in attend state 31 he cannot move into pause state 22 or lost state 23.

(70) In invention embodiments, state blocks containing <<subs>>, e.g. state blocks 14,21,23,31,32 may advantageously be detailed and refined with additional information about sub-status or reasons, according to customer needs and the level of precision required in classifying collected time. For example, for the state 14 having for the couple of status Lost/n.a the additional information may be the following: <<subs>>={Missing Tool/n.a., Missing Material/n.a, Machine not Available/n.a . . . }. Advantageously, with such embodiments, data accuracy at desired level may be acquired.

(71) In invention embodiments, state blocks containing a self-loop, e.g. state blocks 21,31, may conveniently be repeated depending on the required level of details. e.g. for the couple Attend/Operating, <<subs>>={Attend/Setup, Attend/Run, . . . }.