Fire-fighting equipment preventive maintenance task generation method and system based on cloud platform

Abstract

The application discloses a fire-fighting facility preventive maintenance task generation method and system based on a cloud platform, relates to the fire-fighting operation and maintenance technical field, and comprises the following steps: comparing the operation states of fire-fighting facilities to obtain a current degradation rate, calculating an excess amount and shortening a remaining maintenance time length, and determining a preventive maintenance deadline; setting the fire-fighting facilities to be executed in a maintenance exit state to obtain a suspended maintenance task; calculating an interval time length between a suspended maintenance task formation time and the preventive maintenance deadline, and comparing the interval time length with a maintenance task recovery required time length to obtain a recovery conflict task; restoring each fire-fighting facility to a fire-fighting facility operation state before the fire-fighting facility is restored to the maintenance exit state, and writing the recovery conflict result into the to-be-executed maintenance task to obtain a preventive maintenance task. The application improves the time matching of the maintenance task and the fire-fighting facility recovery by comparing the available time of the suspended maintenance task with the fire-fighting facility recovery required time length through industrial cloud computing.

Description

Technical Field

[0001] This invention relates to the field of fire protection operation and maintenance technology, and in particular to a method and system for generating preventive maintenance tasks for fire protection facilities based on a cloud platform. Background Technology

[0002] With the continuous improvement of the digital management level of building fire protection facilities, preventive maintenance of fire protection facilities based on cloud platforms is gradually developing from periodic manual inspections to data-driven operation and maintenance. Existing technologies usually rely on industrial cloud computing to centrally manage the operational data generated by facilities such as fire detection, fire water supply, smoke control and fire separation, and combine equipment files, historical fault records, maintenance cycles, inspection results and building space information to comprehensively analyze the reliability of facility operation and maintenance needs. The cloud management platform determines the maintenance objects based on the degree of equipment abnormality, operation duration, established maintenance cycle and historical maintenance, and generates corresponding maintenance work orders and task arrangements according to maintenance time, equipment importance and operation resource allocation, thereby realizing centralized management of building fire protection facility operation information, maintenance plans and on-site operation information.

[0003] However, existing preventive maintenance task generation methods focus more on the degree of equipment malfunction, maintenance cycle, and task priority. They lack collaborative analysis of time constraints after changes in fire protection capabilities during maintenance operations. For fire protection facilities within the same fire compartment that have overlapping protection ranges, functional substitutions, or linkage dependencies, the entry of some facilities into maintenance operations may cause a reduction in local fire protection capabilities. Furthermore, task adjustments, equipment restoration, and subsequent operations require a certain amount of time, which can easily lead to a situation where maintenance timeliness requirements and fire protection continuity are mutually constrained. This means that the preventive maintenance task generation process fails to consider the loss of fire protection areas after the maintenance of fire protection facilities and the recovery time of maintenance tasks, resulting in a conflict in execution sequence between maintenance timeliness requirements and fire protection continuity. Summary of the Invention

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

[0005] Therefore, this invention provides a cloud-based method for generating preventive maintenance tasks for fire protection facilities to solve the problem of execution sequence conflicts between maintenance timeliness requirements and fire protection continuity.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: In a first aspect, the present invention provides a method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform, which includes, The degradation status of fire protection facilities is compared to obtain the current degradation rate. The excess of the current degradation rate relative to the historical stable degradation rate is calculated, and the remaining maintenance time of the preset maintenance period is shortened. The remaining maintenance time with the shortest duration is selected, and the selected remaining maintenance time is extended. The end time of the extension is determined as the deadline for preventive maintenance. The pending maintenance tasks of each fire protection facility are arranged according to the deadline of preventive maintenance, and the fire protection facilities of each pending maintenance task are set to the maintenance exit state. The fire protection missing areas before and after the maintenance exit state are compared, and the pending maintenance tasks with newly added fire protection missing areas are designated as postponed maintenance tasks. Calculate the interval between the time when the deferred maintenance task is formed and the deadline of the preventive maintenance, and compare it with the time required to restore the obtained maintenance task to obtain the conflicting task to be restored. After completing the verification of the pending maintenance tasks, restore each fire protection facility to its operating state before maintenance was lifted, and write the result of the restoration conflict into the pending maintenance tasks to obtain the preventive maintenance tasks.

[0007] As a preferred embodiment of the cloud platform-based preventive maintenance task generation method for fire protection facilities described in this invention, the current degradation rate is obtained by using the Theil-Sen robust slope method to fit the slope of the operating state of the fire protection facilities, obtaining the state change slope at different sampling locations, and taking the median of the state change slope as the current degradation rate.

[0008] As a preferred embodiment of the cloud platform-based preventive maintenance task generation method for fire protection facilities described in this invention, the remaining maintenance time for shortening the preset maintenance period is obtained by acquiring the original remaining maintenance time, and proportionally converting the original remaining maintenance time based on the excess of the current degradation rate relative to the historical stable degradation rate, to obtain the shortened remaining maintenance time.

[0009] As a preferred embodiment of the cloud platform-based preventive maintenance task generation method for fire protection facilities described in this invention, the specific steps for setting each fire protection facility to be maintained as a maintenance-off state are as follows: Based on the maintenance tasks to be performed, fire protection facilities and fire protection areas are used as nodes. The nodes are established according to the spatial ownership relationship between fire protection facilities and fire protection areas to obtain the fire protection relationship diagram. In the fire protection relationship diagram, select the maintenance tasks to be performed one by one and set them to the maintenance exit state. Check whether each fire protection zone node is still connected to the fire protection facility nodes that are not in the maintenance exit state. Then, gather the space areas that have lost fire protection to obtain the fire protection missing areas before installation and the fire protection missing areas after installation. By comparing the spatial extent of the areas lacking fire protection before and after the installation of fire protection, the spatial areas that exist only in the areas lacking fire protection after the installation are identified as newly added areas lacking fire protection.

[0010] As a preferred embodiment of the cloud-based preventive maintenance task generation method for fire protection facilities described in this invention, the spatial affiliation relationship is the coverage relationship between fire protection facilities, fire protection areas and their respective fire compartments.

[0011] As a preferred embodiment of the cloud-based preventive maintenance task generation method for fire protection facilities described in this invention, the step of treating pending maintenance tasks for areas with newly added fire protection deficiencies as postponed maintenance tasks includes the following steps: The area lacking fire protection is divided into missing sub-areas, and the fire protection area nodes of each missing sub-area are retained; Tracing the fire protection facilities that are out of maintenance along the nodes of each fire protection zone, and merging the missing sub-areas of the same fire protection facility into the fire protection missing range; In the pending maintenance tasks, locate the fire protection facilities that have a spatial relationship with the newly added fire protection missing area, and record the pending maintenance tasks of the fire protection facilities as postponed maintenance tasks.

[0012] As a preferred embodiment of the cloud-based method for generating preventive maintenance tasks for fire protection facilities according to the present invention, the specific steps for calculating the interval between the time of forming the postponed maintenance task and the deadline for preventive maintenance are as follows: Using the unified timing benchmark of the cloud platform, clock offset corrections are performed on the formation time of the postponed maintenance task and the deadline of the preventive maintenance, respectively, to obtain the correction formation time and correction deadline. The time segments are divided according to the time sequence from the time of correction formation to the time of correction cutoff. The duration between the start time and the correction deadline in each time segment of industrial cloud computing is used as the interval duration.

[0013] As a preferred embodiment of the cloud-based preventive maintenance task generation method for fire protection facilities according to the present invention, the specific steps for obtaining the conflict recovery task are as follows: Obtain the time required to restore the maintenance task from the historical maintenance records of fire protection facilities; Check the interval duration against the time required to restore the maintenance task one by one, and determine the time segment in which the duration is first shorter than the time required to restore the maintenance task as the critical recovery segment; The maintenance tasks that temporarily suspend the process to form a critical recovery zone are identified as recovery conflict tasks.

[0014] As a preferred embodiment of the cloud platform-based method for generating preventive maintenance tasks for fire protection facilities according to the present invention, the specific steps for obtaining the preventive maintenance task are as follows: The maintenance and repair of each fire protection facility node will be restored to the operational status of the fire protection facility before the maintenance and repair was set, and newly added areas lacking fire protection will be re-identified. When a newly added area lacking fire protection does not exist in actual space, the conflict task will be restored and reassigned to the pending maintenance task. The execution location will be re-determined using the deadline for preventive maintenance, thus obtaining the preventive maintenance task.

