Tower inspection data management system, method, device and medium

Abstract

The application discloses a tower machine inspection data management system, method, equipment and medium, which is applied to the technical field of tower machine management and comprises a data integration module, which synchronizes the inspection results and inspection images of each tower machine part of an inspection task from an edge computing terminal in real time and synchronizes the inspection log of the inspection task from an inspection handheld terminal in real time, and integrates the inspection log of the inspection task and the inspection results and inspection images of each tower machine part into a graph database; a report generation module, which monitors the triggering of any report type associated triggering event, generates a tower machine inspection data report based on the graph database by using a report template corresponding to any report type; and a file output module, which exports the tower machine inspection data report in a target file format, so that centralized and standardized management of tower machine inspection data is realized, and the traceability of tower machine inspection data and the real-time performance of tower machine inspection reports are improved.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of tower crane management, and in particular to a tower crane inspection data management system, method, device and medium. BACKGROUND

[0002] The tower crane is a kind of hoisting equipment most commonly used on a construction site, also known as a tower crane, and is used for hoisting materials such as steel bars, wood blocks, concrete and steel pipes for construction, and is an indispensable equipment on a construction site. The existing tower crane inspection data management mode usually relies on manual paper records, and has problems such as scattered data, lagging reports, inconsistent standards and difficult traceability. SUMMARY

[0003] The application provides a tower crane inspection data management system, method, device and medium to solve the problems of low management efficiency, poor accuracy and real-time performance of the existing tower crane inspection data management mode. The technical scheme provided by the application is as follows:

[0004] In one aspect, the application provides a tower crane inspection data management method, comprising:

[0005] A data integration module is configured to synchronize the inspection results and images of each tower crane component of the inspection task from the edge computing terminal in real time, and synchronize the inspection log of the inspection task from the inspection handheld terminal in real time; and integrate the inspection log of the inspection task and the inspection results and images of each tower crane component into a graph database;

[0006] A report generation module is configured to monitor the triggering of any report type associated trigger event based on different report type associated trigger events, and when any report type associated trigger event is triggered, generate a tower crane inspection data report based on the graph database by using a report template corresponding to any report type;

[0007] A file output module is configured to export the tower crane inspection data report in a target file format.

[0008] Optionally, the data integration module comprises:

[0009] The inspection result record submodule is configured to splice and hash the tower crane number, the tower crane component number, the automatic inspection timestamp, and the random number corresponding to each tower crane component in a set time window to obtain a globally unique defect identifier of each tower crane component; convert the defect position in the inspection result of each tower crane component from a pixel-level coordinate system to a tower crane coordinate system and then to a geodetic coordinate system to obtain the defect position of each tower crane component in the geodetic coordinate system; map the defect category, defect confidence, and defect physical quantity in the inspection result of each tower crane component to a standard hazard level; convert the inspection result of each tower crane component into natural language to obtain defect description data of each tower crane component; encapsulate the defect position of each tower crane component in the geodetic coordinate system, the standard hazard level, and the defect description data into a defect record; and construct a tower crane node, a tower crane component node, a defect type node, and a defect record node based on the tower crane number, the tower crane component number, the automatic inspection timestamp, the globally unique defect identifier, the defect position in the geodetic coordinate system, the standard hazard level, the defect description data, and the defect record.

[0010] The inspection image record submodule is configured to extract the metadata of each inspection image of each tower crane component in a set time window, and generate a unique fingerprint for each inspection image of each tower crane component based on the metadata of each inspection image of each tower crane component by using a perceptual hashing algorithm; perform deduplication processing on each inspection image of each tower crane component based on the unique fingerprint of each inspection image of each tower crane component; physically archive the deduplicated inspection images of each tower crane component and generate a storage path according to the directory structure of the tower crane, the shooting timestamp, the tower crane component, and the image type; generate a thumbnail and an access link for each deduplicated inspection image of each tower crane component; and construct an inspection image node based on the unique fingerprint, the storage path, the thumbnail, and the access link of each deduplicated inspection image of each tower crane component.

[0011] The inspection log record submodule is configured to split each inspection log of an inspection task in a set time window into five elements including an inspection personnel, a manual inspection timestamp, an inspection tower crane and tower crane component, an inspection operation, and an inspection result; splice and hash the five elements of each inspection log to obtain a unique identifier of each inspection log; and construct an inspection log node based on the unique identifier and the five elements of each inspection log.

[0012] The subgraph generation submodule is configured to construct an edge relationship between nodes based on the tower crane node, the tower crane component node, the defect type node, the defect record node, the inspection image node, and the inspection log node in a set time window to form subgraph data.

[0013] The inspection event aggregation submodule is configured to pack subgraph data in a set time window into one inspection event, and generate a globally unique event identifier for the inspection event; wherein all subgraph data in the set time window forms a graph database.

[0014] Optionally, the data integration module further comprises:

[0015] The voice shorthand submodule is configured to convert voice inspection note information synchronized in real time from the inspection handheld terminal into text inspection note information by using a Whisper model, and insert the text inspection note information into the corresponding inspection log.

[0016] Optionally, the report generation module comprises:

[0017] The dynamic template submodule is configured to initiate a rendering instruction based on the daily briefing, the file format and the globally unique event identifier when the Quartz timer detects a timing wake-up event, and initiate a rendering instruction based on the special report, the file format and the globally unique event identifier when the Webhook receiver detects an abnormal threshold event.

[0018] The intelligent layout submodule is configured to pull subgraph data from the graph database based on the globally unique event identifier in the rendering instruction when the rendering instruction is received, and sequentially perform content verification, standard matching and warning visualization processing on the subgraph data to obtain various intermediate rendering objects.

[0019] Optionally, the file output module comprises:

[0020] The PDF report submodule is configured to generate a daily briefing and / or a special report in PDF format as the tower crane inspection data report based on the various intermediate rendering objects by using the iText7 library.

[0021] The Excel report submodule is configured to generate a daily briefing and / or a special report in Excel format as the tower crane inspection data report based on the various intermediate rendering objects by using the Apache POI.

[0022] The web version report submodule is configured to generate a daily briefing and / or a special report in the form of a web page as the tower crane inspection data report based on the various intermediate rendering objects by using the Three.js.

[0023] Optionally, the tower crane inspection data management system provided by the application further comprises:

[0024] The maintenance work order generation module is configured to parse the standard risk level of each tower crane component from the tower crane inspection data report, call an application programming interface of an ERP system to create a maintenance work order based on the standard risk level of each tower crane component, and associate the maintenance work order with the tower crane inspection data report.

[0025] Optionally, the tower inspection data management system provided by the application further comprises:

[0026] a multi-language support module, configured to use the LLM translation model to output the tower inspection data report as a multi-language tower inspection data report.

[0027] In another aspect, the application provides a tower inspection data management system, applied to the above-mentioned tower inspection data management system, comprising:

[0028] synchronizing the inspection results and inspection images of each tower component of the inspection task in real time from the edge computing terminal and synchronizing the inspection log of the inspection task in real time from the handheld terminal;

[0029] integrating the inspection log of the inspection task and the inspection results and inspection images of each tower component into a graph database;

[0030] based on the trigger events associated with different report types, when any report type associated trigger event is triggered, using the report template corresponding to the report type, generating a tower inspection data report based on the graph database;

[0031] exporting the tower inspection data report in a target file format.

[0032] In another aspect, the application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the above-mentioned tower inspection data management method when executing the computer program.

[0033] In another aspect, the application provides a computer readable storage medium, which stores computer instructions, and the computer instructions are executed by a processor to implement the above-mentioned tower inspection data management method.

[0034] The beneficial effects of the application are as follows:

[0035] The application integrates the inspection log of the inspection task and the inspection results and inspection images of each tower component into a graph database through the data integration module, realizes the structuring and automatic classification of the inspection data, improves the data integration efficiency, and moreover, through the report generation module, when any report type associated trigger event is triggered, using the report template corresponding to the report type, generating a tower inspection data report based on the graph database, realizes the automatic generation of the tower inspection data report without human intervention, shortens the output time of the tower inspection data report, improves the management efficiency, accuracy and real-time performance of the inspection data, and in addition, through the file output module, exporting the tower inspection data report in a target file format, realizes the visualization of the tower inspection data report, and provides data support for the safety of tower operation.

[0036] Other features and advantages of the present application will be set forth in the following specification, and in part will become apparent to those skilled in the art on examination of the specification or by practice of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings. BRIEF DESCRIPTION OF DRAWINGS

[0037] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the present application and together with the description serve to explain the present application. In the drawings:

[0038] Figure 1 It is a schematic diagram of the composition structure of the tower machine inspection data management system in the embodiment of the present application;

[0039] Figure 2 It is a schematic diagram of the general process of the tower machine inspection data management method in the embodiment of the present application;

[0040] Figure 3 It is a schematic diagram of the hardware structure of the electronic device in the embodiment of the present application. DETAILED DESCRIPTION

[0041] In order to make the purpose, technical scheme and beneficial effects of the present application more clear, the technical scheme in the embodiment of the present application will be described clearly and completely below in combination with the drawings in the embodiment of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0042] The embodiment of the present application provides a tower machine inspection data management system, as shown in Figure 1 The tower machine inspection data management system 100 provided by the embodiment of the present application at least includes:

[0043] The data integration module 110 is used for synchronizing the inspection results and inspection images of each tower machine component of the inspection task from the edge computing terminal in real time and synchronizing the inspection log of the inspection task from the inspection handheld terminal in real time; and integrating the inspection log of the inspection task and the inspection results and inspection images of each tower machine component into a graph database;

[0044] The report generation module 120 is used for monitoring the triggering of any report type associated triggering event based on the triggering event associated with different report types, and when any report type associated triggering event is triggered, generating a tower machine inspection data report based on the graph database by using the report template corresponding to any report type;

[0045] The file output module 130 is configured to export the tower crane inspection data report in a target file format.

[0046] In the embodiment, the data integration module 110 integrates the inspection logs of the inspection tasks and the inspection results and images of the tower crane components into a graph database, realizes the structuring and automatic classification of the inspection data, improves the data integration efficiency, and further realizes the automatic generation of the tower crane inspection data report without manual intervention by the report generation module 120, which shortens the output time of the tower crane inspection data report, improves the management efficiency, accuracy and real-time performance of the inspection data, and further realizes the visualization of the tower crane inspection data report by the file output module 130, which provides data support for the safety of the tower crane operation.

[0047] In a possible implementation, the data integration module 110 includes:

[0048] The inspection result recording submodule 111 is configured to splice and hash the tower crane number, the tower crane component number, the automatic inspection timestamp and the random number of each tower crane component in a set time window to obtain a globally unique defect identifier of each tower crane component; convert the defect position in the inspection result of each tower crane component from a pixel-level coordinate system to a tower crane coordinate system and then to a geodetic coordinate system to obtain the defect position of each tower crane component in the geodetic coordinate system; map the defect category, the defect confidence and the defect physical quantity in the inspection result of each tower crane component to a standard hazard level; convert the inspection result of each tower crane component into natural language to obtain defect description data of each tower crane component, and encapsulate the defect position of each tower crane component in the geodetic coordinate system, the standard hazard level and the defect description data into a defect record; and construct a tower crane node, a tower crane component node, a defect type node and a defect record node based on the tower crane number, the tower crane component number, the automatic inspection timestamp, the globally unique defect identifier, the defect position in the geodetic coordinate system, the standard hazard level, the defect description data and the defect record.

[0049] The inspection image recording submodule 112 is configured to extract metadata of each inspection image of each tower component in the set time window, and generate a unique fingerprint for each inspection image of each tower component based on the metadata of each inspection image of each tower component by using a perceptual hashing algorithm; perform deduplication processing on each inspection image of each tower component based on the unique fingerprint of each inspection image of each tower component; physically archive the deduplicated inspection images of each tower component and generate a storage path according to a directory structure of the tower, a shooting timestamp, a tower component and an image type; generate a thumbnail and an access link for each deduplicated inspection image of each tower component; and construct an inspection image node based on the unique fingerprint, the storage path, the thumbnail and the access link of each deduplicated inspection image of each tower component.

[0050] The inspection log recording submodule 113 is configured to split each inspection log of an inspection task in the set time window into five elements including an inspection personnel, a manual inspection timestamp, an inspection tower and a tower component, an inspection operation and an inspection result; perform splicing and hashing processing on the five elements of each inspection log to obtain a unique identifier of each inspection log; and construct an inspection log node based on the unique identifier and the five elements of each inspection log.

[0051] The subgraph generation submodule 114 is configured to construct an edge relationship between nodes based on the tower node, the tower component node, the defect type node, the defect record node, the inspection image node and the inspection log node in the set time window to form subgraph data.

[0052] The inspection event aggregation submodule 115 is configured to pack the subgraph data in the set time window into an inspection event, and generate a globally unique event identifier for the inspection event; and all the subgraph data in the set time window form a graph database.

