A management method and related device for post-investment operation data of long-term rental apartment projects

Abstract

The present application discloses a management method and related devices for post-investment operational data of a long-term rental apartment project, which relates to the field of data processing, including: obtaining the standardized initial operational data set of each operating system, inputting each initial operational data set into a preset data unified model, so that the preset data unified model performs structural mapping operations on each initial operational data set respectively, obtains and stores the operational data set of each operating system, wherein the structural mapping operation includes: based on a preset object entity mapping relationship table, determining the management entity corresponding to each business object in the initial operational data set, and determining the association relationship between each management entity, based on a preset attribute association relationship table, converting the attribute field content of the business object into the attribute field content of the target structure of the management entity. The present application performs structural mapping operations on each initial operational data set based on the preset data unified model, thereby realizing the aggregation and management of the operational data of each operating organization.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a management method and related devices for post-investment operation data of a long-term rental apartment project. Background Art

[0002] The existing management model of long-term rental apartment projects is that the investment institution entrusts the entrusted operation institution in the project location to operate on its behalf, and the investment institution manages the project based on the post-investment operation report of the project fed back by each entrusted operation institution. However, since the above project operation conditions are all data fed back by the entrusted operation institution after statistics and summary, the investment institution cannot determine the accuracy of the project operation report, which in turn makes it impossible for the investment institution to accurately manage the project. Therefore, how to realize the aggregation and management of the post-investment operation data of each entrusted operation institution has become an urgent problem to be solved. Summary of the invention

[0003] In view of the above problems, this application provides a management method and related devices for post-investment operation data of long-term rental apartment projects to achieve the purpose of aggregating and managing the operation data of various operating organizations. The specific plan is as follows:

[0004] The first aspect of the present application provides a method for managing post-investment operation data of a long-term rental apartment project, comprising:

[0005] Obtaining a standardized initial operation data set of each operation system, wherein the standardized initial operation data set includes all data required for formulating a project management plan;

[0006] Input each of the initial operation data sets into a preset data unified model, so that the preset data unified model performs a structure mapping operation on each of the initial operation data sets, obtains and stores the operation data sets of each of the operation systems, wherein the structure mapping operation includes:

[0007] For each of the initial operational data sets: based on the preset object entity mapping relationship table, determine the management entity corresponding to each business object in the initial operational data set, and determine the association relationship between each of the management entities based on the preset entity association relationship table; based on the preset attribute association relationship table, convert the attribute field content of the business object into the attribute field content of the target structure of the management entity corresponding to the business object, and the target structure is a structure recognizable by the management system.

[0008] In a possible implementation, the standardization process includes:

[0009] For each of the above operating systems:

[0010] Sending an operation data set template to the operation system, wherein the operation data set template includes: object names of a plurality of the business objects, and a set of attribute field names of the respective business objects;

[0011] The operation data set template after filling in the instance fed back by the operation system is determined as the initial operation data set of the system after the standardization processing, and the instance is an instance storing data corresponding to each attribute field in the attribute field name set of the business object.

[0012] In a possible implementation, determining the management entity corresponding to each business object in the initial operation data set based on the preset object entity mapping relationship table includes:

[0013] For each of the business objects:

[0014] Search at least one of the management entities corresponding to the business object in the preset object entity mapping relationship table, and call the instance conversion rule corresponding to the management entity to perform instance conversion on the instance of the business object based on the attribute field name set of the business object to obtain multiple attribute field contents of the business object.

[0015] In a possible implementation, the attribute word of the business object is converted into Segment Content The attribute field content converted into the target structure of the management entity corresponding to the business object includes:

[0016] For each of the business objects:

[0017] According to the preset attribute association relationship table, determining the attribute field association relationship between the attribute field content of the business object and the attribute field of the management entity corresponding to the business object;

[0018] For each attribute field of the management entity:

[0019] The attribute definition rule of the attribute field is searched from the preset attribute association relationship table, and based on the attribute definition rule, the attribute field content having the attribute field association relationship with the attribute field is converted into the attribute field content of the target structure of the attribute field.

[0020] In a possible implementation, the method further includes:

[0021] For each of the above operating systems:

[0022] Calling an evaluation indicator calculation formula corresponding to the system identifier of the operation system, and extracting an input parameter set from the operation system based on an input parameter list of the evaluation indicator calculation formula;

[0023] Importing the input parameter set into the evaluation index calculation formula to obtain the evaluation index of the operation system;

[0024] The initial project management plan corresponding to the evaluation index is sent to the front end for display, and the project management plan corresponding to the operation system is generated based on the modification result fed back by the front end.

