A method and system for triggering events in industrial internet building spaces

Abstract

This invention relates to the field of industrial internet technology and provides a method for triggering events in industrial internet building spaces, comprising the following steps: S1: setting data management rules for data flow during building space event triggering in the order of responsible object, responsible scope, and responsible content; S2: when a building space query event is triggered, calling the data management rules to generate a corresponding data viewing permission scope and pushing it to the responsible object, or when a building space management event is triggered, calling the data management rules to generate a message push strategy to obtain the responsible object for the next process, so as to push management data to the responsible object. By optimizing the data management rules, precise control of data permissions, flexible and easy-to-use rule configuration, and intelligent and efficient rule activation logic are achieved, thereby improving the automation and intelligence level of the entire event triggering process and meeting the increasingly complex management needs of modern industrial internet building spaces.

Description

Technical Field

[0001] This invention relates to the technical field of industrial internet, and in particular to an event triggering method and system in industrial internet building space. Background Technology

[0002] In the current booming development of industrial internet-enabled building spaces, various complex business activities heavily rely on efficient and intelligent event-triggered methods and systems to achieve rational resource allocation, smooth business process flow, and precise execution of management decisions. However, existing event-triggered methods and systems in industrial internet-enabled building spaces suffer from numerous unresolved issues, severely limiting their effectiveness in practical applications.

[0003] First, the current system suffers from serious vulnerabilities and deficiencies in data access control. The division of data permissions lacks clear logic and fine granularity, failing to accurately define access and operation permissions for various event-related data based on different user roles and business scenarios. In industrial internet-enabled building spaces, users at different departments and levels have significantly different needs and permissions for event data, but existing access control methods are often too simplistic and crude, leading to chaotic data access. For example, some users may have viewing permissions for event data beyond their scope of responsibility, which not only increases the risk of data leakage but may also lead to the improper dissemination of sensitive information. Furthermore, unreasonable data access settings can affect the accuracy and effectiveness of event triggering, preventing relevant personnel from obtaining key information in a timely manner, thus delaying event processing and response.

[0004] Secondly, the flexibility and ease of use of rule configuration are severely lacking. The existing event-triggered rule configuration interface and process design are not user-friendly, lacking intuitiveness and convenience. The arrangement and combination of rule configuration fields are unreasonable, requiring users to face complex options and logical relationships when setting rules, making it difficult to quickly and accurately express their needs. Moreover, when business requirements change, the existing rule configuration system struggles to respond and adjust quickly. For example, with the continuous optimization and innovation of business processes in industrial internet building spaces, new event types and triggering conditions are constantly emerging, requiring the ability to flexibly add, modify, and delete rules. However, current systems often require specialized technical personnel to perform complex code modifications and system configurations, which is too high a barrier for ordinary business users, severely impacting the system's adaptability and scalability.

[0005] Furthermore, the rule activation logic contains numerous flaws. The existing event-triggered rule activation mechanism is neither clear nor accurate enough, failing to effectively handle complex and ever-changing business scenarios. For different types of events, such as equipment failure alarms, production schedule changes, and safety hazard alerts, there is a lack of unified and scientific rule application standards. When an event is triggered, it is often impossible to accurately determine which rules should be executed and how to combine rules with the specific event context, leading to a chaotic and inefficient event handling process. In addition, the instability of the rule activation logic also poses risks to system operation. When business rules undergo minor changes, a large-scale adjustment and modification of the entire rule activation logic may be required. This not only increases the difficulty and cost of system maintenance but also easily introduces new errors and vulnerabilities.

[0006] Taking a common incident like equipment malfunction reporting as an example, existing systems exhibit significant problems in the processing. When clinical staff report repair requests after discovering equipment malfunctions, chaotic data access control can lead to unauthorized personnel viewing and modifying repair information, affecting the accuracy and seriousness of the reports. Regarding rule configuration, the dispatch rules are inflexible, failing to intelligently dispatch orders based on multiple factors such as equipment type and urgency of the malfunction, resulting in unreasonable allocation of maintenance resources and low maintenance efficiency. Furthermore, in terms of rule activation logic, after a repair incident occurs, relevant information cannot be promptly and accurately pushed to appropriate maintenance and management personnel, delaying the optimal time for fault handling.

