An engineering consultation intelligent decision support method based on project knowledge base

Abstract

The application discloses an engineering consultation intelligent decision support method based on a project knowledge base, relates to the technical field of engineering consultation, and comprises the following steps: performing double-path state deduction on a to-be-adjusted engineering object in project decision benchmark data, respectively tracking state changes of engineering objects generated along an implementation change path and a status maintenance path according to project dependency relations, eliminating common propagation results with the same engineering object state changes and consistent associated propagation relations, collecting path difference results corresponding to remaining differences, and forming a change difference influence set; performing conditional verification on the change difference influence set, converting difference influences satisfying applicable conditions into engineering consultation decisions, and delivering the engineering consultation decisions to an engineering execution end; and adjusting the to-be-adjusted engineering object according to the engineering consultation decisions, marking execution state deviations and newly-added propagation relations, and forming actual execution difference data. The application improves change difference identification precision through synchronous elimination of common propagation results.

Description

Technical Field

[0001] This invention relates to the field of engineering consulting technology, and in particular to an intelligent decision support method for engineering consulting based on a project knowledge base. Background Technology

[0002] As engineering construction projects become increasingly large-scale, specialized, and collaborative, engineering consulting is gradually shifting from the traditional model relying on manual experience and scattered data retrieval to a digital and knowledge-based decision support model. Project knowledge bases, as a crucial technological carrier for organizing engineering consulting information, can uniformly manage design data, construction data, approval records, equipment information, engineering change data, and project status records. They can also leverage technologies such as engineering object association, version management, knowledge retrieval, and relationship modeling to form a semantically related engineering knowledge system. For large and complex engineering projects, different engineering objects typically have multi-level dependencies, including design constraints, interface constraints, construction connections, equipment linkages, and status transmission. When the status of a local project changes, it may propagate along existing dependencies to multiple related engineering objects. Therefore, conducting engineering object relationship organization, status evolution analysis, and engineering consulting decision support based on project knowledge bases has become an important direction for digital research in engineering consulting.

[0003] Existing engineering consulting decision support technologies typically analyze the impact of engineering changes by directly tracking state changes and subsequent propagation results based on existing engineering object relationships. However, state propagation in complex projects often includes changes naturally arising from the original project state and established dependencies, causing the specific impacts actually caused by the change to become intertwined with state changes resulting from the project's own continuation. Especially in multi-level, branching project dependencies, different propagation paths may result in the same engineering object state change but with different propagation sources. This makes it difficult to accurately identify the differential impacts truly caused by the change in the state of the engineering object to be adjusted during the engineering consulting process, thus affecting the accurate determination of the scope of the change's impact and the key propagation locations. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides an intelligent decision support method for engineering consulting based on a project knowledge base to solve the problem of difficulty in accurately identifying the differences caused by changes in the state of the engineering object to be adjusted.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: This invention provides an intelligent decision support method for engineering consulting based on a project knowledge base, comprising: The project knowledge base is used to filter out invalid engineering data corresponding to engineering consulting matters, and the valid engineering data is associated with engineering objects and project dependencies to form project decision-making benchmark data; A dual-path state simulation is performed on the engineering objects to be adjusted in the project decision baseline data. The state changes of the engineering objects generated by the implementation change path and the status quo maintenance path are tracked along the project dependency relationship. Common propagation results with the same state changes and consistent propagation relationship of the engineering objects are hidden. The path difference results corresponding to the remaining differences are collected to form the change difference impact set. The set of changes and differences is verified for conditions. The differences that meet the applicable conditions are converted into engineering consulting decisions and transmitted to the engineering execution end. The engineering execution end adjusts the engineering objects to be adjusted according to the engineering consulting decisions, records the actual status of the engineering objects after adjustment, compares the actual status of the engineering objects with the expected status of the engineering objects, marks the execution status deviation and the new propagation relationship, and forms the actual execution difference data. The project status is updated based on the actual engineering object status in the actual execution difference data. The changes in the updated project status are tracked along the project dependencies. The gaps in the project dependencies where new propagation relationships are added are located, and the new propagation relationships are added to the project dependencies to form the consulting decision results.

[0007] As a preferred embodiment of the intelligent decision support method for engineering consulting based on a project knowledge base as described in this invention, wherein: the formation of project decision benchmark data specifically includes, Search for related engineering data in the project knowledge base, compare the effective relationships between related engineering data, remove invalid engineering data and retain valid engineering data to form a set of valid engineering data; Each valid engineering data in the valid engineering data set is matched with an engineering object, and the valid engineering data that point to the same engineering object are associated to form an engineering object association result. The relationships between project objects are traced along the project object association results. The relationships that can continuously transmit changes in the state of project objects are identified as project dependencies. The identified project dependencies are organized according to the transmission direction of the relationships and the corresponding relationships of project objects to form project dependency data. The engineering objects and project dependencies in the project dependency data are integrated with the set of valid engineering data to form the project decision-making benchmark data.

[0008] As a preferred embodiment of the intelligent decision support method for engineering consulting based on a project knowledge base as described in this invention, wherein: the step of tracking the state changes of engineering objects caused by the implementation change path and the status quo maintenance path along the project dependency relationship specifically involves... Read the current status of the engineering object to be adjusted from the project decision baseline data, and arrange the engineering objects directly connected to the engineering object to be adjusted and their current status in sequence along the project dependency relationship to form a baseline status record; Copy the baseline status record to a change status record and a current status record. Rewrite the current status of the engineering object to be adjusted in the change status record according to the engineering consulting matters, generate the change status of the engineering object, and take the current status of the engineering object to be adjusted in the current status record as the current status of the engineering object. Starting from the project objects to be adjusted in the change status record and the current status record respectively, the change status of the project objects and the current status of the project objects are propagated to the project objects directly connected in the project dependency relationship, forming change propagation record and current status propagation record; The change propagation record and the status propagation record are compared with the baseline status record item by item. The engineering objects whose status has changed and the status of the changed engineering objects are retained to form the change status record and the status change record. The engineering objects in the change status record and the current status change record continue to propagate the status of the engineering objects along the project dependencies. The engineering objects whose status has changed and their changed status are added to the change status record and the current status change record until the status of the engineering objects no longer changes. According to the propagation order in the project dependencies, the records of changes in the status quo are linked together to form the implementation path, and the records of changes in the current status are linked together to form the current status maintenance path. Continue to track the changes in the status of the project object along the implementation change path and the status quo maintenance path, and take the tracked changes in the status of the project object as the changes in the status of the project object generated by the implementation change path and the status quo maintenance path.

[0009] As a preferred embodiment of the intelligent decision support method for engineering consulting based on project knowledge base described in this invention, the engineering consulting matters refer to the specific adjustment requirements and corresponding consulting content raised during the project implementation process for the engineering object to be adjusted.

[0010] As a preferred embodiment of the intelligent decision support method for engineering consulting based on project knowledge base described in this invention, wherein: the formation of the change difference impact set specifically refers to... Based on the propagation order of the engineering object in the implementation change path and the status quo maintenance path, the state change of the engineering object and the associated propagation relationship are reconstructed into the implementation change state propagation chain and the status quo maintenance state propagation chain, respectively. Extract continuous propagation segments from the implementation change state propagation chain and the status quo maintenance state propagation chain, where the state changes of engineering objects are the same and the related propagation relationships are consistent. Use the engineering objects at the beginning and end of the continuous propagation segments to define the common state propagation segment, and write the state changes of engineering objects and related propagation relationships in the continuous propagation segments into the common state propagation segment to form a common propagation result. Based on the changes in the state of the engineering object and the associated propagation relationships recorded in the common state propagation segment, the common propagation results are simultaneously eliminated in the implementation change state propagation chain and the status quo maintenance state propagation chain, forming the implementation change difference propagation chain and the status quo maintenance difference propagation chain; Based on the propagation boundaries exposed in the implementation change state propagation chain and the status quo maintenance state propagation chain after synchronous fading of the common propagation results, the associated propagation relationships that maintain the transmission order in the implementation change difference propagation chain and the status quo maintenance difference propagation chain are reconnected to form a difference propagation structure; Based on the implementation change path and status quo maintenance path to which the state changes of engineering objects in the differential propagation structure belong, the unique state changes of engineering objects and their associated propagation relationships of different paths are collected into path difference results. Based on the propagation order in project dependencies, the path difference results and the associated propagation relationships between the path difference results are arranged sequentially to form a set of change difference impacts.

[0011] As a preferred embodiment of the intelligent decision support method for engineering consulting based on a project knowledge base as described in this invention, wherein: the recording of the adjusted actual engineering object state specifically includes, Obtain applicable conditions related to engineering consulting matters from valid engineering data in project decision-making benchmark data, configure the applicable conditions to the path difference results in the change difference impact set, and form the correspondence of applicable conditions; Based on the correspondence of applicable conditions, the changes in the status of engineering objects and their related propagation relationships in the path difference results are checked. The related propagation relationships that do not meet the applicable conditions are cut off, and the remaining changes in the status of engineering objects and their related propagation relationships are classified as differences that meet the applicable conditions. The changes in the state of engineering objects under the influence of differences that meet the applicable conditions are converted into corresponding state adjustment actions for the engineering objects, and the execution order of the state adjustment actions is determined based on the correlation propagation relationship to form engineering consulting decisions. Transmit the engineering objects to be adjusted, the status adjustment actions, and the execution order in the engineering consulting decision-making process to the engineering execution end; By adjusting the state of the corresponding project object according to the state adjustment actions and execution order through the project execution terminal, the current state of the project object is changed, and the actual state of the project object is obtained.

[0012] As a preferred embodiment of the intelligent decision support method for engineering consulting based on project knowledge base described in this invention, the applicable conditions related to the engineering consulting matters include the status requirements of engineering objects recorded in valid engineering data, project dependency restrictions, engineering implementation constraints, and execution conditions corresponding to the engineering consulting matters.

