Business digital processing method based on WBS and storage medium

By using a WBS-based business digitization approach, the problems of low information transmission efficiency and unusable business experience in traditional business processes have been solved, enabling refined management and efficient collaboration, and improving the accuracy and reliability of project execution.

CN121638847APending Publication Date: 2026-03-10CHINA FAW CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-11-18
Publication Date
2026-03-10

AI Technical Summary

Technical Problem

Traditional business process management methods suffer from inefficient information transmission and the inability to reuse business experience, leading to communication barriers, duplication of work, and decision-making delays, which affect project progress and quality.

Method used

A business digitization processing method based on WBS is adopted. This involves determining processing dimensions, building business role teams, deconstructing business processes, constructing a business architecture network diagram, configuring attributes and assigning roles, forming a target WBS template, and verifying its accuracy.

Benefits of technology

It enabled refined management and efficient collaboration of business processes, improved information transmission efficiency and the reusability of business experience, and ensured that projects proceeded as planned.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121638847A_ABST
    Figure CN121638847A_ABST
Patent Text Reader

Abstract

The invention discloses a service digital processing method based on WBS and a storage medium, and relates to the technical field of information technology fusion. The method comprises the following steps: determining a processing dimension of an initial WBS template based on a business process; determining a service execution period and milestone nodes of the initial WBS template according to the processing dimension; building a service role team of the initial WBS template according to the processing dimension; deconstructing the business process based on a preset decomposition method to obtain a decomposition structure of the initial WBS template; obtaining a service architecture network diagram of the initial WBS template by linking a service unit; carrying out attribute configuration on the service unit and carrying out role allocation on the packet to obtain a target WBS template; and checking the accuracy of the target WBS template, and processing the business process according to the target WBS template. The technical problems that the information transmission efficiency of a traditional business process is low and business experience cannot be reused in the prior art are solved.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of information technology fusion, in particular to a business digital processing method based on WBS and a storage medium. BACKGROUND

[0002] In the current business environment, enterprises are facing increasingly complex and rapidly changing business process challenges. Traditional business process management methods, such as document-based process description and unstructured project management, have obvious problems of low information transmission efficiency. Due to the lack of effective processing methods, business executors often have difficulty in obtaining accurate process information in time, resulting in communication barriers, repeated work and decision delay, which seriously affects the project progress and quality.

[0003] More importantly, traditional process management often ignores the accumulation and reuse of business experience, and each project execution starts almost from scratch, failing to fully utilize the knowledge and best practices accumulated in the past, resulting in resource waste and repeated learning curve.

[0004] In view of the above problems, no effective solution has been proposed. SUMMARY

[0005] The embodiments of the present application provide a business digital processing method based on WBS and a storage medium, to at least solve the technical problems of low information transmission efficiency of traditional business process and unavailability of business experience reuse in related technologies.

[0006] According to one embodiment of the present invention, a business digitization processing method based on a Work Breakdown Structure (WBS) is provided, comprising: determining the processing dimensions of an initial WBS template based on business processes, wherein the processing dimensions include business main lines, business categories, and business levels; determining the business execution cycle and milestone nodes of the initial WBS template according to the processing dimensions, wherein the business execution cycle represents the total time from business initiation to completion, and the milestone nodes represent the phased goals achieved during business execution; constructing a business role team for the initial WBS template according to the processing dimensions, wherein the business role team represents the business roles required to execute the business processes; and deconstructing the business processes based on a preset decomposition method to obtain... The process involves creating a decomposition structure for the initial WBS template. Pre-defined decomposition methods include: a business unit modeling method, a package modeling method, and a WBS decomposition structure construction method. The business unit modeling method identifies multiple business units, the package modeling method identifies multiple packages, and the WBS decomposition structure construction method decomposes or merges business processes. By linking business units, a business architecture network diagram of the initial WBS template is obtained, which illustrates business processes and activities. Attributes are configured for business units, and roles are assigned to packages to obtain the target WBS template. The accuracy of the target WBS template is verified, and business processes are processed based on the target WBS template.

[0007] Optionally, the business digitization processing method based on WBS also includes: updating the target WBS template based on change information, wherein the change information is used to record changes in the information within the WBS template.

[0008] Optionally, the processing dimensions of the initial WBS template are determined based on the business processes, including: decomposing the business processes to determine the main business lines, business categories, and business levels; and integrating the main business lines, business categories, and business levels into the initial WBS template to determine the processing dimensions of the initial WBS template.

[0009] Optionally, the business execution cycle and milestone nodes of the initial WBS template are determined based on the processing dimension, including: determining the execution scale and complexity of the business based on the processing dimension; determining the business execution cycle based on the execution scale and complexity; and determining milestone nodes by combining the business execution cycle, execution scale, and complexity.

[0010] Optionally, a business role team is built based on the processing dimension to construct an initial WBS template, including: determining the business organizational structure based on the processing dimension, wherein the business organizational structure includes functional departments and business areas; determining the initial business roles related to the project according to the business organizational structure by functional department or business area; merging business roles whose functional similarity exceeds a preset similarity threshold among the initial business roles to obtain target business roles; determining the management level of the target business roles based on the business organizational structure; and processing the target business roles and their corresponding management levels in a tree structure so that upper-level business roles control lower-level business roles to obtain a business role team.

[0011] Optionally, the business process is deconstructed based on a preset decomposition method to obtain the decomposition structure of the initial WBS template, including: decomposing the business process into multiple business units based on a business unit modeling method; or decomposing the business process into multiple packages based on a package modeling method; and processing the multiple business units and multiple packages based on a WBS decomposition structure construction method to determine the decomposition structure of the initial WBS template.

[0012] Optionally, by linking business units, a business architecture network diagram of the initial WBS template is obtained, including: determining the node type of each business unit, wherein the node type includes: start node, intermediate node and end node; determining the sequential relationship between business units based on the node type; and linking business units based on the sequential relationship to obtain the business architecture network diagram.

[0013] Optionally, the process involves configuring attributes for business units and assigning roles to packages, including: configuring attributes for business units using preset information, which includes: work hour information, business value, carrier, business rules, inputs, and outputs; determining the start and end times of execution for business units based on work hour information, sequential relationships, and milestone nodes; driving business units based on preset modes, start and end times, where preset modes include: cycle-driven mode, time-driven mode, and relationship-driven mode; and assigning roles to each package through the decomposition structure of business role teams and the initial WBS template.

