JP7026275B1 - Logistics business system construction method and logistics business system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve the efficiency of construction work. A method for constructing a physical distribution business system according to an embodiment of an embodiment includes a modeling process and a generation process. The modeling process abstracts the work and data in the above-mentioned logistics business so that a workflow related to the logistics business can be generated by using a general-purpose workflow engine. The generation process generates the workflow by using the workflow engine based on the work and data abstractly modeled in the modeling process. [Selection diagram] FIG. 8

Description

The embodiment of the disclosure relates to a method of constructing a physical distribution business system and a physical distribution business system.

Conventionally, there is known a workflow system that generates a workflow optimized for work in various fields and executes the work according to the workflow (see, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2014-305646

However, the above-mentioned conventional technique has room for further improvement in order to improve the efficiency of the construction work.

For example, the technology disclosed in Patent Document 1 relates to a workflow system for medical services in the medical field, but when such a workflow system is provided by SI (System Integration), the SI supplier sets the workflow according to the customer's requirements when constructing the system. It was very time-consuming to optimize.

Taking a workflow system related to logistics business (hereinafter, referred to as "logistics business system" as appropriate) as an example, for example, even if it is simply called a logistics business system, the business content, the shape of the load to be handled, the number of warehousing / delivery instructions, and the worker's The number of people, the type and number of equipment used, etc. often differ depending on the logistics company that is the customer.

For this reason, when an SI vendor provides SI, it is often the case that, for example, an existing or standard system is customized according to the customer's requirements. However, in such cases, the business application rate of the system tends to be low because there are many changes that depend on the customer's requirements and it is difficult to standardize work and data. In addition, in customization, since systematization is performed based on the business flow of business, there is also a problem that specification discrepancies occur and it is easy to cause defects. Furthermore, when changing operations or equipment, the range of corrections tends to be large, which requires a large amount of man-hours and makes it difficult to ensure quality.

One aspect of the embodiment is made in view of the above, and an object thereof is to provide a method of constructing a physical distribution business system and a physical distribution business system capable of improving the efficiency of construction work.

The method for constructing a physical distribution business system according to one embodiment is a method for constructing a physical distribution business system executed by a computer, and includes an acquisition process, a modeling process, and a generation process. The acquisition process defines the elements in the physical distribution business, the dependencies between the elements, and the data exchanged between the elements, which the user performing the physical distribution business defines at the second level for abstraction. Obtain information from an external device or storage medium. The modeling process is more embodied than the first level of definition information defined in a general-purpose workflow engine, and is described by the third level of definition information that is more abstract than the second level. The definition information of the second level acquired in the acquisition process is abstractly modeled at the third level so that the workflow related to the distribution business can be generated. The generation process generates the workflow engine customized via the business process modeling language based on the definition information of the third level abstractly modeled in the modeling process. In addition, the modeling step includes data as the element in the definition information of the second level, and works on data indicating an interested party including at least a higher system, a subsystem, a person and a device of the logistics business system. An abstract model is created as data indicating the subject, and data indicating each work performed by the work entity in the logistics business is abstractly modeled as data indicating at least identification, counting, or movement, and a series of work instructions are given to the work entity. Data indicating a certain work instruction is defined as data consisting of at least the combination of identification, counting or movement.

According to one aspect of the embodiment, the efficiency of the construction work can be improved.

FIG. 1 is a schematic explanatory diagram (No. 1) of a method for constructing a physical distribution business system according to an embodiment. FIG. 2 is a schematic explanatory diagram (No. 2) of a method for constructing a physical distribution business system according to an embodiment. FIG. 3 is a schematic explanatory diagram (No. 3) of a method for constructing a physical distribution business system according to an embodiment. FIG. 4 is a schematic explanatory diagram (No. 4) of a method for constructing a physical distribution business system according to an embodiment. FIG. 5 is a diagram showing a configuration example of a physical distribution business system according to an embodiment. FIG. 6 is a diagram showing the roles and main functions of each subsystem. FIG. 7 is an explanatory diagram of a management range in a physical distribution business system. FIG. 8 is a block diagram of the generator according to the embodiment. FIG. 9 is a block diagram of the execution system according to the embodiment. FIG. 10 is an explanatory diagram of elements related to the physical distribution business according to the embodiment. FIG. 11 is a diagram (No. 1) showing a specific example of the management location. FIG. 12 is a diagram (No. 2) showing a specific example of the management location. FIG. 13 is a diagram (No. 3) showing a specific example of the management location. FIG. 14 is a diagram (No. 4) showing a specific example of the management location. FIG. 15 is an explanatory diagram (No. 1) regarding the object. FIG. 16 is an explanatory diagram (No. 2) regarding the object. FIG. 17 is an explanatory diagram (No. 1) regarding the management location. FIG. 18 is an explanatory diagram (No. 2) regarding the management location. FIG. 19 is an explanatory diagram (No. 3) regarding the management location. FIG. 20 is an explanatory diagram (No. 4) regarding the management location. FIG. 21 is an explanatory diagram regarding the work performed by the work subject. FIG. 22 is an explanatory diagram (No. 1) regarding the identification. FIG. 23 is an explanatory diagram (No. 2) regarding the identification. FIG. 24 is an explanatory diagram regarding the count. FIG. 25 is an explanatory diagram (No. 1) regarding movement. FIG. 26 is an explanatory diagram (No. 2) regarding movement. FIG. 27 is an explanatory diagram (No. 3) regarding movement. FIG. 28 is an explanatory diagram (No. 4) regarding movement. FIG. 29 is an explanatory diagram regarding work instructions. FIG. 30 is an explanatory diagram regarding auxiliary work. FIG. 31 is a diagram (No. 1) showing a specific example of the workflow related to the receipt / receipt business. FIG. 32 is a diagram showing an operation example of the UI screen at the time of executing the workflow shown in FIG. 31. FIG. 33 is a diagram (No. 2) showing a specific example of the workflow related to the receipt / receipt business. FIG. 34 is a diagram showing an operation example of the UI screen at the time of executing the workflow shown in FIG. 33. FIG. 35 is a diagram (No. 1) showing a specific example of a workflow including auxiliary work. FIG. 36 is a diagram (No. 2) showing a specific example of the workflow including the auxiliary work. FIG. 37 is a hardware configuration diagram showing an example of a computer that realizes the function of the generator.

Hereinafter, the method of constructing the physical distribution business system disclosed in the present application and the embodiment of the physical distribution business system will be described in detail with reference to the attached drawings. The present invention is not limited to the embodiments shown below.

<Outline of this embodiment>
First, an outline of a method for constructing a physical distribution business system according to an embodiment will be described with reference to FIGS. 1 to 4. 1 to 4 are schematic explanatory diagrams (No. 1) to (No. 4) of a method for constructing a physical distribution business system according to an embodiment.

As already mentioned, there is room for further improvement in the existing technology in order to improve the efficiency of the construction work when the SI company provides the logistics business system to the customer.

Specifically, when providing SI for a logistics business system, it has been very troublesome for an SI company to optimize the workflow according to the customer's requirements when constructing the system.

For example, even if it is a logistics business system, the business content, the shape of the cargo to be handled, the number of warehousing / delivery instructions, the number of workers, and the type and number of equipment used may differ depending on the logistics company that is the customer. many.

For this reason, when an SI vendor provides SI, it is often the case that, for example, an existing or standard system is customized according to the customer's requirements. However, in such cases, the business application rate of the system tends to be low because there are many changes that depend on the customer's requirements and it is difficult to standardize work and data. In addition, in customization, since systematization is performed based on the business flow of business, there is also a problem that specification discrepancies occur and it is easy to cause defects. Furthermore, when changing operations or equipment, the range of corrections tends to be large, which requires a large amount of man-hours and makes it difficult to ensure quality.

Therefore, in the method of constructing the logistics business system according to the embodiment, the work and data in the above-mentioned logistics business are abstractly modeled and abstracted so that the workflow related to the logistics business can be generated by using a general-purpose workflow engine. Based on the above work and data, it was decided to generate the above workflow using the above workflow engine. In addition, "generating the above workflow using the above workflow engine" refers to customizing a general-purpose workflow engine and creating a workflow system that can be utilized in a logistics business system.

In addition, in the abstract modeling, it was decided to abstract the work and data at a level more detailed than the abstraction level defined in the workflow engine.

Further, in the above abstract modeling, it is between the first level which is the abstraction level defined in the workflow engine and the second level which is the abstraction level defined by the user who executes the logistics business. We decided to abstract model the above work and data at the third level.

Further, in the abstract modeling, at least the logistics business executes the elements in the logistics business defined in the second level, the dependencies between the elements, and the data exchanged between the elements. We decided to make an abstract model at the third level above so that it would be possible.

A more specific explanation will be given. First, in the method of constructing the logistics business system according to the embodiment, it was decided to use a general-purpose workflow engine (hereinafter, appropriately referred to as "general-purpose workflow engine") which is a known technology.

The general-purpose workflow engine abstracts the business, defines and models the work and data flow, and realizes the operation screen and data flow suitable for the target workflow without programming, and PDCA (Plan) of the workflow. -Do-Check-Act) Package software that manages cycles. In this embodiment, Activeiti, which is open source, is used. However, it does not limit the general-purpose workflow engine to be used.