[0053] In the embodiments of the present application, the inspection results are continuously generated by the edge computing terminal installed on the tower crane. The edge computing terminal integrates a high-definition visible light camera, an infrared thermal imager, a millimeter wave radar, and a built-in defect recognition model, and can capture and analyze the state of the tower crane components in real time in the climbing, rotating, or stopped state. Subsequently, the inspection results such as crack position and bolt loosening are returned to the data integration module 110. The inspection images are also obtained by the edge computing terminal, and are returned to the data integration module 110 through high-speed WiFi or 5G private network. The visible light and infrared dual-channel are synchronously collected to form a high-definition visible light image and an infrared thermal imaging image. The high-definition visible light image and the infrared thermal imaging image are returned to the data integration module 110 as the inspection images. The inspection log is generated by the inspection handheld terminal carried by the on-site personnel. The inspection handheld terminal has functions such as voice input, photographing, code scanning, and electronic signature. After the on-site personnel complete the manual review, measurement, or emergency disposal operation on each tower crane component of the tower crane, the operation time, personnel information, and abnormal processing process are synchronized to the data integration module 110 in real time or offline in the form of a log, so that the data integration module 110 can continuously receive the inspection results, the inspection images, and the inspection log. The set time window refers to the time interval for packaging and writing the continuously arriving inspection results, inspection images, and inspection logs once. In the tower crane inspection scene, the set time window can be set to 30 seconds, 20 seconds, etc. The starting time is the timestamp of the first time the first tower crane component generates an inspection result or an inspection image or an inspection log. The end time is the starting time plus 30 seconds, 20 seconds, etc. Each set time window is a transaction of the graph database. Each transaction has a globally unique transaction identifier. For example, the globally unique transaction identifier of the transaction is generated based on the starting timestamp and the ending timestamp (i.e., the starting time and the ending time of the set time window) of the transaction and a random number (e.g., 128-bit UUID).

[0054] In the embodiments of the present application, for the inspection results in the set time window, first, when the inspection result recording submodule 111 receives the inspection results of each tower component returned by the edge computing terminal, a globally unique defect identifier (i.e., defect GUID) is assigned to each inspection result. The globally unique defect identifier is formed by concatenating the tower number, the tower component number, the automatic inspection timestamp, and a random number (such as a 128-bit UUID) into a string, and then using the SHA-256 algorithm to hash the string to generate a 256-bit hash value. The first 128 bits (16 bytes) of the hash value are extracted and converted to a 32-bit hexadecimal string as the final globally unique defect identifier (i.e., defect GUID), ensuring that it is not repeated in the entire life cycle. Subsequently, the pixel-level defect positions returned by the edge computing terminal are converted to the tower coordinate system and then mapped to the geodetic coordinate system, so that the defect positions of each defect such as cracks and loose bolts have an engineering-readable physical meaning. The geodetic coordinate system refers to the CGCS2000 geodetic coordinate system (EPSG: 4490) consistent with the national surveying and mapping datum or the WGS-84 geodetic coordinate system (EPSG: 4326) adopted according to the location of the project. The absolute latitude, longitude, and ellipsoidal height of the center of the tower base measured by the GNSS-RTK device on site are used as the origin coordinates of the tower. The three-dimensional coordinates of all defect positions are first expressed in the tower coordinate system (X, Y, Z), and then translated, rotated, and scaled through a seven-parameter conversion model to output the longitude L, latitude B, and elevation H in the geodetic coordinate system, thereby ensuring that the spatial data across towers and across sites can be compared and spliced under the same reference. Next, based on the defect risk degree mapping table, the defect category, defect confidence, and defect physical quantity returned by the edge computing terminal are mapped to the national standard I to IV level standard risk degree level. The defect risk degree mapping table is developed by industry experts based on GB / T 5031-2019, GB 5144-94, and on-site accident statistics, and is fixed to the edge computing terminal through OTA. The core logic of the defect risk degree mapping table is a two-factor judgment. The first factor is the confidence p (0-1) of the defect category, and the second factor is the defect physical metric m (crack length, bolt residual pre-tightening force percentage, rust area, etc.). After quantifying the confidence p and the defect physical metric m, the two-dimensional lookup table can uniquely determine the I, II, III, and IV risk degrees.For example, when p > 0.9 and m falls into the interval of "crack length > 50 mm or bolt residual pre-tightening force < 70%", it is directly classified as level III; when p is between 0.7-0.9 and m is in the interval of "crack length 20-50 mm", it is classified as level II; otherwise, the higher level is taken according to the conservative principle; then, the pre-trained language model (fine-tuned by tower crane domain corpus) is called to convert the inspection results of each tower crane component into natural language to obtain defect description data of each tower crane component, for example, the defect description data is "53 mm longitudinal crack appears at 0.8 m from the north side of the main chord to the lower end surface of the 12th standard section, the crack is open, and the edge has slight rust", which is packaged as a defect record together with the standard hazard level and the defect position in the CGCS2000 coordinate system; finally, based on the tower crane number, the tower crane component number, the automatic inspection timestamp, the globally unique defect identifier, the defect position in the CGCS2000 coordinate system, the standard hazard level, the defect description data and the defect record, the tower crane node, the tower crane component node, the defect type node, the defect record node and the standard clause node are constructed, wherein:

[0055] The tower crane node Crane has attributes including CraneID: unique identifier of the tower crane; Model: tower crane model; Manufacturer: manufacturer; InstallationDate: installation date; Location: installation location of the tower crane (longitude and latitude and elevation in the CGCS2000 coordinate system); Status: current state of the tower crane (such as "normal operation", "decommissioned", etc.); and purpose includes: represents a specific tower crane entity, as the home node of other nodes (such as components, defects, inspection records, etc.);

[0056] The tower crane component node Component has attributes including ComponentID: unique identifier of the component; ComponentName: component name (such as "standard section", "slewing bearing", "lifting arm", etc.); CraneID: identifier of the tower crane it belongs to; Location: specific location of the component (longitude and latitude and elevation in the CGCS2000 coordinate system); InstallationDate: component installation date; Status: current state of the component (such as "normal", "damaged", etc.); and purpose includes: represents each component of the tower crane, as an associated node of the defect record, facilitating positioning of the specific location of the defect;

[0057] Defect, attributes include: DefectID: unique identifier of the defect (GUID); CategoryID: identifier of the defect category; Location: specific location of the defect (latitude, longitude and elevation in CGCS2000 coordinate system); Severity: risk level of the defect (such as "Class I", "Class II", etc.); DetectionTime: timestamp when the defect was detected; Description: natural language description of the defect; ImageID: ID of the image node associated with the defect (if any); LogID: ID of the log node associated with the defect (if any); purposes include: representing a specific defect record, associating with the component node, facilitating tracing the specific location and related components of the defect.

[0058] DefectCategory, attributes include: CategoryID: unique identifier of the defect category; CategoryName: name of the defect category (such as "crack", "loose bolt", etc.); Description: detailed description of the defect category; SeverityLevel: default risk level of the category defect; StandardReference: reference to the corresponding national standard clause; purposes include: representing the classification of defects, facilitating the classification management and query of defects;

[0059] Inspection, attributes include: InspectionID: unique identifier of the inspection record; CraneID: identifier of the tower crane for inspection; StartTime: start time of the inspection; EndTime: end time of the inspection; Inspector: inspector; Status: inspection status (such as "completed", "interrupted", etc.); purposes include: representing a complete inspection activity, serving as an associated node of the defect record, facilitating tracing the detection batch of the defect;

