JP6508246B2 - Processing execution system - Google Patents

Description

The present invention relates to a processing system.

  An administrator or the like defines a series of processes in which input, conversion, and output of fixed data are combined as a workflow, and a processing execution system is known which executes each process in order when a user starts execution of the workflow. It is done. As the user may select and execute a workflow defined in advance, it is possible to save time and effort to individually execute each process, and to efficiently perform business.

  FIG. 25 is a diagram showing an example of processing included in the workflow. Processing 1 is scanning of a document, processing 2 is compression, processing 3 is OCR (Optical Character Recognition), processing 4 is PDF conversion, and processing 5 is mail transmission. A combination of such processing to define a workflow is often performed by a user-side administrator. The user can select a desired workflow from several workflows defined by the administrator (see, for example, Patent Document 1). Patent Document 1 describes an image forming apparatus that displays a workflow definition name in association with processing included in each workflow.

  By the way, it is sufficient to have at least one apparatus for executing a workflow, and conventionally, for example, an apparatus such as an MFP (Multi Function Peripheral) has performed all processing. However, when trying to complete a workflow with one machine, a process that can not be executed by one machine can not be included in the workflow, and there is a demand for some users to combine many types of processes to define a workflow.

  Therefore, it is considered that a plurality of apparatuses execute each process included in the workflow. In addition, when a plurality of apparatuses execute each process, it is considered to support the work and improve operability because the workflow manager performs the work of correlating the process with the apparatus. However, conventionally, there is a problem that no GUI capable of flexibly defining a workflow is provided.

  An object of the present invention is to provide a definition information creation system in which the definition of a workflow is easy in view of the above problems.

The present invention relates to a process execution system having a plurality of processing devices for executing a workflow including a plurality of processing selection operation and the selection for selecting a process to be executed by the one processor from among the plurality of processing and mapping operation for associating the processing unit for each processing to execute has been processed and the processing selected by the operator, and a display control means for displaying on the display device a setting screen for receiving the selection received via the setting screen has the operation and the association operation and the processing unit to execute each process has been identified, the definition information generation means for defining the definition information workflow to be executed by a plurality of processing devices, wherein the definition information generation Means is defined as a connection process for transmitting the definition information from a first processing device inside a firewall to a second processing device on the Internet If it defined in distribution, and generating the definition information having a monitoring process in which the connection process executes processing said second processing device the first processing device after the monitors.

It is possible to provide a process execution system in which workflow definition is easy.

It is a figure showing an example of correspondence of processing and a device. FIG. 7 is an example of a diagram schematically illustrating a procedure in which a manager defines a workflow. It is an example of the system configuration figure of a processing execution system. FIG. 2 is an example of a hardware configuration diagram of a workflow execution request device as an MFP. It is an example of the hardware block diagram of a workflow process server, a management server, or administrator PC. It is a figure which shows an example of the functional block diagram of a management server and administrator PC. It is a figure which shows an example of an apparatus list | wrist table. It is a figure which shows an example of flow definition information. It is an example of the figure which shows the flow definition information of XML format. It is an example of a functional block diagram of a workflow execution request device (MFP) and a workflow processing server. It is an example of the flowchart figure which shows the procedure in which an administrator PC and a management server create flow definition information. It is an example of the figure explaining the definition of a workflow. It is an example of the figure explaining change of matching. It is a figure which shows an example of the matching screen when an administrator selects "it interlock | cooperates to the change of matching." It is a figure which shows an example of the matching screen when an administrator selects "it is not interlocked with the change of matching." It is a figure which shows an example of the matching screen at the time of a manager selecting "inquire or change a correlation." It is a figure which shows the example of a display when a management matches the processing 1-5 with a physical device. It is an example of the sequence diagram which shows the procedure which a process execution system performs a workflow. It is an example of the figure showing the example of a screen at the time of selection of a workflow. It is an example of the schematic block diagram of a process execution system (Example 2). It is an example of the figure explaining the outline at the time of workflow execution of a processing execution system. It is an example of the figure explaining the flow definition information for monitoring. It is an example of the flowchart figure which shows the procedure in which an administrator PC and a management server create flow definition information (Example 2). It is an example of the sequence diagram which shows the procedure which a process execution system performs a workflow (Example 2). It is a figure which shows an example of the process contained in a workflow.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the technical scope of the present invention is not limited to the present embodiment.

  FIG. 1 is a diagram showing an example of correspondence between processing and an apparatus. For example, processes 1, 2, 4, and 5 are associated with the MFP, and process 3 is associated with the server. The workflow administrator uses some graphical user interface (GUI) to associate the process with the device.

  FIG. 2 is an example of a diagram schematically illustrating a procedure in which the administrator defines a workflow in the process execution system according to the present embodiment. In FIG. 2, the selection of processes for making processes 1 to 5 into one workflow has already been completed. The upper part of the figure is referred to as "logical flow column" (corresponding to the first column in the claims), and the lower part is referred to as "physical device flow column" (corresponding to the second column in the claims). The administrator performs an operation of associating the physical device that executes the processes 1 to 5 with the process. Hereinafter, the screen of FIG. 2 is referred to as a correspondence screen, and the correspondence screen is displayed on the administrator PC (Personal Computer).

  FIG. 2A: on the association screen, a device list such as icons or names of physical devices capable of executing any one or more of the processes 1 to 5 is displayed. The user operates a pointing device such as a mouse or a touch panel to drag the device icon 61 of the desired physical device to the physical device flow column. At this time, the administrator PC can automatically display the device icon of the physical device capable of executing the processes 1 to 5 in the physical device flow column.

  FIG. 2 (b): The administrator PC connects the process icons 62 of processes 1 to 5 with the apparatus icon 61 respectively. By connecting the processing icons of the processes 1 to 5 and the apparatus icons by lines, the administrator can visually grasp the correspondence between the processes 1 to 5 and the physical apparatus.

  FIG. 2 (c): The administrator may want to change the association. For example, when associating the process 3 with the workflow processing server, the administrator drags the device icon of the workflow processing server to the physical device flow column. Then, the pointing device is dragged from the processing icon of processing 3 to the device icon of the workflow processing server. As a result, the association between process 3 and the MFP can be changed to association between process 3 and the workflow processing server.

  FIG. 2D: The administrator PC connects the processing icon of processing 3 and the device icon of the workflow processing server with a line. As a result, the administrator can visually grasp that the process 3 and the workflow processing server are associated with each other. The physical devices associated with the processes 4 and 5 remain the original MFP, but it is also possible to automatically associate downstream processes with the workflow processing server. Details will be described later.

  As described above, the processing execution system of the present embodiment creates a logical flow and a flow of a physical device corresponding to that on the same view, so that the administrator can visually associate the processing with the physical device. In addition, since the automatic correspondence can be made, the amount of operation to be performed by the administrator can be reduced. Also, even after being automatically associated, they can be easily changed.

  Hereinafter, a person who defines flow definition information is referred to as a manager, whereas a person who executes a workflow is referred to as a user.

