Django-based manufacturing pfema management system

Abstract

The application is suitable for the field of digital calculation management technology improvement, and provides a manufacturing PFMEA management system based on Django, which comprises an engine module and a whole vehicle module.The engine module is used for recording data information of each component of the engine and storing the data information in data, and generating a data index to form a one-to-one mapping relationship with the number of each engine.The whole vehicle module is used for recording feature data information of related components of the whole vehicle and generating index information to be stored in a database, and forming a one-to-one mapping relationship between the indexed whole vehicle data information and the frame number.The old table data can be quickly and batch imported, and manual input time and effort are avoided.

Description

TECHNICAL FIELD

[0001] The application belongs to the field of digital computing management technology improvement, and particularly relates to a manufacturing PFMEA management system based on Django. BACKGROUND

[0002] At present, the PFMEA (Potential Failure Mode and Effects Analysis) is an English abbreviation of potential failure mode and effects analysis, is an analysis technology mainly used by cross-functional teams to maximize the consideration and discussion of potential failure modes and their related causes / mechanisms. The application of PFMEA in engine factories, cylinder blocks, cylinder heads, crankshafts and assembly is currently limited to the form of Excel table. The use of severity (S), frequency (O), detection (D) and risk priority number (RPN) risk priority level (RPL) in PFMEA still adopts manual analysis input, and is reviewed regularly through paper files. The FMEA management software on the market is mainly developed for DPFMA and SFMEA, and there are few similar software related to PFMEA, and it is difficult to start, which is difficult to meet the actual needs of SGMW. SUMMARY

[0003] The application aims to provide a manufacturing PFMEA management system based on Django, which aims to solve the above technical problems.

[0004] The application is implemented as follows: a manufacturing PFMEA management system based on Django, which comprises an engine module and a whole vehicle module. The engine module is used for recording data information of each component of the engine and storing the data information in data, and generating a one-to-one mapping relationship between the data index and the engine number. The whole vehicle module is used for recording characteristic data information of related components of the whole vehicle and generating index information stored in a database, and forming a one-to-one mapping relationship between the indexed whole vehicle data information and the frame number.

[0005] The further technical scheme of the present application is that the engine module comprises a cylinder body unit, a cylinder cover unit, a crankshaft unit and an assembly unit, the cylinder body unit is used for recording all data information about the cylinder body from the manufacturing of the cylinder body of the engine to the completion of the vehicle assembly and the test result, the cylinder cover unit is used for recording all data information about the cylinder cover from the manufacturing of the cylinder cover of the engine to the completion of the vehicle assembly and the test result, the crankshaft unit is used for recording all data information about the crankshaft from the manufacturing of the crankshaft of the engine to the completion of the vehicle assembly and the test result, and the assembly unit is used for recording all data information in the assembly process of the engine.

[0006] The further technical scheme of the present application is that the vehicle module comprises a stamping unit, a vehicle body unit, a coating unit and a general assembly unit, the stamping unit is used for recording the stamping process and stamping data of each component in the vehicle assembly, and the data of each component is stored in correspondence with the index for subsequent query, the vehicle body unit is used for recording the data and detection data in the manufacturing process of the vehicle body for subsequent query, the coating unit is used for recording the coating data information of the vehicle, and the general assembly unit is used for recording the data, detection data and test data in the assembly of the vehicle.

[0007] The further technical scheme of the present application is that the PFMEA subunit, the PFMEA review subunit and the PFMEA change subunit are arranged in each unit, the PFMEA subunit is used for electronic management of PFMEA, the PFMEA review subunit is used for review of PFMEA by a team, and the PFMEA change subunit is used for control of the process of PFMEA change.

[0008] The further technical scheme of the present application is that the PFMEA subunit is divided into N12, N15, changelogN12, changelogN15, severity (S), frequency (O), detection (D), risk level matrix, TOP5 and RPL=1 subitems, the N12 and N15 subitems are used for query and display of PFMEA information of N12 and N15 models, the changelogN12 and changelogN15 subitems are used for query of change records of corresponding models, and the severity (S) subitem is used for display and query of a PFMEA severity level table.