[0025] The second aspect of the present application provides a management system for post-investment operation data of a long-term rental apartment project, including:

[0026] A data collection module, used to obtain the standardized initial operation data set of each operation system, wherein the standardized initial operation data set includes the full amount of data required for formulating the project management plan;

[0027] A data conversion module is used to input each of the initial operation data sets into a preset data unified model, so that the preset data unified model performs structure mapping operations on each of the initial operation data sets respectively, obtains and stores the operation data sets of each of the operation systems, wherein the structure mapping operation includes: for each of the initial operation data sets: based on a preset object entity mapping relationship table, determining the management entity corresponding to each business object in the initial operation data set, and determining the association relationship between each of the management entities based on a preset entity association relationship table; based on a preset attribute association relationship table, converting the attribute field content of the business object into the attribute field content of the target structure of the management entity corresponding to the business object, wherein the target structure is a structure recognizable by the management system.

[0028] In a possible implementation, the data acquisition module is configured to:

[0029] For each of the above operating systems:

[0030] Sending an operation data set template to the operation system, wherein the operation data set template includes: object names of a plurality of the business objects, and a set of attribute field names of the respective business objects;

[0031] The operation data set template after filling in the instance fed back by the operation system is determined as the initial operation data set of the system after the standardization processing, and the instance is an instance storing data corresponding to each attribute field in the attribute field name set of the business object.

[0032] In a possible implementation, when the data conversion module determines the management entity corresponding to each business object in the initial operation data set based on the preset object entity mapping relationship table, it is set to:

[0033] For each of the business objects:

[0034] Search at least one of the management entities corresponding to the business object in the preset object entity mapping relationship table, and call the instance conversion rule corresponding to the management entity to perform instance conversion on the instance of the business object based on the attribute field name set of the business object to obtain multiple attribute field contents of the business object.

[0035] In a possible implementation, the data conversion module converts the industry Service Object The attribute field content of the target structure of the management entity corresponding to the business object is converted into the attribute field content of the target structure of the management entity corresponding to the business object, including:

[0036] For each of the business objects:

[0037] According to the preset attribute association relationship table, determining the attribute field association relationship between the attribute field content of the business object and the attribute field of the management entity corresponding to the business object;

[0038] For each attribute field of the management entity:

[0039] The attribute definition rule of the attribute field is searched from the preset attribute association relationship table, and based on the attribute definition rule, the attribute field content having the attribute field association relationship with the attribute field is converted into the attribute field content of the target structure of the attribute field.

[0040] In a possible implementation, the management system further includes:

[0041] The management plan output module is used to: for each of the operation systems: call the evaluation index calculation formula corresponding to the system identifier of the operation system, and extract an input parameter set from the operation system based on the input parameter list of the evaluation index calculation formula; import the input parameter set into the evaluation index calculation formula to obtain the evaluation index of the operation system; send the initial project management plan corresponding to the evaluation index to the front end for display, and generate the project management plan corresponding to the operation system based on the modification result fed back by the front end.

[0042] The third aspect of the present application provides a computer program product, including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the method for managing post-investment operation data of a long-term rental apartment project according to the first aspect or any implementation method of the first aspect.

[0043] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:

[0044] The memory is used to store computer programs;

[0045] The processor is used to execute the computer program so that the electronic device can implement the method for managing post-investment operation data of a long-term rental apartment project according to the first aspect or any implementation method of the first aspect.

[0046] A fifth aspect of the present application provides a computer storage medium, which carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement a method for managing post-investment operation data of a long-term rental apartment project according to the first aspect or any implementation of the first aspect.

[0047] By means of the above technical scheme, the present application provides a method and related device for managing the post-investment operation data of a long-term rental apartment project. By configuring, the initial operation data set of each operation system is obtained after standardized processing, so that the types, quantities and attribute fields of the business objects in the initial operation data sets of different operation systems are consistent, thereby providing a basis for subsequent aggregation and management. In addition, by configuring the preset object entity mapping relationship table, the preset entity association relationship table and the preset attribute association relationship table, the extraction of the full amount of data required for the same business from different business data is realized, and the attribute field contents of different structures are all converted into the attribute field contents of the target format, so that the management system can realize the aggregation and management of the operation data of the same format. Finally, by configuring, each initial operation data set is input into the preset data unified model, so that the preset data unified model performs structure mapping operations on each initial operation data set respectively, obtains and stores the operation data set of each operation system, so that the present application, compared with the prior art method of adding plug-ins to the operation system, avoids the risk of plug-ins interfering with the operation logic of the original operation system, improves the operation reliability of the operation system, and reduces the operation cost of the operation organization. It can be seen that the present application reduces the operation cost and improves the operation reliability while realizing the aggregation and management of the operation data of each operation organization. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0049] Figure 1 A flowchart of a method for managing post-investment operation data of a long-term rental apartment project provided for this application;