Also, information defining a workflow is referred to as “flow definition information”. The flow definition information includes at least the following information.
(i) Order of processing 1 to 5
(ii) Physical device to process
(iii) Job setting required for each of the processes 1 to 5 The job setting includes, for example, the resolution and density of reading, an e-mail address, and the like. Further, job settings include those set by the administrator and those set by the user who executes the workflow.

[Configuration example]
FIG. 3A shows an example of a system configuration diagram of the process execution system 500. The workflow execution request device 200, the workflow processing server 100, and the management server 250 are connected via the network 400. Also, the administrator PC 150 can connect to the network.

  The network 400 is a LAN or a WAN in which a plurality of LANs are connected via a router or the like. Also, the Internet may be included unless a firewall is considered. The network 400 may be wired, or some or all may be wireless LANs (such as IEEE 802.11b / a / g / n). Furthermore, the network 400 includes a communication network configured for mobiles such as a cellular phone network, a WiMAX network, and a PHS network. Even if each device of the process execution system 500 communicates on a one-to-one basis in an ad hoc mode of a wireless LAN or the like, it is included in the network 400.

  The workflow execution request device 200 is a device that executes a workflow by itself and requests the workflow processing server 100 to execute a workflow. For example, although the MFP 201, the portable terminal 202, and the client terminal 203 are illustrated, the information processing apparatus having the communication function can be the workflow execution request apparatus 200. One or more workflow execution request devices 200 exist in the process execution system 500. The MFP 201 is an apparatus having a function of forming an image, such as a copier, a scanner, a printer, and a fax machine. The MFP 201 may have one or more of these functions. The MFP 201 processes, for example, image data created by scanning an original as job data, and transmits the job data to the workflow processing server 100 together with flow definition information.

  The mobile terminal 202 is a terminal that a user carries or holds, such as a mobile phone, a smartphone, a tablet terminal, a PDA (Personal Digital Assistant), or a digital camera. For example, image data that is job data captured by a camera of a mobile phone or a digital camera and flow definition information are transmitted to the workflow processing server 100.

  The client terminal 203 is an information processing apparatus used by a user, such as a notebook PC, a desktop PC, a workstation, and a video conference terminal. For example, application data created by an application and Web data acquired from the Web are transmitted as job data to the workflow processing server 100 together with flow definition information.

  Although the workflow execution request apparatus 200 is an apparatus directly operated by the user, the job data does not have to be created or stored by the apparatus directly operated by the user. For example, the client terminal may designate job data stored in a NAS (Network Attached Storage) or another device and transmit it from the NAS or the like to the workflow processing server 100 (the workflow processing server 100 goes for reading). It is possible.

  The workflow processing server 100 is an information processing apparatus such as a PC, a server apparatus, and a thin client. The MFP 201 can also be the workflow processing server 100. The workflow processing server 100 executes one or more of a series of processes included in the workflow. One workflow processing server 100 may exist, but two or more may exist. For example, when job data and flow definition information are received as job data from the workflow execution request apparatus 200, the job data is subjected to an OCR process according to the flow definition information, or transmitted by e-mail.

  The management server 250 receives a workflow definition from the administrator PC 150. The management server 250 stores one or more flow definition information defined by the administrator, and transmits it from the workflow execution request device 200 in response to a request. The user can select a workflow to execute from the workflow list.

  As described above, the workflow execution request apparatus 200 mainly performs input processing, and the workflow execution request apparatus 200 and the workflow processing server 100 mainly perform conversion processing. Is the workflow execution request device 200 or the workflow processing server 100.

  Also, the job data to be input includes physical media such as manuscripts and electronic data such as word processor data, and the output includes physical media such as paper and storage on a document box, and electronic such as electronic mail There is data.

  FIG. 3B shows another example of the system configuration of the process execution system 500. The workflow execution request device 200 and the workflow processing server 100 are connected via the network 400. The workflow processing server 100 shown in FIG. 3B has the functions of the workflow processing server 100 and the management server 250 shown in FIG. Therefore, the workflow processing server 100 of FIG. 3B stores the flow definition information and executes the process. Although either structure of FIG. 3 (a) and (b) may be sufficient, it demonstrates based on the structure of FIG. 3 (a) by this embodiment.

  FIG. 4 shows an example of a hardware configuration diagram of the workflow execution request apparatus 200 as the MFP 201. The MFP 201 includes a controller 130, an operation panel 125, a facsimile control unit (FCU) 126, an imaging unit 127, and a printing unit 128.

  The controller 130 includes a CPU 114, an ASIC 116, an NB (north bridge) 115, an SB (south bridge) 117, a MEM-P (system memory) 111, a MEM-C (local memory) 112, and an HDD (hard disk drive). And 113), a memory card slot 123, an NIC (network interface controller) 118, a USB device 119, an IEEE 1394 device 121, and a Centronics device 122.

  The CPU 114 is an IC for executing various information processing, and executes an application in parallel in units of processes on the OS or platform. The ASIC 116 is an IC for image processing. The NB 115 is a bridge for connecting the CPU 114 and the ASIC 116. The SB 117 is a bridge for connecting the NB 115 and peripheral devices and the like. The ASIC 116 and the NB 115 are connected via, for example, an AGP (Accelerated Graphics Port).

  The MEM-P 111 is a memory connected to the NB 115. The MEM-C 112 is a memory connected to the ASIC 116. The HDD 113 is a storage connected to the ASIC 116 and is used to store image data, document data, programs, font data, form data, and the like. The HDD 113 stores various applications (copy application, scanner application, printer application, fax application, etc.) and a program 131. The program 131 is for receiving the definition of the workflow by the user.

  The memory card slot 123 is connected to the SB 117 and used to set (insert) the memory card 124. The memory card 124 is a flash memory such as a USB memory or an SD memory, and is used to distribute the program 131. The program 131 can also be distributed by downloading it from the predetermined server to the MFP 201.

  The NIC 118 is a controller for performing data communication using a MAC address or the like via the network 400 or the like. The USB device 119 is a device for providing a serial port compliant with the USB standard. The IEEE 1394 device 121 is a device for providing a serial port conforming to the IEEE 1394 standard. The Centronics device 122 is a device for providing a parallel port conforming to the Centronics specification. It is connected to the NB 115 and the SB 117 through the NIC 118, the USB device 119, the IEEE 1394 device 121, the Centronics device 122, and a PCI (Peripheral Component Interconect) bus.

  The operation panel 125 is hardware (an operation unit) for the user to input to the MFP 201, and is hardware (a display unit) for displaying the menu screen by the MFP 201. The operation panel 125 is connected to the ASIC 116. The FCU 126, the imaging unit 127, and the printing unit 128 are connected to the ASIC 116 via a PCI (Peripheral Component Interconect) bus.

  The imaging unit 127 optically scans the document placed on the contact glass, A / D converts the reflected light, performs image processing, and processes color or monochrome digital data (hereinafter referred to as image data). Generate

  The printing unit 128 has, for example, a tandem type photosensitive drum, modulates a laser beam based on the image data described above and PDL data received from the user PC, and scans the photosensitive drum to form a latent image. Toner is attached to the latent image and the developed image for each page is transferred to the sheet by heat and pressure. Not limited to such an electrophotographic plotter, an inkjet plotter engine that ejects droplets to form an image may be used.

  The FCU 126 is connected to the network 400 via the NIC 118 and communicates according to, for example, T.37, T.38 standards, or according to a communication procedure connected to a public communication network, for example, G3, G4 standards. Send and receive Further, even if image data is received when the power of the MFP 201 is OFF, the printing unit 128 can be activated to print the image data on a sheet.

  FIG. 5 shows an example of a hardware configuration diagram of the workflow processing server 100, the management server 250 or the administrator PC 150. The workflow processing server 100, management server 250 or administrator PC 150 are connected to a bus, CPU 301, ROM 302, RAM 303, HDD 304, graphic board 305 to which display 320 is connected, keyboard / mouse 306, media drive 307, and network A communication unit 308 is included. The CPU 301 develops the program 310 stored in the HDD 304 in the RAM 303 and executes the program to control each component to perform input / output or process data. The ROM 302 stores a BIOS and a start program for reading the bootstrap loader from the HDD 304 to the RAM 303. The bootstrap loader reads the OS from the HDD 304 into the RAM 303.

  The HDD 304 may be a non-volatile memory and may be a solid state drive (SSD) or the like. The HDD 304 stores an OS, a device driver, and a program 310 that provides functions to be described later. The program instructs on the display 320, and a GUI screen created by the graphic board 305 is displayed.

  The keyboard / mouse 306 is an input device that receives a user's operation. A media drive 307 reads and writes data on optical media such as compact discs, DVDs and Blu-ray discs. Alternatively, data may be read from or written to a memory card such as a flash memory. The network communication unit 308 is, for example, an Ethernet (registered trademark) card for connecting to a LAN. The OS and program 310 perform processing of TCP / IP (UDP / IP) and application layer protocols. There are various application layer protocols, for example, Simple Network Management Protocol (SNMP), HTTP, FTP, Server Message Block (SMB), and the like.

  The program 310 is a file in an installable format or an executable format, and is recorded and distributed on a computer readable recording medium. Also, the program 310 is distributed as a file in an installable format or an executable format from a server (not shown).

