CN111381629B

CN111381629B - Work support system and work support method

Info

Publication number: CN111381629B
Application number: CN201811635236.7A
Authority: CN
Inventors: 藤井哲也; 河村治树; 庄二利; 郭宏记; 吴勇明
Original assignee: Dainengben Co ltd
Current assignee: Dainengben Co ltd
Priority date: 2018-12-29
Filing date: 2018-12-29
Publication date: 2024-05-14
Anticipated expiration: 2038-12-29
Also published as: JP2020109606A; JP7391551B2; CN111381629A

Abstract

The purpose is to provide a work support system capable of creating a task flow suitable for the proficiency of an operator. According to an embodiment, a job support system includes a task flow management server, a manager terminal, and an operator terminal. The task flow management server manages task flows. The operator supports execution of the job along the task flow by the terminal. The task flow management server includes a task flow creation management processing unit. The task stream creation management processing unit provides a user interface for creating or updating task streams, and manages task streams created or updated using the user interface. The task flow creation management processing unit provides a user interface capable of selectively creating or updating a task flow by applying the 1 st setting for a highly skilled worker and the 2 nd setting for a less skilled worker.

Description

Work support system and work support method

Technical Field

The present invention relates to a job support system and a job support method.

Background

In recent years, electronic assistance has been widely adopted for an operator who is engaged in work by wearing a wearable device by the operator or by bringing a personal computer of a tablet type by the operator. For example, in the case of a wearable device of glasses type, since the display can be viewed while the work is being performed, the work can be advanced by, for example, presenting the work step by step, and thus the work can be performed even by a person who is not a skilled person. In a work support system for electronically supporting a worker who performs a work, a work process is called a task flow (task flow) or the like.

Further, the work support system is used not only for supporting a worker who works, but also for collecting work results of the worker, guidance of the worker, improvement feedback of task flows, and the like.

Prior art literature

Patent literature

Patent document 1: japanese patent laid-open No. 2017-58783

Patent document 2: japanese patent laid-open No. 2007-335711

Patent document 3: international publication No. 2011/070967

Patent document 4: japanese patent application laid-open No. 2013-508862

Disclosure of Invention

Problems to be solved by the invention

In a work support system used for guidance to an operator, improvement feedback of a task flow, and the like, it is important to collect and manage work results of the operator by including work errors. Therefore, for example, operations such as collecting and managing job results of each task in the task flow are performed step by step.

However, among operators who perform work on a work site, there are operators who have high proficiency and operators who have low proficiency. The work is performed by the operators with different proficiency under the same conditions, and the work efficiency may be lowered as a whole. For example, it is not uncommon for a highly skilled worker to be inefficient to advance the work step by step along a task flow created by the worker who is supposed to be less skilled.

The present invention provides a work support system and a work support method capable of creating a task flow or the like suitable for the proficiency of an operator, for example.

Means for solving the problems

According to one aspect, a job support system includes a task flow management server, a manager terminal, and an operator terminal. The task flow management server manages task flows indicating job procedures. The manager uses the terminal to make or update the task flow managed by the task flow management server. The operator terminal supports execution of the job along the task flow provided from the task flow management server. The task flow management server includes a task flow creation management processing unit. The task flow creation management processing unit provides the manager terminal with a user interface for creating or updating task flows, and receives and manages task flows created or updated by the manager terminal using the user interface from the manager terminal. The task flow creation management processing unit provides the manager terminal with the user interface capable of selectively applying the 1 st setting for the high-proficiency worker and the 2 nd setting for the low-proficiency worker to create or update the task flow.

Drawings

Fig. 1 is a diagram showing an example of the configuration of the work support system according to embodiment 1.

Fig. 2 is a diagram showing an example of functional blocks of a task flow management server in the job support system according to embodiment 1.

Fig. 3 is a diagram showing an example of a functional block of an operator terminal in the work support system according to embodiment 1.

Fig. 4 is a diagram showing an example of the external appearance of a wearable device connected to an operator terminal in the work support system according to embodiment 1.

Fig. 5 is a diagram showing an example of the appearance of a main body of a wearable device connected to an operator terminal in the work support system according to embodiment 1.

Fig. 6 is a diagram showing an example of connection between the terminal for the operator and the wearable device in the work support system according to embodiment 1.

Fig. 7 is a diagram showing an example of the appearance of an operator terminal in the work support system according to embodiment 1.

Fig. 8 is a flowchart showing a flow of task flow improvement desired in the job support system according to embodiment 1.

Fig. 9 is a view 1 showing an example of a screen for creating or updating a task flow, which is displayed in the job support system according to embodiment 1.

Fig. 10 is a view showing an example of a screen for creating or updating a task flow displayed in the job support system according to embodiment 1.

Fig. 11 is a view 1 showing an example of a screen for job support displayed based on a task flow in the job support system according to embodiment 1.

Fig. 12 is a view showing an example of a screen for job support displayed based on a task flow in the job support system according to embodiment 1.

Fig. 13 is a flowchart showing a flow of task flow creation in the job support system according to embodiment 1.

Fig. 14 is a flowchart showing a flow of task flow application in the job support system according to embodiment 1.

Fig. 15 is a diagram showing an example of a screen for printing a two-dimensional code corresponding to a task flow, which is displayed in the job support system according to embodiment 2.

Fig. 16 is a diagram showing a display example of a two-dimensional code corresponding to a task flow in the job support system according to embodiment 2.

Fig. 17 is a diagram showing an example of a flow of tasks from the start of the task flow by list selection of the operator terminal in the task support system according to embodiment 2.

Fig. 18 is a diagram showing an example of a flow of tasks from the start of the task flow by the two-dimensional code reading of the operator terminal in the job support system according to embodiment 2.

Fig. 19 is a diagram showing an example of a screen for creating or updating a task flow displayed in the job support system according to embodiment 3.

Fig. 20 is a diagram showing one transition example of a screen on the operator terminal in the case where the detailed button is set to be on in the work support system according to embodiment 3.

Fig. 21 is a diagram for explaining a flow of update of a task flow in the job support system according to embodiment 4.

Fig. 22 is a diagram showing an example of a screen showing allocation of task flows to the operator terminal, which is displayed in the work support system according to embodiment 4.

Detailed Description

Hereinafter, embodiments will be described with reference to the drawings.

(Embodiment 1)

First, embodiment 1 will be described.

Fig. 1 is a diagram showing an example of the configuration of a work support system 1 according to the present embodiment.

As shown in fig. 1, the job support system 1 of the present embodiment includes a task flow management server 10, an operator terminal 20, and a manager terminal 30. Further, a pair of glasses-type wearable devices 20A is connected to the operator terminal 20. Here, the terminal 20 for the operator used by being connected to the wearable device 20A is assumed, but the terminal 20 for the operator may be wearable by itself. The worker terminal 20 may be a mobile device called a tablet computer or the like, and may be used alone without being connected to a wearable device.

The work support system 1 is a system for supporting, for example, a work for manufacturing a product in a manufacturing factory. The work support system 1 is not limited to the second industry such as the manufacturing industry, and can be used to support various kinds of works of the third industry including the first industry such as agriculture and the service industry. Here, it is assumed that the work support system 1 is introduced into an enterprise that manages the manufacturing industry.

The task flow management server 10 is a computer that manages task flows representing job steps. The task flow management server 10 may be a computer of an enterprise operating the manufacturing industry, to which the job support system 1 is introduced, or may be a computer of an enterprise providing a function of supporting a job as a service. The task flow management server 10 may be any computer capable of communicating with the operator terminal 20 and the manager terminal 30.

The task flow management server 10 has a CPU11, a main memory 12, a storage device 13, and a communication device 14. The task management program 100 is installed in the storage device 13, and the cpu11 loads and executes the task management program 100 from the storage device 13 into the main memory 12, thereby constructing a control unit 110 (see fig. 2) described later in the task flow management server 10. The storage device 13 stores various programs and various data in addition to the task management program 100. The communication device 14 performs communication with the operator terminal 20 and the manager terminal 30.