[0014] Optionally, the accuracy of the target WBS template is verified, and the business process is processed according to the target WBS template, including: verifying the target WBS template based on preset verification standards, wherein the preset verification standards include: business integrity, node type and sequential relationship, isolated point check, loop point check, time consistency check, business role verification, empty packet check, and role consistency check; in response to the target WBS template passing the verification, the business process is processed based on the target WBS template.

[0015] According to one embodiment of the present invention, a business digitization processing device based on a Work Breakdown Structure (WBS) is also provided, comprising: a first determining module, configured to determine the processing dimensions of an initial WBS template based on a business process, wherein the processing dimensions include a business main line, a business category, and a business level; a second determining module, configured to determine the business execution cycle and milestone nodes of the initial WBS template according to the processing dimensions, wherein the business execution cycle represents the total time from business initiation to completion, and the milestone nodes represent the phased goals achieved during the business execution process; a building module, configured to build a business role team for the initial WBS template according to the processing dimensions, wherein the business role team represents the business roles required to execute the business process; and a deconstruction module, configured to decompose the business process based on a preset decomposition method. The process involves deconstruction to obtain the initial WBS template's decomposition structure. Pre-defined decomposition methods include: a business unit modeling method, a package modeling method, and a WBS decomposition structure construction method. The business unit modeling method identifies multiple business units, the package modeling method identifies multiple packages, and the WBS decomposition structure construction method decomposes or merges business processes. A linking module is used to link business units to obtain the business architecture network diagram of the initial WBS template, which displays business processes and activities. A configuration module is used to configure attributes for business units and assign roles to packages to obtain the target WBS template. A verification module is used to verify the accuracy of the target WBS template and process business processes according to the target WBS template.

[0016] According to one embodiment of the present invention, a computer-readable storage medium is also provided, wherein the storage medium stores a computer program, wherein the computer program is configured to execute the WBS-based business digitization processing method described above when running on a computer or processor.

[0017] According to one embodiment of the present invention, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the WBS-based business digitization processing method described above.

[0018] According to one embodiment of the present invention, a computer program product is also provided, including a computer program that, when executed by a processor, implements the WBS-based business digitization processing method described above.

[0019] In this embodiment of the invention, the processing dimensions of the initial WBS template are first determined based on the business process, and the business execution cycle and milestone nodes of the initial WBS template are determined according to the processing dimensions. Next, the business role teams of the initial WBS template are built according to the processing dimensions, and the business process is deconstructed based on a preset decomposition method to obtain the decomposed structure of the initial WBS template. Then, by linking business units, the business architecture network diagram of the initial WBS template is obtained, and the attributes of business units are configured and roles are assigned to packages to obtain the target WBS template. Finally, the accuracy of the target WBS template is verified, and the business process is processed according to the target WBS template, achieving the goal of refined management and efficient collaboration. This achieves the technical effect of improving the accuracy and reliability of business process processing, thereby solving the technical problems of low information transmission efficiency and the inability to reuse business experience in traditional business processes in related technologies. Attached Figure Description

[0020] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this invention, illustrate exemplary embodiments of the invention and are used to explain the invention, but do not constitute an undue limitation of the invention. In the drawings: Figure 1 This is a flowchart of a business digitization processing method based on WBS according to one embodiment of the present invention; Figure 2 This is a structural block diagram of a WBS-based business digitization processing device according to one embodiment of the present invention. Detailed Implementation

[0021] For ease of understanding, some concepts related to embodiments of the present invention are illustrated below for reference. A Work Breakdown Structure (WBS) is a business management tool that breaks down and defines business deliverables and tasks into a hierarchical tree structure. Each node (or branch) of the WBS represents a specific work package, which helps to clearly define the scope of business, assign responsibilities, and track progress and costs.

[0022] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0023] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. In the description of these embodiments, unless otherwise stated, "a plurality of" means two or more. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0024] According to one embodiment of the present invention, an embodiment of a business digitization processing method based on WBS is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0025] This method embodiment can be executed in an electronic device, similar control device, or system that includes a memory and a processor. Taking an electronic device as an example, the electronic device may include one or more processors and a memory for storing data. Optionally, the electronic device may also include a communication device for communication functions and a display device. Those skilled in the art will understand that the above structural description is merely illustrative and does not limit the structure of the electronic device. For example, the electronic device may include more or fewer components than described above, or have a different configuration than described above.

[0026] A processor may include one or more processing units. For example, a processor may include a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microcontroller unit (MCU), a field-programmable gate array (FPGA), a neural network processing unit (NPU), a tensor processing unit (TPU), or an artificial intelligence (AI) processor. Different processing units may be independent components or integrated into one or more processors. In some instances, electronic devices may also include one or more processors.

[0027] The memory can be used to store computer programs, such as the computer program corresponding to the WBS-based business digitization processing method in this embodiment of the invention. The processor implements the aforementioned WBS-based business digitization processing method by running the computer program stored in the memory. The memory may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to electronic devices via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0028] Communication devices are used to receive or send data via a network. Specific examples of such networks may include wireless networks provided by the mobile terminal's communication provider. In one example, the communication device includes a network interface controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the communication device may be a radio frequency (RF) module used for wireless communication with the Internet.

[0029] Display devices can be, for example, touchscreen liquid crystal displays (LCDs) and touch displays (also referred to as "touchscreens" or "touch displays"). The LCD allows users to interact with the user interface of the mobile terminal. In some embodiments, the mobile terminal has a graphical user interface (GUI), which allows users to interact with the GUI through finger contact and / or gestures on a touch-sensitive surface. Optional human-computer interaction functions include: creating web pages, drawing, word processing, creating electronic documents, playing games, video conferencing, instant messaging, sending and receiving emails, call interfaces, playing digital video, playing digital music, and / or web browsing, etc. Executable instructions for performing the above human-computer interaction functions are configured / stored in one or more processor-executable computer program products or readable storage media.