[0050] Figure 2 A schematic diagram of an operational data set template provided for this application;

[0051] Figure 3A block diagram of a management system for post-investment operation data of a long-term rental apartment project provided for this application;

[0052] Figure 4 A schematic diagram of the structure of an electronic device provided in this application. DETAILED DESCRIPTION

[0053] The following describes the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. The terms used in the implementation method section of the present application are only used to explain the specific embodiments of the present application, and are not intended to limit the present application.

[0054] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0055] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and need not be used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, which is only to describe the distinction mode adopted by the objects of the same attributes when describing in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0056] It should be noted that, in actual application scenarios, compared with the prior art, this application realizes the aggregation and management of the operation data of each operation organization, while reducing the operation cost and improving the operation reliability. Specifically: Due to the differences in business logic and database table structure between different operation systems and between the operation system and the management system, the management system cannot directly aggregate the operation data of different structures. Therefore, the solution proposed by the prior art is that each operation organization adds a plug-in coupled with the management system in the operation system so that the plug-in sends the required operation data to the management system. However, such plug-ins will not only interfere with the operation logic of the original operation system, reduce the operation reliability of the operation system, but also increase the operation cost of the operation organization. However, this application configures each initial operation data set that has been standardized to be input into a preset data unified model, so that the preset data unified model performs structural mapping operations on each initial operation data set respectively, obtains and stores the operation data set of each operation system, thereby obtaining the full amount of data required for formulating a project management plan without making additional improvements to the existing operation system and management system. And because the attribute field content of each management entity in the above operation data set is a target structure that can be recognized by the management system, the aggregation and management of the operation data of each operation organization is realized. It can be seen that this application not only realizes the aggregation and management of the operating data of each operating organization, but also reduces the operating cost and improves the operational reliability.

[0057] The first aspect of the present application provides a method for managing post-investment operation data of a long-term rental apartment project, such as Figure 1 As shown in the figure, the management method of post-investment operation data of the long-term rental apartment project includes:

[0058] S101. Obtaining a standardized initial operation data set for each operation system, wherein the standardized initial operation data set includes a full amount of data required for formulating a project management plan.

[0059] It should be noted that in actual application scenarios, the above-mentioned standardization processing is a processing step for limiting the data type and data quantity in the initial operation data set. Due to the differences in the database table structure in each operation system, there are differences in the business objects or attribute fields of business objects in different operation data. For example, taking the "customer source channel" business object in the operation data as an example, the attribute fields of the business object in the A operation system include "online", "intermediary" and "natural visit" three attribute fields, while the attribute fields of the business object in the B operation system include "online A APP", "online B APP", "online own APP", "intermediary" and "natural visit" five attribute fields. It can be seen that the attributes and quantities of the same business objects in the operation data of the two operation systems are different. This makes it impossible for the existing management system to summarize and manage the operation data of the above two operation systems. However, this application obtains the initial operation data set of each operation system after standardized processing through configuration, so that the types, quantities and attribute fields of business objects in the initial operation data sets of different operation systems are consistent, thereby providing a basis for subsequent aggregation and management.

[0060] S102. Input each initial operation data set into a preset data unified model, so that the preset data unified model performs a structure mapping operation on each initial operation data set respectively, obtains and stores the operation data set of each operation system, wherein the structure mapping operation includes: for each initial operation data set: based on a preset object entity mapping relationship table, determine the management entity corresponding to each business object in the initial operation data set, and determine the association relationship between each management entity based on a preset entity association relationship table; based on a preset attribute association relationship table, convert the attribute field content of the business object into the attribute field content of the target structure of the management entity corresponding to the business object, and the target structure is a structure recognizable by the management system.

[0061] It should be noted that in actual application scenarios, the above-mentioned business objects (Business Object, BO) are used to represent business entities when executing specific businesses. For example, in the management process of long-term rental apartments, when executing the rental contract business, it is necessary to obtain information about the house, tenant and bill. The business objects include "tenant", "house", "contract" and "bill".

[0062] It should be noted that, in actual application scenarios, the above-mentioned management entity represents a specific business in the management system. The above-mentioned preset data unified model is a model abstracted based on the analysis of the business logic of each operating system. The above-mentioned preset object entity mapping relationship table is a data table used to at least store the mapping relationship between the full amount of business required to execute the business represented by the management entity and the management entity. The above-mentioned preset entity association relationship table is a data table used to at least store the association relationship between management entities representing different businesses. The above-mentioned preset attribute association relationship table is a data table used to at least store the association relationship between the attribute fields of the business object and the attribute fields of the business object under the management entity corresponding to the business object.