By using a general-purpose workflow engine, it is possible to significantly reduce the man-hours required for system construction. However, the general-purpose workflow engine is a general-purpose abstraction of business, and cannot be used as it is in constructing a logistics business system according to each customer who receives SI provision. As shown in FIG. 1, the level of abstraction defined in such a general-purpose workflow engine is hereinafter referred to as a "first level".

On the other hand, it can be said that the requirements of each customer receiving SI provision, that is, each logistics company, are generally expressed at the level of abstraction defined by the user who executes the logistics business. In other words, it is the recognition level of the requirements that each customer is aware of in carrying out the logistics business. As shown in FIG. 1, the level of abstraction defined by the user who executes such a physical distribution business is hereinafter referred to as a “second level”.

Therefore, if a general-purpose workflow engine is used as a standard system, the level of abstraction will be changed from the first level to the second level when using existing technology in order to optimize the workflow according to the customer's requirements. Need to customize to drop to. However, this cannot solve the problems when the above-mentioned existing technology is used.

Therefore, as shown in FIG. 1, in the method of constructing the logistics business system according to the embodiment, it is more specific between the first level and the second level, that is, more specific than the first level, and the second level. At the "third level", which is a more abstract abstraction level, work and data related to logistics operations are abstractly modeled. Then, the workflow creator customizes the general-purpose workflow engine while being aware of its compatibility with the general-purpose workflow engine so that the workflow as a logistics business system can be drawn while making the work and data in the abstract model as workflow options.

Specifically, as shown in FIG. 2, in the method of constructing the physical distribution business system according to the embodiment, the elements in the physical distribution business defined at the second level, the dependency relationships between the elements, and the elements of the physical distribution business. The data exchanged between them is abstractly modeled at the third level so that at least the logistics business can be executed.

The "element" here is, for example, a stakeholder. Stakeholders are, for example, core systems (superior systems), own systems, people (managers, workers, etc.), equipment, and the like. Further, the "dependency between elements" is, for example, a flow connecting stakeholders. Further, the "data exchanged between elements" is, for example, data exchanged in a flow connecting stakeholders.

Then, in the method of constructing the physical distribution business system according to the embodiment, for example, these elements, the dependency between the elements, and the data exchanged between the elements are collected at least in the physical distribution business, particularly the “warehouse business” in the physical distribution business. Is abstracted at the third level so that it can be executed.

For example, in the method of constructing the logistics business system according to the embodiment, an abstract model is implemented especially for the universal part related to the inventory management and transportation control of the warehouse business so as not to be affected by the customer-specific business and business changes. is doing.

