Urban management method and system

Abstract

The invention discloses a city management method and system. The city management method comprises the following steps: constructing a city component facility management platform; carrying out collection field self-definition based on an urban component facility management platform; after the collection field self-definition is completed, part information is collected in real time; performing data processing on the part information acquired in real time; and performing intelligent management according to the processed component information. According to the invention, by constructing a dynamic and precise urban part facility management system, the management cost is significantly reduced, the management efficiency is greatly improved, and the disposal period is shortened. And meanwhile, the accuracy and timeliness of the data are improved by further processing the data. And the safe operation of the facility is ensured by timely repairing the components.

Description

Technical Field

[0001] This application relates to the field of data processing, and more specifically, to an urban management method and system thereof. Background Technology

[0002] Urban component facility management is a core task of municipal infrastructure construction, directly impacting urban operational efficiency and the quality of life for citizens. Currently, traditional urban component management mainly relies on periodic manual surveys, with the following specific methods: Data collection method: Professional surveying companies are commissioned to centrally collect data on urban components using specialized equipment such as RTK and total stations, establishing a static database based on Ministry of Housing and Urban-Rural Development standards to record component location, basic attributes, and other information; Management platform functions: Most municipal management systems are centered on static databases, only supporting basic component location queries and attribute displays, lacking dynamic updates or intelligent application functions. However, traditional management methods have significant drawbacks: Poor data timeliness: Centralized surveys require restarting the surveying process for data updates, with update cycles lasting 1-3 years, resulting in databases being "built but idle," failing to reflect dynamic changes in urban components; Inaccurate ownership association: Static databases cannot directly bind component ownership units and management units, leading to ambiguous maintenance responsibilities and delays in handling faulty components; Limited functionality: Lacking practical functions such as intelligent inspection, case reporting, and navigation positioning, relying on manual experience for management work, resulting in low efficiency; High maintenance costs: Relying on third-party companies for regular surveys requires significant investment of manpower and funds.

[0003] Therefore, how to provide an intelligent, efficient, and low-cost urban management method has become an urgent problem to be solved in this field. Summary of the Invention

[0004] To address the aforementioned issues, this application proposes an urban management method comprising the following steps: constructing an urban component and facility management platform; customizing data collection fields based on the urban component and facility management platform; collecting component information in real time after completing the custom data collection fields; processing the real-time collected component information; and performing intelligent management based on the processed component information.

[0005] The urban management method described above includes constructing an urban component and facility management platform based on a personalized field configuration engine, geographic information technology, mobile internet technology, and GPS positioning technology.

[0006] The urban management method described above includes customizing the data collection fields by setting 16 standard fields, including text, numeric, date, image, coordinate, and enumeration types, and synchronizing the field templates to the mobile terminals of the corresponding ownership units.

[0007] The urban management method described above includes the following sub-steps for real-time collection of component information: determining the type of component to be managed; performing real-time positioning and basic information entry; binding ownership information; supplementing personalized information; and submitting data.

[0008] The urban management method described above, wherein intelligent management based on the processed component information includes performing location queries and selecting precise or fuzzy queries by inputting component information.

[0009] An urban management system includes: a management platform construction unit, a data collection field customization unit, a real-time data collection unit, a data processing unit, and an intelligent management unit. The management platform construction unit is used to construct an urban component and facility management platform. The data collection field customization unit is used to customize data collection fields based on the urban component and facility management platform. The real-time data collection unit is used to collect component information in real time after the data collection fields are customized. The data processing unit is used to process the real-time collected component information. The intelligent management unit is used to perform intelligent management based on the processed component information.

[0010] As described above, in the urban management system, the construction of the urban component facility management platform by the management platform construction unit includes the construction of the management platform based on personalized field configuration engine, geographic information technology, mobile Internet technology and GPS positioning technology.

[0011] In the urban management system described above, the field customization unit allows for the customization of data collection fields, including setting 16 standard fields such as text, numeric, date, image, coordinate, and enumeration types, and synchronizing the field templates to the mobile terminals of the corresponding ownership units.

[0012] In the urban management system described above, the real-time data collection unit collects component information in real time, including the following sub-steps: determining the type of component under management; performing real-time positioning and basic information entry; binding ownership information; supplementing personalized information; and submitting data.

[0013] In the urban management system described above, the intelligent management unit performs intelligent management based on the processed component information, including location query and selecting precise query or fuzzy query by inputting component information.