[0013] As a preferred embodiment of the intelligent decision support method for engineering consulting based on project knowledge base described in this invention, the differential influence that meets the applicable conditions is the differential influence that enters the engineering consulting decision transformation stage after condition verification, and serves as the basis for forming the state adjustment action and execution order of the engineering object to be adjusted.

[0014] As a preferred embodiment of the intelligent decision support method for engineering consulting based on a project knowledge base as described in this invention, wherein: the formation of actual execution difference data specifically includes, According to the execution order in engineering consulting decision-making, the actual state and expected state of the same engineering object to be adjusted are arranged side by side to form an execution status comparison sequence. The actual and expected states of engineering objects in the execution state comparison sequence are verified one by one. Engineering objects with inconsistent states are marked as execution state deviations, and the position of the execution state deviation in the execution order is recorded. Based on the location of the execution state deviation, the engineering objects to be adjusted that continuously exhibit execution state deviations are compressed into a continuous state deviation segment, and the first engineering object to be adjusted that exhibits an execution state deviation in the continuous state deviation segment is taken as the starting position of the state deviation. Starting from the initial position of the state deviation, establish a verification propagation relationship between the subsequent engineering object to be adjusted that first experiences an execution state deviation and the previous engineering object to be adjusted, according to the execution order, and mark the verification propagation relationship not recorded in the project dependency relationship as a new propagation relationship; The execution status deviation and the newly added propagation relationship are associated with the corresponding engineering objects to be adjusted, forming actual execution difference data.

[0015] As a preferred embodiment of the intelligent decision support method for engineering consulting based on a project knowledge base as described in this invention, wherein: the formation of consulting decision results specifically includes, By using the actual project object status in the actual execution difference data, the current project object status of the same project object in the project status is replaced to form the updated project status; By using the propagation order in the project dependencies, the project objects that have changed in the updated project state are sorted sequentially, and the project state changes between the project objects are recorded to form a project state change sequence. Place the newly added propagation relationship at both ends of the project objects in the actual execution difference data into the corresponding order in the project state change sequence, verify the continuity of the existing project dependency relationship between the two project objects, and mark the gaps between project objects where the project state changes continuously but the existing project dependency relationship lacks a propagation relationship as project dependency gaps. The newly added propagation relationship is added to the project dependency gap, and the propagation order between the project objects at both ends of the project dependency gap is rearranged according to the project state change sequence to form the supplemented project dependency. The updated project status is assigned to the engineering objects in the supplemented project dependencies, forming the consulting decision result.

[0016] The beneficial effects of this invention are as follows: By synchronously eliminating hidden effects through common propagation results, the accuracy of change difference identification is improved. Based on the same project decision-making baseline data, implementation change paths and status quo maintenance paths are formed separately. The changes in the state of engineering objects and their associated propagation relationships in the two paths are reconstructed into consequence chains. The identical changes in the state of engineering objects and the consistent associated propagation relationships are used as the identification condition for common propagation results. This eliminates overlapping results generated by the propagation of existing project states and predetermined dependencies from the scope of difference analysis. After the common propagation results are eliminated, the original propagation order and path attribution of the residual chains are maintained, allowing the remaining changes in the state of engineering objects and their associated propagation relationships to be aggregated into path difference results according to the paths, forming a change difference impact set. This enables subsequent condition verification to focus on the actual differences, enhancing the ability of engineering consulting decisions to identify the location, propagation direction, and state change results of key impacts. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart of an intelligent decision support method for engineering consulting based on a project knowledge base.

[0019] Figure 2 Construct a graph based on the baseline data for project decision-making.

[0020] Figure 3 This is a diagram illustrating the dual-path state deduction and the extraction of the impact of differences.

[0021] Figure 4 This is a diagram for engineering consulting decision-making, execution, feedback, and updates.

[0022] Figure 5 This is a diagram showing the association and state transfer of engineering objects on the secondary side of chilled water.

[0023] Figure 6 This is a diagram for dual-path state deduction and verification of newly added propagation relationships. Detailed Implementation

[0024] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0025] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0026] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0027] Example 1, referring to Figures 1-4 This is the first embodiment of the present invention, which provides an intelligent decision support method for engineering consulting based on a project knowledge base, including the following steps: S1. Filter out invalid engineering data corresponding to engineering consulting matters from the project knowledge base, and associate valid engineering data with engineering objects and project dependencies to form project decision-making benchmark data.

[0028] S1.1. Search for related engineering data in the project knowledge base, compare the valid relationships between related engineering data, remove invalid engineering data and retain valid engineering data to form a set of valid engineering data. Specifically, From the project knowledge base, determine the project number, the project object number to be adjusted, and the specific adjustment requirements from the engineering consulting records. Locate the relevant engineering documents according to the project object number, and then search for subsequent engineering documents along the related object numbers recorded in the documents until the scope of related objects no longer increases; all retrieved engineering documents are considered related engineering documents. Merge different versions of the same document according to the document number, verify the version approval record, effective date, and replacement record, and check the applicable project object and project stage; documents that have ceased to be effective, have been replaced by an effective version, or are not applicable to the current project object and project stage are not included in subsequent processing. Only documents and version information applicable to the current matter are retained to form a valid set of engineering documents; for example, if a consulting matter requires adjusting the circulating pump outlet pressure from 0.30 MPa to 0.36 MPa, the circulating pump regulation procedure, pressure verification record, and branch valve linkage instructions are all related engineering documents; if the third version of the same regulation procedure has already taken effect and clearly replaces the second version, the third version is used to verify the adjustment requirements.

[0029] Engineering consulting matters are adjustment requirements proposed and recorded for registered engineering objects. One engineering consulting matter may involve multiple engineering objects. The matter number and the engineering object number are registered in pairs, and each pair of numbers is accompanied by the corresponding adjustment content. The effective relationship refers to the effectiveness of related materials and the substitution relationship between different versions. The document number follows the number in the project document registration record. After the same document is modified, the document number is retained, and a version identifier is used to distinguish the modified content. The document number and the version identifier together determine the specific version.

[0030] S1.2. Each valid engineering data item in the valid engineering data set is matched with a specific engineering object. Valid engineering data items pointing to the same engineering object are associated, forming an engineering object association result. Specifically, For each valid set of engineering documents, verify the engineering object number recorded in the document entries, match the document entries with the same numbers in the engineering object registration record, and record the document number, version identifier, page number, and clause number of the entry. Engineering objects are independently registered equipment, components, and engineering interfaces within the same construction project. The engineering object name is used for display, and the engineering object number is used to determine ownership. When a document records multiple engineering objects, associate them separately according to the objects listed in the entry. When an entry jointly constrains multiple engineering objects, retain the correspondence between the entry and multiple engineering objects. Collect the available document content for the same engineering object according to the document number to form an engineering object association result. Subsequently, the corresponding document and specific clauses can be found through the engineering object number.

[0031] S1.3. Trace the relationships between project objects along the project object association results. Identify the relationships that can continuously transmit changes in the state of project objects as project dependencies. Organize the identified project dependencies according to the transmission direction of the relationships and the corresponding relationships of project objects to form project dependency data. Specifically, The system reads records from valid engineering data regarding engineering connections, implementation conditions, and state changes along the engineering object association results. It determines which engineering object the state influence is transmitted from to which engineering object, and clarifies the conditions that can trigger the transmission and the state that the target engineering object should form after the transmission. Numerical states are calculated according to the conversion relationships clearly recorded in the data, and categorical states are rewritten according to the conditions and corresponding contents clearly recorded in the data. When the target state is affected by multiple predecessor objects at the same time, all necessary conditions are registered together to avoid triggering a change when only one condition is met. Only when the data clearly supports the association between the state transmission direction, triggering conditions, and the state after the change, is it included in the project dependency relationship. Simple same name, adjacent position, and mutual reference of data do not constitute the basis for state transmission.

[0032] Continue verifying subsequent project objects along the confirmed relationships, registering the project object numbers at both ends, as well as the supporting document numbers, versions, and terms, to form project dependency data. Using the circulating pump example, assume the valid data stipulates: when the outlet pressure is between 0.28 and 0.38 MPa, the pressure verification point can change from pending verification to passed; after the pressure verification is passed, the operating permit point can change from unformed to formed; when the operating permit is formed and the outlet pressure reaches 0.36 MPa, the branch regulating valve should be adjusted from 40% opening to 45% opening; the above conditions and corresponding states are registered according to the example data, without inferring them based on the project object name.

[0033] Project dependency relationships represent the relationships in which the state of engineering objects can be transmitted according to the conditions and directions specified in the data; association propagation relationships represent the project dependency relationships actually used in a specific simulation; the source engineering object is the object from which the state influence is transmitted, and the target engineering object is the object to which the state influence is received. The "target" does not represent the state that is desired to be achieved after adjustment.

[0034] S1.4 After completing the selection of the current project object status, the valid project data, the current project object status recorded in the confirmed implementation records, and the dependencies of related projects for the same project object are saved according to the project object number to form the project decision benchmark data. The current project object status adopts the actual status confirmed before the simulation begins, and the status that should be reached as specified in the data is not taken as the actual status. The numerical status retains both the unit of measurement and the recording time. For project objects marked as having abnormal status, the data source and conflicting content are retained. Simulations involving abnormal status are not carried out temporarily. The corresponding project decision benchmark data is established after the status verification is completed.

[0035] S2. Perform dual-path state simulation on the engineering objects to be adjusted in the project decision baseline data. Track the state changes of engineering objects caused by the implementation change path and the status quo maintenance path along the project dependency relationship. Eliminate common propagation results with the same state changes and consistent correlation propagation relationship of engineering objects. Collect the path difference results corresponding to the remaining differences to form the change difference impact set.