[0060] Standard, attributes include: StandardID: unique identifier of the standard clause; StandardName: standard name (such as "GB 5144-94"); ClauseNumber: clause number (such as "5.2.3"); ClauseContent: clause content; purposes include: representing the relevant national standard clause, associating with the defect category node, facilitating the reference of the standard clause.

[0061] In the embodiments of the present application, for the inspection images in the set time window, first, when the inspection image recording submodule 112 receives the inspection images of each tower component returned by the edge computing terminal, the metadata of the inspection images are extracted by calling tools such as ExifTool, including the shooting focal length, GPS information, temperature matrix (for infrared images), etc.; then, based on the metadata of each inspection image of each tower component, a unique fingerprint is generated for each inspection image using the perceptual hashing algorithm (pHash), and each inspection image of each tower component is processed for deduplication based on the unique fingerprint of each inspection image of each tower component, for example, if the Hamming distance is less than a set threshold (such as 10), it is considered that two inspection images are repeated or highly similar, only one representative inspection image is retained, and the remaining inspection images are marked as repeated and optionally deleted; subsequently, the deduplicated inspection images of each tower component are physically archived and a storage path is generated according to the directory structure of the tower, the shooting timestamp, the tower component and the image type, and a thumbnail and an access link are generated for the deduplicated inspection images of each tower component; finally, based on the unique fingerprint, the storage path, the thumbnail and the access link of the deduplicated inspection images of each tower component, an inspection image node is constructed; wherein:

[0062] The inspection image node Image has the following attributes: ImageID: unique identifier of the image; ImagePath: storage path of the image; ImageType: image type (such as “visible light”, “infrared thermal imaging” etc.); DetectionTime: image shooting time; ComponentID: component identifier corresponding to the image; DefectID: defect identifier corresponding to the image (if any); and the following uses: to represent the inspection-related image record, to associate with the defect node, and to facilitate viewing of specific images of the defect.

[0063] In the embodiments of the present application, for the inspection log within the set time window, first, when the inspection log recording submodule 113 receives the inspection log returned by the inspection handheld terminal, the inspection log is split into five elements including the inspection personnel, the manual inspection timestamp, the inspection tower and tower component, the inspection operation and the inspection result, that is, each inspection log carries five elements (who, when, which tower component of which tower, what operation and what result); then, the five elements of the inspection log are spliced into a string, a random number (such as 128-bit UUID) is generated and appended to the end of the string, and SHA-256 hash calculation is performed on the string to obtain a 256-bit hash value, the first 96 bits (12 bytes) of the 256-bit hash value are extracted and converted into Base32 code to obtain a 20-character unique identifier, so that the inspection log obtains a unique and tamper-proof identifier, ensuring the integrity and credibility of the inspection log; finally, based on the unique identifier and the five elements of each inspection log, the inspection log node and the inspection personnel node are constructed, wherein:

[0064] The inspection log node Log includes the following attributes: LogID: unique identifier of the log; LogContent: log content (such as operation time, personnel, abnormal handling process, etc.); DetectionTime: log recording time; ComponentID: component identifier corresponding to the log; DefectID: defect identifier corresponding to the log (if any); and the following uses: indicating the operation log in the inspection process, being associated with the defect node to facilitate tracing the handling process of the defect;

[0065] The inspection personnel node Operator includes the following attributes: OperatorID: unique identifier of the inspection personnel; Name: name of the inspection personnel; Role: role of the inspection personnel (such as “engineer”, “technician”, etc.); Contact: contact information; and the following uses: indicating the personnel participating in the inspection, serving as the associated node of the inspection record and the log to facilitate tracing the operation personnel.

[0066] In the embodiments of the present application, for the tower crane nodes, tower crane component nodes, defect type nodes, defect record nodes, standard clause nodes, inspection image nodes, inspection log nodes and inspection personnel nodes within the set time window, the subgraph generation submodule 114 constructs the edge relationship between each node to form subgraph data; wherein the edge type between the tower crane node and the component node is HAS_COMPONENT, the edge type between the tower crane component node and the defect record node is HAS_DEFECT, the edge type between the defect record node and the defect category node is BELONGS_TO_CATEGORY, the edge type between the defect record node and the standard clause node is REFERENCED_BY, the edge type between the defect record node and the inspection image node is DEPICTS, the edge type between the defect record node and the inspection log node is ABOUT, and the edge type between the inspection personnel node and the inspection log node is CREATED_BY. The subgraph data is constructed through the above edge relationship, and the subgraph data includes: one tower crane node, one or more tower crane component nodes, one or more defect record nodes, one or more defect type nodes, one or more standard clause nodes, one or more inspection image nodes, one or more inspection log nodes, and one or more inspection personnel nodes.

[0067] In the embodiments of the present application, the inspection event aggregation submodule 115 encapsulates the subgraph data within the set time window into an inspection event node InspectionEvent, and generates a globally unique event identifier EventID. The globally unique event identifier EventID takes the globally unique transaction identifier TxID of the transaction corresponding to the set time window, the GUID list DefectGUIDs of all defect records, the pHash fingerprint list ImageHashes of all inspection images, the hash list LogHashes of all log records, the completion timestamp Timestamp of the inspection event, and the SM2 digital signature Signature of the private key of the tower crane inspection data management system based on the splicing result of the above fields as core factors, splices them into a long string, and then performs SHA-256 hash calculation on the spliced string to obtain a 256-bit binary digest. The first 96 bits (12 bytes) of the binary digest are extracted and converted to Base32 encoding to obtain a 20-character globally unique event identifier EventID of the inspection event node InspectionEvent.