[0007] In summary, existing event triggering methods and systems in industrial internet building spaces suffer from problems in data access control, rule configuration, and rule activation logic, which severely impact the overall system performance and application value. These issues not only lead to inefficient event processing and wasted resources but also potentially pose security risks to the normal operation of industrial internet building spaces. Summary of the Invention

[0008] To address the aforementioned issues, the present invention aims to provide an event triggering method and system for industrial internet building spaces. By optimizing data management rules, it achieves precise control of data permissions, flexible and easy-to-use rule configuration, and intelligent and efficient rule activation logic, thereby improving the automation and intelligence level of the entire event triggering process and meeting the increasingly complex management needs of modern industrial internet building spaces.

[0009] The above-mentioned objective of this invention is achieved through the following technical solutions: A method for triggering events in an industrial internet building space includes the following steps: S1: Set up data management rules for data flow during the triggering of building space events, in the order of responsible object, responsible scope, and responsible content; S2: When a building space query event is triggered, the data management rules are invoked to generate the corresponding data viewing permission scope and push it to the responsible object; or when a building space management event is triggered, the data management rules are invoked to generate a message push strategy to obtain the responsible object of the next process, so as to push the management data to the responsible object.

[0010] Furthermore, in step S1, data management rules for data flow during the triggering of architectural space events are set according to the order of responsible object, responsible scope, and responsible content, specifically as follows: Configure each data management rule in the order of the responsible object, the responsible scope, and the responsible content, focusing the main body of the data management rule on the responsible object, which includes a work group or an individual, that is, clearly defining the object of data processing and management; The scope of responsibility includes management objects and rule conditions. The management objects include information such as equipment assets, contract records, installation and acceptance projects, training records and documents. Different ranges of optional conditions are set for different management objects, and different rule conditions are set. The scope of responsibility is defined as binding the business within the scope of responsibility with the business division of the responsible object.

[0011] Furthermore, in step S2, when a building space query event is triggered, the data management rules are invoked to generate a corresponding data viewing permission scope and push it to the responsible object, specifically: The building space query events include queries for equipment asset files and maintenance work orders. The scope of these queries changes over time and cannot be recorded to generate a single work order. The subject of the architectural space query event is the query operator. When the query operator initiates a query, the first query data under the user's original data permissions is obtained. Then, all the data management rules to which the query operator belongs as the responsible object are retrieved. The second query data that conforms to the scope and content of responsibility of the data management rules is then retrieved. The first query data obtained from the original data permissions and the second query data obtained based on the data management rules are deduplicated to obtain all the data that the query operator can view.

[0012] Further, in step S2, when a building space management event is triggered, the data management rules are invoked to generate a message push strategy to obtain the responsible object for the next process, so as to push management data to the responsible object, specifically: The building space management events mentioned include objective and real events such as repair requests, contract expiration, and meter validity period expiration. Once they occur, the events themselves will not change; only the attributes of the events will change. After the building space management event is triggered, the responsible object that has been configured in other processes is first obtained. Then, it is determined that the triggered device and the building space management event are both contained in any of the data management rules. The responsible object that meets the conditions is found through the data management rules. After deduplicating the responsible objects obtained twice, the management data is pushed to the management object to trigger the subsequent management process.

[0013] Furthermore, the event triggering methods in industrial internet building spaces also include: Data permissions triggered by architectural space events include inherent data permissions and variable data permissions. The inherent data permissions are based on the original data permissions of the department to which the subject belongs, while the variable data permissions exist in the form of the division of labor rules of the responsible object generated by the data management rules. The data scope of the two is the union of the two. The inherent data permissions are divided into two categories according to the different management objects: The first category of management objects is information initiated or generated based on physical equipment, including information such as equipment files and repair work order management. The data permission scope is whether the department to which the physical equipment belongs / the department that uses it is within its scope. The second category of management objects is information that can exist independently of physical equipment, including information such as contract management and document management. The data permission scope is whether the management part of the management object is within its scope.