[0036] S2.1. Read the current status of the project object to be adjusted from the project decision baseline data, and arrange the project objects directly connected to the project object to be adjusted and their current statuses sequentially along the project dependencies to form a baseline status record. Specifically, Based on the engineering object numbers in the engineering consulting matters, the engineering objects to be adjusted and their current states are determined from the project decision baseline data. Directly connected engineering objects are registered first, and then indirectly connected engineering objects are added level by level along the project dependency propagation direction until there are no unregistered reachable engineering objects. All states use records confirmed before the start of this dual-path state simulation, and all relationships use the same batch of valid data versions. When the same engineering object arrives via multiple propagation branches, only one current state is registered according to the engineering object number, while retaining all arrival relationships; one state comes from the state selection already completed in S1.4, without reselecting among multiple branches; the baseline state record saves the initial state and connection relationships of each engineering object, remaining unchanged during the simulation.

[0037] S2.2. Copy the baseline status record into a change status record and a current status record. Rewrite the current status of the engineering object to be adjusted in the change status record according to the engineering consulting matters, generating the changed engineering object status. Then, use the current status of the engineering object to be adjusted in the current status record as the current engineering object status. Specifically, Make two complete copies of the baseline status record to create a change status record and a current status record, respectively. Read the specific adjustment requirements according to the correspondence between the item number and the project object number, and rewrite the clearly required changes to the status content in the change status record. Status content not included in the adjustment requirements should remain in the baseline status. The current status record will not be subject to this adjustment requirement. When the adjustment requirement is described in text, determine the specific value according to the allowable status recorded in the valid data of the same project object; adjustment requirements where a unique value cannot be determined will not be extrapolated. In the circulating pump example, only the outlet pressure in the change status record is changed from 0.30 MPa to 0.36 MPa; the current status record retains 0.30 MPa. The initial states of the pressure verification point and the operating permit point remain "pending verification" and "not yet formed," respectively, and the initial opening of the branch regulating valve remains at 40%. "Maintaining the current status" means that the pressure adjustment requested in this application will not be implemented; subsequent status changes triggered normally by the original conditions still need to be extrapolated.

[0038] The baseline state record stores the common pre-deduction state for subsequent comparison; the change state record and the current state record respectively store the continuously updated deduction state under two initial conditions; the change project object state and the current project object state respectively represent the initial state of the project object to be adjusted in the two records.

[0039] S2.3. Starting from the project object to be adjusted in the change status record and the current status record respectively, propagate the changed project object status and the current project object status to the directly connected project objects in the project dependency relationship, forming a change propagation record and a current status propagation record, specifically, The initial states of the engineering objects to be adjusted are recorded in two separate status records. The states of the source engineering objects are checked against the directly connected project dependencies to ensure they meet the specified conditions. The state of the target engineering object is calculated based on the corresponding content of the specified states. When a single check involves multiple source engineering objects, all preceding states at the start of the same round of checks are read. After condition verification, these states are written into the target state to avoid changing the deduction results due to changes in the check order. For relationships where conditions are not met, the verification results are retained, and the target engineering object remains in its state before this round of checks. The change propagation record and the status propagation record respectively record the source engineering object number, the target engineering object number, the states before and after the change, the actual relationships used, and the verification round. Verified relationships where the target state has not changed are also retained, but not recorded as state changes. When multiple relationships require the same target to form the same state, the states are merged and all sources are retained. When multiple necessary relationships require the same target to form incompatible states, the deduction of the corresponding items is stopped, and the process is restarted after the relationship basis is verified.

[0040] S2.4. Compare the change propagation record and the current status propagation record with the baseline status record item by item, retaining the engineering objects whose status has changed and their new status, to form a change status change record and a current status change record. Specifically, By mapping the change propagation record and the current status propagation record to the baseline status record using the project object number, the status of the same project object after propagation is compared with the status before the simulation. The content of changes in value and category is retained to form the change status change record and the current status change record.

[0041] Changes in the initial state of the engineering object to be adjusted, which occur directly based on the consultation requirements, are also included in the change status record to avoid only counting subsequent impacts while omitting the adjustment action itself. Each change retains the baseline state, the state after the change, and the source of propagation. Intermediate engineering objects whose state has not changed are still retained in the propagation record for subsequent tracking of the relationship between them.

[0042] S2.5. Continue to propagate the status of engineering objects in the change status change record and the current status change record along the project dependencies. Add engineering objects with newly occurring status changes and their changed statuses to the change status change record and the current status change record until the status of the engineering objects no longer changes. Specifically, Continue verifying the dependencies of subsequent projects on engineering objects that have undergone new state changes in this round, and also check the reachability relationships that have not yet completed their initial verification to ensure that engineering objects whose initial state meets the conditions but have not yet completed the state update can participate in the simulation. Each round calculates the changed state based on the state at the start of the round, and updates the corresponding state records uniformly after all conditions are verified; new changes are added to the corresponding state change records, while unchanged transit relationships are retained in the propagation record; numerical states use the allowable range and recording precision specified in the valid data, and category states use the allowable states listed in the data. The same engineering object cannot be repeatedly judged as changed due to different units and different recording precisions.

[0043] The simulation ends when all project objects remain unchanged after a complete round of checks. If a loop exists in the propagation, compare the states of all project objects in each round. If the entire set of states reappears but the states in adjacent rounds are still different, it indicates that the propagation has been repeatedly switched. Stop the simulation of the corresponding matter and do not use the results of repeated switching for subsequent decisions. Cases that exceed the allowable state range of the data, lack the necessary prerequisite states, or have conflicting state requirements are also suspended. The simulation will start again from the baseline state after the basis verification is completed.

[0044] S2.6. Following the propagation order in the project dependencies, chain together the change status records to form an implementation change path, and chain together the current status change records to form a status quo maintenance path. Specifically, Based on the established project dependencies, the engineering objects in the two state change records are organized into implementation change paths and status quo maintenance paths, respectively. Connections are registered along the source-to-target direction. When multiple targets are connected from the same source, propagation branches are retained separately. When multiple sources reach the same target, all source engineering objects and their connections are retained. Completed loop propagation retains the actual relationships traversed, and repeated extension stops when the path reaches a registered engineering object again. Engineering objects whose state has not changed but which are connected to the target are maintained through the original propagation record; two state changes occurring at intervals are not directly considered connected. Path organization only changes the record arrangement and does not add new project dependencies.

[0045] S2.7. Continue to track the changes in the status of the project object along the implementation change path and the status quo maintenance path, and take the tracked changes in the status of the project object as the changes in the status of the project object generated by the implementation change path and the status quo maintenance path. Specifically, Check the source of the state change of the project object, the final state, and the actual project dependencies along the two paths. Match the stable state at the end of S2.5 with the baseline state to determine the changes that each project object needs to participate in the comparison.

[0046] When the same engineering object changes multiple times in intermediate stages, the difference between the stable state and the baseline state is compared, and the intermediate stages are retained in the propagation record for verification; the content of finally restoring the baseline state is no longer counted as the final state change.

[0047] The propagation relationships of the final state are based on the relationships actually triggered in the last round in which the final state was formed. When multiple relationships are satisfied together, they are fully preserved. Subsequent checks that only maintain the state do not cover the source of the state.

[0048] The continued tracking in this embodiment is used to complete the source and sequence of existing propagation results, without triggering state propagation again.

[0049] S2.8. Based on the propagation order of the engineering object in the implementation change path and the status quo maintenance path, the state change and related propagation relationships of the engineering object are reconstructed into implementation change state propagation chains and status quo maintenance state propagation chains, respectively. Specifically, Based on the correspondence between the source and the target in the two paths, the propagation relationship between the final state change and the actual supporting state change is continuously registered, forming an implementation change state propagation chain and a status quo maintenance state propagation chain, respectively. For each engineering object location, the engineering object number, baseline state, stabilized state, and propagation relationship are simultaneously stored, with branches and convergences maintaining their original affiliations. When the same engineering object has multiple source engineering objects, all propagation relationships are retained, and subsequent comparisons are made according to the engineering object number and propagation relationship.

[0050] The implementation change path and the status quo maintenance path represent the order of project object transmission and branch affiliation under two different simulation conditions. The two state propagation chains fully record the states before and after the change and their associated propagation relationships along their corresponding paths, used for comparing state changes and propagation sources. The propagation order indicates the sequence of transmission along project dependencies, while the associated propagation relationship clearly specifies which project object the transmission originates from and which project object it reaches.

[0051] S2.9. Extract continuous propagation segments from the implementation change state propagation chain and the status quo maintenance state propagation chain where the state changes of engineering objects are the same and the related propagation relationships are consistent. Define a common state propagation segment by the engineering objects at the beginning and end of the continuous propagation segment, and write the state changes of engineering objects and their related propagation relationships in the continuous propagation segment into the common state propagation segment to form a common propagation result. Specifically, ; In the formula, This represents the set of engineering object numbers in two state propagation chains that have the same baseline state, the same stable state after deduction, and the same set of associated propagation relationships. Indicates the project object number; This represents the set of engineering object numbers that participate in the final state change comparison in the implementation change state propagation chain; This represents the set of engineering object IDs that participate in the comparison of final state changes in the current state propagation chain. This indicates that the path to implement the change is numbered as follows. The baseline state corresponding to the engineering object; This indicates that the path numbered in the "Preserve Current Status" path is... The baseline state corresponding to the engineering object; This indicates that the path number in the implementation change path is... The state of the engineering object after it has stabilized; This indicates that the path numbered in the "Preserve Current Status" path is... The state of the engineering object after it has stabilized; The actual support number in the implementation change path is indicated as follows. The engineering objects form a set of related propagation relationships for the final state change; The actual support number in the path to maintain the status quo is... The engineering objects form a set of relationships for the final state change; each relationship includes the source engineering object number, the target engineering object number, the transmission direction, the triggering condition, and the corresponding state change content.