To give an example of the above-mentioned elements, as shown in FIG. 3, in the method of constructing the logistics business system according to the embodiment, people and equipment at the second level are regarded as "working subjects" at the third level. To abstract. In addition, "commodities" and "items" at the second level are abstracted as "objects" at the third level. In addition, "storage shelves" and "furniture" at the second level are abstracted as "management places" at the third level.

Seen from the first level, the "working subject", "object", "managed place", etc. in these third levels are general-purpose elements defined in the first level ("in the figure" in the figure. It is necessary to embody from "general-purpose element 1", "general-purpose element 2", etc.).

However, when the existing technology is used, the degree of detailing is lower than that of embodying from the first level to the second level, so that the man-hours required for customization are reduced. Therefore, according to the method of constructing the physical distribution business system according to the embodiment, it is possible to improve the efficiency of the physical distribution business system construction work.

Regarding the degree of detailing described above, in the method of constructing the logistics business system according to the embodiment, at least the workflow related to the warehouse business can be generated by the low code development by the business process modeling language using the general-purpose workflow engine. Make an abstract model at the third level.

As a result, the man-hours required for customization can also be reduced, and the efficiency of the construction work of the distribution business system can be improved.

Further, in the method of constructing the physical distribution business system according to the embodiment, each work performed by the above-mentioned work subject in the warehouse business is abstracted by classifying and organizing it into "specific", "count", and "movement".

In addition, the "work instruction", which is a series of work instructions to the work subject described above, is organized, classified, and defined as a combination of the series of work of "identification", "counting", and "movement". Then, as shown in FIG. 4, in the method of constructing the logistics business system according to the embodiment, for example, a workflow composed of up to one "work instruction", "specification", "count", and "movement" is provided. Generate. Note that FIG. 4 shows only an example of the basic form of the workflow according to the embodiment, which is not an essential requirement, but when "specific", "count", and "move" are included, the order cannot be changed.

In addition, among the works performed in the warehouse work, those not included in "specific", "count" and "move" are abstracted as "auxiliary work". As shown in FIG. 4, the "auxiliary work" is abstracted and defined so that it can be arbitrarily arranged in the workflow.

It should be noted that a specific example of the abstract modeling at the third level described with reference to FIGS. 3 and 4, in other words, a definition example of various information at the abstraction level according to the present embodiment, and a specific example of the generated workflow. Examples will be described later with reference to FIGS. 10 to 36.

In this way, in the method of constructing the logistics business system according to the embodiment, the work and data in the logistics business, especially the warehouse business, are abstractly modeled so that the workflow related to the logistics business can be generated by using the general-purpose workflow engine. Based on the abstract modeled work and data, we decided to generate a workflow using a general-purpose workflow engine.

Therefore, according to the method of constructing the physical distribution business system according to the embodiment, the efficiency of the construction work can be improved.

Hereinafter, the configuration of the physical distribution business system 1 to which the method for constructing the physical distribution business system according to the above-described embodiment will be applied will be described more specifically.

<Structure of logistics business system>
FIG. 5 is a diagram showing a configuration example of the logistics business system 1 according to the embodiment. Further, FIG. 6 is a diagram showing the roles and main functions of each subsystem.

As shown in FIG. 5, the logistics business system 1 according to the embodiment includes a management system 30, an execution system 50, a control system 70, and each subsystem of an operation system 90. Each subsystem is provided so as to be able to communicate with each other via a network (not shown). It should be noted that each subsystem may be realized as each process executed by, for example, one computer. In such a case, the subsystems are provided so as to be able to communicate with each other by, for example, interprocess communication.

Further, the physical distribution business system 1 is communicably connected to a core system (not shown), in other words, a higher-level system.

The management system 30 executes each process such as core system linkage, integrated management of each base managed by the execution system 50, business-specific processing associated with warehouse operations, and linkage with the execution system 50.

The execution system 50 is provided for each warehouse base (hereinafter, simply referred to as “base”). The execution system 50 executes each process such as cooperation with other systems, optimization of warehouse work, visualization, and the like. The warehouse work optimization process is executed as a workflow control process based on the workflow group generated by the generation device 10 described later. The visualization process is executed as a UI (User Interface) providing process for the operation system 90 based on the data generated by the workflow group also generated by the generation device 10.

The control system 70 is provided at each base and executes each process of AS / RS (Automated Storage and Retrieval System) control, robot control, and AGV (Automated Guided Vehicle) control based on the operation instruction from the execution system 50.

The operation system 90 provides, for example, a worker with a work operation function based on the UI provided by the execution system 50.

See FIG. 6 for the roles and main functions of each subsystem of the management system 30, the execution system 50, the control system 70, and the operation system 90.

Next, FIG. 7 is an explanatory diagram of a management range in the physical distribution business system 1. The logistics business system 1 performs warehousing / delivery management, inventory management, and the like at each base in accordance with the receipt / shipment instructions from the host system.

As shown in FIG. 7, each base is within the control range of each execution system 50. Further, all the bases, the warehousing source and the warehousing source of the management system 30, are within the management range of the management system 30.

In addition, each base performs each function such as unloading, arrival inspection, warehousing / delivery, sorting / assortment, shipping inspection / shipping packing, and loading. For unloading, for example, a robot or the like is used as a device. For the arrival inspection, for example, an RFID (Radio Frequency Identifier) gate, an HT (Handy Terminal), or the like is used as a device.

For warehousing / delivery, for example, AGV, conveyor, robot, HT, AS / RS and the like are used as equipment. Further, instead of AS / RS, the load may be manually placed on the rack or placed flat.

For sorting and assortment, for example, sorters, HTs, AGVs, conveyors and the like are used as equipment. For shipping inspection and shipping packing, for example, RFID gates, HTs, automatic packing machines and the like are used as equipment. For example, a robot or the like is used as a loading and device.

Returning to the description of FIG. Further, each workflow executed in the physical distribution business system 1 is generated by the generation device 10. The generation device 10 abstractly models the work and data in the physical distribution business so that the workflow related to the physical distribution business can be generated by using the general-purpose workflow engine, and based on the abstract modeled work and data, the general-purpose workflow engine is used. It is a device that uses it to generate a workflow.