[0030] This embodiment provides a WBS-based business digitization processing method running on electronic devices. Figure 1 This is a flowchart of a business digitization processing method based on WBS according to one embodiment of the present invention, such as... Figure 1 As shown, the process includes the following steps: Step S10: Determine the processing dimensions of the initial WBS template based on the business process. The processing dimensions include the main business line, business category, and business level. In this embodiment of the invention, the business process includes the execution order of various business activities of the enterprise, the required resources, task allocation, and the dependencies between business units.

[0031] The initial WBS template is a preliminary work breakdown structure created at the beginning of the project, based on an understanding of the business processes and a preliminary analysis of project requirements.

[0032] A business thread is the core path that runs through all of an enterprise's business processes, reflecting the enterprise's value creation flow. For example, a business thread may include, but is not limited to: Integrated Product Development (IPD), Sales Management Framework (SMF), and Order to Delivery (OTD).

[0033] Business categories are sub-fields within a business process. For example, business categories may include classifying IPD into complete vehicles, powertrains, etc., without limitation.

[0034] Business level is a quantification of the scale, complexity, and scope of impact of business activities. For example, business levels may include classifying vehicles as those built on entirely new platforms, those built on mature platforms, modified models, model years, etc., without limitation here.

[0035] Determining the processing dimensions of the initial WBS template based on business processes can be understood as setting and selecting the main considerations or standards for building the WBS template in the early stages of project management by analyzing and understanding the specific business processes.

[0036] As can be seen, by determining the processing dimensions of the initial WBS template based on the business process, the abstract business process can be transformed into a specific and operable project work unit, which facilitates project team collaboration, resource allocation, and progress tracking.

[0037] Step S11: Determine the business execution cycle and milestone nodes of the initial WBS template according to the processing dimension. The business execution cycle is used to represent the total time from the start to the completion of the business, and the milestone nodes are used to represent the phased goals achieved during the business execution process. In this embodiment of the invention, the business execution cycle refers to the entire timeframe from project initiation to the complete achievement of business objectives; that is, the business execution cycle encompasses all stages of the business process. In this embodiment, the business execution cycle is determined based on a deep understanding of the business process, combined with the characteristics of the business (such as complexity, resource requirements, and external market factors). For example, for a new product development project, the business execution cycle may begin with market research and end with product launch and after-sales support, with a time span potentially ranging from one to two years; no limitation is imposed here.

[0038] Milestones are key dates or events in the execution of a business process, marking the end or beginning of an important phase of a project or business process. Milestones serve as critical checkpoints for project progress and quality control, typically coinciding with the business execution cycle, to assess whether the project is progressing as planned and whether adjustments are necessary.

[0039] Determining the business execution cycle and milestone nodes of the initial WBS template based on the processing dimensions can be understood as determining the total time required from project initiation to project completion, as well as the key points in the project execution process, based on the business main line, business category, and business level.

[0040] For example, assume the time from product concept development to product launch is 18 months. This 18-month period is the business execution cycle, covering the entire process from market analysis, product design, engineering development, testing, production preparation to final product release. Within the business execution cycle, the following milestones can be set: completion of market analysis and proof of concept (approximately month 3); completion of preliminary design and key design decisions (approximately month 6); completion of engineering design and prototype testing (approximately month 9); completion of production preparation and first sample production (approximately month 12); completion of final testing and quality verification (approximately month 15); pre-launch preparation and market launch (approximately month 18). Each milestone is a crucial hurdle in the project, requiring the project team to conduct detailed evaluations and decisions at each milestone to ensure the project progresses as planned.

[0041] It can be seen that determining the business execution cycle and milestone nodes of the initial WBS template based on the processing dimensions ensures that the WBS template closely matches the actual business process, provides a clear timeline and checkpoints for subsequent project execution, and enhances the pertinence and effectiveness of project management.

[0042] Step S12: Build the business role team of the initial WBS template according to the processing dimension, where the business role team is used to represent the business roles required to execute the business process; In this embodiment of the invention, the business role team refers to the collection of various functional roles required when executing a specific business process. Each role has its specific responsibilities and permissions to ensure that the business process is carried out efficiently and in an orderly manner.

[0043] The business role team that builds the initial WBS template based on the processing dimensions can be understood as a team structure that can cover all functional roles required for the entire business execution, based on the already determined business main line, business category, and business level.

[0044] As can be seen, the above steps clarify the functional roles related to the entire business process, as well as the responsibilities and collaboration modes of each role, thereby improving the efficiency and effectiveness of project management, reducing uncertainty in the execution process, and promoting effective communication among team members.

[0045] Step S13: Deconstruct the business process based on the preset decomposition method to obtain the decomposition structure of the initial WBS template. The preset decomposition method includes: business unit modeling method, package modeling method and WBS decomposition structure construction method. The business unit modeling method is used to determine multiple business units, the package modeling method is used to determine multiple packages, and the WBS decomposition structure construction method is used to decompose or merge the business process. In this embodiment of the invention, the business unit modeling method is used to determine the most basic task unit constituting the business process, namely the business unit. The business unit is the lowest level (i.e., leaf node) of the WBS, representing a minimal, independently achievable, and complete work task. Exemplarily, the business unit is the smallest independent and complete task, ensuring that each task can be clearly defined and executed. Each business unit should have a unique responsible department and role to avoid ambiguity or overlap in responsibilities. Furthermore, by determining the approval nodes, levels, and approval roles of the business unit, the transparency and compliance of decision-making and execution are ensured; however, no restrictions are imposed here.

[0046] Package modeling is used to determine the middle-level structure, or packages, in a Work Breakdown Structure (WBS). A package is a collection of business activities with a larger granularity than a business unit, representing a stage or thematic area within a business process. Exemplarily, a package is a collection of sub-packages or business units. Packages exist as intermediate nodes in the WBS, facilitating the organization and categorization of business units. Besides milestone nodes and root nodes, package nodes from different domains are not mixed, ensuring that each package focuses on business activities in a specific domain, thereby improving management efficiency and accuracy. A clear hierarchical relationship exists between packages and sub-packages; a collection of sub-packages constitutes a parent package. This relationship clearly defines the hierarchy and organizational structure of business activities.