[0052] Starting with an engineering object that meets the consistency condition, the propagation continues along the common association propagation relationship between the two state propagation chains. When encountering inconsistent state changes, inconsistent association propagation relationships, branch positions, or merging positions, the propagation is divided into continuous propagation segments, and subsequent branches are processed separately. When passing through an already registered association propagation relationship again, the repeated extension stops. The first and last engineering objects of each continuous propagation segment, consistent state changes within the segment, and association propagation relationships are registered to form a common propagation result. When a continuous propagation segment contains only one engineering object, the same engineering object is registered as the first and last, and consistent association propagation relationships are retained. In the circulating pump example, both outlet pressures meet the pressure verification conditions. The pressure verification point changes from pending verification to passed, and the operating permit point changes from never formed to formed. The same association propagation relationship is used, which can form a common propagation result. The change in circulating pump outlet pressure and the change in branch regulating valve opening from 40% to 45% only exist in the implementation change path and are retained as differences.

[0053] A common state propagation segment is a continuous propagation segment in two state propagation chains that forms the same state change according to the same associated propagation relationship. The first and last engineering objects are used to determine the scope, and the state changes and associated propagation relationships within the segment are used to verify the consistency of the propagation results. The consistency of the entire propagation result cannot be determined solely based on the fact that the first and last engineering objects are the same.

[0054] S2.10. Based on the changes in the state of the engineering object and their associated propagation relationships recorded in the common state propagation segment, the common propagation results are simultaneously eliminated in the implementation change state propagation chain and the status quo maintenance state propagation chain, forming the implementation change difference propagation chain and the status quo maintenance difference propagation chain, specifically as follows: Based on the engineering object number and associated propagation relationship in the common state propagation segment, the corresponding content in the two state propagation chains are located respectively. Common state changes and the same associated propagation relationship are marked as not participating in subsequent difference collection, and the original state, propagation order and data basis are retained. Hiding only changes the scope of participation in difference collection, and the engineering object and project dependency relationship are still retained for subsequent verification of the preconditions for execution. The content that is not hidden in the implementation change path forms the implementation change difference propagation chain, and the content that is not hidden in the status quo maintenance path forms the status quo maintenance difference propagation chain. The two results retain the path attribution respectively.

[0055] S2.11. Based on the synchronous elimination of hidden propagation results, the propagation boundaries exposed in the implementation change state propagation chain and the status quo maintenance state propagation chain are reconnected to maintain the transmission order in the implementation change difference propagation chain and the status quo maintenance difference propagation chain, forming a difference propagation structure, specifically, Within each propagation branch, identify the differences that remain before and after the common state propagation segment, restore the original state propagation chain, and register the common state propagation segments between the differences. When there is only indirect transmission between the differences, retain the complete indirect transmission verification path and do not convert adjacent arrangements into direct project dependencies. Differences across branches remain separate, and all necessary related propagation relationships are retained at the merging points. When the common state propagation segment is located at the beginning or end of the branch, only the actual difference on one side is retained, and missing endpoints are not added. In the circulating pump example, after the pressure verification point and operation permit point are hidden, the circulating pump pressure change and the branch regulating valve opening change are aggregated according to the original sequence. Pressure verification and operation permit are still retained as the basis for execution, and the permit verification before valve adjustment cannot be omitted. After completing the connection between the preceding and following points and the branch affiliation, a difference propagation structure is formed.

[0056] The propagation boundary represents the engineering objects containing the preceding and following differences that are still retained after the common result is hidden; reconnection represents restoring the preceding and following connections of the remaining differences in the original propagation relationship; the difference propagation structure preserves the remaining differences, path attribution, and preceding and following connections, but does not represent the re-establishment of physical connections between engineering objects.

[0057] S2.12. Based on the implementation change path and status quo maintenance path to which the state changes of engineering objects belong in the difference propagation structure, the unique state changes of engineering objects and their associated propagation relationships for different paths are collected into path difference results, specifically, The remaining state changes and related propagation relationships are collected separately according to the implementation change path and the status quo maintenance path to form path difference results; when the same project object forms different states in two paths, the two states are saved separately; when the states are the same but the source relationships are different, the corresponding sources are saved separately to avoid merging different propagation bases; for project objects that change only in one path, the state after stabilization in the other path is also recorded, and the baseline state is used when the other path does not change; the path difference results retain the final state and source differences in both cases for subsequent determination of adjustments that need to be implemented and current status consequences that need to be avoided.

[0058] S2.13. Based on the propagation order in project dependencies, the path difference results and the associated propagation relationships between them are arranged sequentially to form a change difference impact set, specifically, The path difference results are arranged from the source to the target direction of the project dependency relationship. Differences within the same branch are kept sequential, while differences from different branches are grouped separately, and all related propagation relationships corresponding to the converging objects are retained. Circular connections maintain the original relationship and are not forcibly arranged in a unidirectional order. Each difference record includes the project object number, baseline state, the stable state of the two paths, path attribution, and valid data location information. When there are common state propagation segments, the verification location of the conditions within the segment is retained. All path difference results and their preceding and following relationships together form the change difference impact set, which can be used to verify differences by project object and to find the basis for the differences along the original branches.

[0059] S3. Verify the conditions of the change difference impact set, convert the difference impact that meets the applicable conditions into engineering consulting decisions and transmit them to the engineering execution end. The engineering execution end adjusts the engineering objects to be adjusted according to the engineering consulting decisions, records the actual status of the engineering objects after adjustment, compares the actual status of the engineering objects with the expected status of the engineering objects, marks the execution status deviation and the new propagation relationship, and forms the actual execution difference data.

[0060] S3.1 Obtain applicable conditions related to engineering consulting matters from valid engineering data in the project decision-making baseline data, and configure the applicable conditions to the path difference results in the change difference impact set to form an applicable condition correspondence. Specifically, From the valid engineering data of the project decision-making baseline, obtain the applicable project stage requirements, permissible status ranges, and pre-execution requirements for the current engineering consulting matters. Configure these requirements to the corresponding path difference results according to the engineering object number and related propagation relationships to form a correspondence of applicable conditions. Conditions that must be met simultaneously as specified in the data are fully retained; meeting only some conditions does not substitute for all conditions. In the circulating pump example, 0.28 to 0.38 MPa is the permissible outlet pressure range. Pressure verification and operational approval constitute requirements prior to branch regulating valve adjustments, all of which have corresponding data clauses. Applicable conditions are used to check whether adjustments can be executed, while triggering conditions for project dependencies are used to determine how the status affects subsequent engineering objects; these two types of uses are verified separately.

[0061] S3.2. Based on the correspondence of applicable conditions, verify the changes in the status of engineering objects and their related propagation relationships in the path difference results. Cut off the propagation relationships that do not meet the applicable conditions, and classify the remaining changes in the status of engineering objects and their related propagation relationships as differences that meet the applicable conditions. Specifically, Based on the applicable conditions, first check whether the path difference results are within the allowed project stage and allowed status range, then verify the prerequisite requirements along the related propagation relationship; for prerequisite requirements that have already been met, the confirmed actual status is adopted; for requirements that can only be met after the completion of the preceding actions, the preceding actions and completion status are retained, and the execution order is arranged by the subsequent engineering consulting decision, and continued after actual verification by the execution end; related propagation relationships that cannot meet the necessary conditions are truncated in this difference verification, and subsequent effects that depend on the truncated relationship are simultaneously stopped from being retained; when there are propagation branches that clearly allow the conditions to be met independently, the complete prerequisite requirements are re-verified before the corresponding effects are retained. Truncating does not delete the original project dependencies; when the application status of the engineering object to be adjusted cannot pass the condition verification, the data basis that failed is retained, and scattered subsequent actions are not pieced together into an executable decision.

[0062] S3.3. Transform the state changes of engineering objects in the context of differences that meet applicable conditions into corresponding state adjustment actions for the engineering objects, and determine the execution order of these state adjustment actions based on the correlation propagation relationship to form engineering consulting decisions. Specifically, For the impact of differences that meet the applicable conditions, the expected state of the project object is determined by the state of the project object after the implementation of the change path is stabilized, and compared with the actual state before execution. The state adjustment action is determined according to the adjustment method recorded in the effective project data.

[0063] The changes unique to the existing path are used to illustrate the potential consequences of not implementing the adjustment, and are not directly converted into actions that need to be taken; for two paths with the same status but different origins, the prerequisites for implementing the changed path are retained, and the same actions are not issued repeatedly.

[0064] Actions are arranged according to the propagation relationships and prerequisites in the common state propagation segments. The engineering object, pre-execution state, state adjustment actions, expected engineering object state, and prerequisite completion conditions are registered sequentially to form an engineering consulting decision. When there are loop connections, the execution order is based on the preceding objects and initiation conditions clearly defined in the valid data. Loops where the data does not specify the execution order do not generate adjustment actions. Engineering objects clearly included in the actual adjustment scope in the decision are all included in the execution verification scope of subsequent engineering objects to be adjusted in S3. For the circulating pump example, pressure adjustment, pressure verification, operation permit confirmation, and branch regulating valve opening adjustment are arranged according to the data. Verification cannot be skipped simply because two verifications have the same result.

[0065] S3.4. Transmit the engineering objects, state adjustment actions, and execution order from the engineering consulting decision-making process to the engineering execution end. The engineering execution end then changes the current state of the corresponding engineering objects according to the state adjustment actions and execution order to obtain the actual state of the engineering objects. Specifically, The engineering object number, status adjustment actions, execution sequence, and prerequisite completion conditions in the engineering consulting decision-making process are transmitted to the engineering execution end. The engineering execution end verifies the implementation object according to the on-site object number, completes the action through the on-site execution interface corresponding to the engineering object, and records the execution time. For example, for the circulating pump, a set value of 0.36 MPa is written into the existing pressure setting interface. After completing the pressure verification and operation permission confirmation, a set value of 45% is written into the valve opening setting interface. Then, the actual engineering object status is obtained from the on-site pressure measurement record, valve opening feedback, and permission confirmation record. Before each action begins, the actual prerequisite conditions necessary for subsequent actions are verified. If the conditions are not met, subsequent dependent actions are suspended. The simulated status cannot replace on-site confirmation. Feedback is saved according to the corresponding engineering object number, and the measurement unit, recording time, and completion mark are recorded.