[0015] Secondly, this invention provides a cloud-based preventive maintenance task generation system for fire protection facilities, including: The deadline determination module is used to compare the degradation status of fire protection facilities, obtain the current degradation rate, calculate the excess of the current degradation rate relative to the historical stable degradation rate, shorten the remaining maintenance time of the preset maintenance period, select the remaining maintenance time with the shortest duration, and extend the selected remaining maintenance time. The end time of the extension is determined as the deadline for preventive maintenance. The postponement determination module is used to arrange the pending maintenance tasks of each fire protection facility according to the deadline of preventive maintenance, set the fire protection facilities of each pending maintenance task to the maintenance exit state, compare the fire protection missing areas before and after the maintenance exit state, and set the pending maintenance tasks with newly added fire protection missing areas as postponed maintenance tasks. The conflict determination module is used to calculate the interval between the formation time of the postponed maintenance task and the deadline of the preventive maintenance, and compare it with the obtained time required to restore the maintenance task to obtain the conflict task to be restored. The task generation module is used to complete the verification of the maintenance tasks to be performed, restore each fire protection facility to its operating state before the maintenance was cancelled, and write the restoration conflict results into the maintenance tasks to be performed to obtain preventive maintenance tasks.

[0016] The beneficial effects of this invention are as follows: By using industrial cloud computing to postpone the available time for maintenance tasks and the time required for the restoration of fire protection facilities, the time matching between maintenance tasks and the restoration of fire protection facilities is improved. This allows maintenance items with conflicting restoration times to be identified and handled during the task generation stage, avoiding the neglect of fire protection gaps after the removal of fire protection facilities due to time sequence alone in maintenance arrangements. This reduces the possibility of persistent inadequacy of local fire protection capabilities during maintenance. At the same time, it coordinates maintenance deadline requirements, fire protection integrity, and actual restoration capabilities, reducing manual adjustments and repetitive scheduling during the execution phase of maintenance tasks, and improving the feasibility, timing stability, and scheduling rationality of preventive maintenance tasks. 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 a method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform.

[0019] Figure 2 This is a schematic diagram of a cloud-based system for generating preventive maintenance tasks for fire protection facilities.

[0020] Figure 3 A flowchart for obtaining the shortened remaining maintenance time.

[0021] Figure 4 A flowchart for obtaining the conflict recovery task. Detailed Implementation

[0022] 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.

[0023] 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.

[0024] 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.

[0025] Reference Figures 1-4 As one embodiment of the present invention, this embodiment provides a method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform, including the following steps: S1. Compare the degradation status of the fire protection facilities to obtain the current degradation rate, calculate the excess of the current degradation rate relative to the historical stable degradation rate, shorten the remaining maintenance time of the preset maintenance period, select the remaining maintenance time with the shortest duration, and extend the selected remaining maintenance time. The end time of the extension is determined as the deadline for preventive maintenance.

[0026] S1.1. The Theil-Sen robust slope method is used to fit the slope of the fire protection facility's operating state, obtaining the state change slope at different sampling locations. The median of the state change slope is then used as the current degradation rate. Specifically, The fire protection facility operation status data used for degradation comparison shall exclude the operation data generated by the fire controller and on-site data acquisition terminal during the normal operation of the fire protection facility, including the acquisition time. Each operation data shall retain at least the unique number of the fire protection facility, the type of fire protection facility operation status data, the acquisition time, and the fire protection facility operation status value. The fire protection facility operation status values ​​generated during fire testing, maintenance, and communication interruption shall not be included in the degradation comparison.

[0027] The operating status quantities of fire protection facilities used in the Theil-Sen robust slope method are those that can form a continuous numerical sequence according to the acquisition time.

[0028] The operational status variables of fire protection facilities used in the Theil-Sen robust slope method are those that can form a continuous numerical sequence according to the time of acquisition. For the same fire protection facility, which includes multiple operational status variables such as pressure, current, response time, and battery power, the cloud platform collects the operational status values ​​of the fire protection facilities according to the type of operational status variable, so that each type of operational status variable forms a separate operational status value sequence. The Theil-Sen robust slope method is then used to process each operational status value sequence of the fire protection facilities to obtain the current degradation rate of each operational status variable.

[0029] Because the operational status parameters of various fire protection facilities have different dimensions and numerical ranges, the cloud platform does not directly merge the current degradation rates, nor does it calculate the average value using the current degradation rates of different fire protection facility operational status parameters. Instead, the cloud platform compares the current degradation rate of each type of fire protection facility operational status parameter with the historical stable degradation rate of the same type of fire protection facility operational status parameter, obtaining the excess amount for each fire protection facility operational status parameter. Then, it uses each excess amount to calculate the original remaining maintenance time for the same fire protection facility, resulting in a shortened remaining maintenance time for each type of fire protection facility operational status.

[0030] The cloud platform converts all shortened remaining maintenance times for the same fire protection facility into the same time unit, and arranges them in ascending order of duration. The shortened remaining maintenance time at the top of the list is selected as the target remaining maintenance time. The cloud platform uses the current moment, after completing the comparison of all shortened remaining maintenance times, as the starting moment for extension, and extends the target remaining maintenance time along the unified timing benchmark. The end moment of the extension is determined as the unique preventive maintenance deadline for the same fire protection facility.

[0031] If only one type of fire protection facility operation state results in an effective shortened remaining maintenance time, the cloud platform directly determines this unique shortened remaining maintenance time as the target remaining maintenance time. If two or more fire protection facility operation states result in shortened remaining maintenance times with the same shortest duration, the cloud platform selects any shortest duration as the target remaining maintenance time. Since each shortest duration starts from the same current moment and extends sequentially, each shortest duration forms the same preventive maintenance deadline.

[0032] If some fire protection facilities within the same fire protection system have not yet established a historical stable degradation rate, the cloud platform will not use the operational status data of those facilities to calculate the original remaining maintenance time. Instead, it will use the operational status data of those facilities that have already established a historical stable degradation rate to calculate the shortened remaining maintenance time. If none of the operational status data of all fire protection facilities within the same fire protection system have established a historical stable degradation rate, the cloud platform will not shorten the original remaining maintenance time and will set the original remaining maintenance time as the target remaining maintenance time.

[0033] If the historical stable degradation rate of any fire protection facility's operational status quantity is zero and the current degradation rate is greater than zero, the cloud platform will record the shortened remaining maintenance time of the fire protection facility's operational status quantity as zero; after the shortened remaining maintenance time is zero, the target remaining maintenance time is zero, and the cloud platform will determine the current moment as the deadline for preventive maintenance.

[0034] Arrange the operational status values ​​of the same fire protection facility used for degradation comparison according to the collection time sequence. Form a sampling location pair by combining the operational status values ​​of any two sampling locations. Take the difference between the operational status values ​​of the fire protection facility at the subsequent sampling location and the preceding sampling location as the status change. Calculate the state change slope using the collection time difference between the two sampling locations as the time interval. The formula is: ; In the formula, The slope of the state change. For state changes, It is a time interval and is greater than zero.

[0035] Traverse all sampling locations to form state change slopes, and arrange all state change slopes in ascending order of value. When the number of state change slopes is odd, take the state change slope in the middle of the arrangement. When the number of state change slopes is even, take the average of the two state change slopes in the middle of the arrangement. Take the median of the obtained state change slopes as the current degradation rate.

[0036] When the median of the slope of state change is less than zero, the current degradation rate is recorded as zero; when the median of the slope of state change is not less than zero, the median of the slope of state change is used as the current degradation rate.

[0037] It should be noted that the operating status values ​​of fire protection facilities are unified according to the degradation direction of the same fire protection facility operating status quantity. For fire protection facility operating status quantities whose values ​​increase and whose degradation degree increases, the original value direction is maintained. For fire protection facility operating status quantities whose values ​​decrease and whose degradation degree increases, the value change direction is reversed, so that the operating status values ​​of fire protection facilities participating in the degradation comparison all increase in the direction of increasing degradation degree.

[0038] S1.2 Calculate the excess of the current degradation rate relative to the historical stable degradation rate, specifically, The current degradation rate is compared with the historical stable degradation rate of the same fire protection facility and the same type of fire protection facility operating status. The historical stable degradation rate is the operating status of the fire protection facility during the continuous normal operation period formed after the most recent maintenance, and is obtained using the same degradation direction processing method and Theil-Sen robust slope method as S1.1.

[0039] The cloud platform defines the historical operation record retrieval range from the moment the most recent maintenance was completed and the fire protection facilities were confirmed to be back to normal operation to the present moment. It then reads the operational status data of the same fire protection facility and the same type of fire protection facility according to the order of data collection. The cloud platform simultaneously reads fire protection test records, repeat maintenance records, abnormal shutdown records, fault alarm records, communication interruption records, and missing sampling records from the historical operation records, and uses the start and end times of each record to segment the historical operation record retrieval range.