[0047] The Work Breakdown Structure (WBS) approach decomposes or integrates business processes into a structure suitable for project management and execution. For example, it can start with project goals or main business lines, progressively breaking them down into specific tasks or business units to ensure all work is covered and aligned with project objectives. Alternatively, it can start with existing business units or sub-packages, aggregating upwards to form larger packages or project phases, thus helping to identify and integrate common characteristics of underlying activities. Furthermore, it can incorporate experience from previous projects or business processes to optimize the decomposition structure; there are no limitations on this approach.

[0048] The decomposition of the business process based on the preset decomposition method to obtain the decomposition structure of the initial WBS template can be understood as follows: by combining the business unit modeling method, the package modeling method and the WBS decomposition structure construction method to deconstruct the business process, the decomposition structure of the initial WBS template is obtained.

[0049] As can be seen, by using the above decomposition method to transform abstract business processes into a WBS template decomposition structure, all necessary tasks are decomposed, identified, and arranged, providing a solid foundation for the smooth progress of the project.

[0050] Step S14: By linking business units, obtain the business architecture network diagram of the initial WBS template, wherein the business architecture network diagram is used to display business processes and business activities; In this embodiment of the invention, the business architecture network diagram is a visual chart formed by linking and organizing the sequential relationships between business units, used to show the various activities in the business process and their interdependent relationships.

[0051] The business architecture network diagram of the initial WBS template obtained by linking business units can be understood as follows: by establishing the preceding and following business units of each business unit, linking them into chains, and then connecting the chains into a network, a business architecture network diagram is formed.

[0052] As can be seen, determining the business architecture network diagram through the above steps not only shows the structure and flow of the business process, but also includes key information such as the order of task execution, dependencies, time planning, and role allocation, so that the project team can effectively control the project progress and optimize resource allocation.

[0053] Step S15: Configure the attributes of the business units and assign roles to the packages to obtain the target WBS template; In this embodiment of the invention, configuring attributes for business units and assigning roles to packages to obtain the target WBS template can be understood as refining the initial WBS template, configuring detailed attribute information for business units, and assigning clear roles to packages, so that project managers can better plan projects, schedule resources, and control risks.

[0054] It can be seen that by configuring attributes and assigning roles, abstract business processes are transformed into concrete and operable project management tools, thereby improving the team's execution capabilities.

[0055] Step S16: Verify the accuracy of the target WBS template and process the business process according to the target WBS template.

[0056] In this embodiment of the invention, verifying the accuracy of the target WBS template and processing the business process based on the target WBS template can be understood as verifying the accuracy of the target WBS template to confirm whether the target WBS template meets the predetermined design principles and project requirements. If the target WBS template passes the accuracy verification, the business process is processed based on the target WBS template.

[0057] It can be seen that by validating the target WBS template and processing business processes based on the target WBS template, the sequential relationships of tasks and role assignments are clarified, which helps to facilitate collaboration and communication among team members.

[0058] Based on the above steps, the initial WBS template's processing dimensions are first determined based on the business process, and then the business execution cycle and milestone nodes are determined according to these dimensions. Next, the business role teams for the initial WBS template are built based on the processing dimensions, and the business process is deconstructed using a preset decomposition method to obtain the decomposed structure of the initial WBS template. Then, by linking business units, the business architecture network diagram of the initial WBS template is obtained, and the attributes of business units are configured and roles are assigned to packages to obtain the target WBS template. Finally, the accuracy of the target WBS template is verified, and the business process is processed according to the target WBS template, achieving the goals of refined management and efficient collaboration. This achieves the technical effect of improving the accuracy and reliability of business process processing, thereby solving the technical problems of low information transmission efficiency and the inability to reuse business experience in traditional business processes.

[0059] Optionally, the business digitization processing method based on WBS also includes: updating the target WBS template based on change information, wherein the change information is used to record changes in the information within the WBS template.

[0060] In this embodiment of the invention, change information is a detailed record of changes to information within the WBS template during project execution. Change information may include adjustments to the project scope, reassessment of task hours, addition or deletion of business units, changes in role assignments, updates to technical parameters, consideration of external environmental factors, etc., and is not limited here.

[0061] Updating the target WBS template based on change information can be understood as follows: in the process of project management, the plan based on the WBS template is not static. As the project progresses, new challenges, changes in requirements, technology updates, or resource adjustments may occur, thus necessitating updates to the WBS template.

[0062] For example, the current version of the WBS template is recorded. If the information within the WBS template changes, the differences are recorded and the version is upgraded to obtain the latest version of the WBS template. During actual project execution, the latest version of the WBS template can be switched to, and the improved WBS version can be used to execute business processes.

[0063] It can be seen that by updating the WBS template based on change information, not only can the consistency between the project plan and the actual execution be ensured, but the overall management efficiency and quality of the project can also be dynamically improved.

[0064] Optionally, in step S10, the processing dimensions of the initial WBS template are determined based on the business process, including the following execution steps: Step S101: Decompose the business process to determine the main business line, business category, and business level; Step S102: Integrate the main business lines, business categories, and business levels into the initial WBS template to determine the processing dimensions of the initial WBS template.

[0065] In this embodiment of the invention, decomposing the business process and determining the main business line, business category and business level can be understood as systematically analyzing and structuring complex business processes, thereby breaking down business objectives or processes into manageable and traceable components, so as to more precisely control project progress and resource allocation.

[0066] Integrating business lines, business categories, and business levels into the initial WBS template to determine the processing dimensions of the initial WBS template can be understood as incorporating information on business lines, business categories, and business levels into the structure of the WBS template, forming a multi-level task decomposition system from high to low.

[0067] It can be seen that decomposing business processes and identifying business lines, categories, and levels is the foundation for translating business requirements into project management language. Integrating business lines, categories, and levels into the initial WBS template is the key step in transforming abstract analysis into a practical and operable management tool. By constructing the initial WBS template, the processing dimensions of project management are clarified, providing clear guidance for subsequent project execution and monitoring.

[0068] Optionally, in step S11, the business execution cycle and milestone nodes of the initial WBS template are determined according to the processing dimension, including the following execution steps: Step S111: Determine the execution scale and complexity of the business based on the processing dimension; Step S112: Determine the business execution cycle based on the execution scale and complexity; Step S113: Determine milestone nodes based on business execution cycle, execution scale, and complexity.

