Smelting pouring production scheduling method capable of being arranged under multiple limiting conditions

Abstract

The invention relates to a smelting pouring production scheduling method capable of being arranged under multiple limiting conditions, and the method comprises a compiling assembly which comprises a data collection module used for obtaining and storing production data required by a system, and taking the production data as basic data of production scheduling; the production scheduling configuration module is used for performing production scheduling configuration based on the basic data; the flow arrangement configuration module is used for carrying out logic arrangement on each limiting factor in a flow arrangement form; the resource caching module is used for caching data required by a production scheduling algorithm; compiling rules: arranging the components, and supporting serial and parallel arrangement modes; caching the data; production scheduling: production scheduling configuration, production scheduling rule selection, production scheduling result analysis and production scheduling locking. The method has the beneficial effects that the production efficiency is improved, fine resource allocation optimization is realized, the product quality is reliably guaranteed, and the forceful delivery timeliness is enhanced.

Description

Technical Field

[0001] The invention relates to a smelting and pouring scheduling method with programmable multiple restriction conditions, belonging to the technical field of production scheduling. Background Art

[0002] At present, scheduling of smelting and pouring production has always been a difficult problem.

[0003] First, there are many constraints on smelting production scheduling, including: delivery orders, production scheduling, production line capacity, energy consumption (peak and valley electricity), finished product inventory, outsourcing inventory, work-in-progress orders, reserve plans, small-scale trial production, furnace and batch combination, insulation time, etc. These factors are reflected in the actual production scheduling work and are considered by different personnel. For example, the production planner will consider delivery orders, production scheduling, production line capacity, energy consumption, finished product inventory, outsourcing inventory, work-in-progress orders, reserve plans, etc. After splitting into smelting production orders, the smelting section chief will consider small-scale trial production, furnace and batch combination, insulation time, etc. This has led to the fact that it is difficult to ensure delivery and full capacity through artificial capacity scheduling, and it is difficult to provide a more accurate and scientific optimal production scheduling.

[0004] Secondly, due to different processes, the constraints of production scheduling for each production line are different. For example, the static pressure line has a unique insulation time limit, the three cast iron lines have multiple products produced in the same mold, and in the future, cast steel may also have multiple products produced in the same mold. This requires the production scheduling algorithm to be flexible and changeable to cope with various scenarios. Summary of the invention

[0005] In order to overcome the shortcomings of the above-mentioned prior art, the present invention provides a smelting and pouring scheduling method that can be arranged with multiple constraints. It uses process scheduling technology and resource caching technology to comprehensively consider various factors of scheduling constraints, flexibly configure scheduling constraints, and automatically schedule demand plans to obtain optimal smelting plans and pouring plans.

[0006] The present invention is realized by the following technical scheme: a smelting and pouring scheduling method with multiple constraints that can be arranged, comprising: S1 writing components: Data acquisition module, used to obtain and save the production data required by the system as the basic data for production scheduling; The production scheduling configuration module performs production scheduling configuration based on basic data; The process orchestration configuration module logically arranges various restriction factors in the form of process orchestration; Resource cache module, which caches the data required by the production scheduling algorithm; S1 writing components specifically include: S101, component NodeProductInfo: fill product information component; S1011, obtaining cached data to be scheduled; S1012, obtaining cache data product archive; S1013, matching the product files of the data to be scheduled, filling the corresponding product information if the product files exist, and deleting the product files if they do not exist; S1014, writing the processed data to be scheduled into the context productOrder.

[0007] S102, component NodeSort: priority sorting component; S103, component NodeOutsourceFilter: full process outsourcing filtering component; S104, component NodeFinishedFilter: finished product inventory filtering component; S105, component NodeMakingFilter: work-in-progress order filtering component; S106, component NodeConfirmFilter: locked order filter component; S107, component NodeDeliveryFilter: shipped filtering component; S108, component NodeOutsourceFinishedFilter: outsourced inventory filtering component; S109, component NodeSmeltingFurnaceMerge: product material furnace merging and dismantling components; S110, component NodeCapacity: scheduling capacity calculation component; S111, component NodeCooling: insulation zone limiting component.

[0008] The S102, component NodeSort: the priority sorting component specifically includes: S1021, obtaining the production data to be scheduled from the context productOrder; S1022, sort by production date; S1023, sort by product priority; S1024, write the sorted data back to productOrder.