[0066] S3.5. Following the execution order in engineering consulting decision-making, the actual and expected states of the same engineering object to be adjusted are arranged side-by-side to form an execution status comparison sequence. Specifically, In accordance with the execution order in engineering consulting decision-making, the expected state of the same engineering object and the actual state of the engineering object after the action are completed are recorded side by side to form an execution state comparison sequence; when multiple actions are performed on the same engineering object in stages, they are paired according to the engineering object number and the corresponding action order to avoid using the feedback from the previous time for the adjustment in the next time; for states that need to be stabilized before acceptance, the acceptance time and stabilization requirements specified in the valid data are adopted; actions that have not yet been completed are recorded as incomplete, and the lack of feedback is not recorded as having met the expectations; the execution records of different propagation branches retain the branch attribution.

[0067] S3.6. Verify the actual and expected states of engineering objects in the execution state comparison sequence item by item. Mark the engineering objects with inconsistent states as execution state deviations and record the position of the execution state deviation in the execution order. Specifically, The actual and expected states are compared according to the execution status comparison sequence. Category states are compared according to the same meaning. Numerical states are measured in a unified unit and the acceptance tolerance specified in the valid data is adopted. Numerical values ​​without specified tolerance are compared according to the same recording accuracy. Engineering objects that exceed the acceptance requirements are marked as execution status deviations, and the expected state, actual state, difference content and the order of action occurrence are recorded. Records of incomplete actions and missing valid measurements are retained as pending verification statuses and are not considered as confirmed status deviations. When the actual pressure of the circulating pump does not reach the acceptance requirement of 0.36 MPa, the pressure deviation corresponds to the circulating pump pressure adjustment action and is not mixed with subsequent valve opening feedback for comparison.

[0068] S3.7. Based on the location of execution state deviations, the engineering objects to be adjusted that continuously exhibit execution state deviations are compressed into continuous state deviation segments, and the first engineering object to be adjusted to experience an execution state deviation within the continuous state deviation segment is taken as the starting position of the state deviation. Specifically, In the execution status comparison sequence, the confirmed execution status deviations are checked separately for each branch. Engineering objects with adjacent execution sequences and consecutive deviations are grouped into the same continuous status deviation segment, and all objects and deviation contents within the segment are retained. When the actual status meets the requirements, the action is not yet completed, or the feedback has not been verified, the current segment ends, and the subsequently confirmed deviations form a new segment. Each segment uses the first deviation engineering object number and the corresponding action sequence to determine the starting position of the status deviation. Compression only merges the range representation of continuous deviations, does not delete the execution records within the segment, and does not combine deviations with similar times on different branches into one segment.

[0069] S3.8 Starting from the initial position of the state deviation, establish a verification propagation relationship between the subsequent project object to be adjusted that first experiences an execution state deviation and the previous project object to be adjusted, according to the execution order. Mark any verification propagation relationships not recorded in the project dependencies as new propagation relationships. Associate the execution state deviation and the new propagation relationships with the corresponding project objects to be adjusted to form actual execution difference data, specifically, Starting from the beginning of each state deviation and proceeding backward, within the same continuous state deviation segment, the engineering object that first deviates is paired with the preceding engineering object whose execution order is immediately adjacent, clearly identifying the preceding engineering object as the candidate source and the following engineering object as the candidate target. Simultaneously, the actual status of both ends, the time of occurrence, and on-site execution records are noted, forming a propagation relationship to be verified. Each pair of recorded project dependencies is compared against the two ends of the object, the direction of propagation, and the applicable conditions. New propagation relationships to be verified that are not covered by existing records are marked. The new propagation relationships are associated with the corresponding execution state deviations, and the actual status of all completed actions is collected to form actual execution difference data, ensuring that S4 can both update normally completed objects and verify deviation objects.

[0070] S4. Update the project status based on the actual engineering object status in the actual execution difference data, track the changes in the updated project status along the project dependencies, locate the project dependency gaps in the project dependencies where new propagation relationships are added, and supplement the project dependencies with the new propagation relationships to form the consulting decision results.

[0071] S4.1. Using the actual project object status in the actual execution difference data, replace the current project object status of the same project object in the project status to form an updated project status. Specifically, According to the engineering object number in the actual execution difference data, the actual engineering object status formed by the completed actions is written into the corresponding project status, and the pre-execution status, execution time and on-site record source are retained; the update adopts the actual measurement and confirmation results, and the objects with execution status deviations are also updated according to the confirmed actual status, and the on-site deviations are not covered according to the expected status; incomplete actions and unverified feedback do not cover the original confirmed status; after all confirmed statuses are updated, the updated project status is formed.

[0072] S4.2. Based on the propagation order in the project dependencies, sort the project objects that have changed in the updated project state, and record the project state changes between the project objects to form a project state change sequence. Specifically, Identify the engineering objects that have changed from their pre-execution state from the updated project status. Arrange the sources and targets according to the existing project dependencies, and add the actual change time reflected in the site records to form a project status change sequence. Multiple branches from the same source are arranged separately, and all project dependencies are retained at the branch confluence. For two engineering objects that lack existing transmission evidence, only the actual occurrence time and the relationship to be verified are retained, and they are not directly linked into a dependency relationship based on the time sequence. The project status change sequence reflects the transmission range that can be explained by the actual status change and the existing relationship.

[0073] S4.3. Place the newly added propagation relationship between the two ends of the project objects in the actual execution difference data into the corresponding order in the project state change sequence, verify the continuity of the propagation of existing project dependencies between the two ends of the project objects, and mark the gaps between project objects where the project state changes continuously but the existing project dependencies lack propagation relationships as project dependency gaps. Specifically, Map the objects at both ends of the newly added propagation relationship to the sequence of project state changes. If there is no confirmed state change at either end, keep it pending verification and do not fill in the sequence position with the expected change. For relationships where the actual changes at both ends have been confirmed, first find the direct relationship from the source to the target and the continuous indirect relationship along the existing project dependency relationship, and check the propagation conditions one by one with the actual state.

[0074] When a complete transmission path already exists that can explain the change in the target state, the original relationship is retained and gaps are not identified again. When there is no applicable continuous transmission path, the basis for the state change in the on-site execution records, connection acceptance records and valid documents is checked again. Verification needs to confirm at the same time that both ends have actual state transmission paths, the change in the source state precedes the change in the corresponding target, and the change in the target meets the clear preconditions and the corresponding content of the state change.

[0075] For relationships that cannot be directly confirmed by data, within the verification conditions allowed by valid data, the common preconditions that have been registered remain unchanged through the execution end, and the target response is recorded separately when the source status remains unchanged and when the source status changes; the target response is verified in conjunction with the confirmed connection relationship, and only after the data and execution evidence are consistent, the transmission links not covered by the existing relationship are marked as project dependency gaps; records of verification conditions not being met, inconsistent responses, and simultaneous changes in common preconditions are retained for verification and are not added to the relationship; for example, if two engineering objects deviate simultaneously due to the same power supply change, the time continuity is insufficient to support the addition of a new propagation relationship between the two engineering objects.

[0076] A project dependency gap indicates a delivery link that has a clear basis for status transmission but is not yet covered by the existing project dependencies. It does not simply mean a lack of data, mismatched names, or adjacent execution record times.

[0077] S4.4. The newly added propagation relationship is then added to the project dependency gap, and the propagation order between the project objects at both ends of the project dependency gap is rearranged according to the project state change sequence to form the supplemented project dependency relationship. Specifically, Newly added propagation relationships that have passed verification will be added to the corresponding project dependency gaps. The source project object number, target project object number, transmission direction, triggering conditions, corresponding content of status changes, and source of verification data will be fully recorded. The verification conclusions will be associated with and saved with the site records. The supplementary relationship only applies to the scope of verified project objects and prerequisites, and will not be extended to unverified project stages. The transmission order of the connected relationships will be updated according to the source to target direction. It will be checked whether the supplementary relationship and the original relationship require incompatible target states under the same conditions. If there is a conflict, it will be retained for verification and will not directly overwrite the original relationship.

[0078] When a new connection forms a loop, the state stability check in S2.5 is performed to confirm that a consistent state can be formed. After verifying the execution order specified in the valid data, it is used for subsequent deduction to form a supplementary project dependency relationship.

[0079] S4.5. Assign the updated project status to the engineering objects in the supplemented project dependencies to form the consultation decision result, specifically: The updated project status is mapped to the supplemented project dependencies according to the project object number. The project consulting decision, actual execution status, confirmed execution status deviations, and verified relationship supplements are saved to form the consulting decision results. Newly added propagation relationships that have not yet been verified are retained separately and do not participate in the next project dependency simulation. The next project consulting matter uses the confirmed current project object status and the already effective relationships as the basis to re-establish the project decision benchmark data and complete the update of the execution results for subsequent consulting processing.

[0080] Example 2, refer to Figures 5-6 This is the second embodiment of the present invention.

[0081] This embodiment takes a data center chilled water secondary side linkage commissioning project as an example; the project is in the electromechanical linkage commissioning stage, and the air conditioning units on the third and fourth floors have been put into trial operation; the site is equipped with secondary chilled water pump P-02, terminal differential pressure detection point DP-01, electric regulating valve V-3F of the third floor branch, electric regulating valve V-4F of the fourth floor branch, air conditioning unit AHU-3F of the third floor and air conditioning unit AHU-4F of the fourth floor, and the secondary pump control logic corresponds to the project object number C-02; in addition, the secondary pump safety interlock confirmation interface is registered as IL-02 to save the original safety interlock verification status; all project objects have been registered in the project knowledge base.

[0082] The joint commissioning record shows that P-02 operates at the manually set 45 Hz, V-3F maintains a fixed opening of 82%, and V-4F maintains a fixed opening of 78%. When the air conditioning units on the third and fourth floors are under the high-load conditions recorded in the commissioning record, the measured differential pressure of DP-01 is lower than the acceptance limit specified in the "Requirements for Joint Commissioning of Chilled Water". The measured chilled water flow of the two branch lines does not meet the acceptance requirements specified in the corresponding hydraulic balance commissioning record.