[0069] In this embodiment of the invention, determining the execution scale and complexity of a business based on the processing dimension can be understood as determining the coverage and workload of the project in terms of time, space, and resources based on the main business line, business category, and business level, as well as factors such as the interdependence between project tasks, technical difficulty, market uncertainty, and management difficulty, which are not limited here.

[0070] Determining the business execution cycle based on the scale and complexity of the project can be understood as developing a reasonable project timeline based on a full understanding of the project's scale and complexity, and then integrating it into a holistic project execution cycle.

[0071] Determining milestones based on the business execution cycle, scale, and complexity can be understood as follows: First, plan the time nodes for key activities according to the project execution cycle, ensuring that each milestone is set within a reasonable timeframe. Then, assess the contribution of each stage or activity to the overall project goals, setting higher-priority activities as milestones. It is also advisable to set more milestones in stages with large execution scale and high complexity to facilitate more frequent checks on project status and timely identification and resolution of potential problems.

[0072] For example, to implement steps S111 to S113, the project execution cycle can be determined first based on the scope, level, and grade of project management. Then, the phased achievement goals, i.e., milestone nodes, can be determined based on the actual status of project management. Finally, the relative deadlines for the milestone nodes can be determined based on the business objectives. In addition, the meeting level for evaluating milestone node progress can be determined based on the importance of the milestone nodes.

[0073] As can be seen, through the above steps, project managers can comprehensively assess the scale and complexity of the project based on the processing dimensions of the WBS template, and formulate a reasonable timetable and milestone nodes, thereby helping to ensure that the project proceeds as planned and improve the efficiency and success rate of project execution.

[0074] Optionally, in step S12, the business role teams that build the initial WBS template according to the processing dimensions include the following execution steps: Step S121: Determine the business organizational structure based on the processing dimension, wherein the business organizational structure includes functional departments and business areas; Step S122: Based on the business organizational structure, determine the initial business roles related to the project by functional departments or business areas; Step S123: Merge business roles whose functional similarity exceeds a preset similarity threshold in the initial business roles to obtain the target business role; Step S124: Determine the management level of the target business role based on the business organizational structure; Step S125: The target business role and its corresponding management level are processed in a tree structure so that the upper-level business role controls the lower-level business role, thus obtaining the business role team.

[0075] In this embodiment of the invention, determining the business organizational structure based on the processing dimension can be understood as determining the functional departments and business areas involved in the project based on the business main line, business category, and business level.

[0076] Determining the initial business roles related to a project based on the business organizational structure and by functional department or business area can be understood as further determining the initial business roles of each task or activity executor based on the established business organizational structure.

[0077] Merging business roles with functional similarity exceeding a preset similarity threshold in the initial business roles to obtain the target business roles can be understood as reducing role redundancy by analyzing the functional similarity between roles and merging roles with high similarity.

[0078] Determining the management hierarchy of target business roles based on the business organizational structure can be understood as determining the hierarchical position of each role within the project management structure based on the business organizational structure and the functions of the target business roles. For example, the hierarchy is typically based on the role's decision-making power, scope of responsibility, and coordination capabilities, but this is not limited to these aspects here.

[0079] A tree structure is used to process the target business roles and their corresponding management levels, so that the upper-level business roles control the lower-level business roles. The resulting business role team can be understood as organizing the target business roles and their management levels into a tree structure, with the highest-level role in the project as the root node, and branches downward to roles at different levels. This ensures that each role has a clear superior and potential subordinates, thereby realizing the control and coordination of the upper-level roles over the lower-level roles, and thus determining the business role team.

[0080] For example, to implement steps S121 to S125, you can investigate the existing organizational structure, sort out business roles by domain or department, then merge highly similar roles based on the collected set of business roles, then sort out and confirm the management level between roles in conjunction with the business structure, and finally establish a business role team based on the management level and the tree structure adopted, with the principle of parent role managing child role.

[0081] As can be seen, by following the steps above—from determining the organizational structure to refining roles, then optimizing role configurations and defining hierarchies—a clear and well-defined business role team tree structure is formed. This helps improve project management efficiency, ensures the rational allocation of project resources, and promotes efficient collaboration among team members.

[0082] Optionally, in step S13, the business process is deconstructed based on a preset decomposition method to obtain the decomposition structure of the initial WBS template, including the following execution steps: Step S131: Decompose the business process into multiple business units based on the business unit modeling method; or, Step S132: Decompose the business process into multiple packages based on the package modeling method; Step S133: Process multiple business units and multiple packages based on the WBS decomposition structure construction method to determine the decomposition structure of the initial WBS template.

[0083] In this embodiment of the invention, decomposing a business process into multiple business units based on the business unit modeling method can be understood as refining the entire business process into a series of the smallest, manageable, and independent work units through the business unit modeling method, making project management more refined and helping managers monitor and control project progress.

[0084] Decomposing a business process into multiple packages based on the package modeling method can be understood as further decomposing relatively clustered tasks in the business process into packages, which facilitates the grouping and management of complex tasks and resource allocation.

[0085] The WBS decomposition structure construction method is used to process multiple business units and packages to determine the decomposition structure of the initial WBS template. This can be understood as using the WBS decomposition structure construction method to integrate or split multiple business units and packages to form a WBS template decomposition structure with clear hierarchy and complete structure.

[0086] As can be seen, determining the decomposition structure of the initial WBS template through the above steps not only ensures the refinement of tasks and the clarification of responsibilities, but also promotes the rational allocation of resources and the flexibility of management.

[0087] Optionally, in step S14, by linking the business units, a business architecture network diagram of the initial WBS template is obtained, including the following execution steps: Step S141: Determine the node type for each business unit, where the node type includes: start node, intermediate node, and end node; Step S142: Determine the sequential relationship between business units based on node type; Step S143: Link business units based on their sequential relationships to obtain a business architecture network diagram.

[0088] In this embodiment of the invention, the start node refers to the first business unit executed when a project or a sub-project starts. That is, the start node represents initiation activities such as preparatory work or preliminary research.