The task flow management server 10 provides a user interface for creating or updating a task flow to the manager terminal 30. Specifically, the manager terminal 30 is a computer capable of operating a Web browser, and the task flow management server 10 provides a Web page (a 1) including a script (program) to the manager terminal 30. The manager terminal 30 is, for example, a Personal Computer (PC) or the like used by a manager who takes over the entire management of the job. The screen on the manager terminal 30 indicated by the reference numeral b1 is a screen on which a Web page provided from the task stream management server 10 is displayed by a Web browser.

That is, the manager accesses the task flow management server 10 by using the manager terminal 30, and obtains a Web page from the task flow management server 10, so that the manager terminal 30 displays a screen b1 for creating or updating the task flow. The Web page acquired from the task flow management server 10 includes a script (program) for creating or updating a task flow by an operation on a screen, and a script (program) for transferring the task flow created or updated by the operation on the screen to the task flow management server 10. Thus, the manager can create or update a task flow by an operation on the screen of the manager terminal 30, and can transfer the created or updated task flow to the task flow management server 10 (a 2). The transfer of the task flow from the manager terminal 30 to the task flow management server 10 for registration with the task flow management server 10 is also referred to as uploading.

The task flow created or updated by the manager is formed by linking a plurality of tasks in time series. Each task is a task for performing an instruction of executing a method of performing a job by text, a photograph (still image), a moving image, a sound, or the like, or photographing a photograph (still image) or a moving image in the terminal 20 for an operator, reading a barcode, or the like.

The task flow management server 10 stores the task flow transferred from the manager terminal 30 in the storage device 13. The task flow management server 10 provides the task flow created or updated by the manager as the worker terminal 20 of the computer carried by the worker (a 3). The transfer of the task flow from the task flow management server 10 to the worker terminal 20 is performed, for example, when the worker starts a job or the like corresponding to the task flow in a state where the task flow is not supplied to the worker terminal 20. The transfer of the task flow from the task flow management server 10 to the operator terminal 20 at this time is also referred to as downloading. In fig. 1, only 1 operator terminal 20 is shown, but the operator terminals 20 are the same number as the operators, for example. In the work support system 1, it is assumed that 1 worker terminal 20 is assigned to each worker. That is, in the work support system 1, the identifier indicating the operator terminal 20 indicates the operator who uses the operator terminal 20.

The task flow management server 10 manages which task flow is assigned to each worker. The manager distributes task flows to the operators. That is, the task flow management server 10 provides the manager terminal 30 with a user interface (Web page) for distributing task flows to the respective operators.

The operator terminal 20, which is a computer carried by an operator, includes a CPU21, a main memory 22, a storage device 23, a communication device 24, a button unit 25, and an I/O device 26. The operator support program 200 is installed in the storage device 23, and the CPU21 loads and executes the operator support program 200 from the storage device 23 to the main memory 22, thereby constructing a control unit 210 (see fig. 3) to be described later on the operator terminal 20. The storage device 23 stores various programs and various data in addition to the worker support program 200. The communication device 24 performs communication with the task flow management server 10. The button unit 25 is an operation unit provided on the housing peripheral wall of the operator terminal 20 and configured to receive an instruction from an operator. The I/O device 26 performs transmission and reception of data with the wearable device 20A connected to the worker terminal 20. The wearable device 20A is provided with a display, a camera, a microphone, a speaker, and the like, and the operator terminal 20 transmits and receives image data, sound data, and the like to and from the wearable device 20A via the I/O device 26.

The worker terminal 20 stores the task flow transferred from the task flow management server 10 in the storage device 23. The operator terminal 20 supports execution of the job along the task flow. For example, the operator terminal 20 transfers image data for displaying a screen for explaining the operation method to the wearable device 20A, and presents the image data to the operator via a display of the wearable device 20A. The screen denoted by reference numeral b2 is a screen displayed on the display of the wearable device 20A. An operator wearing the wearable device 20A as wearing glasses performs work while viewing the screen. The worker terminal 20 receives, for example, an image or the like captured by a camera of the wearable device 20A from the wearable device 20A, and transmits the image to the task flow management server 10 as a result of the job when the job ends or the like (a 4). As a result of the job transmitted to the task flow management server 10, for example, a required time or the like of each task in the task flow may be included in addition to the image or the like. The task flow management server 10 stores the job result received from the operator terminal 20 in the storage device 13.

Further, communication can be performed between the operator terminal 20 and the manager terminal 30. For example, an image captured by the operator terminal 20 may be transmitted to the manager terminal 30, and the status may be transmitted to the manager, and an instruction from the manager may be requested. In this case, the instruction may be a sound, or may be, for example, an image in which an annotation is written over a transmitted image. In this way, the manager plays a role corresponding to the back support of the worker as well as creating or updating the task flow.

The above is a basic flow of the cooperation of the task flow management server 10, the worker terminal 20, and the manager terminal 30 in the job support system 1 according to the present embodiment.

Fig. 2 is a diagram showing an example of functional blocks of the task flow management server 10.

As shown in fig. 2, the task flow management server 10 includes a control unit 110, a storage unit 120, and a communication unit 130. As described above, the control unit 110 is constructed by loading and executing the task management program 100 installed in the storage device 13 into the main memory 12 by the CPU 11. The control unit 110 may be implemented as an electronic circuit. That is, the control unit 110 may be realized by software or hardware.

Further, the storage section 120 corresponds to the storage device 13, and the communication section 130 corresponds to the communication device 14.

The control unit 110 includes a task flow creation management processing unit 111, an operator management processing unit 112, a task flow assignment processing unit 113, a job support processing unit 114, and a job result management processing unit 115.

The task flow creation management processing unit 111 transmits the Web page data 121 stored in the storage unit 120 for creating or updating the task flow to the manager terminal 30. The task flow creation management processing unit 111 receives the task flow created or updated by the manager terminal 30 using the Web page data 121, and stores the task flow as task flow data 122 in the storage unit 120. In the storage unit 120, a plurality of pieces of Web page data 121 are stored in order to provide various user interfaces. These Web page data 121 are also transferred from the task flow management server 10 to the manager terminal 30 in response to a request from the manager terminal 30 operating the Web browser.

When a new operator terminal 20 is added with an operator, for example, the operator management processing unit 112 transmits Web page data 121 for registering the new operator terminal 20 with the task flow management server 10 to the manager terminal 30. The operator management processing unit 112 uses the Web page data 121 to store the identifier of the operator terminal 20 newly registered on the manager terminal 30 side as the operator data 123 in the storage unit 120. The registered operator terminal 20 may be deleted on the manager terminal 30 side by using the Web page data 121 transmitted from the operator management processing unit 112 to the manager terminal 30. For example, when a user terminal 20 used by a certain user fails and a need to replace it with a new user terminal 20 occurs, the user terminal can be handled by deleting the user terminal 20 before replacement and registering the user terminal 20 after replacement. The worker data 123 is, for example, a data structure in which an entry (record) is ensured for each worker terminal 20, with an identifier of the worker terminal 20 as an index.

The task flow assignment processing unit 113 transmits the Web page data 121 for assigning task flows to the operators to the manager terminal 30. The Web page data 121 is transmitted to the manager terminal 30 in a state including a list of task stream data 122 and a list of worker data 123 stored in the storage unit 120 at this time. The Web page data 121 includes a script (program) for selecting a target worker from a list of workers (worker terminals 20) and selecting a task flow assigned to the selected worker from the list of task flows. In addition, a plurality of task flows may be assigned to each worker. In other words, each worker can engage in a plurality of jobs.

The task flow assignment processing unit 113 records the setting of assignment of task flows to the worker, which has been performed using the Web page data 121 on the manager terminal 30 side, in an entry (record) secured for the worker (the worker terminal 20) in the worker data 123 stored in the storage unit 120. Further, the task flow assigned to the worker can be deleted by the Web page data 121. In this case, the task flow assignment processing unit 113 deletes the task flow to be processed from the entry (record) in the worker data 123 that is secured for the worker (the worker terminal 20). The task flow assignment processing unit 113 transmits an instruction to delete the task flow of the object to the operator terminal 20.