The generator 10 is, for example, a computer used by a workflow creator in an SI company. The generation device 10 may be composed of a plurality of computers.

The generation device 10 causes the execution system 50 to acquire the workflow DB (Database) 12d in which each generated workflow is stored as the workflow DB 53a. The execution system 50 executes the physical distribution business according to each workflow stored in the workflow DB 53a. The execution system 50 corresponds to an example of the "execution unit" according to the embodiment.

<Configuration of generator>
Next, FIG. 8 is a block diagram of the generation device 10 according to the embodiment. In addition, in FIG. 8 and FIG. 9 shown later, the constituent elements necessary for explaining the features of the present embodiment are represented by functional blocks, and the description of general constituent elements is omitted.

In other words, each component shown in FIGS. 8 and 9 is a functional concept and does not necessarily have to be physically configured as shown. For example, the specific form of distribution / integration of each functional block is not limited to the one shown in the figure, and all or part of it is functionally or physically distributed in arbitrary units according to various loads and usage conditions. -It is possible to integrate and configure.

In the description using FIGS. 8 and 9, the description of the components already described above may be simplified or omitted.

As shown in FIG. 8, the generation device 10 according to the embodiment includes an acquisition I / F (Interface) 11, a storage unit 12, and a control unit 13. Further, the UI unit 3 is connected to the generation device 10. The UI unit 3 is an input / output component and is realized by a keyboard, a mouse, a display, a touch panel, and the like.

The acquisition I / F 11 is realized by, for example, a NIC (Network Interface Card) or the like. In such a case, the acquired I / F 11 is connected to, for example, a network (not shown) by wire or wirelessly, and receives warehouse business information from an external device via the network. The warehousing business information corresponds to the above-mentioned information on the second level warehousing business.

Further, the acquired I / F 11 is realized by, for example, USB (Universal Serial Bus) or the like. In such a case, the acquisition I / F 11 is connected to, for example, a storage medium having a USB interface, and the warehouse business information is acquired from the storage medium.

The storage unit 12 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory), a ROM (Read Only Memory), or a flash memory (Flash Memory), or a storage device such as a hard disk or an optical disk. In the example shown in FIG. 8, the storage unit 12 stores the warehouse business information DB 12a, the abstract model DB 12b, the general-purpose workflow engine 12c, and the workflow DB 12d.

The warehouse business information DB 12a is a database in which the warehouse business information acquired by the acquisition unit 13a, which will be described later, is stored via the acquisition I / F 11. The abstract model DB 12b is a database in which definition information regarding work and data in the warehouse business abstractly modeled by the modeling unit 13b described later is stored. The definition information stored in the abstract model DB 12b corresponds to the definition information at the third level described above.

The general-purpose workflow engine 12c corresponds to the general-purpose workflow engine described above. The workflow DB 12d is a database in which each workflow related to the warehouse business generated by the generation unit 13c described later is stored.

The control unit 13 is a controller, and for example, various programs stored in the storage unit 12 by a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or the like execute RAM as a work area. It is realized by being done. Further, the control unit 13 can be realized by, for example, an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

The control unit 13 has an acquisition unit 13a, a modeling unit 13b, and a generation unit 13c, and realizes or executes the functions and operations of information processing described below.

The acquisition unit 13a acquires the second level warehouse business information via the acquisition I / F11. Further, the acquisition unit 13a stores the acquired warehouse business information in the warehouse business information DB 12a.

The modeling unit 13b abstracts the work and data in the warehouse business information stored in the warehouse business information DB 12a at the third level based on the operation of the workflow creator via the UI unit 3 and transfers it to the abstract model DB 12b. Store.

The generation unit 13c generates a workflow using the general-purpose workflow engine 12c based on the work and data related to the warehouse operation at the third level stored in the abstract model DB 12b.

Specifically, the generation unit 13c uses the general-purpose workflow engine 12c to develop low-code for the work and data related to the warehouse work stored in the abstract model DB 12b based on the operation of the workflow creator via the UI unit 3. Constructed or recombined as a workflow by.

Further, the generation unit 13c stores each generated workflow in the workflow DB 12d. As described above, the workflow DB 12d will be provided to the execution system 50 as the workflow DB 53a.

Further, each workflow generated by the generation unit 13c also includes a UI such as a screen used in each workflow, and the execution system 50 receives a work operation from the operation system 90 via the UI, and the work operation is performed. The workflow will be executed according to the above.

<Execution system configuration>
Next, FIG. 9 is a block diagram of the execution system 50 according to the embodiment. As shown in FIG. 9, the execution system 50 according to the embodiment includes an acquisition I / F 51, a communication unit 52, a storage unit 53, and a control unit 54.

Similar to the above-mentioned acquisition I / F11, the acquisition I / F 51 is realized by, for example, NIC or USB, and is an interface for acquiring the workflow DB 12d from the generation device 10 as the workflow DB 53a.

The communication unit 52 is realized by, for example, a NIC or the like. The communication unit 52 is connected to, for example, a network (not shown) by wire or wirelessly, and transmits / receives various information to / from the management system 30, the control system 70, and the operation system 90 via the network.

Similar to the storage unit 12 described above, the storage unit 53 is realized by, for example, a semiconductor memory element such as a RAM, ROM, or a flash memory, or a storage device such as a hard disk or an optical disk. In the example shown in FIG. 9, the storage unit 53 stores the workflow DB 53a.

The control unit 54 is a controller like the control unit 13 described above. For example, various programs stored in the storage unit 53, which are stored in the storage unit 53, are executed by the CPU, MPU, or the like using the RAM as a work area. It will be realized. Further, the control unit 54 can be realized by an integrated circuit such as an ASIC or FPGA.

The control unit 54 has an acquisition unit 54a, a cooperation unit 54b, a workflow control unit 54c, and a UI providing unit 54d, and realizes or executes the functions and operations of information processing described below.

The acquisition unit 54a acquires the workflow DB 12d from the generation device 10 via the acquisition I / F 51 and stores it in the storage unit 53 as the workflow DB 53a.