[0089] Intermediate nodes are all business units in the project execution process, excluding the start and end nodes. An intermediate node depends on the completion of its preceding node and is a prerequisite for the start of its subsequent node. An intermediate node can have multiple preceding and subsequent nodes, reflecting the complex dependencies between business units.

[0090] The end node is the last business unit completed in a project or a sub-project.

[0091] Determining the node type of each business unit can be understood as classifying each business unit and determining its position in the project lifecycle, i.e., whether it is a start node, an intermediate node, or an end node. This helps in building the business architecture network diagram later and ensures the continuity and logic of the process.

[0092] Determining the sequential relationship between business units based on node type can be understood as follows: after determining the node type, it is necessary to further analyze the sequential relationship between business units, that is, which business units must be completed logically or temporally before other units, thereby ensuring the smooth progress of the business process and avoiding chaos or resource conflicts in project execution.

[0093] The business architecture network diagram can be understood as linking business units based on their sequential relationships to draw a business architecture network diagram, thereby reflecting the execution order and dependencies of business units in the entire business process.

[0094] It can be seen that by determining the node types of business units, defining sequential relationships, and constructing a business architecture network diagram, the logic and coherence of business processes are ensured. This not only helps to better plan and control project progress, but also makes it easier for team members to understand their position and role in the project, thereby promoting collaboration within the project team and the efficient achievement of project goals.

[0095] Optionally, in step S15, the attributes of the business unit are configured and the roles of the package are assigned, including the following execution steps: Step S151: Configure the attributes of the business unit using preset information, wherein the preset information includes: working hours information, business value, carrier, business rules, inputs and outputs; Step S152: Determine the start and end times of the execution of the business unit based on the work hour information, sequential relationships, and milestone nodes; Step S153: Drive the business unit based on the preset mode, execution start time and execution end time. The preset modes include: cycle-driven mode, time-driven mode and relationship-driven mode. Step S154: Assign roles to each package through the decomposition structure of business role teams and the initial WBS template.

[0096] In this embodiment of the invention, the working time information refers to the standard working time required to complete a business unit.

[0097] Business value describes the contribution of a business unit to project objectives or corporate strategy.

[0098] The carrier is the execution object or data carrier of a business unit. In different business scenarios, the carrier can be a product, report, design diagram, code, etc., and there are no restrictions here.

[0099] Business rules define the specific criteria, standards, and processes for the execution of business units, thereby ensuring the standardization and consistency of task execution.

[0100] Inputs and outputs are multiple independent and complete forms, certificates, documents, and books. A business unit is allowed to have multiple inputs and outputs.

[0101] The cycle-driven pattern is used to maintain the project cycle and the number of times it is driven, and business units are driven according to the cycle.

[0102] The time-driven model generates and executes tasks based on the business unit's planning or required timeframe.

[0103] The relationship-driven pattern is used to determine and maintain the companion relationships between business unit nodes, or to determine and maintain the mandatory nature of these companion relationships. For example, determining and maintaining the companion relationships between business unit nodes includes: FS / FF / SS / SF, where FS: FinishtoStart, indicating that the preceding sequence must end before the following sequence can begin; FF: FinishtoFinish, indicating that the preceding sequence must end before the following sequence can end; SS: StarttoStart, indicating that the preceding sequence must start before the following sequence can begin; and SF: StarttoFinish, indicating that the preceding sequence must start before the following sequence can end. Determining and maintaining the mandatory nature of companion relationships includes: normal dependencies or mandatory dependencies. Mandatory dependencies generate and execute tasks according to the companion relationship; non-mandatory dependencies generate tasks according to time or the companion relationship.

[0104] Configuring the attributes of business units using preset information can be understood as configuring the attributes of each business unit in detail based on preset information (such as working hours, business value, carrier, business rules, inputs and outputs), ensuring the completeness of information for each business unit and facilitating subsequent execution and management.

[0105] Determining the start and end times of a business unit based on work hours, sequential relationships, and milestones can be understood as calculating and determining the expected start and end times for each business unit based on its work hours, sequential relationships, and project milestone requirements. This helps in constructing the project's time framework and ensuring that each task starts and completes on time. For example, by combining the standard work hours, sequential relationships, and milestones of the business unit, the relative start and end times of the Work Breakdown Structure (WBS) are determined from top to bottom. This ensures that the relative time range of child nodes is within the time range of the parent node, and that the relative end time of a subsequent node is not earlier than the relative time of its predecessor; however, this is not a strict limitation.

[0106] Driving a business unit based on a preset mode, execution start time, and execution end time can be understood as follows: according to the selected preset driving mode and the determined execution time of the business unit, the project management tool or system will automatically or manually start, monitor, and adjust the execution of the business unit to ensure that the project proceeds as planned.

[0107] Assigning roles to each package using the business role teams and the initial WBS template decomposition structure can be understood as utilizing the previously established business role teams and WBS template decomposition structure to assign business roles responsible for execution and management to each package. This ensures that each task has a clear executor and supervisor, which helps improve the efficiency and quality of project execution. For example, combining the already defined role teams and WBS decomposition structure, roles are assigned to each package, enabling upper-level roles to manage lower-level roles, upper-level package roles to be responsible for the business of lower-level packages, and upper-level package roles to be responsible for the plans of lower-level packages; this is not limited to specific roles.

[0108] For example, other methods for maintaining node information include: defining the main lines of work for each domain and maintaining the node's attribution to the main lines; defining the critical path of the project and maintaining the node's attribution to the critical path; and defining whether a node is a critical node.

[0109] As can be seen, through the above steps, project managers not only configured the attributes of business units and determined the execution time of business units, but also selected appropriate driving modes and assigned roles to packages. This not only built a dynamic and orderly project execution environment, but also optimized the project management process.

[0110] Optionally, in step S16, the accuracy of the target WBS template is verified, and the business process is processed according to the target WBS template, including the following execution steps: Step S161: Verify the target WBS template based on preset verification standards, which include: business integrity, node type and sequential relationship, isolated point check, loop point check, time consistency check, business role verification, empty packet check, and role consistency verification. Step S162: In response to the successful verification of the target WBS template, process the business process based on the target WBS template.

