Vehicle exhaust system technology management system and method

Abstract

This invention discloses a vehicle exhaust system technical management system and method. The system adopts a web-based architecture, including a user interface layer, a business logic layer, and a data access layer. The business logic layer integrates three main modules: pre-design research, development phase assurance, and after-sales maintenance. Each module is further subdivided into sub-modules for managing knowledge in specific domains. Through this unified platform, centralized storage, classified management, and related sharing of technical knowledge throughout the entire lifecycle of the exhaust system are achieved. This allows for the systematic accumulation and continuation of technical knowledge, effectively solving the problems of knowledge dispersion, easy loss, and difficulty in sharing and analysis in traditional management, and improving the systematic nature and collaborative efficiency of technical management.

Description

Technical Field

[0001] This invention belongs to the field of automotive technical maintenance and management technology. Specifically, this invention relates to a vehicle exhaust system technical management system and method. Background Technology

[0002] With the continuous advancement of commercial vehicle technology and increasingly stringent environmental regulations worldwide, exhaust system aftertreatment technologies are constantly being updated and iterated, making the corresponding product development and design processes increasingly complex. Against this backdrop, in order to achieve efficient and compliant product development, enterprises have an increasingly urgent need for systematic, end-to-end management of exhaust system technology.

[0003] Currently, the management of technical data and knowledge related to exhaust systems within the industry is generally fragmented. Different departments, projects, or personnel often rely on their own accumulated or locally available information for querying and application when carrying out related work, lacking a unified and integrated technical management platform.

[0004] Furthermore, the existing management model has significant shortcomings in terms of systemicity and comprehensiveness: First, there is a disconnect between technology development and cost control, and a lack of a mechanism to link design decisions with economic benefits in real time; second, there is insufficient benchmarking analysis and research on internal and external technical solutions, making it difficult to support scientific decision-making; third, there is a lack of integrated tools for analyzing and solving quality problems, resulting in weak quality control capabilities; and fourth, the tracking and response to cutting-edge technology developments in the industry is lagging behind, which restricts the improvement of technological innovation capabilities.

[0005] This invention provides a vehicle exhaust system technology management system and method, particularly regarding how to integrate knowledge management of vehicle exhaust system technology to achieve knowledge management throughout the entire lifecycle of the vehicle exhaust system. Summary of the Invention

[0006] This invention aims to at least solve one of the technical problems existing in the prior art. To this end, this invention provides a vehicle exhaust system technology management system and method, with the purpose of integrating knowledge management of vehicle exhaust system technology to achieve knowledge management throughout the entire lifecycle of the vehicle exhaust system.

[0007] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is: a vehicle exhaust system technical management system, which adopts a Web-based architecture and includes: The user interface layer is used to provide the user interaction interface; The business logic layer is used to implement knowledge management logic for the entire lifecycle of the vehicle exhaust system. It integrates a pre-design research module, a development phase assurance module, and an after-sales maintenance module; and... The data access layer is used to interact with the database, store and retrieve data related to exhaust system technology knowledge; The pre-design research module, the development phase assurance module, and the after-sales maintenance module each include several sub-modules for managing knowledge specific to the exhaust system.

[0008] The business logic layer also includes a host management module and a backend management module. The host management module is used to manage the system's operating environment and configuration, while the backend management module is used to manage user permissions and system basic data.

[0009] The pre-design research module includes: exhaust system design standards sub-module, component design requirements sub-module, exhaust system best practices and lessons learned sub-module, and technology dynamics sub-module; The development phase assurance module includes: an exhaust system component management submodule, an exhaust system and sub-component benchmarking study submodule, and an exhaust system DFMEA submodule; The after-sales maintenance module includes: an exhaust system fault management submodule and a problem analysis and troubleshooting tool submodule.

[0010] The exhaust system fault management submodule stores fault data categorized by the fault occurrence stage, which includes the manufacturing stage, testing stage, and after-sales stage, and also stores corresponding solution data. The analysis and problem-solving tools submodule integrates data models or application interfaces for various quality analysis tools.

[0011] The exhaust system component management submodule stores material information and corresponding cost data for exhaust system components. The exhaust system design standards submodule stores exhaust system design specification data corresponding to different emission regulation versions.