[0009] A further technical solution of the present application is that the frequency (O) sub-item is used for querying PFMEA frequency level information; the detection degree (D) sub-item is used for querying PFMEA detection degree level information; the risk level matrix sub-item is used for querying PFMEA risk level matrix diagram information; the TOP5 sub-item is used for querying PFMEA data table TOP5 information and automatic screening of front problems; and the RPL=1 sub-item is used for querying PFMEA data table RPL=1 information and automatic screening of key attention problems.

[0010] A further technical solution of the present application is that the PFMEA review sub-unit is used for team review of PFMEA, which is divided into a newly created review list sub-item, an initiated list sub-item, a flow monitoring sub-item, a to-do list sub-item and an already done list archiving sub-item, the newly created review list sub-item is used for filling in review information by an operator; and the initiated list sub-item is used for viewing an initiated review list list item.

[0011] A further technical solution of the present application is that the flow monitoring sub-item is used for viewing a flow progress of a current initiated process; the to-do list sub-item is used for viewing a current process to be processed; and the already done list archiving sub-item is used for viewing a process form that has been archived and historical archiving query.

[0012] A further technical solution of the present application is that the PFMEA change sub-unit is used for controlling a process of PFMEA change, which is divided into an initiation process item, an initiated list item, a flow monitoring item, a to-do list item and an already done list archiving item, the initiation process item is used for clicking to enter a next level interface of the system; and the initiated list item is used for displaying a change process list list item that has been initiated.

[0013] A further technical solution of the present application is that the flow monitoring item is used for displaying a flow progress of a current change process; the to-do list item is used for viewing a process form that needs to be processed currently; and the already done list archiving item is used for viewing a process form that has been archived.

[0014] An advantageous effect of the present application is that old table data can be quickly and batch imported and migrated, manual input time and effort are avoided, a single region needs to be manually input for one week in a traditional way, all input needs to be performed for one month, and the automatic batch import function can be used to complete the input in less than 1 minute, thereby greatly improving work efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0015] Figure 1 is a block diagram of a manufacturing PFMEA management system based on Django provided by an embodiment of the present application.

[0016] Figure 2 is a principle schematic diagram of a Model layer and a Template.

[0017] Figure 3 is a schematic diagram of a login interface of an entering system provided by an embodiment of the present application.

[0018] Figure 4 is a schematic diagram of a main interface after login of the system provided by an embodiment of the present application.

[0019] Figure 5 is a schematic diagram of a PFMEA module provided by an embodiment of the present application.

[0020] Figure 6 is a schematic diagram of the PFMEA module after entering provided by an embodiment of the present application.

[0021] Figure 7 is a schematic diagram of the changelogN12 and changelogN15 submodules after entering provided by an embodiment of the present application.

[0022] Figure 8 is a schematic diagram of the severity (S) submodule after entering provided by an embodiment of the present application.

[0023] Figure 9 is a schematic diagram of the frequency (O) submodule after entering provided by an embodiment of the present application.

[0024] Figure 10 is a schematic diagram of the detectability (D) submodule after entering provided by an embodiment of the present application.

[0025] Figure 11 is a schematic diagram of the risk rating matrix submodule after entering provided by an embodiment of the present application.

[0026] Figure 12 is a schematic diagram of the TOP5 submodule after entering provided by an embodiment of the present application.

[0027] Figure 13 is a schematic diagram of the RPL=1 submodule after entering provided by an embodiment of the present application.

[0028] Figure 14 is a schematic diagram of the newly created review list after entering provided by an embodiment of the present application.

[0029] Figure 15 is a schematic diagram of the list item of the review list initiated by viewing provided by an embodiment of the present application.

[0030] Figure 16 is a schematic diagram of the progress of the current initiated process provided by an embodiment of the present application.

[0031] Figure 17 is a schematic diagram of the current to-be-processed process provided by an embodiment of the present application.

[0032] Figure 18 is a schematic view of a post-archived process form review entry provided by an embodiment of the present application.

[0033] Figure 19 is a schematic view of a post-initiation process button entry into the system interface provided by a PFMEA change module of an embodiment of the present application.

[0034] Figure 20 is a schematic view of a post-flow transfer monitoring display of the current change process flow progress interface provided by an embodiment of the present application. DETAILED DESCRIPTION

[0035] As shown in Figure 1 the present application provides a Django-based manufacturing PFMEA management system, which comprises an engine module and a whole vehicle module. The engine module is used for recording data information of each component of the engine and storing the data information in data, and generating a data index to form a one-to-one mapping relationship with the number of each engine. The whole vehicle module is used for recording feature data information of related components of the whole vehicle and generating index information to be stored in a database, and forming a one-to-one mapping relationship between the indexed whole vehicle data information and the frame number.