[0111] In this embodiment of the invention, business integrity refers to checking whether the WBS template covers all business activities of the project based on the vertical decomposition structure of the WBS and the business architecture network diagram, ensuring that no tasks or activities are missed, thereby guaranteeing business integrity.

[0112] The node type and sequential relationship refer to ensuring that the node type of the business unit is correct and that the sequential relationship is matched. That is, the starting node has no preceding business unit, the middle node has both preceding and following business units, and the ending node has no following business unit.

[0113] Isolated point checking refers to ensuring that a business unit has no isolated points and that the business unit is in the business process, that is, the business unit has at least one preceding or succeeding business unit.

[0114] Loop point checking refers to confirming that there are no circularly dependent business units in the WBS template, that is, there are no self-loops or circular chains.

[0115] Time consistency check refers to verifying whether the start and end times of all business units conform to the overall project timeframe, ensuring that the time of child nodes is within the time of parent nodes, and that the time of subsequent nodes is not earlier than the time of preceding nodes.

[0116] Business role verification refers to verifying that each node has a clearly defined business role responsible for its execution and management.

[0117] Empty packet checking refers to checking whether all packets have sub-packets or business units to ensure that no empty packets exist.

[0118] Role consistency verification refers to confirming that the roles in the WBS template are consistent with the actual role assignments of the project team.

[0119] Validating the target WBS template based on preset validation standards can be understood as follows: after the target WBS template is built, it needs to be fully validated according to the aforementioned preset validation standards. This includes checking whether business activities are complete, whether node types and their sequential relationships are appropriate, whether there are any isolated or loop nodes, whether the time schedule is consistent, whether each node has a designated role, whether there are any empty packages, and whether role assignments are consistent with the actual team. The validation process can be performed manually or automatically using professional software tools; there are no restrictions here.

[0120] In response to the successful validation of the target WBS template, processing business processes based on the target WBS template can be understood as follows: if the target WBS template passes all validation criteria, the actual business processes can be processed and executed according to the validated target WBS template. This includes: developing a detailed project plan, including task allocation, timelines, and resource configuration. During project execution, the WBS template is used as a reference to monitor progress and ensure timely and high-quality task completion. When project changes occur, business processes are quickly adjusted and updated based on the template to maintain the flexibility of project management; no restrictions are imposed here.

[0121] As can be seen, the above steps can effectively improve the efficiency of project management, ensure that the project proceeds smoothly along the preset milestones, and thus achieve the goals on time and efficiently.

[0122] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of the present invention.

[0123] This embodiment also provides a WBS-based business digitization processing apparatus, which is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0124] Figure 2 This is a structural block diagram of a WBS-based business digitization processing device according to one embodiment of the present invention, such as... Figure 2As shown, a WBS-based business digitization processing device 200 is used as an example. This device includes: a first determining module 201, used to determine the processing dimensions of an initial WBS template based on business processes, wherein the processing dimensions include business main lines, business categories, and business levels; a second determining module 202, used to determine the business execution cycle and milestone nodes of the initial WBS template according to the processing dimensions, wherein the business execution cycle represents the total time from business initiation to completion, and the milestone nodes represent the phased goals achieved during business execution; a building module 203, used to build the business role teams of the initial WBS template according to the processing dimensions, wherein the business role teams represent the business roles required to execute the business processes; and a deconstruction module 204, used to deconstruct the business processes based on a preset decomposition method. The process involves deconstructing the initial WBS template to obtain its decomposition structure. Preset decomposition methods include: a business unit modeling method, a package modeling method, and a WBS decomposition structure construction method. The business unit modeling method identifies multiple business units, the package modeling method identifies multiple packages, and the WBS decomposition structure construction method decomposes or merges business processes. A linking module 205 links the business units to obtain the business architecture network diagram of the initial WBS template, which displays business processes and activities. A configuration module 206 configures the attributes of business units and assigns roles to packages to obtain the target WBS template. A verification module 207 verifies the accuracy of the target WBS template and processes the business processes according to the target WBS template.

[0125] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0126] Embodiments of the present invention also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to perform the steps in any of the above method embodiments when run on a computer or processor.

[0127] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps: Step S10: Determine the processing dimensions of the initial WBS template based on the business process. The processing dimensions include the main business line, business category, and business level. Step S11: Determine the business execution cycle and milestone nodes of the initial WBS template according to the processing dimension. The business execution cycle is used to represent the total time from the start to the completion of the business, and the milestone nodes are used to represent the phased goals achieved during the business execution process. Step S12: Build the business role team of the initial WBS template according to the processing dimension, where the business role team is used to represent the business roles required to execute the business process; Step S13: Deconstruct the business process based on the preset decomposition method to obtain the decomposition structure of the initial WBS template. The preset decomposition method includes: business unit modeling method, package modeling method and WBS decomposition structure construction method. The business unit modeling method is used to determine multiple business units, the package modeling method is used to determine multiple packages, and the WBS decomposition structure construction method is used to decompose or merge the business process. Step S14: By linking business units, obtain the business architecture network diagram of the initial WBS template, wherein the business architecture network diagram is used to display business processes and business activities; Step S15: Configure the attributes of the business units and assign roles to the packages to obtain the target WBS template; Step S16: Verify the accuracy of the target WBS template and process the business process according to the target WBS template.

[0128] Optionally, in this embodiment, the computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0129] Embodiments of the present invention also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0130] Optionally, in this embodiment, the processor in the above-described electronic device may be configured to run a computer program to perform the following steps: Step S10: Determine the processing dimensions of the initial WBS template based on the business process. The processing dimensions include the main business line, business category, and business level. Step S11: Determine the business execution cycle and milestone nodes of the initial WBS template according to the processing dimension. The business execution cycle is used to represent the total time from the start to the completion of the business, and the milestone nodes are used to represent the phased goals achieved during the business execution process. Step S12: Build the business role team of the initial WBS template according to the processing dimension, where the business role team is used to represent the business roles required to execute the business process; Step S13: Deconstruct the business process based on the preset decomposition method to obtain the decomposition structure of the initial WBS template. The preset decomposition method includes: business unit modeling method, package modeling method and WBS decomposition structure construction method. The business unit modeling method is used to determine multiple business units, the package modeling method is used to determine multiple packages, and the WBS decomposition structure construction method is used to decompose or merge the business process. Step S14: By linking business units, obtain the business architecture network diagram of the initial WBS template, wherein the business architecture network diagram is used to display business processes and business activities; Step S15: Configure the attributes of the business units and assign roles to the packages to obtain the target WBS template; Step S16: Verify the accuracy of the target WBS template and process the business process according to the target WBS template.

