Operation and maintenance service management system and method based on CMDB data model and scene arrangement

Abstract

The invention provides an operation and maintenance service management system and method based on a CMDB data model and scene arrangement. The method belongs to the technical field of IT operation and maintenance automation, configuration management database (CMDB) and low-code process orchestration crossing. The method comprises the following steps: constructing a visual self-defined CMDB model for operation and maintenance service data, generating initial CMDB model data, automatically generating a unified data interface and a front-end UI, and constructing an operation and maintenance service data management platform; performing event-driven dynamic arrangement engine configuration according to the operation and maintenance service data management platform, converting an operation and maintenance scene into an executable workflow, generating operation and maintenance scene arrangement workflow data, and performing full-service flow data acquisition to obtain original operation and maintenance service data and service execution timestamp data; performing data preprocessing on the original operation and maintenance service data to generate standardized operation and maintenance service data; through the operation and maintenance service management method based on the CMDB data model and scene arrangement, the efficiency and accuracy of operation and maintenance service management are improved.

Description

Technical Field

[0001] This invention proposes an operation and maintenance business management system and method based on CMDB data model and scenario orchestration, belonging to the cross-technical fields of IT operation and maintenance automation, configuration management database (CMDB) and low-code process orchestration. Background Technology

[0002] In the current field of operations and maintenance management, mainstream CMDB and operations and maintenance automation solutions have many shortcomings that urgently need to be addressed.

[0003] Traditional CMDBs focus solely on storage configuration items (CI) and their topology relationships, resulting in a severe disconnect from business processes. For example, when performing business operations such as "server offline," the business process needs to be modeled separately in an independent BPMN engine. The lack of semantic connection between the two makes it impossible for the process to perceive changes in CI status, leading to low operational efficiency.

[0004] In terms of interfaces, different business scenarios require calling different microservice APIs, such as asset services, monitoring services, and ticket services, lacking a unified interface automatically generated based on the CMDB model. This results in high adaptation costs for consumers and complex and cumbersome operation and maintenance work.

[0005] In the development phase, adding a new operation and maintenance scenario, such as "network device configuration backup," still requires developers to invest a lot of effort in writing controllers, service layers, DAOs, and front-end pages. This cannot be achieved through pure configuration and violates the principle of efficient development.

[0006] Furthermore, the results of automated script execution are not written back to the CMDB in a structured manner, causing inconsistencies between the model state and the physical environment, significantly diminishing the authority of the CMDB. Existing publicly available patents or products are mostly limited to isolated functions, failing to deeply integrate the visual custom CMDB model with automated orchestration scenarios to build a three-in-one operational operating system, thus hindering a paradigm shift in operational services. Summary of the Invention

[0007] This invention provides an operation and maintenance business management system and method based on CMDB data model and scenario orchestration, to solve the problems mentioned in the background art above:

[0008] The present invention proposes an operation and maintenance business management method based on CMDB data model and scenario orchestration, the method comprising:

[0009] S1. Construct a visual custom CMDB model for operation and maintenance business data, generate initial CMDB model data, and automatically generate and process unified data interfaces and front-end UI to build an operation and maintenance business data management platform.

[0010] S2. Configure the event-driven dynamic orchestration engine according to the operation and maintenance business data management platform to transform the operation and maintenance scenario into an executable workflow, generate operation and maintenance scenario orchestration workflow data, and collect full business flow data to obtain raw operation and maintenance business data and business execution timestamp data; perform data preprocessing on the raw operation and maintenance business data to generate standardized operation and maintenance business data.

[0011] S3. Based on standardized operation and maintenance business data, perform model-driven interface calls to automatically adapt the unified RESTful / gRPC interface to different business scenarios and generate adapted operation and maintenance business interface data; execute operation and maintenance business through the adapted operation and maintenance business interface data, and perform structured processing on the execution results to generate structured execution result data.

[0012] S4. Perform status tracking processing on operation and maintenance business through business execution timestamp data to generate operation and maintenance business status tracking data; perform status update and write-back processing on operation and maintenance business status tracking data through structured execution result data, write the execution results back to the CMDB model, and generate updated CMDB model data.

[0013] S5. Based on the updated CMDB model data, perform a weighted stability index assessment to generate an operation and maintenance business stability index; based on the operation and maintenance business stability index, perform risk warning and process optimization processing to generate operation and maintenance business risk warning and optimization data.

[0014] The present invention proposes a system for implementing the operation and maintenance business management method based on CMDB data model and scenario orchestration as described above, the system comprising:

[0015] Platform construction module: Builds a visual custom CMDB model for operation and maintenance business data, generating initial CMDB model data; Based on the initial CMDB model data, it automatically generates and processes a unified data interface and front-end UI to build an operation and maintenance business data management platform;

[0016] Data Acquisition Module: Based on the event-driven dynamic orchestration engine configuration of the operation and maintenance business data management platform, the module transforms operation and maintenance scenarios into executable workflows, generates operation and maintenance scenario orchestration workflow data, performs full business flow data acquisition, and obtains raw operation and maintenance business data and business execution timestamp data; it also performs data preprocessing on the raw operation and maintenance business data to generate standardized operation and maintenance business data.