The cooperation unit 54b executes the above-mentioned cooperation process with another system. The workflow control unit 54c executes the workflow control process based on the workflow DB 53a. The workflow control process corresponds to the optimization process of warehouse work as described above. Further, the workflow control process includes various operation instructions to the control system 70 and the like.

The UI providing unit 54d executes the UI providing process for the operation system 90 based on the workflow DB 53a. The UI providing process corresponds to the visualization process as described above. The workflow control unit 54c receives a work operation from the operation system 90 via the UI provided by the UI providing unit 54d, and performs the workflow control process so that the workflow corresponding to the work operation is appropriately executed.

Next, definition examples of various information at the abstraction level according to the present embodiment will be sequentially described with reference to FIGS. 10 to 30.

<About work subject, object, management place>
First, FIG. 10 is an explanatory diagram of elements related to the logistics business system 1 according to the embodiment. 11 to 14 are diagrams (No. 1) to (No. 4) showing specific examples of the management location.

As already described with reference to FIG. 3, as shown in FIG. 10, in the method of constructing the physical distribution business system 1 according to the embodiment, the elements related to the physical distribution business system 1 are "working entity", "object", and "management". Organize and classify as "place".

As shown in FIG. 10, the "working subject" is a person, a device, or the like, and is a subject performing work such as carrying or counting an object. Further, the "object" is a product or the like, which is an object to be carried, counted, or the like. Further, the "management place" is a storage shelf, furniture, etc., and is a place and a unit for managing the object.

As shown in FIG. 11, such a "management place" is, for example, a label No. Or, slip No. And furniture No. It is a management unit enclosed by etc. This is based on the idea that labels, slips, etc. merely identify a place in space.

Further, as shown in FIG. 12, the “management place” is, for example, a management unit grouped by a work area. Further, as shown in FIG. 13, the “management place” is a management unit grouped by, for example, a worker who has performed counting. In other words, if the counted workers are different, the "management place" will be different.

Alternatively, as shown in FIG. 14, the "management place" is a management unit grouped by a single transport portion of the transport device E such as an AGV.

Next, the "object" will be described more specifically. 15 and 16 are explanatory views (No. 1) and (No. 2) regarding the object.

In the method for constructing the physical distribution business system 1 according to the embodiment, a SKU (Stock Keeping Unit), which is also generally used, is used as a unit for stock keeping by distinguishing objects. As shown in FIG. 15, the object is managed differently even if it is the same item if the "management entity" that manages the object is different. The "management entity" is, for example, a shipper, a depositor, a business division, or the like.

Further, regarding the object, the "item" primarily identifies the object. It may be a different item due to differences in color, shape, packing style, quantity, etc. In this embodiment, in principle, it is the same as the management of the host system.

Further, regarding the object, the "attached information" is information attached to the item, for example, a lot, a warehousing date, an expiration date, a non-defective item classification, and the like. "Attached information" is not limited to items that are described in items such as lots and expiration dates, but also items that are not described but are managed as attribute information, such as warehousing dates and non-defective item categories. Even if there is a lot description, it is not included if it is not managed as an inventory management unit.

On the premise of these, as shown in FIG. 16, the object has a SKU No. in the unit of SKU. Is given. In this way, SKU is used as a unit for stock management by distinguishing objects.

Next, the "managed place" will be described more specifically. 17 to 20 are explanatory views (No. 1) to (No. 4) regarding the management location.

FIG. 17 shows the data management range of the “management place”. As shown in FIG. 17, one "warehouse" corresponds to one execution system 50. In other words, the range managed by one execution system 50 is one "warehouse". It should be noted that one "warehouse" referred to here is not necessarily a group of buildings.

On the other hand, an "area" is a place in a warehouse. An "area" is identified by an attribute within the warehouse. The attributes in the warehouse are physical divisions such as floors and rooms, classification by storage equipment such as AS / RS and fixed racks, definition of virtual places such as arrival place and moving middle place, and the like.

Therefore, as shown in FIG. 17, each execution system 50 manages the area master as standard and manages the data using the area as a key. For warehouses, keep it as a fixed value.

Further, the management system 30 or the general execution system (not shown) manages data using the warehouse + area as a key. The warehouse master is not managed by default, but is managed as needed.

Further, in the method of constructing the physical distribution business system 1 according to the embodiment, the object is managed and identified by the management place system shown in FIG. Specifically, as shown in FIG. 18, the above-mentioned "area" is, for example, a room number, an AS / RS unit, or the like. The arrival place, etc. is defined so that, for example, the system unique number of the arrival place, etc. can be read as the area notation on the customer side.

Further, the "location" is a place where inventory registration is performed, and is, for example, a shelf number, a division number, or the like. The location system can be defined according to the customer's requirements. A standard definition example is as shown in FIG. 19, for example.

Further, "Furniture No." is, for example, a pallet No. Oricon (folding container) No. Or, bin No. Or, Tote No. Or box No. And so on. The hierarchical management method when using multiple fixtures, such as when placing the Oricon on the pallet, will be described later.

In addition, the "frontage inside the fixture" is the frontage No. when the inside of the fixture is partitioned. Is. Further, the "identification information" is information that can identify the management unit of the object, and includes not only physical identification but also virtual identification that can be identified by visual sense or work record. The "identification information" is, for example, the above-mentioned label No. And slip No. In addition, the work No. of each work instruction. Or user ID + inventory registration date and time.

Although it is a hierarchical management method when a plurality of fixtures are used, in the method of constructing the logistics business system 1 according to the embodiment, when a plurality of fixtures are used, the fixture having a smaller management range is linked to the object. Attach and manage. However, if all layers are allowed to be managed, it will be complicated and cause operational mistakes such as registration mistakes and incorrect delivery. Therefore, it is premised that restrictions are set on the permitted layers.

For example, the first layer is a shelf, the second layer is a pallet, and the third layer is an Oricon, and management is performed up to a maximum of three layers. Further, in order to maintain the uniqueness of the furniture, preconditions such as setting the first digit as a type may be provided.

