A method for generating a standardized deployment and implementation package for intelligent operation and maintenance of large generators
By establishing an implementation package object model and a dependency closure mechanism, standardized deployment and acceptance mapping lists are generated, solving the problems of consistency and replicability of implementation results for intelligent operation and maintenance capabilities of large generators, and realizing the transformation from project experience-based integration to standardized products.
Patent Information
- Application Number
- CN202611204290.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-10
- Publication Date
- 2026-11-17
AI Technical Summary
The lack of a systematic implementation package generation mechanism in existing technologies makes it difficult to form a large-scale engineering product for intelligent operation and maintenance of large generators. This results in problems such as poor consistency of implementation results, unclear dependencies, missing version identification, and disconnected acceptance.
By establishing a unified implementation package object model, identifying candidate capability units, performing dependency closure unpacking and conflict checks, generating standardized deployment and acceptance mapping lists, and freezing implementation package versions, a deployable, acceptable, and reproducible implementation package is formed.
This has enabled the transformation of intelligent operation and maintenance capabilities for large generators from project experience-based integration to standardized products, ensuring the replicability, inheritability, and upgradeability of the implementation package, and reducing the risks and costs of deployment and acceptance.
Smart Images

Figure CN123114491A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of engineering encapsulation and standardized implementation technology of intelligent operation and maintenance capabilities for large generators, and in particular to a method for generating a standardized deployment and implementation package for intelligent operation and maintenance of large generators. Background Technology
[0002] As the capacity of large generator units continues to increase and their operating conditions become increasingly complex, their intelligent operation and maintenance capabilities have evolved from the development stage of single algorithms or software modules to a comprehensive technical system encompassing multiple dimensions, including data foundation, object rules, image and signal analysis, knowledge agents, evidence delivery, and collaborative interfaces. However, the key bottleneck in engineering implementation no longer lies in breakthroughs in individual capabilities, but rather in how to integrate these heterogeneous capabilities into a tangible, replicable, and acceptable overall implementation unit. As industrial equipment with clear object boundaries, complex component structures, significant differences in operating conditions, and stringent delivery requirements, the engineering deployment of large generators naturally demands a unified organizational method and standardized packaging form for their operation and maintenance capabilities. Without a systematic implementation package generation mechanism, even if various intelligent operation and maintenance capabilities have reached a certain level of technological maturity, their transformation into actual engineering projects will remain at a project-experience-based integration stage for a long time, making it difficult to form scalable engineering products.
[0003] In existing practices, when faced with different unit types and project requirements, implementation teams typically combine necessary data modules, rule bases, analysis tools, workflow configurations, interface mappings, and delivery documents based on project experience. These are then manually compiled into deployment instructions, acceptance materials, and on-site implementation plans. While this model can achieve delivery at the case-by-case level, it has several inherent flaws: First, the same set of technical capabilities presents different combinations and boundary divisions in different projects, leading to inconsistent implementation results. Second, the lack of a unified encapsulation structure and explicit description of data models, object rules, analysis modules, workflows, knowledge bodies, and interface dependencies necessitates repeated review and reconfirmation of dependencies during replication, resulting in low efficiency and a high risk of errors. Third, the implementation output lacks clear version identification and applicable boundary definitions, failing to inherit existing results and hindering support for subsequent iterations and upgrades; a new implementation baseline must be established for each new project. Fourth, the lack of a pre-defined mapping relationship between acceptance objects and implementation units means acceptance materials are often compiled separately after implementation, leading to a disconnect between deployment and acceptance, increasing later rectification costs and delivery risks.
[0004] Therefore, existing technologies urgently need a standardized implementation package generation method for intelligent operation and maintenance of large generators. By establishing a unified implementation package object model, capability unit organization specifications, dependency closure expansion mechanism, applicable boundary trimming rules, and version freezing process, existing intelligent operation and maintenance capabilities can be transformed from "project experience-based combinations" to "structured implementation package outputs." This ensures that the implementation package, from its inception, forms a clear organizational relationship and traceable delivery boundaries with unit objects, component objects, operating condition objects, interface objects, and acceptance objects. This will enable the transformation of intelligent operation and maintenance capabilities for large generators from one-time engineering deliverables to a standardized product form that is replicable, inheritable, and upgradable. Summary of the Invention
[0005] The main objective of this invention is to provide a method for generating a standardized deployment implementation package for intelligent operation and maintenance of large generators.
[0006] Another object of the present invention is to provide an electronic device.
[0007] A third objective of this invention is to provide a non-transitory computer-readable storage medium.
[0008] To achieve the above objectives, a first aspect of the present invention proposes a method for generating a standardized deployment implementation package for intelligent operation and maintenance of large generators, comprising: Read existing capability libraries, rule libraries, interface libraries, and template libraries to identify candidate capability units that can be included in the implementation package, and establish an implementation package target profile based on the target application scope and target scenario. The target profile includes unit scope, component scope, operating condition scope, data conditions, delivery boundaries, and acceptance requirements. From the candidate capability units, capability units that meet the target profile are selected. Dependency closure expansion is performed on the selected capability unit set to supplement the missing prerequisite units and supporting rules into the capability unit set, forming a candidate implementation package. Conflict checks and applicable boundary pruning are performed on the candidate implementation packages, and standard implementation packages, enhanced implementation packages, or degraded implementation packages are generated based on the pruning results; A deployment list and an acceptance mapping list are generated for the generated implementation package. After the deployment list and the acceptance mapping list are generated, the implementation package version is frozen, forming a deployable, acceptable, and reproducible implementation package object.
[0009] Optionally, based on the target application scope and target scenario, an implementation package target profile can be established, including: Based on the target application scope, determine the set of unit types and component range to which the implementation package applies; Based on the target scenario, determine the applicable operating conditions range for the implementation package; Based on the target application scope and the target scenario, determine the minimum data scope and data conditions required for the implementation package, as well as the delivery boundaries and acceptance requirements of the implementation package. The delivery boundaries include the minimum deliverables and the scope of deliverables, and the acceptance requirements include the acceptance objects and acceptance pass conditions.
[0010] Optionally, capability units that satisfy the target profile are selected from the candidate capability units. Dependency closure expansion is performed on the selected capability unit set to supplement the missing prerequisite units and supporting rules into the capability unit set, forming a candidate implementation package, including: The range of units, components, operating conditions, data conditions, delivery boundaries, and acceptance requirements in the target profile are matched and compared with the applicable scope, minimum input requirements, output object set, delivery dependencies, and acceptance dependencies of each candidate capability unit to obtain the matching results of each candidate capability unit in each dimension. Based on the matching results, the candidate capability units are divided into target units and extended units. Target units are capability units that cannot be implemented if they are missing, while extended units are capability units that do not affect the implementation of the package but affect the package's enhanced capabilities if they are missing. The target unit and the extended unit are retained to form a set of filtered capability units.
[0011] Optionally, dependency closure expansion is performed on the selected set of capability units to supplement the missing prerequisite units and supporting rules into the set of capability units, forming a candidate implementation package, including: The selected set of capability units is used as the initial set for closure computation. The dependent objects of each capability unit are checked layer by layer. The dependent objects include object dependencies, data dependencies, process dependencies, interface dependencies, delivery dependencies and acceptance dependencies. The missing prerequisite units and supporting rules are added to the capability unit set layer by layer until no new missing dependencies are generated, thus completing the dependency closure expansion and forming a candidate implementation package.
[0012] Optionally, conflict checking and applicable boundary trimming are performed on the candidate implementation packages, including: Each capability unit in the candidate implementation package is subjected to pairwise conflict detection, wherein the conflict includes at least version conflicts of the same object rule, version conflicts of the same interface, and mutual exclusion conflicts of the process order. The degree of conflict is determined based on the conflict detection results. If the degree of conflict exceeds the threshold, the candidate implementation package is returned to be pruned to eliminate conflict dependencies before further processing. Based on the unit scope, component scope, operating condition scope, data conditions, delivery boundaries, and acceptance requirements in the target profile, capability units in the candidate implementation package that exceed the applicable boundaries are trimmed and eliminated to obtain the trimmed candidate implementation package.
[0013] Optionally, a standard implementation package, an enhanced implementation package, or a downgraded implementation package can be generated based on the tailoring results, including: If the candidate implementation package after trimming has complete target units, complete dependency closures, and meets the minimum delivery and acceptance requirements, then a standard implementation package is generated. If an enhanced implementation package is generated by further including extended units on top of the standard implementation package and having enhanced delivery and collaboration capabilities; If the target unit is complete but some expansion capabilities are removed, and the minimum implementable and minimum acceptable skeletons are still retained, then a downgraded implementation package is generated.
[0014] Optionally, a deployment manifest and an acceptance mapping manifest are generated for the generated implementation package. After the deployment manifest and the acceptance mapping manifest are generated, the implementation package version is frozen, forming a deployable, acceptable, and reproducible implementation package object, including: Based on the set of capability units in the generated implementation package, an object binding list, a data access list, an interface list, a workflow list, a delivery initialization list, and a risk and prohibition condition list are generated, which together constitute the deployment list; Based on the set of capability units and the set of deliverables in the generated implementation package, the necessary acceptance objects, the acceptance inspection items corresponding to each acceptance object, and the minimum pass threshold are determined, and a set of traceability requirements and version consistency inspection items are generated, which together constitute the acceptance mapping list. After generating the deployment list and the acceptance mapping list, verify that the target units of the current implementation package are complete, the dependency closures are complete, there are no high conflict dependencies, the minimum deliverables are available, and the minimum acceptance items are executable. When all verification conditions are met, freeze the implementation package version as the official version to form a deployable, acceptable, and reproducible implementation package object.
[0015] To achieve the above objectives, a second aspect of this application provides an electronic device, including a processor and a memory; wherein the processor reads executable program code stored in the memory to run a program corresponding to the executable program code, for implementing a standardized deployment implementation package generation method for intelligent operation and maintenance of large generators as described in the first aspect embodiment.
[0016] To achieve the above objectives, a third aspect of this application provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements a method for generating a standardized deployment implementation package for intelligent operation and maintenance of a large generator as described in the first aspect embodiment.
[0017] The embodiments of the present invention have the following beneficial effects: (1) This method establishes a unified implementation package object as a capability-bearing unit, so that data models, object rules, analysis modules, workflows, knowledge bodies, interface mappings and delivery templates are combined in a structured and controlled manner, which solves the problem that the intelligent operation and maintenance capabilities of large generators have long remained in the project experience-based integration state due to the lack of a unified encapsulation object.
[0018] (2) This method uses capability unit screening rules and dependency closure mechanism to explicitly organize the object dependency, data dependency, process dependency, interface dependency and acceptance dependency relationships between capability units in the implementation package generation stage. It also automatically excludes capability units that exceed the applicable conditions by combining applicable boundary trimming rules, thus eliminating the risk of deployment failure caused by missing dependencies or unclear boundaries during the replication implementation process.
[0019] (3) This method outputs the deployment list and acceptance mapping list simultaneously during the implementation package generation stage, so that the implementation package has object binding relationship, interface access requirements, workflow activation configuration, acceptance check items and minimum pass threshold from the beginning of generation. A traceable one-to-one correspondence is formed between deployment and acceptance, which reduces the later rectification cost and delivery risk.
[0020] (4) This method establishes a three-level classification system of standard implementation packages, enhanced implementation packages and degraded implementation packages, so that the same set of capability units can output implementation packages of different specifications according to the data completeness and delivery requirements of different projects. This maintains the standardization of core capabilities and takes into account the feasibility of different scenarios, providing a unified technical foundation for the replication, promotion and industrialization of large generator intelligent operation and maintenance capabilities within the group.
[0021] (5) This method establishes a version freezing and difference recording mechanism, so that each generated implementation package retains complete information on the capability unit version, rule version, interface version, delivery version and acceptance version, and records the differences between the implementation package and the source package, so that the implementation package has the product attributes of being inheritable, upgradable and auditable, and realizes the transformation of the intelligent operation and maintenance capability of large generators from a one-time engineering delivery to a standardized product form that can be continuously evolved. Attached Figure Description
[0022] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a flowchart illustrating a method for generating a standardized deployment implementation package for intelligent operation and maintenance of large generators, as provided in an embodiment of the present invention. Detailed Implementation
[0023] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.
[0024] 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.
[0025] The following describes, with reference to the accompanying drawings, a method for generating a standardized deployment implementation package for intelligent operation and maintenance of large generators according to an embodiment of the present invention.
[0026] Example 1 This invention provides a method for generating a standardized deployment implementation package for intelligent operation and maintenance of large generators. Figure 1 This is a flowchart illustrating a method for generating a standardized deployment implementation package for intelligent operation and maintenance of a large generator, as provided in an embodiment of the present invention. Figure 1 As shown, the method includes the following steps: Step S1: Read the existing capability library, rule library, interface library and template library, identify candidate capability units that can enter the implementation package, and establish the implementation package target profile according to the target application scope and target scenario. The target profile includes the unit scope, component scope, operating condition scope, data conditions, delivery boundary and acceptance requirements.
[0027] This step, as the foundational stage of the entire implementation package construction process, plays a crucial role in collecting basic resources, initially identifying candidate capabilities, quantifying and defining scenario goals, and constructing the implementation package target profile. It provides a unified, quantifiable, and standardized boundary basis for all subsequent unit selection, dependency completion, package trimming, and level classification work. In the specific implementation process, the system first batch-reads the four core resource libraries pre-stored on the platform: the capability library, rule library, interface library, and template library. It comprehensively retrieves various fixed operation and maintenance capability units, operation and maintenance adaptation rules, cross-module interaction interfaces, standardized delivery templates, and other resource data from these libraries. Based on the unit attributes, functional positioning, adaptation scope, and output characteristics of each resource, it initially identifies and collects all capability resources with the potential to be included in the operation and maintenance implementation package, forming an initial set of candidate capability units.
[0028] It should be noted that the candidate capability units obtained through the resource library are only a general set of basic resources, with a wide range of adaptability but weak scenario specificity, and cannot directly match the customized operation and maintenance needs of specific units, specific operating conditions, or specific projects. Therefore, this step needs to combine the target application scope and target operation and maintenance scenario of the current project to construct a specific implementation package target profile, accurately defining the unit adaptation boundaries, component adaptation boundaries, operating condition boundaries, basic data conditions, deliverable boundaries, and acceptance standard requirements of this implementation package. To achieve standardized and quantitative definition of adaptation boundaries and unify the data caliber throughout the entire process, this application embodiment specifically defines an applicable scope object ScopeObj, which is used to structurally and parametrically represent the full-dimensional adaptation attributes of the implementation package. The specific expression of this applicable scope object is: ScopeObj =<ScopeID,UnitTypeSet,PartScope,CondScope,DataScope,DeliverScope,CollaborateScope> .
[0029] Among them, ScopeID is a unique identifier for the applicable scope, used to uniquely distinguish the adaptation scope model of different scenarios and versions; UnitTypeSet is the set of unit types that the implementation package can adapt to, limiting the types of large generator models supported by this implementation package; PartScope is the applicable scope of the unit components corresponding to the implementation package, clarifying the boundaries of the core components and auxiliary components of the unit covered by operation and maintenance; CondScope is the range of unit operating conditions that the implementation package adapts to, limiting various adaptable operating conditions such as steady state, transient state, and variable load; DataScope is the minimum data range required for the normal operation of the implementation package, defining the bottom line of basic data, historical data, and ledger information required to start the operation and maintenance process and execute the capability unit; DeliverScope is the delivery boundary range corresponding to the implementation package, specifying the types, formats, and content range of the final output deliverables; CollaborateScope is the multi-party collaborative operation and maintenance range that the implementation package adapts to, adapting to multi-party collaborative operation scenarios of OEMs, owners, and maintenance units.
[0030] Optionally, in this embodiment, the refined construction logic of the target profile strictly corresponds to the parameter dimensions of the applicable scope objects, achieving a one-to-one correspondence between the profile content and the structured model. Specifically, during the construction process, firstly, based on the project's target application scope, the set of unit types adapted to this implementation package and the corresponding coverage of core unit components are precisely determined; secondly, based on the project's target operation and maintenance scenario, the range of unit operating conditions that this implementation package can stably adapt to and operate compliantly is defined, eliminating invalid adaptation conditions that exceed operating conditions or scenarios; thirdly, combining the dual constraints of the target application scope and the target scenario, the minimum data items, data formats, and data completeness conditions required for the implementation package's operation are clarified, locking in the basic data threshold; finally, the delivery boundaries and acceptance requirements of the implementation package are precisely defined, whereby the delivery boundaries clearly define the complete scope of the minimum delivery objects, core deliverables, and auxiliary deliverables, and the acceptance requirements clearly define the operation and maintenance objects covered by acceptance, item-by-item inspection standards, and quantified acceptance thresholds. The final target profile fully covers six core dimensions: unit scope, component scope, operating condition scope, data conditions, delivery boundaries, and acceptance requirements. It is strictly matched and aligned with the ScopeObj object model, providing a standardized and quantitative basis for the accurate matching and selection of subsequent candidate capability units.
[0031] Step S2: Select capability units that meet the target profile from the candidate capability units, perform dependency closure expansion on the selected capability unit set, and add the missing predecessor units and supporting rules into the capability unit set to form a candidate implementation package.
[0032] Building upon the foundational resource acquisition, initial candidate unit collection, and standardized implementation package target profile construction completed in S1, this step involves refined capability unit adaptation and screening, unit attribute classification, multi-level dependency completion, and global dependency closure expansion. The result is a candidate implementation package that is functionally complete, dependency-rich, clearly defined, and suitable for subsequent tailoring and tiering. Notably, this step abandons the traditional, extensive manual screening approach, relying instead on a standardized capability unit model and a quantitative adaptation scoring algorithm to achieve automated and precise screening. This effectively addresses industry-wide issues such as poor adaptability, ambiguous boundaries, excessive redundant units, and missing dependencies inherent in manual screening.
[0033] To standardize the definition of the minimum functional unit of the operation and maintenance implementation package and unify the structured parameter format of all capability resources, this application defines a capability unit object CapUnit as the basic encapsulation carrier of all operation and maintenance capabilities. Its specific expression is: CapUnit = <UnitID,UnitType,InputNeedSet,OutputObjSet,RuleNeedSet,FlowNeedSet,InterfaceNeedSet,DeliverNeedSet,AcceptNeedSet,UnitVer> .
[0034] Among them, UnitID is a globally unique identifier for the capability unit, used to distinguish different functions and types of operation and maintenance capability units; UnitType is the capability unit type, covering at least eight types: data foundation unit, object rule unit, analysis unit, evidence management unit, knowledge body unit, workflow unit, interface unit, and delivery unit, comprehensively covering the entire chain of capabilities for data, rules, analysis, process, delivery, and acceptance in the entire operation and maintenance process of large generators; InputNeedSet is the minimum set of input requirements required for the operation of the capability unit, clarifying the basic data and prerequisites for the unit to start execution; OutputObjSet is the set of output objects generated after the capability unit is executed, representing the core operation and maintenance results and data output of the unit; RuleNeedSet is the set of rules to be called during the operation of the capability unit; FlowNeedSet is the set of operation and maintenance processes that the capability unit adapts to and connects with; InterfaceNeedSet is the set of interfaces required for the interaction and communication of the capability unit; DeliverNeedSet is the delivery dependency condition corresponding to the capability unit; AcceptNeedSet is the acceptance dependency condition corresponding to the capability unit; UnitVer is the version number of the capability unit, used to manage the unit's iterative updates and version consistency adaptation.
[0035] Furthermore, to achieve quantitative admission and precise screening of candidate capability units, this application embodiment constructs a unit adaptation scoring model for any candidate capability unit. and the target profile that has been built Define the unit adaptation score calculation formula:
[0036] in, The comprehensive adaptation score is given to the corresponding candidate capability unit. The higher the score, the stronger the adaptability, matching degree and practicality of the unit with the current target scenario and target requirements. , , , , These are the preset weight coefficients for each evaluation dimension, which can be configured differently according to the priority of the operation and maintenance scenario.
[0037] It should be noted that the specific definitions and quantification logic of each core parameter within the formula are as follows: To assess the applicability matching degree, this mainly characterizes the degree of consistency between the capability unit and the boundary conditions corresponding to the target profile in three core dimensions: unit type adaptation, component coverage, and operating condition adaptation. Data condition matching degree represents the degree of completeness of the matching between the existing data resources reserved by the current operation and maintenance project and the minimum input data requirements required for the normal operation of the capability unit; To determine the delivery requirement matching degree, the output results, data objects and functional effects of the capability unit are characterized as whether they can directly support the target delivery requirements and delivery indicators of this implementation package. The degree of matching with acceptance requirements indicates whether the capability unit is an essential unit for achieving the target acceptance item, meeting the acceptance criteria, and ensuring acceptance. The penalty value is a mismatch value assigned when the required operating conditions, basic data, interaction interfaces, and collaborative conditions of a capability unit significantly exceed the adaptation boundaries of the current target scenario. This penalty value lowers the overall adaptation score and automatically suppresses and filters invalid and over-fit units. This application pre-sets a fixed unit filtering threshold. When the calculation is obtained When the current scenario is deemed suitable, the unit is allowed to enter the formal candidate unit set; when If the compatibility is deemed insufficient, it will not be included in the implementation package construction system.
[0038] Optionally, this application employs a multi-dimensional, full-element comparison method to complete the refined screening process. The six core dimensions of the target profile—unit scope, component scope, operating condition scope, data conditions, delivery boundaries, and acceptance requirements—are precisely matched against the applicable scope, minimum input requirements, output object set, delivery dependencies, and acceptance dependencies of each candidate capability unit. This accurately obtains the matching results and adaptation shortcomings of each unit across different dimensions. Notably, this application categorizes qualified units after admission into two types based on their impact on the overall functionality of the implementation package: core units and extended units. Core units are the basic framework units for the implementation package; the absence of any core unit directly leads to the implementation package's functional failure, inability to be formed, and inability to meet basic operation and maintenance and delivery acceptance requirements. Extended units are capability enhancement units for the implementation package. The absence of these units does not cause the overall implementation package to fail or affect basic deployment, but it reduces the implementation package's functional richness, scenario adaptability, and collaborative operation and maintenance capabilities. This classification provides a core basis for subsequent implementation package grading, trimming, and downgrading.
[0039] To thoroughly resolve the issues of missing prerequisite dependencies, incomplete supporting rules, and broken process connections between capability units, this application implements a systematic dependency closure unpacking process on the selected set of qualified capability units. To standardize the definition of the association constraints between units, this application defines a dependency object DepObj, used to structurally represent the dependencies of all units, with the specific expression: DepObj =<DepID,SrcUnit,TarUnit,DepType,MandatoryFlag,DepVer> Among them, DepID is the unique identifier of the dependency relationship; SrcUnit is the source front-end unit corresponding to the dependency relationship, providing basic support for the back-end unit; TarUnit is the target dependency unit that needs front-end support; DepType is the dependency type, which includes at least six types of dependencies covering object dependencies, data dependencies, process dependencies, interface dependencies, delivery dependencies, and acceptance dependencies; MandatoryFlag is the mandatory dependency flag, used to determine whether the current dependency is a necessary condition for the normal operation of the target unit; DepVer is the version constraint corresponding to the dependency, ensuring that the versions of the front-end and back-end units are compatible.
[0040] Based on a standardized dependency object model, this application defines a dependency closure calculation formula to achieve fully automatic completion iteration of multi-level dependencies. The specific formula is: Closure(CoreSet) = CoreSet ∪ Dep1 ∪ Dep2 ∪ ... ∪ Depn. Here, CoreSet is the initial set of core units after filtering, serving as the baseline for closure calculation; Depk represents the set of dependency units at the k-th level, with the number of levels dynamically and adaptively determined based on the actual dependency iteration depth. During closure calculation, the system iterates through all mandatory dependencies of all units layer by layer, incorporating all mandatory dependency units with MandatoryFlag set to true and triggered by the unit at the previous level into the set layer by layer, iterating and completing the dependency until the entire set of units no longer generates new missing dependencies, ultimately forming a complete candidate implementation package unit set with complete dependencies, smooth processes, and functional closure.
[0041] Furthermore, to quantify the completeness of dependency completion and control the basic quality of candidate implementation packages, this application defines a dependency satisfaction rate calculation formula:
[0042] in, This represents the total number of all dependencies required for the current implementation package to run completely, including all levels of mandatory and dependent dependencies. This represents the number of valid dependencies that have been successfully included in the unit set or have met the adaptation criteria. This application pre-sets a dependency eligibility threshold. If the calculated Below If the current implementation package is found to have incomplete dependency completion or insufficient basic conditions, it cannot generate a standard implementation package. Instead, it can only output a package to be completed or a downgraded implementation package to ensure the availability and controllability of the output package.
[0043] It should be further noted that during the synchronous process of dependency closure unwrapping and dependency completion, this step simultaneously performs global dependency conflict detection, proactively avoiding unit adaptation contradictions. This application specifically defines a formula for calculating dependency conflict degree:
[0044] in, The degree of version conflict between different units mainly represents the adaptation contradiction caused by different version requirements of multiple units for the same rule and the same interface; The degree of process mutual exclusion indicates whether there are mutual exclusion, conflict, or deadlock issues in the execution flow, start / stop order, and calling logic of different units; The degree of object boundary conflict characterizes the overlapping, contradictory, and overlapping issues in the scope of operation and maintenance objects and data boundaries adapted by different units; , , These are the preset weight coefficients for the corresponding conflict dimensions. When the calculated... Higher than the preset conflict threshold If the current candidate implementation package is determined to have a high-level incompatibility conflict, it must be returned for trimming and rectification. Only after eliminating all conflict dependencies and unifying the adaptation standards can it proceed to the next processing step.
[0045] Step S3: Perform conflict checks and applicable boundary pruning on the candidate implementation packages, and generate standard implementation packages, enhanced implementation packages, or degraded implementation packages based on the pruning results.
[0046] This step involves conducting a full-domain secondary conflict check, precise trimming of applicable boundaries, and implementation package level classification for the complete candidate implementation packages processed by S2. A quantitative scoring system is used to achieve standardized classification of package quality, and standardized implementation packages adapted to different operation and maintenance scenarios and project levels are output in a targeted manner. This ensures that basic operation and maintenance requirements are implemented, while avoiding resource redundancy, configuration waste, and over-adaptation problems caused by forced adaptation of full packages.
[0047] For example, this application embodiment achieves quantitative judgment of the overall quality of the implementation package by constructing a tailoring scoring model, accurately assessing the completeness, fit, and risk of the package. The specific tailoring scoring formula is as follows:
[0048] in, For a single candidate implementation package The comprehensive adaptation and tailoring score indicates that the higher the score, the better the implementation package's completeness, adaptability, security, and usability. to These are preset weight coefficients for each evaluation dimension, used to differentiate the evaluation priority of each dimension.
[0049] The specific explanations and evaluation logic of each core parameter in the formula are as follows: The core unit completeness is used to determine whether all core skeleton units of the implementation package are complete, without missing or replacement gaps. To determine the dependency satisfaction rate, the quantification parameters from the previous steps are used to characterize the completeness of the overall unit dependency completion. To determine the minimum dataset satisfaction rate, it is determined whether the basic input data, historical data, and ledger information necessary for the implementation package to run are complete and meet the minimum operating requirements. The implementation window satisfaction rate is used to characterize whether the unit downtime window and operation and maintenance window of the current project can fully cover the entire process of implementation package deployment, commissioning and verification. To determine the delivery boundary satisfaction rate, we need to determine whether the current package can fully support the output and implementation requirements of the minimum deliverable and minimum acceptance objects. To implement risk penalties, points are deducted for high-risk scenarios such as overlapping use of high-risk units, missing key interfaces, missing key operation and maintenance roles, and abnormal operating condition adaptation, thus quantifying the implementation risks.
[0050] Optionally, the conflict checking and boundary trimming in this step have a standardized and implementable complete execution process. First, the system performs pairwise full-domain conflict detection on all capability units within the candidate implementation package, focusing on identifying three types of core incompatible conflicts: version conflicts of rules for the same maintenance object, version adaptation conflicts of the same interaction interface, and mutually exclusive conflicts in the workflow order of multiple units; then, relying on... The conflict degree calculation results accurately determine the conflict level. If the conflict degree exceeds the threshold, it is automatically returned for rectification. Adaptation conflicts are completely eliminated by trimming conflicting units, unifying version standards, and optimizing process logic. Finally, in strict accordance with the boundary constraints of the target profile constructed by S1, redundant capability units in the candidate implementation package that exceed the unit adaptation range, component coverage range, operating condition range, data condition requirements, and delivery boundary requirements are precisely trimmed and eliminated. In the end, a trimmed candidate implementation package with accurate boundaries, no adaptation conflicts, and that fits the actual needs of the project is obtained.
[0051] To further clarify, this application establishes a standardized three-level package classification rule based on the trimming scoring results, the completeness of core units, and the adaptability of extended units, to achieve differentiated output. The specific classification logic is as follows: If the trimmed candidate implementation package has all core units complete, dependency closures complete and without missing parts, no high-level conflicts, and fully meets the minimum delivery standards and minimum acceptance requirements, it is judged as a standard implementation package, suitable for most routine operation and maintenance projects; if, under the premise of a complete skeleton and basic capabilities of the standard implementation package, all compatible and compliant extended units are additionally integrated, and it has enhanced delivery capabilities and multi-party collaborative operation and maintenance capabilities, it is judged as an enhanced implementation package, suitable for complex scenarios and high-standard operation and maintenance projects; if the implementation package has complete core units and a complete and usable basic functional skeleton, but some non-essential extended capabilities are adapted and trimmed, retaining only the minimum implementable and minimum acceptable basic operation and maintenance capabilities, it is judged as a downgraded implementation package, suitable for lightweight project scenarios with simple operation and maintenance, limited window periods, and incomplete data.
[0052] Step S4: Generate a deployment list and an acceptance mapping list for the generated implementation package. After generating the deployment list and the acceptance mapping list, freeze the implementation package version to form a deployable, acceptable, and reproducible implementation package object.
[0053] This step automatically generates a standardized deployment list and acceptance mapping list for the standard implementation package, enhanced implementation package, and downgraded implementation package formed by S3 hierarchy. It completes the comparison record of differences between the old and new versions and the verification of compliance conditions, and finally realizes the freezing of implementation package versions. It stably outputs standardized implementation package objects that are deployable, acceptable, replicable, traceable, and iterative, and at the same time achieves seamless connection and adaptation with the large generator full-process operation and maintenance closed loop system.
[0054] It should be noted that, in order to achieve standardized and structured output of deployment configurations, this application defines a deployment manifest object, DeployManifest, to uniformly standardize the deployment configuration content and parameter structure of all implementation packages. The specific expression is: DeployManifest=<ManifestID,PackID,ObjectBindSet,DataBindSet,InterfaceSet,FlowSet,DeliverInitSet,RiskSet> The structured object model consists of: ManifestID (a unique identifier for the deployment manifest); PackID (a unique identifier for the corresponding implementation package), ensuring precise binding between the manifest and the implementation package; ObjectBindSet (a set of bound maintenance objects for the unit, specifying the corresponding unit, component, and equipment objects for deployment); DataBindSet (a set of bound maintenance data, defining data access, data mapping, and data matching rules); InterfaceSet (a set of interaction interfaces required for deployment); FlowSet (a set of maintenance execution workflows); DeliverInitSet (a set of delivery initialization configurations, completing pre-delivery configuration); and RiskSet (a set of risk points and prohibited operating conditions during maintenance implementation, enabling proactive risk management). Based on this structured object model, this step automatically generates a complete list of object bindings, data access, rules loading, workflow activation, interface access, delivery initialization, and risks and prohibited conditions, providing comprehensive support for on-site deployment.
[0055] Meanwhile, to completely resolve the industry pain points of traditional operation and maintenance implementation being disconnected from acceptance, acceptance standards being postponed, and acceptance materials being hastily cobbled together, this application's embodiment defines an acceptance mapping object AcceptMap to achieve a strong binding and pre-establishment of implementation package delivery capabilities and acceptance standards. The specific expression is: AcceptMap =<AcceptID,PackID,AcceptObjSet,CheckItemSet,PassGate,TraceNeedSet,VersionTag> Here, AcceptID is the unique identifier for the acceptance mapping; PackID is the identifier for the corresponding implementation package; AcceptObjSet is the set of core operation and maintenance objects corresponding to the acceptance; CheckItemSet is the set of acceptance inspection items to be implemented item by item; PassGate is the quantifiable and executable acceptance passing threshold standard; TraceNeedSet is the set of evidence retention, log recording, and ledger archiving requirements required for acceptance traceability; and VersionTag is the version tag for the acceptance mapping, ensuring the traceability of acceptance standard iterations. This step, based on this object model, solidifies the acceptance objects, inspection items, passing thresholds, traceability requirements, and version verification rules during the implementation package generation stage, achieving integrated implementation and acceptance.
[0056] It should be further noted that, in order to unify the standardized attributes of the final output package and achieve full lifecycle management, this application embodiment defines a complete implementation package object ImplPack as the carrier of the final standardized operation and maintenance product, specifically expressed as: ImplPack=<PackID,PackType,ScopeSet,UnitSet,DepSet,CutRuleSet,DeliverSet,AcceptSet,PackState,PackVer> Among them, PackID is the unique identifier of the implementation package; PackType is the implementation package category, distinguishing between standard packages, enhanced packages, and degraded packages; ScopeSet is the set of applicable scopes of the implementation package; UnitSet is the set of all capability units integrated within the package; DepSet is the set of inter-unit dependencies; CutRuleSet is the set of package body trimming rules; DeliverSet is the set of deliverables; AcceptSet is the acceptance set; PackState is the running and build status of the implementation package; and PackVer is the implementation package version number.
[0057] Furthermore, the implementation package version PackVer of this application is a multi-dimensional aggregated version, consisting of six sub-versions: data model version, object rule version, capability unit version, interface mapping version, delivery template version, and acceptance mapping version. This allows for a comprehensive and detailed representation of the iterative changes to the implementation package. To ensure controllable and traceable version iteration, this application addresses newly generated implementation packages... Implementation package with historical benchmark sources It automatically records the difference set DiffSet, which specifically covers the addition of units, deletion of units, replacement of units, changes in rules, changes in interfaces, and changes in acceptance items. This transforms the iterative upgrade of the implementation package from the traditional complete reconstruction mode to a controllable incremental evolution mode based on the baseline package, greatly improving the stability and standardization of the iteration.
[0058] It is worth mentioning that this application sets strict and comprehensive version freeze admission conditions to prevent unqualified packages from being officially launched. Only when the five core conditions are met simultaneously—complete and unmissing core units, complete and unmissing dependency closures, no high-level adaptation conflicts, all minimum deliverables, and the minimum acceptance items can be executed normally—can the current candidate implementation package be frozen as an official version.
[0059] Optionally, this step has a complete standardized implementation process: First, based on the capability unit set and delivery system of the mature implementation package, a fully covered standardized deployment list and acceptance mapping list are automatically generated; second, the differences between the new version and the baseline version are compared, and the iterative changes are fully recorded; then, all the access conditions for version freezing are verified item by item, and the implementation package version information is locked after all verifications are passed; finally, a reusable, deployable, acceptable, and iterative standardized implementation package object is output.
[0060] For example, the standardized implementation package constructed in this application can be fully and deeply integrated with the large generator operation and maintenance closed-loop system without changing the algorithm body and core logic of the original operation and maintenance system, and achieves seamless integration only through capability encapsulation and boundary solidification. Specific integration methods include: integration with the unit status acquisition module to uniformly define the data collection, data import, and status identification entry capabilities within the package; integration with the status expression and object management module to standardize the basic framework system of unit objects, component objects, inspection unit objects, and defect objects; integration with the multi-source data governance module to explicitly define the minimum dataset and interface dependency boundaries required for operation and maintenance; integration with the intelligent analysis module to fully incorporate various analysis capability units into the implementation package while retaining the original analysis algorithm body unchanged; integration with the re-inspection tracking module to simultaneously incorporate the re-inspection task entry, task closure conditions, and supporting delivery interfaces; integration with the trend evolution module to solidify the minimum historical data requirements and trend object output boundaries required for trend analysis; integration with the evidence delivery module to unify evidence management rules and delivery templates, forming standardized evidence delivery boundaries; and integration with the multi-party collaboration system of the OEM, owner, and maintenance parties to simultaneously solidify the boundaries of shared interfaces and unified acceptance boundaries, achieving standardized collaborative operation and maintenance.
[0061] In the application of one embodiment of the present invention, the implementation process is as follows: This invention takes the standardized implementation package for the closed-loop scenario of in-situ testing and re-inspection of a 600MW thermal power unit as a specific application carrier, and fully explains the actual implementation process of the technical solution of this application. The overall implementation process fully covers the fully engineered encapsulated logic of capability identification, quantitative screening, dependency completion, conflict verification, hierarchical trimming, list generation and version solidification.
[0062] First, the system relies on pre-set capability libraries, rule libraries, interface libraries, and template libraries to complete a comprehensive traversal of basic resources. Combined with the target application scope and actual operation and maintenance scenarios of this 600MW unit in-situ inspection and re-inspection closed loop, it accurately identifies and defines the core operation and maintenance capability boundaries and functional requirements needed for this project. It should be understood that, for the actual business requirements of this 600MW thermal power unit's in-situ inspection, defect analysis, evidence retention, re-inspection tracking, and closed-loop acceptance, the core capability dimensions to be covered by this implementation package specifically include: standardized management capabilities for unit and component objects; unified access capabilities for multi-source results data from in-situ inspections of the unit; intelligent analysis capabilities for unit operation image data and equipment status; evidence collection and standardized delivery capabilities throughout the operation and maintenance process; closed-loop tracking capabilities for the entire defect re-inspection task process; basic interface adaptation capabilities for connecting to external business systems; and standardized acceptance objects and acceptance verification capabilities for corresponding operation and maintenance scenarios. Based on the above scenario requirements, the system automatically constructs an implementation package target profile adapted to this 600MW unit operation and maintenance business, clarifying the unit scope, component scope, operating condition adaptation scope, required basic data conditions, delivery output boundaries, and project acceptance requirements corresponding to this implementation package, providing a precise quantitative benchmark for subsequent capability selection and package construction.
[0063] After completing the scenario profiling and target boundary construction, the system conducts adaptation and admission screening based on the full-domain candidate capability unit resources. It should be noted that this embodiment strictly adopts the unit adaptation scoring algorithm disclosed in this application to quantitatively score each candidate capability unit. The Score_unit(u) comprehensively calculates the overall score of each capability unit in terms of applicable scope matching, data condition matching, delivery requirement matching, acceptance requirement matching, and mismatch penalty dimensions. Capability units whose scores meet preset thresholds are included in the candidate system. After quantitative comparison and screening, the data foundation unit, object rule unit, status analysis unit, evidence delivery unit, and re-inspection task tracking unit all meet the core requirements of this 600MW unit in-situ testing closed-loop scenario in terms of unit adaptation, scenario matching, delivery support, and acceptance adaptation. Their unit adaptation scores are up to standard, and all are essential capabilities to ensure the implementation of the entire process of testing, analysis, delivery, re-inspection, and closed-loop acceptance. Therefore, the system uniformly collects the above capability units to form the core unit set CoreSet of this implementation package. It should be noted that some enhanced collaboration capability units, which are used to improve the efficiency of multi-party collaboration and expand the dimensions of operation and maintenance, can enrich the expansion capabilities of the implementation package, but they are not essential units for this basic closed-loop business. Therefore, these units are uniformly classified into the extended unit set and are only retained as optional enhanced capabilities, and are not included in the core skeleton.
[0064] To ensure logical coherence, complete dependencies, and seamless operation among core units, the system automatically performs global dependency closure unpacking on the established core unit set. For example, the system parses the dependency objects corresponding to each core capability unit layer by layer, identifying mandatory association constraints between units. In this 600MW unit in-situ inspection closed-loop scenario, the normal operation of the re-inspection task tracking unit strongly depends on the unit component object definitions, defect object definitions, and re-inspection rule constraints provided by the object rule unit, and also strongly depends on the task delivery and result archiving support provided by the evidence delivery unit. Meanwhile, the complete operation of the evidence delivery unit requires the data foundation unit to complete the collection, organization, and storage of multi-source inspection data, status data, and analysis result data. Based on these dependencies, the system automatically identifies the missing pre-support units and supporting rule resources in the current core set through dependency closure calculation logic, fills in all mandatory dependencies layer by layer, iteratively completes dependency closure convergence, and completely avoids the problems of missing pre-conditions for unit operation and business process breaks.
[0065] After completing dependency closure completion, the system automatically performs dependency satisfaction rate quantification calculation and global dependency conflict detection. Furthermore, the system... The formula calculates the overall satisfaction level of all dependencies in this implementation package, verifying that all pre-dependencies, data dependencies, interface dependencies, and process dependencies of all core units have been fulfilled, and the dependency satisfaction rate meets the preset qualified threshold. Simultaneously, the system... The conflict degree calculation model performs multi-dimensional detection of version conflicts, process mutual exclusion, and object boundary conflicts for all included core and extended units. The detection results show that the adaptation versions of each capability unit in this scenario are unified, the execution process logic is compatible, the object boundaries are clear and there are no overlapping contradictions, there are no high-level conflict dependencies, the overall unit set is in compliance with the adaptation status, and can smoothly enter the subsequent boundary trimming and hierarchical judgment stage.
[0066] The system, taking into account the completeness of actual data, on-site operation and maintenance window conditions, minimum delivery requirements, and acceptance standards of this 600MW unit in-situ testing and re-inspection closed-loop project, through... The tailored scoring formula was used to complete the comprehensive quality quantitative assessment and grading of the implementation package. It should be understood that the core units of this project are complete, dependency closures are fully converged, basic data conditions meet the minimum operational requirements, and the on-site operation and maintenance window can fully cover the deployment and verification process, fully supporting the project's minimum delivery goals and minimum acceptance closure requirements. The scoring result meets the conditions for a standard implementation package. However, since this project site has no complex collaborative expansion needs, no high-standard enhanced delivery requirements, and does not include all enhanced extension units, it does not meet the criteria for an enhanced implementation package. Finally, based on the grading rules, the system stably outputs a standard implementation package adapted to the on-site testing and re-inspection closure scenario of this 600MW thermal power unit, ensuring the availability of the basic business closure while avoiding resource waste and over-adaptation issues caused by redundant capabilities.
[0067] After the implementation package is tailored and tiered, the system automatically generates standardized deployment manifest objects (DeployManifest) and acceptance mapping objects (AcceptMap) for the standard implementation package, thus solidifying the engineering information of the implementation package. Specifically, the system, based on the capability unit composition and business adaptation boundaries of this implementation package, automatically generates a complete deployment resource system, including a list of unit and component object bindings, a list of in-situ testing data access bindings, a list of system interaction interfaces, a list of operation and maintenance workflow activations, a list of delivery initialization configurations, and a list of on-site implementation risks and prohibitions, providing a standardized configuration basis for on-site deployment. At the same time, the system synchronously matches the business closed-loop requirements, solidifying the set of acceptance objects corresponding to this implementation package, the exclusive acceptance inspection items for in-situ testing and re-inspection closed loops, the minimum acceptance threshold, the requirements for business traceability logs and evidence retention, and the version consistency verification rules, forming a quantifiable, implementable, and traceable acceptance mapping system.
[0068] After the deployment list and acceptance mapping list are generated and verified to be error-free, the system verifies that the core units are complete, dependencies are not missing, conflicts have been cleared, and all delivery and acceptance conditions are met. Finally, the version of the implementation package for this scenario is frozen, and a standardized engineering implementation package that is deployable, acceptable, and replicable is output. It is evident that the core difference between this application's solution and the compression and compilation logic of traditional software installation packages is that it is not simply a matter of integrating and encapsulating various functional modules. Instead, it addresses the intelligent operation and maintenance business characteristics of heavy power equipment such as large generators and thermal power units by systematically, engineeredly, and standardizedly encapsulating scattered operation and maintenance capabilities, business rules, data interfaces, delivery standards, and acceptance systems. This forms a standardized engineering implementation unit with clear boundaries, deployable capabilities, quantifiable acceptance criteria, and reusable replication, effectively solving the industry pain points of traditional unit operation and maintenance capabilities being fragmented, configurations inconsistent, delivery lacking standards, and difficult to close the acceptance loop.
[0069] Example 2 To implement the methods of the above embodiments, the present invention also provides an electronic device, which includes a memory and a processor; wherein the processor reads executable program code stored in the memory to run a program corresponding to the executable program code, so as to implement the various steps of the methods described above.
[0070] Example 3 To implement the above embodiments, this application also proposes a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the method described in the foregoing embodiments.
[0071] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.
[0072] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.
[0073] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this invention, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.
Claims
1. A method for generating a standardized deployment and implementation package for intelligent operation and maintenance of large generators, characterized in that, include: Read existing capability libraries, rule libraries, interface libraries, and template libraries to identify candidate capability units that can be included in the implementation package, and establish an implementation package target profile based on the target application scope and target scenario. The target profile includes unit scope, component scope, operating condition scope, data conditions, delivery boundaries, and acceptance requirements. From the candidate capability units, capability units that meet the target profile are selected. Dependency closure expansion is performed on the selected capability unit set to supplement the missing prerequisite units and supporting rules into the capability unit set, forming a candidate implementation package. Conflict checks and applicable boundary pruning are performed on the candidate implementation packages, and standard implementation packages, enhanced implementation packages, or degraded implementation packages are generated based on the pruning results; A deployment list and an acceptance mapping list are generated for the generated implementation package. After the deployment list and the acceptance mapping list are generated, the implementation package version is frozen, forming a deployable, acceptable, and reproducible implementation package object.
2. The method according to claim 1, characterized in that, Based on the target application scope and target scenario, establish an implementation package target profile, including: Based on the target application scope, determine the set of unit types and component range to which the implementation package applies; Based on the target scenario, determine the applicable operating conditions range for the implementation package; Based on the target application scope and the target scenario, determine the minimum data scope and data conditions required for the implementation package, as well as the delivery boundaries and acceptance requirements of the implementation package. The delivery boundaries include the minimum deliverables and the scope of deliverables, and the acceptance requirements include the acceptance objects and acceptance pass conditions.
3. The method according to claim 2, characterized in that, From the candidate capability units, capability units that satisfy the target profile are selected. Dependency closure expansion is performed on the selected capability unit set to supplement the missing prerequisite units and supporting rules into the capability unit set, forming a candidate implementation package, including: The range of units, components, operating conditions, data conditions, delivery boundaries, and acceptance requirements in the target profile are matched and compared with the applicable scope, minimum input requirements, output object set, delivery dependencies, and acceptance dependencies of each candidate capability unit to obtain the matching results of each candidate capability unit in each dimension. Based on the matching results, the candidate capability units are divided into target units and extended units. Target units are capability units that cannot be implemented if they are missing, while extended units are capability units that do not affect the implementation of the package but affect the package's enhanced capabilities if they are missing. The target unit and the extended unit are retained to form a set of filtered capability units.
4. The method according to claim 3, characterized in that, Dependency closure expansion is performed on the selected set of capability units to supplement the missing prerequisite units and supporting rules into the set of capability units, forming a candidate implementation package, including: The selected set of capability units is used as the initial set for closure computation. The dependent objects of each capability unit are checked layer by layer. The dependent objects include object dependencies, data dependencies, process dependencies, interface dependencies, delivery dependencies and acceptance dependencies. The missing prerequisite units and supporting rules are added to the capability unit set layer by layer until no new missing dependencies are generated, thus completing the dependency closure expansion and forming a candidate implementation package.
5. The method according to claim 4, characterized in that, Perform conflict checks and applicable boundary pruning on the candidate implementation packages, including: Each capability unit in the candidate implementation package is subjected to pairwise conflict detection, wherein the conflict includes at least version conflicts of the same object rule, version conflicts of the same interface, and mutual exclusion conflicts of the process order. The degree of conflict is determined based on the conflict detection results. If the degree of conflict exceeds the threshold, the candidate implementation package is returned to be pruned to eliminate conflict dependencies before further processing. Based on the unit scope, component scope, operating condition scope, data conditions, delivery boundaries, and acceptance requirements in the target profile, capability units in the candidate implementation package that exceed the applicable boundaries are trimmed and eliminated to obtain the trimmed candidate implementation package.
6. The method according to claim 5, characterized in that, Based on the tailoring results, standard implementation packages, enhanced implementation packages, or downgraded implementation packages are generated, including: If the candidate implementation package after trimming has complete target units, complete dependency closures, and meets the minimum delivery and acceptance requirements, then a standard implementation package is generated. If an enhanced implementation package is generated by further including extended units on top of the standard implementation package and having enhanced delivery and collaboration capabilities; If the target unit is complete but some expansion capabilities are removed, and the minimum implementable and minimum acceptable skeletons are still retained, then a downgraded implementation package is generated.
7. The method according to claim 6, characterized in that, Generate a deployment manifest and an acceptance mapping manifest for the generated implementation package. After generating the deployment manifest and the acceptance mapping manifest, freeze the implementation package version to form a deployable, acceptable, and reproducible implementation package object, including: Based on the set of capability units in the generated implementation package, an object binding list, a data access list, an interface list, a workflow list, a delivery initialization list, and a risk and prohibition condition list are generated, which together constitute the deployment list; Based on the set of capability units and the set of deliverables in the generated implementation package, the necessary acceptance objects, the acceptance inspection items corresponding to each acceptance object, and the minimum pass threshold are determined, and a set of traceability requirements and version consistency inspection items are generated, which together constitute the acceptance mapping list. After generating the deployment list and the acceptance mapping list, verify that the target units of the current implementation package are complete, the dependency closures are complete, there are no high conflict dependencies, the minimum deliverables are available, and the minimum acceptance items are executable. When all verification conditions are met, freeze the implementation package version as the official version to form a deployable, acceptable, and reproducible implementation package object.
8. An electronic device, characterized in that, Including processor and memory; The processor reads executable program code stored in the memory to run a program corresponding to the executable program code, so as to implement the method as described in any one of claims 1-7.
9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-7.