[0063] It should be noted that in actual application scenarios, due to differences in the business logic of each operating system, the business objects and attribute field contents of the business objects involved in the same business in different operating systems are different. For example, when a tenant renews his lease, the business logic of operating system A is to regenerate a new contract, while the business logic of operating system B is to modify the contract end date in the old contract to the new date, without generating a new contract, and to record additional renewal information. It can be seen that the business objects involved in different operating data for the same business are different, which makes it impossible for the existing management system to summarize and manage the operating data of the above two operating systems. Therefore, this application realizes the extraction of the full amount of data required for the same business from different business data by configuring a preset object entity mapping relationship table, a preset entity association relationship table, and a preset attribute association relationship table, and converts all attribute field contents of different structures into attribute field contents of the target format, so that the management system can realize the aggregation and management of operating data in the same format.

[0064] It should be noted that in actual application scenarios, the present application configures each initial operation data set to be input into a preset data unified model, so that the preset data unified model performs structural mapping operations on each initial operation data set respectively, obtains and stores the operation data set of each operation system, so that compared with the prior art method of adding plug-ins to the operation system, the present application avoids the risk of the plug-in interfering with the operation logic of the original operation system, improves the operation reliability of the operation system, and reduces the operation cost of the operation organization.

[0065] This application obtains the standardized initial operation data set of each operation system through configuration, so that the types, quantities and attribute fields of business objects in the initial operation data sets of different operation systems are consistent, thereby providing a basis for subsequent aggregation and management. In addition, by configuring the preset object entity mapping relationship table, the preset entity association relationship table and the preset attribute association relationship table, the full amount of data required for the same business is extracted from different business data, and the attribute field contents of different structures are all converted into the attribute field contents of the target format, so that the management system can realize the aggregation and management of the operation data of the same format. Finally, by configuring each initial operation data set to be input into the preset data unified model, so that the preset data unified model performs structural mapping operations on each initial operation data set respectively, obtains and stores the operation data set of each operation system, so that this application, compared with the prior art of adding plug-ins to the operation system, avoids the risk of plug-ins interfering with the operation logic of the original operation system, improves the operation reliability of the operation system, and reduces the operation cost of the operation organization. It can be seen that this application reduces the operation cost and improves the operation reliability while realizing the aggregation and management of the operation data of each operation organization.

[0066] In a possible implementation, the above standardization process includes:

[0067] For each operating system:

[0068] Sending an operation data set template to the operation system, wherein the operation data set template includes: object names of multiple business objects, and a set of attribute field names of each business object;

[0069] The operation data set template filled with instances fed back by the operation system is determined as the initial operation data set of the system after standardization. The instance is an instance storing data corresponding to each attribute field in the attribute field name set of the business object.

[0070] It should be noted that, in actual application scenarios, the above-mentioned operation data set template may be obtained after sorting out and defining various business objects involved in the business logic of each operation system, and the specific acquisition process may include the following steps A1 to A4:

[0071] For the business logic of different businesses in each operating system:

[0072] Step A1, determining the main business object of the business logic and the secondary business object of the main business object, and triggering step A2.

[0073] Step A2, for each primary business object and each secondary business object: determine each attribute field of the business object under the business logic, wherein the types of the attribute field include attribute fields of the business object and attribute fields between business objects, and trigger step A3.

[0074] In a possible implementation, the attribute fields of the above business objects may be: For example, assuming that the business object is "room", the corresponding attribute fields include "project number", "building number", "unit", "floor", "room number", "building area", "unit type" and "orientation". The attribute fields between the above business objects may be: For example, there may be actions such as repair and review between the two business objects "tenant" and "room", and the attribute fields shared by the two business objects "tenant" and "room" include "repair record" and "review record".

[0075] Step A3, for each attribute field: based on the data table structure of the management system, define the field content of the attribute field, and trigger step A4.

[0076] In a possible implementation, the field content of the above attribute field can be a business or technical standard that represents business definition, business rules, data category, data format, value range, etc. For example, the field content of the attribute field "Housing Type" can be defined as: Chinese name "Housing Type", English name "Building Floor Plan Type", business definition "a set of residential types composed of different usable areas and living spaces", business rule "collected according to the information stated in the commercial housing sales contract or the attached page of the house ownership certificate", data category "enumeration", value range "one bedroom and one living room, two bedrooms and one living room, three bedrooms and one living room, four bedrooms and one living room, two bedrooms and two living rooms, three bedrooms and two living rooms, four bedrooms and two living rooms, duplex structure, villa, bay, other".