[0040] Each segmented time interval begins at the moment when the fire protection facilities resume normal operation and ends at the start of any of the following scenarios: fire testing, re-maintenance, abnormal shutdown, fault alarm, communication interruption, or missing sampling. After any scenario ends and the fire protection facilities resume normal operation, the cloud platform forms the next time interval starting from the moment the fire protection facilities resume normal operation. The cloud platform only retains the time intervals that do not include fire testing, re-maintenance, abnormal shutdown, fault alarm, communication interruption, and missing sampling, and defines the retained time intervals as continuous normal operation intervals.

[0041] The cloud platform arranges the continuous normal operation intervals from earliest to latest according to the start time of each interval, and prioritizes the continuous normal operation interval formed first after the most recent maintenance. The cloud platform checks the collection time within the continuous normal operation interval according to the preset sampling period of the same fire protection facility operation status quantity, and deletes sampling positions with duplicate collection times, collection time intervals that do not conform to the preset sampling period, and missing fire protection facility operation status values, and determines the remaining sampling positions as valid sampling positions.

[0042] The continuous normal operation interval used to obtain the historical stable degradation rate includes at least three valid sampling locations that are different at different acquisition times, and the duration of the continuous normal operation interval is not less than the preset stable observation time.

[0043] The preset stable observation duration is determined based on the preset sampling cycle of the same type of fire protection facility operation status quantity, so that no less than three effective sampling locations can be formed within the preset stable observation duration; the preset stable observation duration is pre-registered in the cloud platform according to the type of fire protection facility and the type of fire protection facility operation status quantity.

[0044] If the first continuous normal operation interval formed after the most recent maintenance includes no less than three valid sampling positions, and the duration of the continuous normal operation interval is not less than the preset stable observation period, then the cloud platform will start from the beginning of the continuous normal operation interval to extract the valid sampling positions within the preset stable observation period, and determine the extraction result as the continuous normal operation period.

[0045] If the first continuous normal operation interval formed after the most recent maintenance includes no less than three valid sampling locations, but the duration of the continuous normal operation interval is longer than the preset stable observation time, then the cloud platform will only use the valid sampling locations in the beginning part of the continuous normal operation interval that are within the preset stable observation time, so as to avoid the subsequent degradation changes caused by the long-term operation of fire protection facilities from entering the historical stable degradation rate.

[0046] If the number of valid sampling locations in the first continuous normal operation interval formed after the most recent maintenance is less than three, or the duration of the continuous normal operation interval is shorter than the preset stable observation time, the cloud platform will not use the first continuous normal operation interval to obtain the historical stable degradation rate, and will continue to check the subsequent continuous normal operation intervals from the beginning to the end according to the start time of the continuous normal operation interval, until a continuous normal operation interval that simultaneously meets the requirements of the number of valid sampling locations and the preset stable observation time is obtained.

[0047] If the number of valid sampling locations and the preset stable observation duration are not met in all continuous normal operation intervals between the most recent maintenance completion time and the current time, the cloud platform will not generate a historical stable degradation rate for the same type of fire protection facility operation status quantity, and will record the same type of fire protection facility operation status quantity as insufficient historical stable degradation rate data.

[0048] Fire protection facility operation status data that is insufficient in the historical stable degradation rate are not included in the comparison between the current degradation rate and the historical stable degradation rate, nor are they used to generate excess data.

[0049] After the cloud platform obtains the continuous normal operation period, the operating status values ​​of the fire protection facilities during the continuous normal operation period are processed in the same way as S1.1 in terms of degradation direction. Then, any two valid sampling locations are combined into a sampling location pair to form the state change slope respectively. The median of all state change slopes is determined as the historical stable degradation rate.

[0050] When the current degradation rate exceeds the historical stable degradation rate, the excess is obtained by subtracting the historical stable degradation rate from the current degradation rate, as shown in the formula: ; In the formula, For exceeding the limit, Given the current degradation rate, This represents the historically stable degradation rate.

[0051] When the current degradation rate is not greater than the historical stable degradation rate, the excess is recorded as zero, so that the excess only reflects the part of the current degradation rate that exceeds the historical stable degradation rate.

[0052] S1.3. Obtain the original remaining maintenance time. The original remaining maintenance time is proportionally reduced based on the amount by which the current degradation rate exceeds the historical stable degradation rate, resulting in the shortened remaining maintenance time. Specifically, The original remaining maintenance duration is the duration from the current time to the end of the preset maintenance period.

[0053] When the excess is greater than zero, the historical stable degradation rate is added to the excess to form the total degradation rate corresponding to the current degradation rate. Then, the original remaining maintenance time is calculated based on the proportion of the historical stable degradation rate to the total degradation rate, using the following formula: ; In the formula, The remaining maintenance time is the original amount. To shorten the remaining maintenance time, For the historical stable degradation rate, This is an excessive amount.

[0054] Among them, the historical stable degradation rate and the excess amount have the same dimension. The ratio of the historical stable degradation rate to the total degradation rate is a dimensionless ratio. As the excess increases, the conversion ratio decreases accordingly. When the excess is zero, the original remaining maintenance time remains unchanged, thus obtaining the shortened remaining maintenance time.

[0055] When the historical stable degradation rate is greater than zero, the original remaining maintenance time is calculated according to the proportion of the historical stable degradation rate to the total degradation rate; when the historical stable degradation rate is equal to zero and the current degradation rate is equal to zero, the original remaining maintenance time remains unchanged; when the historical stable degradation rate is equal to zero and the current degradation rate is greater than zero, the preventive maintenance deadline is set to the current moment.

[0056] Under the unified timing benchmark of the cloud platform, the current moment when the shortened remaining maintenance time is formed is taken as the starting moment, and the shortened remaining maintenance time is extended sequentially along the time line. The moment corresponding to the end position of the extension is recorded as the deadline for preventive maintenance.

[0057] When the shortened remaining maintenance time changes, the deadline for preventive maintenance will be moved forward accordingly.

[0058] It should be noted that the preset maintenance period is determined based on the maintenance cycle that has been registered for the corresponding fire protection facility in the cloud platform. The start time of the most recent maintenance completion is taken as the start time of the maintenance cycle, and the end time of the preset maintenance period is taken as the time after the most recent maintenance completion time is extended by the corresponding maintenance cycle. If there is no historical maintenance completion record for the fire protection facility, the start time of the maintenance cycle is taken as the time when the fire protection facility is put into operation.

[0059] S2. Arrange the pending maintenance tasks of each fire protection facility according to the deadline of preventive maintenance, and set the fire protection facilities of each pending maintenance task to the maintenance exit state. Compare the fire protection missing areas before and after the maintenance exit state, and set the pending maintenance tasks with newly added fire protection missing areas as postponed maintenance tasks.

[0060] S2.1 Arrange the pending maintenance tasks for each fire protection facility according to the preventive maintenance deadline, specifically as follows: Each fire protection facility is arranged in the order of its preventive maintenance deadline. The fire protection facilities with the earlier preventive maintenance deadline are placed in the first-order execution position, and the fire protection facilities with the later preventive maintenance deadline are placed in the second-order execution position. Fire protection facilities with the same preventive maintenance deadline are kept at the same execution order level, and their order within the same execution order level is determined according to the existing numbering of the fire protection facilities.

[0061] The maintenance tasks are formed sequentially according to the location of each fire protection facility after arrangement, and the correspondence between the fire protection facilities and the deadline for preventive maintenance is maintained, thus forming a sequence of maintenance tasks to be performed.

[0062] For example, if the deadlines for preventive maintenance of the first, second, and third fire protection facilities are August 10, August 6, and August 15, respectively, then the maintenance task corresponding to the second fire protection facility is in the first execution position, the maintenance task corresponding to the first fire protection facility is in the second execution position, and the maintenance task corresponding to the third fire protection facility is in the third execution position, forming a sequence of maintenance tasks to be executed from front to back.

[0063] S2.2 Set all fire protection facilities awaiting maintenance to the maintenance off status, specifically as follows: S2.2.1. Based on the maintenance tasks to be performed, using fire protection facilities and fire protection zones as nodes, establish the node edges according to the spatial affiliation between fire protection facilities and fire protection zones to obtain the fire protection relationship diagram, specifically, Before the maintenance and withdrawal of each fire protection facility in the same fire compartment, the boundaries of the fire protection areas are placed under the same spatial coordinate reference. All fire protection area boundaries are superimposed on each other, and the intersection and boundary lines of the fire protection area boundaries are used as the dividing points. The same fire compartment is divided into non-overlapping minimum spatial areas, and each minimum spatial area is set as a fire protection area node.