[0014] Furthermore, when the triggered building space management event is a fault report, the specific workflow includes: After discovering a device malfunction, the device user reports the malfunction through the industrial internet system and creates a repair work order. Based on the repair work order, it is determined that the triggered device and the device malfunction event are both contained within any one of the data management rules. The order is then sent to the responsible person through the data management rule for processing. After receiving the repair order, the dispatch manager reviews it. Once the review is approved, the dispatch manager matches the repair personnel according to the data management rules and dispatches the order to the repair personnel for processing. After receiving the repair work order, the maintenance personnel may begin repair work, apply to transfer the work order to other engineers or maintenance teams, or suspend repair work. After the repair is completed, the order is sent to the person in charge of the order or the person who created it for acceptance.

[0015] Furthermore, the event triggering methods in industrial internet building spaces also include: When the status of the repair work order changes, the industrial internet system calls the data management rules to generate a message push strategy to obtain the responsible object for the next process, so as to push the repair to the responsible object; The industrial internet system configures rules, including dispatch rules, maintenance process rules, and acceptance rules, through the data management rules, and automatically performs operations such as dispatching, transferring, and suspending the repair work orders according to the configured data management rules.

[0016] An event-triggered system for performing events in an industrial internet building space as described above includes: The data management rule generation module is used to set data management rules for data flow during the triggering of building space events, according to the order of responsible object, responsible scope, and responsible content. The building space event triggering module is used to, when a building space query event is triggered, invoke the data management rules to generate a corresponding data viewing permission scope and push it to the responsible object; or, when a building space management event is triggered, invoke the data management rules to generate a message push strategy to obtain the responsible object for the next process, so as to push management data to the responsible object. A computer device includes a memory and one or more processors, the memory storing computer code that, when executed by the one or more processors, causes the one or more processors to perform the method described above.

[0017] A computer-readable storage medium storing computer code that, when executed, performs the method described above.

[0018] Compared with the prior art, the present invention has at least one of the following beneficial effects: By configuring data management rules in the order of responsible object, scope, and content, the rule subject is clearly focused on the responsible object. Whether it is a work group or an individual, the data processing and management object can be clearly defined. Compared with the traditional vague rule settings, this configuration method greatly improves the clarity and operability of the rules, making it more convenient and efficient for users to understand and apply the rules.

[0019] (2) For building space query events, such as equipment asset file queries and maintenance work order queries, by first obtaining the query data under the user's original data permissions, then retrieving the query data based on data management rules, and performing deduplication, it is possible to accurately determine all the data that the query operator can view. This method solves the problems of unclear permissions and chaotic data viewing scope in traditional query events, ensuring that users can only obtain data within their permission range, thus improving data security and query accuracy. In building space management events, such as repair requests and contract expiration, by first obtaining the originally configured responsible parties, then querying the responsible parties that meet the conditions according to data management rules, and then pushing management data after deduplication, the intelligent and precise message push is realized. This avoids the problems of inaccurate and untimely information push in traditional management events, ensuring that relevant information can be accurately conveyed to the appropriate personnel, effectively improving the efficiency and response speed of event handling.

[0020] (3) Data permissions are divided into inherent data permissions and variable data permissions, with the scope of both being the union of the two. Furthermore, inherent data permissions are further categorized according to the different managed objects. This data permission management method is more scientific and reasonable, taking into account both the user's original data permissions based on their department and the variable data permissions granted by the division of labor rules generated by the data management rules. Compared with the traditional single data permission management model, it can more comprehensively and accurately control users' access to and operation of data, effectively ensuring data security and privacy. Attached Figure Description