[0012] The technology dynamics submodule stores information on technological developments and regulatory updates related to exhaust systems.

[0013] The present invention also provides a vehicle exhaust system technology management method, applied to the aforementioned vehicle exhaust system technology management system, the method comprising: Receive user operation commands through the user interface layer; Based on the user's operation instructions, the business logic layer calls the data access layer to retrieve the corresponding exhaust system technical knowledge data from the database, or writes updated exhaust system technical knowledge data to the database. The processing logic of the business logic layer covers the entire lifecycle knowledge management process, including pre-design research, development phase assurance, and after-sales maintenance, and classifies and manages knowledge data in specific fields through corresponding sub-modules.

[0014] Before receiving user operation instructions through the user interface layer, a user permission verification step is also included: Receive access requests initiated by users through the user interface layer; The system determines whether the user is authorized to access the requested resource based on preset permission rules. If authorized, access is allowed and subsequent steps can be performed; if not authorized, access is denied.

[0015] The method also includes a fault data management step: The exhaust system fault management submodule receives and stores fault records identified by fault stage type, including manufacturing stage faults, testing stage faults, and after-sales stage faults, and stores corresponding solutions.

[0016] The method also includes a cost data association step: The exhaust system component management submodule associates and stores and manages component information, material information, and cost data.

[0017] This invention's vehicle exhaust system technology management system comprehensively covers the entire chain of exhaust system technology activities, from regulatory research and design development to after-sales feedback, through three major modules: pre-design research, development phase assurance, and after-sales maintenance. Data and knowledge generated at each stage can seamlessly flow and be linked within a unified platform, centrally stored in the system's database, and managed by structured functional modules. This allows the company's core technical knowledge to be independent of specific personnel, forming organizational assets. Even with personnel turnover, relevant knowledge can be fully preserved and continued. This integrated knowledge management system for vehicle exhaust system technology achieves knowledge management throughout the entire lifecycle of the vehicle exhaust system. Attached Figure Description

[0018] Figure 1 This is an architecture diagram of the vehicle exhaust system technical management system of the present invention. Detailed Implementation

[0019] To facilitate understanding of the present invention, a more comprehensive description of the present invention will be given below with reference to the accompanying drawings, which illustrate several embodiments of the present invention. However, the present invention can be implemented in different forms and is not limited to the embodiments described in the text. Rather, these embodiments are provided to make the disclosure of the present invention more thorough and complete.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly associated with those skilled in the art to which this invention pertains. The terminology used herein in the specification of this invention is for the purpose of describing particular embodiments and is not intended to limit the invention. The term "and / or" as used herein includes any and all combinations of one or more of the associated listed items.

[0021] Firstly, such as Figure 1 As shown, this embodiment of the invention provides a vehicle exhaust system technology management system, which adopts a web-based architecture and includes: The user interface layer is used to provide the user interaction interface; The business logic layer is used to implement knowledge management logic for the entire lifecycle of the vehicle exhaust system. It integrates a pre-design research module, a development phase assurance module, and an after-sales maintenance module; and... The data access layer is used to interact with the database, store and retrieve data related to exhaust system technology knowledge; The pre-design research module, the development phase assurance module, and the after-sales maintenance module each include several sub-modules for managing knowledge specific to the exhaust system.

[0022] Specifically, in this embodiment of the invention, the vehicle exhaust system technology management system integrates knowledge management of exhaust system technology, enabling knowledge management throughout the entire lifecycle of the exhaust system. This vehicle exhaust system technology management system achieves knowledge sharing of exhaust system technology, thereby eliminating knowledge barriers within a company. The system's access control settings facilitate knowledge maintenance and management. The system allows for functions such as adding, deleting, uploading, and downloading, providing easy operation and human-computer interaction. Users can also update relevant knowledge content within this tool.

[0023] This invention provides an exhaust system technology management system, constructing an integrated management platform for technical knowledge specifically designed for the development of commercial vehicle exhaust systems. Through the combined application of specific software technology stacks and the structured design of business logic, this system achieves unified support and management of technical activities at each stage of the exhaust system's entire lifecycle. The system uses a web service built on the Django framework as its core application carrier. This framework provides a stable infrastructure for the system's development and deployment. The preferred development environment is PyCharm, and the database uses MySQL for relational data storage, which can be efficiently managed and maintained using database management tools such as Navicat Premium.