[0064] Verify the fire protection zone during normal operation of the fire protection facilities and the minimum space area represented by each fire protection zone node. When the fire protection zone during normal operation of the fire protection facilities includes the corresponding minimum space area, write the node-to-node graph edge between the fire protection facility node and the fire protection zone node.

[0065] The boundaries of fire protection zones are taken from the boundary coordinates registered in the spatial layout data of fire protection facilities stored in the cloud platform, and the boundaries of each fire protection zone uniformly adopt the same spatial coordinate reference.

[0066] Spatial Boolean processing uses the minimum coordinate resolution that the fire protection zone boundary data can distinguish as the geometric processing accuracy. Coordinate differences smaller than this minimum coordinate resolution are treated as the same boundary position.

[0067] The specific steps to obtain the minimum distinguishable coordinate resolution are as follows: Read the coordinate fields and planar positioning error of each fire protection zone boundary. Determine the minimum coordinate increment based on the number of coordinate fields retained, and determine the larger value between the minimum coordinate increment and the planar positioning error as the geometric processing accuracy. Check the planar distance between fire protection zone boundary points and the shortest distance from the fire protection zone boundary point to the adjacent fire protection zone boundary line according to the geometric processing accuracy. Unify the fire protection zone boundaries that are not greater than the geometric processing accuracy to the same boundary position, and retain the fire protection zone boundaries that are greater than the geometric processing accuracy in their original boundary positions. Superimpose the fire protection zone boundaries that have completed the boundary position correction, and divide the same fire compartment by the intersection of the fire protection zone boundaries and the boundary line to obtain the minimum non-overlapping spatial area.

[0068] When one fire protection facility corresponds to multiple fire protection zones, the nodes are written with graph edges between the fire protection facility node and the multiple fire protection zone nodes respectively. When multiple fire protection facilities jointly provide fire protection for the same fire protection zone, the nodes are retained with graph edges between the multiple fire protection facility nodes and the same fire protection zone node. The resulting fire protection facility nodes, fire protection zone nodes and graph edges are then combined into a fire protection relationship diagram.

[0069] S2.2.2 In the fire protection relationship diagram, select each maintenance task to be performed and set it to maintenance exit status. Check whether each fire protection zone node is still connected to the fire protection facility nodes that are not in maintenance exit status, and aggregate the spatial areas that have lost fire protection to obtain the fire protection missing areas before installation and the fire protection missing areas after installation. Specifically, The steps to select each maintenance task to be performed and set it to maintenance exit status are as follows: The cloud platform arranges the maintenance tasks to be executed in the order of their deadlines for preventive maintenance, and selects the maintenance tasks to be executed one by one from the front to the back of the list. Each time, the maintenance task to be executed at a certain position in the list is determined as the current maintenance task to be executed.

[0070] The maintenance tasks that are arranged before the current maintenance task are designated as the preceding maintenance tasks, and the fire protection facility nodes involved in the preceding maintenance tasks remain in the maintenance off state; the maintenance tasks that are arranged after the current maintenance task are designated as the subsequent maintenance tasks, and the fire protection facility nodes involved in the subsequent maintenance tasks remain in the operating state of the fire protection facilities before the maintenance off state was set.

[0071] Before the verification of the fire protection missing areas before the current maintenance task is completed, the fire protection facility nodes involved in the current maintenance task are kept in the maintenance exit state and the fire protection facility operation status before the maintenance exit state is maintained. By keeping the fire protection facility nodes involved in the previous maintenance task in the maintenance exit state, the fire protection missing areas before the current maintenance task begins to record the fire protection missing areas that have been formed before the current maintenance task begins to be verified.

[0072] If the current maintenance task involves only one fire protection facility, the cloud platform will use one fire protection facility node as the current setting object; if the current maintenance task involves multiple fire protection facilities that need to be simultaneously deactivated for fire protection capability verification, the cloud platform will use multiple fire protection facility nodes as the same group of current setting objects, and determine the fire protection missing area before setting if none of the multiple fire protection facility nodes are set to maintenance deactivation status.

[0073] Before the fire protection facility nodes involved in the current maintenance task are set to the maintenance exit state, the cloud platform traverses all fire protection area nodes in the fire protection relationship graph and reads all fire protection facility nodes connected by the graph edges between each fire protection area node.

[0074] The cloud platform verifies whether the fire protection facility nodes connected to each fire protection zone node are in a maintenance-out state. If a fire protection zone node is still connected to at least one fire protection facility node that is not in a maintenance-out state, the fire protection facility node that is not in a maintenance-out state can still participate in the fire protection capability verification through the graph edges between nodes, and the cloud platform will determine the fire protection zone node as a fire protection zone node that maintains fire protection.

[0075] If all fire protection facility nodes connected to a fire protection zone node are in a maintenance-out state, then the fire protection zone node is not connected to any fire protection facility nodes that can participate in the fire protection capability verification. The cloud platform will identify the fire protection zone node as a fire protection zone node that lost fire protection before its setup.

[0076] The cloud platform reads the spatial boundaries saved by each fire protection zone node that lost fire protection before the setup, and obtains the spatial area occupied by each fire protection zone node that lost fire protection before the setup according to the spatial boundaries. The fire protection zone nodes are non-overlapping spatial areas formed by superimposing the fire protection zone boundaries. Therefore, each fire protection zone node has a unique spatial boundary and spatial range.

[0077] The cloud platform aggregates the spatial areas occupied by all fire protection zone nodes that were previously without fire protection. It merges spatial areas with common boundaries along the common boundary and retains the original spatial boundaries of separate spatial areas, thus obtaining the areas lacking fire protection before installation.

[0078] If there are no fire protection area nodes that lost fire protection before the setup in the fire protection relationship diagram, the cloud platform will record the fire protection missing area before the setup as an empty area. The fire protection missing area before the setup is used to record the fire protection missing that already existed after the fire protection facility nodes involved in the previous maintenance task were kept in the maintenance exit state.

[0079] After determining the missing fire protection areas before setting up, the cloud platform reads the unique number of the fire protection facility saved in the current maintenance task to be performed, and locates the fire protection facility node with the same unique number in the fire protection relationship diagram.

[0080] The cloud platform records the operating status of the fire protection facilities nodes involved in the current maintenance task before the maintenance exit status is set. Then, the fire protection facilities nodes are set to the maintenance exit status. After the fire protection facilities nodes enter the maintenance exit status, the fire protection facilities nodes will no longer provide fire protection to the fire protection area nodes through the node-to-node graph edges during the current fire protection capability verification period.

[0081] The maintenance exit status is the verification status written to the fire protection facility node during the maintenance task verification period. The maintenance exit status only changes the status of the fire protection facility node in the fire protection capability verification, does not change the actual operating status of the on-site fire protection facilities, does not send start / stop commands to the on-site fire protection facilities, and does not delete the nodes already established in the fire protection relationship diagram.

[0082] If the current maintenance task involves multiple fire protection facilities, the cloud platform records the operating status of multiple fire protection facility nodes before the maintenance exit status is set, and sets multiple fire protection facility nodes to the maintenance exit status at the same time; after all multiple fire protection facility nodes have completed the maintenance exit status setting, the missing fire protection area after the setting is determined.

[0083] After the maintenance exit status of the fire protection facility nodes involved in the current maintenance task is completed, the cloud platform re-traverses all fire protection area nodes in the fire protection relationship graph and reads all fire protection facility nodes connected by the graph edges between each fire protection area node.

[0084] If a fire protection zone node is still connected to at least one fire protection facility node that is not in a maintenance withdrawal state, the fire protection facility node that is not in a maintenance withdrawal state will still participate in the fire protection capability verification, and the cloud platform will identify the fire protection zone node as a fire protection zone node that maintains fire protection.

[0085] If all fire protection facility nodes connected to a fire protection zone node are in a maintenance-out state, then the fire protection zone node has lost the fire protection facility nodes that can participate in the fire protection capability verification. The cloud platform will identify the fire protection zone node as a fire protection zone node that has lost fire protection after being set up.

[0086] The cloud platform reads the spatial boundaries saved by the fire protection zone nodes that have lost fire protection after being set, and obtains the spatial area occupied by the fire protection zone nodes that have lost fire protection after being set.

[0087] The cloud platform merges spatial areas with common boundaries along the common boundary, and retains the original spatial boundaries of the separate spatial areas, thus obtaining the areas lacking fire protection after the installation.

[0088] If there is no fire protection zone node in the fire protection relationship diagram that loses fire protection after being set, the cloud platform will record the area with missing fire protection after being set as an empty area.

[0089] The set fire protection missing area is used to record the fire protection missing that occurs after the fire protection facility nodes involved in the previous maintenance task and the fire protection facility nodes involved in the current maintenance task are in the maintenance exit state.

