RU2843492C1 - Method and system for generating a matrix of data on production schedules, structured according to the order, timing and duration of performing operations of all production orders - Google Patents

Abstract

FIELD: digital technologies.

SUBSTANCE: invention relates to digital technologies, particularly to methods of generating a matrix of data on production schedules for performing operations of all production orders. Method is carried out by a processor which is hosted on a server. Server has access to the storage device. Device stores files with production schedules, each containing a matrix of data on production schedules, structured in order, timing and duration of execution of operations of all production orders. Matrix includes data on the date of completion of each order and data on the date of beginning and end of each operation of each order.

EFFECT: high speed and stability of generating report management forms in the form of matrices of data for executing operations of all production orders, structured according to order, timing and duration.

2 cl, 2 dwg

Description

Field of technology

[01] The invention relates to methods of processing data to simplify the management and control of the execution of orders in production, in particular, to methods of generating data matrices on production plans for the execution of operations of all production orders.

State of the art

[02] A method for forming and structuring an electronic database is known from the prior art (RU 2696295 C1, G06F 16/22, published 01.08.2019). This solution is only suitable for combining data from ready-made tables and is not suitable for structuring tasks in large-scale production.

Disclosure of invention

[03] When working with orders, production increases its efficiency if it makes the right decisions on the loading of its capacities. Production resources are limited by the number of workers, their qualifications, machines and other equipment, as well as production and storage areas. Incoming orders consist of many parts that undergo certain technological operations, which in turn must be implemented in the best possible way. The amount of information required for processing and the complexity of the organization in production reaches a scale that a person cannot cope with. In addition, there is a need to complete the execution of the order on time, in accordance with the order contract. However, if production fulfills the order too early, it will have to bear the costs associated with storing the finished product. If production does not fulfill the order on time, it will likely face legal costs. In this regard, there is a need to adjust the completion of production processes for the execution of the order to the agreed date of delivery of the order. The production facilities have adopted a hierarchical management structure, where the top level is occupied by production managers, the middle level by shop management personnel, and the lower level by production site foremen. At each production level, it is necessary to monitor the progress of order fulfillment. The declared method and system provide such an opportunity.

[04] The objective of the invention is to instantly generate a report on the state of production of any level of complexity that is easy for a person to perceive and analyze.

[05] Technical result: increasing the speed and stability of generating reporting forms for management in the form of data matrices for the execution of operations for all production orders, structured by order, timeframe and duration.

Brief description of the drawings

[06] Fig. 1 is a schematic diagram of a computer system configured to implement certain non-limiting embodiments of the present technology.

[07] Fig. 2 is a schematic diagram of a networked computing environment incorporating the computer system of Fig. 1 and suitable for use with certain non-limiting embodiments of the present technology.

[08] List of symbols:

1 - user

2 - user's computer

3 - communication network

4 - server containing processor

5 - order data storage

6 - online production platform

7 - Request for production plans

8 - array of order IDs

9 - array of all operations of all orders

10 - sequences of basic operations

11 - sequences of planned operations

12 - file with production plans

13 - storage device

21 - RAM

22 - central processor

23 - I/O interface

24 - Solid State Drive

Implementation of the invention

[09] A computer-implemented method for generating a data matrix of production plans for the execution of operations of all production orders executed on an online production platform (6), wherein the online production platform (6) is located on a server (4), the server (4) has access to a storage device (13) storing:

at least one file with production plans (12), each of which contains: a matrix of data on the basic deadlines for the execution of operations and at least one matrix of data on the planned deadlines for the execution of operations, structured according to the order, deadlines and duration of the execution of operations of all production orders, wherein the matrices include at least: data on the completion dates of each order and data on the start and end dates of each operation of each order,

wherein the method is performed by a server (4), which includes a processor communicatively connected to the user's computer (1),

Moreover, the method contains:

receiving a request for production plans from the user's computer (7), as a result of which the processor receives data containing: the start date and end date of the order execution planning period;

formation, based on the data from the request for production plans (7), of an array of order identifiers (8) related to the planning period, with subsequent transfer to the order data warehouse (5);

receiving from the order data warehouse (5) an array of all operations of all orders (9) included in the orders specified in the array of order identifiers (8), where the array of all operations of all orders (9) includes, at least: contractual dates of order shipment; a numeric priority of execution, which specifies the order of execution of orders, wherein each operation of the order contains a duration attribute, which specifies the duration of the operation; a precedence attribute, which contains a list of operations, after the execution of which the implementation of the sought operation can be started; an attribute of the operation completion flag, which indicates that the operation is completed before the start date of the planning period; a production rate attribute, which indicates the number of machines of a certain group that can be released in a certain period; an attribute of the size of the part movement batch, which indicates the maximum number of parts that can be manufactured in a certain period of time in accordance with the technical capabilities of production;