[0021] Figure 1 This is an overall flowchart of the event triggering method in the industrial internet building space of the present invention; Figure 2 This is a schematic diagram of an interface example of the data management rule configuration method of the present invention; Figure 3 This is a schematic diagram of a sample equipment asset list within the scope of responsibility of this invention; Figure 4 This is a schematic diagram illustrating the prompt for required fields not being filled in in this invention; Figure 5 This is a diagram illustrating the calling logic of the data management rules in this invention. Figure 6 This is a schematic diagram of the query event rule invocation process of the present invention; Figure 7 This is a schematic diagram of the event rule invocation process of the present invention; Figure 8 This is a schematic diagram illustrating the full-organizational data access permissions of the present invention; Figure 9 This is a flowchart of the fault reporting process in the building space management of this invention; Figure 10This is a structural diagram of the event triggering system in the industrial internet building space of this invention. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0023] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in this specification means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0024] First Embodiment like Figure 1 As shown, this embodiment provides an event triggering method in an industrial internet building space, including the following steps: S1: Set up data management rules for data flow during the triggering of building space events, in the order of responsible object, responsible scope, and responsible content.

[0025] In this embodiment, step S1 specifically involves configuring each data management rule in the order of the responsible object, the responsible scope, and the responsible content, focusing the main body of the data management rule on the responsible object, which includes a work group or an individual, i.e., clearly defining the data processing and management object; the responsible scope includes the management object and rule conditions, and the management object includes information such as equipment assets, contract records, installation and acceptance projects, training records, and document materials; different selectable ranges of conditions are set for different management objects, and different rule conditions are set. The scope of responsibility is defined as binding the business within the scope of responsibility with the business division of the responsible object.

[0026] like Figure 2 The image shown is an example of an interface for configuring data management rules in this embodiment. The rule configuration page will be optimized and iterated upon based on the existing version, mainly including component optimization, text guidance optimization, and operation optimization.

[0027] (1) Entrance A new "Management Rules" section has been added under System Configuration in the left-hand menu, replacing the original "Division of Labor Rules".

[0028] The existing functions are based on the division of labor between maintenance, quality control, and metrology. However, in real management scenarios, multiple functions often overlap. For example, medical engineers are usually responsible for both maintenance and regular quality control.

[0029] (2) Configuration page display The display logic of the configuration page remains largely consistent with existing functionality, grouping data management rules into sets and displaying the configured rules by set. This iteration primarily includes the following adjustments: Adjust the order of the fields within the rule to display them as three categories: responsible party, scope of responsibility, and responsible content. Focusing the rule body on the responsible party helps users have a clearer understanding of the core elements of rule setting, namely, who is responsible for it.

[0030] The quantity of equipment assets within the "Scope of Responsibility" field is appended after the first condition. Clicking on the quantity of equipment assets displays a complete list of all equipment assets on the right, with a default of 100 items per page. The list can be closed by clicking outside the selected area or by clicking the close button in the upper right corner of the selected area. Equipment asset lists associated with contracts use a unified component. For example... Figure 3 The image shown is a sample diagram of the equipment asset list within the scope of responsibility.

[0031] Add a "Responsibilities" field. This binds business processes to task allocation rules, increasing the usability of these rules.

[0032] It also allows users to edit and modify existing rules.

[0033] (3) Add rules The addition of rules remains largely consistent with existing functionality. The main adjustments in this iteration include: A "Responsible Content" field has been added, which supports single and multiple selections for users and departments.

[0034] The "Scope of Responsibility" field has been expanded to include two selection options: managed objects and rule conditions. Managed objects include equipment assets, contract records, installation and acceptance projects, training records, and documentation. The selectable conditions for the scope of responsibility will vary depending on the managed object.

[0035] The equipment asset supports fields such as type, professional category, management department, affiliated institution (displayed and effective when equipment assets within an institution belong to multiple institutions), affiliated department, using department, current location, and a maximum number of names. All fields support dropdown selection for single or multiple selections. The management department can be selected from any department within the institution or "unrestricted management department." When "unrestricted management department" is selected, it is not possible to select departments within the institution simultaneously.

[0036] A "Responsible Content" field has been added to bind business functions to job responsibilities. Supports viewing equipment assets and subscribing to repair notifications; viewing equipment assets is selected by default and cannot be deselected. Subscribing to contract expiration notifications and metering validity expiration notifications will not be implemented in this iteration due to incomplete message center upgrades.