[0090] S2.2.3. Compare the spatial extent of the fire protection deficiency areas before and after installation, and determine the spatial areas that exist only in the fire protection deficiency areas after installation as the newly added fire protection deficiency areas. Specifically, Before comparing the areas lacking fire protection before and after the installation, the cloud platform verifies the spatial coordinate reference and geometric processing accuracy used for the two areas lacking fire protection.

[0091] If two areas lacking fire protection use the same spatial coordinate reference and the same geometric processing precision, the cloud platform will directly perform a spatial range comparison.

[0092] If two areas lacking fire protection use different spatial coordinate references, the cloud platform will convert the two areas lacking fire protection to the same spatial coordinate reference according to the coordinate transformation parameters recorded in the fire protection facility spatial layout data.

[0093] If two areas lacking fire protection use different geometric processing precisions, the cloud platform will use the geometric processing precision with the larger value to uniformly correct the boundary positions of the two areas lacking fire protection.

[0094] The cloud platform verifies the boundary points and boundary lines of the two fire protection missing areas according to the geometric processing accuracy. If the distance between different boundary points is not greater than the geometric processing accuracy, the cloud platform unifies the different boundary points to the same boundary position. If the shortest distance from the boundary point to the adjacent boundary line is not greater than the geometric processing accuracy, the cloud platform adjusts the boundary point to the adjacent boundary line. After the boundary position correction is completed, the fire protection missing areas before and after the fire protection missing areas have the same spatial comparison benchmark.

[0095] The cloud platform overlays the spatial boundaries of the fire protection-deficient area before and after the fire protection-deficient area is set, and uses the intersection and boundary lines of the two fire protection-deficient areas to divide the space covered by the two fire protection-deficient areas into non-overlapping comparison sub-areas.

[0096] The cloud platform verifies each comparison sub-region one by one whether it is located in the fire protection deficiency area before the setting and whether it is located in the fire protection deficiency area after the setting. If a comparison sub-region is located in both the fire protection deficiency area before the setting and the fire protection deficiency area after the setting, the comparison sub-region belongs to the fire protection deficiency that existed before the current maintenance task was set to the maintenance exit state. The cloud platform will not include the comparison sub-region in the newly added fire protection deficiency area.

[0097] If a comparison sub-region is located only within the fire protection missing area after the setting, and not within the fire protection missing area before the setting, then the comparison sub-region is a newly emerging fire protection missing area after the fire protection facility node involved in the current maintenance task is set to maintenance exit state. The cloud platform will retain the comparison sub-region as the newly added fire protection missing sub-region.

[0098] If a comparison sub-region is located only within the pre-installation fire protection missing area and not within the post-installation fire protection missing area, the cloud platform records an abnormal change in spatial range between the two fire protection missing areas and re-verifies the maintenance exit status and spatial boundaries of the fire protection area nodes.

[0099] If the preceding fire protection facility node remains in the maintenance and out-of-service state and the current fire protection facility node is newly added to the maintenance and out-of-service state, the area of ​​missing fire protection after installation should not be smaller than the area of ​​missing fire protection before installation.

[0100] The cloud platform gathers all newly added fire protection missing sub-areas, merges newly added fire protection missing sub-areas with common boundaries along the common boundary, and retains the original spatial boundaries of newly added fire protection missing sub-areas that are separate from each other, thus obtaining the newly added fire protection missing areas.

[0101] It should be noted that if the fire protection missing area is an empty area before setting, and the fire protection missing area after setting includes an actual space area, then all the space areas in the fire protection missing area after setting are the newly added fire protection missing areas after the current maintenance task is set to the maintenance exit state. The cloud platform will identify the fire protection missing area after setting as the newly added fire protection missing area.

[0102] If the fire protection missing area before and after setting has the same spatial boundary and the same spatial range, and no fire protection missing area is added after the fire protection facility node involved in the current maintenance task is set to maintenance exit status, the cloud platform will record the newly added fire protection missing area as an empty area.

[0103] If the fire protection missing area is set to an empty area after the setting, then the fire protection facility node involved in the current maintenance task will not form a fire protection missing area after the maintenance exit status is set, and the cloud platform will add a fire protection missing area and record it as an empty area.

[0104] If the spatial range comparison results only form boundary points and boundary lines that do not constitute a closed area, the cloud platform will not determine the boundary points and boundary lines as the actual spatial area, and will record the newly added fire protection missing area as an empty area.

[0105] Among them, spatial ownership relationship refers to the coverage relationship between fire protection facilities, fire protection areas and their respective fire compartments.

[0106] S2.3 Maintenance tasks awaiting execution in areas with newly added missing fire protection systems will be temporarily suspended. Specifically, S2.3.1. The smallest space occupied by each fire protection zone node in the newly added fire protection missing area shall be taken as the missing sub-area, and the fire protection zone node to which each missing sub-area belongs shall be retained, so that the missing sub-area only includes the fire protection missing newly formed after the fire protection facility node involved in the current maintenance task is set to the maintenance exit state, and does not include the fire protection missing formed by the previous maintenance task.

[0107] S2.3.2. Tracing back the fire protection facilities in the maintenance withdrawal state along the inter-node map edges of each fire protection zone node, and merging the missing sub-zones of the same fire protection facility into a fire protection gap range, specifically, Starting from the fire protection zone nodes retained in each missing sub-region, proceed in reverse along the graph edges between nodes in the fire protection relationship diagram to reach the fire protection facility nodes, and read the operating status of the fire protection facilities corresponding to each fire protection facility node one by one.

[0108] When the operating status of a fire protection facility is "maintenance out of service", an attribution relationship is established between the fire protection facility corresponding to the fire protection facility node and the missing sub-region where the fire protection area node at the starting end of the graph edge between the nodes is located. If the operating status of a fire protection facility is not "maintenance out of service", the corresponding fire protection facility will not be included in the missing sub-region attribution.

[0109] When a missing sub-area is traced back to multiple fire protection facilities that are out of maintenance, the attribution relationship between the missing sub-area and the multiple fire protection facilities is retained respectively; missing sub-areas with the same attribution relationship are gathered according to the fire protection facilities; overlapping missing sub-areas are merged after removing duplicate parts; and spatially separated missing sub-areas retain their original spatial boundaries. All missing sub-areas corresponding to the same fire protection facility are combined into a fire protection missing range.

[0110] S2.3.3. In the pending maintenance tasks, locate the fire protection facilities that have a spatial relationship with the newly added fire protection missing area, and record the pending maintenance tasks of the fire protection facilities as postponed maintenance tasks. Specifically, According to the fire protection facilities corresponding to the fire protection gap, each fire protection facility corresponding to the maintenance task to be performed is checked in the sequence of maintenance tasks to be performed. When the fire protection facilities corresponding to the maintenance task to be performed are consistent with the fire protection facilities corresponding to the fire protection gap, the current execution position of the maintenance task to be performed in the sequence of maintenance tasks to be performed is cancelled. The original preventive maintenance deadline and the corresponding relationship of fire protection facilities of the maintenance task to be performed are retained. The maintenance task to be performed that is removed from the current execution position is recorded as a postponed maintenance task. At the same time, the time when the maintenance task to be performed is recorded as a postponed maintenance task is recorded according to the unified timing benchmark of the cloud platform, and the recorded time is used as the time when the postponed maintenance task is formed.

[0111] When the fire protection facilities corresponding to the maintenance task to be performed are inconsistent with the fire protection facilities corresponding to the area where fire protection is missing, the current execution position of the maintenance task to be performed in the sequence of maintenance tasks to be performed remains unchanged.

[0112] S3. Calculate the interval between the time when the deferred maintenance task is formed and the deadline of the preventive maintenance, and compare it with the time required to restore the obtained maintenance task to obtain the task to be restored.

[0113] S3.1 Calculate the interval between the time when the deferred maintenance task is formed and the time when the preventive maintenance is due, specifically, S3.1.1. Using the unified timing benchmark of the cloud platform, clock offset corrections are performed on the formation time of the deferred maintenance task and the deadline of the preventive maintenance, respectively, to obtain the correction formation time and correction deadline. Specifically, The cloud platform maintains a unified timing benchmark using the same NTP time source. When synchronizing the local clock time used to record the formation time of the deferred maintenance task and the deadline time of the preventive maintenance, it simultaneously saves the unified timing benchmark time and the local clock time.

[0114] The difference between the unified timing reference time and the local clock time at the same synchronization moment is the clock offset. A positive clock offset indicates that the local clock lags behind the unified timing reference, while a negative clock offset indicates that the local clock leads the unified timing reference.

