CN111381629A

CN111381629A - Work support system and work support method

Info

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

Abstract

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

Description

Work support system and work support method

Technical Field

The present invention relates to an operation support system and an operation support method.

Background

In recent years, electronic support has been widely adopted for an operator who is working by wearing a wearable device or carrying a tablet personal computer. For example, in the case of a glasses-type wearable device, since the display can be viewed while performing a work, the work can be performed even by an unskilled person by advancing the work in steps presented step by step, for example. In an operation support system for electronically supporting an operator performing an operation, an operation process is referred to as a task flow (task flow) or the like.

The work support system is used not only to support an operator who is working, but also to collect a work result of the operator, and to provide guidance to the operator, feedback for improving a task flow, and the like.

Documents of the prior art

Patent document

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

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

Patent document 3: international publication No. 2011/070967

Patent document 4: japanese Kohyo publication 2013-508862

Disclosure of Invention

Problems to be solved by the invention

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

However, there are not only those having high proficiency but also those having low proficiency among the operators who perform work at the work site. The operator with different proficiency is all operated under the same condition, so that the overall operation efficiency may be reduced. For example, it is not uncommon for a highly skilled operator to be ineffective in advancing the work step by step along a task flow created by an operator with low assumed skill.

An object of the present invention is to provide a work support system and a work support method capable of creating a task flow or the like suitable for the skill of an operator, for example.

Means for solving the problems

According to an aspect, a work support system includes a task flow management server, a manager terminal, and a worker terminal. The task flow management server manages a task flow representing a work process. The manager creates or updates the task flow managed by the task flow management server by using the terminal. The operator terminal supports execution of a 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 a user interface for creating or updating a task flow to the administrator terminal, and receives and manages a task flow created or updated by the administrator terminal using the user interface from the administrator terminal. The task flow creation management processing unit provides the user interface to the administrator terminal, the user interface being capable of creating or updating a task flow by selectively applying the 1 st setting for a worker with high proficiency and the 2 nd setting for a worker with low proficiency.

Drawings

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

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

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

Fig. 4 is a diagram showing an example of an 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 an external appearance of a main body of a wearable device connected to an operator terminal in the operation support system according to embodiment 1.

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

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

Fig. 8 is a flowchart showing a flow of task flow improvement intended in the work 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 displayed in the work support system according to embodiment 1.

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

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

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

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

Fig. 14 is a flowchart showing a flow of a job flow application in the work 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 job flow displayed in the job support system according to embodiment 2.

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

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

Fig. 18 is a diagram showing an example of a flow until a task flow is started by reading a two-dimensional code by a terminal of an operator in the work 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 work support system according to embodiment 3.

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

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

Fig. 22 is a diagram showing an example of a screen showing assignment of a task flow to an operator terminal 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 explained.

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

As shown in fig. 1, the work support system 1 of the present embodiment includes a task flow management server 10, a terminal 20 for an operator, and a terminal 30 for an administrator. A glasses-type wearable device 20A is connected to the operator terminal 20. Here, the operator terminal 20 used by connecting the wearable device 20A is assumed, but the operator terminal 20 itself may be wearable. The operator 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 a work of manufacturing a product in a manufacturing plant, for example. 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 in the first industry such as agriculture and the third industry such as the service industry. Here, it is assumed that the work support system 1 is introduced into a company that operates a manufacturing industry.

The task flow management server 10 is a computer that manages a task flow representing a work process. The task flow management server 10 may be a computer of an enterprise that manages a manufacturing industry and that is introduced into the work support system 1, or may be a computer of an enterprise that provides a function of supporting a work as a service. The task flow management server 10 may be any computer that can communicate with the worker terminal 20 and the administrator 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 storage device 13 is loaded with the task management program 100, 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 on 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 worker terminal 20 and the administrator terminal 30.

The task flow management server 10 provides a user interface for making or updating a task flow to the administrator-use terminal 30. Specifically, the administrator terminal 30 is a computer capable of operating a Web browser, and the task flow management server 10 provides a Web page including a script (program) to the administrator terminal 30 (a 1). The administrator terminal 30 is used by an administrator who is responsible for the overall management of jobs, for example, a Personal Computer (PC). The screen on the administrator terminal 30 denoted by reference numeral b1 is a screen for displaying a Web page supplied from the task flow management server 10 by a Web browser.

That is, the administrator accesses the task flow management server 10 by using the administrator terminal 30, acquires a Web page from the task flow management server 10, and displays a screen b1 for creating or updating a task flow on the administrator terminal 30. 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 a task flow created or updated by an operation on a screen to the task flow management server 10. Thus, the administrator can create or update the task flow by an operation on the screen of the administrator 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 administrator terminal 30 to the task flow management server 10 for registration with the task flow management server 10 is also referred to as upload.

A task flow created or updated by an administrator is a time-series connection of a plurality of tasks. Each task is a task for explaining a work method by text, photograph (still image), moving image, voice, or the like, or a task for instructing an operator to execute instructions such as photographing a photograph (still image) or moving image in the terminal 20, reading a barcode, or the like.

The task flow management server 10 stores the task flow transferred from the administrator terminal 30 in the storage device 13. Then, the task flow management server 10 provides the task flow created or updated by the administrator to the worker terminal 20 which is a computer carried by the worker (a 3). The transfer of the task flow from the task flow management server 10 to the operator terminal 20 is performed, for example, when the operator starts a job corresponding to the task flow in a state where the task flow is not supplied to the operator terminal 20. The transfer of the task flow from the task flow management server 10 to the worker terminal 20 at this time is also called downloading. Fig. 1 shows only 1 operator terminal 20, but the number of operator terminals 20 is the same as that of 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 using the operator terminal 20.