[0037] If any of the three categories—"Responsible Content," "Scope of Responsibility," and "Responsible Content"—is left blank, a message will appear under the corresponding missing field upon confirmation, prompting "Please fill in the required field," and the border of the corresponding checkbox will be highlighted in red. For example... Figure 4 The image shown is a diagram illustrating the prompt when a required field is not filled.

[0038] (4) Editing rules It supports editing based on already saved rules.

[0039] S2: When a building space query event is triggered, the data management rules are invoked to generate the corresponding data viewing permission scope and push it to the responsible object; or when a building space management event is triggered, the data management rules are invoked to generate a message push strategy to obtain the responsible object of the next process, so as to push the management data to the responsible object.

[0040] In this embodiment, step S2 specifically includes: like Figure 5 The diagram illustrates the call logic of data management rules. First, we clarify that the trigger condition for a rule call is the detection of a specific event. This event could be a user's proactive query, a repair request, or a change in data after certain conditions are met, such as a contract nearing its expiration date. Furthermore, we understand that rule calls constrain subsequent management processes, ensuring that the right people receive the right information. Therefore, the logic for a rule taking effect can be abstracted as "trigger condition trigger - rule call - management process trigger".

[0041] Finally, the application of the task allocation rule involves granting additional permissions to the responsible party, beyond the user's own data permissions, to perform tasks related to the equipment assets within their designated area of ​​responsibility. For example, if Zhang San can view the equipment assets in the ICU, and the task allocation rule is configured so that "[Responsible party Zhang San] can view the equipment asset files for [equipment assets professionally classified as emergency medical equipment] and perform [repair order message push operations]", then Zhang San can view the equipment asset files for both ICU and equipment professionally classified as emergency medical equipment, and also has the permission to receive push notifications after a repair request is submitted for equipment professionally classified as emergency medical equipment.

[0042] (1) Triggering conditions We can first divide the triggered events into two categories. One category is query events, including queries of equipment asset files and maintenance work orders. The scope of these queries will change over time and cannot be recorded as a single work order. The other category is management events, such as repair requests and contract expiration dates. These are objective realities, and once they occur, the event itself will not change; only the attributes of the event will change.

[0043] The query event application rules address the question of what content users can see. Query events include equipment asset file queries, maintenance work order queries, etc. When applying query event rules, based on the operator's existing data permission scope for viewing equipment assets, the rules designated for that operator grant that operator the permission to view equipment assets within the scope of the configured equipment assets.

[0044] Management event application rules address the question of which user should receive information. Management events include repair notifications, contract expiration reminders, and meter expiration reminders. When applying management event rules, the information flow goes beyond the originally configured personnel. It also extends the information flow to the responsible parties within the rules that govern the equipment asset that triggered the management event. These responsible parties must possess the corresponding responsibilities. For example, if User 1 is already subscribed to equipment asset 'a', and rules 1 and 2 cover equipment asset 'a', with User 2 and Department 1 as their responsible parties, both having notification subscription permissions, then after a repair request is generated, the work order will be pushed to User 1, User 2, and all users under Department 1.

[0045] All management events will generate work orders, even near-expiration reminders will generate separate work orders. This way, when monitoring events, only a unified check of whether new data has been added to the database is needed, instead of the monitoring part requiring hard-coded adjustments and additions to the code when adding or adjusting the management events to be monitored. All management events generate work orders, with unified configuration of the database tables to be monitored; adding new data immediately applies the rules and triggers subsequent management processes.

[0046] (2) Calling rules like Figure 6 The diagram illustrates the query event rule invocation process. The subject of the query event is the operator. When a user initiates a query, in addition to the device assets within their original data permissions, they are also granted additional viewing permissions for device assets within the same scope through rules. The deduplication result of these two permissions represents all the device assets that the operator can view.

[0047] like Figure 7The diagram illustrates the process of invoking rules for management events. The management event topic is used to transfer information to designated users. After a management event occurs, in addition to the originally designated responsible parties, rules also transfer information to additional responsible parties. The deduplication result of these two processes constitutes the list of users to whom the management process needs to be routed.