[0017] Business execution module: Based on standardized operation and maintenance business data, it performs model-driven interface calls, automatically adapts the unified RESTful / gRPC interface to different business scenarios, and generates adapted operation and maintenance business interface data; it executes operation and maintenance business through the adapted operation and maintenance business interface data, and performs structured processing on the execution results to generate structured execution result data;

[0018] Write-back processing module: Performs status tracking processing on operation and maintenance business using business execution timestamp data to generate operation and maintenance business status tracking data; performs status update write-back processing on operation and maintenance business status tracking data using structured execution result data, writes the execution results back to the CMDB model, and generates updated CMDB model data;

[0019] Optimization module: Based on the updated CMDB model data, a weighted stability index is evaluated to generate an operation and maintenance business stability index; based on the operation and maintenance business stability index, risk warnings and process optimizations are performed to generate operation and maintenance business risk warnings and optimization data.

[0020] The beneficial effects of this invention are as follows: By employing an operation and maintenance (O&M) business management method based on a CMDB data model and scenario orchestration, the efficiency and accuracy of O&M business management are improved. A visually customizable CMDB model makes business data management more intuitive and convenient. Unified data interfaces and automatic front-end UI generation reduce development and adaptation costs, eliminating the need for developers to write extensive code for new scenarios, saving manpower and time. An event-driven dynamic orchestration engine transforms O&M scenarios into executable workflows, enhancing the flexibility and adaptability of business processes and enabling rapid response to various O&M needs. Execution result write-back achieves a closed-loop data flow across the entire business process, reducing data inconsistency issues and avoiding O&M decision-making errors caused by inconsistencies between model states and the physical environment. It ensures a unified data source, avoiding data fragmentation, and reduces the difficulty of consumer-side adaptation through a unified interface. In complex and ever-changing O&M scenarios, it effectively avoids O&M failures caused by inconsistent interfaces and disjointed processes, ensuring the stable operation of O&M services and significantly improving the overall O&M level and quality. Attached Figure Description

[0021] Figure 1 This is a diagram illustrating the steps of the method described in this invention;

[0022] Figure 2 This is a system module diagram of the present invention. Detailed Implementation

[0023] The preferred embodiments of the present invention will be described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit the present invention.

[0024] One embodiment of the present invention, such as Figure 1 As shown, the operation and maintenance business management method based on CMDB data model and scenario orchestration includes:

[0025] S1. Construct a visual custom CMDB model for operation and maintenance business data, including defining model attributes, model relationships, and model views, and generating initial CMDB model data. The initial CMDB model data includes basic CRUD (Create, Read, Update, Query) management capabilities for business data. Based on the initial CMDB model data, perform unified data interface and front-end UI automatic generation processing to build an operation and maintenance business data management platform. The operation and maintenance business data management platform has a unified data consumption interface.

[0026] S2. Configure the event-driven dynamic orchestration engine according to the operation and maintenance business data management platform to transform the operation and maintenance scenario into an executable workflow, generate operation and maintenance scenario orchestration workflow data, collect full business flow data through the operation and maintenance scenario orchestration workflow data to obtain raw operation and maintenance business data and business execution timestamp data; perform data preprocessing on the raw operation and maintenance business data to generate standardized operation and maintenance business data.

[0027] S3. Based on standardized operation and maintenance business data, perform model-driven interface calls to automatically adapt the unified RESTful / gRPC interface to different business scenarios and generate adapted operation and maintenance business interface data; execute operation and maintenance business through the adapted operation and maintenance business interface data, and perform structured processing on the execution results to generate structured execution result data.

[0028] S4. Perform status tracking processing on operation and maintenance services using business execution timestamp data to generate operation and maintenance service status tracking data; perform status update and write-back processing on operation and maintenance service status tracking data using structured execution result data, write the execution results back to the CMDB model, and generate updated CMDB model data; perform consistency verification on the updated CMDB model data to ensure that the model status is consistent with the physical environment;

[0029] S5. Based on the updated CMDB model data, perform a weighted stability index assessment to generate an operation and maintenance business stability index; based on the operation and maintenance business stability index, perform risk warning and process optimization processing to generate operation and maintenance business risk warning and optimization data, and realize closed-loop management of all business flow data.

[0030] The working principle and effects of the above technical solution are as follows: This operation and maintenance business management method can unify data sources and data consumption interfaces, significantly improve the consistency and management efficiency of operation and maintenance data, and reduce the problem of data clutter in the traditional model; the visual custom CMDB model eliminates the need for repeated development, reducing the time and manpower costs of implementing operation and maintenance scenarios; the dynamic orchestration engine makes the operation and maintenance process more standardized, reducing the internal friction caused by the complexity of process intersections; the closed-loop management and consistency verification of the entire business flow enhances the stability and controllability of operation and maintenance business, avoiding decision-making biases caused by the disconnect between model data and the physical environment; it can quickly adapt to the needs of different operation and maintenance scenarios, improve the accuracy of business execution and status tracking, effectively reduce potential faults, and make operation and maintenance management more efficient and smooth.

[0031] In one embodiment of the present invention, S1 includes:

[0032] S11. Collect all basic data of operation and maintenance business. The basic data includes asset information, operation and maintenance process records, business-related data and equipment configuration details. Based on the visual operation interface, clarify the core attributes of the CMDB model one by one, define the core elements, including field type data format, mandatory requirements and unique identification rules, and generate basic data of model attributes.