The task flow management server 10 manages which task flow is assigned to each worker. The manager performs assignment of task flows to the respective workers. That is, the task flow management server 10 provides a user interface (Web page) for assigning a task flow to each worker to the administrator terminal 30.

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 into 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 operator 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 peripheral wall of the housing of the operator terminal 20 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 operator terminal 20. The wearable device 20A is provided with a display, a camera, a microphone, a speaker, and the like, and the operator transmits and receives image data, audio data, and the like to and from the wearable device 20A via the I/O device 26 using the terminal 20.

The worker terminal 20 stores the job flow transferred from the job flow management server 10 in the storage device 23. The operator uses the terminal 20 to support execution of the work along the task flow. For example, the operator terminal 20 transfers image data for displaying a screen explaining a working 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. The operator wearing the wearable device 20A as wearing glasses performs work while viewing the screen. The operator terminal 20 receives an image captured by the camera of the wearable device 20A, for example, from the wearable device 20A, and when a job ends, for example, transmits the image as a result of the job to the task flow management server 10 (a 4). As a result of the job transmitted to the task flow management server 10, for example, a required time of each task in the task flow, etc. may be included in addition to the image, etc. The task flow management server 10 stores the work result received from the worker terminal 20 in the storage device 13.

Further, communication can be performed between the operator terminal 20 and the administrator terminal 30. For example, an image photographed by the operator terminal 20 may be transmitted to the administrator terminal 30, the status may be transmitted to the administrator, and an instruction from the administrator may be requested. The instruction in this case may be a voice, or may be, for example, an image obtained by overlaying a comment on a transmitted image. In this way, the administrator plays a role of not only creating or updating the task flow but also performing backward support corresponding to the operator.

The above is a basic flow of cooperation of the task flow management server 10, the operator terminal 20, and the administrator terminal 30 in the work 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 the CPU11 loading and executing the task management program 100 installed in the storage device 13 into the main memory 12. In addition, the control unit 110 may be configured as an electronic circuit. That is, the control unit 110 may be implemented 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 work support processing unit 114, and a work result management processing unit 115.

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

For example, when a new worker terminal 20 is added along with an increase in workers, the worker management processing unit 112 transmits, to the administrator terminal 30, Web page data 121 for registering the new worker terminal 20 with the workflow management server 10. The worker management processing unit 112 uses the Web page data 121 to store the identifier of the worker terminal 20 newly registered on the manager terminal 30 side as worker data 123 in the storage unit 120. The registered worker terminal 20 may be deleted on the manager terminal 30 side by using the Web page data 121 transmitted from the worker management processing unit 112 to the manager terminal 30. For example, when the worker terminal 20 used by a certain worker fails and a replacement with a new worker terminal 20 is necessary, the worker terminal 20 before the replacement can be deleted and the worker terminal 20 after the replacement can be registered. The operator data 123 is a data structure in which entries (entries) are secured for each operator terminal 20, for example, with the identifier of the operator terminal 20 as an index.

The job flow assignment processing unit 113 transmits Web page data 121 for assigning a job flow to an operator to the administrator terminal 30. The Web page data 121 is transmitted to the administrator terminal 30 in a state including a list of the task flow data 122 and a list of the worker data 123 stored in the storage unit 120 at that point in time. The Web page data 121 includes a script (program) for selecting a target operator from a list of operators (operator terminals 20) and selecting a task flow to be assigned to the selected operator 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 perform a plurality of tasks.

The job flow assignment processing unit 113 records the setting of assignment of a job flow to an operator performed by the administrator terminal 30 using the Web page data 121, into an entry (record) secured for the operator (the operator terminal 20) in the operator data 123 stored in the storage unit 120. Further, the job 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) secured for the operator (the operator terminal 20) in the operator data 123. The task flow assignment processing unit 113 also sends an instruction to the operator terminal 20 to delete the task flow to be executed.

The work support processing unit 114 notifies the worker terminal 20 of a list of the task flows assigned to the worker (the worker terminal 20) by the task flow assignment processing unit 113, or transmits the requested task flow to the worker terminal 20 from the list.

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

Fig. 3 is a diagram showing an example of 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 controller 210 is configured by the CPU21 loading and executing the operator support program 200 installed in the storage device 23 into the main memory 22. In addition, the control unit 210 may be configured as an electronic circuit. That is, the control unit 210 may be implemented 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 job flow saving processing unit 211, a job flow execution processing unit 212, a job result record transmission processing unit 213, and an environment setting processing unit 214.

The job flow storage processing unit 211 stores the job flow data 122 transferred from the job flow management server 10 in the storage unit 220. Further, 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 accordance with an instruction from the task flow management server 10.

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

The job result record transmission processing unit 213 stores the image and the like obtained as a result of the job by the job 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. Each time the job 1 time is completed, the job result record transmission processing unit 213 transfers the job result data 222 corresponding to the job stored in the storage unit 220 to the task flow management server 10. The transmission of the job result data 222 from the worker terminal 20 to the task flow management server 10 is also referred to as uploading.

The environment setting processing unit 214 performs setting for making the operator terminal 20 and the wearable device 20A connected to the operator terminal 20 easy to use for each operator who actually uses the operator terminal 20 and the wearable device 20A, and stores the setting as profile data 221 in the storage unit 220. For example, a wearable device main body 1024 (see fig. 4) of the glasses type wearable device 20A, which will be described later, is attached to one of the left and right temples. Normally, the wearable device main body 1024 is attached to the right temple when the right eye is the worker of the main eye, and the wearable device main body 1024 is attached to the left temple when the left eye is the worker of the main eye. The wearable device main body 1024 is turned upside down when attached to the right temple and when attached to the left temple. The display is then also turned upside 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 the specification data 221.