[0077] Step A4, taking "Long-term Rental Apartment Data Standard" as the root node and the data obtained in the above steps A1 to A3 as leaf nodes at each level, generates a tree-structured operation data set template.

[0078] In order to facilitate the understanding of the above operation data set template, a possible implementation of this application is specifically described here:

[0079] like Figure 2As shown, it is a schematic diagram of the operation data set template. The root node is "Long-term rental apartment post-investment operation management data standard", the first-level leaf nodes are "people", "contracts", "products", "resource items" and "other public", a total of five main business objects, the second-level leaf nodes are "real estate", "product contracts", "housing rental", "customer general" and "cleaning", a total of five secondary business objects, and the third-level leaf nodes only display the attribute fields of "real estate", including "house location", "house type" and "rental area", among which "rental area" is also used in "housing rental". The fourth-level leaf node is the field content definition of the attribute field of each third-level leaf node. When in use, the operation system only needs to compare the names of its own business objects and their attribute fields with the corresponding node names in the above-mentioned operation data set template for consistency, and fill in the corresponding field content into the above-mentioned template if the comparison passes.

[0080] In a possible implementation, based on a preset object entity mapping relationship table, determining the management entity corresponding to each business object in the initial operation data set includes:

[0081] For each business object:

[0082] Search at least one management entity corresponding to the business object in the preset object entity mapping relationship table, and call the instance conversion rule corresponding to the management entity to perform instance conversion on the instance of the business object based on the attribute field name set of the business object to obtain multiple attribute field contents of the business object.

[0083] It should be noted that in actual application scenarios, the correspondence between the above management entities and business objects can be obtained based on the above operation data set template. For example, the "room" business object only corresponds to the "room" management entity. The "tenant" business object can correspond to both the "individual tenant" management entity and the "corporate tenant" management entity.

[0084] It should be noted that, in an actual application scenario, the above-mentioned preset entity association relationship table can be obtained by importing the above-mentioned preset object entity mapping relationship table into an entity-relationship diagram (ER) generation tool to obtain an ER diagram.

[0085] It should be noted that in actual application scenarios, since the above-mentioned business objects and management entities are one-to-many or newly added, in order to avoid data aggregation errors due to omissions, this application can call the instance conversion rule corresponding to the management entity based on the attribute field name set of the business object to perform instance conversion on the instance of the business object, and obtain the contents of multiple attribute fields of the business object, thereby improving data aggregation accuracy and data integrity. Specifically:

[0086] There are three types of instance conversion rules, including splitting, splicing, merging, and adding, where:

[0087] Assume that a business object corresponds to multiple management entities, such as a user renting three rooms under one contract. In this case, one "contract" business object corresponds to three "rental contract" management entities (one "rental contract" management entity corresponds to only one "room" business object). At this time, the above "contract" business object is split according to the primary key "contract number + room number" of the "rental contract" management entity using the splitting rule to obtain three "contract" business objects, and each business object has only one room number in the full attribute field content.

[0088] Assume that multiple business objects correspond to one management entity, such as the "bill" management entity corresponds to both the "receipt" business object and the "refund" business object. At this time, the attribute field contents of the "receipt" business object and the "refund" business object are merged using the merge rule to obtain the "receipt and refund bill" business object, which includes all the attribute field contents of the "receipt" business object and the "refund" business object.

[0089] Assume that the business object lacks the attribute field content required by the management entity. For example, when the user checks out, the settlement amount is directly generated without recording the receivables and refunds details. In this case, it is necessary to use the new rules to extract the "receivables and refunds" attribute field content according to the attribute field content of the "settlement fees" of the parent business object of the "receivables and refunds details" business object, generate the "receivables and refunds bill" business object, and add the values ​​to the "bill" management entity.

[0090] In a possible implementation, based on a preset attribute association relationship table, converting the attribute field content of the business object into the attribute field content of the target structure of the management entity corresponding to the business object includes:

[0091] For each business object:

[0092] According to the preset attribute association relationship table, determine the attribute field association relationship between the content of each attribute field of the business object and each attribute field of the management entity corresponding to the business object;

[0093] For each attribute field of a managed entity:

[0094] The attribute definition rule of the attribute field is searched from the preset attribute association relationship table, and based on the attribute definition rule, the attribute field content having an attribute field association relationship with the attribute field is converted into the attribute field content of the target structure of the attribute field.