[0033] S12. Supplement detailed parameters to the basic data of model attributes. The detailed parameters include configuration display rules, editing permissions, verification logic, error prompts and field width and height settings, improve the attribute configuration dimensions, and generate complete configuration data for model attributes.

[0034] S13. Organize the hierarchical relationships, dependency logic, and associated constraints of different operation and maintenance business objects, build a two-way association system between models, clarify the mapping rules of associated fields, and generate model relationship configuration data.

[0035] S14. Integrate the complete configuration data of model attributes and the configuration data of model relationships, design a multi-dimensional model view, configure the corresponding information, including view display fields, sorting priority, search conditions and custom rendering styles, and generate model view configuration data.

[0036] S15. Integrate the complete configuration data of model attributes, model relationship configuration data, and model view configuration data to form initial CMDB model data. The initial CMDB model data has the ability to add, delete, modify, and query business data. Based on this data, build a unified data interaction specification, automatically generate standardized data consumption interfaces and modular front-end interaction interfaces, and construct an operation and maintenance business data management platform.

[0037] The working principle and effects of the above technical solution are as follows: This CMDB model construction method can comprehensively integrate basic operational and maintenance business data, improve data integrity, and reduce the scattered and messy data situation in the traditional model; visual operation combined with detailed parameter supplementation reduces the technical threshold and time cost of model construction, and attribute configuration can be improved without complex development; bidirectional association between models and multi-dimensional view design enhance the clarity of data association and the flexibility of use; unified data interaction specifications and automatically generated standardized interfaces avoid the trouble of data docking without a basis. It can accurately match the data management needs of different operational and maintenance businesses, and quickly generate modular front-end interfaces, making the addition, deletion, modification and query of operational and maintenance data smoother, and avoiding the extra workload caused by subsequent data management chaos.

[0038] In one embodiment of the present invention, S2 includes:

[0039] S21. Deploy an event-driven dynamic orchestration engine based on the operation and maintenance business data management platform, configure basic settings, including engine core parameters, execution environment, scheduling mechanism and fault tolerance strategy, and generate basic configuration data for the orchestration engine.

[0040] S22. Deconstruct and organize various operation and maintenance business scenarios, including sorting out the scenario execution logic, participating objects, triggering conditions, execution order and branch judgment rules, and transform the scenarios into standardized executable workflow nodes to generate scenario node deconstruction data.

[0041] S23. Configure each workflow node, including configuring the execution script, input and output parameters, node dependencies and timeout handling mechanisms, etc., connect all nodes to form a complete workflow, and generate operation and maintenance scenario orchestration workflow data;

[0042] S24. Guided by the workflow data of the operation and maintenance scenario orchestration, start the full business flow data collection mechanism to capture the process data in the operation and maintenance business process. The process data includes raw business data, equipment operation status data, operation log data and business execution timestamp data of each link.

[0043] S25. Preprocess the collected raw data. The preprocessing includes cleaning, deduplication, format normalization, abnormal data filtering and missing value supplementation to eliminate data redundancy and inconsistency and generate standardized operation and maintenance business data that conforms to unified standards.

[0044] The working principle and effects of the above technical solution are as follows: This dynamic orchestration and data processing solution can break down complex operation and maintenance scenarios into standardized workflow nodes, improve the standardization of process execution, and reduce the internal friction caused by process overlap and entanglement in traditional models. Comprehensive data collection across all business flows, coupled with preprocessing such as cleaning, deduplication, and format standardization, improves data purity and avoids redundant and inconsistent data interfering with subsequent operations. Fault tolerance strategies in the engine's basic settings enhance the stability of process operation and reduce the impact of unexpected interruptions. Node configuration is refined down to the execution script and dependencies, making process connections smoother and reducing the debugging costs of scenario implementation. It can quickly adapt to the implementation needs of different operation and maintenance scenarios and lay a solid foundation for subsequent operations through standardized data, avoiding management chaos caused by the disconnect between processes and data, and making the advancement of operation and maintenance business more efficient and controllable.

[0045] In one embodiment of the present invention, step S22 includes:

[0046] Break down various operation and maintenance business scenarios, organize them, transform the scenarios into standardized and executable workflow nodes, and generate scenario node breakdown data;

[0047] Operation and maintenance business scenarios are categorized according to business attributes. These business scenario categories include configuration optimization, automatic inspection, compliance inspection, application deployment, and scheduled operation and maintenance. The core objectives and applicable scope of each scenario are distinguished to generate scenario classification data.

[0048] Based on the scenario classification data, the core links of each scenario are broken down one by one, unnecessary processes are removed, key execution nodes of the scenario are extracted, and scenario core link breakdown data is generated.

[0049] The data is broken down for the core links of the scenario, and the execution logic, participating objects, triggering conditions, execution order and branch judgment rules of each link are sorted out. The relationship logic between each element is clarified and the scenario link element data is generated.

[0050] Referring to the unified workflow node specification, the scenario element data is transformed into executable workflow nodes with a unified structure and clear definition, clarifying the core functions and boundaries of each node, and generating the initial version of scenario node data;

[0051] Verify the completeness, logical coherence, and executability of the initial version of the scene node data, correct deviations in node definitions and missing elements, and form standardized scene node decomposition data.