calculation of basic terms for the execution of operations, which: forms for the array of all operations of all orders (9) sequences of basic operations (10), ordered using the attributes: duration and precedence, in such a way that several operations that do not contain precedence attributes in relation to each other can be executed in parallel; after which it determines the recommended term for the execution of each operation of the sequence of basic operations (10) of all orders of the array of all operations of all orders (9), taking into account that the end date of the last operation of each order is indicated equal to the contractual date of shipment of the corresponding order;

calculation of planned order shipment dates, which calculates for all orders of the array of all operations of all orders (9) planned order shipment dates based on at least: the operation completion flag; the numerical priority of order fulfillment; the production rate; the size of the batch of movement of the part;

calculation of planned execution dates of operations, which forms for the array of all operations of all orders (9) sequences of planned operations (11), ordered using attributes: duration, precedence, in such a way that several operations that do not contain precedence attributes in relation to each other can be executed in parallel, after which it calculates the planned execution date of each operation of the sequence of planned operations (11) of all orders of the array of all operations of all orders (9), taking into account that the end date of the last operation of each order is specified equal to the planned date of shipment of the order,

forming, on the basis of sequences of basic operations (10) and sequences of planned operations (11), a matrix of data on production orders, on the basis of which at least one file with production plans (12) is formed, which is transmitted to the user's computer (2).

[10] A system for generating a matrix of data on production plans for the execution of operations of all production orders executed on an online production platform (6), wherein the system comprises a server on which the online production platform (9) is located, wherein the server includes:

a processor communicatively connected to the user's electronic device;

a storage device that stores:

at least one file with production plans (12), each of which contains: a matrix of data on the basic deadlines for the execution of operations and at least one matrix of data on the planned deadlines for the execution of operations, structured according to the order, deadlines and duration of the execution of operations of all production orders, wherein the matrices include at least: data on the completion dates of each order and data on the start and end dates of each operation of each order,

computer-readable instructions;

whereby the processor, after executing computer-readable instructions, is configured to:

receiving from the user's computer (2) a request for production plans (7), as a result of which the processor receives data containing: the start date and end date of the order execution planning period;

formation, based on the data from the request for production plans (7), of an array of order identifiers (8) related to the planning period, with subsequent transfer to the order data warehouse (5);

receiving from the order data warehouse (5) an array of all operations of all orders (9) included in the orders specified in the array of order identifiers (8), where the array of all operations of all orders (9) includes, at least: contractual dates of order shipment; a numeric priority of execution, which specifies the order of execution of orders, wherein each order operation contains a duration attribute, which specifies the duration of the operation; a precedence attribute, which contains a list of operations, after the execution of which the implementation of the sought operation can be started; an attribute of the operation completion flag, which indicates that the operation is completed before the start date of the planning period; an attribute of the production rate, which indicates the number of machines of a certain group that can be released in a certain period; an attribute of the size of the part movement batch, which indicates the maximum number of parts that can be manufactured in a certain period of time in accordance with the technical capabilities of production;

calculation of basic terms for the execution of operations, which: forms for the array of all operations of all orders (9) sequences of basic operations (10), ordered using the attributes: duration and precedence, in such a way that several operations that do not contain precedence attributes in relation to each other can be executed in parallel; after which it determines the recommended term for the execution of each operation of the sequence of basic operations (10) of all orders of the array of all operations of all orders (9), taking into account that the end date of the last operation of each order is indicated equal to the contractual date of shipment of the corresponding order;

calculation of planned order shipment dates, which calculates for all orders of the array of all operations of all orders (9) planned order shipment dates based on at least: the operation completion flag; the numerical priority of order fulfillment; the production rate; the size of the batch of movement of the part;

calculation of planned execution dates of operations, which forms for the array of all operations of all orders (9) sequences of planned operations (11), ordered using attributes: duration, precedence, in such a way that several operations that do not contain precedence attributes in relation to each other can be executed in parallel, after which it calculates the planned execution date of each operation of the sequences of planned operations (11) of all orders of the array of all operations of all orders (9), taking into account that the end date of the last operation of each order is specified equal to the planned date of shipment of the order,

forming, on the basis of sequences of basic operations (10) and sequences of planned operations (11), a matrix of data on production orders, on the basis of which at least one file with production plans (12) is formed, which is transmitted to the user's computer (2).