[0095] It should be noted that in actual application scenarios, due to the different database structures of different operating systems, there are differences in the naming rules for the same attribute field, which makes it very easy to aggregate the contents of different attribute fields into the same attribute field when aggregating data. Therefore, this application configures the attribute definition rule for searching the attribute field from the preset attribute association table, and based on the attribute definition rule, converts the attribute field content that has an attribute field association relationship with the attribute field into the attribute field content of the target structure of the attribute field, thereby improving the accuracy of data aggregation.

[0096] In a possible implementation, the implementation method of converting the attribute field content having an attribute field association relationship with the attribute field into the attribute field content of the target structure of the attribute field based on the attribute definition rule may be:

[0097] Assuming that the attribute field content of the "Expense" business object includes "First-level classification" and "Second-level classification", and the associated attribute field in the management entity corresponding to the business object is the "Expense Account" field, then based on the attribute definition rule "Merge", the specific values ​​of the "First-level classification" and "Second-level classification" are merged into the "Expense Account" field.

[0098] Assuming that the content of the attribute field of the business object is character type, and the content of the associated attribute field in the management entity corresponding to the business object is integer type, the character type is converted to integer type based on the attribute definition rule "Format Conversion", and the integer value is filled into the associated attribute field.

[0099] It should be noted that in actual application scenarios, in order to ensure the accuracy of the above conversion process and improve the accuracy of data aggregation. After the conversion is completed, the converted attribute field content can be verified using a verification script pre-configured with verification rules. The types of the above verification rules include but are not limited to: accuracy and completeness verification, business logic consistency verification and data consistency verification. Among them, the accuracy and completeness verification is used to ensure the accuracy and completeness of the converted attribute field content, such as whether the converted contract end time is earlier than the conversion completion time. If so, it indicates a conversion error. The business logic consistency check is used to ensure that the business logic is executed correctly. For example, the converted contract ID must exist in the corresponding management entity. If it is missing, it indicates a conversion error. The data consistency check is used to verify whether there is any missing conversion data. For example, if the value of the bill is 0 after it is converted from character type to integer type, it indicates a conversion error. At this time, the automatic compensation mechanism can be triggered to compensate the data.

[0100] In one possible implementation, the above Figure 1 The management method of post-investment operation data of a long-term rental apartment project shown also includes:

[0101] For each operating system:

[0102] Calling an evaluation indicator calculation formula corresponding to the system identifier of the operation system, and extracting an input parameter set from the operation system based on the input parameter list of the evaluation indicator calculation formula;

[0103] Import the input parameter set into the evaluation index calculation formula to obtain the evaluation index of the operation system;

[0104] The initial project management plan corresponding to the evaluation indicators is sent to the front end for display, and the project management plan corresponding to the operation system is generated based on the modification results fed back by the front end.

[0105] It should be noted that in actual application scenarios, since the above evaluation indicators involve differences in the management model and region of the entrusted operating institutions corresponding to different operating systems, in order to facilitate unified calculation, the above evaluation indicator calculation formula can be set after comprehensive evaluation based on the actual operating conditions of each entrusted operating institution, for example:

[0106] For the A and B operating systems in Region A, the formula for calculating the evaluation index corresponding to system identifier A is: "Number of rented rooms (including staff rooms) / Total number of houses in operation (including staff rooms)". The formula for calculating the evaluation index corresponding to system identifier B is: "Number of rented rooms (excluding staff rooms) / Total number of houses in operation (excluding staff rooms)". In order to unify the standards, the formula for calculating the evaluation index corresponding to A and B can be unified as: "Number of rented rooms (excluding staff rooms) / Total number of houses in operation (including staff rooms)".

[0107] It should be noted that in actual application scenarios, in order to maintain data aggregation accuracy, the above steps can be repeated based on the operation data of each operation system during the operation period after running for a period of time. Figure 1 The management method of post-investment operation data of the long-term rental apartment project shown can be dynamically updated.

[0108] The second aspect of the present application provides a management system for post-investment operation data of a long-term rental apartment project, such as Figure 3 As shown, the management system for post-investment operation data of the long-term rental apartment project includes:

[0109] The data collection module 301 is used to obtain the standardized initial operation data set of each operation system, and the standardized initial operation data set includes the full amount of data required for formulating the project management plan;

[0110] The data conversion module 302 is used to input each initial operation data set into a preset data unified model so that the preset data unified model performs structure mapping operations on each initial operation data set respectively, obtains and stores the operation data set of each operation system, wherein the structure mapping operation includes: for each initial operation data set: based on the preset object entity mapping relationship table, determine the management entity corresponding to each business object in the initial operation data set, and determine the association relationship between each management entity based on the preset entity association relationship table; based on the preset attribute association relationship table, convert the attribute field content of the business object into the attribute field content of the target structure of the management entity corresponding to the business object, and the target structure is a structure recognizable by the management system.