Fig. 4 shows an example of the external appearance of the wearable device 20A. The wearable device 20A is provided with a spectacle frame 1142 and a wearable device main body 1024. The spectacle frame 1142 may be a shape in which lenses are removed from normal spectacles, and may be worn on the face of an operator. The frame 1142 may be configured to receive eyeglasses.

The spectacle frame 1142 includes attachment tools 1144 for attaching and detaching the wearable device main body 1024 to the left and right temples. In fig. 4, the attachment tool 1144 of the temple on the right side of the operator is not illustrated since it is shielded by the wearable device main body 1024. As described above, the wearable device main body 1024 includes the display 1124 (see fig. 5), and since the display 1124 is viewed by a single eye, the left and right temples are provided with the attachment tools 1144 to attach the wearable device main body 1024 to the main eye side. Further, the wearable device 20A for the right eye and the left eye in which the wearable device main body 1024 is fixed to the spectacle frame 1142 may be prepared without detachably attaching the wearable device main body 1024 to the spectacle frame 1142 with the attaching tool 1144. Further, the wearable device main body 1024 may be attached to the head of the operator using a helmet, a visor, or the like, instead of the spectacle frame 1142.

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

In a state where the wearable device main body 1024 is attached to the attachment tool 1144, the engagement piece 1128 can move forward and backward in the attachment tool 1144. Therefore, the wearable device main body 1024 can adjust its front-rear position so that the operator focuses on the display 1124. Further, the attachment tool 1144 is rotatable about an axis 1144A orthogonal to the temple, and after the wearable device main body 1024 is attached to the eyeglass frame 1142, the vertical 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 main body 1024 can be sprung up from the spectacle frame 1142. Thus, even when the visual field is obstructed 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 of or put back from the visual field of the operator without taking away or putting back the entire wearable device 20A from the face.

The wearable device main body 1024 includes a side surface portion along a temple of the spectacle frame 1142 and a front surface portion positioned in the line of sight of an eyeball of one of the operators. The angle of the front part relative to the side part can be adjusted.

As shown in fig. 4, a camera 1116, a lamp 1118, and a camera LED1120 are provided on the outer surface of the front portion. The lamp 1118 is auxiliary lighting that emits light when photographing in a dark area. The camera LED1120 is turned on when a photograph or a moving image is taken, and is used to recognize that a person to be photographed is taking a photograph.

The 1 st, 2 nd, and 3

rd buttons

1102, 1104, and 1106 are provided on the upper side surface of the side surface portion of the wearable device main body 1024 attached to the right temple. In addition, when the dominant eye of the operator is the left eye, the wearable device main body 1024 is attached to the left temple. Since the wearable device main body 1024 is turned upside down depending on whether it is attached to the right side or the left side, the 1 st, 2 nd, and 3

rd buttons

1102, 1104, and 1106 may be provided on both the upper side and the lower side of the side surface 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. The touchpad 1110 and the 4 th button 1108 can be operated with an index finger. The

buttons

1102, 1104, and 1106 are disposed at positions that can be operated by the index finger, middle finger, and ring finger, respectively, when the wearable device body 1024 is disposed on the right side. The touch panel 1110 can detect a case where an operator moves a finger up and down and back as indicated by an arrow on the surface thereof. The detection of the movement includes a movement of a slide (flick) in which the finger is swiftly wiped, in addition to a movement of a drag (drag) which moves while keeping the finger in contact.

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. Note that, the reason why the 4 th button 1108 is provided not on the upper portion of the side surface portion but on the outer surface of the side surface portion is because of a spatial relationship, and the 4 th button 1108 may be provided on the upper portion of the side surface portion in the same manner as the 1 st to 3

rd buttons

1102, 1104, and 1106. The illuminance sensor 1114 detects ambient illuminance for automatically adjusting 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 formed of an LCD is provided on the inner side of the front portion. A microphone 1126, a speaker 1130, and an engagement piece 1128 are provided inside the side surface portion. The microphone 1126 is disposed in front of the side surface portion, the speaker 1130 is disposed behind the side surface portion, and the engagement piece 1128 is disposed behind the side surface portion. Headphones may also be used in place of the speakers 1130. In this case, the microphone and the headphone may be provided integrally as a headset.

Fig. 6 shows an example of connection between the operator terminal 20 and the wearable device 20A. A receptacle 1132 into which a plug 1146A of one end of a cable 1146 of USB type-C (registered trademark) standard is inserted is provided behind the side surface portion. The plug 1146B at the other end of the cable 1146 of the usb type-C standard is inserted into the connector 1207 of the usb type-C standard on the upper end surface of the operator terminal 20. In this way, the wearable device main body 1024 is connected to the operator terminal 20 via the USB type-C standard cable 1146, and an image or the like is transmitted between the wearable device main body 1024 and the operator terminal 20. The wearable device main body 1024 may be connected to the operator terminal 20 by wireless communication such as wireless LAN and 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. However, the wearable device main body 1024 may be provided with a driving power source.

Fig. 7 shows an example of the appearance of the operator terminal 20. The operator terminal 20 is a small PC that can be held with one hand, and 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 wearable while being accommodated in a pocket of a work clothes, a holster attached to a belt, or a shoulder bag.