[0014] This application has the following beneficial effects: This application significantly reduces management costs, greatly improves management efficiency, and shortens the response cycle by constructing a dynamic and precise urban component facility management system. Simultaneously, further data processing enhances data accuracy and timeliness, strengthening the foundation for decision-making. Timely reporting of component repairs ensures the safe operation of the facilities. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0016] Figure 1 This is a flowchart illustrating the urban management method provided according to an embodiment of this application; Figure 2 This is a schematic diagram of the internal structure of an urban management system provided according to an embodiment of this application. Detailed Implementation

[0017] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0018] Example 1 like Figure 1 As shown, this embodiment provides a city management method, which specifically includes the following steps: Step S1: Construct an urban component facility management platform.

[0019] Based on a personalized field configuration engine, geographic information technology (GIS), mobile internet technology, and GPS positioning technology, a three-tier management platform architecture of "data acquisition layer - data processing layer - application layer" is constructed.

[0020] The data acquisition layer deploys mobile terminal applications (for use by personnel of affiliated units), integrates GPS positioning functions, and supports on-site information entry and photo uploading; The data processing layer is configured with a GIS server, a data verification module, and a database storage unit for data reception, format verification, coordinate association, and real-time storage. At the application layer, we developed a "component management map", a case reporting work order system, a navigation module, and a special inspection statistics module, providing a visual operation interface.

[0021] The process of developing an urban component and facility management platform also includes binding ownership and defining responsibilities.

[0022] Step S2: Based on the urban component facility management platform, customize the data collection fields.

[0023] It includes 16 standard field types (including text, numeric, date, image, coordinate, and enumeration types) to cover the basic attribute requirements of city components (such as "component location", "status", and "installation date").

[0024] Furthermore, the ownership units of the components independently identify management needs and customize exclusive fields.

[0025] For example, the municipal department has added fields such as "well depth", "well cover material" and "cleaning cycle" for storm drains; the street light management office has added fields such as "power", "lighting duration" and "maintenance record" for street lights. Once configured, the field templates are synchronized to the mobile terminal (APP) of the corresponding ownership unit for use during data collection.

[0026] Step S3: After completing the customization of the collection fields, collect component information in real time.

[0027] The information collection is carried out by maintenance personnel (non-professional surveyors) from the ownership unit, who carry mobile terminals (phones / tablets) equipped with the data collection APP, during routine inspections or maintenance sites.

[0028] During the data collection process, users first log in to the mobile terminal APP using the exclusive account of the ownership unit, and the system automatically associates the types of components that the unit can manage.

[0029] Step S3 includes the following sub-steps: Step S31: Determine the type of component to be managed.

[0030] When users log in to the APP using their exclusive account, the system automatically verifies the binding relationship between the account and permissions, and automatically associates the types of components that the entity can manage.

[0031] Step S32: Perform real-time positioning and basic information entry.

[0032] The GPS automatically acquires the coordinates of the currently collected component location, and the component type is selected, and basic information is filled in.

[0033] The component types include manhole covers and streetlights, and the basic information includes whether the condition is faulty or normal.

[0034] Real-time positioning enables both precise and fuzzy search capabilities in subsequent practical applications.

[0035] Precise Query: Combining GPS positioning and GIS electronic map, you can directly locate the component by entering the component ID or keywords (such as "XX Road rainwater well") and simultaneously display complete attributes (including ownership unit, responsible person, and personalized fields such as "well depth" and "material"), without the need to manually flip through paper ledgers or switch between multiple systems.

[0036] Fuzzy search: Allows inspectors to view the distribution of all components within a 50-meter radius of their current location, and can also filter by "fault / normal" status, reducing reliance on the inspectors' experience and providing accurate location guidance for subsequent inspections and handling.

[0037] Step S33: Bind ownership information.

[0038] Determine the ownership information of the currently logged-in unit, including but not limited to the unit name, responsible person, and contact number.

[0039] For ownership information, manual correction is supported in ownership adjustment scenarios.

[0040] Step S34: Supplement personalized information.

[0041] Enter customized data according to the pre-configured fields, such as "well depth 2 meters" for rainwater wells, and upload on-site photos for visual verification.

[0042] Step S35: Submit the data.

[0043] Step S4: Process the real-time collected component information.

[0044] Data processing specifically includes using GIS technology to link spatial information to achieve data-space correlation, solving the problem of data collection being disconnected from location in traditional technologies, while also supporting dynamic data updates to solve the problem of lagging data updates in traditional methods.