[0036] The engine module comprises a cylinder block unit, a cylinder head unit, a crankshaft unit and an assembly unit. The cylinder block unit is used for recording all data information about the cylinder block from the manufacturing of the cylinder block of the engine to the completion of the whole vehicle equipment and the test result. The cylinder head unit is used for recording all data information about the cylinder head from the manufacturing of the cylinder head of the engine to the completion of the whole vehicle equipment and the test result. The crankshaft unit is used for recording all data information about the crankshaft from the manufacturing of the crankshaft of the engine to the completion of the whole vehicle equipment and the test result. The assembly unit is used for recording all data information in the assembly process of the engine.

[0037] The whole vehicle module comprises a stamping unit, a vehicle body unit, a coating unit and a general assembly unit. The stamping unit is used for recording the stamping process and stamping data of each component in the whole vehicle assembly, and storing the data of each component for subsequent query by corresponding index mapping. The vehicle body unit is used for recording data and detection data in the manufacturing process of the vehicle body for subsequent query. The coating unit is used for recording coating data information of the whole vehicle. The general assembly unit is used for recording data, detection data and test data in the assembly of the whole vehicle.

[0038] In each unit, PFMEA subunit, PFMEA review subunit and PFMEA change subunit are arranged, the PFMEA subunit is used for electronic management of PFMEA; the PFMEA review subunit is used for team review of PFMEA; and the PFMEA change subunit is used for controlling the process of PFMEA change.

[0039] The PFMEA subunit is divided into N12, N15, changelogN12, changelogN15, severity (S), frequency (O), detection (D), risk level matrix, TOP5 and RPL=1 subitems; the N12 and N15 subitems are used for querying and displaying PFMEA information of N12 and N15 models; the changelogN12 and changelogN15 subitems are used for querying change records of corresponding models; and the severity (S) subitem is used for displaying and querying PFMEA severity level table.

[0040] The frequency (O) subitem is used for querying PFMEA frequency level information; the detection (D) subitem is used for querying PFMEA detection level information; the risk level matrix subitem is used for querying PFMEA risk level matrix information; the TOP5 subitem is used for querying PFMEA data table TOP5 information and automatic screening of front problems; the function of automatically screening front problems of the TOP5 module mainly uses the sorting algorithm of RPN value, and the main logic is that the back-end function first sorts the RPN value of each PFMEA record through the ORM in the Django framework of python, then extracts the data corresponding to the top five largest RPN values into a list, and then extracts the corresponding PFMEA record items according to the list and stores them in the TOP5 special PFMEA database table. After the front-end initiates a TOP5 data request, the topcreate function of the back-end is executed and the result is returned to the front-end interface for display. Clicking the interface enters the following interface; and the RPL=1 subitem is used for querying PFMEA data table RPL=1 information and automatic screening of key attention problems.

[0041] The PFMEA review subunit is used for team review of PFMEA, which is divided into new review list subitem, initiated list subitem, flow monitoring subitem, to-do list subitem and done list archiving subitem; the new review list subitem is used for filling review information by an operator; and the initiated list subitem is used for viewing the initiated review list items.

[0042] The flow transfer monitoring sub-item is used to view the transfer progress of the current initiated process; the to-do list sub-item is used to view the current to-be-processed process; and the completed list archiving sub-item is used to view the archived process forms and historical archiving query.

[0043] The PFMEA change sub-unit is used to control the PFMEA change process, which is divided into an initiated process item, an initiated list item, a flow transfer monitoring item, a to-do list item and a completed list archiving item. The initiated process item is used to click into the next interface of the system; and the initiated list item is used to display the initiated change process list.

[0044] The flow transfer monitoring item is used to display the transfer progress of the current change process; the to-do list item is used to view the current process form to be processed; and the completed list archiving item is used to view the archived process form.

[0045] Under the background of the digital wave of intelligent manufacturing, combined with the actual situation of the engine factory, the PFMEA management system is built by using the popular python language at present. The system includes a server and a client, adopts a B / S architecture, the server adopts a Django framework, and the client adopts HTML, CSS and Javascripts technology.