[0024] like Figure 1 As shown, the management system comprises four main components: a web service based on the Django framework, a database, a user access control module, and a knowledge management module covering the entire lifecycle of the commercial vehicle exhaust system. The web service, built on the Django framework, forms the core of the system's application and employs a layered design, specifically including a user interface layer, a business logic layer, and a data access layer.

[0025] The user interface layer is mainly used to provide a user interaction interface, receive user commands, and display data.

[0026] The business logic layer is mainly used to implement all the business rules and business processes of the system. The logic of user permission management and knowledge management of the entire life cycle of commercial vehicle exhaust system are implemented in this layer.

[0027] The data access layer is mainly used to encapsulate all operations on the database and realize data interaction between the business logic layer and the database.

[0028] The preferred database is MySQL relational database, used for persistent storage of all knowledge data in the system. The user access management module is integrated into the business logic layer and is responsible for authenticating and authorizing user access requests.

[0029] In this embodiment of the invention, the business logic layer integrates a pre-design research module, a development phase assurance module, an after-sales maintenance module, a host management module, and a backend management module. The host management module is used to manage the system's operating environment and configuration, while the backend management module is used to manage user permissions and basic system data.

[0030] The pre-design research module is used for technical input and research management in the early stages of product development. Furthermore, the pre-design research module includes several sub-modules, such as... Figure 1 As shown, the pre-design research module includes: exhaust system design standards sub-module, component design requirements sub-module, exhaust system best practices and lessons learned sub-module, and technology dynamics sub-module.

[0031] The exhaust system design standards submodule manages design specifications and regulatory requirements, storing exhaust system design specification data corresponding to different emission regulation versions. Specifically, this submodule centrally manages mandatory design specifications and general technical requirements under different regulatory systems. Its database establishes a design specification library indexed by emission regulation version (e.g., China V, China VI) and applicable region (e.g., specific overseas markets). Users can search for specific regulatory entries through the navigation area and view or edit the corresponding detailed technical requirements through the form area, ensuring that the design complies with regulatory constraints from the outset.

[0032] The Component Design Requirements submodule stores specific design knowledge for components, including design specifications for each sub-part of the vehicle exhaust system. Specifically, this submodule stores and manages detailed design rules, parameter ranges, performance indicators, and other proprietary technical knowledge for key components of the exhaust system (including but not limited to exhaust pipes, bellows, mufflers, brackets, clamps, and exhaust tailpipes). Given that its content involves core design know-how, this submodule implements independent and stricter access control. Its interface also provides navigation, operation, and data editing areas for authorized users to maintain and query these key design bases.

[0033] The Exhaust System Best Practices and Lessons Learned (BP&LL) submodule is used to accumulate and reuse development experience. Specifically, this submodule is used to structure and archive successful design schemes, optimized process routes, proven solutions (Best Practice), and problems encountered, failure cases, and root causes (Lessons Learned) accumulated during the development of historical projects. This function aims to promote the accumulation and reuse of experience and knowledge, and avoid repeating mistakes. Access to this data is also subject to access control.

[0034] The Technology Dynamics submodule tracks cutting-edge technological developments in the industry, storing information on exhaust system-related technological advancements and regulatory updates, including technological innovations in exhaust systems. Specifically, this submodule tracks, collects, and organizes the latest technological developments, new material applications, new processes, and updates and forecasts of regulations and standards in major global markets related to exhaust systems. This information is then pushed to the platform to provide information support for technology planning and preliminary research.

[0035] The development phase assurance module is used for technical collaboration and quality control during the detailed design and verification phases of the product. Furthermore, the development phase assurance module comprises several sub-modules, such as... Figure 1 As shown, the development phase assurance modules include: exhaust system component management submodule, exhaust system and sub-component benchmarking study submodule, and exhaust system DFMEA submodule.