[0068] Through the above steps, all related nodes and edge relationships are constructed to form a complete subgraph data for subsequent query, analysis and report generation; wherein, all subgraph data within the set time window forms a graph database. Among them, the inspection event node InspectionEvent, the attributes include: EventID: a globally unique event identifier; CraneID: tower crane number; ComponentID: tower crane component number; StartTime: event start time (i.e. the start time of the set time window); EndTime: event end time (i.e. the end time of the set time window); DefectCount: the number of defect positions found in this inspection event; LogCount: the number of logs recorded in this event; ImageCount: the number of inspection images taken in this inspection event; InspectorID: the personnel number of the inspector; the purposes include: data aggregation and encapsulation, encapsulating all related data (including defect records, images, logs, personnel, etc.) within the set time window into a complete event body, so that all information of each inspection activity is centrally managed, facilitating subsequent query and analysis; event identification and indexing, a globally unique event identifier is provided through EventID, which is used to uniquely identify an inspection event, not only as the primary key in the graph database, but also used for blockchain storage, ensuring the non-tamperability and traceability of the event; version management, each re-inspection or new inspection activity will generate a new InspectionEvent node, and connect with the previous version through the NEXT_VERSION edge to form a version chain, thereby supporting the traceability and analysis of the defect history of the tower crane component; query and traceability, through Event-ID, defect records, images, logs, etc. can be pulled at one time, without complex queries across multiple tables or nodes, improving query efficiency and response speed; report generation, InspectionEvent node provides a unified data entry for report generation, whether it is a PDF, Excel or web-based report, it can quickly locate the relevant data through Event-ID and generate a complete report, ensuring the accuracy and consistency of the report; data analysis, InspectionEvent node supports in-depth analysis of inspection data, through analyzing the defect records, images and logs in the event body, it can generate defect distribution heat map, component health curve diagram, etc., providing data support for tower crane maintenance and management; blockchain storage, the Event-ID of InspectionEvent node is written into the blockchain to form an unalterable evidence chain, not only ensuring the authenticity and integrity of the data, but also providing strong support for subsequent audit and compliance check;Real-time monitoring and early warning, the InspectionEvent node can reflect the inspection state of the tower crane in real time, through the defect record and log in the event body, potential safety hazards can be found in time, and the early warning mechanism is triggered; user interface display, the InspectionEvent node provides structured data display for the user interface, the user can quickly view the detailed information of each inspection through the event body, including defect position, image, processing process, etc., which is convenient for on-site operators and managers to make real-time monitoring and decision; data backup and recovery, the InspectionEvent node supports data backup and recovery, through the integrity and consistency of the event body, it can quickly recover to the latest state when data is lost or damaged. In this way, by completing the above processing of the inspection result, the inspection image and the inspection log respectively, the same tower crane, the same component, the defect record, the image set and the operation log appearing in the set time window can be automatically packaged into an event body as an aggregation unit, written into the graph database at one time, each event body carries a unified version number and a globally unique event identifier, supports subsequent incremental update and historical backtracking, if new inspection result or inspection image or inspection log appears after a set time (for example, 30 seconds), the next set time window is started, and a version chain is formed. Therefore, the inspection result, the inspection image and the inspection log are no longer isolated files, but form a comprehensive digital archive that can be expanded, called and verified at any time under the unified space-time coordinates, unified semantic system and unified identity.

[0069] In the embodiment of the application, the data integration module 110 further includes:

[0070] The blockchain writing submodule 116 is configured to, after the aggregation of the inspection event is completed, that is, the defect node, the image node, and the log node have all been stored in the database, and the three have been associated through the edges in the graph database, first, generate a to-be-chained record, the to-be-chained record including: an event summary, a 256-bit hash summary generated by performing SHA-256 hash calculation on a global unique transaction identifier TxID, a list of GUIDs of all defect records DefectGUIDs, a list of pHash fingerprints of all inspection images ImageHashes, and a list of hashes of all log records LogHashes; a timestamp, a completion timestamp Timestamp when the aggregation of the event is completed; a signature, an SM2 digital signature Signature of the event summary based on a private key of the tower crane inspection data management system; then, using a consensus algorithm (for example, a Raft consensus algorithm), write the to-be-chained record to a consortium chain (Hyperledger Fabric light channel), write the generated hash summary to the Hyperledger Fabric light channel, limit the block size to 512 bytes, ensure that each block only contains the hash summary of one event, the block time is short, and the real-time performance of the data can be ensured. After the on-chain writing is successful, write {EventID, block number, transaction number} back to the InspectionEvent node of the graph database, and any third party can verify the integrity of the event in the graph database through the on-chain EventID, for example, recompute the event summary and compare it with the on-chain event summary, and verify the SM2 signature, so as to confirm whether the event is tampered with. Through the above operation, each inspection event can obtain an unforgeable EventID on the lightweight consortium chain while being stored in the graph database, and the low-cost and high-trust evidence storage of the off-chain full data and the on-chain lightweight hash is realized.

[0071] In a possible implementation, the data integration module 110 further includes:

[0072] The voice shorthand submodule 116 is configured to convert the voice inspection note information synchronized in real time from the inspection handheld terminal into text inspection note information by using a Whisper model, and insert the text inspection note information into the corresponding inspection log.

[0073] In the embodiments of the present application, the Whisper model is a speech recognition model based on Transformer, which can efficiently convert speech into text. Specifically, first, the voice inspection note information is preprocessed, such as noise reduction and enhancement, to improve the recognition accuracy. Then, the preprocessed voice inspection note information is input into the Whisper model to obtain the text inspection note information. Then, the text inspection note information is spell-checked and grammar-corrected to ensure the accuracy and readability of the text. Then, according to the metadata of the voice inspection note information (such as the operator, timestamp, tower crane number, tower crane component number, etc.), the corresponding inspection log node is found in the graph database, and the transcribed text inspection note information is inserted into the corresponding inspection log node. If the inspection log node already exists, the text inspection note information is appended to the existing content, and if the inspection log node does not exist, a new inspection log node is created and the text inspection note information is inserted. Finally, the attributes of the inspection log node are updated, including the operation time, operator, operation content, etc., to ensure the integrity and consistency of the inspection log. Through the above steps, the voice shorthand sub-module 116 realizes efficient conversion from voice collection to text recording, and ensures the integrity and traceability of the data, providing important support for data integration of the tower crane inspection data management system.

[0074] In one possible implementation, the report generation module 120 includes:

[0075] The dynamic template sub-module 121 is configured to initiate rendering instructions based on the daily briefing, file format, and globally unique event identifier when the Quartz timer detects a timed wake-up event, and initiate rendering instructions based on the special report, file format, and globally unique event identifier when the Webhook receiver detects an abnormal threshold event.

[0076] The intelligent layout sub-module 122 is configured to pull subgraph data from the graph database based on the globally unique event identifier in the rendering instruction when the rendering instruction is received, and sequentially perform content verification, standard matching, and warning visualization processing on the subgraph data to obtain various intermediate rendering objects.

[0077] In the embodiments of the present application, the Quartz timer is used to trigger tasks at specified time points, for example, in the tower crane inspection data management system, the Quartz timer is configured to automatically trigger a task once a day at 18:00, and the task content is: when the Quartz timer triggers, the dynamic template submodule 121 detects the timing wake-up event, and initiates the rendering instruction based on the daily briefing template, the file format (such as PDF, Excel, web version selected by the user or defaulted by the system) and the globally unique event identifier Event-ID. The Webhook receiver is used to send a notification to a specified URL when a specific event occurs, for example, in the tower crane inspection data management system, the Webhook receiver triggers a task once when it detects an abnormal threshold event (such as deviation of verticality, crack propagation, etc.), and the task content is: when the Webhook receiver detects an abnormal threshold event, the dynamic template submodule 121 detects an abnormal wake-up event, and initiates a rendering instruction based on the special report template, the file format (such as PDF, Excel, web version selected by the user or defaulted by the system) and the globally unique event identifier Event-ID. After the intelligent layout submodule 122 receives the rendering instruction from the dynamic template submodule 121, it parses the globally unique event identifier Event-ID in the rendering instruction, and based on the globally unique event identifier Event-ID, it pulls the subgraph data related to the event represented by the globally unique event identifier Event-ID from the graph database (including defect record nodes, inspection image nodes, inspection log nodes, etc.). After the pulled subgraph data is checked for integrity, it is ensured that all necessary fields (such as defect records, inspection image paths, inspection log contents, etc.) exist and are in the correct format, and for defect records with a standard hazard level of III and above, a red warning box is drawn on the inspection image corresponding to the defect record. The data that has undergone the above content verification, standard matching and warning visualization processing is packaged into an intermediate rendering object for use by the subsequent file output module 130.