[0009] The S103, component NodeOutsourceFilter, the full process outsourcing filtering component specifically includes: S1031, obtaining the production data to be scheduled from the context productOrder; S1032, filter outsourced products in all processes and delete them from the production data to be scheduled; S1033, writing the filtered production data to be scheduled into the context productOrder.

[0010] The S104, component NodeFinishedFilter finished product inventory filtering component specifically includes: S1041, obtaining the production data to be scheduled from the context productOrder; S1042, obtaining cached finished product inventory data; S1043, matching the production data to be scheduled, and deducting the production data to be scheduled in sequence; S1044, writing the filtered production data to be scheduled into the context productOrder.

[0011] The S109, component NodeSmeltingFurnaceMerge product material furnace merging and dismantling components specifically include: S1091, obtain the production data to be scheduled from the context productOrder; S1092, disassemble into a whole furnace according to product information configuration; S1093: If the furnace is not integrated, it shall be integrated according to the same product and material of the same day; S1094, if the furnace is still not integrated and the production configuration [Is the material replaceable for integration] is yes, search for replaceable materials for integration; S1095, if the furnace is still not integrated, search for subsequent plans for the same product and material and integrate the furnace according to the date; S1096, if the furnace is still not integrated and the production scheduling configuration [Whether the material can be replaced during the furnace integration] is yes, search for the subsequent planned replaceable materials in order by date for furnace integration; S1097: If the furnace is still not repaired and the [Minimum furnace start-up package] is not reached, it is marked as not meeting the minimum furnace start-up package, saved and stored, and deleted from the production data to be scheduled; S1098, write the processed data into the context productOrder.

[0012] The S110, component NodeCapacity scheduling capacity calculation component specifically includes: S1101, obtaining the production data to be scheduled from the context productOrder; S1102, obtaining a factory calendar from a cache; S1103, match the factory calendar by date. If the date matches, calculate the capacity. If the capacity meets the requirement, mark it as capacity meets. If the capacity does not meet the requirement, match the factory calendar of the next day. If the date does not match the factory calendar, mark it as capacity cannot be met. Save and store it, and delete it from the production data to be scheduled. S1104, write the processed data into the context productOrder.

[0013] S2 writing rules: arrange components and support serial and parallel arrangement; S3 cache data: The S3 cache data includes: S301, product files, cached in the form of key-value, where key is the product material code and value is the product information; S302, smelting furnace information, cached in the form of key-value, the key is the production line plus the sequence number, the value is the equipment code plus the equipment name; S303, confirmed plan, cached in key-value format, key is product material code, value is confirmed number; S304, the shipped data is cached in the form of key-value, where the key is the product material code and the value is the shipment quantity; S305, finished product inventory data, cached in the form of key-value, where the key is the product material code and the value is the finished product inventory number; S306, outsourcing inventory data is cached in the form of key-value, where the key is the product material code and the value is the outsourcing inventory quantity; S307, WIP order data is cached in the form of key-value, where the key is the product material code and the value is the number of WIP; S308, factory calendar, load the factory calendar to calculate the daily working hours and cache them in the form of key-value, where the key is the production line plus the date, and the value is a map object, including the start time, end time, and working hours; S309, insulation zone, simulates caching of static pressure line insulation zone, caches in the form of key-value, key is date plus insulation zone track number, value is current insulation quantity; S310, the production data to be scheduled is loaded with the delivery order and cached in the form of key-value, where the key is the production line plus the date and the value is the production order set; S311, production scheduling configuration data, load the production scheduling configuration data, cache in the form of key-value, including: scheduling start date, key is schedulingStartDate, value is date type; whether the furnace can replace the material, key is materialReplaceFlag, value is Boolean type; minimum furnace opening bag, key is pouringMinBag, value is integer type; horizontal line, vertical line, static pressure line melting time, key is the production line abbreviation plus PouringTime, value is integer type; horizontal line, vertical line, static pressure line melting furnace maximum parallel number, key is the production line abbreviation plus PouringNum, value is integer type.