[0036] The exhaust system component management submodule is used for the associated management of materials, resources, and costs, storing material information and corresponding cost data for exhaust system components. Specifically, the main function of this submodule is to achieve the associated management of the technical and commercial attributes of components. For each component, the system not only records its basic information such as its number and name, but also associates it with its optional materials (such as stainless steel 201, 304, Q355, 510L, etc.) and corresponding material costs (e.g., in yuan / kilogram). Users can edit or query the material options and cost details of a specific part through the form area, thus allowing for simultaneous cost consideration during design and selection.

[0037] The exhaust system DFMEA submodule is used to perform design potential failure analysis. Specifically, the exhaust system DFMEA submodule integrates the digital management functions of Failure Mode and Effects Analysis (DFMEA) to systematically identify, assess and prioritize potential failure risks in the exhaust system and its sub-components in the design, and record corresponding prevention and detection measures.

[0038] The Exhaust System and Sub-component Benchmarking Study submodule manages competitive product or technology analysis data. Specifically, it manages benchmarking analysis data related to competing products or advanced technological solutions. It not only stores system-wide benchmark information but also focuses on detailed benchmarking data for common high-failure-rate or high-performance-difference components such as mufflers and catalytic converters, providing a reference for design optimization and target setting. The Technology Updates submodule and the Benchmarking Study submodule together build a capability for capturing and analyzing information on the external technological environment and competitive landscape. The former focuses on trends and future regulations, while the latter focuses on the current state of competing products. Their combination provides comprehensive information support for technological innovation and product planning, helping to overcome the weakness of lagging technological developments and proactively guiding innovation.

[0039] The after-sales maintenance module is used for quality feedback and closed-loop management of issues after a product is launched on the market. Furthermore, the after-sales maintenance module includes several sub-modules, such as... Figure 1 As shown, the after-sales maintenance module includes: an exhaust system fault management submodule and a problem analysis and troubleshooting tool submodule.

[0040] The exhaust system fault management submodule stores fault data categorized by the fault occurrence stage, including the manufacturing, testing, and after-sales stages, and associates it with corresponding solution data. Specifically, the exhaust system fault management submodule constructs a fault information management system covering the entire product lifecycle. It strictly categorizes faults into manufacturing faults, testing faults, and after-sales faults, recording them accordingly. For each fault case, it meticulously records the phenomena, cause analysis, short-term containment measures, and long-term solutions (including both short-term and long-term measures). Furthermore, the module pre-installs a standardized fault terminology library, covering various damage-related fault modes, degradation-related fault modes, loosening-related fault modes, misalignment-related fault modes, blockage and penetration-related fault modes, performance degradation or functional failure-related fault modes, etc., to standardize fault descriptions and improve data consistency and analyzability. This page is divided into a navigation area, a button area, and a form area; the form area is editable.

[0041] The Analysis and Problem Solving Tools submodule integrates data models and application interfaces for various quality analysis tools. Specifically, it integrates several commonly used quality engineering and problem analysis methodologies, such as the 5W2H analysis method, the SCQA structured expression model (Scenario-Conflict-Problem-Answer), causal chain analysis, the 8D problem-solving method, QFD (Quality Function Deployment), and error-proofing design principles. This module aims to provide engineers with standardized methodological support and process guidance for analyzing failures, locating root causes, and developing effective corrective actions. The Analysis and Problem Solving Tools submodule explicitly and structurally integrates various quality analysis methods that previously relied on personal experience, transforming them into standardized process tools. This reduces over-reliance on personal experience, improves the standardization, systematicity, and efficiency of team analysis and problem-solving of complex technical issues, and effectively strengthens quality management capabilities.

[0042] The vehicle exhaust system technology management system described in the above embodiment integrates knowledge management of vehicle exhaust system technology, enabling knowledge management throughout the entire lifecycle of the vehicle exhaust system. This system achieves knowledge sharing of exhaust system technology, thereby eliminating knowledge barriers within enterprises. The vehicle exhaust system technology management system has access control settings, which facilitates knowledge maintenance and management. The system allows for adding, deleting, uploading, and downloading functions, providing easy operation and human-computer interaction. Users of the system can also update relevant knowledge content within the tool.