[0048] The reason for positioning the task allocation rules as granting users additional management permissions is primarily to prevent conflicts from occurring if the priority of the task allocation rules is higher than existing management permissions. For example, subscription notifications will become a supplement to the task allocation rules in the future, serving as a case-specific management method for specially managed equipment assets.

[0049] (3) Management process trigger The management processes involved in this update include repair request notifications, contract expiration notifications, and metering expiration notifications, all of which fall under the category of push notifications. The following explanation will use push notifications as an example. However, it's important to note that with future adjustments to management processes, the division of responsibilities can be extended to more management scenarios, such as scrapping and procurement applications. Rules can be used to assign responsibility for business flows (including approval flows) within the management process. Therefore, this section will still be referred to as "management process," even though this iteration only involves the single subsequent management process of push notifications.

[0050] Furthermore, the event triggering method in the industrial internet building space of this embodiment also includes: like Figure 8 The diagram illustrates the data access permissions for the entire organization. Data permissions are a way to control the range of data that users can view and manipulate. Understanding the structure of data permissions helps in understanding the logic behind the following requirements.

[0051] Data permissions triggered by architectural space events include inherent data permissions and variable data permissions. The inherent data permissions are based on the original data permissions of the department to which the subject belongs, while the variable data permissions exist in the form of the division of labor rules of the responsible object generated by the data management rules. The data scope of the two is the union of the two.

[0052] The inherent data permissions are divided into two categories according to the different managed objects: The first category of managed objects is information initiated or generated based on physical equipment, including equipment files and repair work order management. The data permission scope is whether the department to which the physical equipment belongs / the department using it is within its scope. The second category of managed objects is information that can exist independently of physical equipment, including contract management and document management. The data permission scope is whether the managed part of the managed object is within its scope. For example, if user A's department is the Medical Equipment Department, then A has data permissions for equipment belonging to / using the Medical Equipment Department and the management records generated therefrom, as well as contracts and documents managed by the Medical Equipment Department.

[0053] For existing customers, adding multiple affiliated departments remains feasible, and the operational pressure after the launch of this feature is at a low level.

[0054] The aforementioned data permission settings are based on the premise that existing functional modules are capable of differentiating data permissions. For example, if the repair work order management module does not have data permissions set, anyone with viewing permissions for the repair work order management module can view all repair work order records for the entire organization. In this case, differentiating data permissions would be meaningless, as it would be impossible to assign repair requests with different building space codes to different repair personnel. Therefore, developing an intelligent management rule engine is particularly important.

[0055] One specific application of this embodiment is fault reporting in building space management; therefore, this embodiment uses the fault reporting process as an example for detailed explanation. Figure 9 As shown, when the triggered building space management event is a fault report, the specific workflow includes: 1. Reporting process for repair work orders 1.1 Work Order Creation Clinical staff: After discovering a malfunction, they report it through the system. The report information includes a description of the malfunction and equipment information.

[0056] Work order withdrawal: If the repair information is incorrect or needs to be modified, clinical staff can withdraw the work order themselves.

[0057] 1.2 Work Order Approval The dispatcher is responsible for reviewing the repair order upon receipt. If the order information is incomplete or incorrect, it can be returned to the clinical staff for re-filling.

[0058] Work order closure: If the work order information is complete and no repair is required, the work order can be closed directly.

[0059] 1.3 Work Order Dispatch Dispatch manager: After approval, the work order will be dispatched to the corresponding maintenance team or engineer based on the type and urgency of the fault.

[0060] Automatic order dispatch: The system can automatically match and dispatch orders to suitable maintenance personnel according to preset rules.

[0061] 2. Work Order Processing Flow 2.1 Work Order Acceptance Maintenance Engineer: After receiving the dispatched work order, perform the order acceptance operation and confirm the start of maintenance work.

[0062] 2.2 Maintenance Process Under Repair: The engineer begins repair work. If an unsolvable problem is encountered, the order can be transferred to another engineer or repair team.