[0052] The working principle and effects of the above technical solution are as follows: This scenario decomposition method classifies scenarios according to business attributes, improving the accuracy of scenario classification and reducing confusion between different types of business scenarios; it removes unnecessary processes to extract core links, reducing process redundancy and making execution more focused on core objectives; it sorts out the elements and related logic of each link, enhancing the logical coherence of workflow nodes and avoiding gaps in subsequent execution; it transforms into unified and standardized executable nodes, improving the adaptability of different scenarios and reducing the trouble of repeated development; it verifies and corrects node data, ensuring the completeness and executability of node definitions, avoiding process bottlenecks caused by missing elements or logical deviations, and making the implementation of operation and maintenance scenarios smoother and more efficient.

[0053] In one embodiment of the present invention, S3 includes:

[0054] S31. Extract interface call requirements for different business scenarios from standardized operation and maintenance business data, clarify key information of the requirements, including data transmission protocol, interface type, parameter format and response requirements, and generate interface call requirement data.

[0055] S32. Based on the interface call requirement data, start the model-driven interface adaptation mechanism, automatically match the corresponding RESTful or gRPC interface, complete the dynamic mapping, format conversion and compatibility adjustment of interface parameters, and generate adapted operation and maintenance business interface data.

[0056] S33. Perform connectivity testing, data transmission verification, and response speed testing on the adapted operation and maintenance business interface data to verify the effectiveness of interface adaptation and generate interface adaptation verification result data.

[0057] S34. Based on the interface adaptation verification result data, trigger the corresponding operation and maintenance business execution process through the adapted interface, record the execution information in real time during the business execution process, including key operations, resource consumption, progress nodes, and anomalies, and generate business execution process data.

[0058] S35. Classify and organize the business execution process data and final execution results, standardize the fields, complete the related information and mark the result status, and transform them into structured execution result data with a unified structure.

[0059] The working principle and effects of the above technical solution are as follows: This interface adaptation and execution solution extracts interface requirements from standardized data, automatically matches and adapts to corresponding interfaces, improves interface integration efficiency, and reduces the time cost of manual adaptation; it verifies the effectiveness of interfaces through multi-dimensional testing, enhances call stability, and reduces transmission failures or data deviations; it records the entire business execution process in real time, and then, after classification, organization, and standardization, improves the regularity and usability of the result data; it can adapt to the interface requirements of different business scenarios, and ensures that the execution results are clear and traceable, avoiding the situation where data is scattered and difficult to use; the structured data with a unified structure provides reliable support for subsequent status updates and closed-loop management, avoiding process bottlenecks caused by interface incompatibility or data chaos, and making the execution of operation and maintenance business smoother and more accurate.

[0060] In one embodiment of the present invention, S33 includes:

[0061] Perform connectivity testing, data transmission verification, and response speed testing on the adapted operation and maintenance business interface data to verify the effectiveness of interface adaptation and generate interface adaptation verification result data.

[0062] Extract the core information from the adapted operation and maintenance business interface data. The core information includes interface address, communication port, connection protocol, etc., and organize it into basic interface test data.

[0063] Based on the interface basic test data, initiate a connection request across network environments, detect the network link connectivity between the interface and the target service, record the connection success or failure status, and generate interface connectivity test data.

[0064] Based on the parameter specifications in the interface call requirement data, construct multiple sets of test data packets, send them to the corresponding service through the adapted interface, compare the consistency between the returned data and the expected results, and generate data transmission verification data.

[0065] Multiple rounds of API call requests are continuously initiated, the response time of each request is recorded, the average response time, peak response time, and response stability fluctuation value are calculated, and response speed detection data is generated.

[0066] Integrate interface connectivity test data, data transmission verification data, and response speed test data, mark qualified and abnormal items, and form complete interface adaptation verification result data.

[0067] The working principle and effects of the above technical solution are as follows: This interface verification method first extracts core information and organizes test data to make testing more targeted and improve verification efficiency; it detects interface connectivity across network environments to identify link connectivity issues in advance and reduce the risk of network interruption during subsequent business execution; it verifies transmission consistency using multiple sets of test data packets to enhance data transmission accuracy and avoid transmission errors caused by parameter mismatch; it tests response speed through multiple rounds of calls to fully understand interface performance and reduce the risk of business delays due to slow responses; it integrates various test data and marks qualified and abnormal items to make the verification results clear and intuitive, avoids overlooking potential risks, lays a solid foundation for stable interface calls in the future, and makes operation and maintenance business execution smoother and more reliable.

[0068] In one embodiment of the present invention, step S4 includes:

[0069] S41. Parse the business execution timestamp data, connect the nodes of each stage of the operation and maintenance business in chronological order, establish a status tracking link, and capture status information in real time. The status information includes business execution status, progress changes, abnormal trigger points and recovery status, and generate operation and maintenance business status tracking data.

[0070] S42. Perform real-time fusion and comparison between structured execution result data and operation and maintenance business status tracking data, update business execution status information, result identifiers and node completion status, and generate real-time operation and maintenance business status data.

[0071] S43. According to the data storage rules of the CMDB model, synchronize the real-time status data of operation and maintenance business and the structured execution result data back to the CMDB model, overwrite the original corresponding data entries, and generate updated CMDB model data.

[0072] S44. Compare the updated CMDB model data with the actual status of the physical operation and maintenance environment, and verify the data field information, including the matching degree, the accuracy of the association relationship, the consistency of the status and the time synchronization, and generate a data consistency verification report.