The job support processing unit 114 notifies the operator terminal 20 of a list of the task flows allocated to the operator (operator terminal 20) by the task flow allocation processing unit 113, or transmits the requested task flows to the operator terminal 20 from the list.

The job result management processing unit 115 stores job result data 222 (see fig. 3) transferred from the operator terminal 20, which will be described later, in the storage unit 120.

Fig. 3 is a diagram showing an example of the functional blocks of the operator terminal 20.

As shown in fig. 3, the operator terminal 20 includes a control unit 210, a storage unit 220, a communication unit 230, and an I/O processing unit 240. As described above, the control unit 210 is constructed by the CPU21 loading and executing the worker support program 200 installed in the storage device 23 into the main memory 22. The control unit 210 may be implemented as an electronic circuit. That is, the control unit 210 may be realized by software or hardware.

Further, the storage section 220 corresponds to the storage device 23, the communication section 130 corresponds to the communication device 24, and the I/O processing section 240 corresponds to the I/O device 26.

The control unit 210 includes a task flow storage processing unit 211, a task flow execution processing unit 212, a job result record transmission processing unit 213, and an environment setting processing unit 214.

The task flow storage processing unit 211 stores the task flow data 122 transferred from the task flow management server 10 in the storage unit 220. The task flow storage processing unit 211 can delete the task flow data 122 stored in the storage unit 220 and designated from the task flow management server 10, in response to an instruction from the task flow management server 10.

The task flow execution processing unit 212 executes job support for the operator using the operator terminal 20 based on the task flow data 122 stored in the storage unit 220. Specifically, text, photographs, sounds, moving images, and the like for the work method included in the task flow data 122 are transferred to the wearable device 20A worn by the worker as if the worker were wearing glasses via the I/O processing unit 240, and are presented to the worker through a display or a speaker of the wearable device 20A. The task flow execution processing section 212 also performs processing of receiving, from the wearable device 20A via the I/O processing section 240, an image photographed as a result of the job by the camera of the wearable device 20A.

The job result record transmission processing unit 213 stores the image or the like acquired as the job result by the task flow execution processing unit 212 as job result data 222 in the storage unit 220. The job result record transmission processing unit 213 may measure the time required for each task and store the time as job result data 222 in the storage unit 220. The job result record transmission processing unit 213 transfers job result data 222 corresponding to the job stored in the storage unit 220 to the task stream management server 10 every time 1 job is completed. The transmission of the job result data 222 from the operator terminal 20 to the job flow management server 10 is also referred to as uploading.

The environment setting processing unit 214 performs a setting for making the operator terminal 20 and the wearable device 20A connected to the operator terminal 20 easy for each operator who actually uses the operator terminal 20 and the wearable device 20A to use, and stores the setting as specification (profile) data 221 in the storage unit 220. For example, a wearable device body 1024 (see fig. 4) of the eyeglass type wearable device 20A described later is attached to one of the left and right temples. In general, the wearable device main body 1024 is attached to the right side temple in the case where the right eye is the dominant eye worker, and the wearable device main body 1024 is attached to the left side temple in the case where the left eye is the dominant eye worker. Also, in the case of the right-side temple mounting and in the case of the left-side temple mounting, the wearable device main body 1024 is inverted up and down. With this, the display is also inverted up and down. The environment setting processing unit 214 records, for example, information on which of the left and right temples the wearable device main body 1024 is attached to as specification data 221.

Fig. 4 shows an example of the external appearance of wearable device 20A. The wearable device 20A is provided with a spectacle frame 1142 and a wearable device body 1024. The eyeglass frame 1142 may be a shape in which lenses are removed from ordinary eyeglasses and worn on the face of an operator. The frame 1142 may be a structure to which glasses are attached.

The eyeglass frame 1142 includes attachment tools 1144 for attaching and detaching the wearable device main body 1024 to the left and right temple. In fig. 4, the attachment tool 1144 of the temple on the right side of the worker is hidden by the wearable device main body 1024, and is not shown. As described above, since the wearable device main body 1024 includes the display 1124 (see fig. 5), the display 1124 is visually recognized by a single eye, the mounting tool 1144 is provided on the left and right temple so as to mount the wearable device main body 1024 on the main eye side. In addition, the wearable device 20A for the right eye and the left eye, in which the wearable device body 1024 is fixed to the eyeglass frame 1142, may be prepared without detachably attaching the wearable device body 1024 to the eyeglass frame 1142 with the attachment tool 1144. Further, the wearable device body 1024 may be worn on the head of the worker not using the eyeglass frame 1142 but using a helmet, goggles, or the like.

The wearable device main body 1024 is mounted to the eyeglass frame 1142 by pushing its engagement pieces 1128 (see fig. 5) into the upper and lower frames of the mounting tool 1144. In the case of detaching the wearable device body 1024 from the eyeglass frame 1142, the wearable device body 1024 is pulled out from the mounting tool 1144.

The engagement piece 1128 can move forward and backward in the mounting tool 1144 in a state where the wearable device body 1024 is mounted on the mounting tool 1144. Accordingly, the front-rear position of the wearable device main body 1024 can be adjusted so that the operator is in focus with the display 1124. Further, the mounting tool 1144 can rotate about an axis 1144A perpendicular to the temple, and after the wearable device main body 1024 is mounted on the eyeglass frame 1142, the up-down position of the display 1124 can be adjusted so as to be positioned on the line of sight of the operator. Further, the rotation angle of the attachment tool 1144 is about 90 degrees, and by rotating the attachment tool 1144 upward largely, the wearable device body 1024 can be sprung from the eyeglass frame 1142. Thus, even when the visual field is blocked by the wearable device body 1024 and the real object is difficult to see, or when the wearable device body 1024 interferes with a surrounding object in a narrow place, the wearable device body 1024 can be temporarily taken out from and put back into the visual field of the worker without taking out/putting on the wearable device 20A from the face as a whole.

The wearable device main body 1024 includes a side surface portion along the temple of the lens holder 1142 and a front surface portion on the visual line of one eyeball of the operator. The angle of the front face portion relative to the side face portion can be adjusted.

As shown in fig. 4, a camera 1116, a lamp 1118, and a camera LED1120 are provided on the outer side surface of the front face. The lamp 1118 is auxiliary illumination that emits light when photographing a dark portion. The camera LED1120 is turned on when a photograph or a moving image is taken, and recognizes that a subject person is taking the photograph.

The 1 st, 2 nd, 3 rd buttons 1102, 1104, 1106 are provided on the upper side of the side face portion of the wearable device main body 1024 mounted on the right side temple. In addition, in the case where the principal eye of the worker is the left eye, the wearable device main body 1024 is mounted to the left temple. Since the wearable device main body 1024 is inverted up and down according to whether it is mounted on the right side or the left side, the 1 st, 2 nd, 3 rd buttons 1102, 1104, 1106 may be provided on both of the upper side and the lower side of the side face portion.

A touch panel 1110, a4 th button 1108, a microphone 1112, and an illuminance sensor 1114 are provided on the outer surface of the side surface portion. Touchpad 1110 and button 4 1108 can be operated with the index finger. The buttons 1102, 1104, 1106 are disposed in positions that can be operated with the index finger, the middle finger, and the ring finger, respectively, when the wearable device body 1024 is disposed on the right side. The touch panel 1110 can detect, on the surface thereof, a situation in which the operator moves his finger up and down and back and forth as indicated by an arrow. The detection of this movement includes, in addition to the movement of a drag (drag) that moves while maintaining the state of finger contact, a movement of a slip (flick) that quickly wipes the finger.

The 1 st button 1102 is disposed at a position operable by the index finger, the 2 nd button 1104 is disposed at a position operable by the middle finger, the 3 rd button 1106 is disposed at a position operable by the ring finger, and the 4 th button 1108 is disposed at a position operable by the little finger. The 4 th button 1108 is not provided on the upper part of the side surface but on the outer side surface of the side surface, and the 4 th button 1108 may be provided on the upper part of the side surface in the same manner as the 1 st to 3 rd buttons 1102, 1104, 1106 because of the space. The illuminance sensor 1114 detects illuminance around the display in order to automatically adjust the brightness of the display.