[11] To use the claimed system, the user (1) logs into the online production platform (6), for example, the corporate information system for production planning (CIPP) or another MES platform, via the user's computer (2). The user (1) generates a request for production plans to obtain information on the production status, simultaneously transmitting information on the start date and end date of the order fulfillment period (7). This request and information on the start date and end date of the order fulfillment period are sent via a communication network (3), for example in the form of the Internet, Intronet, local area network, etc., to a server (4) containing a processor. The processor processes data on the start date and end date of the order planning period (7), generating, using the appropriate software, an array of order identifiers (8), which is then sent to the order data warehouse, which can be implemented in the form of a microcomputer designed with the ability to receive, process and issue data. The storage processes the order data of the order identifier array (8), forming, using the appropriate software, an array of all operations of all orders (9) of production. After which the storage transmits the array of all operations of all orders (9) to the server processor (4). The received array of all operations of all orders (9) is processed by the processor, forming sequences of basic operations (10). In addition, the processor, based on the array of all operations of all orders (10), forms sequences of planned operations (11). Sequences of basic operations (10) and sequences of planned operations (10), which can be data expressed in a table, lines, or expressed in any other forms, when combined into a single document, form a file with production plans (12). This file with production plans (12) is sent to the user's computer (2) as a response to a request for production plans (7) of the user (1). The file with production plans (12) can be an album of forms, which reflects the main parameters of orders, as well as the planned shipment schedule.

[12] The calculation of the basic execution dates, which ultimately forms a cyclogram, occurs as follows. The processor receives a list of operations of one of the orders as input. Each order operation has its execution duration and predecessors of the operations that must be executed before it. Thus, the order operations are arranged in a sequence, numbering their order. The processor also calculates the optimal execution time for all the order operations, taking into account the order of their execution, while several operations can be executed in parallel, at the same time, if they are not predecessors/successors for each other. In this way, sequences are constructed in the form of a chain of operations. For each operation, a time interval is determined for when the operation should optimally begin and end. For the last operation, the end date is indicated equal to the order shipment date under the contract.

[13] As an example of the operation of the cyclogram calculation processor, we will take order #1 received from the order information warehouse. The date and time of shipment of order #1 under the contract: 8:00 a.m., February 14, 2025. The order also contains a list of five operations. The cyclogram calculation processor runs the algorithm, where it sequentially analyzes each of the five operations. For example, the first operation, “painting”, has a predecessor attribute specified in its characteristics: the second, third, and fourth operations, respectively, “grinding”, “degreasing”, and “priming”, which must be completed before the first operation, “painting”, can be started. The second, third, and fourth operations have a predecessor specified as an attribute: the fifth operation, “welding”, which must be completed before the second, third, and fourth operations can be started. The fifth operation does not contain any successor attributes. Thus, the cyclogram calculation processor builds a sequence in the form of the following chain of operations: the fifth operation "welding" - then the parallel second - "grinding", the third - "degreasing" and the fourth - "priming" operations - then the first operation "painting". It is indicated that the execution time of each operation is one day, therefore, the estimated execution time for the entire cyclogram is three days. And the optimal start date for the fifth operation of the order is three days before the date and time of shipment of the order under the contract, namely: 8 am, February 11. The optimal start date for the second, third and fourth operations: 8 am, February 12, immediately after the end of the first operation. And the optimal start date for the first operation: 8 am, February 13. Thus, a plan for the optimal execution of the order is built, which defines the sequence of actions, as well as the optimal start and end dates for each of the operations. The example is provided to facilitate understanding of the processor's operation and may contain information that is incorrect from a technological point of view.

[14] Each production order includes the following data, which is stored in the order data warehouse (5):

- Product card, including: order opening date; delivery date under the contract; shipment date under the contract; release date according to the schedule; product item; quantity of products,

- Design documentation for the product/part, including: references to parts that include this part; references to incoming parts of our own production; the need for materials and purchased components;

- List of operations: operation number; operation name; operation execution area; operation duration; labor costs for performing operations; technological equipment; predecessor; operation type; feature of the main product - the first in the cyclogram.

[15] Sequences of basic operations (10) and sequences of planned operations (11) contain, for example, the following data: delivery date under the contract/shipment date under the contract; product; number of products in the order; number of products in the batch; array of operations for manufacturing the product; duration of operations; predecessors for each operation.

[16] The file with production plans contains both the data of the sequence of basic operations (10) and the data of the sequence of planned operations (11).

[17] To ensure understanding of the terms, the following explanations are provided. Order ID array: Each order contains an ID to enable software to identify them.

[18] Array of all operations of all orders: data about each operation of each order, collected together.