[0073] S45. For the discrepancies found in the data consistency verification report, analyze the causes of the discrepancies and perform corresponding operations, including data correction, model adjustment and environment verification, to ensure that the CMDB model data is completely synchronized with the physical environment.

[0074] The working principle and effects of the above technical solution are as follows: This status tracking and data synchronization solution parses timestamps to connect business nodes and establish a tracking link, improving the timeliness of operation and maintenance business status monitoring and reducing the problem of status ambiguity during execution; it integrates and compares two types of data to update real-time status, enhancing the accuracy of status information and avoiding management deviations caused by information lag; it synchronously writes back to the CMDB model according to rules to ensure data source uniformity and reduce data dispersion in the traditional model; it compares the physical environment to verify data consistency, avoiding the disconnect between model data and the actual environment and reducing decision-making errors caused by data deviations; it analyzes and handles the causes of discrepancies to ensure complete data synchronization, making the operation and maintenance status traceable throughout the process and building a solid foundation for data reliability, making the closed-loop management of the entire business flow more robust and the operation and maintenance decisions more evidence-based.

[0075] In one embodiment of the present invention, S41 includes:

[0076] Extract core information from the business execution timestamp data, including node identifier, time record, business association identifier and operation type, remove invalid and redundant time records, and generate core timestamp parsing data;

[0077] Based on the core parsing data of timestamps, the business nodes of each stage are sorted in chronological order, the connection order and dependency logic between nodes are sorted out, and node time sequence sorting data is generated.

[0078] Based on the node time sequence data, the execution start time, expected end time and actual end time of each node are defined, the node execution cycle and connection gap are clarified, and node time boundary data is generated.

[0079] Real-time monitoring of the execution dynamics of each node, recording the business execution status, progress completion ratio, specific time point of exception trigger, exception type, recovery operation and recovery duration, and generating real-time status data of the nodes;

[0080] By integrating node time-series sorting data, node time boundary data, and node real-time status data, a status tracking link is built that runs through the entire business process, forming complete operation and maintenance business status tracking data.

[0081] The working principle and effects of the above technical solution are as follows: This status tracking data generation method extracts core information and removes redundant records, improving data purity and reducing interference from invalid data in subsequent processing; it sorts node connections and dependencies by time, enhancing process coherence and avoiding tracking disorder caused by disordered node order; it defines node time boundaries, making execution cycles and connection gaps clearly visible, improving the accuracy of progress control; it monitors node dynamics in real time and records anomalies and recovery details, enhancing the comprehensiveness of status tracking and reducing the omission of anomalies; it integrates multiple types of data to build a full-process tracking link, making the status of operation and maintenance business traceable throughout the process and avoiding the problem of ambiguous status during the process; it can quickly grasp the execution status of each node and promptly locate the root cause of anomalies, making operation and maintenance management more targeted and reducing decision-making delays caused by unclear status.

[0082] In one embodiment of the present invention, S42 includes:

[0083] Extract the core fields from the structured execution result data. The core fields include the business unique identifier, node ID, final execution result, and result status code, and organize them to form the core execution result data.

[0084] Extract key information from the operation and maintenance business status tracking data. This key information includes business association identifiers, node identifiers, current execution status, progress percentage, and anomaly records to generate core status tracking data.

[0085] Based on the unique business identifier and node ID, establish the field correspondence between the core data of execution results and the core data of status tracking, and generate data association mapping data;

[0086] Based on the data association mapping data, the matching fields are compared in real time one by one to verify the consistency between the execution result and the current state, supplement the missing state information, correct the bias data, and generate the data fusion comparison result;

[0087] Based on the data fusion and comparison results, the overall business information is updated. The overall business information includes the execution status, the completion status of each node, the result identification attributes, and the progress completion ratio, which are integrated to form complete real-time status data of the operation and maintenance business.

[0088] The working principle and effects of the above technical solution are as follows: This data fusion and comparison method extracts the core information and key content of the two types of data, making processing more focused, improving data utilization efficiency, and reducing redundant information interference; it establishes an association mapping based on business and node identifiers, making data correspondence more accurate, enhancing the correlation between the two types of data, and avoiding field matching mismatches; it compares and verifies the consistency between the execution results and the current status in real time, supplements missing information and corrects deviations, improves the accuracy of status data, and avoids misleading management with erroneous information; it updates and integrates the overall execution status of the business and the completion status of nodes, making the real-time status of operation and maintenance clear and verifiable, reducing management troubles caused by ambiguous status; it can quickly grasp the dynamics of business progress and lay a solid foundation for subsequent data write-back, making operation and maintenance management smoother and more accurate.

[0089] In one embodiment of the present invention, S43 includes:

[0090] Extract the core elements from the data storage rules of the CMDB model. These core elements include field storage format, data association logic, storage hierarchy structure, and unique identifier field, and organize them to form the core data of the storage rules.

[0091] The fields of real-time status data and structured execution result data of operation and maintenance business are mapped to the target fields in the core data of storage rules, clarifying the field mapping relationship of data writing and generating field alignment mapping data;

[0092] Based on field alignment mapping data, the field format, data type and value range of the two types of data are adjusted to conform to the storage specifications of the CMDB model, and standardized write-back data is generated.