[Function, table]
FIG. 6 is a diagram showing an example of a functional block diagram of the management server 250 and the administrator PC 150. As shown in FIG. The administrator PC 150 has a screen data request unit 51, an operation reception unit 52, a display control unit 53, and a flow definition information transmission unit 54. The operation receiving unit 52 receives an operation of the keyboard / mouse 306 by the administrator. The screen data request unit 51 requests the management server 250 for screen data. The display control unit 53 is, for example, a browser application, analyzes the screen data, and displays it on the display 320. The screen displayed on the display 320 is the association screen. When the operation receiving unit 52 receives an operation of the administrator on the association screen displayed on the display 320, flow definition information is defined. The flow definition information transmission unit 54 transmits the flow definition information defined by the administrator to the management server 250.

  The management server 250 includes a screen data DB 44, an apparatus list table 45, a workflow list DB 38, a connection information DB 46, a screen data transmission unit 41, a flow definition information reception unit 42, and a flow definition information creation unit 43. The screen data DB 44 stores, for example, screen data described in HTML, JavaScript (registered trademark), XML, and the like. Further, in the device list table 45, a device list of physical devices capable of executing processing is registered, and in the workflow list DB 38, a list of workflows defined by the administrator is registered. The physical device is a component of the processing execution system 500 capable of executing a workflow, and more specifically, is a workflow execution request device 200 and a workflow processing server 100.

  When the screen data transmission unit 41 receives a request from the administrator PC 150, the screen data transmission unit 41 reads screen data from the screen data DB 44 and transmits the screen data to the administrator PC 150. The flow definition information receiving unit 42 outputs the flow definition information received from the administrator PC 150 to the flow definition information creating unit 43. The flow definition information creation unit 43 creates flow definition information with reference to the connection information DB 46, and registers the created flow definition information in the workflow list DB 38. The same workflow list DB 38 is stored in the workflow processing server 100 or the MFP 201.

  FIG. 7A shows an example of the device list table 45. As shown in FIG. In the device list table 45, a process, a physical device capable of executing the process, and a machine ID are registered in association with each other. The machine ID is identification information that uniquely identifies a physical device in the processing execution system 500. The device list table 45 is transmitted to the administrator PC 150 together with the screen data. Thereby, the administrator PC can avoid the inconsistency between the process and the physical device.

  FIG. 7B shows an example of the connection information DB 46. As shown in FIG. In the connection information DB 46, the IP address and the authentication information of the physical device of the connection destination are registered. With this IP address, for example, when one workflow is executed by a plurality of physical devices, the MFP 201 can transmit flow definition information and job data to the workflow processing server 100. Instead of the IP address, the machine ID may be registered, and the IP address may be specified from the DNS based on the machine ID. The authentication information is information used when the physical device (MFP or workflow processing server) authenticates the user. For example, in the MFP, the user name and password are authentication information, but the authentication information of the workflow processing server 100 is an administrator name and password. At the time of execution of a workflow, the workflow execution request device requests appropriate authentication information from the user.

  8 (a) and 8 (b) are diagrams showing an example of the flow definition information. FIG. 8 (a) shows flow definition information viewed from the administrator or the user, and FIG. 8 (b) shows flow definition information created by the management server 250. Workflows 2 and 3 are omitted in FIG. Immediately after being transmitted from the administrator PC 150 to the management server 250, the configuration is as shown in FIG.

  As shown in FIG. 8A, in the workflow list DB 38, flow definition information of each workflow is registered. Specifically, the physical devices associated with the order of the series of processes and each process are registered in the workflow name. The maximum number of processes included in one workflow may be five or more, or may be less than five. It is also up to the user to define a workflow that contains only one process. In FIG. 8A, the job setting of each process ((iii) above) is omitted.

  The flow definition information creation unit 43 inserts the connection process to create the flow definition information of FIG. 8B. Although details will be described later, connection processing is inserted when the physical device that executes the processing is switched. Processing 2-1 and processing 3-1 correspond to the connection processing.

  FIG. 9 is an example of a diagram showing flow definition information in XML format. <Flows> to </ flows> define one workflow. Also, <flow> to </ flow> define the order of each process of the workflow.

  One process is described in one <plugin id> tag unit and describes what process is performed. For example, "plugin id =" SCAN "" means a process of reading a document, and "type =" input "" means that the data processing type is input. “DisplayName =“ scan ”” is a process name displayed when the user looks at the administrator PC 150, the operation panel 125 or the like. “Proceed = machineID — 001” is the machine ID of the physical device associated with the process.

  Besides, "plugin id =" Compression "" is compression processing, "plugin id =" Connect "" is connection processing, "plugin id =" OCR "" is OCR, and "plugin id =" PDFConverter "" is "Plugin id =" MailSend "" means mail transmission, respectively, for PDF conversion. Also, "type =" filter "" is conversion type, "type =" output "" is output type, and "type =" send "" is transmission for connection processing which does not apply to either. , Each means.

  Also, <parameter> to </ parameter> are job settings, and job settings necessary for each process are described. There are job settings set by fixed values, in addition to those set by the administrator or the user.