[19] Basic and planned dates for the execution of operations differ due to the difference between contract and planned dates for the completion of orders. Basic dates are calculated based on a fixed contract date. A change in the planned dates for the execution of an order in relation to the contract dates is associated with rescheduling, which is necessary to ensure uniform loading of production capacities. Planned dates for the completion of orders are used to form a sequence of planned dates for the execution of operations (11), and contract dates for the completion of orders are used to form a sequence of basic dates for the execution of operations (10).

[20] Data matrices should be understood, for example, as a set of rows with data (attributes) about operations presented in a matrix structure (rows, columns, cells visually represent a matrix), for example, including data on sequences of basic operations (10) and planned operations (11). Also, a data matrix can be made in the form of a Gantt chart or any other options.

[21] The examples and conditional statements in the application are described to provide understanding to the reader, and not to limit its scope to such specifically given examples and conditions. It should be understood that those skilled in the art will be able to devise various mechanisms that, although not explicitly described in this document, nevertheless embody the principles of the present technology and are included within its spirit and scope.

[22] Furthermore, the description of the implementation of the present technology may be described in a relatively simplified form for the purpose of ease of understanding. Those skilled in the art will understand that various implementations of the present technology may have greater complexity.

[23] In some cases, examples of modifications to the present technology may also be set forth. These modifications are not an exhaustive list, and a person skilled in the art will be able to make other modifications while still remaining within the scope of the present technology. Furthermore, cases where examples of modifications are not given should not be interpreted to mean that no modifications can be made and/or that what is described is the only way to implement such an element of the present technology.

[24] Moreover, all statements in this document that set forth principles, aspects, and implementations of the technology, as well as specific examples thereof, are intended to cover both their structural and functional equivalents, whether now known or hereafter developed. Thus, for example, those skilled in the art will recognize that any block diagrams in this document represent conceptual views of illustrative circuitry embodying the principles of the present technology. Likewise, it will be understood that any flow charts, sequence diagrams, state transition diagrams, pseudo-codes, and the like represent various processes that may be substantially represented on computer-readable media and thereby executed by a computer or processor, whether or not such computer or processor is explicitly shown.

[25] The functions of the various elements shown in the figures, including any functional unit designated as "storage," "processor," may be provided by dedicated hardware as well as hardware capable of executing software in conjunction with associated software. When provided by a processor, the functions may be provided by a single dedicated processor, a single shared processor, or a plurality of separate processors, some of which may be shared. Furthermore, the explicit use of the term "processor" or "controller" should not be construed as referring exclusively to hardware capable of executing software and may implicitly include, but are not limited to, digital signal processor (DSP) hardware, a network processor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), read-only memory (ROM) for storing software, random access memory (RAM), and non-volatile storage. Other hardware, traditional and/or specialized, may also be included.

[26] The communication network may be the Internet, an intranet, a global network, a local network, etc. It should be clearly understood that the implementations for the communication network are intended for illustrative purposes only. How the corresponding communication channel (not separately numbered) between each of the user's computer (2), the server (4) and the communication network (3) is implemented will depend, among other things, on how each of the user's computer (2) and the server (4) is implemented. Just as an example, and not a limitation, the user's computer (2) is implemented as a wireless communication device, such as a laptop, the communication channel can be implemented as a wireless communication channel. Examples of wireless communication channels include, but are not limited to, a communication channel in a 3G network, a communication channel in a 4G network, and the like. The communication network (3) may also use a wireless connection to the server (4) and each of the third-party servers.

Claims (24)