[0131] Embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0132] Optionally, in this embodiment, the computer program in the above-described computer program product can be configured to perform the following steps when executed by a processor: Step S10: Determine the processing dimensions of the initial WBS template based on the business process. The processing dimensions include the main business line, business category, and business level. Step S11: Determine the business execution cycle and milestone nodes of the initial WBS template according to the processing dimension. The business execution cycle is used to represent the total time from the start to the completion of the business, and the milestone nodes are used to represent the phased goals achieved during the business execution process. Step S12: Build the business role team of the initial WBS template according to the processing dimension, where the business role team is used to represent the business roles required to execute the business process; Step S13: Deconstruct the business process based on the preset decomposition method to obtain the decomposition structure of the initial WBS template. The preset decomposition method includes: business unit modeling method, package modeling method and WBS decomposition structure construction method. The business unit modeling method is used to determine multiple business units, the package modeling method is used to determine multiple packages, and the WBS decomposition structure construction method is used to decompose or merge the business process. Step S14: By linking business units, obtain the business architecture network diagram of the initial WBS template, wherein the business architecture network diagram is used to display business processes and business activities; Step S15: Configure the attributes of the business units and assign roles to the packages to obtain the target WBS template; Step S16: Verify the accuracy of the target WBS template and process the business process according to the target WBS template.

[0133] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0134] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0135] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0136] In the several embodiments provided by this invention, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection can be through some interfaces; the indirect coupling or communication connection of units or modules can be electrical or other forms.

[0137] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0138] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0139] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0140] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A WBS-based business digitization processing method, characterized by, The method comprises the following steps: determining the processing dimension of the initial WBS template based on the business process, wherein the processing dimension comprises a business main line, a business category and a business level; determining the business execution cycle and the milestone node of the initial WBS template according to the processing dimension, wherein the business execution cycle is used to represent the total time from the start to the completion of the business, and the milestone node is used to represent the phased achievement of the target in the business execution process; building the business role team of the initial WBS template according to the processing dimension, wherein the business role team is used to represent the business roles required to execute the business process; deconstructing the business process based on a preset decomposition method to obtain the decomposition structure of the initial WBS template, wherein the preset decomposition method comprises a business unit modeling method, a package modeling method and a WBS decomposition structure construction method, the business unit modeling method is used to determine a plurality of business units, the package modeling method is used to determine a plurality of packages, and the WBS decomposition structure construction method is used to decompose or merge the business process; obtaining the business architecture network diagram of the initial WBS template by linking the business units, wherein the business architecture network diagram is used to show the business process and the business activity; configuring attributes of the business units and assigning roles to the packages to obtain a target WBS template; verifying the accuracy of the target WBS template and processing the business process according to the target WBS template.

2. The method of claim 1, wherein, The method further comprises: updating the target WBS template based on change information, wherein the change information is used to record the case that the information in the WBS template changes.

3. The method of claim 1, wherein, The method of determining the processing dimension of the initial WBS template based on the business process comprises: decomposing the business process to determine the business main line, the business category and the business level; integrating the business main line, the business category and the business level into the initial WBS template to determine the processing dimension of the initial WBS template.

4. The method of claim 1, wherein, The method of determining the business execution cycle and the milestone node of the initial WBS template according to the processing dimension comprises: determining the execution scale and the complexity of the business based on the processing dimension; determining the business execution cycle according to the execution scale and the complexity; determining the milestone node in combination with the business execution cycle, the execution scale and the complexity.

5. The method of claim 1, wherein, The method of building the business role team of the initial WBS template according to the processing dimension comprises: determining the business organization structure based on the processing dimension, wherein the business organization structure comprises functional departments and business fields; determining the initial business roles related to the project according to the functional departments or the business fields based on the business organization structure; merging the business roles with a functional similarity exceeding a preset similarity threshold in the initial business roles to obtain target business roles; determining the management level of the target business roles based on the business organization structure. The target business role and the corresponding management level are processed in a tree structure form, so that an upper business role controls a lower business role, and a business role team is obtained.

6. The method of claim 1, wherein, The business process is deconstructed based on a preset decomposition method to obtain a decomposition structure of the initial WBS template, including: The business process is decomposed into a plurality of business units based on the business unit modeling method; or The business process is decomposed into a plurality of packages based on the package modeling method. The plurality of business units and the plurality of packages are processed based on the WBS decomposition structure construction method to determine the decomposition structure of the initial WBS template.

7. The method of claim 1, wherein, The business architecture network diagram of the initial WBS template is obtained by linking the business units, including: Determining the node type of each business unit, wherein the node type includes a start node, an intermediate node, and an end node; Determining the precedence relationship between the business units based on the node type; Linking the business units based on the precedence relationship to obtain the business architecture network diagram.

8. The method of claim 1, wherein, The business units are attribute-configured and the packages are role-assigned, including: Attribute-configuring the business units using preset information, wherein the preset information includes work hour information, business value, carrier, business rule, input, and output; Determining the execution start time and the execution end time of the business unit according to the work hour information, the precedence relationship, and the milestone node; Driving the business unit based on a preset mode, the execution start time, and the execution end time, wherein the preset mode includes a periodic driving mode, a time driving mode, and a relationship driving mode; Assigning a role to each package through the business role team and the decomposition structure of the initial WBS template.

9. The method of claim 1, wherein, The accuracy of the target WBS template is verified, and the business process is processed based on the target WBS template, including: Verifying the target WBS template based on a preset verification standard, wherein the preset verification standard includes business integrity, node type and precedence relationship, isolated point check, ring point check, time consistency check, business role verification, empty package check, and role consistency verification; In response to the verification of the target WBS template passing, processing the business process based on the target WBS template.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, wherein the computer program is configured to execute the WBS-based business digital processing method described in any one of claims 1 to 9 when running on a computer or a processor.