[0043] Secondly, embodiments of the present invention also provide a vehicle exhaust system technology management method, applied to the vehicle exhaust system technology management system of the foregoing embodiments, the method comprising: Receive user operation commands through the user interface layer; Based on user operation instructions, the business logic layer calls the data access layer to retrieve the corresponding exhaust system technical knowledge data from the database, or writes updated exhaust system technical knowledge data to the database. The business logic layer's processing logic covers the entire lifecycle knowledge management process, from pre-design research and development phase assurance to after-sales maintenance, and classifies and manages knowledge data in specific domains through corresponding sub-modules.

[0044] Before receiving user operation instructions through the user interface layer, a user permission verification step is also included: Receive access requests initiated by users through the user interface layer; Determine whether a user is authorized to access the requested resource based on preset permission rules; If authorized, access is allowed and subsequent steps can be performed; if not authorized, access is denied.

[0045] When a user initiates an access request through the system's user interface layer, the user access management module intervenes first, authenticating the user's identity and the resources they are requesting to access based on a pre-defined access rule base. Only after successful authentication is the user allowed to enter the corresponding functional module to perform operations; otherwise, access is denied. This step ensures the security of core technologies and data assets.

[0046] After authorized access, the user inputs operation commands (such as query, add, or modify) through the user interface layer. The business logic layer receives the command, parses its corresponding business rules, and then calls the data access layer to execute the specific operation on the database. After completing the interaction with the database, the data access layer processes the results through the business logic layer and then feeds them back to the user interface layer for display. This process is the foundation for the implementation of all sub-module functions.

[0047] The vehicle exhaust system technical management method of this invention also includes a fault data management step: The exhaust system fault management submodule receives and stores fault records with fault stage types identified, including manufacturing stage faults, testing stage faults, and after-sales stage faults, and associates and stores corresponding solutions.

[0048] Specifically, the exhaust system fault management submodule receives fault reports from users. These reports must identify the stage at which the fault occurred, categorized into three main types: manufacturing stage faults, testing stage faults, and after-sales stage faults. The system forcibly associates fault records with corresponding solutions (typically including short-term containment measures and long-term fundamental solutions). This means that each fault record points to its corresponding solution entry at the database level, ensuring complete traceability of the problem from record to closure.

[0049] The vehicle exhaust system technical management method of this invention also includes a cost data association step: The exhaust system component management submodule links and stores and manages component information, material information, and cost data.

[0050] Specifically, in the exhaust system component management submodule, when a user creates or maintains data for a component (such as an exhaust pipe), the system guides or requires the user to simultaneously maintain the component's optional material information (such as stainless steel 304) and its corresponding material cost data (such as unit price in yuan / kg).

[0051] The system establishes a mapping between the three fields of "component identification," "material specifications," and "cost data" in the database and stores them uniformly. This allows for the immediate acquisition and evaluation of the cost impact of different material options during the design and selection process.

[0052] In this embodiment of the invention, key management activities (such as the requirement that fault records be phased and associated with specific measures; and the requirement that component data be associated with costs) are solidified into mandatory logical processes executed by the system. This overcomes the problems of arbitrary process execution and non-standard data recording in traditional manual management, ensuring the consistency of management actions and the structure of data, and laying a reliable foundation for subsequent data analysis.

[0053] The fault data management process, through mandatory "fault-response" correlation storage, ensures at the methodological level that every quality issue entered into the system must have a corresponding solution record, forming a built-in digital closed loop from problem identification and analysis to solution. Combined with stage-based classification, it can effectively trace the root cause of the problem to whether it is in the manufacturing, testing, or design stage, greatly improving the efficiency of quality backtracking and analysis.

[0054] Furthermore, the established cost data association management process seamlessly integrates cost considerations into the technical design activities. When engineers design or select components through the system, the process requires them to simultaneously maintain and associate cost information. This ensures that cost factors become real-time input parameters for technical decisions from the design stage, effectively solving the long-standing problem of the disconnect between technical development and cost control. Example

[0055] The vehicle exhaust system technical management system of this embodiment can be deployed on a general-purpose computer device. This computer device acts as the execution entity, responsible for running the backend services written in the Python programming language. The system development and deployment are preferably based on the Django web application framework. During deployment, the Python runtime environment and corresponding environment variables need to be configured on the computer device, and a MySQL database system needs to be installed for persistent data storage. For ease of database management and operation, relevant database management tools can be used. Development can be carried out in an integrated development environment (IDE), and an independent virtual environment can be created within the project to install and run the necessary third-party dependency libraries, such as drivers for database connections and libraries for image processing.