The <current_point> tag indicates processing to be processed by the physical device at a current time in the workflow (when the physical device acquires the flow definition information or immediately after the update). The "current_point" may be described as the current point. The MFP 201 or the workflow processing server 100 looks at the current point to determine the processing to be executed. When processing is performed, the current point is updated to the processing to be performed next. For example, when the scan is complete, the <current_point> tag is updated as follows.
<current_point>
<plugin id = "Compression"/>
</ current_point>
FIG. 10 shows an example of a functional block diagram of a workflow execution request device (for example, an MFP) and the workflow processing server 100. The workflow execution request device 200 has a login acceptance unit 37 and a flow definition selection acceptance unit 36. The login acceptance unit 37 requests authentication information necessary for execution of the workflow. This authentication information may be, for example, login information for logging in to the MFP operated by the user. That is, the user who can log in to the MFP is authorized to execute the workflow. In this case, when the physical device switches, each physical device refers to the connection information DB 46 to acquire necessary authentication information and attach it to the flow definition information. If the authentication information is strictly required, the login acceptance unit 37 requests the user for the authentication information of all the physical devices that perform the process included in the workflow.

  The flow definition selection accepting unit 36 accepts the selection of the workflow by the user. Since the workflow list DB 38 can be obtained in advance from the management server 250 if the MFP 201 is in the company, the user causes the operation panel 125 to display a list of workflows by a predetermined operation, and selects a desired workflow. When the workflow execution request device 200 is, for example, a portable terminal, the management server 250 or the workflow processing server 100 is accessed to receive the workflow registered in the workflow list DB 38.

  In addition, the flow definition selection receiving unit 36 requests a necessary job setting in each process included in the workflow selected by the user. For example, the input requests the setting of the resolution and density that can be set in the scan, the conversion requests the compression ratio, for example, and the output (print) accepts the setting of the e-mail address. When the input is electronic data, the setting of the job data (document data, image data, video data, etc.) to be processed is accepted, and when the output is printing on a physical sheet, the sheet size, enlargement / reduction, aggregation Accept job settings such as, color / monochrome, number of copies, and finishing. The flow definition selection receiving unit 36 updates the flow definition information by job setting of each process.

  The MFP 201 includes one or more plug-ins 21, a flow control unit 22, and a job control unit 23 as functions related to execution of a workflow. The job control unit 23 controls the execution of each process of the workflow. First, the job receiving unit 33 acquires flow definition information from the flow definition selection receiving unit 36. After this, job data is obtained by executing input processing. The flow definition information is stored in job data and job queue 35.

  Further, when flow definition information and job data are transmitted from another physical apparatus (the MFP is from the workflow processing server, and the workflow processing server is from the MFP), these are stored in the job queue 35. One job corresponds to one process to which one Plugin id is assigned.

  The job receiving unit 33 checks whether it is necessary to process job data by itself based on the flow definition information of the workflow once stored in the job queue 35. That is, it is confirmed that the machine ID of the own machine is linked to the process of the current point. Also, even when the machine ID of the own machine is linked to the process of the current point, the connection process is performed when “Plugin id = Connect”, so the job execution unit 31 updates the flow definition information, The job transfer unit 32 transfers the flow definition information and the job data. The transfer destination is described in the flow definition information.

  If the machine ID of the own machine is linked to the process of the current point and the process of the current point is not the connection process, the job execution unit 31 reads the flow definition information and the job data from the job queue 35 and executes the process. Do. The job execution unit 31 outputs the flow definition information and the job data to the flow control unit 22.

  The flow control unit 22 selects the plug-in 21 in accordance with the flow definition information and executes the process. The plug-in 21 is one described above that performs input processing, one that performs PDF conversion, one that transmits electronic mail, one that performs OCR processing, one that performs translation, one that performs output processing, and the like. The plug-ins 21 can operate on a common platform, and the MFP 201 and the workflow processing server can add and delete one plug-in 21 independently. Plugins do not participate in each other's processing. The present invention is not limited to such a plug-in 21 and may be processed by an application program.

  The flow control unit 22 confirms the process of the current point, calls the plug-in 21 that performs the process, and causes the job to be executed. If the job is completed normally, the flow control unit 22 updates the process of the current point. The flow control unit 22 stores the flow definition information and the job data in the job queue 35.

  The job detection unit 34 detects that a job has been input to the job queue 35. That is, when job data created by the plug-in 21 executing one process is stored in the job queue 35, the job detection unit 34 detects it. Then, the job execution unit 31 or the like repeatedly performs the same processing.

  The workflow processing server 100 includes one or more plug-ins 21, a flow control unit 22, and a job control unit 23. That is, the job execution has the same function as that of the MFP 201. This means that the workflow execution procedure is the same between the workflow processing server 100 and the MFP 201.

  Therefore, even if processing is performed between the MFP 201 and the workflow processing server 100, the workflow can be executed because the flow definition information and the job data are transmitted and received through the connection processing. That is, the workflow can be constructed flexibly.