[0111] In a possible implementation, the data acquisition module 301 is configured to:

[0112] For each operating system:

[0113] Sending an operation data set template to the operation system, wherein the operation data set template includes: object names of multiple business objects, and a set of attribute field names of each business object;

[0114] The operation data set template filled with instances fed back by the operation system is determined as the initial operation data set of the system after standardization. The instance is an instance storing data corresponding to each attribute field in the attribute field name set of the business object.

[0115] In a possible implementation, the data conversion module 302 is configured to:

[0116] For each business object:

[0117] Search at least one management entity corresponding to the business object in the preset object entity mapping relationship table, and call the instance conversion rule corresponding to the management entity to perform instance conversion on the instance of the business object based on the attribute field name set of the business object to obtain multiple attribute field contents of the business object.

[0118] In a possible implementation, the data conversion module 302 converts the attribute field content of the business object into the attribute field content of the target structure of the management entity corresponding to the business object based on the preset attribute association relationship table, including:

[0119] For each business object:

[0120] According to the preset attribute association relationship table, determine the attribute field association relationship between the content of each attribute field of the business object and each attribute field of the management entity corresponding to the business object;

[0121] For each attribute field of a managed entity:

[0122] The attribute definition rule of the attribute field is searched from the preset attribute association relationship table, and based on the attribute definition rule, the attribute field content having an attribute field association relationship with the attribute field is converted into the attribute field content of the target structure of the attribute field.

[0123] In one possible implementation, the above Figure 3 The management system for post-investment operation data of the long-term rental apartment project shown also includes:

[0124] The management plan output module is used for each operation system: calling the evaluation index calculation formula corresponding to the system identifier of the operation system, and extracting the input parameter set from the operation system based on the input parameter list of the evaluation index calculation formula; importing the input parameter set into the evaluation index calculation formula to obtain the evaluation index of the operation system; sending the initial project management plan corresponding to the evaluation index to the front end for display, and generating the project management plan corresponding to the operation system based on the modification results fed back by the front end.

[0125] The third aspect of the present application provides a computer program product, including computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the method for managing post-investment operation data of a long-term rental apartment project according to the first aspect or any implementation method of the first aspect.

[0126] A fourth aspect of the present application provides an electronic device, comprising at least one processor and a memory connected to the processor, wherein:

[0127] The memory is used to store computer programs;

[0128] The processor is used to execute a computer program so that the electronic device can implement the method for managing post-investment operation data of a long-term rental apartment project according to the first aspect or any implementation method of the first aspect.

[0129] The present application also provides an electronic device in an embodiment. Figure 4 As shown, it shows a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present application. The electronic device in the embodiments of the present application may include but is not limited to fixed terminals such as mobile phones, notebook computers, PDAs (personal digital assistants), PADs (tablet computers), desktop computers, etc. Figure 4 The electronic device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0130] like Figure 4As shown, the electronic device may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage device 408 to a random access memory (RAM) 403. When the electronic device is powered on, various programs and data required for the operation of the electronic device are also stored in the RAM 403. The processing device 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0131] Typically, the following devices may be connected to the I / O interface 405: an input device 406 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 407 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 408 including, for example, a memory card, a hard disk, etc.; and a communication device 409. The communication device 409 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. Although Figure 4 An electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0132] A fifth aspect of the present application provides a computer storage medium, which carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement a method for managing post-investment operation data of a long-term rental apartment project according to the first aspect or any implementation of the first aspect.

[0133] It should also be noted that the device embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, in the drawings of the device embodiments provided by the present application, the connection relationship between the modules indicates that there is a communication connection between them, which may be specifically implemented as one or more communication buses or signal lines.

[0134] Through the description of the above implementation mode, the technicians in the field can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course, it can also be implemented by special hardware including special integrated circuits, special CPUs, special memories, special components, etc. In general, all functions completed by computer programs can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be various, such as analog circuits, digital circuits or special circuits. However, for the present application, software program implementation is a better implementation mode in more cases. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer floppy disk, a U disk, a mobile hard disk, a ROM, a RAM, a disk or an optical disk, etc., including a number of instructions to enable a computer device (which can be a personal computer, a training device, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0135] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0136] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a training device, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, training device, or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)), etc.

Claims