[0115] Select the clock offset from the most recent time synchronization before the time the deferred maintenance task was created and the time the preventive maintenance deadline was set, respectively. Add the corresponding clock offset to the time the deferred maintenance task was created and the time the preventive maintenance deadline was set, using the following formula: in, The time to be corrected. To record the clock offset of the local clock relative to a unified timing reference used at the time to be calibrated. This is the corrected time.

[0116] The time after which the maintenance task is postponed is converted is recorded as the correction formation time, and the time after which the preventive maintenance deadline is converted is recorded as the correction deadline time. When the clock offset is zero, the original time remains unchanged, and the correction formation time and the correction deadline time are expressed in the same time unit and the same time zone.

[0117] S3.1.2. Divide the time segment according to the time sequence from the time of correction formation to the time of correction cutoff, specifically as follows: Using the time of correction formation as the starting time of the first time segment, the format of the time field used to record the formation time of the deferred maintenance task and the deadline of the preventive maintenance is read. Based on the smallest time unit that the time field can record, the minimum recordable time increment of the formation time of the deferred maintenance task and the minimum recordable time increment of the deadline of the preventive maintenance are obtained respectively.

[0118] When the time of formation of the deferred maintenance task and the time of expiration of the preventive maintenance task use the same minimum recordable time increment, the same minimum recordable time increment is determined as the minimum time interval; when the time of formation of the deferred maintenance task and the time of expiration of the preventive maintenance task use different minimum recordable time increments, the minimum recordable time increment with a longer duration is determined as the minimum time interval, so that the time of formation of correction, the time of expiration of correction and each time segment adopt a uniform time division accuracy.

[0119] For example, when both the time of the postponed maintenance task and the deadline for preventive maintenance are recorded to the second, the minimum time interval is one second; when one time is recorded to the second and the other time is recorded to the minute, the minimum time interval is one minute.

[0120] It should be noted that the aforementioned values ​​are only used to illustrate how the minimum time interval is obtained; the actual minimum time interval is determined based on the smallest time unit that the time field can record.

[0121] The minimum time interval is converted into the time unit used for the correction formation time and correction cutoff time. The converted minimum time interval is used as the length of the time segment. Starting from the correction formation time, the time segment is advanced segment by segment towards the correction cutoff time. The time after each advancement is used as the end time of the current time segment and simultaneously as the start time of the next time segment.

[0122] If the time after the advance is earlier than the correction deadline, the next time segment is formed. If the time after the advance is equal to the correction deadline, the segmentation ends. If the time after the next advance is later than the correction deadline, the correction deadline is used to replace the time after the next advance as the end time of the last time segment. This forms a time segment that extends continuously from the correction formation time to the correction deadline and where adjacent time segments are connected end to end.

[0123] Except for the last time segment, the duration between the start and end times of each time segment is equal to the minimum time interval; the duration between the start and correction cutoff times of the last time segment is less than or equal to the minimum time interval. There is no time overlap or time gap between the time segments.

[0124] The minimum time interval is used to limit the precision of each time segment division. The time segment length represents the duration from the start time to the end time of a single time segment. The interval duration in S3.1.3 represents the duration from the start time to the correction cutoff time of each time segment. The time segment length and the interval duration are different time quantities.

[0125] When the correction formation time is earlier than the correction deadline, time segments are formed step by step according to the minimum time interval. When the correction formation time is equal to the correction deadline, the time interval is no longer advanced according to the minimum time interval. Instead, the correction formation time is used as both the start and end time of the time segment, forming a time segment with a duration of zero. When the correction formation time is later than the correction deadline, it is determined that the delay in maintenance tasks has exceeded the deadline for preventive maintenance. Therefore, time segments are no longer divided from the correction formation time to the correction deadline, and the subsequent interval duration used for comparison is recorded as zero.

[0126] The start times of adjacent time segments differ by a minimum time interval. Therefore, when using the start times of each time segment to locate and recover the critical segment, the time positioning accuracy for recovering the start time of the critical segment does not exceed a minimum time interval.

[0127] S3.1.3. According to the chronological order of each time segment, the duration from the start time to the correction cutoff time in each time segment of industrial cloud computing is used as the interval duration, as follows: ; In the formula, For duration, To correct the cutoff time, This represents the start time of the corresponding time segment.

[0128] The correction cutoff time and the start time of the current time segment are expressed using the same time zone and the same time unit, so that a duration with a unified dimension can be formed between the correction cutoff time and the start time of the current time segment. The interval duration of the current time segment represents the available duration from the start time of the current time segment to the end time of the correction cutoff time, and does not represent the time segment length of the current time segment itself.

[0129] Each time segment follows the time segment division results determined in S3.1.2. The start time of the first time segment is the correction formation time, and the start time of the subsequent time segment is the end time of the previous time segment. The start times of two adjacent time segments differ by the minimum time interval determined in S3.1.2. Except for the last time segment, the time segment length between the start and end times of each time segment is equal to the minimum time interval; the time segment length between the start and end times of the last time segment is no greater than the minimum time interval.

[0130] The start time of each time segment is no later than the correction cutoff time, so the duration is no less than zero, and the duration of each time segment is used as the interval duration of the corresponding time segment.

[0131] If the start time of the current time segment is earlier than the correction deadline, the industrial cloud computing will determine the duration between the start time and the correction deadline of the current time segment as the interval duration of the current time segment; if the start time of the current time segment is equal to the correction deadline, the industrial cloud computing will record the interval duration of the current time segment as zero.

[0132] Starting from the first time segment, each time a complete time segment is advanced, the start time of the next time segment is delayed by a minimum time interval from the start time of the previous time segment. Therefore, the interval length of the next time segment is shortened by a minimum time interval compared to the interval length of the previous time segment. The interval length of the last time segment is the duration between the start time of the last time segment and the correction deadline.

[0133] If the correction formation time is equal to the correction deadline time, then S3.1.2 forms a time segment with a duration of zero, and the industrial cloud computing records the interval duration of the time segment with a duration of zero as zero; if the correction formation time is later than the correction deadline time, then the postponed maintenance task has exceeded the preventive maintenance deadline time, the industrial cloud computing will no longer form an interval duration greater than zero, and will record the interval duration used for subsequent comparison as zero.

[0134] The interval duration of each time segment is shortened sequentially from the earliest to the latest starting time of the time segment, providing time data for subsequent comparisons of the interval duration with the time required to restore the maintenance task.

[0135] S3.2. Compare the time required to restore the obtained maintenance task to obtain the restoration conflict task, specifically, S3.2.1 Obtain the time required to restore the maintenance task from the historical maintenance records of fire protection facilities. Specifically, From the historical maintenance records of the same fire protection facility, select the historical maintenance record that simultaneously records the start time of the maintenance task and the time when the fire protection facility's operating status is restored to its pre-retirement operating status. The duration between the two times is recorded as the historical restoration duration.

[0136] The start time of the maintenance task is the time recorded when the fire protection facility maintenance task enters the execution state. The time when the fire protection facility operation status is restored to the operation status before the exit is the time recorded when the fire protection facility completes maintenance and is restored to the operation status before the maintenance exit state is set. The time when the maintenance exit state begins to be removed is used to record the start time of the fire protection facility operation status restoration phase, and is not used as the start time of the historical restoration duration.

[0137] When there are multiple historical maintenance records of fire protection facilities that meet the above recording conditions, they are arranged from the most recent to the oldest maintenance completion time, and the historical recovery time closest to the current time is used as the time required to restore the maintenance task.

[0138] If there is only one historical maintenance record of fire protection facilities that meets the above recording conditions, the historical recovery time corresponding to the historical maintenance record of fire protection facilities shall be directly used as the time required for the restoration of the maintenance task. Historical maintenance records of fire protection facilities that are missing any time shall not be used to obtain the time required for the restoration of the maintenance task.

[0139] If there is no historical maintenance record for the same fire protection facility that simultaneously records the start time of the maintenance task and the time when the fire protection facility's operating status was restored to its pre-retirement operating status, then from the historical maintenance records of fire protection facilities stored on the cloud platform, a historical maintenance record for a fire protection facility whose model is the same as the fire protection facility model involved in the postponed maintenance task, whose maintenance items are the same as the maintenance items recorded in the postponed maintenance task, and which simultaneously records the start time of the maintenance task and the time when the fire protection facility's operating status was restored to its pre-retirement operating status will be selected.

[0140] If there are multiple historical maintenance records of fire protection facilities that meet the above-mentioned recording conditions under the same fire protection facility model and the same maintenance items, they shall be arranged from the most recent to the oldest maintenance completion time, and the historical recovery time closest to the current time shall be used as the time required to restore the maintenance task; if there is only one historical maintenance record of fire protection facilities that meets the above-mentioned recording conditions, the historical recovery time formed by that historical maintenance record shall be directly used as the time required to restore the maintenance task.