[0083] For the engineering consulting item ZX-017 regarding the formation of water supply status, C-02 will be adjusted from manual fixed-frequency control to automatic differential pressure regulation control at the end point. The item number, project object number, and adjustment content will be registered. The operating mode of P-02, the regulation status of V-3F and V-4F, and the subsequent changes in the flow of the two-level branch will be deduced according to the project dependencies, and then the adjustment actions that need to be actually implemented will be determined. The original safety interlock requirements will remain effective.

[0084] Search the project knowledge base for related engineering documents concerning ZX-017, including "Secondary Chilled Water Pump Control Logic Description", "Chilled Water Secondary Side Piping and Valve Table", "Secondary Pump Inverter Parameter Confirmation Record", "Third-Floor Chilled Water Branch Hydraulic Balance Debugging Record", "Fourth-Floor Chilled Water Branch Hydraulic Balance Debugging Record", and "Chilled Water Linkage Debugging Requirements"; verify the version approval record, effective date, substitution relationship, applicable engineering objects, and project stage according to the document number.

[0085] The "Secondary Chilled Water Pump Control Logic Description" contains versions V2 and V3; the version history clearly states that version V3 has been approved and has replaced version V2, therefore version V3 is retained; the secondary pump installation inspection data generated during the equipment installation phase is not applicable to the current linkage commissioning status judgment and is excluded from the scope of this data; after verification, a valid set of engineering data is formed.

[0086] Establish a correspondence based on the project object number in the data entries; the entries involving P-02, V-3F, and V-4F in the "Table of Secondary Piping and Valves for Chilled Water" correspond to the corresponding project objects respectively; the control mode entry corresponds to C-02, the secondary pump operation entry corresponds to P-02, the terminal differential pressure entry corresponds to DP-01, and the safety interlock verification entry corresponds to IL-02; the three-layer hydraulic balance commissioning record corresponds to V-3F and AHU-3F, and the four-layer hydraulic balance commissioning record corresponds to V-4F and AHU-4F; each correspondence simultaneously retains the data number, version, and clause location, forming the project object association result.

[0087] Based on valid engineering data, the status transmission direction, triggering conditions, and changed status are registered; after C-02 completes the automatic differential pressure adjustment setting at the end and IL-02 passes verification, P-02 is ready to be put into automatic adjustment operation; when P-02 operates within the adjustment range specified in the valid parameter record, DP-01 provides valid feedback, and the corresponding operating conditions in the hydraulic balance record are met, DP-01 can enter the differential pressure acceptance range; after DP-01 completes differential pressure verification, V-3F and V-4F respectively meet the prerequisites for putting into automatic adjustment; when the branch valves are normally adjusted, the corresponding air conditioning units are operating, and the water-side conditions meet the requirements, the corresponding branch flow can enter the acceptance range; the prerequisites that jointly determine the target status are fully registered.

[0088] The valid documentation also stipulates that the original safety interlocks must be confirmed in each round of joint commissioning; when C-02 adopts manual fixed-frequency control and automatic differential pressure adjustment control at the end, the same interlocking check content is performed; the relationship between C-02 and IL-02 is registered as follows: when the confirmation of this round of joint commissioning has been initiated and the original safety protection conditions meet the interlocking verification requirements, IL-02 will enter the verification process from pending confirmation; switching of control mode is not a necessary condition for interlocking verification, ensuring that the current status quo path can also perform interlocking confirmation.

[0089] The confirmed relationships are organized into project dependency data; the branch affiliation of DP-01 to V-3F and DP-01 to V-4F is retained respectively, and the subsequent transmission direction of V-3F to AHU-3F and V-4F to AHU-4F is retained respectively; the pipeline sharing relationship is saved as connection data, and the state propagation relationship of V-3F to V-4F is not directly registered based solely on the shared pipeline.

[0090] The project decision-making baseline data was established using status records that had been verified on-site before the start of this simulation and were applicable to the current joint commissioning phase. C-02 is manually controlled at a fixed frequency, P-02's actual operating frequency is 45 Hz, DP-01 feedback is effective but the differential pressure has not reached the acceptance limit, V-3F and V-4F are at 82% and 78% fixed opening respectively, AHU-3F and AHU-4F are both running but the corresponding branch flow has not met the standard, and IL-02 is pending confirmation for this round of joint commissioning. The numerical status retains the unit of measurement, acquisition time, and record source; any content with conflicting records will be incorporated into the baseline after on-site verification.

[0091] Identify directly and indirectly related engineering objects from C-02 along the project dependencies, and supplement the prerequisite states involved in the joint triggering conditions to form a baseline state record; when the same engineering object arrives via different branches, only one state is retained, and all arrival relationships are saved separately; copy the baseline state record into a change state record and a current state record, and only change C-02 to automatic differential pressure regulation control at the end in the change state record; the current state record maintains manual fixed frequency control, and the remaining engineering objects adopt the same initial state.

[0092] Propagation is performed along two separate status records; the preceding status at the start of each round is read, and the target status is updated uniformly after the condition verification is completed; in the status change record, IL-02 enters the verification pass stage from pending confirmation according to the joint debugging confirmation requirements; after the C-02 control mode and IL-02 status meet the conditions together, P-02 enters the automatic adjustment state of operating within the specified range according to the effective parameter record; then DP-01 is deduced to enter the differential pressure acceptance range, V-3F and V-4F are put into automatic adjustment respectively, and the corresponding branch flow of AHU-3F and AHU-4F enters the acceptance range.

[0093] In the current status record, C-02 continues to be manually controlled at a fixed frequency, and IL-02 still enters the verification process from pending confirmation according to the same joint commissioning confirmation requirements; since C-02 has not implemented control mode adjustment, P-02 continues to operate at 45 Hz, and DP-01, the two branch valves and the flow of the two branch lines remain at the baseline state; after a complete round of checks without any further status changes, the simulation of the two paths ends.

[0094] The simulated stable state is compared with the baseline state to form a change state record and a current state change record. The change in control method that occurred directly in C-02 according to the consultation requirements is included in the change state record. The source of propagation is also saved for changes in P-02 and subsequent engineering objects. The change path and the current state maintenance path are organized and implemented according to the original transmission direction. The states before and after the change and the actual related propagation relationships are further registered to form two state propagation chains.

[0095] Comparing the records of IL-02 in the two state propagation chains, both paths show that the process starts from the pending confirmation stage of the current joint debugging and passes the verification. The source engineering object is C-02, and the triggering conditions, transmission direction, and verification content are consistent, thus forming a common propagation result. The common state propagation segment only contains IL-02, and the first and last engineering objects are both registered as IL-02, while retaining the association propagation relationship from C-02 to IL-02.

[0096] Mark the common state changes corresponding to IL-02 as not participating in the difference aggregation, while retaining the interlock verification records and execution prerequisites; continue to retain the C-02 control mode change, P-02 operation mode change, DP-01 differential pressure change, two branch valve adjustment status changes and two-level branch flow changes in the implementation change path; the current status maintenance path notes the baseline status maintained by the corresponding engineering objects.

[0097] The remaining differences are sorted out according to the original propagation order. The verification position required by IL-02 is still retained between C-02 and P-02, and the two branches are respectively placed. After the common propagation results are hidden, the interlock confirmation is still an action that must be completed before P-02 can run automatically. All remaining differences, the final state of the two paths and the propagation basis together form the set of changes in the difference impact.

[0098] Obtain applicable conditions from valid engineering data; for P-02 to be put into automatic adjustment, the requirements of the linkage commissioning stage must be met, the frequency converter must be allowed to adjust automatically, the DP-01 feedback must be valid, and the original safety interlock verification must be passed; the effective adjustment range after automatic operation must also be consistent with the parameter confirmation record; for V-3F and V-4F to be put into automatic adjustment, the corresponding branch flushing and exhaust must be completed, the actuator feedback must be normal, the valve must not be locked by fault, and the DP-01 differential pressure verification must be passed; the flow acceptance of the two-level branches requires the air conditioning unit to be in operation, the valve adjustment status to be valid, and the flow measurement record to be valid.

[0099] Conditions that have already been met are recorded on-site; conditions that require the completion of preceding actions to be met are retained as prerequisites for execution; engineering consulting decisions are arranged in the following order: C-02 control mode adjustment, IL-02 interlock confirmation, P-02 automatic operation input and operation range verification, DP-01 differential pressure verification, and then V-3F and V-4F automatic adjustment and corresponding branch flow acceptance are arranged respectively; each action is recorded with the project object number, pre-execution status, expected project object status and prerequisite completion conditions.

[0100] The engineering execution unit adjusted the control mode of C-02 according to the site number and confirmed IL-02 according to the original inspection content; the site feedback indicated that both actions met expectations; then the automatic operation of P-02 was put into operation, and DP-01 continued to provide effective differential pressure feedback.

[0101] The operating frequency of P-02 stopped increasing after rising from 45 Hz to 48 Hz. Field parameter readings and operation records indicate that P-02 was limited by a temporary 48 Hz frequency upper limit, and the actual effective adjustment range was inconsistent with the automatic adjustment range required by the effective parameter confirmation record. The measured differential pressure of DP-01 was greater than the value recorded before execution, but still lower than the lower limit of the linkage commissioning and acceptance.

[0102] The automatic operation of P-02 has been completed, but the actual operating range has not reached expectations; the differential pressure measurement and verification of DP-01 has been completed, but the measured results have not passed the acceptance test; since the differential pressure prerequisites required for V-3F and V-4F have not been met, the automatic adjustment of the two valves has been suspended at the engineering execution end, and the flow acceptance of the two branch lines has been marked as incomplete; it has been confirmed on-site that V-3F and V-4F are still maintaining a fixed opening of 82% and 78% respectively, and the valve adjustments that have not yet been performed will not be registered as deviations in the execution status.