[0014] S4 Scheduling: Scheduling configuration, selecting scheduling rules, analyzing scheduling results, and locking scheduling: S401, production scheduling configuration, including: factory calendar, product priority, product substitution material, horizontal line\vertical line\static line melting time, horizontal line\vertical line\static line pouring time, horizontal line\vertical line\static line parallel furnace number, minimum furnace opening package; S402, select a scheduling rule, which is a scheduling rule configured for S3 cache data; S403, production scheduling result analysis, analyzing the production scheduling results and adjusting the production scheduling errors caused by production scheduling configuration errors and basic data errors; S404, production scheduling lock, fine-tune the production scheduling results by date, lock them after confirmation, and support locking plans for the next 7 days.

[0015] The beneficial effects of the present invention are: improved production efficiency, refined resource allocation optimization, reliable product quality assurance, strong delivery timeliness enhancement, production scheduling result analysis and production scheduling locking functions, just like a rigorous auditor, multi-dimensional review of the production scheduling plan, timely correction of configuration and data deviations, locking the plan for the next 7 days, production scheduling execution is as stable as a rock, and the risk of delivery delays is eliminated. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The present invention is further described below with reference to the accompanying drawings and embodiments.

[0017] Figure 1 It is the overall flow chart of the present invention; Figure 2 is a flow chart of production scheduling rule I of the present invention; Figure 3 It is a flow chart of the production scheduling rule III of the present invention. DETAILED DESCRIPTION

[0018] like Figure 1A smelting and pouring scheduling method with multiple constraints that can be programmed is shown, comprising: S1 writing components: Data acquisition module, used to obtain and save the production data required by the system as the basic data for production scheduling; The production scheduling configuration module performs production scheduling configuration based on basic data; The process orchestration configuration module logically arranges various restriction factors in the form of process orchestration; Resource cache module, which caches the data required by the production scheduling algorithm; Process orchestration is to modify the vertical writing of code into component-based writing, and then implement arbitrary logic arrangement through orchestration rules. Here we take Java technology as an example. Component: A separate code file with the annotation @NodeComponent("a") and the component name in brackets.

[0019] Context: Data passed within a component, supports multiple contexts, and is cached in program memory in the form of key-value.

[0020] Orchestration rules: Orchestrate components, supporting serial and parallel orchestration. Orchestration rule execution mechanism: After the orchestration rules are changed, the program loads all classes annotated with @NodeComponent. When an orchestration rule is executed, an execution record is generated to record the completion of component execution, and components are executed in sequence according to the rule settings.

[0021] S1 writing components specifically include: S101, component NodeProductInfo: fill product information component; S1011, obtaining cached data to be scheduled; S1012, obtaining cache data product archive; S1013, matching the product files of the data to be scheduled, filling the corresponding product information if the product files exist, and deleting the product files if they do not exist; S1014, writing the processed data to be scheduled into the context productOrder.

[0022] S102, component NodeSort: priority sorting component; specifically includes: S1021, obtaining the production data to be scheduled from the context productOrder; S1022, sort by production date; S1023, sort by product priority; S1024, write the sorted data back to productOrder.

[0023] S103, component NodeOutsourceFilter: full process outsourcing filtering component; specifically includes: S1031, obtaining the production data to be scheduled from the context productOrder; S1032, filter outsourced products in all processes and delete them from the production data to be scheduled; S1033, writing the filtered production data to be scheduled into the context productOrder.

[0024] S104, component NodeFinishedFilter: finished product inventory filtering component; specifically includes: S1041, obtaining the production data to be scheduled from the context productOrder; S1042, obtaining cached finished product inventory data; S1043, matching the production data to be scheduled, and deducting the production data to be scheduled in sequence; S1044, writing the filtered production data to be scheduled into the context productOrder.

[0025] S105, component NodeMakingFilter: The work-in-progress order filtering component is similar to S104; S106, component NodeConfirmFilter: the locked order filtering component is similar to S104; S107, component NodeDeliveryFilter: the shipped filtering component is similar to S104; S108, component NodeOutsourceFinishedFilter: the outsourced inventory filtering component is similar to S104; S109, component NodeSmeltingFurnaceMerge: product material furnace merging and dismantling components; specifically includes: S1091, obtain the production data to be scheduled from the context productOrder; S1092, disassemble into a whole furnace according to product information configuration; S1093: If the furnace is not integrated, it shall be integrated according to the same product and material of the same day; S1094, if the furnace is still not integrated and the production configuration [Is the material replaceable for integration] is yes, search for replaceable materials for integration; S1095, if the furnace is still not integrated, search for subsequent plans for the same product and material and integrate the furnace according to the date; S1096, if the furnace is still not integrated and the production scheduling configuration [Whether the material can be replaced during the furnace integration] is yes, search for the subsequent planned replaceable materials in order by date for furnace integration; S1097: If the furnace is still not repaired and the [Minimum furnace start-up package] is not reached, it is marked as not meeting the minimum furnace start-up package, saved and stored, and deleted from the production data to be scheduled; S1098, write the processed data into the context productOrder.