As shown in the upper part of FIG. 20, on the premise of the explanation using FIGS. 17 to 19, the objects A to L and the fixtures 101 to 104 managed by the location system “AA-10-02-3-4”, It is assumed that there are 201 and 202 arrangements.

In such a case, the management location of each of the objects A to L is managed as shown in the left table in the lower part of FIG. Further, for each of the fixtures 101 to 104, 201, and 202, the management location is managed as shown in the right table at the bottom of FIG. 20.

<About the work performed by the work subject>
Next, the work performed by the above-mentioned work subject will be described more specifically. FIG. 21 is an explanatory diagram regarding the work performed by the work subject. 22 and 23 are explanatory views (No. 1) and (No. 2) relating to the identification.

Further, FIG. 24 is an explanatory diagram regarding the count. In addition, FIGS. 25 to 28 are explanatory views (No. 1) to (No. 4) relating to movement.

As described above, in the method of constructing the logistics business system 1 according to the embodiment, as shown in FIG. 21, the work performed by the work subject is "specification", "counting", "movement", and other "auxiliary work". Is classified and organized.

In addition, there are two types of "specification", "verification" and "registration". In addition, "move" includes "receipt registration", "delivery registration", and "deletion". Further, the "auxiliary work" includes "authentication", "input", "number acquisition", "reference", "confirmation", "output", "operation instruction", "event", and "fixed cycle".

As shown in FIG. 22, first, "collation" in "specification" is to specify an object to be moved or counted and collate it with collation source information such as work instructions or master information. Further, "registration" in "specification" is to confirm attribute information (lot, warehousing date, non-defective product / defective product, etc.) outside the collation item, and to specify and register the SKU.

As shown in FIG. 23, "collation" is, for example, a product barcode or a label No. And furniture No. Collate with. Further, "registration" confirms and registers the above-mentioned attribute information.

Further, as shown in FIG. 24, "counting" is to count the specified object in SKU units. Here, the counting means may not be limited, such as measuring by weight or volume.

Further, as shown in FIG. 25, "movement" is to move an object to another management location. It should be noted that "movement" includes not only physical movement but also virtual movement without physical movement.

Physical movement is, as shown in FIG. 26, literally physically moving a place. On the other hand, as shown in FIG. 27, the virtual movement is to change the management unit by, for example, label division or provision during movement. Further, the virtual movement is, for example, changing the range on the virtual space side as shown in FIG. 28.

Returning to the description of FIG. In addition, among the "movements", the first movement to the warehouse shall be "receipt registration". Similarly, of the "movements", the final movement from the warehouse shall be "delivery registration". In addition, of the "movement", if it is out of the object management target in the warehouse, it is "deleted".

The above-mentioned "work instruction" is a series of work instructions to the work subject including each of the "specific", "count", and "move" works described with reference to FIGS. 22 to 25. FIG. 29 is an explanatory diagram regarding work instructions.

As shown in FIG. 29, "work instructions" include those with movement and those without movement. "Work instructions" that accompany movement include "warehousing registration", "receipt", "inventory movement", "replenishment movement", "delivery", "sorting", "shipping packaging", and "shipping registration".

"Receipt registration" identifies the object and registers inventory information when it is first moved to the warehouse. It also counts as needed. "Receiving" identifies an object according to a warehousing work instruction and moves it to a physical location.

"Inventory movement" physically moves an object. "Replenishment movement" physically moves the object according to the replenishment work instruction. "Delivery" physically moves the object according to the delivery work instruction. It also counts as needed.

"Sorting" physically moves an object according to a sorting instruction. It also counts as needed. "Shipping packaging" identifies an object and physically moves it to the packaging box. It also counts as needed. "Shipping registration" identifies the object and deletes the inventory information at the time of the final move from the warehouse.

On the other hand, "work instructions" that do not involve movement include "arrival inspection," "shipment inspection," and "inventory." "In-stock inspection" identifies and counts objects according to the in-stock work instructions. "Shipping inspection" identifies and counts objects according to shipping work instructions. "Inventory" identifies and counts objects according to inventory work instructions. The inventory work instruction is generated from, for example, inventory information.

Next, the above-mentioned "auxiliary work" will be described more specifically. FIG. 21 is an explanatory diagram regarding auxiliary work. As already mentioned, among the work performed by the work subject, the work not included in the above-mentioned "specification", "count", and "movement" is "auxiliary work".

As shown in FIG. 30, “auxiliary work” includes “authentication”, “input”, “number acquisition”, “reference”, “confirmation”, “output”, “operation instruction”, “event”, and “fixed”. There is a "cycle".

"Authentication" is the work of performing user authentication, device authentication, and the like. "Input" is the work of inputting data. For "input", for example, input necessary information as input for the next work.

"Number acquisition" is SKUNo. It is a work to acquire a number such as. In addition, "number acquisition" includes the numbering when there is no corresponding number. "Reference" is the work of referencing / confirming data.

"Confirmation" is, for example, the work of pressing a button on the UI screen. "Output" is the work of performing form output, message output, log output, and the like. "Operation instruction" is a work of giving an operation instruction to a device. The "operation instruction" is, for example, calling a transport device, moving to another place, or the like.

An "event" is a work that is triggered by an event generated by the previous work. "Fixed cycle" is a work generated by fixed cycle processing.

The workflow defines the procedure of each work described so far in the work instruction. The workflow creator operates the generation device 10, defines the input items and output items associated with each work abstracted in the abstract model DB 12b, and then uses the general-purpose workflow engine 12c to perform various workflows related to warehouse operations. To generate.

<Specific example of workflow>
Here, specific examples of various generated workflows will be described with reference to FIGS. 31 to 36. FIG. 31 is a diagram (No. 1) showing a specific example of the workflow related to the receipt / receipt business. Further, FIG. 32 is a diagram showing an operation example of the UI screen at the time of executing the workflow shown in FIG. 31.

Further, FIG. 33 is a diagram (No. 2) showing a specific example of the workflow related to the receipt / receipt business. Further, FIG. 34 is a diagram showing an operation example of the UI screen at the time of executing the workflow shown in FIG. 33.