[0103] like Figure 6 As shown, C-02 has switched to automatic differential pressure regulation control at the end, and IL-02 has completed this round of safety interlock verification. DP-01 collects the water supply differential pressure and provides the measurement results to C-02 along the feedback direction indicated by the dotted line. C-02 controls P-02 to operate based on the differential pressure feedback. P-02 has been put into automatic regulation, but is limited by the 48 Hz upper limit. Although the differential pressure of DP-01 has increased, it is still below the acceptance lower limit. P-02 supplies water to the third and fourth floor branches through the shared water supply main. The third floor branch is connected to AHU-3F via V-3F, and the fourth floor branch is connected to AHU-4F via V-4F. Since the differential pressure precondition has not yet been met, V-3F maintains a fixed opening of 82%, and V-4F maintains a fixed opening of 78%. The automatic regulation of both valves is suspended. AHU-3F and AHU-4F continue to be in operation. This round of branch flow acceptance has not yet been completed.

[0104] The execution status comparison sequence is formed according to the order of actions; the actual status of C-02 and IL-02 is as expected; the actual status of P-02 is that automatic adjustment has been put into operation but is limited by the 48 Hz upper limit, which is inconsistent with the expected effective adjustment range; the actual status of DP-01 is that the differential pressure has risen but has not passed the acceptance test, which is inconsistent with the expected differential pressure verification.

[0105] The P-02 operating range verification and the DP-01 differential pressure verification are adjacent completed checks within the same propagation branch. Since the two checks show confirmed deviations consecutively, they are classified into the same continuous state deviation section. The starting position of the state deviation is determined by the P-02 project object number and the sequence of automatic operation activation. Since subsequent valve actions have not yet been executed, the continuous state deviation section ends at DP-01.

[0106] P-02 and DP-01 are registered as a propagation relationship to be verified, with the following information noted: actual frequency of P-02, temporary frequency upper limit, measured differential pressure of DP-01, time of status change, and source of field record. Although the existing project dependencies already include P-02 to DP-01, the original status correspondence is based on the condition that the effective adjustment range meets the parameter confirmation record, and does not cover the situation where the adjustment range is insufficient due to temporary frequency limitation. Therefore, the uncovered restricted operation relationship is marked as a new propagation relationship and will continue to be retained as a relationship to be verified.

[0107] The actual execution difference data is formed by collecting records of normal completion of C-02 and IL-02, execution status deviations of P-02 and DP-01, subsequent actions that have not yet been completed, and propagation relationships to be verified.

[0108] Update the project status according to the confirmed actual status; C-02 is updated to automatic differential pressure regulation control at the end, IL-02 is updated to the current interlock verification passed, P-02 is updated to automatic regulation has been put into operation and actual operation is limited by the 48 Hz upper limit, DP-01 is written with the latest measured differential pressure and the status of failure to pass acceptance; V-3F and V-4F retain the confirmed fixed opening degree; AHU-3F and AHU-4F corresponding branches retain the most recently confirmed flow record, and note that the current flow acceptance is not completed; the status before execution, execution time and the source of the field record are still saved.

[0109] Organize the project status change sequence according to the existing project dependencies and note the actual occurrence time; P-02 changes from manual 45 Hz operation to automatic regulation limited operation, and the measured differential pressure of DP-01 changes with the operation. Both ends have confirmed actual status changes; Although DP-01 is still in the differential pressure non-compliant state, the measured differential pressure value has changed. Keep separate records of the value change and the acceptance status.

[0110] Examine the direct and continuous indirect transmissions from P-02 to DP-01 along the existing relationships; the applicable conditions of the original direct relationships cannot cover the temporary 48 Hz frequency limiting conditions, and no existing indirect relationships that can fully explain the limited operation results were found; temporarily retain the records to be verified, and further examine the pipeline connection data, effective parameter records and field execution records to verify the actual state transmission path.

[0111] To illustrate the subsequent verification, this embodiment adopts the scenario where the upper limit of the automatic adjustment frequency allowed by the valid data is higher than 48 Hz, and the temporary frequency limit value on site is 48 Hz; within the debugging range allowed by the valid data, the load of the two-story air conditioning units, the 82% opening degree of V-3F, the 78% opening degree of V-4F, the on / off status of the pipeline, the differential pressure setting requirements, and the original safety protection conditions remain unchanged, and P-02 is subjected to controlled verification.

[0112] First, maintain the temporary 48 Hz upper limit and record the actual frequency of P-02 and the differential pressure of DP-01; then, according to the approved verification requirements, restore the temporary frequency limit to the adjustment range allowed by the parameter confirmation record, and record the response of P-02 and the differential pressure of DP-01; after completing the verification, restore the settings before verification and record the operating status again; all frequency adjustments are within the allowable range of valid data, and the pump operation record and differential pressure measurement record are corresponding to the unified acquisition time.

[0113] The following verification results, which yielded consistent responses, illustrate the relationship confirmation: When the 48 Hz upper limit was maintained, P-02 reached its operating upper limit, and the differential pressure of DP-01 remained below the acceptance lower limit; after restoring the allowable adjustment range, the actual frequency of P-02 continued to increase, and DP-01 subsequently entered the differential pressure acceptance range; after restoring the 48 Hz upper limit, DP-01 again fell below the acceptance lower limit; during the period when the source status was maintained, the target status did not change in the opposite direction, the change in the source status preceded the corresponding target response, and the records of the common preconditions remained consistent.

[0114] Based on the confirmed pipeline connections and comparison records, it was confirmed that under the current load and fixed valve opening conditions, the 48 Hz operating limit of P-02 could keep DP-01 in a state of substandard differential pressure; the restricted operational transmission content not yet covered by the existing relationships was identified as a gap in project dependencies; records where common preconditions changed, responses could not be repeated, and verification data was insufficient were retained for further verification.

[0115] The newly verified propagation relationships will be added to the project dependencies. The source project object will be registered as P-02, the target project object as DP-01, and the propagation direction will be registered as P-02 to DP-01. The triggering conditions are limited to the load, valve opening, pipeline status, effective differential pressure feedback, and 48 Hz operating upper limit that have been verified this time. The corresponding target status will be registered as the differential pressure not reaching the acceptance lower limit, and will be associated with specific measurement records, parameter reading records, and on-site verification records.

[0116] The original relationship is used for operating conditions where the effective adjustment range meets the parameter confirmation requirements, and the supplementary relationship is used for the confirmed restricted operating conditions. The trigger conditions and target states of the two types of relationships are checked item by item to confirm that there are no incompatible state requirements under the same conditions. Then, the state propagation can be checked to ensure stable termination according to Example 1. The supplementary relationship is only used within the verified applicable range. Unverified load and valve opening states continue to be processed according to the corresponding data.

[0117] After the verification is completed and the settings before verification are restored, the operating status of P-02 and the differential pressure of DP-01 are confirmed again, and the last confirmed field status is taken as the current project status. The updated project status and the supplemented project dependencies are matched according to the engineering object number, and the engineering consulting decisions, completed actions, execution status deviations, suspended subsequent actions and relationship verification basis are saved to form the consulting decision results corresponding to ZX-017.

[0118] like Figure 5As shown, the data is arranged from top to bottom according to the simulation comparison, actual execution, and relationship verification. In the implementation change path, C-02 is adjusted to automatic differential pressure regulation control at the end, P-02 is put into automatic regulation after the interlock verification is passed, DP-01 differential pressure verification is passed, and the two branch valves enter automatic regulation respectively, with the corresponding branch flow rates passing acceptance. In the status quo maintenance path, C-02 remains under manual fixed-frequency control, P-02 operates at 45 Hz, and V-3F and V-4F maintain fixed openings of 82% and 78% respectively, but the differential pressure and branch flow rates still do not meet the standards. In both paths, IL-02 has entered interlock verification from pending confirmation and uses the same correlation propagation relationship. Therefore, only the content corresponding to IL-02 is framed as a common propagation result, eliminating... The interlock verification requirement is still retained as a prerequisite for execution. The actual execution section shows that after C-02 adjustment is completed and IL-02 verification is passed, P-02 is limited by the 48 Hz upper limit, the differential pressure of DP-01 rises but is still below the acceptance lower limit, P-02 and DP-01 constitute a continuous state deviation section, and P-02 is the starting position of the deviation. The dashed arrows leading to the two valves indicate that subsequent actions are suspended, the valves maintain their original fixed opening, and the flow acceptance of the two branch lines is not completed. The bottom performs relationship verification in the order of existing transmission path verification, common prerequisite condition maintenance, and frequency limit state comparison. After the verification is passed, the restricted working condition triggering conditions and corresponding state changes that are not yet covered between P-02 and DP-01 are supplemented, and the verification basis is saved.

[0119] The consultation decision results clearly record that the requirements for this round of water supply improvement have not yet been completed. The acceptance of V-3F and V-4F automatic regulation and the flow of the two-level branch still need to wait for the differential pressure prerequisite to be met. When new engineering consultation matters are formed in the future regarding frequency limitation, the project decision benchmark data will be re-established based on the most recently confirmed on-site status and the already effective relationship basis, and the impact of restricted operation will be incorporated into the dual-path state simulation.

[0120] This embodiment also provides a computer device applicable to the intelligent decision support method for engineering consulting based on a project knowledge base, comprising: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement the intelligent decision support method for engineering consulting based on a project knowledge base as proposed in the above embodiment.

[0121] The computer device can be a terminal, comprising a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0122] This embodiment also provides a storage medium storing a computer program that, when executed by a processor, implements the intelligent decision support method for engineering consulting based on a project knowledge base as proposed in the above embodiments. The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Red-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0123] In summary, this invention improves the accuracy of change difference identification by synchronously eliminating hidden effects of common propagation results. Based on the same project decision-making baseline data, two paths are formed: an implementation change path and a status quo maintenance path. The changes in the state of engineering objects and their associated propagation relationships in these two paths are reconstructed into a consequence chain. The identical changes in the state of engineering objects and the consistent associated propagation relationships are used as the criteria for identifying common propagation results. This eliminates overlapping results generated by the propagation of existing project states and predetermined dependencies from the scope of difference analysis. After eliminating the hidden effects of common propagation results, the original propagation order and path attribution of the residual chain are maintained, allowing the remaining changes in the state of engineering objects and their associated propagation relationships to be aggregated into path difference results according to the paths, forming a change difference impact set. This enables subsequent condition verification to focus on the actual differences, enhancing the ability of engineering consulting decisions to identify the location, propagation direction, and state change results of key impacts.