Fig. 5 shows an example of the appearance of the back surface of the wearable device main body 1024. A display 1124 made up of an LCD is provided on the inner side of the front face. A microphone 1126, a speaker 1130, and an engagement piece 1128 are provided inside the side surface portion. The microphone 1126 is provided in front of the side portion, the speaker 1130 is provided behind the side portion, and the engagement piece 1128 is provided behind the side portion. Headphones may also be used in place of the speakers 1130. In this case, the microphone and the headphone may be integrally provided as a headset.

Fig. 6 shows an example of connection between the worker terminal 20 and the wearable device 20A. A receptacle 1132 into which a plug 1146A of one end of a USB type-C (registered trademark) standard cable 1146 is inserted is provided at the rear of the side face portion. The plug 1146B at the other end of the USB type-C standard cable 1146 is inserted into the USB type-C standard connector 1207 at the upper end face of the operator terminal 20. In this way, the wearable device body 1024 is connected to the operator terminal 20 via the cable 1146 of the USB type-C standard, and an image or the like is transmitted between the wearable device body 1024 and the operator terminal 20. The wearable device main body 1024 may be connected to the operator terminal 20 through wireless communication such as wireless LAN or bluetooth.

In the present embodiment, the wearable device main body 1024 does not include a battery or a DC terminal as a driving power source, and the driving power source is supplied from the operator terminal 20 to the wearable device main body 1024 via the USB type-C cable 1146. The wearable device body 1024 may also be provided with a driving power source.

Fig. 7 shows an example of the external appearance of the operator terminal 20. The operator terminal 20 is a small PC that can be held by one hand, has a size of about 10cm or less in width, about 18cm or less in height, about 2cm in thickness, and about 300g in weight, and is small and lightweight. Therefore, the operator terminal 20 can be accommodated in a pocket of a work clothes, a leather sheath or a shoulder bag attached to a waist belt, and is wearable.

A5 button 1202 including an up button 1202a, a lamp button 1202b, a down button 1202c, a left button 1202d, and a decision button (also referred to as a center button or a carriage return button) 1202e is disposed on the front surface of the operator terminal 20, and a fingerprint sensor 1204 is disposed below the 5 button. The fingerprint sensor 1204 is used for user authentication at the time of login (log in) of the operator terminal 20. The 5 button 1202 is capable of inputting a command.

Further, the buttons 1202a to 1202d of the 5 buttons 1202 may be assigned to numerals, and the user may be authenticated by inputting a password using the 5 buttons 1202. In this case, the fingerprint sensor 1204 may be omitted. Since the numbers are assigned to the 4 buttons other than the decision button 1202e, the number is only 4 in variety. Thus, it is possible that the randomly entered numbers coincide with the password. But if the number of digits of the password is increased, the probability that the randomly entered digits coincide with the password can be reduced. Authentication by the 5 button 1202 may be performed in the operator terminal 20 including the fingerprint sensor 1204.

The 5 button 1202 is capable of performing the same operations as those of the buttons 1102, 1104, 1106, 1108 and the touch pad 1110 of the wearable device main body 1024. Since the operator cannot see the state in which the buttons 1102, 1104, 1106, 1108 and the touch panel 1110 of the wearable device main body 1024 are being operated, the operator sometimes needs to be used to perform a desired operation. Further, since the buttons 1102, 1104, 1106, 1108 and the touch panel 1110 are small, there are cases where operation is difficult. In the present embodiment, the same operation can be performed by the 5 button 1202 of the operator terminal 20, and thus, such a fear is eliminated.

On the upper side of the operator terminal 20, a connector 1206 of the USB 3.0 standard, a connector 1207 of the USB type-C standard, and an audio jack 1208 are provided.

A card slot 1218 for a memory card is provided on one side surface (left side surface as viewed from the front) of the operator terminal 20. The memory card is, for example, an SD card, a Micro SD card (registered trademark), or the like.

The other side surface (the side surface on the right side as viewed from the front) of the operator terminal 20 is provided with a slot 1210 for a ken-to-on (kensington) lock (registered trademark), a power switch 1212, a power LED1213, a DC IN/battery LED1214, a DC terminal 1216, and a cooling vent 1222. The power LED1213 is arranged near the power switch 1212, and is turned on during the power-on period. The DC IN/battery LED1214 displays the state of the operator terminal 20 and the remaining amount of the battery, whether the battery is charged or not. The operator terminal 20 can be driven by a battery, but can also be driven in a state where the AC adapter is connected to the DC terminal 1216. Although not shown, the rear surface may be configured to replace the battery with a one touch operation (one touch).

Here, a flow of task flow improvement to be performed in the job support system 1 according to the present embodiment will be described with reference to fig. 8.

First, a task flow is created by the manager (step A1), and a job (execution) along the task flow is performed by the worker (step A2). If the worker ends his job, the result of the job is uploaded to the task flow management server 10 (step A3).

The manager checks (reviews: review) the job result managed by the task flow management server 10 (step A4), and updates the task flow (step A5). Thereafter, the steps A2 to A5 are repeated to improve the task flow.

Next, a function of creating a task flow suitable for the proficiency of the operator provided by the work support system 1 of the present embodiment will be described.

Fig. 9 is a diagram showing an example of a screen for creating or updating a task flow, which is displayed on the manager terminal 30 using the Web page provided from the task flow management server 10. The Web page implements a task flow graphical editor on the administrator terminal 30 that has a user interface for creating or updating task flows.

At the time of creation of a task stream, the task stream graphic editor first displays an edit screen (task stream editor screen c 1) configured with an icon indicating the start of a task stream shown by reference numeral c101 and an icon indicating the end of a task stream shown by reference numeral c 102. The task stream graphic editor displays a task template list c2 on the side of the task stream editor screen c 1. The manager creates a task stream by arranging the target task template in the task template list c2 on the task stream editor screen c 1. In updating the task stream, the task stream graphic editor displays an edit screen of the task stream configured with the update object.

The configuration of the task template on the task stream editor screen c1 is performed by an operation of a mouse called drag (dragand drop) or the like, for example. The connection between task templates arranged on the task stream editor screen c1 is performed by a mouse operation such as drawing a line segment (arrow) from the region where the task template is arranged before the task template is arranged to the region where the subsequent task template is arranged. The same mouse operation is performed between the icon c101 indicating the start of the task flow and the first task template, and between the last task template and the icon c102 indicating the end of the task flow. That is, the manager can create a task stream by arranging task templates (c 103-1 to c 4) between an icon c101 indicating the start of the task stream and an icon c102 indicating the end of the task stream on the task stream editor screen c1 and connecting them.

The task template c2-1 shown in fig. 9 is a task template selected when the job method is presented in text. For example, when a previous task is completed and a transition is made to the task, a text indicating a job method is presented to the operator.

The task template c2-2 is a task template selected when the job method is presented in a photograph (still image).

The task template c2-3 is a task template selected in the case where the job method is presented as a moving image.

The task template c2-4 is a task template selected when the job method is presented with sound.

The task template c2-5 is a task template selected in the case of indicating reading of a barcode.

The task templates c2 to 6 are task templates selected when the job method is presented in PDF (registered trademark).

The task templates c2-7 are task templates selected in the case of accessing information to be referred to through URLs.

The task templates 2 to 8 are task templates selected in the case of instructing photographing of a photograph (still image).

The task templates 2 to 9 are task templates selected in the case of instructing photographing of a moving image.

In addition, although not shown in fig. 9, there are task templates or the like selected when a job method is presented in both text and a photograph (still image), for example. The task template not shown in fig. 9 can be selected by operating a scroll bar (scroll bar) c3 to appear on the screen.

In addition, the task stream graphic editor displays an object (object) c104 that represents a task template of the editing object. For example, the region where the target task template is arranged is indicated by a pointer, and by performing an operation called clicking (click) or the like of a mouse, the object c104 can be moved to indicate the task template. For example, in the case where the object c104 represents the task template c2-1, that is, in the case where the task template c2-1 is an editing object, the task flow graphic editor sets a preview area c4 for inputting text representing a job method on the screen.