[0078] In one possible implementation, the file output module 130 includes:

[0079] The PDF report submodule 131 is used to generate daily briefings and / or special reports in PDF format as tower crane inspection data reports based on various intermediate rendering objects through the iText7 library;

[0080] The Excel report submodule 132 is used to generate daily briefings and / or special reports in Excel format as tower crane inspection data reports based on various intermediate rendering objects through Apache POI;

[0081] The web version report submodule 133 is configured to generate a daily briefing and / or a special report in the form of a web page based on the intermediate rendering objects by Three.js as the tower crane inspection data report.

[0082] In the embodiments of the present application, the PDF report uses the iText7 library to generate a PDF file from the intermediate rendering objects and embeds a digital signature and LTV verification information; the Excel report uses Apache POI to generate an Excel file from the intermediate rendering objects and supports secondary analysis; and the web version report uses Three.js to generate an interactive three-dimensional visualization web page from the intermediate rendering objects and completes user authentication through JWT. Subsequently, the integrity of the intermediate rendering objects is verified by recalculating the hash value, and the original data in the graph database is quickly located through the globally unique event identifier EventID, thereby ensuring the traceability of the tower crane inspection data report. Through the above process, the full-process automation from event triggering to report generation is realized, thereby ensuring the accuracy and consistency of the tower crane inspection data report.

[0083] In a possible implementation, the file output module 130 is further configured to acquire current meteorological data such as wind speed, temperature, humidity, etc. from a meteorological data system, adjust the weight of the standard risk level of each defect record based on the current meteorological data, and then adjust the standard risk level of each defect record based on the weight of the standard risk level of each defect record, wherein the weight of the standard risk level is increased when the wind speed is greater than a wind speed threshold, for example, the weight is increased by 0.2 when the wind speed is greater than 5 m / s; the weight of the standard risk level is increased when the ambient temperature is greater than a first temperature threshold or less than a second temperature threshold (the second temperature threshold is less than the first temperature threshold), for example, the weight is increased by 0.1 when the ambient temperature is less than 0°C or greater than 35°C; the weight of the standard risk level is increased when the ambient humidity is greater than a humidity threshold, for example, the weight is increased by 0.1 when the ambient humidity is greater than 80%; and then a meteorologically sensitive version of the tower crane inspection data report is generated based on the adjusted standard risk level of each defect record, so that the safety risk under the current environment can be more accurately reflected through dynamic adjustment.

[0084] In a possible implementation, the file output module 130 is further configured to extract the current defect records of each tower crane component from the graph database, including but not limited to defect location (longitude, latitude, and elevation), standard hazard level, and the like, convert the current defect records of each tower crane component into a heat map representing the density and hazard level of the defects by color depth using a geographic information system tool (such as Leaflet.js or Mapbox) or a data visualization library (such as D3.js), convert the heat map into a real-time defect heat map code by encoding, for example, save the heat map as a PNG or JPEG image, or save the heat map as a GIF or video format to support dynamic display, or convert the heat map into a Base64 encoded string to facilitate embedding into a web page or mobile application, and then push the real-time defect heat map code to the mobile terminal lock screen of the manager as a dynamic wallpaper for display through a push service (such as Firebase Cloud Messaging). Through the above process, a high-quality real-time defect heat map can be generated, and the manager can be reminded to pay attention to potential problems of the tower crane in a timely manner, thereby providing strong support for the maintenance and management of the tower crane.

[0085] In a possible implementation, the tower crane inspection data management system 100 provided by the present application further includes:

[0086] The maintenance work order generation module 140 is configured to parse the standard hazard level of each tower crane component from the tower crane inspection data report, create a maintenance work order by calling the application program interface of the ERP system based on the standard hazard level of each tower crane component, and associate the maintenance work order with the tower crane inspection data report.

[0087] In the embodiments of the present application, after the maintenance work order generation module 140 creates a maintenance work order by calling the application program interface of the ERP system, a maintenance work order node can also be created and associated with the defect record node to facilitate tracing the maintenance of the defect, wherein the maintenance work order node MaintenanceOrder (if any) has the following attributes: OrderID: unique identifier of the maintenance work order; DefectID: associated defect identifier; Status: work order status (such as “to be processed”, “completed”, etc.); AssignedTo: assigned maintenance personnel; CreateTime: work order creation time; CompleteTime: work order completion time; and purpose: to represent the maintenance work order of the defect, and to be associated with the defect node to facilitate tracing the maintenance of the defect.

[0088] In a possible implementation, the tower crane inspection data management system 100 provided by the present application further includes:

[0089] The multilingual support module 150 is configured to output the tower inspection data report into a multilingual tower inspection data report by using an LLM translation model.

[0090] In the embodiments of the present application, the core function of the multilingual support module 150 is to output the tower inspection data report into a report in multiple languages to meet the needs of different users. The multilingual support module 150 uses an LLM translation model such as ChatGLM-6B, GPT-3, etc., which can ensure the accuracy and naturalness of the translation.

[0091] In one possible implementation, the tower inspection data management system 100 provided by the present application further comprises:

[0092] The health curve generation module 160 is configured to analyze the tower inspection data report and historical tower inspection data by using an LSTM time series prediction model to generate a tower health curve.

[0093] In the embodiments of the present application, the core function of the health curve generation module 160 is to generate a tower health curve by analyzing the tower inspection data report and historical tower inspection data. The health curve generation module 160 uses an LSTM time series prediction model, which can effectively process time series data and capture long-term dependencies, thereby effectively predicting the health status of the tower. Further, the historical defect record data of multiple towers can be used as nodes to construct a graph neural network. The graph neural network can be used to predict the group failure probability of the entire group of towers in a future set period of time (for example, one week in the future) and generate a group failure probability curve, thereby providing prediction and analysis of the health status and group failure probability of the tower, and providing strong support for the maintenance and management of the tower.

[0094] Based on the above embodiments, the present application provides a tower inspection data management method applied to an electronic device such as a computer, a mobile phone, a tablet computer, etc. equipped with the tower inspection data management system described above. Referring to Figure 2 The general process of the tower inspection data management method provided by the present application is as follows:

[0095] Step 201: synchronizing the inspection results and inspection images of each tower component of the inspection task from the edge computing terminal in real time and synchronizing the inspection log of the inspection task from the inspection handheld terminal in real time.