[0045] Step S4 includes the following sub-steps:

[0046] Step S41: Automatically verify the real-time collected component information.

[0047] After receiving the collected data, the data processing layer triggers an automatic verification process. The verification criteria include: Integrity check: No non-empty fields (such as "part type" and "ownership unit") are missing; Format validation: Numeric fields (such as "well depth") conform to the numeric format, and telephone fields conform to the 11-digit mobile phone number rule; Uniqueness check: No duplicate component IDs (to prevent the same component from being entered multiple times); Ownership conflict verification: If the collected ownership information conflicts with the system's preset scope of responsibility (e.g., unit A enters the component that unit B is responsible for), an "ownership conflict" warning will be triggered.

[0048] If all the above checks pass, proceed to step S42.

[0049] If one or more of the above checks fail, the component information will be marked as "pending review" and sent to the city management command center for verification by staff.

[0050] As an example, if there is a conflict of ownership during the verification process, the staff will organize the ownership determination (such as holding a coordination meeting to clarify the responsible unit), and after the determination, the correct ownership unit will re-enter or correct the information.

[0051] Step S42: Perform data storage and map update.

[0052] The verified component information is synchronously stored in the GIS database, and the component's basic attributes, ownership information, and personalized fields are updated.

[0053] All data collected by the ownership units through mobile terminals (including basic attribute data such as component location / type, ownership data such as unit name / responsible person, personalized data such as rainwater well "depth" / street light "power", and multimedia data such as on-site photos) will be uniformly stored in the GIS database to avoid data being scattered across different carriers or systems.

[0054] In another embodiment of the present invention, node selection is used to store component information to prevent data loss due to abnormal storage of the GIS database.

[0055] This includes the following sub-steps: Step S421: Determine the multiple criteria for node selection.

[0056] These multiple indicators include node degree, connection strength, and importance.

[0057] Node degree characterizes the importance of a node in terms of its local importance, calculates the number of a node's neighbors, and reflects the degree of influence a node has on its surrounding neighbors.

[0058] Connection strength characterizes the importance of a node in terms of the importance of its relationships with other nodes. It calculates the sum of the communication frequencies between a node and other nodes, reflecting the node's ability to spread messages in a local area.

[0059] Central domain importance characterizes the importance of a node from the perspective of its global importance, reflecting the degree to which a node is located at the center of the network.

[0060] Understandably, multiple nodes form a network topology, where any node... node degree Represented as: ; in Represents any node The neighborhood of the node, that is, the neighborhood of the node The set of adjacent nodes, b is The adjacent nodes, This represents the node degree of b.

[0061] any node Connection strength Represented as: ; in Represents a node The weight of the edge connecting node b.

[0062] At the node neighborhood In the equation, the neighborhoods of any two nodes h and j are respectively... , Define nodes The central domain is , express No two nodes in the middle are connected by any means. The number of shortest paths, express Passing between any pair of nodes The number of shortest paths, let The node degree is , Middle node The length to node b is Then any node Central domain importance Represented as: ; in .

[0063] Nodes whose node degree, connection strength, and central domain importance are all greater than a specified threshold are selected as nodes for storing component information.

[0064] Understandably, the specified thresholds for node degree, connection strength, and central domain importance can be set separately, and nodes whose node degree, connection strength, and central domain importance are all greater than the corresponding specified thresholds are selected as nodes for storing component information.

[0065] Step S422: Select nodes for component information storage based on multiple indicators.

[0066] Furthermore, the component location coordinates are linked to an electronic map to generate visual markers. These visual markers include component type icons and ownership unit identifiers.

[0067] Furthermore, the updated component information is simultaneously synchronized to the application layer and pushed to relevant management departments for querying and access.

[0068] Step S5: Perform intelligent management based on the processed component information.

[0069] The following are specific application examples of intelligent management achieved through the methods described above: Using the location query function, users can select precise query by inputting component information to confirm the component's location and attributes, or perform a fuzzy query to confirm the distribution of components within a specified range. When inspection personnel discover a component malfunction, they report the case through the PointCollection APP. The APP automatically associates with component information in the vicinity of the current location. The fault type is selected, and on-site photos are uploaded. An automatic work order is generated, containing component ownership, location, and fault description. The work order is directly dispatched to the corresponding ownership unit. The personnel handling the issue receive the work order through the APP, use GPS navigation to locate the faulty component, and perform repairs. After completion, repair photos are uploaded, the work order status is updated to "processed," and the information is archived on the management platform.