[0124] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for intelligent decision support in engineering consulting based on a project knowledge base, characterized in that, include: The project knowledge base is used to filter out invalid engineering data corresponding to engineering consulting matters, and the valid engineering data is associated with engineering objects and project dependencies to form project decision-making benchmark data; A dual-path state simulation is performed on the engineering objects to be adjusted in the project decision baseline data. The state changes of the engineering objects generated by the implementation change path and the status quo maintenance path are tracked along the project dependency relationship. Common propagation results with the same state changes and consistent propagation relationship of the engineering objects are hidden. The path difference results corresponding to the remaining differences are collected to form the change difference impact set. The set of changes and differences is verified for conditions. The differences that meet the applicable conditions are converted into engineering consulting decisions and transmitted to the engineering execution end. The engineering execution end adjusts the engineering objects to be adjusted according to the engineering consulting decisions, records the actual status of the engineering objects after adjustment, compares the actual status of the engineering objects with the expected status of the engineering objects, marks the execution status deviation and the new propagation relationship, and forms the actual execution difference data. The project status is updated based on the actual engineering object status in the actual execution difference data. The changes in the updated project status are tracked along the project dependencies. The gaps in the project dependencies where new propagation relationships are added are located, and the new propagation relationships are added to the project dependencies to form the consulting decision results.

2. The intelligent decision support method for engineering consulting based on project knowledge base as described in claim 1, characterized in that: The data used to form the project decision-making benchmark are specifically: Search for related engineering data in the project knowledge base, compare the valid relationships between related engineering data, remove invalid engineering data and retain valid engineering data to form a set of valid engineering data; Each valid engineering data in the valid engineering data set is matched with an engineering object, and the valid engineering data that point to the same engineering object are associated to form an engineering object association result. The relationships between project objects are traced along the project object association results. The relationships that can continuously transmit changes in the state of project objects are identified as project dependencies. The identified project dependencies are organized according to the transmission direction of the relationships and the corresponding relationships of project objects to form project dependency data. The engineering objects and project dependencies in the project dependency data are integrated with the set of valid engineering data to form the project decision-making benchmark data.

3. The intelligent decision support method for engineering consulting based on a project knowledge base as described in claim 2, characterized in that: The process of tracing the state changes of engineering objects along the project dependencies, resulting from the implementation of change paths and the status quo maintenance paths, specifically involves... Read the current status of the engineering object to be adjusted from the project decision baseline data, and arrange the engineering objects directly connected to the engineering object to be adjusted and their current status in sequence along the project dependency relationship to form a baseline status record; Copy the baseline status record to a change status record and a current status record. Rewrite the current status of the engineering object to be adjusted in the change status record according to the engineering consulting matters, generate the change status of the engineering object, and take the current status of the engineering object to be adjusted in the current status record as the current status of the engineering object. Starting from the project objects to be adjusted in the change status record and the current status record respectively, the change status of the project objects and the current status of the project objects are propagated to the project objects directly connected in the project dependency relationship, forming change propagation record and current status propagation record; The change propagation record and the status propagation record are compared with the baseline status record item by item. The engineering objects whose status has changed and the status of the changed engineering objects are retained to form the change status record and the status change record. The engineering objects in the change status record and the current status change record continue to propagate the status of the engineering objects along the project dependencies. The engineering objects whose status has changed and their changed status are added to the change status record and the current status change record until the status of the engineering objects no longer changes. According to the propagation order in the project dependencies, the records of changes in the status quo are linked together to form the implementation path, and the records of changes in the current status quo are linked together to form the current status maintenance path. Continue to track changes in the status of engineering objects along the implementation change path and the status quo maintenance path, and use the tracked changes in the status of engineering objects as the changes in the status of engineering objects generated by the implementation change path and the status quo maintenance path.

4. The intelligent decision support method for engineering consulting based on project knowledge base as described in claim 3, characterized in that: The engineering consulting matters mentioned refer to the specific adjustment requirements and corresponding consulting content raised during the project implementation process for the engineering objects to be adjusted.

5. The intelligent decision support method for engineering consulting based on project knowledge base as described in claim 4, characterized in that: The set of effects of the changes is specifically formed as follows: Based on the propagation order of the engineering object in the implementation change path and the status quo maintenance path, the state change of the engineering object and the associated propagation relationship are reconstructed into the implementation change state propagation chain and the status quo maintenance state propagation chain, respectively. Extract continuous propagation segments from the implementation change state propagation chain and the status quo maintenance state propagation chain, where the state changes of engineering objects are the same and the related propagation relationships are consistent. Use the engineering objects at the beginning and end of the continuous propagation segments to define the common state propagation segment, and write the state changes of engineering objects and related propagation relationships in the continuous propagation segment into the common state propagation segment to form a common propagation result. Based on the changes in the state of the engineering object and the associated propagation relationships recorded in the common state propagation segment, the common propagation results are simultaneously eliminated in the implementation change state propagation chain and the status quo maintenance state propagation chain, forming the implementation change difference propagation chain and the status quo maintenance difference propagation chain; Based on the propagation boundaries exposed in the implementation change state propagation chain and the status quo maintenance state propagation chain after synchronous fading of the common propagation results, the associated propagation relationships that maintain the transmission order in the implementation change difference propagation chain and the status quo maintenance difference propagation chain are reconnected to form a difference propagation structure. Based on the implementation change path and status quo maintenance path to which the state changes of engineering objects in the differential propagation structure belong, the unique state changes of engineering objects and their associated propagation relationships of different paths are collected into path difference results. Based on the propagation order in project dependencies, the path difference results and the associated propagation relationships between the path difference results are arranged sequentially to form a set of change difference impacts.

6. The intelligent decision support method for engineering consulting based on project knowledge base as described in claim 5, characterized in that: The adjusted actual state of the recorded project object is specifically as follows: Obtain applicable conditions related to engineering consulting matters from valid engineering data in project decision-making benchmark data, configure the applicable conditions to the path difference results in the change difference impact set, and form the correspondence of applicable conditions; Based on the correspondence of applicable conditions, the changes in the status of engineering objects and their related propagation relationships in the path difference results are checked. The related propagation relationships that do not meet the applicable conditions are cut off, and the remaining changes in the status of engineering objects and their related propagation relationships are classified as differences that meet the applicable conditions. The changes in the state of engineering objects under the influence of differences that meet the applicable conditions are converted into corresponding state adjustment actions for the engineering objects, and the execution order of the state adjustment actions is determined based on the correlation propagation relationship to form engineering consulting decisions. Transmit the engineering objects to be adjusted, the status adjustment actions, and the execution order in the engineering consulting decision-making process to the engineering execution end; By adjusting the state of the corresponding project object according to the state adjustment actions and execution order through the project execution terminal, the current state of the project object is changed, and the actual state of the project object is obtained.

7. The intelligent decision support method for engineering consulting based on project knowledge base as described in claim 6, characterized in that: The applicable conditions related to the engineering consulting matters include the requirements for the status of the engineering object recorded in the valid engineering data, restrictions on project dependencies, constraints on engineering implementation, and the execution conditions corresponding to the engineering consulting matters.

8. The intelligent decision support method for engineering consulting based on project knowledge base as described in claim 6, characterized in that: The differential impact that meets the applicable conditions is the differential impact that enters the engineering consulting decision-making transformation stage after the conditions are verified, and serves as the basis for forming the status adjustment actions and execution order of the engineering object to be adjusted.

9. The intelligent decision support method for engineering consulting based on project knowledge base as described in claim 8, characterized in that: The formation of actual execution difference data specifically refers to, According to the execution order in engineering consulting decision-making, the actual state and expected state of the same engineering object to be adjusted are arranged side by side to form an execution status comparison sequence. The actual and expected states of engineering objects in the execution state comparison sequence are verified one by one. Engineering objects with inconsistent states are marked as execution state deviations, and the position of the execution state deviation in the execution order is recorded. Based on the location of the execution state deviation, the engineering objects to be adjusted that continuously exhibit execution state deviations are compressed into a continuous state deviation segment, and the first engineering object to be adjusted that exhibits an execution state deviation in the continuous state deviation segment is taken as the starting position of the state deviation. Starting from the initial position of the state deviation, establish a verification propagation relationship between the subsequent engineering object to be adjusted that first experiences an execution state deviation and the previous engineering object to be adjusted, according to the execution order, and mark the verification propagation relationship not recorded in the project dependency relationship as a new propagation relationship; The execution status deviation and the newly added propagation relationship are associated with the corresponding engineering objects to be adjusted, forming actual execution difference data.

10. The intelligent decision support method for engineering consulting based on a project knowledge base as described in claim 9, characterized in that: The formation of the consultation and decision-making results specifically refers to, By using the actual project object status in the actual execution difference data, the current project object status of the same project object in the project status is replaced to form the updated project status; By using the propagation order in the project dependencies, the project objects that have changed in the updated project state are sorted sequentially, and the project state changes between the project objects are recorded to form a project state change sequence. Place the newly added propagation relationship at both ends of the project objects in the actual execution difference data into the corresponding order in the project state change sequence, verify the continuity of the existing project dependency relationship between the two project objects, and mark the gaps between project objects where the project state changes continuously but the existing project dependency relationship lacks a propagation relationship as project dependency gaps. The newly added propagation relationship is added to the project dependency gap, and the propagation order between the project objects at both ends of the project dependency gap is rearranged according to the project state change sequence to form the supplemented project dependency. The updated project status is assigned to the engineering objects in the supplemented project dependencies, forming the consulting decision result.

Images