[0096] Step 202: integrating the inspection log of the inspection task and the inspection results and inspection images of each tower component into a graph database.

[0097] Step 203: based on the different report type associated trigger events, when any report type associated trigger event is triggered, a tower inspection data report is generated based on the graph database by using the report template corresponding to any report type.

[0098] Step 204: the tower inspection data report is exported in a target file format.

[0099] It should be noted that the above tower inspection data management method provided by the embodiments of the present application solves the technical problems by the similar principle as the above tower inspection data management system provided by the embodiments of the present application, and therefore, the implementation of the above tower inspection data management method provided by the embodiments of the present application can be referred to the implementation of the above tower inspection data management system provided by the embodiments of the present application, and the repeated parts will not be described herein.

[0100] Next, the electronic device provided by the embodiments of the present application is briefly introduced. The electronic device can be a computer, a tablet computer, a mobile phone, or the like tower inspection data management device, as shown in Figure 3 The electronic device 300 provided by the embodiments of the present application at least includes a processor 301, a memory 302, and a computer program stored in the memory 302 and executable on the processor 301, and the processor 301 executes the computer program to implement the tower inspection data management method provided by the embodiments of the present application.

[0101] The electronic device 300 provided by the embodiments of the present application can further include a bus 303 connecting different components (including the processor 301 and the memory 302). Among them, the bus 303 represents one or more of several types of bus structures, including a memory bus, a peripheral bus, a local bus, etc.

[0102] The memory 302 can include a readable medium in the form of a volatile memory, such as a random access memory (RAM) 3021 and / or a cache memory 3022, and can further include a read-only memory (ROM) 3023. The memory 302 can also include a program tool 3025 having a set of (at least one) program modules 3024, including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination thereof can include the implementation of a network environment.

[0103] The processor 301 can be one processing element or a collective name of multiple processing elements. For example, the processor 301 can be a microcontroller unit (MCU), or a central processing unit (CPU), or one or more integrated circuits configured to implement the tower crane inspection data management method provided in the embodiments of the present application. Specifically, the processor 301 can be a general-purpose processor, including but not limited to a CPU, an application specific integrated circuit (ASIC), a ready-to-program gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc.

[0104] The electronic device 300 can also communicate with one or more devices that enable a user to interact with the electronic device 300 (for example, a mobile phone, a computer, etc.), and / or with various external devices 304 that enable the electronic device 300 to communicate with one or more other electronic devices (for example, a router, a modem, etc.). Such communication can be carried out through an input / output (I / O) interface 305. In addition, the electronic device 300 can also communicate with one or more networks (for example, a local area network (LAN), a wide area network (WAN), and / or a public network such as the Internet) through a network adapter 306. As shown, the network adapter 306 communicates with other modules of the electronic device 300 through the bus 303. It should be understood that although Figure 3 the network adapter 306 is shown as a separate component, the network adapter 306 can be incorporated as a part of the processor 301 or the bus 303. Figure 3 It should be understood that although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 300, including but not limited to microcode, device drivers, redundant processors, external disk drive arrays, redundant arrays of independent disks (RAID) subsystems, tape drives, and data backup storage subsystems, etc.

[0105] It should be noted that the electronic device 300 shown is merely an example, and should not impose any limitation on the functions and use range of the embodiments of the present application. Figure 3 It should be noted that the electronic device 300 shown is merely an example, and should not impose any limitation on the functions and use range of the embodiments of the present application.

[0106] In addition, the embodiment of the present application further provides a computer readable storage medium, which stores computer instructions. The computer instructions are executed by a processor to implement the tower crane inspection data management method provided by the embodiment of the present application. Specifically, the computer instructions can be built-in or installed in the processor. Thus, the processor can implement the tower crane inspection data management method provided by the embodiment of the present application by executing the built-in or installed computer instructions.

[0107] Furthermore, the tower crane inspection data management method provided by the embodiment of the present application can also be implemented as a program product. The program product includes program codes. The program codes are executed by a processor to implement the tower crane inspection data management method provided by the embodiment of the present application.

[0108] The program product provided by the embodiment of the present application can adopt any combination of one or more readable media. Specifically, the readable media can be a readable signal medium or a readable storage medium. The readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. More specifically, the readable storage medium includes, but is not limited to, an electrical connection having one or more wires, a portable disk, a hard disk, a RAM, a ROM, an erasable programmable read-only memory (EPROM), an optical fiber, a portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0109] The program product provided by the embodiment of the present application can adopt a CD-ROM and include program codes, and can also run on an electronic device. However, the program product provided by the embodiment of the present application is not limited to this. In the embodiment of the present application, the readable storage medium can be any tangible medium containing or storing programs, which can be used by or in combination with an instruction execution system, device or component.

[0110] It should be noted that, although several units or sub-units of the device are mentioned in the above detailed description, such division is merely exemplary and not mandatory. In fact, according to the embodiment of the present application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided into units embodied by multiple units.

[0111] Furthermore, although the operations of the method(s) herein can be described in a particular, sequential order, this order is not meant to be a limitation and one or more of the operations described can be performed in parallel, or in a different order, including before or after other operations described. The various steps described can be implemented in hardware, software, or a combination thereof. The subject specification can be implemented by computer software implemented by one or more processors of a computing device.

[0112] While the preferred embodiments of the application have been described above, it should be understood that they have been presented by way of example only, and not limitation. Numerous changes to the embodiments can be made in addition to those described and nevertheless accomplish the same objectives of the application. Thus, while the application is susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in order to elucidate the application. It should be understood, therefore, that the application is not to be limited to the particular embodiments described but it is intended to cover any and all modifications and equivalents within the scope of the appended claims.

[0113] Obviously, numerous modifications and variations of the present application are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims, the application can be practiced otherwise than as specifically described herein.

Claims