[0070] Furthermore, relevant management departments can also issue special inspection tasks for components, specifying the inspection scope and completion deadline.

[0071] For example, when a "Rainwater Well Cleaning Project" is issued, maintenance personnel mark the wells as "cleaned" in the app after completing the cleaning. The system then tracks the progress in real time and generates a visual report.

[0072] Preferably, the system supports exporting inspection records, which include time, personnel, and component status, for use in performance evaluation and management review.

[0073] Example 2 like Figure 2 As shown in the figure, an urban management system provided in this application embodiment specifically includes: a management platform construction unit 210, a data collection field customization unit 220, a real-time data collection unit 230, a data processing unit 240, and an intelligent management unit 250.

[0074] The management platform construction unit 210 is used to construct the urban component facility management platform.

[0075] Based on a personalized field configuration engine, geographic information technology (GIS), mobile internet technology, and GPS positioning technology, a three-tier management platform architecture of "data acquisition layer - data processing layer - application layer" is constructed.

[0076] The data acquisition layer deploys mobile terminal applications (for use by personnel of affiliated units), integrates GPS positioning functions, and supports on-site information entry and photo uploading; The data processing layer is configured with a GIS server, a data verification module, and a database storage unit for data reception, format verification, coordinate association, and real-time storage. At the application layer, we developed a "component management map", a case reporting work order system, a navigation module, and a special inspection statistics module, providing a visual operation interface.

[0077] The process of developing an urban component and facility management platform also includes binding ownership and defining responsibilities.

[0078] The data collection field customization unit 220 is used to customize data collection fields based on the urban component facility management platform.

[0079] It includes 16 standard field types (including text, numeric, date, image, coordinate, and enumeration types) to cover the basic attribute requirements of city components (such as "component location", "status", and "installation date").

[0080] Furthermore, the ownership units of the components independently identify management needs and customize exclusive fields.

[0081] For example, the municipal department has added fields such as "well depth", "well cover material" and "cleaning cycle" for storm drains; the street light management office has added fields such as "power", "lighting duration" and "maintenance record" for street lights. Once configured, the field templates are synchronized to the mobile terminal (APP) of the corresponding ownership unit for use during data collection.

[0082] The real-time acquisition unit 230 is used to acquire component information in real time after the acquisition fields are customized.

[0083] The information collection is carried out by maintenance personnel (non-professional surveyors) from the ownership unit, who carry mobile terminals (phones / tablets) equipped with the data collection APP, during routine inspections or maintenance sites.

[0084] During the data collection process, users first log in to the mobile terminal APP using the exclusive account of the ownership unit, and the system automatically associates the types of components that the unit can manage.

[0085] The real-time acquisition unit 230 performs the following sub-steps: Step E1: Determine the type of component to be managed.

[0086] When users log in to the APP using their exclusive account, the system automatically verifies the binding relationship between the account and permissions, and automatically associates the types of components that the entity can manage.

[0087] Step E2: Perform real-time positioning and basic information entry.

[0088] The GPS automatically acquires the coordinates of the currently collected component location, and the component type is selected, and basic information is filled in.

[0089] The component types include manhole covers and streetlights, and the basic information includes whether the condition is faulty or normal.

[0090] Real-time positioning enables both precise and fuzzy search capabilities in subsequent practical applications.

[0091] Precise Query: Combining GPS positioning and GIS electronic map, you can directly locate the component by entering the component ID or keywords (such as "XX Road rainwater well") and simultaneously display complete attributes (including ownership unit, responsible person, and personalized fields such as "well depth" and "material"), without the need to manually flip through paper ledgers or switch between multiple systems.

[0092] Fuzzy search: Allows inspectors to view the distribution of all components within a 50-meter radius of their current location, and can also filter by "fault / normal" status, reducing reliance on the inspectors' experience and providing accurate location guidance for subsequent inspections and handling.

[0093] Step E3: Bind ownership information.

[0094] Determine the ownership information of the currently logged-in unit, including but not limited to the unit name, responsible person, and contact number.

[0095] For ownership information, manual correction is supported in ownership adjustment scenarios.

[0096] Step E4: Supplement personalized information.

[0097] Enter customized data according to the pre-configured fields, such as "well depth 2 meters" for rainwater wells, and upload on-site photos for visual verification.

[0098] Step E5: Submit the data.

[0099] The data processing unit 240 is used to process the component information collected in real time.