In addition, FIGS. 35 and 36 are diagrams (No. 1) and (No. 2) showing specific examples of workflows including auxiliary work. In addition, in FIGS. 35 and 36, each work filled with diagonal lines corresponds to an auxiliary work.

First, in the example of FIG. 31, in the receiving / warehousing business, it is assumed that the arrival slip is attached together with the product at the time of receiving the goods. In addition, the slip No. A bar code indicating the above is attached, and the worker can use the slip No. After checking whether the arrival schedule and the product and quantity match, it shall be put into Oricon. After that, the Oricon chart shall be transported to the warehousing destination by AGV.

In such a case, for example, a workflow as shown in FIG. 31 is generated. Specifically, when the arrival slip bar code is scanned at the start of the arrival work, the slip No. output as a result of the scan. Is input and an arrival work instruction is created in the "work instruction".

Then, based on the created work instruction, the item barcode is scanned and the attached information is input in "specification". Then, based on the work instruction and the specific information in the "specific", the quantity is input in the subsequent "count".

Then, "movement (receipt registration)" is performed based on the work instruction, the specific information, and the quantity in the "count". In "Movement (receipt registration)", Oricon No. Bar code scanning is performed and the arrival work is completed.

On the other hand, the warehousing work is started triggered by the event of "movement (receipt registration)". In the warehousing work, the fixture No. output as a result of the start of the warehousing work. Is used as an input to create a move work instruction in the "work instruction".

Then, based on the created work instruction, transportation by, for example, AGV is performed in "movement". If the result of such transportation is OK, the warehousing work is completed.

In the example of FIG. 31, in the workflow of the arrival work, up to one "work instruction", "specific", "count", and "move" are included, and "specific", "count", and "move" are included. It is executed in a predetermined order. That is, it can be seen that the workflow of the arrival work is generated based on the basic form of the workflow described with reference to FIG.

Further, in the example of FIG. 31, one "work instruction" and one "movement" are included in the workflow of the warehousing work, respectively. That is, the workflow of the warehousing operation does not include a series of operations of "identification", "counting", and "moving", but indicates "moving" which is abstractly modeled at the third level according to the embodiment. It can be seen that it is generated based on the "work instruction" to be performed.

In the case of the workflow of FIG. 31, for example, the operation of the UI screen in the operation system 90 at the time of scanning the arrival slip barcode can be made to correspond to the operation example shown in FIG. 32, for example.

Next, in the example of FIG. 33, in the receiving / warehousing business, it is assumed that only the goods enter the warehouse at the time of receiving the goods. Then, the worker searches for the target arrival schedule, collates whether the product and the quantity match, and at the end of the arrival work, the inventory label No. An inventory label containing the above shall be issued. Another worker then scans the inventory label and puts the goods on the shelves.

In such a case, for example, a workflow as shown in FIG. 33 is generated. Specifically, when the item barcode is scanned at the start of the arrival work, the item No. output as a result of such scanning. Is input and an arrival work instruction is created in the "work instruction".

Then, based on the created work instruction, the attached information is input in "specification". Then, based on the work instruction and the specific information in the "specific", the count-up is performed by the item barcode scan in the subsequent "count".

Then, "movement (receipt registration)" is performed based on the work instruction, the specific information, and the quantity in the "count". In "Move (receipt registration)", the inventory label No. Is issued and the arrival work is completed.

On the other hand, in the warehousing work, the inventory label No. issued in "movement (receipt registration)" by another worker at the start of the warehousing work. When the inventory label barcode including is scanned, the inventory label No. output as a result of the scan. Based on, a move work instruction is created in the "work instruction".

Then, based on the created work instruction, for example, in "Move", the worker manually puts the product in the shelf and scans the shelf number bar code of the stored shelf. If the result is OK, the warehousing work is completed. ..

In the example of FIG. 33, in the workflow of the arrival work, as in the case of FIG. 31, up to one "work instruction", "specific", "count", and "move" are included, respectively, and "specific", "Count" and "move" are executed in a predetermined order. That is, it can be seen that the workflow of the arrival work is generated based on the basic form of the workflow described with reference to FIG.

Further, in the example of FIG. 33, one "work instruction" and one "movement" are included in the workflow of the warehousing work, respectively. That is, the workflow of the warehousing operation does not include a series of operations of "identification", "counting", and "moving", but indicates "moving" which is abstractly modeled at the third level according to the embodiment. It can be seen that it is generated based on the "work instruction" to be performed.

In the case of the workflow of FIG. 33, for example, the operation of the UI screen in the operation system 90 at the time of item barcode scanning can correspond to the operation example shown in FIG. 34, for example.

Next, in the example of FIG. 35, as a specific example of the workflow including the auxiliary work, a workflow related to calling a transport device such as an AGV will be given as an example. As described above, the auxiliary work can be arranged at any position in the workflow.

As shown in FIG. 35, in the case of calling the transport device, after the work is started, the ST No. Is input, and STNo. Is output as a result of such input. Based on, the call button is presented to the operator in "confirmation".

Then, when the operator presses the call button, the STNo. The "event" in the transport work executes the transport work by using the event of calling the transport device corresponding to the above as a trigger. Then, when the "output" receives the transfer completion from the "event", the "output" registers the transfer record.

Next, in the example of FIG. 36, as a specific example of the workflow including the auxiliary work, the workflow related to the warehousing work is given as an example.

As shown in FIG. 36, the warehousing work is started, and in the "input", the fixture No. When is input, "output" outputs the item label in the fixture accordingly. On the other hand, the fixture No. entered in "Input". In the "work instruction", a move work instruction is created based on the above.

Then, the work No. included in the created work instruction. And, based on the destination, in the "operation instruction", these work Nos. And the transport instruction including the transport destination is notified to the "event" in the transport work.

The "event" is triggered by such a notification, and the work No. is followed by the "work instruction". And the transfer destination is output, and the transfer by the transfer device is performed in "move". If the result of such transportation is OK, the warehousing work is completed.

On the other hand, the "output" in the transport work registers the transport record when the transport completion is received from the "event".