A 5-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 an enter button) 1202e is disposed on the front surface of the operator terminal 20, and a fingerprint sensor 1204 is disposed below the button. The fingerprint sensor 1204 is used for user authentication when the worker logs in (log in) with the terminal 20. The 5 button 1202 is capable of inputting a command.

Further, each of the buttons 1202a to 1202d of the 5-button 1202 may be assigned to a numeral, and a password may be input by using the 5-button 1202 to perform user authentication at the time of login. In this case, the fingerprint sensor 1204 may be omitted. Since numerals are assigned to 4 buttons other than the decision button 1202e, the number is only 4. Thus, it is possible that the randomly entered number corresponds to the password. However, if the number of digits of the password is increased, the probability that the randomly input number coincides with the password can be reduced. The authentication by the 5-button 1202 may be performed also in the operator terminal 20 provided with the fingerprint sensor 1204.

The 5-button 1202 can perform the same operation as that of the

buttons

1102, 1104, 1106, 1108 of the wearable device body 1024 and the touch panel 1110. Since the operator cannot see how the

buttons

1102, 1104, 1106, and 1108 of the wearable device main body 1024 and the touch panel 1110 are operated, the operator may need to be accustomed to performing a desired operation. Since the

buttons

1102, 1104, 1106, 1108 and the touch panel 1110 are small, they may be difficult to operate. In the present embodiment, the operator can perform the same operation using the 5-button 1202 of the terminal 20, and therefore such a fear is eliminated.

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

A card slot 1218 for a memory card is provided on one side surface (a side surface on the left side 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 right side surface as viewed from the front) of the operator terminal 20 is provided with a slot 1210 for a kenscoton lock (registered trademark), a power switch 1212, a power LED1213, a DC IN/battery LED1214, a DC terminal 1216, and a cooling air vent 1222. The power LED1213 is disposed near the power switch 1212 and is lit during the power-on period. The DC IN/battery LED1214 shows whether or not the battery is the state of the operator terminal 20 during charging and the remaining amount of the battery. The operator terminal 20 can be driven by a battery, but can be driven in a state where an AC adapter is connected to the DC terminal 1216. Although not shown, the back surface can be configured to replace the battery by one touch operation (one touch).

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

First, a task flow is created by a manager (step a1), and a job (execution) along the task flow is performed by a worker (step a 2). If the worker's job is finished, the job result is uploaded to the task flow management server 10 (step A3).

The administrator checks (reviews) the job results managed by the task flow management server 10 (step a4), and updates the task flow (step a 5). After that, the task flow is improved by repeating the steps a2 to a 5.

Next, a function of creating a task flow suitable for the skill level of the operator, which is 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 displayed on the administrator terminal 30 using a Web page supplied from the task flow management server 10. The Web page implements a task flow graphic editor having a user interface for creating or updating a task flow on the administrator terminal 30.

When creating a task flow, the task flow graphic editor first displays an editing screen on which an icon indicating the start of the task flow indicated by reference numeral c101 and an icon indicating the end of the task flow indicated by reference numeral c102 are arranged (task flow editor screen c 1). The task flow graphic editor displays a task template list c2 on the side of the task flow editor screen c 1. The administrator creates a task flow by placing the target task templates in the task template list c2 on the task flow editor screen c 1. Upon update of the task flow, the task flow graphic editor displays an editing screen of the task flow in which the update object is arranged.

The task template is placed on the task flow editor screen c1 by, for example, a mouse operation called drag and drop (drag and drop). The task templates arranged on the task flow editor screen c1 are connected by a mouse operation such as drawing a line segment (arrow) from the area where a task template is arranged before the task template is arranged to the area where a task template is arranged after the task template is arranged. The same mouse operation is performed between the icon c101 indicating the start of the task flow and the task template at the head, and between the last task template and the icon c102 indicating the end of the task flow. That is, the administrator can create a task flow by arranging and connecting task templates (c 103-1 to c4) between an icon c101 indicating the start of a task flow and an icon c102 indicating the end of the task flow on the task flow editor screen c 1.

Note that the task template c 2-1 shown in fig. 9 is a task template selected when the job method is presented in text. For example, when a preceding task is ended and the task is shifted to, a text indicating a work method is presented to the worker.

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

The task template c 2-3 is a task template selected when the job method is presented as a moving image.

The task template c 2-4 is a task template selected when the job method is presented by voice.

Task template c 2-5 is a task template selected in the case of a read indicating a barcode.

The job template c 2-6 is a job template selected when the job method is presented in PDF (registered trademark).

The task template c 2-7 is a task template selected when accessed to information to be referred to by a URL.

The task templates 2 to 8 are task templates selected in a case where photographing of a photograph (still image) is instructed.

The task templates 2 to 9 are task templates selected when shooting of a moving image is instructed.

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

Further, the task flow graphic editor displays an object (object) c104 representing a task template for editing the object. For example, by indicating an area where the target task template is arranged with a pointer and performing an operation of a mouse called click (click) or the like, the object c104 can be moved to indicate the task template. For example, in the case where the object c104 represents the task template c 2-1, that is, in the case where the task template c 2-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 indicates an area (task template c 103-2) in which a task template c 2-2 is arranged, and in the case where the task template c 2-2 is an editing object, the task flow graphic editor sets a preview area c4 for registering a photograph (still image) indicating a work method on the screen.

That is, the administrator can register a text, a photograph (still image), and the like to be presented to the worker in preview area c 4.

Further, the task flow 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 c 502. These buttons c501 and c502 are slide-type buttons, and slide rightward (toward the screen) is on and slide leftward (toward the screen) is off.