[Operation procedure of creating flow definition information]
FIG. 11 is an example of a flowchart showing a procedure for the administrator PC 150 and the management server 250 to create flow definition information.

  When the screen data request unit 51 of the administrator PC 150 requests the screen data of the association screen from the management server 250, the screen data transmission unit 41 of the management server 250 transmits the screen data to the administrator PC 150 (S210).

  The screen data request unit 51 receives screen data (S110).

  The display control unit 53 analyzes the screen data and displays the association screen on the display 320 (S120).

  The user operates the keyboard / mouse 306 to set one or more processes in the logical flow field (S130).

  Next, the user operates the keyboard / mouse 306 to associate each process in the logical flow field with the physical device (S140). The details will be described with reference to FIGS.

  The flow definition information transmission unit 54 transmits the flow definition information to the management server 250 (S150).

  The flow definition information receiving unit 42 of the management server 250 receives the flow definition information (S220).

  Then, the flow definition information creation unit 43 determines whether there is an association in which the physical device to be processed is switched (S230). That is, it is determined whether or not there is processing to switch from the MFP 201 to the workflow processing server 100 or from the workflow processing server 100 to the MFP 201.

  If there is no association in which the physical device to be processed is switched (No in S230), the flow definition information creation unit 43 registers the flow definition information in the workflow list DB 38 without updating it (S250).

  If there is an association in which the physical device to be processed is switched (Yes in S230), the flow definition information creation unit 43 inserts connection processing immediately before the physical device is switched (S240). Then, the updated flow definition information is registered in the workflow list DB 38 (S250). As shown in FIG. 9, “plugin id” of connection processing is determined in advance as “Connect” and “type” is “send”. Also, since the connection process is not displayed, there is no "displayName" (blank). Also, the physical device “proceed” to be processed is a physical device that performs the previous processing. In addition, the flow definition information creation unit 43 reads the IP address associated with the physical device (connection destination) that performs the next process from the connection information DB 46, and describes the IP address in the job setting (parameter) of the connection process. By using the connection information DB 46 in this manner, connection processing can be easily inserted.

  The management server 250 and the administrator PC 150 do not communicate with each other to create the flow definition information, but the administrator may operate the stand-alone type PC to create the flow definition information.

[Example of workflow definition]
FIG. 12 is an example of a diagram for explaining the definition of a workflow. FIG. 12A shows an example of the initial state of the association screen. The administrator sequentially sets the processing in the upper logical flow column, and defines the physical device to execute the processing in the lower physical device flow column. In addition, the processing list and the device list are displayed on the association screen. Both the device list and the process list icons are the extraction of “physical device” and “process” of the device list table 45. The processes 1 to 5 of the process list are actually displayed so that the process names such as OCR and PDF conversion can be grasped.

  For example, “processing 1” is displayed on the upper stage of the initial state correspondence screen while flashing. This is to clearly indicate where the administrator drags the processing icon 62 of the processing list. The administrator may arrange the processing icons in any order without performing such support, or only the squares for setting the processing icons may be displayed. Note that operations such as dragging of an icon in a server client environment are enabled in a so-called rich client environment, and are realized by combining technologies such as HTML5 Canvas tag and JavaScript, for example. As shown in FIG. 12A, when the administrator selects a process and drags it to “process 1” of the logical flow column, the first process is set.

  When the administrator sets the process 1, it is possible to select the device icon 61 from the device list. The display control unit 53 can select only the physical device capable of executing the process 1 from the device list, or when there is only one physical device capable of executing the process 1, the physical device flow can be performed without the administrator operating A device icon capable of executing the process 1 is displayed in the field (in this way, the automatic placement of the physical device icon is called automatic placement). In the case of automatic arrangement, the processing icon and the device icon are automatically connected.

  As shown in FIG. 12 (b), when the administrator selects a process and drags it to the logical flow column, the second process is set. The display control unit 53 displays “→” at the subsequent stage of process 1 and displays the process icon of process 2 at a predetermined position. The administrator repeats such an operation to define a logic flow. Then, after setting process 2, the device icon 61 of the MFP is dragged to the physical device flow field.

  The administrator can also arrange the physical device before the processing icon. Although only the physical device is arranged in the physical device flow, the administrator arranges the processing icon in the logical flow column, but the processing may not be executed by the physical device. In this case, the display control unit 53 replaces the physical device in the physical device flow column with the physical device capable of executing the process.