[0046] The system adopts the following technical solutions: through web technology development, the limitation of excel form is completely eliminated, so as to realize automatic screening of previous problems; through the django.core.mail module of the Djnago framework, the function of automatic reminding and pushing of email is realized; through python and Mysql database technology, the process node information is stored in the database in time, and the review process is realized; based on web development programming, new functions can be flexibly expanded;

[0047] Through the ORM (Object-Relational Mapping) technology of Django, the database can be directly operated by using the code, so as to realize efficient screening of data, and the xlrd library of python is used to realize automatic generation and export of excel electronic documents;

[0048] Based on the layui front-end visualization framework, HTML5, CSS and other web technologies are used to realize the uniformity of system document format, simplicity and lightness, and avoid the problem of opening lag;

[0049] After the browser inputs the system service website, the login interface is entered, as shown in Figure 3 .

[0050] I. After inputting the account and password, click the login button to enter the system main interface, as shown in Figure 4As shown, the main interface is divided into two first-level modules, with the left side being the engine module and the right side being the vehicle module. The engine module is divided into four second-level modules, namely the cylinder block, cylinder head, crankshaft, and assembly modules. The vehicle module is divided into four second-level modules, namely the stamping, body, painting, and assembly modules:

[0051] Upon entering each second-level module, it is further divided into multiple third-level modules, which are PFMEA modules, such as Figure 5 As shown, PFMEA review module, and PFMEA change module.

[0052] PFMEA module: The PFMEA module is mainly for electronic management of PFMEA. Upon clicking into PFMEA, it is divided into N12, N15, changelogN12, changelogN15, severity (S), frequency (O), detection (D), risk level matrix, TOP5, and RPL = 1 sub-modules, as shown below. Figure 6

[0053] ① N12 and N15 sub-modules are mainly used to query and display PFMEA information for N12 and N15 models. Upon clicking into the interface, it is as follows:

[0054] ② changelogN12 and changelogN15 sub-modules are mainly used to query change records for corresponding models. Upon clicking into the interface, it is as shown below: Figure 7

[0055] ③ Severity (S) sub-module is mainly used to display and query PFMEA severity level table. Upon entering the interface, it is as shown below: Figure 8

[0056] ④ Frequency (O) sub-module is mainly used to query PFMEA frequency level information. Upon entering the interface, it is as shown below: Figure 9

[0057] ⑤ Detection (D) sub-module is mainly used to query PFMEA detection level information. Upon entering the interface, it is as shown below: Figure 10

[0058] ⑥ Risk level matrix sub-module is mainly used to query PFMEA risk level matrix information. Upon entering the interface, it is as shown below: Figure 11

[0059] ⑦ TOP5 sub-module is mainly used to query PFMEA data table TOP5 information, which is used for automatic screening of front-end problems. The function of automatically screening front-end problems in the TOP5 module is mainly achieved by using the sorting algorithm for RPN values. The main logic is that the back-end function first sorts each

[0060] ​​​​​​The RPN value of the PFMEA record is sorted by the ORM in the Python Django framework, and the data corresponding to the top 5 largest RPN values is extracted and placed in a list. Then, the corresponding PFMEA record is extracted and stored in the TOP5 special PFMEA database table according to the list. After the front-end initiates a TOP5 data request, the topcreate function in the back-end is executed and the result is returned to the front-end interface for display. Clicking on the interface, as shown in Figure 12 ;

[0061] The RPL=1 sub-module is mainly used to query the RPL=1 information of the PFMEA data table, and is used for automatic screening of key attention issues. Clicking on the interface, as shown in Figure 13 ;

[0062] PFMEA review module: The PFMEA review module is mainly used for the team to review the PFMEA. The module is divided into sub-function modules such as new review list, initiated list, flow monitoring, to-do list, and handled list archiving.

[0063] When the new review list is clicked, the new review list interface is entered, as shown in Figure 14 , where the operator fills in the review information, and then the review list is automatically transferred to the next regional node;

[0064] Clicking on the initiated list can view the list of initiated review lists, as shown in Figure 15 ;

[0065] Clicking on the flow monitoring can view the flow progress of the current initiated process, as shown in Figure 16 ;

[0066] Clicking on the to-do list can view the current to-do process, as shown in Figure 17 ;

[0067] Clicking on the handled list archiving can view the archived process form, which is used for historical archiving query. The interface after entering is shown in Figure 18 ;