The skip button c501 is a button that is set to on when the task is allowed to skip to the next task. If the skip button c501 is set to ON (ON), the skip button is displayed ON a screen presented to the operator, and the operator can skip the job and shift to the next job by selecting the skip button. The skip button c501 is set to on mainly when a task flow for a worker with high skill level is created. When a task flow for a worker with low skill level is created, 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 passing the task and shifting to the next task.

The back button c502 is a button set to on when a return to a previous task is permitted and the previous task is redone. If the back button c502 is set to on, the back button is displayed on a screen for presenting 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 on mainly when a task flow for a highly skilled operator is created. When a task flow for a worker with low skill level is created, the back button c502 is set to off, and as a result, the back button is not displayed on the screen presented to the worker, and the worker is prohibited from returning to the previous task and redoing the previous task. By prohibiting the rework, what kind of mistakes the worker with low skill has made can be collected as the work result.

In the button setting area c5, there are also a photograph shooting button c503, a moving image shooting button c504, an outgoing call button c505, and a Detail (Detail) button c 506. These buttons c503 to c506 are also slide-type buttons (toward the screen), and slide rightward to open (toward the screen) and slide leftward to close.

The photo shooting button c503 is a button set to on when a button for taking a photo 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 outgoing call button c505 is a button set to on when a button for performing communication with the administrator terminal 30 is displayed. The detail button c506 will be described later.

Further, the task flow graphic editor configures a save button c6 and a task flow release button c7 on the screen. The save button c6 is a button for sending the created or updated task stream to the task stream management server 10. The task flow issuance button c7 is a button for issuing (releasing) the task flow transmitted from the save button c6 to the task flow 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 the task flow is clicked and an object c104 indicates the icon c 102.

When the icon c102 indicating the end of the task flow is selected, the task flow graphic editor sets a button setting area d1 on the screen, which is different from the case where the task template is selected. In this button setting area d1, there are a redo button d101 and a repeat button d 102.

The redo button d101 is a button set to on when a job is permitted to be redone from the task at the head of the task stream. In the case of redo, the job results before redo are discarded. If the redo button d101 is set to on, the redo button is displayed on the screen presented to the operator, and by selecting the redo button, the operator can redo the job from the task at the head of the task stream while setting the job before redoing to be absent. The redo button d101 is set to on mainly when a task flow for an operator with high skill level is created. When a task flow for an operator with low skill level is created, the redo button d101 is set to off, and as a result, the redo button is not displayed on the screen presented to the operator, and the operator is prohibited from redoing the task from the task at the head of the task flow by setting the task before redoing to be absent. By prohibiting the redo, it is possible to prevent the operator with low skill from repeatedly making the same mistake, and to collect what kind of mistake was made as the operation result.

The repeat button d102 is a button that is set to on when a job is permitted to be redone from the task at the head of the task stream, as in the redo button d 101. The difference from the redo button d101 is that the job result before redo is not discarded. If the repeat button d102 is set to on, a repeat button is displayed on a screen presented to the operator, and by selecting the repeat button, the operator can redo the job from the task at the head of the task stream while retaining the job result of the job before redoing. The repeat button d102 is set to on when creating a task flow for an operator with moderate skill level, which is less likely to repeat the same error, but which error has been made as a result of the operation. When a task flow for an operator with low skill level is created, the repeat button d102 is set to off, and as a result, the repeat button is not displayed on the screen presented to the operator, and the operator is prohibited from redoing the job from the task at the head of the task flow. By prohibiting the rework, it is possible to prevent the operator with low skill from repeatedly making the same mistake.

Fig. 11 is a diagram for explaining a difference in the screen 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 a case where both the skip button c501 and the back button c502 are set on. On the other hand, fig. 11(B) shows an example of a screen in a case where both the skip button c501 and the back button c502 are set to off.

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

When both the skip button c501 and the back button c502 are turned 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 inspection of the device every time, for example, can operate the skip button e1 to skip a task of inspection of the device, or can operate the back button e2 to redo a previous task by the judgment of the person.

On the other hand, when both the skip button c501 and the back button c502 are set to 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, an operator with low skill is prohibited from skipping a task for inspection of the apparatus like an operator with high skill, and is also prohibited from redoing the previous task in accordance with the judgment of the person.

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

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

When both the redo button d101 and the repeat button d102 are turned on, as shown in fig. 12(a), the redo button f3 and the repeat button f2 are displayed together with the complete button f1 on the screen displayed on the operator terminal 20 side. Therefore, the operator with high skill can operate the redo button f3 in accordance with the judgment of the user, discard the job record of the job before redoing, and redo the job from the first task. Further, by operating the repeat button f2, an operator with moderate skill can keep the job record of the job before the redo without discarding the job record, and can redo the job from the first task. In addition, although the example in which both the redo button f3 and the repeat button f2 are displayed is described here, the redo button d101 may be turned off and the repeat button d102 may be turned on for an operator with moderate skill, and only the repeat button f2 of the redo button f3 and the repeat button f2 may be displayed.

On the other hand, when both the redo button d101 and the repeat button d102 are set to off, as shown in fig. 12(B), the redo button f3 and the repeat button f2 are not displayed on the screen displayed on the operator terminal 20 side, and only the complete button f1 is displayed. Therefore, for example, a worker with low skill is prohibited from redoing the work from the top task according to the judgment of the person, such as a worker with high skill.