In fig. 9, an object c104 represents an area (task template c 103-2) in which the task template c2-2 is arranged, and in the case where the task template c2-2 is an editing object, the task stream graphic editor sets a preview area c4 on the screen for registering a photograph (still image) representing a job method.

That is, the manager can register a text, a photograph (still image), or the like to be presented to the operator in the preview area c 4.

Further, the task stream graphic editor sets a button setting area c5 for performing various settings for each task on the screen. In the button setting area c5, there are first a Skip (Skip) button c501 and a Back (Back) button c502. These buttons c501 and c502 are sliding buttons, and the right sliding (toward the screen) is on and the left sliding (toward the screen) is off.

The skip button c501 is a button set to be on in a case where the task is allowed to pass over and shift to the next task. If the skip button c501 is set to ON (ON), the skip button is displayed ON the screen presented to the operator, and by selecting the skip button, the operator can move the task past and down. The skip button c501 is set to be turned on mainly when a task stream for a highly skilled worker is produced. When a task flow for a worker with low proficiency is produced, the skip button c501 is set to off, and as a result, the skip button is not displayed on the screen presented to the worker, and the worker is prohibited from moving the task past and down.

The back button c502 is a button set to be on in the case of allowing a return to a previous task to redo the previous task. If the back button c502 is set to on, the back button is displayed on the screen presented to the operator, and by selecting the back button, the operator can return to the previous task and redo the previous task. The back button c502 is set to be turned on mainly when a task flow for a highly skilled worker is produced. When a task flow for an operator with low proficiency is produced, the back button c502 is set to off, and as a result, the back button is not displayed on the screen presented to the operator, and the operator is prohibited from returning to the previous task and redoing the previous task. By prohibiting rework, what errors the operator with low proficiency makes can be collected as the result of the operation.

In the button setting area c5, a photograph photographing button c503, a moving image photographing button c504, a call-out button c505, and a Detail (Detail) button c506 are also present. These buttons c503 to c506 are also sliding buttons (toward the screen) and are opened and sliding buttons (toward the screen) and closed.

The photograph photographing button c503 is a button set to be on when a button for photographing a photograph is displayed. The moving image photographing button c504 is a button set to on when a button for performing moving image photographing is displayed. The send button c505 is a button set to be on when a button for performing communication with the manager terminal 30 is displayed. The detailed button c506 is described later.

Further, the task stream graphic editor configures a save button c6 and a task stream issue button c7 on the screen. The save button c6 is a button for transmitting the created or updated task stream to the task stream management server 10. The task stream issue button c7 is a button for issuing (release) the task stream sent from the save button c6 to the task stream management server 10 as a completed version that can be provided to the worker.

Fig. 10 shows a state in which an icon c102 indicating the end of a task flow is clicked and an object c104 indicates the icon c 102.

When the icon c102 indicating the end of the task stream is selected, the task stream graphic editor sets a button setting area d1 on the screen different from the case where the task template described above is selected. In the button setting area d1, a redo button d101 and a repeat button d102 are present.

The redo button d101 is a button set to be on when the task from the beginning of the task stream is allowed to be redone. In the case of redo, the results of the job prior to redo are discarded. If the rework button d101 is set to be on, the rework button is displayed on a screen presented to the operator, and by selecting the rework button, the operator can rework the job from the beginning of the task stream by setting the job before the rework to be absent. The rework button d101 is set to be on mainly when a task flow for a highly skilled worker is produced. When a task stream for an operator with low proficiency is produced, the rework button d101 is set to be off, and as a result, the rework button is not displayed on the screen presented to the operator, and the operator is prohibited from reworking the task from the beginning of the task stream while the job before the rework is set to be absent. By prohibiting rework, it is possible to prevent the operator with low skill from repeatedly making the same error, and collect what kind of error is made as the result of the work.

The repeat button d102 is a button set to be on when the job is allowed to be reworked from the beginning of the task stream, similarly to the rework button d 101. The difference from the redo button d101 is that the job result before the redo is not discarded. If the repetition button d102 is set to on, the repetition button is displayed on a screen presented to the operator, and by selecting the repetition button, the operator can save the job result of the job before the rework and rework the job from the task at the head of the task stream. The repeat button d102 is set to be on when, for example, a task flow for an operator of a high skill level is created, which is less likely to cause the same error to occur repeatedly, but which is to be collected as a result of the operation. When a task flow for a worker with low proficiency is produced, the repetition button d102 is set to be off, and as a result, the repetition button is not displayed on the screen presented to the worker, and the worker is prohibited from reworking the task from the beginning of the task flow. By prohibiting rework, the same error can be prevented from repeated occurrence by a less skilled operator.

Fig. 11 is a diagram for explaining the difference in screen images displayed on the operator terminal 20 side due to the setting of the skip button c501 and the back button c 502.

In fig. 11, fig. 11 (a) shows an example of a screen in the case where both of the skip button c501 and the back button c502 are set to on. On the other hand, fig. 11 (B) shows an example of a screen in the case where both of the skip button c501 and the back button c502 are set to off.

If the worker starts the job, the tasks defined by the task flow are sequentially presented to the worker. Specifically, text, a photograph (still image), a moving image, which will explain the working method, are displayed on the display of the wearable device 20A, or sound is output from the speaker of the wearable device 20A. 1 screen is displayed for 1 task, and the operator performs a job in accordance with the display, and if the instructed job is completed, the operator operates a forward (Next) button e3 to shift to the Next job.

When both the skip button c501 and the back button c502 are set to on, as shown in fig. 11 (a), the skip button e1 and the back button e2 are displayed together with the next button e3 on the screen displayed on the operator terminal 20 side. Therefore, for example, a highly skilled operator who does not need to perform maintenance of the apparatus each time can skip the task of maintenance of the apparatus by operating the skip button e1, or can redo the previous task by operating the back button e2 according to his/her own judgment.

On the other hand, when both the skip button c501 and the back button c502 are set to be off, as shown in fig. 11 (B), the skip button e1 and the back button e2 are not displayed on the screen displayed on the operator terminal 20 side, and only the forward button e3 is displayed. Therefore, for example, a worker with low proficiency is prohibited from skipping the task of the inspection of the device as a worker with high proficiency does, and the task is prohibited from being reworked according to the judgment of the person.

Fig. 12 is a diagram for explaining the difference in screen images displayed on the operator terminal 20 side due to the setting of the rework button d101 and the repeat button d 102.

In fig. 12, fig. 12 (a) shows an example of a screen in the case where both the redo button d101 and the repeat button d102 are set to on. On the other hand, fig. 12 (B) shows an example of a screen in the case where both the redo button d101 and the repeat button d102 are set to off.

When both the rework button d101 and the repeat button d102 are set to be on, as shown in fig. 12 (a), the rework button f3 and the repeat button f2 are displayed together with the finish button f1 on the screen displayed on the operator terminal 20 side. Therefore, the operator with high skill can operate the rework button f3 according to his/her judgment, discard the job record of the job before the rework, and rework the job from the head task. Further, by operating the repeat button f2, the operator with moderate proficiency can save the job record of the job before the rework without discarding the record, and can rework the job from the head task. Although the example in which both the replay button f3 and the repeat button f2 are displayed is shown here, only the repeat button f2 out of the replay button f3 and the repeat button f2 may be displayed by setting the replay button d101 to off and the repeat button d102 to on for an operator with moderate proficiency.

On the other hand, when both the rework button d101 and the repeat button d102 are set to be off, as shown in fig. 12 (B), the rework button f3 and the repeat button f2 are not displayed on the screen displayed on the operator terminal 20 side, but only the finish button f1 is displayed. Therefore, for example, a worker with low proficiency is prohibited from reworking a task from the beginning of the task according to his/her judgment, such as a worker with high proficiency.

As described above, the job support system 1 according to the present embodiment can set whether or not to skip and to rework in a task unit, and can set whether or not to discard a job record before rework and to save a job record before rework in a task unit (job) when creating or updating a task stream. The work support system 1 of the present embodiment, which provides the functions for setting these, can create a task flow suitable for the proficiency of the operator.