[0093] By matching the original data entries to be updated in the CMDB model using the unique identifier field, the location of the target data to be covered is located, and the target update entry location data is generated.

[0094] The standardized data is synchronously written back to the location pointed to by the target update entry, overwriting the original data content, integrating all updated model data entries, and generating updated CMDB model data.

[0095] The working principle and effects of the above technical solution are as follows: This data write-back method extracts the core elements of storage rules to organize data, making the write-back process systematic, improving operational standardization, and reducing the chaos of irregular writes; it clearly maps fields to enhance data alignment accuracy and avoids errors caused by field misalignment; it adjusts data formats to adapt to storage specifications, improving compatibility and reducing the trouble of writing due to incompatible formats; it locates target entries through unique identifiers, improving update accuracy and avoiding accidental modification of irrelevant data; it synchronously writes, overwrites, and integrates data, ensuring the timeliness and consistency of CMDB model data and avoiding conflicts between old and new data; it not only makes data write-back efficient and smooth but also maintains the regularity of model data, laying a solid foundation for subsequent consistency verification and making operation and maintenance data management more reliable.

[0096] In one embodiment of the present invention, step S5 includes:

[0097] S51. Extract key indicators from the updated CMDB model data. The key indicators include business response speed, execution success rate, resource utilization rate, fault recovery time, interface call latency, and data consistency compliance rate. Clarify the evaluation criteria and weight allocation of each indicator and generate indicator evaluation system data.

[0098] S52. Based on the data of the indicator evaluation system, calculate the scores of each indicator and sum them by weight to generate the operation and maintenance business stability index, which intuitively reflects the overall operation status of the operation and maintenance business.

[0099] S53. Analyze the stability index of operation and maintenance business and the scores of each indicator, identify the risk points, process bottlenecks, model configuration defects, interface adaptation problems, etc. corresponding to index anomalies, and generate a problem analysis report.

[0100] S54. For the various problems in the problem analysis report, formulate targeted measures, including risk prevention and control measures, process optimization plans, model adjustment strategies, interface adaptation rule update suggestions, etc., and generate operation and maintenance business risk warning and optimization data;

[0101] S55. Apply the risk warning and optimization data of operation and maintenance business to the corresponding links. The corresponding links include CMDB model adjustment, scenario orchestration process optimization, interface adaptation rule update and orchestration engine parameter tuning. Continuously iterate and improve the operation and maintenance business management mechanism to form a closed-loop management of full business flow data.

[0102] The working principle and effects of the above technical solution are as follows: This closed-loop optimization method extracts multi-dimensional key indicators to establish an evaluation system, improving the comprehensiveness of operation and maintenance business evaluation and avoiding biased judgments caused by single indicators; weighted calculation of stability index makes the overall operating status intuitively visible, enhancing the control of operation and maintenance. Analyzing the index and indicator scores accurately identifies risk points, process bottlenecks, and configuration defects, reducing the omission of potential problems; formulating targeted prevention and control measures and optimization plans reduces the probability of failure; reverse application of optimization data iterates and improves the management mechanism, allowing CMDB models, scenario orchestration, interface adaptation, etc., to continuously adapt to business needs, avoiding rigid management models; it can not only provide real-time early warning of operation and maintenance risks, but also promote the self-upgrading of the management system, making the full business flow management more resilient and efficient, and ensuring the stable and smooth progress of operation and maintenance business.

[0103] One embodiment of the present invention, such as Figure 2 As shown, a system for implementing the operation and maintenance business management method based on CMDB data model and scenario orchestration as described in claim 1, the system comprising:

[0104] Platform construction module: This module constructs a visual custom CMDB model for operation and maintenance business data, including defining model attributes, model relationships, and model views, generating initial CMDB model data. This initial CMDB model data includes basic CRUD (Create, Read, Update, Query) management capabilities for business data. Based on the initial CMDB model data, a unified data interface and front-end UI are automatically generated and processed to construct an operation and maintenance business data management platform. This platform has a unified data consumption interface.

[0105] Data Acquisition Module: Based on the event-driven dynamic orchestration engine configuration of the operation and maintenance business data management platform, the module transforms operation and maintenance scenarios into executable workflows, generates operation and maintenance scenario orchestration workflow data, and collects full business flow data through the operation and maintenance scenario orchestration workflow data to obtain raw operation and maintenance business data and business execution timestamp data; it also performs data preprocessing on the raw operation and maintenance business data to generate standardized operation and maintenance business data.

[0106] Business execution module: Based on standardized operation and maintenance business data, it performs model-driven interface calls, automatically adapts the unified RESTful / gRPC interface to different business scenarios, and generates adapted operation and maintenance business interface data; it executes operation and maintenance business through the adapted operation and maintenance business interface data, and performs structured processing on the execution results to generate structured execution result data;

[0107] Write-back processing module: Performs status tracking processing on operation and maintenance business using business execution timestamp data to generate operation and maintenance business status tracking data; performs status update write-back processing on operation and maintenance business status tracking data using structured execution result data, writes the execution results back to the CMDB model, and generates updated CMDB model data; performs consistency verification on the updated CMDB model data to ensure that the model status is consistent with the physical environment;

[0108] Optimization module: Based on the updated CMDB model data, a weighted stability index is evaluated to generate an operation and maintenance business stability index; based on the operation and maintenance business stability index, risk warnings and process optimization are performed to generate operation and maintenance business risk warning and optimization data, realizing closed-loop management of all business flow data.