[0068] PFMEA change module: The PFMEA change module is mainly used for controlling the process of PFMEA changes. The PFMEA change module is divided into sub-function items such as initiation process, initiated list, flow monitoring, to-do list, and handled list archiving. Clicking on the initiation process button under the PFMEA change module enters the system interface, as shown in Figure 19 ;

[0069] Clicking on the initiated list displays the initiated change process list;

[0070] Clicking the flow transfer monitoring shows the current change flow transfer progress, the interface is shown in Figure 20 ;

[0071] Clicking the to-do list button can view the process form that needs to be processed currently;

[0072] Clicking the to-do list button can view the process form that needs to be processed currently;

[0073] PFMEA report module is mainly used for PFMEA process information report display, which is divided into engine factory and whole vehicle factory overall state information, engine factory and whole vehicle factory TOP5 information display, engine and whole vehicle factory monthly RPL trend information display and RPL state information display, engine and whole vehicle PFMEA review according to plan execution statistical information display.

[0074] The chart display of PFMEA report module adopts Echarts chart, which is a JavaScript-based open source visualization chart library. All data is grabbed from the database data by Django-ORM and then returned to the front end for display. Email reminder function: after the initiator initiates the PFMEA review process, the process participants in the acceptance area are reminded by email; improve work efficiency: when the new system is enabled, old table data can be quickly imported and migrated in batches, avoiding time-consuming and laborious manual entry. Traditional manual entry of a single area takes one week, and all entries take up to a month. Using the automatic batch import function, it can be completed in less than 1 minute, greatly improving work efficiency; one-key export sharing: review forms and PFMEA forms can be exported one by one, which is convenient for printing and sharing; easy to maintain: the system is based on Django framework, easy to maintain, strong scalability, and the front-end interface based on Layui is elegant and atmospheric, and easy to operate; save development cost: use open source technology for independent development, compared with outsourcing to external suppliers, it is expected to save 500,000 yuan in cost.

[0075] In manufacturing industry, it often involves complex process flow, each link of which has a deep or shallow impact on the final product. For the impact of each factor, forward-looking preventive analysis can effectively analyze potential risks and reduce failure rate. To achieve this process, PFEMA management system is independently developed and has been deployed and implemented. Web technology is used for management, which can effectively improve work efficiency and manage PFEMA information efficiently.

[0076] The main principle of the technology is to use the current mainstream Python language for backend development, which uses the mainstream web framework of Python-Django, which is based on the MVT mode.

[0077] The MVT mode of Django is inspired by the classic MVC mode (i.e. data model layer, view layer, control layer), which also divides the interaction process into three levels; Model: data storage layer, handles all data-related business, interacts with the database, and provides data addition, deletion, modification, and query; Template: template layer (also called presentation layer) specifically handles page display; View: business logic layer, handles specific business logic, its role is to connect the Model layer and the Template; The principle diagram is as Figure 2 shown;

[0078] This patent is based on open source tools, by writing front and back-end code, when the user accesses the system deployed server IP address through the browser, you can enter the login page, when the input username password can access the system function; After entering the system, select the area where the user is located, you can view the PFMEA information of the current area, you can also add, delete, update, export and a series of functions. When the user can review the page of the system, submit the review form, that is, through the HTTP protocol to initiate a request request, the server will respond to the request request, that is, to execute the view layer function, and return the result to the front end.

[0079] After the system is deployed, it replaces the original paper process, solves the industry pain points of low efficiency of the original paper process mode, cumbersome information query of excel table, and inability to automatically screen previous problems, effectively accelerates the digital transformation of the company.

[0080] Previous TOP problem automatic screening: can automatically screen out previous problems, replace traditional manual screening; Information automatic promotion reminder: according to the actual situation, you can set up regular push reminders for relevant persons to review PFMEA; Automatic flow monitoring: review workflow, avoid missing intermediate process, flow state can be monitored in real time; The system can be flexibly expanded: the development process reserves API interface to realize the expansion function; Form one-key export: replace traditional manual screening, realize automatic screening of the data you want, one-key export to table file for sharing and printing; Traditional PFMEA file automatic batch import: the system can directly read the original table file to realize one-key import of table data; Permission management is controllable: through the admin administrator module, the back-end realizes the permission management of regional managers, avoids data loss and tampering caused by accidental deletion and misoperation.