[0056] By executing the database migration commands provided by the Django framework, the corresponding table structures for each system module can be generated in the configured MySQL database. After completing the above configuration, running the project will start the web service, and users can access the system through the corresponding HTTP page in a browser.

[0057] The user access and control process is as follows: Users first access the system's project homepage. The homepage provides login and registration entry points. The login process implements strict identity verification, including password verification and image CAPTCHA verification, to ensure access security. Only after successful verification can users enter the system's main interface.

[0058] User permissions within the system are centrally managed by the administrator through integrated user management functions. Administrators have the authority to add, edit, and delete user accounts, and to assign different operational permissions to different users. Specifically, for specific modules storing core knowledge (know-how) within the system, independent and more stringent access control is implemented. In this embodiment, typically only the administrator account with the admin privileges possesses the highest level of management authority in the system.

[0059] The interface and data structure of the functional modules are described below: The system main interface is presented as follows Figure 1 The architecture shown divides the business logic layer into three main functional modules: "Pre-design Research," "Development Phase Assurance," and "After-sales Maintenance." The user interfaces of each functional module and its sub-modules all use a consistent interaction logic layout, typically including a navigation area (for function and data categorization navigation), a button area (for performing operations such as add, delete, modify, query, and submit), and a form area (for displaying and editing structured data). The form area supports authorized users to enter and modify data.

[0060] The following provides a detailed explanation of the specific data content of each submodule: 1. Pre-design research module: Exhaust System Design Standards Submodule: This submodule integrates a database of exhaust system design specifications for different emission regulations and regional requirements, such as the "China V", "China VI" and various "overseas projects" specific design specifications.

[0061] Component Design Requirements Submodule: This submodule integrates detailed design specifications and requirements for various specific components of the exhaust system (such as exhaust pipes, bellows, mufflers, muffler brackets, muffler bands, V-clamps, exhaust tailpipes, etc.).

[0062] Exhaust System Best Practices and Lessons Learned Submodule: This submodule is used to integrate and manage successful practices and lessons learned from past development projects.

[0063] Technology Updates Submodule: This submodule is used to integrate information on technological innovations and regulatory updates within the industry.

[0064] 2. Modules guaranteed during the development phase: Exhaust System Component Management Submodule: This submodule is used to integrate component information and cost data management. In the database, for components such as exhaust pipes, bellows, and mufflers, the available materials (such as stainless steel 201, stainless steel 304, steel Q355, 510L, etc.) and the corresponding material cost data (the cost unit can be recorded as yuan / kilogram) are recorded respectively.

[0065] Exhaust System and Sub-component Benchmarking Study Sub-module: This sub-module integrates benchmark analysis data on competing products or technical solutions, especially detailed benchmarking information for whole vehicle projects and commonly faulty components.

[0066] Exhaust System DFMEA Submodule: This submodule integrates the design failure mode and effects analysis data of the exhaust system.

[0067] 3. After-sales maintenance module: Exhaust System Fault Management Submodule: This submodule integrates fault data and solutions occurring at each stage of product manufacturing, testing, and after-sales service. Faults are categorized and recorded, such as manufacturing faults, testing faults, and after-sales faults. For each fault record, detailed solutions are provided, including short-term containment measures and long-term radical solutions. Simultaneously, this module pre-installs a standardized fault terminology library, covering various fault modes such as damage, degradation, loosening, misalignment, blockage and leakage, performance degradation, or functional failure.

[0068] Analysis and Problem Solving Tools Submodule: This submodule integrates a variety of structured quality analysis tools and methodologies, such as 5W2H analysis, SCQA framework, cause-effect chain analysis, 8D method, quality function deployment, and error-proofing design principles, providing standardized support for problem analysis.

[0069] This embodiment proposes a management system and method for commercial vehicle exhaust systems, with a computer device as the execution entity. The computer device uses the Django framework in PyCharm to deploy Django data on a server. The specific implementation process is as follows: S1. First, install Python on your computer and set the appropriate environment variables.