1. A method for managing post-investment operation data of a long-term rental apartment project, characterized in that: include: Obtaining a standardized initial operation data set of each operation system, wherein the standardized initial operation data set includes all data required for formulating a project management plan; Input each of the initial operation data sets into a preset data unified model, so that the preset data unified model performs a structure mapping operation on each of the initial operation data sets, obtains and stores the operation data sets of each of the operation systems, wherein the structure mapping operation includes: For each of the initial operational data sets: based on the preset object entity mapping relationship table, determine the management entity corresponding to each business object in the initial operational data set, and determine the association relationship between each of the management entities based on the preset entity association relationship table; based on the preset attribute association relationship table, convert the attribute field content of the business object into the attribute field content of the target structure of the management entity corresponding to the business object, and the target structure is a structure recognizable by the management system.

2. The method for managing post-investment operation data of a long-term rental apartment project according to claim 1, characterized in that: The standardization process comprises: For each of the above operating systems: Sending an operation data set template to the operation system, wherein the operation data set template includes: object names of a plurality of the business objects, and a set of attribute field names of the respective business objects; The operation data set template filled with instances fed back by the operation system is determined as the initial operation data set of the system after the standardization processing, and the instance is an instance storing data corresponding to each attribute field in the attribute field name set of the business object.

3. The method for managing post-investment operation data of a long-term rental apartment project according to claim 2 is characterized in that: The determining, based on the preset object entity mapping relationship table, the management entity corresponding to each business object in the initial operation data set includes: For each of the business objects: Search at least one of the management entities corresponding to the business object in the preset object entity mapping relationship table, and call the instance conversion rule corresponding to the management entity to perform instance conversion on the instance of the business object based on the attribute field name set of the business object to obtain multiple attribute field contents of the business object.

4. The method for managing post-investment operation data of a long-term rental apartment project according to claim 3 is characterized in that: The converting the attribute field content of the business object into the attribute field content of the target structure of the management entity corresponding to the business object based on the preset attribute association relationship table includes: For each of the business objects: According to the preset attribute association relationship table, determining the attribute field association relationship between the attribute field content of the business object and the attribute field of the management entity corresponding to the business object; For each attribute field of the management entity: The attribute definition rule of the attribute field is searched from the preset attribute association relationship table, and based on the attribute definition rule, the attribute field content having the attribute field association relationship with the attribute field is converted into the attribute field content of the target structure of the attribute field.

5. The method for managing post-investment operation data of a long-term rental apartment project according to claim 1, characterized in that: The method further comprises: For each of the above operating systems: Calling an evaluation indicator calculation formula corresponding to the system identifier of the operation system, and extracting an input parameter set from the operation system based on an input parameter list of the evaluation indicator calculation formula; Importing the input parameter set into the evaluation index calculation formula to obtain the evaluation index of the operation system; The initial project management plan corresponding to the evaluation index is sent to the front end for display, and the project management plan corresponding to the operation system is generated based on the modification result fed back by the front end.

6. A management system for post-investment operation data of long-term rental apartment projects, characterized in that: include: A data collection module, used to obtain the standardized initial operation data set of each operation system, wherein the standardized initial operation data set includes the full amount of data required for formulating the project management plan; A data conversion module is used to input each of the initial operation data sets into a preset data unified model, so that the preset data unified model performs structure mapping operations on each of the initial operation data sets respectively, obtains and stores the operation data sets of each of the operation systems, wherein the structure mapping operation includes: for each of the initial operation data sets: based on a preset object entity mapping relationship table, determining the management entity corresponding to each business object in the initial operation data set, and determining the association relationship between each of the management entities based on a preset entity association relationship table; based on a preset attribute association relationship table, converting the attribute field content of the business object into the attribute field content of the target structure of the management entity corresponding to the business object, wherein the target structure is a structure recognizable by the management system.

7. The management system for post-investment operation data of long-term rental apartment projects according to claim 6 is characterized in that: The management system also includes: The management plan output module is used to: for each of the operation systems: call the evaluation index calculation formula corresponding to the system identifier of the operation system, and extract an input parameter set from the operation system based on the input parameter list of the evaluation index calculation formula; import the input parameter set into the evaluation index calculation formula to obtain the evaluation index of the operation system; send the initial project management plan corresponding to the evaluation index to the front end for display, and generate the project management plan corresponding to the operation system based on the modification result fed back by the front end.

8. A computer program product, characterized in that It includes computer-readable instructions. When the computer-readable instructions are executed on an electronic device, the electronic device implements the method for managing post-investment operation data of a long-term rental apartment project as described in any one of claims 1 to 5.

9. An electronic device, characterized in that: The method comprises at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program so that the electronic device can implement the method for managing post-investment operation data of a long-term rental apartment project as described in any one of claims 1 to 5.

10. A computer storage medium, characterized in that: The storage medium carries one or more computer programs. When the one or more computer programs are executed by an electronic device, the electronic device can implement the method for managing post-investment operation data of a long-term rental apartment project as described in any one of claims 1 to 5.

Images