Fig. 13 is a flowchart showing a flow of task flow creation in the job support system 1 according to the present embodiment.

The task flow management server 10 provides a user interface (Web page) for creating a task flow to the manager terminal 30 in response to a request from the manager terminal 30 (step B1). When the manager creates a task flow for an operator with high proficiency (step B2: yes), the manager creates a task flow set 1, which is permitted to be reworked, using the provided user interface (step B3). Here, the 1 st setting is a setting that allows discarding the job result before the rework and the rework job, or a setting that allows retaining the job result before the rework and the rework job.

On the other hand, when a task flow for an operator with low proficiency is created (step B2: NO), the manager creates a task flow set at 2, such as a task flow for which rework is prohibited, using the provided user interface (step B4). The task flow management server 10 manages the task flow created in the manager terminal 30 using the provided user interface (step B5).

Fig. 14 is a flowchart showing a flow of task flow application in the job support system 1 according to the present embodiment.

The task flow management server 10 provides a user interface (Web page) for distributing task flows to operators (operator terminals 20) to the manager terminals 30 in response to a request from the manager terminals 30 (step C1). The manager sets allocation of a task flow to the worker (worker terminal 20) using the provided user interface (step C2).

The task flow management server 10 manages the setting of the allocation of the task flow to the worker (the worker terminal 20) performed in the manager terminal 30 using the provided interface (step C3), and provides the task flow allocated to the worker terminal 20 (the worker) to the worker terminal 20 (step C4). Next, the operator terminal 20 performs job support along the supplied task flow (step C5).

As described above, in the work support system 1 according to the present embodiment, for example, a task flow suitable for the proficiency of the worker is realized in which the task flow for the setting that allows the rework is created for the worker having high proficiency, and the task flow for the setting that prohibits the rework is created for the worker having low proficiency.

(Embodiment 2)

Next, embodiment 2 will be described. The work support system 1 of the present embodiment is assumed to have the same configuration as the work support system 1 of embodiment 1. Therefore, in this embodiment, the reference numerals used in embodiment 1 are also used. In the following, for the purpose of describing the work support system 1 of the present embodiment, reference is made to the accompanying drawings used for the purpose of describing the work support system 1 of embodiment 1.

As also described in the description of the work support system 1 of embodiment 1, a plurality of task flows may be allocated to each worker. In other words, each worker engages in a plurality of jobs.

When an operator carrying the operator terminal 20 and wearing the wearable device 20A connected to the operator terminal 20 like glasses starts any one of a plurality of jobs obtained as a list from the job flow management server 10, the operator operates a button of the operator terminal 20 or the wearable device 20A to select a job flow corresponding to the job from the plurality of job flows. The worker terminal 20 presents a list listing a plurality of task flows as selection branches to the worker, for example, and accepts an operation of selecting 1 task flow from among them. If the task flow is not stored in the storage unit 220, the worker terminal 20 downloads the selected task flow from the task flow management server 10. In this case, the operator may feel trouble about the operation itself of selecting 1 task flow from among the task flows.

The job support system 1 according to the present embodiment provides a function capable of efficiently selecting a task flow at the time of starting the job, and this will be described below.

The task flow creation management processing unit 111 of the task flow management server 10 in the job support system 1 according to the present embodiment transmits Web page data 121 capable of printing two-dimensional codes corresponding to the task flow data 122 stored in the storage unit 120, respectively, to the manager terminal 30. The Web page data 121 includes a script (program) for realizing a list of display task streams, selecting a target task stream from among them, and printing a two-dimensional code corresponding to the selected task stream.

Fig. 15 is a diagram showing an example of a screen for printing a two-dimensional code corresponding to a task stream displayed on the manager terminal 30 by the Web page data 121. The screen is not a screen provided exclusively for printing the two-dimensional code, and printing of the two-dimensional code is present as one of the actions that can be performed on the screen.

As shown in fig. 15, a list of task streams managed by the task stream management server 10 is displayed on a screen for printing two-dimensional codes. The list includes information of the version, last update date, last publisher, status, and the like of each task flow. The list includes a button g1 for instructing to generate a two-dimensional code. That is, a pair of buttons g1 and a task stream are displayed on the screen. The administrator can cause the screen to display the two-dimensional code corresponding to the task stream by clicking the button g1 of the column in which the target task stream is displayed, for example, with a mouse or the like.

Fig. 16 is a diagram showing an example of a display of a two-dimensional code corresponding to a certain task flow by the button g1 of the task flow being operated.

If the button g1 of a certain task stream is operated, as shown in fig. 16, a two-dimensional code area h1 in which a two-dimensional code h3 corresponding to the task stream and a button h2 indicating printing of the two-dimensional code h3 are arranged is provided on the screen. The manager clicks the button h2 in the two-dimensional code area h1 with a mouse or the like, for example, and can print the two-dimensional code h3 in the two-dimensional code area h1 with a printer connected to the manager terminal 30.

The two-dimensional code thus printed may be distributed to an operator, or may be attached to a work table, a wall, or the like in a work area. In the former case, for example, it is conceivable to distribute a two-dimensional code or the like corresponding to the job performed by each worker in the day. In the latter case, for example, it is conceivable to attach two-dimensional codes corresponding to respective operations performed by various types of working machines arranged in a production line to each work area, or the like.

The task flow execution processing unit 212 of the operator terminal 20 in the job support system 1 according to the present embodiment provides a function of reading the two-dimensional code printed as described above and automatically selecting the task flow indicated by the two-dimensional code.

Fig. 17 is a diagram showing an example of a flow of the task flow to start the task flow by list selection, not by two-dimensional code reading, in the operator terminal 20.

At the time of starting the operator terminal 20, the task flow execution processing unit 212 displays a screen in which the icon j1 for selecting a task flow from the list shown in fig. 17 (a) is in a selected state as a start screen. Icons in the selected state in the icon group are displayed in a larger size than other icons. If the icon j1 is selected (decided) by a button operation of the operator terminal 20 or the mobile device 20A, the task stream execution processing unit 212 displays a list screen for selecting 1 task stream from among the plurality of task streams as shown in fig. 17 (B1). Next, if 1 task stream is selected from the plurality of task streams displayed as selection branches on the list screen, the task stream execution processing unit 212 displays a screen that indicates the content of the task stream and that configures a start button for starting the task stream as shown in fig. 17 (B2). By selecting the start button on the screen, the download from the task stream management server 10 is executed if necessary, and the job along the task stream is started. The above is a flow until the task flow is started by normal list selection.

In contrast, fig. 18 shows an example of a flow of the task flow from the user terminal 20 to the start of the task flow by the two-dimensional code reading.

In the start screen shown in fig. 17 (a), when the icon j1 is in the selected state, if the operator performs an operation of moving the icon group left and right with the button of the terminal 20 or the wearable device 20A, the state is shifted to the state where another icon is selected. Here, it is assumed that the button of the operator terminal 20 or the wearable device 20A is operated so that the icon to be selected is positioned at the center of the screen. Fig. 18 (a) shows a screen in which an icon j2 for selecting a task stream by reading a two-dimensional code is in a selected state.

If the icon j2 is selected (decided) by a button operation of the user terminal 20 or the wearable device 20A, the task flow execution processing unit 212 shifts the user terminal 20 to a state in which the user terminal 20 photographs the two-dimensional code with the camera of the wearable device 20A. Specifically, as shown in fig. 18 (B1), the operator terminal 20 is caused to transition to a state in which the subject image captured by the camera of the wearable device 20A is displayed on the display of the wearable device 20A. At this time, the task flow execution processing section 212 displays the guide section k1 for alignment on the display of the wearable device 20A.

If the two-dimensional code h3 is included in the guide k1 and the camera is in focus, the task flow execution processing unit 212 automatically reads the two-dimensional code h 3. That is, a release operation or the like by the operator is not required. When the two-dimensional code h3 is read, the task flow execution processing unit 212 displays a screen as shown in fig. 18 (B2) that shows the content of the task flow indicated by the two-dimensional code h3 and has a start button for starting the task flow. By selecting the start button on the screen, the download from the task stream management server 10 is executed if necessary, and the job along the task stream is started.