[0070] S2, install MySQL+Navicat on the computer device, and select the correct configuration type and connection port.

[0071] S3, install PyCharm on the computer device.

[0072] S4. Open the project corresponding to this invention in PyCharm, create the corresponding virtual environment, and install the corresponding third-party libraries, such as paho-mqtt, pillow, pymysql, etc.

[0073] S5. Configure the corresponding runtime files and modify the database configuration. Then, use the database migration commands provided by the Django framework to execute python manage.py makemigrations and python manage.pymigrate in sequence to complete the generation and initialization of the database structure.

[0074] S6 runs the Python project and can access the corresponding HTTP page, which is the homepage of this application.

[0075] S7, the homepage of this invention project, in addition to the title "A Management System for Vehicle Exhaust System Technology", also includes information such as login and registration. Login requires a password and image verification. Only those who meet the login requirements can enter the system. Administrators can add, edit and delete users, and manage users through the Django framework.

[0076] S8. After meeting the login requirements, you can enter the main page of the project content of this application, as shown in the attached figure. It is the knowledge management of the entire life cycle of commercial vehicle exhaust system, including modules such as pre-design research, design improvement, and post-design changes.

[0077] S9, the pre-design research module in this invention includes a sub-module of exhaust system design standards (including regulatory requirements), a sub-module of component design requirements, a sub-module of best practices (BP) for exhaust systems, a sub-module of Lessons-Learn (LL) for exhaust systems, and a sub-module of new technology developments; this page is divided into a navigation area, a button area, and a form area, and the form area is editable.

[0078] S10, the development phase guarantee module in this invention includes a sub-module for exhaust system component management (including material and cost management), a sub-module for benchmarking study of exhaust system and sub-components, and a sub-module for exhaust system DFMEA; this page is divided into a navigation area, a button area, and a form area, and the form area is editable.

[0079] S11, the after-sales maintenance module in this invention includes a sub-module for analyzing and solving problems and a sub-module for exhaust system fault management.

[0080] S12, in which the exhaust system components (including material and cost management) module integrates the input and cost management of exhaust system components. It is subdivided according to the components, including exhaust pipe, bellows, muffler, muffler bracket, muffler band, V-clamp, exhaust tailpipe, etc. The cost corresponds to the corresponding part and its material, such as stainless steel 201, stainless steel 304, steel Q355, 510L, etc., and is calculated in yuan / kg. This page is divided into a navigation area, a button area and a form area, and the form area is editable.

[0081] S13, in which the exhaust system design standards (including regulatory requirements) module integrates the current exhaust system design specifications, namely the exhaust system design specifications for China V, China VI and overseas projects; this page is divided into a navigation area, a button area and a form area, and the form area is editable.

[0082] S14, in which the component design requirements module integrates the design specifications for various components (exhaust pipe, bellows, muffler, muffler bracket, muffler band, V-clamp, exhaust tailpipe), this part is the know-how item, and permissions are set separately; this page is divided into a navigation area, a button area and a form area, and the form area is editable.

[0083] S15, in which the exhaust system fault management module integrates exhaust system fault situations and solutions during the development and after-sales stages. Faults are divided into BIR (manufacturing fault), TIR (testing fault), and FIR (after-sales fault), recording exhaust system fault situations during the manufacturing, testing, and after-sales stages respectively; and providing detailed corresponding solutions (including short-term and long-term measures); and providing commonly used fault terms, namely various damage-type fault modes, degradation-type fault modes, loosening-type fault modes, misalignment-type fault modes, blockage and penetration-type fault modes, performance degradation or functional failure-type fault modes, etc.; this page is divided into a navigation area, a button area, and a form area, and the form area is editable.

[0084] S16, in which the analysis and problem-solving tools module integrates quality analysis tools, including the 5W2H analysis method, SCQA framework (scenario-conflict-problem-answer), cause-effect chain analysis, 8D method, QFD (Quality Function Deployment), and error-proofing design, etc.; this page is divided into a navigation area, a button area, and a form area, and the form area is editable.

[0085] S17, in which the exhaust system DFMEA module integrates the exhaust system DMEA.