In this way, the job support system 1 according to the present embodiment can set the possibility of skipping and the possibility of redoing in task units when creating or updating a task flow, and can set the possibility of redoing in task flow (job) units after discarding a job record before redoing and the possibility of redoing after retaining a job record before redoing. The work support system 1 of the present embodiment, which provides the functions of these, can create a task flow suitable for the skill of the operator.

Fig. 13 is a flowchart showing a flow of task flow creation in the work 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 administrator terminal 30 in response to a request from the administrator terminal 30 (step B1). When the manager creates a task flow for a worker with high skill (step B2: YES), the manager creates a task flow with the 1 st setting such as permission of redo using the provided user interface (step B3). Here, the 1 st setting is a setting for allowing a job result before redoing to be discarded and a job to be redone, or a setting for allowing a job result before redoing to be retained and a job to be redone.

On the other hand, when a task flow for a worker with low skill level is created (NO in step B2), the administrator creates a task flow set at the 2 nd setting such as no redo, using the provided user interface (step B4). The task flow management server 10 manages the task flow created in the administrator terminal 30 using the provided user interface (step B5).

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

The task flow management server 10 provides the administrator terminal 30 with a user interface (Web page) for assigning a task flow to an operator (operator terminal 20) in response to a request from the administrator terminal 30 (step C1). The administrator sets assignment 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 assignment of a task flow to an operator (operator terminal 20) performed in the administrator terminal 30 using the provided interface (step C3), and provides the task flow assigned to the operator terminal 20 (operator) to the operator terminal 20 (step C4). Next, the operator uses the terminal 20 to perform work support along the provided task flow (step C5).

As described above, in the work support system 1 of the present embodiment, for example, a task flow suitable for the skill level of the operator is realized in which a set task flow such as permission of redo is created for an operator with high skill level and a set task flow such as prohibition of redo is created for an operator with low skill level.

(embodiment 2)

Next, embodiment 2 will be explained. 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, the reference numerals used in embodiment 1 are also applied to this embodiment. In the following, in order to explain the work support system 1 of the present embodiment, the drawings used for explaining the work support system 1 of embodiment 1 are sometimes applied.

As described in the description of the work support system 1 according to embodiment 1, a plurality of task flows may be assigned to each worker. In other words, each worker performs a plurality of tasks.

When an operator who carries the operator terminal 20 and wears the wearable device 20A connected to the operator terminal 20 like glasses starts any one of a plurality of jobs listed in the job flow management server 10, a button of the operator terminal 20 or the wearable device 20A is operated to select a job flow corresponding to the job from the plurality of job flows. The operator terminal 20 presents a list in which a plurality of task flows are listed as options to the operator, for example, and accepts an operation of selecting 1 task flow from the list. If the job flow is not stored in the storage unit 220, the worker downloads the selected job flow from the job flow management server 10 by using the terminal 20. In this case, there is a possibility that the selection of a different task flow may be mistaken, and the operation of selecting 1 task flow from a plurality of task flows may inherently be troublesome for the operator.

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

The job flow creation management processing unit 111 of the job flow management server 10 in the job support system 1 according to the present embodiment transmits Web page data 121, which can be printed in two-dimensional codes corresponding to the job flow data 122 stored in the storage unit 120, to the administrator terminal 30. The Web page data 121 includes a script (program) for displaying a list of job flows, selecting a target job flow from the list, and printing a two-dimensional code corresponding to the selected job flow.

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

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

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

If the button g1 of a certain job flow is operated, as shown in fig. 16, a two-dimensional code area h1 in which a two-dimensional code h3 corresponding to the job flow and a button h2 instructing to print the two-dimensional code h3 are arranged is provided on the screen. The administrator can print the two-dimensional code h3 in the two-dimensional code area h1 by clicking the button h2 in the two-dimensional code area h1 with a mouse or the like, for example, by a printer connected to the administrator terminal 30.

The two-dimensional code thus printed may be distributed to an operator, for example, or may be pasted to a 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 a work performed by each worker on 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 machine tools arranged in a production line to respective operation areas.

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

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

When the operator terminal 20 is started, the task flow execution processing unit 212 displays, as a start screen, 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. The icon in the selected state among the icon group is displayed in a larger size than the other icons. If the icon j1 is selected (determined) by the button operation of the operator terminal 20 or the wearable device 20A, the task flow execution processing unit 212 displays a list screen for selecting 1 task flow from the plurality of task flows as shown in fig. 17 (B1). Next, if 1 task flow is selected from among the plurality of task flows displayed as option branches on the list screen, the task flow execution processing unit 212 displays a screen as shown in fig. 17(B2) in which the start button for starting the task flow is arranged, indicating the content of the task flow. By selecting the start button on the screen, downloading from the task flow management server 10 is performed if necessary, and a job along the task flow is started. The above is a flow until the task flow is started by normal list selection.

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

In the start screen shown in fig. 17(a) in which the icon j1 is selected, if the operator performs an operation of moving the icon group left and right with the buttons of the terminal 20 or the wearable device 20A, the screen transitions to a state in which another icon is selected. Here, it is assumed that the operator operates the buttons of the terminal 20 or the wearable device 20A 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 flow by reading a two-dimensional code is in a selected state.

If the icon j2 is selected (determined) by a button operation of the operator terminal 20 or the wearable device 20A, the task flow execution processing unit 212 shifts the state in which the operator terminal 20 photographs the two-dimensional code to 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 unit 212 displays the guide k1 for alignment on the display of the wearable device 20A.