[0063] Suspend repairs: If it is necessary to wait for parts or for other reasons during the repair process, the repair can be suspended and the reason for suspension should be recorded.

[0064] 2.3 Work Order Acceptance Acceptance: After the repair is completed, the person in charge of dispatching the work order or the person who created the work order shall conduct an acceptance inspection. Once the acceptance is passed, the work order status shall be updated to "Completed".

[0065] Acceptance failed: If the acceptance fails, the work order will be returned to the maintenance engineer for repair.

[0066] 3. Work order status flow 3.1 Work Order Status Pending dispatch: After a work order is created, it awaits review and dispatch by the person in charge of dispatching.

[0067] Pending orders: The work order has been dispatched and is awaiting acceptance by the maintenance engineer.

[0068] Under Repair: The work order has been accepted and the repair engineer is currently performing the repairs.

[0069] Suspension: The maintenance process is suspended due to special reasons.

[0070] Pending Acceptance: Repairs completed, awaiting acceptance.

[0071] Closed: The work order has been completed or no repair is required.

[0072] 3.2 Message Push Strategy When a work order changes status, the system will send notifications to relevant personnel according to a preset message push strategy to ensure timely information delivery.

[0073] 4. Work Order Management Rule Engine 4.1 Rule Configuration System administrators can configure rules for work order management, including dispatch rules, maintenance process rules, and acceptance rules.

[0074] 4.2 Intelligent Decision Making The rules engine automatically performs operations such as dispatching, transferring, and pausing work orders based on the configured rules, thereby improving the efficiency and accuracy of work order processing.

[0075] 5. Work order data permissions 5.1 Data Access Control The system controls users' access to and operation of work order information based on their roles and permissions, ensuring data security.

[0076] Second Embodiment like Figure 10 As shown, this embodiment provides an industrial internet building space event triggering system for executing the industrial internet building space event triggering method as described in the first embodiment, characterized in that it includes: Data management rule generation module 1 is used to set data management rules for data flow during the triggering of building space events, according to the order of responsible object, responsible scope, and responsible content. The building space event triggering module 2 is used to, when a building space query event is triggered, call the data management rules to generate the corresponding data viewing permission scope and push it to the responsible object, or when a building space management event is triggered, call the data management rules to generate a message push strategy to obtain the responsible object of the next process, so as to push the management data to the responsible object.

[0077] A computer-readable storage medium stores computer code that, when executed, performs the methods described above. Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. This program can be stored in a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0078] The above description is merely a preferred embodiment of the present invention. The scope of protection of the present invention is not limited to the above embodiments. All technical solutions falling within the scope of the present invention's concept are within the scope of protection of the present invention. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principles of the present invention should also be considered within the scope of protection of the present invention.

[0079] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

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

Claims

1. A method for triggering events in an industrial internet building space, characterized in that, Includes the following steps: S1: Set up data management rules for data flow during the triggering of building space events, in the order of responsible object, responsible scope, and responsible content; S2: When a building space query event is triggered, the data management rules are invoked to generate the corresponding data viewing permission scope and push it to the responsible object; or when a building space management event is triggered, the data management rules are invoked to generate a message push strategy to obtain the responsible object of the next process, so as to push the management data to the responsible object.

2. The event triggering method in industrial internet building space according to claim 1, characterized in that, In step S1, data management rules for data flow during the triggering of architectural space events are set in the order of responsible object, responsible scope, and responsible content. Specifically: Configure each data management rule in the order of the responsible object, the responsible scope, and the responsible content, focusing the main body of the data management rule on the responsible object, which includes a work group or an individual, that is, clearly defining the object of data processing and management; The scope of responsibility includes management objects and rule conditions. The management objects include information such as equipment assets, contract records, installation and acceptance projects, training records and documents. Different ranges of optional conditions are set for different management objects, and different rule conditions are set. The scope of responsibility is defined as binding the business within the scope of responsibility with the business division of the responsible object.