[0141] If there are no historical maintenance records for the same fire protection facility, the same model of fire protection facility, and the same maintenance item that meet the recording conditions, then the cloud platform will read the time required to restore the maintenance task pre-registered according to the fire protection facility model and maintenance item.

[0142] The time required to restore a pre-registered maintenance task is the sum of the operation time required to complete the corresponding maintenance item and the duration required for the fire protection facilities to restore their fire protection capabilities, so that the postponed maintenance task that lacks historical maintenance records of fire protection facilities can still be executed to restore the conflict determination.

[0143] S3.2.2. Verify the interval duration against the time required to restore the maintenance task one by one. The time segment where the duration first falls short of the time required to restore the maintenance task is defined as the critical recovery segment. Specifically, Arrange the divided time segments from earliest to latest according to their start time, and maintain the correspondence between each time segment and its corresponding interval length.

[0144] Starting from the first time segment where the correction is formed, the interval duration of the current time segment is compared with the time required to restore the maintenance task of the same fire protection facility using the same time unit. If the interval duration of the current time segment is longer than the time required to restore the maintenance task, the comparison continues to the next time segment. If the interval duration of the current time segment is equal to the time required to restore the maintenance task, the comparison continues to the next time segment.

[0145] When the interval duration of the current time segment is less than the time required for the maintenance task to recover for the first time, the comparison to the next time segment is stopped, the start and end times of the current time segment are retained, and the current time segment is recorded as the recovery critical segment; until the last time segment corresponding to the correction deadline has not yet had an interval duration less than the time required for the maintenance task to recover, the recovery critical segment is not formed.

[0146] S3.2.3 For maintenance tasks that have formed a critical recovery zone, continuously verify the unified timing benchmark of the cloud platform with the start time of the critical recovery zone. When the unified timing benchmark of the cloud platform is earlier than the start time of the critical recovery zone, maintain the maintenance task in a suspended manner, and re-verify the newly added missing fire protection areas at the start time of each subsequent time zone.

[0147] Maintenance tasks that are temporarily suspended and whose unified timing benchmark on the cloud platform is no earlier than the start time of the recovery critical section and have not yet been re-added to the sequence of maintenance tasks to be executed are identified as recovery conflict tasks.

[0148] S4. After completing the verification of the pending maintenance tasks, restore each fire protection facility to its operating state before the maintenance was lifted, and write the restoration conflict results into the pending maintenance tasks to obtain the preventive maintenance tasks.

[0149] S4.1. Restore all fire protection facilities to their operational state before maintenance and decommissioning, specifically as follows: During the process of setting the fire protection facility nodes involved in the maintenance tasks to the maintenance exit status one by one according to the order of the maintenance tasks to be performed, the time of setting the maintenance exit status of each fire protection facility node, the operating status of the fire protection facility before setting the maintenance exit status, and the maintenance exit status after setting the maintenance exit status are recorded respectively. A status transition record is formed according to the time of setting the maintenance exit status, and the operating status of the fire protection facility recorded before setting the maintenance exit status of each fire protection facility node is retained.

[0150] It should be noted that the state transition records the logical state changes formed by multiple fire protection facilities entering the maintenance exit state in sequence during the verification of the maintenance task to be performed. Each maintenance exit state setting records the state change of a fire protection facility node from the original fire protection facility operation state to the maintenance exit state. It does not mean that the same fire protection facility goes through multiple different actual fire protection facility operation states in sequence.

[0151] The maintenance exit status indicates that the fire protection facility node will not participate in the current fire protection capability assessment during the fire protection relationship verification period. The maintenance exit status only changes the status of the fire protection facility node participating in the fire protection capability assessment, and does not change the actual operation status of the fire protection facilities on site, nor does it change the historical operation status of the fire protection facilities that has been formed during the normal operation of the fire protection facilities.

[0152] After completing the maintenance exit status verification of all pending maintenance tasks, obtain all fire protection facility nodes that are still in the maintenance exit status from the status migration record, as well as the maintenance exit status setting time of each fire protection facility node. Arrange all fire protection facility nodes from latest to earliest according to the maintenance exit status setting time to form the status restoration order.

[0153] The status restoration order includes all fire protection facility nodes that were set to the maintenance exit state during the verification of the pending maintenance task and remain in the maintenance exit state after the verification is completed. The status restoration order is the reverse of the order in which each fire protection facility node entered the maintenance exit state, so that the fire protection facility nodes that enter the maintenance exit state later are arranged at the beginning of the status restoration order.

[0154] Using the state recovery sequence, starting from the first item in the state recovery sequence, each fire protection facility node is restored from the maintenance exit state to the fire protection facility operation state recorded in the state migration record before the maintenance exit state was set. After the current fire protection facility's state recovery is completed, the next item is executed, until all fire protection facilities involved in the state recovery sequence are restored to the fire protection facility operation state recorded before the maintenance exit state was set.

[0155] The above-mentioned state restoration refers to the restoration of the logical state of the fire protection facility nodes in the fire protection relationship diagram during the verification of the maintenance task to be performed. It does not mean that the on-site fire protection facilities are repeatedly started and stopped according to the state restoration order. After the fire protection facility nodes are restored to the fire protection facility operation status recorded before the maintenance exit state setting, the fire protection capability verification is carried out again according to the existing nodes and graph edges in the fire protection relationship diagram.

[0156] After completing all state transitions in the state recovery sequence, verify the current recorded operating status of each fire protection facility in the state recovery sequence against the operating status of the fire protection facilities recorded before the maintenance exit status was set, which is saved in the state migration record. If the current recorded operating status of all fire protection facility nodes is consistent with the operating status of the fire protection facilities saved in the state migration record, then the restoration of all maintenance exit statuses is considered complete. If the current recorded operating status of any fire protection facility node is inconsistent, then restore the operating status of the fire protection facility node again according to the state migration record.

[0157] The fire protection missing area formed before the first maintenance task involving the fire protection facility node was set to the maintenance exit state is identified as the fire protection missing area before verification.

[0158] After restoring the status of all fire protection facility nodes, follow the method in S2.2.2 to check the fire protection area nodes, re-traverse all fire protection area nodes in the fire protection relationship diagram, and check whether each fire protection area node is still connected to fire protection facility nodes that are not in the maintenance withdrawal state.

[0159] If all fire protection facility nodes connected to a fire protection zone node are in a maintenance-out state, then the fire protection zone node is identified as a fire protection zone node that loses fire protection after restoration. If a fire protection zone node is still connected to at least one fire protection facility node that is not in a maintenance-out state, then the fire protection zone node is identified as a fire protection zone node that retains fire protection after restoration. The spatial area occupied by fire protection zone nodes that lose fire protection after restoration is collected to obtain the area lacking fire protection after restoration.

[0160] Following the method in S2.2.3 for comparing the fire protection missing areas before and after installation, the fire protection missing areas before verification and after restoration are compared, and the spatial areas that only exist in the fire protection missing areas after restoration are redefined as newly added fire protection missing areas.

[0161] If the newly identified missing fire protection area does not exist in actual space, the fire protection relationship diagram is considered to have been restored to the fire protection relationship before the verification of the maintenance task to be performed; if the newly identified missing fire protection area still exists in actual space, the fire protection relationship diagram is considered to have not yet been restored to the fire protection relationship before the verification of the maintenance task to be performed, and the relevant postponed maintenance task status for restoring conflict tasks remains.

[0162] S4.2. Write the conflict recovery results into the pending maintenance tasks to obtain preventative maintenance tasks, specifically: The results of resolving conflict, the start and end times of resolving critical sections, the interval used to form critical sections, and the time required for maintenance task recovery are compiled into the conflict resolution results.

[0163] When the newly identified missing fire protection area does not exist in actual space, the conflict recovery result will be written into the conflict recovery task, and the conflict recovery task with the conflict recovery result will be re-placed into the maintenance task sequence to be executed.

[0164] According to the arrangement of maintenance tasks to be performed in S2.1, the execution position of the restoration conflict task is re-determined using the deadline of preventive maintenance; the restoration conflict task with the earlier deadline of preventive maintenance is arranged in the earlier execution position, and the restoration conflict task with the later deadline of preventive maintenance is arranged in the later execution position. When the deadlines of preventive maintenance are the same, the execution position is determined according to the existing numbering order of the fire protection facilities.

[0165] The re-entry of conflict-recovering tasks into the pending maintenance task sequence retains the fire protection facilities, preventive maintenance deadlines, and the results of the conflict recovery, and the rearranged pending maintenance tasks are identified as preventive maintenance tasks.

[0166] If the newly identified areas lacking fire protection still have actual space, the conflict recovery task will not be re-added to the pending maintenance task sequence. The conflict recovery task will remain in the suspended maintenance task status and will not become a currently executable preventive maintenance task.