As shown in FIG. 12C, when the administrator sets the device icon 61 in the physical device flow column, the processing icon and the device icon are connected. As a result, the device icon of the MFP and the processing icons of processing 1 and processing 2 are connected by a line.
FIG. 12D shows a correspondence screen when the administrator adds a process. When the administrator adds the processing icon to the processing flow column, the display control unit 53 automatically follows the correspondence of the processing of the previous stage to the addition of the processing of the logical flow. That is, since the MFP is associated with process 2, the display control unit 53 associates the process 3 with the MFP. By doing this, the administrator can associate the process 3 with the physical device with a small number of operations.

  Therefore, a plurality of processes can be associated with one physical device simply by the administrator dragging the process icon to the logical flow field.

  FIG. 13 is an example of a diagram for explaining change in association. Processes 1 to 5 are associated with the MFP. When one of the processes 1 to 5 is to be associated with another physical device, as shown in FIG. 13A, the administrator drags the device icon to the physical device flow field.

  In FIG. 13B, the processing icon of the workflow processing server is added to the physical device flow. At this point in time, the display control unit 53 does nothing because the process of changing the association is unknown. Further, for example, when the process 3 is associated with the workflow processing server 100, the administrator PC 150 may change the association only for the process 3, or may the association between the processes 4 and 5 after the process 3 also be changed I can not judge.

  Therefore, the display control unit 53 displays a dialog box that receives the setting of the change method of association. This dialog box can be displayed not only at the time of addition of the device icon in FIG. 13B but also at an arbitrary timing by the administrator.

  FIG. 13C shows an example of the dialog box. In response to the statement "Association of subsequent logical flow processing", one of the three change methods of "Link to change in association" "Not linked to change in association" "Inquire to change association or inquire" It is alternatively selectable. The administrator clicks the radio button with the pointing device in consideration of the necessity of changing the physical device in the subsequent processes 4 and 5 and the like.

・ "We are linked to change of correspondence"
FIG. 14A is a diagram showing an example of the association screen when the administrator selects “Link to change in association”. The administrator associates the process 3 with the workflow processing server 100. The association is realized by dragging from process 3 of the logic flow to the workflow processing server 100 or displaying a broken line from the association menu and connecting from the process 3 to the workflow processing server 100.

  FIG. 14B is a view showing an example of the correspondence screen after the change of the correspondence. Since “link with change in association” is selected, the physical devices in processes 4 and 5 are also changed from the MFP to the workflow processing server 100 in accordance with the change in association in process 3.

・ "Not linked to change in association"
FIG. 15A is a diagram showing an example of the association screen when the administrator selects “do not interlock with change in association”. FIG. 15B is a diagram showing an example of the association screen after the association change. Since “do not interlock with change in association” is selected, even if the association in process 3 is changed, the physical devices in processes 4 and 5 remain MFP. In this case, the display control unit 53 displays the processing icon of the MFP on the subsequent stage of the processing icon of the workflow processing server, and connects the processing with the processing 4 and 5.

・ "Inquire whether to change the mapping"
FIG. 16A is a diagram showing an example of the association screen when the administrator selects “inquire or change the association”. FIG. 16 (b) shows an example of a dialog box for inquiry. The display control unit 53 selects “Inquire whether to change the association”, and when the device icon is added to the physical device flow column and the processing 3 and the device icon of the workflow processing server are associated, this dialog box is displayed. indicate.

  In the dialog box, "Please put a check in the one to be associated with the physical device" workflow processing server "and press the OK button" is displayed. In addition, “select all” button and “cancel all” button are prepared, and processing 4 and processing 5 subsequent to processing 3 are displayed together with check boxes. The administrator can select a process to be associated with the workflow processing server 100 (that is, a process to change the association) by clicking a “select all” button or a check box.

Color Classification Display after Creation FIG. 17A is a diagram illustrating a display example when the administrator associates the processes 1 to 5 with the physical device. In FIG. 17A, the areas where the process icons of processes 1 and 2 and the apparatus icon of the MFP are arranged are filled in the same color, and the process icon of process 3 and the apparatus icon of the workflow processing server 100 are arranged. The area where the process is performed is filled in with the same color, and the area in which the process icons of processes 4 and 5 and the apparatus icon of the MFP are arranged is filled with the same color. That is, the processing associated with the physical device is color-coded to the same color. Therefore, the manager can easily distinguish the correspondence between the process and the physical device visually by color coding.

  FIG. 17B is a view showing another display example of the correspondence between processes 1 to 5 and physical devices. In FIG. 17A, areas other than the icons are color-coded, but in FIG. 17B, the icons are color-coded. That is, the processing icons of processes 1 and 2 are the same color as the device icons of the MFP, and the processing icons of process 3 and the device icons of the workflow processing server 100 are the same color. The icons are in the same color. Even with such color coding, the correspondence between the processing and the physical device can be easily determined visually.

  In addition to color coding, halftone dots may be applied to areas or icons to represent differences in correspondence (the presence or absence of halftone dots is switched each time the correspondence changes), or differences in correspondence are represented by the shapes of the icons. You may