[0026] S110, component NodeCapacity: scheduling capacity calculation component; specifically includes: S1101, obtaining the production data to be scheduled from the context productOrder; S1102, obtaining a factory calendar from a cache; S1103, match the factory calendar by date. If the date matches, calculate the capacity. If the capacity meets the requirement, mark it as capacity meets. If the capacity does not meet the requirement, match the factory calendar of the next day. If the date does not match the factory calendar, mark it as capacity cannot be met. Save and store it, and delete it from the production data to be scheduled. S1104, write the processed data into the context productOrder.

[0027] S111, component NodeCooling: Insulation zone restriction component, the insulation zone has 4 chains, and each chain has 50 boxes available. When there is free time, the product will go through 4 chains, and each chain takes 1.5 hours. If there is a product with a insulation time of more than 6 hours, it needs to stay in the insulation zone until the time is met. However, in order to prevent production blockage, it is necessary to ensure that 2 chains are operating normally. Therefore, there are only 2 insulation zones that can stay. Therefore, the logic of the insulation zone component is as follows: S1111, obtain the production data to be scheduled from the context productOrder.

[0028] S1112, obtaining the insulation zone data from the cache data.

[0029] S1113, when areas 1 and 2 are empty and the time is less than 6 hours, the production schedule is returned. If it is greater than 6 hours, the smaller value of the production schedule and 100 is returned, and the corresponding insulation area cache is insulated.

[0030] S1114, when any one of areas 1 and 2 is occupied, if the time is less than 4 hours, the production number is returned; if it is greater than 4 hours, the smaller value of the production number and the remaining value of the two areas is returned, and the corresponding insulation area cache is insulated.

[0031] S1115: When both zones are occupied and the time is less than 3 hours, the production schedule is returned; if it is greater than 3 hours, the smaller value of the production schedule and the remaining time of the two zones is returned.

[0032] S1116, if the available heat preservation number is equal to 0, this data is moved back 5 places. If it is greater than 0 but less than the scheduled production number, the available heat preservation number is recorded, and a new piece of data to be scheduled is created for the remaining quantity and placed in the next 5 places.

[0033] S1117, write the processed data into the context productOrder.

[0034] S2 writing rules: arrange components and support serial and parallel arrangement; S201, production scheduling rule I, applies to horizontal lines and vertical lines. The production plan is a processed production plan (finished product inventory, work-in-progress information, and outsourced inventory have been removed). The production scheduling rules are as follows: Figure 2 .

[0035] S202, production scheduling rule II, is applicable to static pressure lines. The production plan is a processed production plan (finished product inventory, work-in-progress information, and outsourced inventory have been removed). Just add the restriction of the insulation zone at the end of S201.

[0036] S203, production scheduling rules III, applicable to horizontal lines and vertical lines, production plans are not processed, production scheduling rules are as follows Figure 3 .

[0037] S3 cache data: The S3 cache data includes: S301, product files, cached in the form of key-value, where key is the product material code and value is the product information; S302, smelting furnace information, cached in the form of key-value, the key is the production line plus the sequence number, the value is the equipment code plus the equipment name; S303, confirmed plan, cached in key-value format, key is product material code, value is confirmed number; S304, the shipped data is cached in the form of key-value, where the key is the product material code and the value is the shipment quantity; S305, finished product inventory data, cached in the form of key-value, where the key is the product material code and the value is the finished product inventory number; S306, outsourcing inventory data is cached in the form of key-value, where the key is the product material code and the value is the outsourcing inventory quantity; S307, WIP order data is cached in the form of key-value, where the key is the product material code and the value is the number of WIP; S308, factory calendar, load the factory calendar to calculate the daily working hours and cache them in the form of key-value, where the key is the production line plus the date, and the value is a map object, including the start time, end time, and working hours; S309, insulation zone, simulates caching of static pressure line insulation zone, caches in the form of key-value, key is date plus insulation zone track number, value is current insulation quantity; S310, the production data to be scheduled is loaded with the delivery order and cached in the form of key-value, where the key is the production line plus the date and the value is the production order set; S311, production scheduling configuration data, load the production scheduling configuration data, cache in the form of key-value, including: scheduling start date, key is schedulingStartDate, value is date type; whether the furnace can replace the material, key is materialReplaceFlag, value is Boolean type; minimum furnace opening bag, key is pouringMinBag, value is integer type; horizontal line, vertical line, static pressure line melting time, key is the production line abbreviation plus PouringTime, value is integer type; horizontal line, vertical line, static pressure line melting furnace maximum parallel number, key is the production line abbreviation plus PouringNum, value is integer type.