As described above, in the job support system 1 according to the present embodiment, for example, by reading the two-dimensional code obtained from the manager or by reading the two-dimensional code attached to the table, the wall, or the like of the work area, it is possible to select a correct task flow without selecting an incorrect task flow or performing a troublesome operation. That is, the job support system 1 according to the present embodiment can efficiently select a task flow at the time of job start.

(Embodiment 3)

Next, embodiment 3 will be described. The work support system 1 of the present embodiment is assumed to have the same configuration as the work support system 1 of embodiment 1. Therefore, in this embodiment, the reference numerals used in embodiment 1 are also used. In the following, for the purpose of describing the work support system 1 of the present embodiment, reference is made to the accompanying drawings used for the purpose of describing the work support system 1 of embodiment 1.

As also described in the description of the job support system 1 according to embodiment 1, the task flow management server 10 provides an interface (Web page) for creating or updating a task flow to the manager terminal 30 in response to a request from the manager terminal 30. By using this Web page, the manager terminal 30 displays a screen for creating or updating a task flow as shown in fig. 9.

As described above, the screen is provided with the button setting area c5 for performing various settings for each task, and the detailed button c506 is present in the button setting area c 5. Fig. 9 shows a state in which the detailed button c506 is set to off. The detailed button c5 is a button set to be turned on when a text and a photograph (still image) representing a more detailed operation method are registered in addition to a text and a photograph (still image) representing an operation method registered in the preview area c4 in relation to a task template represented by the object c 104. Specifically, as described above, although 1 screen is displayed for substantially every 1 task for the operator, a detailed explanation, for example, using a plurality of screens can be presented to the operator regarding the task in which the detailed button c506 is set to be on.

That is, the job support system 1 of the present embodiment provides a function of setting the task flow to two levels. By setting the task flow to two levels, a worker with high proficiency can advance the task according to the simple description of the upper layer, while a worker with low proficiency can advance the task while further referring to the detailed description of the lower layer for a task that is not enough according to the simple description of the upper layer alone.

Fig. 19 shows a state of the screen in the case where the detailed button c506 is set to on.

If the detailed button c506 is set to on, a task stream graphic editor implemented by a script (program) contained in the Web page sets a detailed step edit screen m1 at, for example, the lower part of the task stream editor screen c 1.

In the detailed procedure edit screen m1, the manager can create a detailed task flow for the task by the same operation as in the case of editing on the task flow editor screen c 1. In the detailed procedure edit screen m1, the icon c101 indicating the start of the task flow and the icon c102 indicating the end of the task flow are not arranged, but the task templates are sequentially shifted from the left-positioned task template to the right (toward the screen). For example, if it is assumed that the task template c2-1 prompting the job method as text is placed first, and the task template c2-2 selected in the case of prompting the job method as a photograph (still image) is placed in the right-side adjacent position thereof, the text registered by the task template c2-1 is prompted first, and the photograph (still image) registered by the task template c2-2 is prompted by the operation of the advance button e 3. Fig. 19 shows a state in which a photograph (still image) m2 showing the job method is registered as a task at the beginning of a detailed task stream by the task template c 2-2.

If a task stream containing a detailed task stream is generated or updated, the task stream is uploaded to the task stream management server 10 through a script (program) contained in a Web page. That is, the task flow management server 10 has a function of providing an interface for creating or updating task flows of two layers, and a function of managing task flows of two layers.

Fig. 20 is a diagram showing a transition example of the screen of the operator terminal 20 in the case where the detailed button c506 is set to be on.

In fig. 20, fig. 20 (a) is a screen of a task before the detailed button C506 is set to the on task in the screen shown in fig. 19, fig. 20 (B) is a screen of a task itself after the detailed button C506 is set to the on task in the screen shown in fig. 19, and fig. 20 (C) is a screen of a task after the detailed button C506 is set to the on task in the screen shown in fig. 19. When the detailed button c506 is set to on, the task flow execution processing unit 212 of the operator terminal 20 displays a detailed button n1 for shifting to a detailed task flow, as shown in fig. 20 (B).

For example, if the task of fig. 20 (a) is completed, the operator with high skill operates the advance button e3 to shift to the task of fig. 20 (B), and if the task is completed, the operator operates the advance button e3 to shift to the task of fig. 20 (C), with the task of fig. 20 (B) being described simply. That is, the operator with high skill does not need to operate the detailed button n1, and may not follow the detailed task flow. When the skip button c501 is set to on, the task can be skipped and transferred to the next task.

In contrast, for example, by an operator who is a low-skilled operator and whose task in fig. 20 (B) is not enough for a simple explanation, the operator can shift to the head of the detailed task flow by operating the detailed button n 1. In fig. 20, fig. 20 (D1) is a screen of a task at the beginning of a detailed task stream, fig. 20 (D2) is a screen of a task subsequent to (D1) in the detailed task stream, and fig. 20 (D3) is a screen of a final task subsequent to (D2) and being a detailed task stream in the detailed task stream.

In the case of shifting to the task of fig. 20 (D1), the task of fig. 20 (D2) can be shifted by operating the forward button e3, and the task of fig. 20 (D1) can be reviewed on the screen of the task of fig. 20 (D2) by operating the backward button e 2. If the forward button e3 is operated on the screen of the task of fig. 20 (D2), the task is shifted to fig. 20 (D3). Since the task of fig. 20 (D3) is the last task of the detailed task flow, if the forward button e3 is operated on the screen of the task of fig. 20 (D3), the screen of the task of fig. 20 (B) in which the detailed button n1 is operated is returned.

As described above, the work support system 1 according to the present embodiment can handle two-level task flows including, for example, an upper-level task flow for a high-skilled worker and a lower-level task flow for a low-skilled worker. That is, the work support system 1 of the present embodiment can create a task flow suitable for the proficiency of the operator.

(Embodiment 4)

Next, embodiment 4 will be described. The work support system 1 of the present embodiment is assumed to have the same configuration as the work support system 1 of embodiment 1. Therefore, in this embodiment, the reference numerals used in embodiment 1 are also used. In the following, for the purpose of describing the work support system 1 of the present embodiment, reference is made to the accompanying drawings used for the purpose of describing the work support system 1 of embodiment 1.

In addition, as described above, at the time of updating the task stream, the task stream graphic editor implemented by the script (program) included in the Web page displays the editing screen of the task stream on which the update object is arranged. The update of the task flow may be started by selecting a task flow to be updated from a list of task flows managed by the task flow management server 10 as shown in fig. 15, for example.

Incidentally, when a certain task flow has been updated, if the task flow before the update is downloaded by the operator terminal 20 or if the task flow is in progress along the task flow before the update, there is no possibility that a problem may occur in that the task cannot be performed suddenly, for example, because the result of the task uploaded from the operator terminal 20 does not coincide with the task flow after the update.

The job support system 1 according to the present embodiment provides a function of managing task flows in a divided manner (managing the task flows for each version) and causing the task flows before update and the task flows after update to coexist, and this will be described below.

Fig. 21 is a diagram for explaining a flow of update of a task flow of the job support system 1 according to the present embodiment. The display of the screen shown in fig. 21 and the transition of the screen are realized by a script (program) included in a Web page provided from the task flow management server 10 to the manager terminal 30.

In fig. 21, fig. 21 (a) is an example of a screen for displaying a task flow to be updated. As described above, this screen can be displayed by selecting a task flow to be updated from a list of task flows managed by the task flow management server 10 as shown in fig. 15, for example.

For example, a region for presenting version information of a task stream to be updated is provided on the left part (facing the screen) of the screen. Here, it is shown that the task flow of the update object is the first edition (version: 00001) that is not updated. In addition, for example, an edit button p1 for shifting to a screen for editing a task stream as shown in fig. 9 is arranged at an upper portion of the screen. The manager can shift to a screen for editing the task stream by operating the edit button p1.