[0100] Data processing specifically includes using GIS technology to link spatial information to achieve data-space correlation, solving the problem of data collection being disconnected from location in traditional technologies, while also supporting dynamic data updates to solve the problem of lagging data updates in traditional methods.

[0101] The data processing unit 240 performs the following sub-steps: Step T1: Automatically verify the real-time collected component information.

[0102] After receiving the collected data, the data processing layer triggers an automatic verification process. The verification criteria include: Integrity check: No non-empty fields (such as "part type" and "ownership unit") are missing; Format validation: Numeric fields (such as "well depth") conform to the numeric format, and telephone fields conform to the 11-digit mobile phone number rule; Uniqueness check: No duplicate component IDs (to prevent the same component from being entered multiple times); Ownership conflict verification: If the collected ownership information conflicts with the system's preset scope of responsibility (e.g., unit A enters the component that unit B is responsible for), an "ownership conflict" warning will be triggered.

[0103] If all the above checks pass, proceed to step T2.

[0104] If one or more of the above checks fail, the component information will be marked as "pending review" and sent to the city management command center for verification by staff.

[0105] As an example, if there is a conflict of ownership during the verification process, the staff will organize the ownership determination (such as holding a coordination meeting to clarify the responsible unit), and after the determination, the correct ownership unit will re-enter or correct the information.

[0106] Step T2: Perform data storage and map update.

[0107] The verified component information is synchronously stored in the GIS database, and the component's basic attributes, ownership information, and personalized fields are updated.

[0108] All data collected by the ownership units through mobile terminals (including basic attribute data such as component location / type, ownership data such as unit name / responsible person, personalized data such as rainwater well "depth" / street light "power", and multimedia data such as on-site photos) will be uniformly stored in the GIS database to avoid data being scattered across different carriers or systems.

[0109] In another embodiment of the present invention, node selection is used to store component information to prevent data loss due to abnormal storage of the GIS database.

[0110] The process of selecting nodes to store component information includes the following sub-steps: Step W1: Determine the multiple criteria for node selection.

[0111] These multiple indicators include node degree, connection strength, and importance.

[0112] Node degree characterizes the importance of a node in terms of its local importance, calculates the number of a node's neighbors, and reflects the degree of influence a node has on its surrounding neighbors.

[0113] Connection strength characterizes the importance of a node in terms of the importance of its relationships with other nodes. It calculates the sum of the communication frequencies between a node and other nodes, reflecting the node's ability to spread messages in a local area.

[0114] Central domain importance characterizes the importance of a node from the perspective of its global importance, reflecting the degree to which a node is located at the center of the network.

[0115] Understandably, multiple nodes form a network topology, where any node... node degree Represented as: ; in Represents any node The neighborhood of the node, that is, the neighborhood of the node The set of adjacent nodes, b is The adjacent nodes, This represents the node degree of b.

[0116] any node Connection strength Represented as: ; in Represents a node The weight of the edge connecting node b.

[0117] At the node neighborhood In the equation, the neighborhoods of any two nodes h and j are respectively... , Define nodes The central domain is , express No two nodes in the middle are connected by any means. The number of shortest paths, express Passing between any pair of nodes The number of shortest paths, let The node degree is , Middle node The length to node b is Then any node Central domain importance Represented as: ; in .

[0118] Nodes whose node degree, connection strength, and central domain importance are all greater than a specified threshold are selected as nodes for storing component information.

[0119] Understandably, the specified thresholds for node degree, connection strength, and central domain importance can be set separately, and nodes whose node degree, connection strength, and central domain importance are all greater than the corresponding specified thresholds are selected as nodes for storing component information.

[0120] Step W2: Select nodes based on multiple indicators to store component information.

[0121] Furthermore, the component location coordinates are linked to an electronic map to generate visual markers. These visual markers include component type icons and ownership unit identifiers.

[0122] Furthermore, the updated component information is simultaneously synchronized to the application layer and pushed to relevant management departments for querying and access.

[0123] The intelligent management unit 250 is used for intelligent management based on the processed component information.

[0124] The following are specific application examples of intelligent management achieved through the methods described above: Using the location query function, users can select precise query by inputting component information to confirm the component's location and attributes, or perform a fuzzy query to confirm the distribution of components within a specified range. When inspection personnel discover a component malfunction, they report the case through the PointCollection APP. The APP automatically associates with component information in the vicinity of the current location. The fault type is selected, and on-site photos are uploaded. An automatic work order is generated, containing component ownership, location, and fault description. The work order is directly dispatched to the corresponding ownership unit. The personnel handling the issue receive the work order through the APP, use GPS navigation to locate the faulty component, and perform repairs. After completion, repair photos are uploaded, the work order status is updated to "processed," and the information is archived on the management platform.