[0109] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A method for operation and maintenance business management based on CMDB data model and scenario orchestration, characterized in that, The method includes: S1. Construct a visual custom CMDB model for operation and maintenance business data, generate initial CMDB model data, and automatically generate and process unified data interfaces and front-end UI to build an operation and maintenance business data management platform. S2. Configure the event-driven dynamic orchestration engine according to the operation and maintenance business data management platform to transform the operation and maintenance scenario into an executable workflow, generate operation and maintenance scenario orchestration workflow data, and collect full business flow data to obtain raw operation and maintenance business data and business execution timestamp data; perform data preprocessing on the raw operation and maintenance business data to generate standardized operation and maintenance business data. S3. Based on standardized operation and maintenance business data, perform model-driven interface calls to automatically adapt the unified RESTful / gRPC interface to different business scenarios and generate adapted operation and maintenance business interface data; execute operation and maintenance business through the adapted operation and maintenance business interface data, and perform structured processing on the execution results to generate structured execution result data. S4. Perform status tracking processing on operation and maintenance business through business execution timestamp data to generate operation and maintenance business status tracking data; perform status update and write-back processing on operation and maintenance business status tracking data through structured execution result data, write the execution results back to the CMDB model, and generate updated CMDB model data. S5. Based on the updated CMDB model data, perform a weighted stability index assessment to generate an operation and maintenance business stability index; based on the operation and maintenance business stability index, perform risk warning and process optimization processing to generate operation and maintenance business risk warning and optimization data.

2. The operation and maintenance business management method based on CMDB data model and scenario orchestration according to claim 1, characterized in that, S1 includes: S11. Collect all basic data of operation and maintenance business, clarify the core attributes of CMDB model one by one based on the visual operation interface, define the core elements, and generate basic data of model attributes. S12. Supplement detailed parameters to the basic data of model attributes, improve the attribute configuration dimensions, and generate complete configuration data for model attributes. S13. Organize the hierarchical relationships, dependency logic, and associated constraints of different operation and maintenance business objects, build a two-way association system between models, clarify the mapping rules of associated fields, and generate model relationship configuration data. S14. Integrate the complete configuration data of model attributes and the configuration data of model relationships, design a multi-dimensional model view, configure the corresponding information, and generate the model view configuration data; S15. Integrate complete configuration data of model attributes, configuration data of model relationships, and configuration data of model views to form initial CMDB model data. Based on this data, build a unified data interaction specification, automatically generate standardized data consumption interfaces and modular front-end interaction interfaces, and construct an operation and maintenance business data management platform.

3. The operation and maintenance business management method based on CMDB data model and scenario orchestration according to claim 1, characterized in that, The S2 includes: S21. Deploy an event-driven dynamic orchestration engine based on the operation and maintenance business data management platform, configure basic settings, and generate basic configuration data for the orchestration engine. S22. Decompose various operation and maintenance business scenarios, sort them out, transform the scenarios into standardized and executable workflow nodes, and generate scenario node decomposition data; S23. Configure each workflow node, connect all nodes to form a complete workflow, and generate operation and maintenance scenario orchestration workflow data; S24. Guided by the workflow data of operation and maintenance scenarios, start the full business flow data collection mechanism to capture process data in the process of operation and maintenance business. S25. Preprocess the collected raw data to eliminate data redundancy and inconsistency, and generate standardized operation and maintenance business data that conforms to unified standards.

4. The operation and maintenance business management method based on CMDB data model and scenario orchestration according to claim 3, characterized in that, S22 includes: Break down various operation and maintenance business scenarios, organize them, transform the scenarios into standardized and executable workflow nodes, and generate scenario node breakdown data; Classify operation and maintenance business scenarios according to business attributes, distinguish the core objectives and applicable scope of each scenario, and generate scenario classification data. Based on the scenario classification data, the core links of each scenario are broken down one by one, unnecessary processes are removed, key execution nodes of the scenario are extracted, and scenario core link breakdown data is generated. The data is broken down for the core links of the scenario, and the execution logic, participating objects, triggering conditions, execution order and branch judgment rules of each link are sorted out. The relationship logic between each element is clarified and the scenario link element data is generated. Referring to the unified workflow node specification, the scenario element data is transformed into executable workflow nodes with a unified structure and clear definition, clarifying the core functions and boundaries of each node, and generating the initial version of scenario node data; Verify the completeness, logical coherence, and executability of the initial version of the scene node data, correct deviations in node definitions and missing elements, and form standardized scene node decomposition data.

5. The operation and maintenance business management method based on CMDB data model and scenario orchestration according to claim 1, characterized in that, The S3 includes: S31. Extract interface call requirements for different business scenarios from standardized operation and maintenance business data, clarify key information of the requirements, and generate interface call requirement data. S32. Based on the interface call requirement data, start the model-driven interface adaptation mechanism to automatically match the corresponding RESTful or gRPC interface and generate the adapted operation and maintenance business interface data. S33. Perform connectivity testing, data transmission verification, and response speed testing on the adapted operation and maintenance business interface data to verify the effectiveness of interface adaptation and generate interface adaptation verification result data. S34. Based on the interface adaptation verification result data, trigger the corresponding operation and maintenance business execution process through the adapted interface, record the execution information in real time during the business execution process, and generate business execution process data. S35. Classify and organize the business execution process data and final execution results, standardize the fields, complete the related information and mark the result status, and transform them into structured execution result data with a unified structure.

