[0043] The principles and features of the present invention will be described below with reference to the accompanying drawings. The examples cited are only used to explain the present invention, and are not used to limit the scope of the present invention.
[0044] Such as figure 1 As shown, it is a manufacturing execution method of the aviation MRO industry according to a specific embodiment of the present invention, which specifically includes the following steps:
[0045] Step 1: Receive a user request and corresponding user information;
[0046] Step 2: Compare the user request with the historical information in the database to determine whether there is a user request corresponding to the user request in the historical information, if yes, go to step 3; otherwise, go to step 4;
[0047] Step 3: Call the short-term plan corresponding to the user request in the historical information, and perform step 15;
[0048] Step 4: Determine whether there is corresponding user information in the database, if yes, go to step 6; otherwise, go to step 5;
[0049] Step 5: Create a user information table in the database to save user information, and assign corresponding level information to the user information;
[0050] Step 6: Call the user information stored in the database to obtain the level information in the user information;
[0051] Step 7: Determine whether the level information is important, if it is, configure high priority based on user information, and go to step 8; otherwise, configure low priority based on user information and go to step 9;
[0052] Step 8: Determine whether the current configuration resource meets the requirements of the user request, if not, feedback the user request, and update the configuration resource according to the user request, and go to step 10; if it is satisfied, go to step 10 directly;
[0053] Step 9: Determine whether the current configuration resource meets the requirements of the user request, if yes, go to step 10; otherwise, the feedback cannot be completed information, end;
[0054] Step 10: Generate mid- and long-term plans according to user requests, and perform step 11;
[0055] Step 11: Determine whether the scheduled execution time is reached, if yes, go to step 13; otherwise, go to step 12;
[0056] Step 12: Release the currently occupied configuration resources, and execute step 11 regularly;
[0057] Step 13: Generate a short-term plan, detect the current configuration resources, and allocate the current configuration resources according to the current short-term plan;
[0058] Step 14: Execute the short-term plan, complete the short-term plan, collect relevant information during the execution of the short-term plan and user request to generate historical information, and save the historical information in the database.
[0059] The configuration resources include maintenance equipment, operators, and material equipment.
[0060] The level information includes important and common.
[0061] The user’s level information is allocated according to the user importance algorithm. The user importance algorithm judges whether it is an important customer based on the user’s reputation, the user’s habits and whether it is a major customer, such as paying on time and delivering maintenance equipment on time as an important customer; and often Cancel demand, often change demand to ordinary customers; while large customers are handled as important customers.
[0062] Such as figure 2 As shown, it is an aerospace MRO industry manufacturing execution system according to a specific embodiment of the present invention, including a receiving module 1, a judgment module 2, a grade judgment module 3, a request judgment module 4, a resource judgment module 5, and an execution module 6;
[0063] The receiving module 1 is used to receive a user request and corresponding user information;
[0064] The judgment module 2 is used to judge whether there is corresponding user information in the database. If so, call the user information stored in the database to obtain the level information in the user information; otherwise, create a user information table in the database to save the user information, and Assign corresponding level information to user information;
[0065] The level judgment module 3 is used to judge whether the level information is important, if so, configure a high priority according to user information, and trigger the request judgment module 4; otherwise, configure a low priority according to user information to trigger the resource judgment module 5;
[0066] The request judging module 4 is used to judge whether the current configuration resources meet the requirements of the user request, if so, generate a medium and long-term plan according to the user request, and trigger the execution module 6; otherwise, feed back the user request and update the configuration resource according to the user request;
[0067] The resource judgment module 5 judges whether the currently configured resource meets the requirements of the user request, and if so, generates a mid- and long-term plan according to the user request; otherwise, it feedbacks that the information cannot be completed and ends;
[0068] The execution module 6 is used to generate a short-term plan, allocate current configuration resources according to the current short-term plan, execute the short-term plan, and complete the short-term plan; collect relevant information during the execution of the short-term plan and user requests to generate historical information, and save the historical information to In the database.
[0069] The execution module 6 includes a time judgment module 61, a short-term planning module 62, and a short-term execution module 63;
[0070] The time judgment module 61 is used to judge whether the timing reaches the scheduled execution time, and if so, trigger the short-term planning module 62; otherwise, release the currently occupied configuration resources;
[0071] The short-term plan module 62 is used to generate a short-term plan, detect currently configured resources, and allocate the currently configured resources according to the current short-term plan;
[0072] The short-term execution module 63 is used to execute the short-term plan, complete the short-term plan, collect relevant information during the execution of the short-term plan and user request to generate historical information, and save the historical information in the database.
[0073] The receiving module 1 includes a request receiving module 11, a comparison and judgment module 12, and a history calling module 13;
[0074] The request receiving module 11 is configured to receive a user request and corresponding user information;
[0075] The comparison judgment module 12 compares the user request with the historical information in the database, and judges whether there is a user request corresponding to the user request in the historical information, and if so, triggers the history calling module 13; otherwise, triggers the judgment module 2;
[0076] The historical calling module 13 is used to call the short-term plan corresponding to the user request in the historical information to trigger the execution module.
[0077] The configuration resources include maintenance equipment, operators, and material equipment.
[0078] The level information includes important and common.
[0079] The user’s level information is allocated according to the user importance algorithm. The user importance algorithm judges whether it is an important customer based on the user’s reputation, the user’s habits and whether it is a major customer, such as paying on time and delivering maintenance equipment on time as an important customer; and often Cancel demand, often change demand to ordinary customers; while large customers are handled as important customers.
[0080] The following is the overall process when the present invention is specifically implemented.
[0081] 1. Maintenance requirements/intentions:
[0082] 1.1 Maintenance intention: The maintenance intention is the customer's idea of maintenance, but it has not yet determined whether the demand will be implemented and the execution time.
[0083] After pre-registration and resource scheduling, the maintenance intention enters the MMS long-term plan. The MMS decision reminder will check the status of the plan, remind the customer whether they are sure to implement the plan, and deal with it accordingly (if the customer decides not to execute the plan, the plan is ended, if the customer thinks that there is a change in maintenance requirements, such as time and maintenance items, the system Registration and resource scheduling will be performed again. If the customer confirms the implementation, the plan will enter the short-term planning stage.
[0084] 1.2 Maintenance requirements: Maintenance requirements are actual needs put forward by customers, that is, to start maintenance of a certain equipment/machine at a certain time, and propose a maintenance list and time requirements.
[0085] Maintenance requirements directly enter the system's mid-term planning range. Once the customer confirms the implementation, the requirements enter the short-term planning stage.
[0086] 2. Pre-registration:
[0087] The user enters user information, demand information, etc. into the system for registration. After analyzing the importance of users, the feasibility of requirements, and the cost-effectiveness of the project, enter the resource schedule for analysis.
[0088] User information determines the importance of the user. The demand information determines the feasibility of execution. Determine the cost performance after comprehensive analysis of requirements.
[0089] User importance algorithm (user’s reputation, user habits, such as whether to pay on time, whether to deliver maintenance equipment on time, whether to cancel demand (often), whether to change demand (often), whether it is a major customer, etc.).
[0090] Cost-effective algorithm (complexity of demand, whether new demand, whether there is similar demand in the past, current resource situation, future resource situation, future demand situation, quotation situation of the other party, etc.).
[0091] 3. Resource scheduling:
[0092] Resource scheduling maintains resource information, and provides models of manpower, materials, equipment, and process methods for strategic decision-making or overall planning by simulating the resource occupancy under different maintenance schedules. The specific resource scheduling process is as follows image 3 Shown.
[0093] (1) Staff qualification:
[0094] The employee-role (skill) correspondence relationship. An employee can correspond to multiple roles. For example, Zhang San can be a welder or a painter. Li Si has a maintenance license for Boeing 747 and 737, but he does not have a maintenance license for Boeing 767 and other Boeing models, nor does he have a maintenance license for Airbus.
[0095] (2) Enterprise maintenance history:
[0096] The maintenance history (experience) of the same demand for the same machinery and equipment of the enterprise can be used as a reference and reference for this demand.
[0097] The repair history of different needs of the same equipment by the enterprise.
[0098] The company’s similar repair history to other equipment.
[0099] If it is exactly the same or similar requirements, it has great reference value in resource allocation and quotation. If it is a different requirement, it can also be handled based on past experience and similar maintenance history of other machinery and equipment.
[0100] (3) Machine and equipment maintenance history:
[0101] In addition to the maintenance history of the machine in this company in (2), the maintenance history of the machine in other companies is also included as a reference for this maintenance.
[0102] (4) Material situation:
[0103] According to the maintenance list provided, material resources need to be drawn up and prepared, and a material preparation list is provided.
[0104] The material situation needs to reflect the material supplier, market price and inventory situation. To prepare for short-term planning of purchases. Materials can be stocked according to prices and related conditions, or purchased in real time. Real-time purchases need to be reminded in advance when there is a possible shortage, so as not to affect the production plan.
[0105] (5) Tool situation:
[0106] Tool modeling needs to define and model the function and quantity of the tool. Certain competitive tools and resources need to be allocated reasonably to increase productivity.
[0107] (6) Process conditions:
[0108] Enterprise process modeling provides decision-making on the dispatch of different processes at different maintenance needs.
[0109] Patent point: Evaluation and assignment algorithm of man-machine material method.
[0110] Resource coordination process such as Figure 4 Shown.
[0111] 4. Medium and long-term plan:
[0112] Medium and long-term plans include:
[0113] 4.1. Intentional needs. The importance of this demand will gradually decrease over time, and the resources it occupies will be temporarily "borrowed" to the ongoing plan or the plan to be executed in the future to ensure the normal progress of other plans. At the same time, with the adjustment of resources in the intentional demand plan, the system will give the customer a decision reminder to remind the customer whether to continue to implement the plan, so as to plan future resources and plan implementation.
[0114] Patent point: Decision reminding algorithm for intentional demand.
[0115] 4.2. Substantive needs. When the demand is about to reach the start time point, the system decision reminder system will confirm to the user whether the change time is to execute the plan, usually one week, to remind the customer to prepare the machine and equipment for entry, the system prepares resources and enters the short-term planning stage.
[0116] 5. Short-term plan:
[0117] (1) Project/plan generation (project number, project name, person in charge, project content description, start time, deadline, project type, customer, project status, etc.)
[0118] The project is claimed by the project manager or planner, and the claim time is generally one week before the start of the project to prepare for the project.
[0119] (2) Work order formulation, detailed to each work (work), including work number, work description, stage, working time, type of work, project number, work status, etc.
[0120] The work is assigned by the project manager to the staff, who log in to the system by swiping the card, time, track the work, and end the work when it is completed.
[0121] Work consists of many states, and there is real-time tracking and processing in the actual scheduling process.
[0122] (3) Human resource preparation;
[0123] (4) Material resource preparation;
[0124] (5) Tool resource preparation.
[0125] Human, material and tool resources are allocated and prepared based on the results of resource scheduling.
[0126] 6. Plan to dispatch workers:
[0127] (1) The project manager appoints the project manager;
[0128] (2) The project manager claims the project.
[0129] Relevant authority check, whether the project manager can assign the project, and whether the project manager has the authority to claim the project.
[0130] Qualification check, whether the project manager has the management qualification of the project.
[0131] 7. Plan execution:
[0132] Patent point: the timing algorithm of multi-player and multi-card.
[0133] 8. On-site scheduling:
[0134] On-site scheduling includes:
[0135] (1) Manage and process work orders through data collection;
[0136] (2) Apply, assign, use, and return the required tools according to the site conditions;
[0137] (3) Apply, distribute, use and return the required spare parts according to the site conditions;
[0138] (4) Real-time reporting of work progress (including timing);
[0139] (5) Kanban management, real-time task viewing;
[0140] (6) Work card collection, sorting, data collection and batch processing of work cards after the site.
[0141] 9. Data collection:
[0142] (1) Equipment data collection. Perform data collection on the company's equipment, check whether the equipment is in normal operation, and monitor the equipment to ensure normal maintenance;
[0143] (2) Work card data collection. Collect the data of the work card to track and process the work card to ensure the normal and orderly completion of the work.
[0144] 10. Work order status: status decision algorithm.
[0145] 11. Tool management: Tool management includes the purchase, application, lease, maintenance, return, and scrapping of tools. The tool form includes fields such as tool type, storage time, storage location, status, etc.
[0146] Patent point: tool tracking method.
[0147] 12. Spare parts management: Spare parts include the management of the purchase, storage and delivery of basic materials and vulnerable materials required for maintenance. The form includes material type, quantity, inventory address, storage time, etc.
[0148] 13. Unconventional plan:
[0149] In the on-site scheduling process, there are the following situations that require special consideration:
[0150] (1) User changes requirements;
[0151] (2) Users add new demands;
[0152] (3) The user cancels the demand.
[0153] The above demand changes in the on-site scheduling process are all unconventional plans, and these plans need to be executed to enter the on-site scheduling. Unconventional plans require additional plan formulation, preparation and addition to the work card list, and enter the plan execution module after dispatch, and perform scheduling and execution according to the plan.
[0154] Patent point: Stage time modification algorithm, relative time concept.
[0155] 14. The plan is completed: the plan needs to be completed,
[0156] (1) Collect work card information;
[0157] (2) Generate relevant reports;
[0158] (3) Feedback to customers;
[0159] (4) The project manager closes the project.
[0160] 15. Data archiving:
[0161] (1) Backup and archive all project data;
[0162] (2) Generate project historical experience records;
[0163] (3) Data analysis.
[0164] 16. Decision analysis:
[0165] 16.1 Customer analysis:
[0166] Factors affecting customer importance include customer popularity, customer market share, customer payment quantity (per order), customer payment habits, and customer contact difficulty.
[0167] A certain mathematical modeling is used to form a customer’s importance analysis chart so that customer-related decisions can be provided during each demand analysis.
[0168] 16.2 Persons, machines, materials and methods:
[0169] Modeling of manpower, machinery, material resources, and technology provides feasibility decisions for whether requirements can be completed, provides decision-making models for cost-effective analysis, and provides planning support for short-term plans.
[0170] 16.3 Decisions to convert mid- and long-term plans to short-term plans:
[0171] The medium and long-term plan decides the future situation of the plan according to the plan type, the nature of the customer, and the time characteristics, and reminds the customer whether to implement it or decides the execution time of the plan to the short-term plan.
[0172] 16.4 On-site scheduling status decision:
[0173] The status of various work cards in the on-site scheduling needs to be analyzed to determine the processing methods (reporting, waiting) of the work cards in this state.
[0174] 16.5 On-site dispatching algorithm:
[0175] Reasonably arrange human and material resources, optimize human and material resources, and complete various tasks with maximum efficiency and optimization in quality and quantity.
[0176] 16.6 On-site scheduling time adjustment algorithm:
[0177] Project-> Stage-> Work;
[0178] Relative time, and modification of relative time;
[0179] The project time is modified and assigned to the stage and work card through a weighted algorithm.
[0180] 16.7 On-site scheduling multi-person multi-card time algorithm:
[0181] One card can be completed by multiple people;
[0182] One person can make multiple cards;
[0183] The algorithm of each person's working time on each card, and the algorithm of each card's time allocation for each person.
[0184] 16.8 Kanban management:
[0185] Project status, progress; work card status, progress; report; real-time push.
[0186] 17. Business Intelligence:
[0187] 17.1 Tool tracking algorithm:
[0188] According to the data collector on the tool, analyze the flow trajectory of the tool, optimize the tracking tool, and ensure the loan and return of the tool.
[0189] 17.2 Warehouse Modeling (3D):
[0190] Warehouse 3D modeling to ensure maximum introduction of machines;
[0191] The machine is modeled to determine whether the warehouse can accommodate the machine.
[0192] 17.3 Customer information mining: mining customer habits and behaviors to provide better services.
[0193] 17.4 Resource scheduling mining: mining people, machines, materials and methods to maximize the efficiency of resource use and increase productivity.
[0194] 18. Basic platform: OS-like support platform (resource management, process management, communication management, file management, configuration management).
[0195] 19. Customer feedback: see customer feedback flowchart Figure 5.
[0196] 3A+M monitoring system architecture (Admin, Audit, Application+Monitor), three-power separation system monitoring, to ensure safe and efficient operation.
[0197] The above descriptions are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection of the present invention. Within range.