1. A tower inspection data management system, characterized in that, The method comprises the following steps: a data integration module is used to synchronize the inspection results and inspection images of each tower component of a real-time inspection task from an edge computing terminal and the inspection log of the inspection task from an inspection handheld terminal; the inspection log of the inspection task and the inspection results and inspection images of each tower component are integrated into a graph database; a report generation module is used to monitor the triggering of any report type associated triggering event based on different report type associated triggering events, and when any report type associated triggering event is triggered, generate a tower crane inspection data report based on the graph database by using the report template corresponding to the report type; a file output module is used to export the tower crane inspection data report in a target file format; wherein the data integration module comprises: an inspection result recording submodule for splicing and hash processing the tower crane number, tower component number, automatic inspection timestamp and random number corresponding to each tower component within a set time window to obtain a globally unique defect identifier for each tower component; converting the defect position in the inspection result of each tower component from a pixel-level coordinate system to a tower crane coordinate system and then to a geodetic coordinate system to obtain the defect position of each tower component in the geodetic coordinate system; mapping the defect category, defect confidence and defect physical quantity in the inspection result of each tower component to a standard hazard level; converting the inspection result of each tower component into natural language to obtain defect description data for each tower component; encapsulating the defect position in the geodetic coordinate system, standard hazard level and defect description data of each tower component as a defect record; and constructing a tower crane node, a tower component node, a defect type node and a defect record node based on the tower crane number, tower component number, automatic inspection timestamp, globally unique defect identifier, defect position in the geodetic coordinate system, standard hazard level, defect description data and defect record; an inspection image recording submodule for extracting the metadata of each inspection image of each tower component within a set time window, and generating a unique fingerprint for each inspection image of each tower component based on the metadata of each inspection image of each tower component using a perceptual hash algorithm; performing deduplication processing on each inspection image of each tower component based on the unique fingerprint of each inspection image of each tower component; physically archiving and generating a storage path for each deduplicated inspection image of each tower component according to the directory structure of the tower crane, shooting timestamp, tower component and image type; generating a thumbnail and access link for each deduplicated inspection image of each tower component; and constructing an inspection image node based on the unique fingerprint, storage path, thumbnail and access link of each deduplicated inspection image of each tower component; an inspection log recording submodule for splitting each inspection log of the inspection task within a set time window into five elements including an inspection personnel, a manual inspection timestamp, an inspection tower crane and tower component, an inspection operation and an inspection result; splicing and hash processing the five elements of each inspection log to obtain a unique identifier for each inspection log; and constructing an inspection log node based on the unique identifier and five elements of each inspection log. The subgraph generation submodule is configured to construct edge relationships among nodes to form subgraph data based on the tower crane nodes, the tower component nodes, the defect type nodes, the defect record nodes, the inspection image nodes, and the inspection log nodes within a set time window. The inspection event aggregation submodule is configured to pack the subgraph data within a set time window into an inspection event, and generate a globally unique event identifier for the inspection event.

2. The tower crane inspection data management system of claim 1, wherein, The data integration module further includes: The voice shorthand submodule is configured to convert voice inspection note information synchronized in real time from the inspection handheld terminal into text inspection note information by using a Whisper model, and insert the text inspection note information into a corresponding inspection log.

3. The tower crane inspection data management system of claim 1, wherein, The report generation module includes: The dynamic template submodule is configured to initiate a rendering instruction based on the daily briefing, the file format, and the globally unique event identifier when a timing wake-up event is detected by a Quartz timer, and initiate a rendering instruction based on the special report, the file format, and the globally unique event identifier when an abnormal threshold event is detected by a Webhook receiver; The intelligent layout submodule is configured to pull subgraph data from the graph database based on the globally unique event identifier in the rendering instruction when the rendering instruction is received, and sequentially perform content verification, standard matching, and warning visualization processing on the subgraph data to obtain various intermediate rendering objects.

4. The tower crane inspection data management system of claim 3, wherein, The file output module includes: The PDF report submodule is configured to generate a PDF format daily briefing and / or special report as the tower crane inspection data report based on the various intermediate rendering objects by using an iText7 library; The Excel report submodule is configured to generate an Excel format daily briefing and / or special report as the tower crane inspection data report based on the various intermediate rendering objects by using an Apache POI; The web version report submodule is configured to generate a web form daily briefing and / or special report as the tower crane inspection data report based on the various intermediate rendering objects by using a Three.js.

5. The tower crane inspection data management system of claim 1, wherein, Further includes: The maintenance work order generation module is configured to parse standard danger level of each tower component from the tower crane inspection data report, call an application programming interface of an ERP system to create a maintenance work order based on the standard danger level of each tower component, and associate the maintenance work order with the tower crane inspection data report.

6. The tower crane inspection data management system of claim 1, wherein, Further includes: The multi-language support module is configured to output the tower crane inspection data report as a multi-language tower crane inspection data report by using an LLM translation model.

7. A tower inspection data management method, characterized in that, Applied to the tower crane inspection data management system of any one of claims 1-6, comprising: synchronizing inspection results and inspection images of each tower component of an inspection task in real time from an edge computing terminal and synchronizing inspection logs of the inspection task in real time from an inspection handheld terminal; integrating the inspection logs of the inspection task and the inspection results and inspection images of each tower component into a graph database; Based on the trigger events associated with different report types, when any report type associated trigger event is triggered, the report template corresponding to the report type is adopted, and the tower inspection data report is generated based on the graph database; The tower inspection data report is exported in a target file format; The inspection log of the inspection task and the inspection results and inspection images of each tower component are integrated into a graph database, including: The tower number, tower component number, automatic inspection timestamp, and random number corresponding to each tower component in a set time window are spliced and hashed to obtain a globally unique defect identifier for each tower component. The defect position in the inspection result of each tower component is converted from the pixel-level coordinate system to the tower coordinate system and then to the geodetic coordinate system to obtain the defect position of each tower component in the geodetic coordinate system. The defect category, defect confidence, and defect physical quantity in the inspection result of each tower component are mapped to a standard hazard level. The inspection result of each tower component is converted into natural language to obtain defect description data for each tower component. The defect position in the geodetic coordinate system, the standard hazard level, and the defect description data of each tower component are encapsulated as a defect record. Based on the tower number, tower component number, automatic inspection timestamp, globally unique defect identifier, defect position in the geodetic coordinate system, standard hazard level, defect description data, and defect record, a tower node, a tower component node, a defect type node, and a defect record node are constructed. The metadata of each inspection image of each tower component in a set time window is extracted, and based on the metadata of each inspection image of each tower component, a unique fingerprint is generated for each inspection image of each tower component using a perceptual hashing algorithm. Each inspection image of each tower component is processed for deduplication based on the unique fingerprint of each inspection image of each tower component. The deduplicated inspection images of each tower component are physically archived and a storage path is generated according to the directory structure of the tower, the shooting timestamp, the tower component, and the image type. A thumbnail and an access link are generated for each deduplicated inspection image of each tower component. Based on the unique fingerprint, storage path, thumbnail, and access link of each deduplicated inspection image of each tower component, a inspection image node is constructed. Each inspection log in the set time window is split into five elements including the inspection personnel, manual inspection timestamp, inspection tower and tower component, inspection operation, and inspection result. The unique identifier of each inspection log is obtained by splicing and hashing the five elements of each inspection log. Based on the unique identifier and the five elements of each inspection log, an inspection log node is constructed. Based on the tower node, tower component node, defect type node, defect record node, inspection image node, and inspection log node in the set time window, the edge relationship between the nodes is constructed to form a subgraph data. Packaging the subgraph data in a set time window as a patrol inspection event, and generating a globally unique event identifier for the patrol inspection event; wherein all subgraph data in the set time window constitutes the graph database.

8. An electronic device, comprising: The computer readable storage medium stores computer instructions, and the computer instructions are executed by the processor to implement the tower crane patrol inspection data management method of claim 7.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions, and the computer instructions are executed by the processor to implement the tower crane patrol inspection data management method of claim 7.

Images