[0081] The above merely describes preferred embodiments of the present application, and is not used to limit the present application, any modification, equivalent replacement and improvement within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A Django-based manufacturing PFMEA management system, characterized by, The Django-based manufacturing PFMEA management system comprises an engine module and a whole vehicle module, the engine module is used for recording data information of each component of the engine and storing the data information in data, and generating a data index to form a one-to-one mapping relationship with the number of each engine; the whole vehicle module is used for recording feature data information of related components of the whole vehicle and generating index information to be stored in a database, and forming a one-to-one mapping relationship between the indexed whole vehicle data information and the frame number; The engine module comprises a cylinder block unit, a cylinder head unit, a crankshaft unit and an assembly unit, the cylinder block unit is used for recording all data information about the cylinder block of the engine from manufacturing to completion of whole vehicle equipment and test results; the cylinder head unit is used for recording all data information about the cylinder head of the engine from manufacturing to completion of whole vehicle equipment and test results; the crankshaft unit is used for recording all data information about the crankshaft of the engine from manufacturing to completion of whole vehicle equipment and test results; and the assembly unit is used for recording all data information of the engine during assembly. The whole vehicle module comprises a stamping unit, a vehicle body unit, a coating unit and a general assembly unit, the stamping unit is used for recording stamping processes and stamping data of each component during whole vehicle assembly, and storing the data of each component for subsequent query by corresponding index mapping; the vehicle body unit is used for recording data and detection data during manufacturing of the vehicle body for subsequent query; the coating unit is used for recording data information of the whole vehicle during coating; and the general assembly unit is used for recording data, detection data and test data of the whole vehicle during assembly.

2. The Django-based manufacturing PFMEA management system of claim 1, wherein, PFMEA subunits, PFMEA review subunits and PFMEA change subunits are arranged in each unit, the PFMEA subunits are used for electronic management of PFMEA; the PFMEA review subunits are used for review of PFMEA by a team; and the PFMEA change subunits are used for controlling the process of PFMEA change.

3. The Django-based manufacturing PFMEA management system of claim 2, wherein, The PFMEA subunits are divided into N12, N15, changelogN12, changelogN15, severity (S), frequency (O), detection (D), risk level matrix, TOP5 and RPL=1 subitems; the N12 and N15 subitems are used for querying and displaying PFMEA information of N12 and N15 models; the changelogN12 and changelogN15 subitems are used for querying change records of corresponding models; and the severity (S) subitem is used for displaying and querying a PFMEA severity level table.

4. The Django-based manufacturing PFMEA management system of claim 3, wherein, The frequency (O) sub-item is used to query PFMEA frequency level information; the detection degree (D) sub-item is used to query PFMEA detection degree level information; the risk level matrix sub-item is used to query PFMEA risk level matrix diagram information; the TOP5 sub-item is used to query PFMEA data table TOP5 information and automatic screening of front position problems; and the RPL=1 sub-item is used to query PFMEA data table RPL=1 information and automatic screening of key attention problems.

5. The Django-based manufacturing PFMEA management system of claim 4, wherein, The PFMEA review sub-unit is used for team review of PFMEA, which is divided into a newly created review list sub-item, an initiated list sub-item, a flow monitoring sub-item, a to-do list sub-item and an already done list archiving sub-item, the newly created review list sub-item is used for an operator to fill in review information here; The initiated list sub-item is used to view an initiated review list item.

6. The Django-based manufacturing PFMEA management system of claim 5, wherein, The flow monitoring sub-item is used to view the flow progress of a current initiated process; the to-do list sub-item is used to view a current process to be processed; and the already done list archiving sub-item is used to view a process form that has been archived and historical archiving query.

7. The Django-based manufacturing PFMEA management system of claim 6, wherein, The PFMEA change sub-unit is used to control a process of PFMEA change, which is divided into an initiation process item, an initiated list item, a flow monitoring item, a to-do list item and an already done list archiving item, the initiation process item is used to click to enter a next level interface of the system; The initiated list item is used to display an initiated change process list.

8. The Django-based manufacturing PFMEA management system method of claim 7, wherein, The flow monitoring item is used to display the flow progress of a current change process; the to-do list item is used to view a process form that needs to be processed currently; and the already done list archiving item is used to view a process form that has been archived.

Images