3. The event triggering method in industrial internet building space according to claim 1, characterized in that, In step S2, when a building space query event is triggered, the data management rules are invoked to generate the corresponding data viewing permission scope and push it to the responsible object, specifically: The building space query events include queries for equipment asset files and maintenance work orders. The scope of these queries changes over time and cannot be recorded to generate a single work order. The subject of the architectural space query event is the query operator. When the query operator initiates a query, the first query data under the user's original data permissions is obtained. Then, all the data management rules to which the query operator belongs as the responsible object are retrieved. The second query data that conforms to the scope and content of responsibility of the data management rules is then retrieved. The first query data obtained from the original data permissions and the second query data obtained based on the data management rules are deduplicated to obtain all the data that the query operator can view.

4. The event triggering method in industrial internet building space according to claim 1, characterized in that, In step S2, when a building space management event is triggered, the data management rules are invoked to generate a message push strategy to obtain the responsible object for the next process, so as to push management data to the responsible object, specifically: The building space management events mentioned include objective and real events such as repair requests, contract expiration, and meter validity period expiration. Once they occur, the events themselves will not change; only the attributes of the events will change. After the building space management event is triggered, the responsible object that has been configured in other processes is first obtained. Then, it is determined that the triggered device and the building space management event are both contained in any of the data management rules. The responsible object that meets the conditions is found through the data management rules. After deduplicating the responsible objects obtained twice, the management data is pushed to the management object to trigger the subsequent management process.

5. The event triggering method in industrial internet building space according to claim 1, characterized in that, Also includes: Data permissions triggered by architectural space events include inherent data permissions and variable data permissions. The inherent data permissions are based on the original data permissions of the department to which the subject belongs, while the variable data permissions exist in the form of the division of labor rules of the responsible object generated by the data management rules. The data scope of the two is the union of the two. The inherent data permissions are divided into two categories according to the different management objects: The first category of management objects is information initiated or generated based on physical equipment, including information such as equipment files and repair work order management. The data permission scope is whether the department to which the physical equipment belongs / the department that uses it is within its scope. The second category of management objects is information that can exist independently of physical equipment, including information such as contract management and document management. The data permission scope is whether the management part of the management object is within its scope.

6. The event triggering method in industrial internet building space according to claim 1, characterized in that, When the triggered building space management event is a fault repair report, the specific workflow includes: After discovering a device malfunction, the device user reports the malfunction through the industrial internet system and creates a repair work order. Based on the repair work order, it is determined that the triggered device and the device malfunction event are both contained within any one of the data management rules. The order is then sent to the responsible person through the data management rule for processing. After receiving the repair order, the dispatch manager reviews it. Once the review is approved, the dispatch manager matches the repair personnel according to the data management rules and dispatches the order to the repair personnel for processing. After receiving the repair work order, the maintenance personnel may begin repair work, apply to transfer the work order to other engineers or maintenance teams, or suspend repair work. After the repair is completed, the order is sent to the person in charge of the order or the person who created it for acceptance.

7. The event triggering method in industrial internet building space according to claim 6, characterized in that, Also includes: When the status of the repair work order changes, the industrial internet system calls the data management rules to generate a message push strategy to obtain the responsible object for the next process, so as to push the repair to the responsible object; The industrial internet system configures rules, including dispatch rules, maintenance process rules, and acceptance rules, through the data management rules, and automatically performs operations such as dispatching, transferring, and suspending the repair work orders according to the configured data management rules.

8. An industrial internet building space event triggering system for executing the industrial internet building space event triggering method as described in any one of claims 1-7, characterized in that, include: The data management rule generation module is used to set data management rules for data flow during the triggering of building space events, according to the order of responsible object, responsible scope, and responsible content. The building space event triggering module is used to, when a building space query event is triggered, call the data management rules to generate the corresponding data viewing permission scope and push it to the responsible object, or when a building space management event is triggered, call the data management rules to generate a message push strategy to obtain the responsible object of the next process, so as to push the management data to the responsible object.

9. A computer device comprising a memory and one or more processors, the memory storing computer code that, when executed by the one or more processors, causes the one or more processors to perform the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing computer code, wherein when the computer code is executed, the method of any one of claims 1 to 7 is performed.

Images