1. A method for generating a matrix of data on production plans for the execution of operations of all production orders executed on an online production platform (6), wherein the online production platform (6) is located on a server (4), the server (4) has access to a storage device (13) storing: at least one file with production plans (12), each of which contains: a matrix of data on the basic deadlines for the execution of operations and at least one matrix of data on the planned deadlines for the execution of operations, structured according to the order, deadlines and duration of the execution of operations of all production orders, wherein the matrices include at least: data on the completion dates of each order and data on the start and end dates of each operation of each order, wherein the method is performed by a server (4), which includes a processor communicatively connected to the user's computer (1), the method contains: receiving a request for production plans from the user's computer (7), as a result of which the processor receives data containing: the start date and end date of the order execution planning period; formation, based on the data from the request for production plans (7), of an array of order identifiers (8) related to the planning period, with subsequent transfer to the order data warehouse (5); receiving from the order data warehouse (5) an array of all operations of all orders (9) included in the orders specified in the array of order identifiers (8), where the array of all operations of all orders (9) includes, at least: contractual dates of order shipment; a numeric priority of execution, which specifies the order of execution of orders, wherein each operation of the order contains a duration attribute, which specifies the duration of the operation; a precedence attribute, which contains a list of operations, after the execution of which the implementation of the sought operation can be started; an attribute of the operation completion flag, which indicates that the operation is completed before the start date of the planning period; an attribute of the production rate, which indicates the number of machines of a certain group that can be released in a certain period; an attribute of the size of the part movement batch, which indicates the maximum number of parts that can be manufactured in a certain period of time in accordance with the technical capabilities of production; calculation of basic terms for the execution of operations, which forms for the array of all operations of all orders (9) sequences of basic operations (10), ordered using the attributes: duration and precedence, in such a way that several operations that do not contain precedence attributes in relation to each other can be executed in parallel; after which it determines the recommended term for the execution of each operation of the sequence of basic operations (10) of all orders of the array of all operations of all orders (9), taking into account that the end date of the last operation of each order is indicated equal to the contractual date of shipment of the corresponding order; calculation of planned order shipment dates, which calculates for all orders of the array of all operations of all orders (9) planned order shipment dates based on at least: the operation completion flag; the numerical order fulfillment priority; the production rate; the size of the part movement batch; calculation of planned execution dates of operations, which forms for the array of all operations of all orders (9) sequences of planned operations (11), ordered using attributes: duration, precedence, in such a way that several operations that do not contain precedence attributes in relation to each other can be executed in parallel, after which it calculates the planned execution date of each operation of the sequence of planned operations (11) of all orders of the array of all operations of all orders (9), taking into account that the end date of the last operation of each order is specified equal to the planned date of shipment of the order, forming, on the basis of sequences of basic operations (10) and sequences of planned operations (11), a matrix of data on production orders, on the basis of which at least one file with production plans (12) is formed, which is transmitted to the user's computer (2). 2. A system for generating a matrix of data on production plans for the execution of operations of all production orders executed on an online production platform (6), wherein the system comprises a server on which the online production platform (9) is located, wherein the server includes: a processor communicatively connected to the user's electronic device; a storage device that stores: at least one file with production plans (12), each of which contains: a matrix of data on the basic deadlines for the execution of operations and at least one matrix of data on the planned deadlines for the execution of operations, structured according to the order, deadlines and duration of the execution of operations of all production orders, wherein the matrices include, at least: data on the completion dates of each order and data on the start and end dates of each operation of each order, computer-readable instructions; wherein the processor, after executing computer-readable instructions, is configured to: receiving from the user's computer (2) a request for production plans (7), as a result of which the processor receives data containing: the start date and end date of the order execution planning period; formation, based on the data from the request for production plans (7), of an array of order identifiers (8) related to the planning period, with subsequent transfer to the order data warehouse (5); receiving from the order data warehouse (5) an array of all operations of all orders (9) included in the orders specified in the array of order identifiers (8), where the array of all operations of all orders (9) includes, at least: contractual dates of order shipment; a numeric priority of execution, which specifies the order of execution of orders, wherein each operation of the order contains a duration attribute, which specifies the duration of the operation; a precedence attribute, which contains a list of operations, after the execution of which the implementation of the sought operation can be started; an attribute of the operation completion flag, which indicates that the operation is completed before the start date of the planning period; an attribute of the production rate, which indicates the number of machines of a certain group that can be released in a certain period; an attribute of the size of the part movement batch, which indicates the maximum number of parts that can be manufactured in a certain period of time in accordance with the technical capabilities of production; calculation of basic terms for the execution of operations, which forms for the array of all operations of all orders (9) sequences of basic operations (10), ordered using the attributes: duration and precedence, in such a way that several operations that do not contain precedence attributes in relation to each other can be executed in parallel; after which it determines the recommended term for the execution of each operation of the sequence of basic operations (10) of all orders of the array of all operations of all orders (9), taking into account that the end date of the last operation of each order is indicated equal to the contractual date of shipment of the corresponding order; calculation of planned order shipment dates, which calculates for all orders of the array of all operations of all orders (9) planned order shipment dates based on at least: the operation completion flag; the numerical order fulfillment priority; the production rate; the size of the batch of movement of the part; calculation of planned execution dates of operations, which forms for the array of all operations of all orders (9) sequences of planned operations (11), ordered using attributes: duration, precedence, in such a way that several operations that do not contain precedence attributes in relation to each other can be executed in parallel, after which it calculates the planned execution date of each operation of the sequences of planned operations (11) of all orders of the array of all operations of all orders (9), taking into account that the end date of the last operation of each order is specified equal to the planned date of shipment of the order, forming, on the basis of sequences of basic operations (10) and sequences of planned operations (11), a matrix of data on production orders, on the basis of which at least one file with production plans (12) is formed, which is transmitted to the user's computer (2).