Operation model of complex product multi-specialty collaborative research and development process
Through structured processing and activity pool hierarchical architecture, the problems of rigid R&D processes and inflexible capacity allocation are solved, and flexible configuration and automatic matching of processes and capabilities are achieved, which improves the flexibility and efficiency of the R&D process.
Patent Information
- Application Number
- CN202411033413.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-30
- Publication Date
- 2024-11-15
AI Technical Summary
In the existing technology, the R&D process of complex products is rigid and cannot be flexibly adjusted, and the configuration of capability elements does not meet the needs of different types of products, resulting in the process being unable to effectively guide and constrain the R&D process.
By structured processing of product R&D processes, building an activity pool hierarchical structure, matching R&D activities with capability elements, forming a R&D activity capability unit, and achieving flexible configuration and automatic matching of processes and capabilities according to the target product cutting process, dynamically adjusting task execution .
It realizes the flexibility and flexible configuration of process capabilities, avoids process rigidity, improves the flexibility and efficiency of the R&D process, and ensures the reasonable configuration and execution of tasks.
Smart Images

Figure CN118966737A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of multi-discipline collaborative R&D of complex products, and in particular, relates to an operation model of a multi-discipline collaborative R&D process of complex products. Background Art
[0002] With the increasing emphasis on independent R&D capabilities for products with significant impacts, especially the R&D of technology-intensive products in the fields of aviation, aerospace, and automobiles, the traditional R&D model based on experience is gradually shifting to process-based, model-based, and information-based R&D. Therefore, many scientific research companies use the product R&D system as a carrier for the transformation of the R&D model and systematically carry out the construction of the product R&D system. Build a systematic R&D process, build business capability elements with the process as the core, and integrate the process and supporting capability elements into the information system. Relying on the operation of the information system, ensure that the product follows the prescribed process, calls the corresponding capability elements, completes product development, and plays a role in standardizing, constraining, and guiding the entire process of product development.
[0003] The R&D of many high-tech intensive products often involves multi-field and cross-professional collaboration, and involves a lot of iterations and repetitions. Therefore, how to effectively run the process to ensure the "rigidity" of product R&D, play a role in standardization, constraint, and guidance; and be relatively "flexible but not rigid", not restrict the thinking of R&D personnel, and promote rapid iteration of multiple disciplines, is the key issue in achieving the transformation of R&D model, and is also the core technology.
[0004] In the prior art, after the process is structured, the structured process and supporting capability documents and software tools are directly integrated into the information system. At the beginning of the project or task, the process to be executed is prefabricated, and the relevant requirements of the process activities are configured to form tasks and then assigned to task executors. The R&D team strictly executes according to the logic of the process, and the execution of the subsequent tasks can be triggered only after the completion of the preceding activities.
[0005] The disadvantages of the prior art are as follows:
[0006] 1. The process is rigid and not smooth, and the guidance for product development is insufficient
[0007] The research and development of high-tech intensive products, especially new products, is essentially a process of continuous exploration and collective wisdom. The research and development process often has only a top-level logical sequence, while the chronological order before and after the specific task level is not very strict. In many cases, multiple professionals work in parallel and iterate repeatedly to complete a certain task. It is also common for the research and development process of the same type of products to be different. Therefore, according to the existing technical solutions, product research and development should be carried out strictly in the chronological order specified by the process. On the one hand, a large number of adjustments to the logical order of the process are required for specific product research and development projects. At the same time, repeated adjustments will also occur during the operation of the process, resulting in the process failing to standardize, constrain, and guide product research and development.
[0008] 2. The configuration of processes and capability elements is not flexible, and there is a lack of necessary judgment process on whether the capability elements can meet the needs of activities.
[0009] In existing technical solutions, capability elements and process activities are "hard-linked" and integrated into the information system, and their configuration is often fixed. However, for different types of product research and development (such as different generations of aircraft engines; or military aircraft and civil aircraft), it is usually necessary to reconfigure the capability elements, and the existing technical solutions do not support this configuration; in addition, for different types of products, whether their capability elements can support the execution of response activities, the existing technical solutions also lack an effective evaluation process.
[0010] The above two issues affect the effectiveness of the process. Summary of the invention
[0011] The purpose of this application is to provide an operating model for the multi-disciplinary collaborative R&D process of complex products to solve the problems of rigid existing R&D processes and inflexible configuration of processes and capability elements.
[0012] The technical solution of this application is: an operation model of a multi-professional collaborative R&D process for complex products, including:
[0013] Obtain the product development process, structure the product development process, and obtain a typical process element model; the product development process includes a structured process and a textual process;
[0014] Extract various R&D activities in the product R&D process to form a product R&D activity list. Based on the product R&D activity list, build a hierarchical structure of activity pools for product R&D.
[0015] Associating R&D activities with the activity attribute matching capability elements in the basic database to form R&D activity capability units, and storing the R&D activity capability units in different hierarchical structures of the activity pool;
[0016] Tailor the structured process based on the specific target product to form a product-specific structured process customized based on the target product process;
[0017] Extract product-specific structured processes, match corresponding nodes and resource information, and form preliminary R&D tasks;
[0018] Configure the R&D activity capability units in the activity pool according to the preliminary R&D tasks, verify the matching degree between the R&D activity capability units and the task requirements in the preliminary R&D tasks, and if the matching degree meets the requirements, issue the formal task; if not, re-match until the requirements are met; issue a certain R&D task in the formal task to the task executor, and use the data in the activity pool to drive the task executor to perform the corresponding R&D task;
[0019] After the R&D task is completed, the task status is mapped back to the product-specific structured process to monitor the entire product development process until all R&D tasks are completed;
[0020] After completing all R&D tasks as required, they will be approved and stored in the activity pool as successful cases and corresponding R&D activity capability units.
[0021] Preferably, the product R&D activity list is divided into three levels: product physical object activity layer, professional activity layer, and personal activity layer; the product physical object activity layer is decomposed by corresponding mapping of each level of the product decomposition structure model to obtain the project R&D activities of the corresponding level; the professional activity layer further decomposes each project R&D activity to obtain R&D activities at each professional level, and the activity granularity of the R&D activities at the professional level is to the extent that they can be undertaken by a single profession; the personal activity layer is further decomposed by the R&D activities at each professional level to obtain personal R&D activities that can be undertaken by a single person.
[0022] Preferably, the R&D activity capability unit includes activity attributes, capability file attributes, external file attributes, software tool attributes, business role attributes and success case attributes.
[0023] Preferably, the specific method for tailoring the structured process is: obtaining all improvement information of the target product through a structured process or a textual process, determining the target attribute information corresponding to all the improvement information, and then replacing the corresponding attribute information of the previous generation product with the target attribute information.
[0024] Preferably, the specific method for obtaining the preliminary R&D tasks is: extract the product-specific structured process in step four, use the task logic in the process as a constraint, and based on a unified task model, match time, personnel, resources, risks and dynamic monitoring indicator information to form the preliminary R&D tasks of the target product.
[0025] Preferably, the preliminary R&D tasks are automatically matched with the R&D activity capability units through coding attributes, which include product category information, sub-category information, hierarchical object information in the product decomposition structure, hierarchical information of the corresponding process, hierarchical information in the activity pool, task name information and activity name information.
[0026] Preferably, the specific method of using data in the activity pool to drive the task executor to perform the corresponding R&D task is as follows: after a certain R&D task in the formal task is issued to the task executor, the task executor retrieves the corresponding R&D activity capability unit from the activity pool to complete the input requirements of the product database of the target product. When the corresponding input requirements in the product database are complete, the execution of the task is triggered. The task executor calls the data required for task execution, and based on the capability files and tools provided by the capability unit, uses the R&D activity capability unit as an external constraint, and uses successful cases as a reference to complete the specified output requirements and trigger the completion of the task.
[0027] The operating model of the multi-disciplinary collaborative R&D process for complex products in this application has the following advantages and benefits:
[0028] 1. By building an "activity pool" based on processes and using activities as a guide to build capability units for different types of products, flexible configuration of processes and R&D capabilities can be achieved;
[0029] 2. Construct process-based product R&D tasks, establish a mapping relationship between R&D tasks and activities in the "activity pool" through feature coding, and realize automatic matching of R&D tasks and capabilities; identify items that do not meet the task requirements through the comparison of task requirements and capability units, support the adjustment of planned tasks, and avoid unreasonable setting of planned tasks that affect process operation;
[0030] 3. By discretizing process activities into a series of product development tasks, using input data to drive task triggers, and calling corresponding capability units to complete task execution, we can avoid the rigid operating mode in which subsequent tasks can only be executed after the predecessor tasks are completed, and improve the flexibility of process execution. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] In order to more clearly illustrate the technical solution provided by the present application, the following is a brief introduction to the accompanying drawings. Obviously, the accompanying drawings described below are only some embodiments of the present application.
[0032] Figure 1 This is a schematic diagram of the typical process element model of this application;
[0033] Figure 2 A schematic diagram of the construction mode of the physical object activity layer, professional activity layer, and personal activity layer of the product of this application;
[0034] Figure 3A schematic diagram of the method for determining whether the capability document of this application needs to be structured;
[0035] Figure 4 Schematic diagram of the unified task model for this application. DETAILED DESCRIPTION
[0036] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0037] An operational model for a multi-disciplinary collaborative R&D process for a complex product includes the following steps:
[0038] Step 1: Obtain the product development process, structure the product development process, and obtain a typical process element model
[0039] Product development processes include structured processes and textual processes. Compared with textual processes, structured processes are usually implemented in information systems. They digitize all attributes of the process, have the ability to associate and call related elements, and realize the system operation of the entire R&D system. At the same time, structured processes are more intuitive and easy to understand, which can be quickly understood and executed by executives and managers, saving time for complicated text understanding.
[0040] There is no difference between structured processes and textual processes in the information they contain, such as Figure 1 , usually includes five basic elements, namely, activity content, executor requirements, input requirements, output requirements, and practical cases. Each basic element contains some attribute information. Of course, different product development processes can add relevant attribute information based on specific characteristics. It should be emphasized that structured processes are a prerequisite for the implementation of the present invention. Textual processes do not support the construction and operation of the "activity pool" (that is, step three cannot be executed).
[0041] Structuring the product development process means extracting the basic element information of the product development process data, and placing it into each basic element of the structured process according to the attribute information to form a process element description model.
[0042] Step 2: Build a hierarchical structure of activity pools for product development
[0043] like Figure 2, extract various R&D activities in the product R&D process to form a product R&D activity list, which is divided into three levels: product physical object activity level, professional activity level, and personal activity level. According to the product R&D activity list, a hierarchical structure of the activity pool for product R&D is constructed.
[0044] The three activity layers are decomposed step by step from top to bottom and supported step by step from bottom to top, including:
[0045] 1. Product physical object activity layer:
[0046] This level is usually mapped and decomposed by the various levels of the product breakdown structure model to obtain the corresponding level of project R&D activities. Considering the control cost, project activities generally do not exceed 4 levels.
[0047] Each project R&D activity often requires the collaboration of multiple professionals to complete. Taking a certain engine as an example, its product object level R&D activity construction model is as follows: Figure 2 , engine R&D activities are divided into multiple levels, including engine body R&D, core engine R&D, compressor R&D, etc.
[0048] 2. Professional activity layer
[0049] The professional activity layer further decomposes each project R&D activity to obtain R&D activities at each professional level. The activity granularity of the professional level R&D activities is to the extent that they can be undertaken by a single profession. The project activities of compressor R&D are decomposed into compressor aerodynamic design activities, compressor material selection design, etc. Among them, compressor material selection design only requires materials professionals to complete.
[0050] 3. Personal activity layer:
[0051] The R&D activities at each professional level are further decomposed to obtain individual R&D activities that can be undertaken by a single person. The individual R&D activity construction model is as follows: Figure 3 , capable of structural modeling, emergency calculations and structural optimization, etc.
[0052] Each level of R&D activities is used to undertake different types of personnel.
[0053] Step 3: Associate the R&D activities with the activity attribute matching capability elements in the basic database to form R&D activity capability units, and store the R&D activity capability units in different hierarchical structures of the activity pool.
[0054] Combined with the attribute definition of the process in step 1, the attributes such as required data and capability requirements are structured to facilitate association with the basic database. The R&D activity capability unit usually includes the following aspects:
[0055] 1) Attributes of the activity itself
[0056] The attributes of the activity itself include the attribute information shown in Table 1, among which the coding, hierarchical attributes, standard working hours, standard costs, input and output data requirements, etc. need to be structured, and the text description of the content does not need to be structured.
[0057] Table 1 Activity attribute information
[0058]
[0059] 2) Capability file attributes that support activity execution
[0060] Capability documents usually refer to documents that present specific operating methods, such as instructions and guidelines required to support R&D activities. Capability documents need to be stored and managed in a unified database. Figure 3 Whether the capability element information needs to be structured should be judged based on its correspondence with the activities. For example, if one capability element or multiple capability elements correspond to one R&D activity, the capability element does not need to be structured; if one capability element corresponds to two or more R&D activities, the capability element needs to be structured, and the relevant content in the capability element should be mapped to different R&D activities.
[0061] The capability element number, name, applicable product category, storage path and other information are associated with the activity as attribute information, which serves as capability file attribute information of the R&D activity capability unit.
[0062] 3) External file attributes that constrain activity execution
[0063] External constraint documents mainly refer to relevant national standards, national military standards and other standard documents that constrain activities. External documents need to be stored and managed in a unified database. Since the granularity of documents is generally larger than that of R&D activities, similar to Figure 3 b) Therefore, the external constraint file needs to be structured, and the external constraint clauses, storage paths and other information related to the activity should be associated with the activity as attribute information, which serves as the external constraint attribute information of the R&D activity capability unit.
[0064] 4) Attributes of software tools that support the execution of R&D activities
[0065] Refers to the software tools that support the execution of activities. The software needs to be stored and managed in a unified enterprise-level database. The software name, number, applicable product category, storage path and other information are associated with the activity as attributes, which serve as the software tool attribute information of the R&D activity capability unit.
[0066] 5) Business role attributes
[0067] Refers to the requirements for activity executors. The business role model needs to be stored and managed in a unified database. The role name, level requirements, role model storage path, corresponding position, position model path and other information need to be structured and associated with the activity as attribute information, as the business role attribute information of the R&D activity capability unit.
[0068] 6) Success Case Attributes:
[0069] The success case can be documented and can be matched with the result data in the product database (the database storing the final product information), and the number, name, storage path, etc. of the success case can be associated with the activity as attribute information. As the attribute information of the success case of the activity.
[0070] According to the various attributes of R&D activities, the matching data models, capability files, job capability models, successful cases in the product database, external standards, R&D tools, etc. are associated with the relevant databases to eventually form an R&D activity capability unit.
[0071] Step 4: Tailor the structured process based on the specific target product to form a product-specific structured process customized based on the target product process
[0072] The structured process in step one presents the entire "end-to-end" product development process, which is a "big and comprehensive" general process built for the development of new products. However, many products are often improved on the basis of previous products, or developed by inheriting certain functional modules of other products. Therefore, in the development of specific products, it is necessary to tailor the general structured process according to the product type and characteristics, and then form a special process suitable for the development of the target product.
[0073] The specific method for tailoring the structured process is: obtain all improvement information of the target product through a structured process or a textual process, determine the target attribute information corresponding to all the improvement information, and then replace the corresponding attribute information of the previous generation product with the target attribute information.
[0074] Step 5: Extract product-specific structured processes, match corresponding nodes and resource information, and form preliminary R&D tasks
[0075] Specifically, extract the product-specific structured process in step 4, use the task logic in the process as a constraint, match time, personnel, resources, risks, dynamic monitoring indicators and other attribute information based on a unified task model, and form the preliminary R&D tasks of the target product. Figure 4 shown.
[0076] Step 6: Configure the R&D activity capability units in the activity pool according to the preliminary R&D tasks, and verify the matching degree between the R&D activity capability units and the task requirements in the preliminary R&D tasks. If the matching degree meets the requirements, the formal tasks will be issued; if not, re-matching will be performed until the requirements are met.
[0077] Since the preliminary R&D tasks of the target product and the R&D activity capability units in the "activity pool" are both derived from the R&D process, the two can be automatically matched through coding attributes. In order to adapt to the situation where different products carry out the same activity and call different capability units, the coding of the preliminary R&D tasks and R&D activity capability units must contain the information shown in Table 2:
[0078] Table 2 Information contained in the coding of R&D tasks and activities in the “process pool” and their corresponding relationships
[0079]
[0080] After the two are matched, the capability unit and the corresponding attributes of the task are automatically checked to see if they are satisfied, identify any unreasonable aspects of the task's executor capabilities, input data requirements, output data requirements, cycle nodes, etc., and provide feedback to the product R&D team to adjust the planned tasks and form a formal task.
[0081] When the following situations occur, the planned tasks need to be adjusted:
[0082] 1. The personnel roles configured for the initial R&D task do not match the role settings specified for the activity in the "Activity Pool";
[0083] 2. The role capability level of the personnel configured for the initial R&D task is lower than the role capability level required by the corresponding activity in the "activity pool";
[0084] 3. The input data / output data requirements of the preliminary R&D task configuration do not match the input data / output data specified for the activities in the "Activity Pool";
[0085] 4. The formulation cycle of the preliminary R&D task configuration deviates by more than 30% from the standard working hours specified for the activities in the “activity pool”.
[0086] Step 7: Assign a certain R&D task from the formal tasks to the task executor, and use the data in the activity pool to drive the task executor to perform the corresponding R&D task
[0087] Specifically: after a certain R&D task in the formal task is issued to the task executor, the task executor retrieves the corresponding R&D activity capability unit from the activity pool to complete the input requirements of the product database of the target product. When the corresponding input requirements in the product database are complete, the execution of the task is triggered. The task executor calls the data required for task execution, and based on the capability files and tools provided by the capability unit, uses the R&D activity capability unit as an external constraint and successful cases as a reference, completes the specified output requirements and triggers the completion of the task.
[0088] The completed task is only one of the R&D tasks. Since the entire product-specific structured process has several R&D tasks at multiple levels, each R&D task needs to be monitored separately.
[0089] Step 8: After the R&D task is completed, map the task status back to the product-specific structured process and monitor the entire product development process until all R&D tasks are completed
[0090] Since R&D tasks originate from product-specific structured processes, the status of R&D tasks (such as unsystemized, in progress, completed) can be synchronized to the corresponding activities in the product-specific structured processes, and can present the current progress of product R&D in real time and accurately, providing support for managers to control the entire product R&D process.
[0091] Step 9: After completing all R&D tasks as required, they will be approved and stored in the activity pool as successful cases and corresponding R&D activity capability units.
[0092] After completing the task, the relevant information and data of the task execution will be used as a case. After approval by the product R&D project manager and the product R&D system supervisor, it can be associated with the corresponding activity in the activity pool as a successful case to provide reference for the development of other products.
[0093] Through the above design, the advantages and benefits of the present invention are as follows:
[0094] 1. By building an "activity pool" based on processes and using activities as a guide to build capability units for different types of products, flexible configuration of processes and R&D capabilities can be achieved;
[0095] 2. Construct process-based product R&D tasks, establish a mapping relationship between R&D tasks and activities in the "activity pool" through feature coding, and realize automatic matching of R&D tasks and capabilities; identify items that do not meet the task requirements through the comparison of task requirements and capability units, support the adjustment of planned tasks, and avoid unreasonable setting of planned tasks that affect process operation;
[0096] 3. By discretizing process activities into a series of product development tasks, using input data to drive task triggers, and calling corresponding capability units to complete task execution, we can avoid the rigid operating mode in which subsequent tasks can only be executed after the predecessor tasks are completed, and improve the flexibility of process execution.
[0097] It should be noted that for the same activity, different capability units can be established according to the characteristics of different categories of products. Taking aircraft engines as an example, the same "engine design point thermal calculation" activity, given that the tools, capability files, and external constraints used in military and civil aircraft to carry out this activity may be different, it is necessary to establish multiple capability units for the "engine design point thermal calculation" activity. This allows for flexible use of different types of products.
[0098] Finally, it should be noted that: the drawings of the embodiments disclosed in the present invention only involve structures related to the embodiments disclosed in the present invention, and other structures can refer to the general design. In the absence of conflict, the same embodiment and different embodiments of the present invention can be combined with each other;
[0099] Finally: The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. An operational model for the multi-disciplinary collaborative R&D process of complex products, It is characterized in that include: Obtain the product development process, structure the product development process, and obtain a typical process element model; Product development processes include structured processes and textual processes; Extract various R&D activities in the product R&D process, form a product R&D activity list, and build a hierarchical structure of activity pools for product R&D based on the product R&D activity list; Associating R&D activities with the activity attribute matching capability elements in the basic database to form R&D activity capability units, and storing the R&D activity capability units in different hierarchical structures of the activity pool; Tailor the structured process based on the specific target product to form a product-specific structured process customized based on the target product process; Extract product-specific structured processes, match corresponding nodes and resource information, and form preliminary R&D tasks; Configure the R&D activity capability units in the activity pool according to the preliminary R&D tasks, and verify the matching degree between the R&D activity capability units and the task requirements in the preliminary R&D tasks. If the matching degree meets the requirements, issue the formal tasks; if not, re-match until the requirements are met; Assign a certain R&D task from the formal tasks to the task executor, and use the data in the activity pool to drive the task executor to perform the corresponding R&D task; After the R&D task is completed, the task status is mapped back to the product-specific structured process to monitor the entire product development process until all R&D tasks are completed; After completing all R&D tasks as required, they will be approved and stored in the activity pool as successful cases and corresponding R&D activity capability units.
2. The operation model of the multi-disciplinary collaborative R&D process of complex products as described in claim 1, Features: The product R&D activity list is divided into three levels: product physical object activity level, professional activity level, and personal activity level. The product physical object activity level is mapped and decomposed to each level of the product decomposition structure model to obtain the project R&D activities at the corresponding level. The professional activity layer further decomposes the R&D activities of each project to obtain R&D activities at each professional level. The granularity of the R&D activities at the professional level is such that they can be undertaken by a single profession. The personal activity layer further decomposes the R&D activities at each professional level to obtain personal R&D activities that can be undertaken by a single person.
3. The operation model of the multi-disciplinary collaborative R&D process of complex products as described in claim 1, Features: The R&D activity capability unit includes activity attributes, capability file attributes, external file attributes, software tool attributes, business role attributes and success case attributes.
4. The operation model of the multi-disciplinary collaborative R&D process of complex products as claimed in claim 1, Features: The specific method for tailoring the structured process is: obtain all improvement information of the target product through a structured process or a textual process, determine the target attribute information corresponding to all the improvement information, and then replace the corresponding attribute information of the previous generation product with the target attribute information.
5. The operation model of the multi-disciplinary collaborative R&D process of complex products as claimed in claim 1, It is characterized in that The specific method for obtaining the preliminary R&D tasks is: extract the product-specific structured process in step four, use the task logic in the process as a constraint, and based on a unified task model, match time, personnel, resources, risks and dynamic monitoring indicator information to form preliminary R&D tasks for the target product.
6. The operation model of the multi-disciplinary collaborative R&D process of complex products as claimed in claim 1, Features: The preliminary R&D tasks are automatically matched with the R&D activity capability units through coding attributes, which include product category information, sub-category information, hierarchical object information in the product decomposition structure, hierarchical information of the corresponding process, hierarchical information in the activity pool, task name information and activity name information.
7. The operation model of the multi-disciplinary collaborative R&D process of complex products as claimed in claim 1, It is characterized in that The specific method of using data in the activity pool to drive task executors to perform corresponding R&D tasks is as follows: after a certain R&D task in the formal task is issued to the task executor, the task executor retrieves the corresponding R&D activity capability unit from the activity pool to complete the input requirements of the product database of the target product. When the corresponding input requirements in the product database are complete, the execution of the task is triggered. The task executor calls the data required for task execution, and based on the capability files and tools provided by the capability unit, uses the R&D activity capability unit as an external constraint, and uses successful cases as a reference to complete the specified output requirements and trigger the completion of the task.
Citation Information
Cited By
Domain MBSE process definition method
CN120560639A
A domain-specific mbse process definition method
CN120560639B