If the two-dimensional code h3 is contained in the guide k1 and the focus of the camera is located, the two-dimensional code h3 is automatically read by the task flow execution processing section 212. That is, the releasing operation or the like by the operator is not necessary. When the two-dimensional code h3 is read, the job flow execution processing unit 212 displays a screen on which a start button for starting the job flow is arranged, as shown in fig. 18(B2), indicating the content of the job flow indicated by the two-dimensional code h 3. By selecting the start button on the screen, downloading from the task flow management server 10 is performed if necessary, and a job along the task flow is started.

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

(embodiment 3)

Next, embodiment 3 will be explained. 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, the reference numerals used in embodiment 1 are also applied to this embodiment. In the following, in order to explain the work support system 1 of the present embodiment, the drawings used for explaining the work support system 1 of embodiment 1 are sometimes applied.

As described in the description of the work 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 administrator terminal 30 in response to a request from the administrator terminal 30. By using the Web page, the administrator uses the terminal 30 to display 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 where the detail button c506 is set to off. The detail button c5 is a button set to on when a text and a photograph (still image) indicating a more detailed job method are registered in addition to a text and a photograph (still image) indicating a job method registered in the preview area c4 with respect to the task template indicated by the object c 104. Specifically, as described above, although the operator basically displays 1 screen for each 1 task, the operator can be presented with a detailed description using a plurality of screens for example regarding the task for which the detail button c506 is set to on.

That is, the work support system 1 of the present embodiment provides a function of setting a task flow to two levels. By setting the task flow to two levels, the operator with high skill can advance the task according to the simple explanation of the upper level, while the operator with low skill can advance the task while referring to the detailed explanation of the lower level for the task which is not enough according to the simple explanation of the upper level.

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

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

In the detailed step editing screen m1, the administrator 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 step editing 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, and the task templates on the left side (on the screen) are sequentially shifted to the task templates on the right side. For example, if it is assumed that the task template c 2-1 presenting the job method in text is placed first and the task template c 2-2 selected in the case of presenting the job method in photograph (still image) is placed adjacent to the right side thereof, the text registered by the task template c 2-1 is presented first and the photograph (still image) registered by the task template c 2-2 is presented by the operation of the advance button e 3. Fig. 19 shows a state in which a photograph (still image) m2 indicating a job method is registered as the top task of the detailed task stream from the task template c 2-2.

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

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

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

For example, if the worker with high skill finishes the task of fig. 20(a), the worker operates the forward button e3 to shift to the task of fig. 20(B), the task of fig. 20(B) is described only for simplicity, and if the worker finishes the task, the worker operates the forward button e3 to shift to the task of fig. 20 (C). 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 job can be skipped and shifted to the next job.

On the other hand, for example, an operator with low skill level or an operator whose task in fig. 20(B) is insufficient by a simple explanation can shift to the task at the head of the detailed task flow by operating the detailed button n 1. In fig. 20, fig. 20(D1) is a screen of the first task of the detailed task flow, fig. 20(D2) is a screen of the task subsequent to (D1) in the detailed task flow, and fig. 20(D3) is a screen of the last task subsequent to (D2) in the detailed task flow.

In the case of the task transition to fig. 20(D1), the task transition to fig. 20(D2) can be made by operating the forward button e3, and the screen of the task of fig. 20(D1) can be viewed again by operating the backward button e2 on the screen of the task of fig. 20 (D2). If the forward button e3 is operated on the screen of the task in fig. 20(D2), the flow shifts to the task in 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 returns to the screen of the task of fig. 20(B) in which the detailed button n1 is operated.

In this way, the work support system 1 of the present embodiment can handle a two-level task flow including, for example, an upper-level task flow for a highly skilled operator and a lower-level task flow for a less skilled operator. That is, the work support system 1 of the present embodiment can create a task flow suitable for the skill of the operator.

(embodiment 4)

Next, embodiment 4 will be explained. 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, the reference numerals used in embodiment 1 are also applied to this embodiment. In the following, in order to explain the work support system 1 of the present embodiment, the drawings used for explaining the work support system 1 of embodiment 1 are sometimes applied.

As described above, when a task flow is updated, a task flow graphic editor implemented by a script (program) included in a Web page displays an editing screen on which a task flow to be updated is placed. The task flow update can 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 is updated, if the task flow before update is downloaded by the operator terminal 20 or if a work is being performed along the task flow before update, there is a possibility that a problem of a sudden job becoming impossible may occur, for example, due to a result of the work uploaded from the operator terminal 20 not matching the task flow after update.

The work support system 1 of the present embodiment provides a function of performing a classification management of a task flow (management for each version) and a coexistence of a task flow before update and a task flow after update, which will be described below.

Fig. 21 is a diagram for explaining a flow at the time of updating the job flow in the work support system 1 according to the present embodiment. The display of the screen and the transition of the screen shown in fig. 21 are realized by a script (program) included in a Web page provided from the task flow management server 10 to the administrator 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.

On the left part of the screen (toward the screen), for example, a region for presenting version information of a task flow to be updated is provided. Here, the task stream showing the update object is an initial version (version: 00001) that is not updated. Further, on the upper part of the screen, for example, an edit button p1 for shifting to a screen for editing a task stream as shown in fig. 9 is arranged. The administrator can transition to a screen for editing the task stream by operating the edit button p 1.

In fig. 21, (B) of fig. 21 is an example of a screen for editing a task flow displayed by operating an editing button p1 on the screen of fig. 21 (a). On this screen, for example, for a certain task, editing is performed such as changing the presentation method with text to presentation with a photograph (still image), changing a photograph (still image), adding/deleting a task, or changing the settings of various buttons.