[0038] S4 Scheduling: Scheduling configuration, selecting scheduling rules, analyzing scheduling results, and locking scheduling: S401, production scheduling configuration, including: factory calendar, product priority, product substitution material, horizontal line\vertical line\static line melting time, horizontal line\vertical line\static line pouring time, horizontal line\vertical line\static line parallel furnace number, minimum furnace opening package; S402, select a scheduling rule, which is a scheduling rule configured for S3 cache data; S403, production scheduling result analysis, analyzing the production scheduling results and adjusting the production scheduling errors caused by production scheduling configuration errors and basic data errors; S404, production scheduling lock, fine-tune the production scheduling results by date, lock them after confirmation, and support locking plans for the next 7 days.

Claims

1. A smelting and pouring scheduling method with multiple constraints, characterized in that: include: S1 writing components: Data acquisition module, used to obtain and save the production data required by the system as the basic data for production scheduling; The production scheduling configuration module performs production scheduling configuration based on basic data; The process orchestration configuration module logically arranges various restriction factors in the form of process orchestration; Resource cache module, which caches the data required by the production scheduling algorithm; S2 writing rules: arrange components and support serial and parallel arrangement; S3 caches data; S4 Scheduling: Scheduling configuration, selecting scheduling rules, analyzing scheduling results, and locking scheduling.

2. A smelting and pouring scheduling method with multiple constraints arrangable according to claim 1, characterized in that: The S1 writing components specifically include: S101, component NodeProductInfo: fill product information component; S102, component NodeSort: priority sorting component; S103, component NodeOutsourceFilter: full process outsourcing filtering component; S104, component NodeFinishedFilter: finished product inventory filtering component; S105, component NodeMakingFilter: work-in-progress order filtering component; S106, component NodeConfirmFilter: locked order filter component; S107, component NodeDeliveryFilter: shipped filtering component; S108, component NodeOutsourceFinishedFilter: outsourced inventory filtering component; S109, component NodeSmeltingFurnaceMerge: product material furnace merging and dismantling components; S110, component NodeCapacity: scheduling capacity calculation component; S111, component NodeCooling: insulation zone limiting component.

3. A method for scheduling smelting and pouring with multiple constraints according to claim 2, characterized in that: The S101, component NodeProductInfo: filling product information component specifically includes: S1011, obtaining cached data to be scheduled; S1012, obtaining cache data product archive; S1013, matching the product files of the data to be scheduled, filling the corresponding product information if the product files exist, and deleting the product files if they do not exist; S1014, writing the processed data to be scheduled into the context productOrder.

4. A method for scheduling smelting and pouring with multiple constraints according to claim 2, characterized in that: The S102, component NodeSort: the priority sorting component specifically includes: S1021, obtaining the production data to be scheduled from the context productOrder; S1022, sort by production date; S1023, sort by product priority; S1024, write the sorted data back to productOrder.

5. The method for scheduling smelting and pouring with multiple constraints according to claim 2, characterized in that: The S103, component NodeOutsourceFilter, the full process outsourcing filtering component specifically includes: S1031, obtaining the production data to be scheduled from the context productOrder; S1032, filter outsourced products in all processes and delete them from the production data to be scheduled; S1033, writing the filtered production data to be scheduled into the context productOrder.

6. The method for scheduling smelting and pouring with multiple constraints according to claim 2, characterized in that: The S104, component NodeFinishedFilter finished product inventory filtering component specifically includes: S1041, obtaining the production data to be scheduled from the context productOrder; S1042, obtaining cached finished product inventory data; S1043, matching the production data to be scheduled, and deducting the production data to be scheduled in sequence; S1044, writing the filtered production data to be scheduled into the context productOrder.