[0086] S18, in which the exhaust system and sub-component benchmarking study module integrates relevant benchmark information, especially the benchmarking analysis of the main project and the benchmarking analysis of common faulty components; this page is divided into a navigation area, a button area and a form area, and the form area is editable.

[0087] S19, in which the Exhaust System Best Practices (BP) & Lesson-Learn (LL) submodule integrates the best practices and lessons learned in exhaust system development. This part of the data is development know-how, and this page also has separate permissions. This page is divided into a navigation area, a button area and a form area, and the form area is editable.

[0088] S20, the Technology Dynamics module integrates information on technological innovations and regulatory updates related to exhaust systems; this page is divided into a navigation area, a button area, and a form area, with the form area being editable.

[0089] The present invention has been described above by way of example with reference to the accompanying drawings. Obviously, the specific implementation of the present invention is not limited to the above-described manner. Any non-substantial improvements made using the inventive concept and technical solution of the present invention, or the direct application of the inventive concept and technical solution of the present invention to other occasions without modification, are all within the protection scope of the present invention.

Claims

1. A vehicle exhaust system technical management system, characterized in that, The system adopts a web-based architecture, including: The user interface layer is used to provide the user interaction interface; The business logic layer is used to implement knowledge management logic for the entire lifecycle of the vehicle exhaust system. It integrates a pre-design research module, a development phase assurance module, and an after-sales maintenance module; and... The data access layer is used to interact with the database, store and retrieve data related to exhaust system technology knowledge; The pre-design research module, the development phase assurance module, and the after-sales maintenance module each include several sub-modules for managing knowledge specific to the exhaust system.

2. The system according to claim 1, characterized in that, The business logic layer also includes a host management module and a backend management module. The host management module is used to manage the system's operating environment and configuration, while the backend management module is used to manage user permissions and system basic data.

3. The system according to claim 1 or 2, characterized in that, The pre-design research module includes: exhaust system design standards sub-module, component design requirements sub-module, exhaust system best practices and lessons learned sub-module, and technology dynamics sub-module; The development phase assurance module includes: an exhaust system component management submodule, an exhaust system and sub-component benchmarking study submodule, and an exhaust system DFMEA submodule; The after-sales maintenance module includes: an exhaust system fault management submodule and a problem analysis and troubleshooting tool submodule.

4. The system according to claim 3, characterized in that, The exhaust system fault management submodule stores fault data categorized by the fault occurrence stage, which includes the manufacturing stage, testing stage, and after-sales stage, and also stores corresponding solution data. The analysis and problem-solving tools submodule integrates data models or application interfaces for various quality analysis tools.

5. The system according to claim 3, characterized in that, The exhaust system component management submodule stores material information and corresponding cost data for exhaust system components. The exhaust system design standards submodule stores exhaust system design specification data corresponding to different versions of emission regulations.

6. The system according to claim 3, characterized in that, The technology dynamics submodule stores information on technological developments and regulatory updates related to exhaust systems.

7. A vehicle exhaust system technical management method, applied to the system as described in any one of claims 1-6, characterized in that, The method includes: Receive user operation instructions through the user interface layer; According to the user's operation instructions, the business logic layer calls the data access layer to retrieve the corresponding exhaust system technical knowledge data from the database, or writes updated exhaust system technical knowledge data to the database. The processing logic of the business logic layer covers the entire lifecycle knowledge management process, including pre-design research, development phase assurance, and after-sales maintenance, and classifies and manages knowledge data in specific fields through corresponding sub-modules.

8. The method according to claim 7, characterized in that, Before receiving user operation instructions through the user interface layer, a user permission verification step is also included: Receive access requests initiated by users through the user interface layer; The system determines whether the user is authorized to access the requested resource based on preset permission rules. If authorized, access is permitted and subsequent steps can be performed; Access is denied if not authorized.

9. The method according to claim 7, characterized in that, The method also includes a fault data management step: The exhaust system fault management submodule receives and stores fault records identified by fault stage type, including manufacturing stage faults, testing stage faults, and after-sales stage faults, and associates and stores corresponding solutions.

10. The method according to claim 7, characterized in that, The method also includes a cost data association step: The exhaust system component management submodule associates and stores and manages component information, material information, and cost data.

Images