On the screen for creating or editing the task flow, as described above, a task flow delivery button c7 is arranged for delivering the created or updated task flow as a completed version that can be provided to the operator. When editing is performed on a certain task flow and the task flow delivery button c7 is operated, the updated task flow is in a state in which it can be provided to the operator (operator terminal 20). When the editing is completed and the save button c6 is operated, the updated task flow is transferred to the task flow management server 10. The task flow management server 10 manages the updated task flow together with the task flow before update. That is, the task flow management server 10 manages the task flow data 122 by generations (by management for each version).

In fig. 21, (C) of fig. 21 is an example of a screen displaying a task flow to be updated, which is displayed by operating the task flow delivery button C7 on the screen of fig. 21 (B). That is, if the editing of the task flow is finished and the task flow distribution button c7 is operated, the screen returns to the screen after the editing button p1 is operated. As shown in FIG. 21(C), it is shown that the task flow is a modified version (version: 00002). The task flow may be updated by editing the task flow of the latest version at that point in time, or by editing the task flow of an old version other than the latest version. By selecting version information on the screen, a task flow as a base can be selected.

Next, a task flow obtained by performing such updating is reflected on the operator (operator terminal 20).

Fig. 22 shows an example of a screen displayed on the administrator terminal 30 by the Web page data 121 for displaying a list of the task flows assigned to the workers (worker terminals 20), which is provided to the administrator terminal 30 by the task flow assignment processing unit 113 of the task flow management server 10. Fig. 22 shows a state in which a task flow list of the worker (worker terminal 20) to which 3 task flows are assigned is displayed.

As shown in fig. 22, a recall (Revoke) button q1 and a Viewer (Viewer) button q2 are arranged on the screen in pairs with the task flow. When the withdrawal button q1 of a certain task flow is operated, a request for deleting the task flow assigned to the worker (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.

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

Then, as described in embodiment 1, the updated workflow is newly assigned to the operator (operator terminal 20), and the updated workflow is downloaded by the operator terminal 20 at the time of the first operation after reassignment, for example, so that the replacement of the updated workflow from the pre-updated workflow is completed. The administrator may replace the task flow when the job is not interrupted, depending on the status of each worker.

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

As described above, in the work support system 1 according to the present embodiment, the task flow before the work update and the task flow after the update can be made to coexist, so that the update of the task flow does not cause trouble to the work.

Several embodiments of the present invention have been described, but these embodiments are presented as examples and are not intended to limit the scope of the invention. These new embodiments may be implemented in other various forms, and various omissions, substitutions, and changes may 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 equivalent scope thereof.

Description of the reference symbols

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

Claims

1. An operation support system is characterized in that,

the disclosed device is provided with:

a task flow management server for managing a task flow representing a work process;

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 the administrator terminal with a user interface for creating or updating a task flow, and receives and manages the task flow created or updated by the administrator terminal using the user interface from the administrator terminal;

the task flow creation management processing unit provides the user interface to the administrator terminal, the user interface being capable of creating or updating a task flow by selectively applying the 1 st setting for a worker with high proficiency and the 2 nd setting for a worker with low proficiency.

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

the 1 st setting is a setting for allowing redo of a job 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 redo 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 worker terminal;

the 1 st setting is either a setting for allowing the job result before the redo to be discarded and the job to be redone, or a setting for allowing the job result before the redo to be saved and the job to be redone.

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

the 1 st setting is a setting that is applied to a task unit constituting a task flow and allows a transition to a subsequent task in an uncompleted state;

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

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

the 1 st setting is a setting that is applied to a task unit constituting a task flow, allows a return to a preceding task, and redos from the preceding task;

the 2 nd setting is a setting for prohibiting a return to a preceding task and performing a redo operation from the preceding 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 administrator terminal;

the operator terminal includes a job flow execution processing unit that reads the two-dimensional code printed by the administrator terminal using the 2 nd user interface, and selects a job flow corresponding to the read two-dimensional code from among a plurality of job flows provided by the job flow management server.

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

the task flow creation management processing unit is capable of managing two hierarchical task flows including a1 st task flow and a2 nd task flow for specifying a corresponding task set for a task in the 1 st task flow;

the 1 st setting is a setting that is applied to a task unit constituting the 1 st task flow and does not set a transition path from the 1 st task flow to the 2 nd task flow;

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

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

the task flow creation management processing unit may manage the task flow for each version;

the task flow management server includes a task flow assignment processing unit that provides a3 rd user interface to the administrator terminal, the 3 rd user interface being used to assign a target task flow to the worker terminal or to release assignment of a task flow assigned to the worker terminal from among a plurality of versions of task flows managed by the task flow creation management processing unit;

the above-mentioned task flow distribution processing section,

providing the worker terminal with a task flow assigned to the worker terminal by the administrator terminal using the 3 rd user interface, among the task flows managed by the task flow creation management processing unit;

when the assignment of the task flow assigned to the worker terminal is released by the manager terminal using the 3 rd user interface, the manager terminal instructs the worker terminal to delete the task flow from which the assignment has been released; and is

The old version of the task flow applied to the operator terminal can be replaced with the latest version of the task flow at an arbitrary timing 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 worker terminal according to a request.

10. A work support method for a work support system including a task flow management server for managing a task flow representing a work process, a manager terminal for creating or updating the task flow managed by the task flow management server, and a worker terminal for supporting execution of a work along the task flow supplied from the task flow management server,

the above-mentioned task flow management server is,

providing the user interface for creating or updating a task flow by selectively applying a1 st setting for a worker with high proficiency and a2 nd setting for a worker with low proficiency to the administrator terminal; and is

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