<Hardware configuration>
The generation device 10, the management system 30, the execution system 50, the control system 70, and the operation system 90 according to the above-described embodiment are realized by a computer 1000 having a configuration as shown in FIG. 37, for example. The generator 10 will be described as an example. FIG. 37 is a hardware configuration diagram showing an example of a computer that realizes the functions of the generator 10. The computer 1000 includes a CPU 1100, a RAM 1200, a ROM 1300, an HDD (Hard Disk Drive) 1400, a communication interface (I / F) 1500, an input / output interface (I / F) 1600, and a media interface (I / F) 67.

The CPU 1100 operates based on a program stored in the ROM 1300 or the HDD 1400, and controls each part. The ROM 1300 stores a boot program executed by the CPU 1100 when the computer 1000 is started, a program depending on the hardware of the computer 1000, and the like.

The HDD 1400 stores a program executed by the CPU 1100, data used by the program, and the like. The communication interface 1500 receives data from another device via the communication network and sends it to the CPU 1100, and transmits the data generated by the CPU 1100 to the other device via the communication network.

The CPU 1100 controls an output device such as a display or a printer, and an input device such as a keyboard or a mouse via the input / output interface 1600. The CPU 1100 acquires data from the input device via the input / output interface 1600. Further, the CPU 1100 outputs the generated data to the output device via the input / output interface 1600.

The media interface 1700 reads a program or data stored in the recording medium 1800 and provides the program or data to the CPU 1100 via the RAM 1200. The CPU 1100 loads the program from the recording medium 1800 onto the RAM 1200 via the media interface 1700, and executes the loaded program. The recording medium 1800 is, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or PD (Phase change rewritable Disk), a magneto-optical recording medium such as MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor. Memory etc.

For example, when the computer 1000 functions as the generation device 10 according to the embodiment, the CPU 1100 of the computer 1000 realizes each function of the control unit 13 by executing a program loaded on the RAM 1200. Further, the data in the storage unit 12 is stored in the HDD 1400. The CPU 1100 of the computer 1000 reads and executes these programs from the recording medium 1800, but as another example, these programs may be acquired from another device via a communication network.

<Summary>
As described above, the generation device 10 according to the embodiment includes a modeling unit 13b and a generation unit 13c. The modeling unit 13b abstractly models the work and data in the physical distribution business so that the workflow related to the physical distribution business can be generated by using the general-purpose workflow engine. The generation unit 13c uses the workflow engine to generate the workflow based on the work and data abstracted by the modeling unit 13b.

Therefore, according to the generation device 10 according to the embodiment, it is possible to improve the efficiency of the construction work of the physical distribution business system 1.

In particular, in this embodiment, between the first level and the second level, that is, a "third level" that is more specific than the first level and more abstract than the second level. At "level", we decided to make an abstract model of work and data related to logistics operations.

This makes it possible to extract parts that are not visible to both the customer and the Si vendor and share information in the systematization process for providing the logistics business system 1 as SI.

Incidentally, the abstraction level according to the present embodiment is assumed to be between FL5 and FL6 in the functional layer (FL) in the business process model.

Further, in the above-described embodiment, Activeiti is taken as an example as a general-purpose workflow engine, but the general-purpose workflow engine is not limited. As another example, for example, Airflow, Argo, or the like may be used.

Further effects and variations can be easily derived by those skilled in the art. For this reason, the broader aspects of the invention are not limited to the particular details and representative embodiments described and described above. Accordingly, various modifications can be made without departing from the spirit or scope of the general concept of the invention as defined by the appended claims and their equivalents.

1 Logistics business system 10 Generator 11 Acquisition I / F
12 Storage unit 12a Warehouse business information DB
12b abstract model DB
12c General-purpose workflow engine 12d Workflow DB
13 Control unit 13a Acquisition unit 13b Modeling unit 13c Generation unit 30 Management system 50 Execution system 51 Acquisition I / F
52 Communication unit 53 Storage unit 53a Workflow DB
54 Control unit 54a Acquisition unit 54b Coordination unit 54c Workflow control unit 54d UI provider 70 Control system 90 Operation system

Claims (6)

It is a method of constructing a logistics business system executed by a computer.
An external device or external device or definition information about the elements in the logistics business, the dependencies between the elements, and the data exchanged between the elements, defined by the user performing the logistics business at the second level of abstraction. The acquisition process to acquire from the storage medium and
A workflow related to the logistics operation is generated by the definition information of the third level, which is more concrete than the definition information of the first level defined in the general-purpose workflow engine and abstracted from the second level. A modeling step of abstractly modeling the definition information of the second level acquired in the acquisition step at the third level so as to be possible.
Including a generation process that generates the workflow engine customized via a business process modeling language based on the definition information of the third level abstractly modeled in the modeling process.
The modeling step is
Data included as the element in the second level of the definition information and showing at least interested parties including higher-level systems, subsystems, people and devices of the logistics business system are abstractly modeled as data showing the work entity. , Data indicating each work performed by the work entity in the distribution business is abstractly modeled as data indicating at least identification, counting or movement, and data indicating work instructions which are instructions for a series of operations to the work entity are obtained. Defined as data consisting of at least the combination of identification, counting or movement
A method of constructing a logistics business system characterized by this. The modeling step is
The method for constructing a physical distribution business system according to claim 1 , wherein the definition information regarding inventory management and transportation control in the physical distribution business is abstractly modeled. The modeling step is
2 . _ _ _ _ How to build the logistics business system described in. The modeling step is
The method for constructing a physical distribution business system according to claim 1 , 2 or 3 , wherein the definition information in the physical distribution business is abstractly modeled into a physical unit and a virtual unit. The modeling step is
The physical distribution according to any one of claims 1 to 4 , wherein the work subject in the physical distribution business, the object of the work performed by the work subject , and the management place of the object are abstractly modeled. How to build a business system. A physical distribution business system constructed by using the method for constructing a physical distribution business system according to any one of claims 1 to 5 .
A logistics business system characterized by having an execution unit that executes the logistics business by the customized workflow engine .

Images