[Operation procedure of execution of workflow]
FIG. 18 is an example of a sequence diagram illustrating a procedure of executing a workflow by the process execution system 500. FIG. 19 is an example of a diagram showing an example of a screen when selecting a workflow.
S1: When the user operates the MFP 201, the MFP 201 displays a list of workflows. FIG. 19A shows an example of a workflow selection screen on which a list of workflows is displayed. The user selects a desired workflow from workflows 1 to 3 and presses the OK button. Execution of the workflow starts by pressing the OK button. The user can press the detail button if necessary to display the processes included in the workflow and the order of the processes.

  When the workflow starts, as shown in FIG. 19B, the MFP 201 requests input of a user name and a password. The username and password are authentication information for execution of the workflow. The username and password when logging in to the MFP 201 may be diverted. The user name and the password are preferably included in the flow definition information, and by being included, each physical device can be authenticated and security can be improved.

S2: The user selects and executes a workflow.
S3: The MFP 201 starts processing of the workflow. For example, processing or machine ID described in the flow definition information is extracted.
S4: The MFP 201 sends a workflow connection request to the extracted workflow processing server 100. This is a communication for confirming whether the physical device that executes the workflow can execute the workflow.
S5: The workflow processing server 100 performs a workflow acceptance process. The workflow reception process is, for example, a process of giving a unique JobID to a workflow.
S6: The workflow processing server 100 starts processing of the workflow. The process start of the workflow means executing the workflow when the flow definition information and the like are transmitted.
S7: The workflow processing server 100 transmits workflow reception information (for example, JobID etc.) to the MFP 201.
S8: When the MFP 201 confirms that execution of the workflow is possible, the execution of processes 1 to 5 starts. The job reception unit 33 analyzes the flow definition information. This analysis is to confirm that the processing of the current point is executed by the own machine.
S9: As a result of analysis, when the own machine performs the process, the flow control unit 22 executes the process assigned to the own machine using the plug-in 21. Since the process 1 is an input, job data is prepared by scanning an original or reading out or receiving electronic data designated as job data.
S10: The flow control unit 22 updates the flow definition information by changing the current point to the next process. Job data and flow definition information are stored in a job queue.

S8 to S10 are repeatedly executed for each process. When processing 1 and processing 2 are executed and the flow definition information is updated, the current point is the connection processing of processing 2.1. Since analysis of the flow definition information is connection processing (S8), the flow control unit 22 requests the job transfer unit to transfer the job without performing the process (S9). Also, the flow control unit 22 updates the flow definition information (S10).
S11: Then, as connection processing, the job transfer unit transmits flow definition information and job data to the workflow processing server 100 in association with the JobID. Note that the MFP 201 may inquire about the progress of the process from S11 to S15.
S12: The processing procedure of the workflow processing server 100 is the same. The job receiving unit stores flow definition information and job data in a job queue, and analyzes the flow definition information.
S13: As a result of analysis, when the own machine performs the process, the flow control unit 22 executes the process assigned to the own machine using the plug-in 21.
S14: The flow control unit 22 updates the flow definition information by changing the current point to the next process.

When the flow definition information is updated, the current point is the connection process of process 3.1 (S12), and the flow control unit 22 requests the job transfer unit to transfer the job without performing the process (S13). Further, the flow control unit 22 updates the flow definition information (S14).
S15: The job transfer unit transmits flow definition information and job data to the MFP 201 as connection processing.
S16: The job receiving unit stores the flow definition information and the job data in the job queue, and analyzes the flow definition information.
S17: As a result of analysis, when the own machine performs the process, the flow control unit 22 executes the process assigned to the own machine using the plug-in 21.
S18: The flow control unit 22 updates the flow definition information by changing the current point to the next process. S16 to S18 are repeatedly executed for the processes 4 and 5.

  As described above, since the processing execution system 500 of this embodiment displays the logical flow section and the physical device flow section on one screen, the administrator can easily define the flow definition information. Further, since the correspondence between the process and the physical device can be applied to the added process, the amount of operation of the administrator can be reduced. Also, by setting the method of changing the association in advance, it is possible to change the association between only some of the processes and the physical device, or change the association between all the downstream processes and the physical device. It can be selected arbitrarily.

  The first embodiment does not limit where the physical device that executes the workflow is located, but the workflow may include processing that is processed by a cloud computer on the Internet (hereinafter simply referred to as a cloud).

  FIG. 20 is an example of a schematic configuration diagram of the process execution system 500 of the present embodiment. The workflow execution request device 200 and the workflow processing server 100 are inside the company, whereas the cloud 600 is outside the company. Therefore, in order to communicate from the cloud 600 to the workflow processing server 100 or the workflow execution request device 200, the firewall 601 must be exceeded.

  However, since it is prevented from crossing the firewall 601 from the cloud 600, it is difficult to return the workflow executed by the cloud to the company once. Thus, in the present embodiment, a processing execution system 500 compatible with the cloud will be described.

  FIG. 21A is an example of a diagram for explaining the outline at the time of workflow execution of the process execution system 500 of this embodiment. For example, when the MFP 201 executes the processes 1 and 2, the cloud executes the process 3, and the MFP executes the processes 4 and 5, the workflow execution request apparatus 200 that has executed the process 2 monitors the cloud. Monitoring is to inquire the completion of processing to the cloud, and by the cloud responding to an inquiry from the company, the cloud can transmit flow definition information and job data to the company. In a firewall, in general, responses from the destination IP address of packets sent from inside the company by the administrator etc. (the source IP address of the communication from the outside is the destination IP address set in the communication from inside the company) are passing The setting of permitting is possible. Therefore, with the firewall 601 configured as such, it is possible to receive flow definition information and job data as a response to the packet transmitted by the physical device inside the company.

  FIG. 21B is an example of a diagram for explaining an outline at the time of execution of a workflow including the process performed by the workflow processing server 100. For example, it is assumed that the MFP 201 executes processing 1, the workflow processing server 100 executes processing 2, the cloud executes processing 3, the workflow processing server 100 executes processing 4, and the MFP 201 executes processing 5. In this case, the workflow processing server 100 that has executed the process 2 monitors the cloud.

  Note that the physical device that has performed processing immediately before the cloud may monitor the cloud, or the physical device that performs processing after the cloud may monitor the cloud. Alternatively, the workflow execution request device 200 may constantly monitor the cloud. In this embodiment, it is assumed that the physical device that has performed the processing immediately before the cloud monitors the cloud.