7. The method for scheduling smelting and pouring with multiple constraints according to claim 2, characterized in that: The S109, component NodeSmeltingFurnaceMerge product material furnace merging and dismantling components specifically include: S1091, obtain the production data to be scheduled from the context productOrder; S1092, disassemble into a whole furnace according to product information configuration; S1093: If the furnace is not integrated, it shall be integrated according to the same product and material of the same day; S1094, if the furnace is still not integrated and the production configuration [Is the material replaceable for integration] is yes, search for replaceable materials for integration; S1095, if the furnace is still not integrated, search for subsequent plans for the same product and material and integrate the furnace according to the date; S1096, if the furnace is still not integrated and the production scheduling configuration [Whether the material can be replaced during the furnace integration] is yes, search for the subsequent planned replaceable materials in order by date for furnace integration; S1097: If the furnace is still not repaired and the [Minimum furnace start-up package] is not reached, it is marked as not meeting the minimum furnace start-up package, saved and stored, and deleted from the production data to be scheduled; S1098, write the processed data into the context productOrder.

8. The method for scheduling smelting and pouring with multiple constraints according to claim 2, characterized in that: The S110, component NodeCapacity scheduling capacity calculation component specifically includes: S1101, obtaining the production data to be scheduled from the context productOrder; S1102, obtaining a factory calendar from a cache; S1103, match the factory calendar by date, if it matches, calculate the capacity, mark it as capacity met, if it does not meet, match the factory calendar of the next day, until the end of the factory calendar, if it still does not match, mark it as capacity cannot be met, save it into the warehouse, and delete it from the data to be scheduled; S1104, write the processed data into the context productOrder.

9. The method for scheduling smelting and pouring with multiple constraints according to claim 1, characterized in that: The S3 cache data includes: S301, product files, cached in the form of key-value, where key is the product material code and value is the product information; S302, smelting furnace information, cached in the form of key-value, the key is the production line plus the sequence number, the value is the equipment code plus the equipment name; S303, confirmed plan, cached in key-value format, key is product material code, value is confirmed number; S304, the shipped data is cached in the form of key-value, where the key is the product material code and the value is the shipment quantity; S305, finished product inventory data, cached in the form of key-value, where the key is the product material code and the value is the finished product inventory number; S306, outsourcing inventory data is cached in the form of key-value, where the key is the product material code and the value is the outsourcing inventory quantity; S307, WIP order data is cached in the form of key-value, where the key is the product material code and the value is the number of WIP; S308, factory calendar, load the factory calendar to calculate the daily working hours and cache them in the form of key-value, where the key is the production line plus the date, and the value is a map object, including the start time, end time, and working hours; S309, insulation zone, simulates caching of static pressure line insulation zone, caches in the form of key-value, key is date plus insulation zone track number, value is current insulation quantity; S310, the production data to be scheduled is loaded with the delivery order and cached in the form of key-value, where the key is the production line plus the date and the value is the production order set; S311, production scheduling configuration data, load the production scheduling configuration data, cache in the form of key-value, including: scheduling start date, key is schedulingStartDate, value is date type; whether the furnace can replace the material, key is materialReplaceFlag, value is Boolean type; minimum furnace opening bag, key is pouringMinBag, value is integer type; horizontal line, vertical line, static pressure line melting time, key is the production line abbreviation plus PouringTime, value is integer type; horizontal line, vertical line, static pressure line melting furnace maximum parallel number, key is the production line abbreviation plus PouringNum, value is integer type.

10. The method for scheduling smelting and pouring with multiple constraints according to claim 1, characterized in that: The S4 production scheduling includes: S401, production scheduling configuration, including: factory calendar, product priority, product substitution material, horizontal line\vertical line\static line melting time, horizontal line\vertical line\static line pouring time, horizontal line\vertical line\static line parallel furnace number, minimum furnace opening package; S402, select a scheduling rule, which is a scheduling rule configured for S3 cache data; S403, production scheduling result analysis, analyzing the production scheduling results and adjusting the production scheduling errors caused by production scheduling configuration errors and basic data errors; S404, production scheduling lock, fine-tune the production scheduling results by date, lock them after confirmation, and support locking plans for the next 7 days.

Images