6. The operation and maintenance business management method based on CMDB data model and scenario orchestration according to claim 1, characterized in that, The S4 includes: S41. Parse the business execution timestamp data, connect the nodes of each stage of the operation and maintenance business in chronological order, establish a status tracking link, capture status information in real time, and generate operation and maintenance business status tracking data. S42. Perform real-time fusion and comparison between structured execution result data and operation and maintenance business status tracking data, update business execution status information, result identifiers and node completion status, and generate real-time operation and maintenance business status data. S43. According to the data storage rules of the CMDB model, synchronize the real-time status data of operation and maintenance business and the structured execution result data back to the CMDB model, overwrite the original corresponding data entries, and generate updated CMDB model data. S44. Compare the updated CMDB model data with the actual status of the physical operation and maintenance environment, verify the data field information, and generate a data consistency verification report. S45. For the discrepancies found in the data consistency verification report, analyze the causes of the discrepancies and perform corresponding operations.

7. The operation and maintenance business management method based on CMDB data model and scenario orchestration according to claim 6, characterized in that, S41 includes: Extract core information from business execution timestamp data, remove invalid and redundant time records, and generate core timestamp parsing data; Based on the core parsing data of timestamps, the business nodes of each stage are sorted in chronological order, the connection order and dependency logic between nodes are sorted out, and node time sequence sorting data is generated. Based on the node time sequence data, the execution start time, expected end time and actual end time of each node are defined, the node execution cycle and connection gap are clarified, and node time boundary data is generated. Real-time monitoring of the execution dynamics of each node, recording the business execution status, progress completion ratio, specific time point of exception trigger, exception type, recovery operation and recovery duration, and generating real-time status data of the nodes; By integrating node time-series sorting data, node time boundary data, and node real-time status data, a status tracking link is built that runs through the entire business process, forming complete operation and maintenance business status tracking data.

8. The operation and maintenance business management method based on CMDB data model and scenario orchestration according to claim 6, characterized in that, S42 includes: Extract the core fields from the structured execution result data and organize them to form the core execution result data; Extract key information from the operation and maintenance business status tracking data to generate core status tracking data; Based on the unique business identifier and node ID, establish the field correspondence between the core data of execution results and the core data of status tracking, and generate data association mapping data; Based on the data association mapping data, the matching fields are compared in real time one by one to verify the consistency between the execution result and the current state, supplement the missing state information, correct the bias data, and generate the data fusion comparison result; Based on the data fusion and comparison results, update the overall business information and integrate it to form complete real-time status data of operation and maintenance business.

9. The operation and maintenance business management method based on CMDB data model and scenario orchestration according to claim 1, characterized in that, The S5 includes: S51. Extract key indicators from the updated CMDB model data, clarify the evaluation criteria and weight allocation of each indicator, and generate indicator evaluation system data. S52. Based on the data of the indicator evaluation system, calculate the scores of each indicator and sum them by weight to generate the operation and maintenance business stability index, which intuitively reflects the overall operation status of the operation and maintenance business. S53. Analyze the stability index of operation and maintenance services and the scores of each indicator, and generate a problem analysis report; S54. Develop targeted measures for various issues identified in the problem analysis report, and generate operational and maintenance business risk warnings and optimization data; S55. Apply the risk warning and optimization data of operation and maintenance business to the corresponding links, continuously iterate and improve the operation and maintenance business management mechanism, and form a closed-loop management of the entire business flow data.

10. A system for implementing the operation and maintenance business management method based on CMDB data model and scenario orchestration as described in claim 1, characterized in that, The system includes: Platform construction module: Builds a visual custom CMDB model for operation and maintenance business data, generating initial CMDB model data; Based on the initial CMDB model data, it automatically generates and processes a unified data interface and front-end UI to build an operation and maintenance business data management platform; Data Acquisition Module: Based on the event-driven dynamic orchestration engine configuration of the operation and maintenance business data management platform, the module transforms operation and maintenance scenarios into executable workflows, generates operation and maintenance scenario orchestration workflow data, performs full business flow data acquisition, and obtains raw operation and maintenance business data and business execution timestamp data; it also performs data preprocessing on the raw operation and maintenance business data to generate standardized operation and maintenance business data. Business execution module: Based on standardized operation and maintenance business data, it performs model-driven interface calls, automatically adapts the unified RESTful / gRPC interface to different business scenarios, and generates adapted operation and maintenance business interface data; it executes operation and maintenance business through the adapted operation and maintenance business interface data, and performs structured processing on the execution results to generate structured execution result data; Write-back processing module: Performs status tracking processing on operation and maintenance business using business execution timestamp data to generate operation and maintenance business status tracking data; performs status update write-back processing on operation and maintenance business status tracking data using structured execution result data, writes the execution results back to the CMDB model, and generates updated CMDB model data; Optimization module: Based on the updated CMDB model data, a weighted stability index is evaluated to generate an operation and maintenance business stability index; based on the operation and maintenance business stability index, risk warnings and process optimizations are performed to generate operation and maintenance business risk warnings and optimization data.

Images