[0167] This embodiment also provides a cloud-based preventive maintenance task generation system for fire protection facilities, including: The deadline determination module is used to compare the degradation status of fire protection facilities, obtain the current degradation rate, calculate the excess of the current degradation rate relative to the historical stable degradation rate, shorten the remaining maintenance time of the preset maintenance period, select the remaining maintenance time with the shortest duration, and extend the selected remaining maintenance time. The end time of the extension is determined as the deadline for preventive maintenance. The postponement determination module is used to arrange the pending maintenance tasks of each fire protection facility according to the deadline of preventive maintenance, set the fire protection facilities of each pending maintenance task to the maintenance exit state, compare the fire protection missing areas before and after the maintenance exit state, and set the pending maintenance tasks with newly added fire protection missing areas as postponed maintenance tasks. The conflict determination module is used to calculate the interval between the formation time of the postponed maintenance task and the deadline of the preventive maintenance, and compare it with the obtained time required to restore the maintenance task to obtain the conflict task to be restored. The task generation module is used to complete the verification of the maintenance tasks to be performed, restore each fire protection facility to its operating state before the maintenance was cancelled, and write the restoration conflict results into the maintenance tasks to be performed to obtain preventive maintenance tasks.

[0168] This embodiment also provides a computer device applicable to the cloud-based method for generating preventive maintenance tasks for fire protection facilities, 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 cloud-based method for generating preventive maintenance tasks for fire protection facilities as proposed in the above embodiment.

[0169] 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.

[0170] This embodiment also provides a storage medium storing a computer program. When executed by a processor, the program implements the method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform, 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.

[0171] In summary, this invention improves the time matching between maintenance tasks and fire protection facility restoration by using industrial cloud computing to postpone the available time for maintenance tasks and the time required for fire protection facility restoration. This allows maintenance items with conflicting restoration schedules to be identified and handled during the task generation phase, avoiding the neglect of fire protection gaps after fire protection facilities are removed due to time sequence alone in maintenance scheduling. It also reduces the possibility of persistent inadequacy of local fire protection capabilities during maintenance. At the same time, it coordinates maintenance deadline requirements, fire protection integrity, and actual restoration capabilities, reducing manual adjustments and repetitive scheduling during the maintenance task execution phase, and improving the feasibility, timing stability, and scheduling rationality of preventive maintenance tasks.

[0172] 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 generating preventive maintenance tasks for fire protection facilities based on a cloud platform, characterized in that: include, The degradation status of fire protection facilities is compared to obtain the current degradation rate. The excess of the current degradation rate relative to the historical stable degradation rate is calculated, and the remaining maintenance time of the preset maintenance period is shortened. The remaining maintenance time with the shortest duration is selected, and the selected remaining maintenance time is extended. The end time of the extension is determined as the deadline for preventive maintenance. The pending maintenance tasks of each fire protection facility are arranged according to the deadline of preventive maintenance, and the fire protection facilities of each pending maintenance task are set to the maintenance exit state. The fire protection missing areas before and after the maintenance exit state are compared, and the pending maintenance tasks with newly added fire protection missing areas are designated as postponed maintenance tasks. Calculate the interval between the time when the deferred maintenance task is formed and the deadline of the preventive maintenance, and compare it with the time required to restore the obtained maintenance task to obtain the conflicting task to be restored. After completing the verification of the pending maintenance tasks, restore each fire protection facility to its operating state before maintenance was lifted, and write the result of the restoration conflict into the pending maintenance tasks to obtain the preventive maintenance tasks.

2. The method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform as described in claim 1, characterized in that: The current degradation rate is obtained by fitting the slope of the operating state of the fire protection facilities using the Theil-Sen robust slope method, obtaining the slope of the state change at different sampling locations, and taking the median of the slope of the state change as the current degradation rate.

3. The method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform as described in claim 2, characterized in that: The remaining maintenance time for shortening the preset maintenance period is obtained by acquiring the original remaining maintenance time, and proportionally calculating the original remaining maintenance time based on the amount by which the current degradation rate exceeds the historical stable degradation rate, thus obtaining the shortened remaining maintenance time.

4. The method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform as described in claim 3, characterized in that: The specific steps for setting each fire protection facility awaiting maintenance to the maintenance-off state are as follows: Based on the maintenance tasks to be performed, fire protection facilities and fire protection areas are used as nodes. The nodes are established according to the spatial ownership relationship between fire protection facilities and fire protection areas to obtain the fire protection relationship diagram. In the fire protection relationship diagram, select the maintenance tasks to be performed one by one and set them to the maintenance exit state. Check whether each fire protection zone node is still connected to the fire protection facility nodes that are not in the maintenance exit state. Then, gather the space areas that have lost fire protection to obtain the fire protection missing areas before installation and the fire protection missing areas after installation. By comparing the spatial extent of the areas lacking fire protection before and after the installation of fire protection, the spatial areas that exist only in the areas lacking fire protection after the installation are identified as newly added areas lacking fire protection.

5. The method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform as described in claim 4, characterized in that: The spatial attribution relationship refers to the coverage relationship between fire protection facilities, fire protection areas, and their respective fire compartments.

6. The method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform as described in claim 5, characterized in that: The specific steps for designating maintenance tasks in areas with newly added fire protection deficiencies as temporarily suspended maintenance tasks are as follows: The area lacking fire protection is divided into missing sub-areas, and the fire protection area nodes of each missing sub-area are retained; Tracing the fire protection facilities that are out of maintenance along the nodes of each fire protection zone, and merging the missing sub-areas of the same fire protection facility into the fire protection missing range; In the pending maintenance tasks, locate the fire protection facilities that have a spatial relationship with the newly added fire protection missing area, and record the pending maintenance tasks of the fire protection facilities as postponed maintenance tasks.

7. The method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform as described in claim 6, characterized in that: The specific steps for calculating the interval between the formation time of the postponed maintenance task and the deadline of the preventive maintenance are as follows: Using the unified timing benchmark of the cloud platform, clock offset corrections are performed on the formation time of the postponed maintenance task and the deadline of the preventive maintenance, respectively, to obtain the correction formation time and correction deadline. The time segments are divided according to the time sequence from the time of correction formation to the time of correction cutoff. The duration between the start time and the correction deadline in each time segment of industrial cloud computing is used as the interval duration.

8. The method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform as described in claim 7, characterized in that: The specific steps for obtaining the conflict recovery task are as follows: Obtain the time required to restore the maintenance task from the historical maintenance records of fire protection facilities; Check the interval duration against the time required to restore the maintenance task one by one, and determine the time segment in which the duration is first shorter than the time required to restore the maintenance task as the critical recovery segment; The maintenance tasks that temporarily suspend the process to form a critical recovery zone are identified as recovery conflict tasks.

9. The method for generating preventive maintenance tasks for fire protection facilities based on a cloud platform as described in claim 8, characterized in that: The specific steps for obtaining the preventive maintenance task are as follows: The maintenance and repair of each fire protection facility node will be restored to the operational status of the fire protection facility before the maintenance and repair was set, and newly added areas lacking fire protection will be re-identified. When a newly added area lacking fire protection does not exist in actual space, the conflict task will be restored and reassigned to the pending maintenance task. The execution location will be re-determined using the deadline for preventive maintenance, thus obtaining the preventive maintenance task.

10. A cloud-based system for generating preventive maintenance tasks for fire protection facilities, based on the cloud-based method for generating preventive maintenance tasks for fire protection facilities according to any one of claims 1 to 9, characterized in that: include, The deadline determination module is used to compare the degradation status of fire protection facilities, obtain the current degradation rate, calculate the excess of the current degradation rate relative to the historical stable degradation rate, shorten the remaining maintenance time of the preset maintenance period, select the remaining maintenance time with the shortest duration, and extend the selected remaining maintenance time. The end time of the extension is determined as the deadline for preventive maintenance. The postponement determination module is used to arrange the pending maintenance tasks of each fire protection facility according to the deadline of preventive maintenance, set the fire protection facilities of each pending maintenance task to the maintenance exit state, compare the fire protection missing areas before and after the maintenance exit state, and set the pending maintenance tasks with newly added fire protection missing areas as postponed maintenance tasks. The conflict determination module is used to calculate the interval between the formation time of the postponed maintenance task and the deadline of the preventive maintenance, and compare it with the obtained time required to restore the maintenance task to obtain the conflict task to be restored. The task generation module is used to complete the verification of the maintenance tasks to be performed, restore each fire protection facility to its operating state before the maintenance was cancelled, and write the restoration conflict results into the maintenance tasks to be performed to obtain preventive maintenance tasks.

Images