[Flow definition information including monitoring processing]
The flow definition information includes a monitoring process because a physical device in the company monitors the cloud. As already described in the first embodiment, the administrator creates the flow definition information as shown in FIG. Then, the flow definition information creation unit 43 of the management server 250 creates flow definition information including connection processing, but in the present embodiment, the flow definition information creation unit 43 creates flow definition information including monitoring processing.

  FIG. 22 is an example of a diagram for explaining flow definition information for monitoring. The flow definition information creation unit 43 detects the external physical device (cloud) set as the physical device after the connection processing with reference to the flow definition information into which the connection processing of FIG. 22A is inserted. . In FIG. 22A, process 3 is executed by the cloud. The fact that the physical device to be processed is a cloud is registered in the device list table 45, for example.

  As shown in FIG. 22B, the flow definition information creation unit 43 creates process flow definition information for monitoring in which the physical device is set to the MFP 201 that performs the process 2.1 with the process 3 as the monitoring. The flow definition information for monitoring only needs to be monitored, and processing 1 to processing 2.1 is set to blank (not processed). Since the target of monitoring is a cloud that executes processing 3, an IP address and the like are registered in the device list table 45.

  In the case of a workflow that needs to receive flow definition information and job data multiple times from the cloud, create as many flow definition information for monitoring as that number.

  At the time of execution of the workflow, the physical device updates the flow definition information and updates the current point of the flow definition information for monitoring according to the progress of processing. Then, when the current point of the flow definition information and the flow definition information for monitoring becomes the process 3, only the flow definition information is transmitted to the cloud. The flow definition information for monitoring is held by the MFP as it is because the physical device in process 3 is the MFP (own machine). Thus, the MFP can monitor the cloud. After the monitoring, the flow definition information for monitoring is discarded because there is no subsequent processing in the flow definition information for monitoring.

  Also, the flow definition information for monitoring may be created by the physical device when the workflow is executed. The physical device creates flow definition information for monitoring when the current point is connection processing and the physical device that executes processing after connection processing is a cloud. Since it is the own machine to monitor, it is sufficient to carry out the monitoring process as it is.

  FIG. 23 is an example of a flowchart showing a procedure for the administrator PC 150 and the management server 250 to create flow definition information. FIG. 23 is the same as FIG. 11, but after the flow definition information creation unit 43 inserts the connection process immediately before the physical device is switched in step S240, it is determined whether the physical device that performs the process after the connection process is a cloud or not Is determined (S245).

When the physical device that performs processing after the connection processing is a cloud (Yes in S245), the flow information creation unit creates flow definition information for monitoring (S246). The subsequent processes may be the same as in the first embodiment.
FIG. 24 is an example of a sequence diagram showing the procedure of the process execution system 500 executing a workflow. FIG. 24 is also similar to FIG. 18, but the execution procedure of the process 3 is different.

The current point of the flow definition information and the flow definition information for monitoring becomes processing 3 by steps S8 to S10.
S11: As connection processing, the job transfer unit transmits flow definition information and job data to the workflow processing server 100 in association with JobID. The processing procedure of the workflow processing server 100 is the same as that of the first embodiment.
S31: Since at least flow definition information for monitoring is stored in the job queue, the job reception unit analyzes the flow definition information.
S32: As a result of analysis, it is analyzed that the own machine performs monitoring processing, so the job control unit (which may be the flow control unit 22) performs cloud monitoring processing. The job control unit updates the flow definition information by changing the current point to the next process, but discards the flow definition information because there is no next process.
S15: The job transfer unit of the cloud transmits flow definition information and job data to the MFP 201 as a response to the inquiry as connection processing. The subsequent steps are the same as in the first embodiment.

  As described above, in addition to the effects of the first embodiment, the process execution system 500 of the present embodiment enables flexible and easy definition of a workflow beyond the firewall.

21 plug-in 22 flow control unit 23 job control unit 31 job execution unit 33 job reception unit 34 job transfer unit 35 job queue 100 workflow processing server 150 administrator PC
200 Workflow Execution Request Device 500 Processing Execution System

JP 2011-035779 A

Claims (5)

What is claimed is: 1. A processing execution system having a plurality of processing devices that execute a workflow comprising a plurality of processing, comprising:
A selection operation for selecting a process to be executed by one processing apparatus from the plurality of processes, and an associating operation for associating the process selected by the selection operation with the processing apparatus for executing the process for each process Display control means for displaying on the display device a setting screen to be received;
Definition information generation means for defining, in definition information, a workflow to be executed by a plurality of processing devices in which a processing device that executes each process is specified by the selection operation and the association operation received via the setting screen And
When the connection processing for transmitting the definition information from the first processing device inside the firewall to the second processing device on the Internet is defined in the definition information, the definition information generation means A processing execution system characterized by generating the definition information having a monitoring process in which the first processing device monitors the second processing device which executes the subsequent processing.   The plurality of processing devices may include one or more processing devices in a first network configured on one side via a firewall, and a second network configured on the other side via the firewall. The processing execution system according to claim 1, comprising one or more processing devices.   The processing execution system according to claim 2, wherein the first network is a local network, and the second network is the Internet. The storage means which memorize | stores the correspondence information which matched the process used as the option which comprises the said workflow, and the processing apparatus which can execute this process is provided in any one of the Claims 1-3 characterized by the above-mentioned. Processing execution system.   The one or more processing devices may include a processing device that receives a selection of a workflow to be executed based on the definition information generated by the definition information generation unit and an execution instruction for executing the selected workflow. The processing execution system according to any one of claims 1 to 4, characterized by the above.

Images