[0125] Furthermore, relevant management departments can also issue special inspection tasks for components, specifying the inspection scope and completion deadline.

[0126] For example, when a "Rainwater Well Cleaning Project" is issued, maintenance personnel mark the wells as "cleaned" in the app after completing the cleaning. The system then tracks the progress in real time and generates a visual report.

[0127] Preferably, the system supports exporting inspection records, which include time, personnel, and component status, for use in performance evaluation and management review.

[0128] This application also provides a computer storage medium storing computer instructions, which, when invoked, are used to execute the urban management method.

[0129] The embodiments disclosed in this invention provide a computer-readable storage medium storing computer program instructions that, when executed on a computer, cause the computer to perform the aforementioned urban management method.

[0130] This invention provides a processor for processing the aforementioned urban management method.

[0131] In this embodiment of the invention, the processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0132] The various methods, steps, and logic diagrams disclosed in the embodiments of this invention can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The processor reads information from the storage medium and, in conjunction with its hardware, completes the steps of the above methods.

[0133] The storage medium can be memory, such as volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.

[0134] Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate Synchronous DRAM (DDRSDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM).

[0135] This application has the following beneficial effects: This application significantly reduces management costs, greatly improves management efficiency, and shortens the response cycle by constructing a dynamic and precise urban component facility management system. Simultaneously, further data processing enhances data accuracy and timeliness, strengthening the foundation for decision-making. Timely reporting of component repairs ensures the safe operation of the facilities.

[0136] Although the examples referenced in this application are described for illustrative purposes only and not for limiting the scope of this application, changes, additions and / or deletions to the implementation may be made without departing from the scope of this application.

[0137] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for urban management, characterized in that, Includes the following steps: To construct an urban component and facility management platform; Customize the data collection fields based on the urban component and facility management platform; After completing the customization of the data collection fields, real-time data collection of component information is performed. Data processing is performed on the real-time collected component information; Intelligent management is implemented based on the processed component information.

2. The urban management method as described in claim 1, characterized in that, The construction of the urban component facility management platform includes building the management platform based on a personalized field configuration engine, geographic information technology, mobile Internet technology, and GPS positioning technology.

3. The urban management method as described in claim 1, characterized in that, Customizing the data collection fields includes setting 16 standard fields, including text, numeric, date, image, coordinate, and enumeration types, and synchronizing the field templates to the mobile terminals of the corresponding ownership units.

4. The urban management method as described in claim 1, characterized in that, Real-time collection of component information includes the following sub-steps: Determine the types of components to be managed; Real-time location tracking and basic information entry; Bind ownership information; Provide personalized information supplementation; Submit the data.

5. The urban management method as described in claim 1, characterized in that, Intelligent management based on the processed component information includes location querying, allowing users to select precise or fuzzy queries by inputting component information.

6. A city management system, characterized in that, include: The system comprises a management platform construction unit, a data collection field customization unit, a real-time data collection unit, a data processing unit, and an intelligent management unit. The management platform construction unit is used to build a management platform for urban components and facilities. The data collection field customization unit is used to customize data collection fields based on the urban component and facility management platform; The real-time acquisition unit is used to acquire component information in real time after the acquisition fields are customized. The data processing unit is used to process the component information collected in real time. The intelligent management unit is used for intelligent management based on the processed component information.

7. The urban management system as described in claim 6, characterized in that, The management platform construction unit constructs an urban component facility management platform, including building the management platform based on a personalized field configuration engine, geographic information technology, mobile internet technology, and GPS positioning technology.

8. The urban management system as described in claim 6, characterized in that, The custom field collection unit allows users to customize collection fields by setting 16 standard fields, including text, numeric, date, image, coordinate, and enumeration types, and synchronizing the field templates to the mobile terminals of the corresponding ownership units.

9. The urban management system as described in claim 6, characterized in that, The real-time acquisition unit performs the following sub-steps to collect component information in real time: Determine the types of components to be managed; Real-time location tracking and basic information entry; Bind ownership information; Provide personalized information supplementation; Submit the data.

10. The urban management system as described in claim 6, characterized in that, The intelligent management unit performs intelligent management based on the processed component information, including location query and selection of precise or fuzzy query by inputting component information.

Images