In fig. 21, fig. 21 (B) is an example of a screen for editing a task stream displayed by operating the edit button p1 on the screen of fig. 21 (a). On this screen, for example, editing is performed to change the text presentation operation method to presentation with a photograph (still image), change a photograph (still image), add/delete a task, change settings of various buttons, or the like for a certain task.

Further, on the screen for generating or editing the task stream, as described above, a task stream release button c7 for releasing the created or updated task stream as a completed version that can be provided to the operator is provided. If editing is performed on a certain task flow and the task flow release button c7 is operated, the updated task flow is in a state that can be provided to the worker (the worker terminal 20). The updated task stream is transferred to the task stream management server 10 when the save button c6 is operated after the editing is completed. The task flow management server 10 manages the updated task flow together with the task flow before the update. That is, the task flow management server 10 manages the task flow data 122 in segments (manages per version).

In fig. 21, fig. 21 (C) is an example of a screen for displaying a task stream to be updated, which is displayed by operating the task stream issue button C7 on the screen in fig. 21 (B). That is, if editing of the task stream is ended and the task stream release button c7 is operated, the screen after the edit button p1 is operated is returned. As shown in fig. 21 (C), it is shown that the task flow is a modified version (version: 00002). The update of the task stream may be performed by editing the task stream of the latest version at this point in time or by editing the task stream of an old version other than the latest version. By selecting version information on the screen, a task stream can be selected as a basis.

Next, a task flow obtained by reflecting such update to the operator (operator terminal 20) will be described.

Fig. 22 shows an example of a screen displayed on the manager terminal 30 by the Web page data 121 provided to the manager terminal 30 by the task stream allocation processing unit 113 of the task stream management server 10 and used for displaying a list of task streams allocated to the worker (the worker terminal 20). Fig. 22 shows a state in which a list of task flows of an operator (operator terminal 20) to which 3 task flows are assigned is displayed.

As shown in fig. 22, a withdraw (recall) button q1 and a Viewer (Viewer) button q2 are arranged in pairs with the task flow on the screen. When the withdraw button q1 of a certain task flow is operated, a request for deleting the task flow assigned to the worker (the worker terminal 20) is transmitted to the task flow management server 10. The task flow assignment processing unit 113 of the task flow management server 10 that received the instruction deletes the information of the instructed task flow held in the entry for the worker (the worker terminal 20) of the worker data 123.

In this case, the task flow assignment processing unit 113 instructs the operator terminal 20 to delete the instructed task flow. When the task flow (task flow data 122) is stored in the storage unit 220, the task flow storage processing unit 211 of the operator terminal 20 that has received the instruction deletes the task flow stored in the storage unit 220.

Then, as described in embodiment 1, by reassigning the updated task flow to the worker (the worker terminal 20), for example, at the time of first performing the work after reassignment, the updated task flow is downloaded by the worker terminal 20, and the replacement of the updated task flow from the task flow before the update is completed. Depending on the situation of each worker, the manager may replace the task flow at a point in time when the task is not obstructed.

The viewer button q2 is a button for referring to a task stream downloaded to an operator (operator terminal 20). By operating the viewer button q2, the manager can refer to the task flow downloaded to the worker (the worker terminal 20).

As described above, in the job support system 1 according to the present embodiment, the task flow before the job update and the task flow after the update can coexist so as not to cause a trouble in the job due to the update of the task flow.

Several embodiments of the present invention have been described, but these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the spirit of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

Description of the reference numerals

1 … A work support system; 10 … task flow management server; 20 … operator terminals; 20a … wearable device; 30 … manager terminals; 100 … task manager; 110 … control unit; 111 … task flow creation management processing unit; 112 … an operator management processing unit; 113 … task flow assignment processing section; 114 … a job support processing unit; 115 … job result management processing unit; 120 … storage; 121 … Web page data; 122 … task flow data; 123 … worker data; 130 … communication section; 200 … worker support programs; 210 … control unit; 211 … task flow storage processing section; 212 … task flow execution processing section; 213 … job result record transmission processing section; 214 … an environment setting processing section; 220 … storage; 221 … specification data; 222 … job result data; 230 … communication unit; 240 … I/O processing section.

Claims

1. A work support system, characterized in that,

The device is provided with:

a task flow management server that manages task flows indicating operation steps;

A manager terminal for creating or updating the task flow managed by the task flow management server; and

An operator terminal for supporting execution of a job along a task flow provided from the task flow management server;

the task flow management server includes a task flow creation management processing unit that provides a user interface for creating or updating a task flow to the manager terminal, and receives and manages a task flow created or updated by the manager terminal using the user interface from the manager terminal;

The task flow creation management processing unit provides the manager terminal with the user interface capable of selectively applying the 1 st setting for the high-proficiency worker and the 2 nd setting for the low-proficiency worker to create or update the task flow.

2. The work support system according to claim 1, wherein,

The 1 st setting is a setting for allowing a task to be reworked from a task at the head of a task stream composed of a plurality of tasks;

the 2 nd setting is a setting for prohibiting the rework of the job.

3. The work support system according to claim 2, wherein,

The task flow management server includes a job result management processing unit that receives and manages a job result performed along the task flow from the operator terminal;

The 1 st setting is either a setting that allows the work result before the rework to be discarded and the work to be reworked or a setting that allows the work result before the rework to be saved and the work to be reworked.

4. The work support system according to claim 1, wherein,

The 1st setting is a setting applied to task units constituting a task flow, which allows transition to a subsequent task in an unfinished state;

The 2 nd setting is a setting for prohibiting the transition to a subsequent task in the unfinished state.

5. The work support system according to claim 1, wherein,

The 1 st setting is a setting applied to a task unit constituting a task flow, which allows a return to a previous task and a rework from the previous task;

The 2 nd setting is a setting for prohibiting the return to the previous task and performing the rework from the previous task.

6. The work support system according to claim 1, wherein,

The task flow creation management processing unit provides a2 nd user interface for printing a two-dimensional code corresponding to the managed task flow to the manager terminal;

The worker terminal includes a task flow execution processing unit that reads the two-dimensional code printed by the manager terminal using the 2 nd user interface and selects a task flow corresponding to the read two-dimensional code from a plurality of task flows that can be provided from the task flow management server.

7. The work support system according to claim 1, wherein,

The task stream creation management processing unit can manage two hierarchical task streams including a1 st task stream and a2 nd task stream for specifying a corresponding task set for a task in the 1 st task stream;

The 1 st setting is a setting applied to a task unit constituting the 1 st task flow, in which a transition path from the 1 st task flow to the 2 nd task flow is not set;

the 2 nd setting is a setting for setting the transition path from the 1 st task flow to the 2 nd task flow.

8. The work support system according to claim 1, wherein,

The task flow creation management processing unit can manage task flows for each version;

the task flow management server includes a task flow assignment processing unit that provides the manager terminal with a 3 rd user interface for assigning or de-assigning a target task flow to or from among the task flows of the plurality of versions managed by the task flow creation management processing unit;

The task stream allocation processing unit is configured to,

Providing, to the operator terminal, a task flow assigned to the operator terminal by the manager terminal using the 3 rd user interface, among the task flows managed by the task flow creation management processing unit;

When the manager terminal uses the 3 rd user interface to de-allocate the task stream allocated to the worker terminal, the manager terminal instructs the deletion of the de-allocated task stream; and

The task flow of the old version applied to the operator terminal can be replaced with the task flow of the latest version at any time through the 3 rd user interface.

9. The work support system according to claim 8, wherein,

The 3 rd user interface displays a task flow assigned to the operator terminal according to a request.

10. A job support method for a job support system including a job flow management server for managing a job flow indicating a job step, a manager terminal for creating or updating the job flow managed by the job flow management server, and a worker terminal for supporting execution of a job along the job flow provided from the job flow management server,

The task flow management server described above,

Providing a user interface for the manager terminal, which can selectively apply the 1 st setting for the high-proficiency operator and the 2 nd setting for the low-proficiency operator to produce or update the task stream; and

And receiving and managing a task stream created or updated by the manager terminal using the user interface from the manager terminal.