Work order management method and device based on multi-system linkage, equipment and medium

Abstract

This invention proposes a work order management method, device, equipment, and medium based on multi-system linkage. The method includes: determining a hierarchical field of a target rule as a first field; obtaining target resident information from a data lake based on the target resident identifier; determining a target risk level based on the target rule and the first resident information corresponding to the first field; determining a key field corresponding to the target risk level as a second field; and after creating a target work order, displaying the first resident information based on a preset first style and displaying the second resident information corresponding to the second field based on a preset second style. According to the technical solution of this invention, the target risk level of a resident can be assessed using the first resident information, and the second resident information can be dynamically determined based on the target risk level. Different styles allow follow-up personnel to quickly locate the first and second resident information from the follow-up work order, improving the readability of the follow-up work order and increasing follow-up efficiency.

Description

Technical Field

[0001] This invention relates to the field of intelligent work order management technology, and in particular to a work order management method, device, equipment and medium based on multi-system linkage. Background Technology

[0002] Currently, follow-up visits to address outstanding payments are an important part of property management. These visits require tailored communication based on the specific reasons for the arrears to improve collection efficiency. Traditional methods primarily rely on manual recording of each homeowner's reasons for non-payment, which is inefficient and no longer meets today's efficiency requirements.

[0003] In some related technologies, work order templates are typically pre-set. Based on the preset fields in the template, corresponding resident information is retrieved from the database. After the resident information is filled into the work order template, a follow-up work order is generated and then assigned to the appropriate follow-up personnel for further follow-up. However, if all resident information is retrieved for each follow-up work order, the work order template becomes quite complex. Before processing each work order, the follow-up personnel need to mark useful resident information in the work order, which increases the processing time and affects the efficiency of follow-up visits. Summary of the Invention

[0004] This invention aims to at least solve one of the technical problems existing in the prior art. To this end, this invention proposes a work order management method, device, equipment, and medium based on multi-system linkage, which can dynamically adjust the display content and display mode of follow-up work orders according to the risk level of residents, thereby improving the efficiency of follow-up visits.

[0005] In a first aspect, embodiments of the present invention provide a work order management method based on multi-system linkage, applied to a work order system. The work order system is communicatively connected to a data lake, which includes multiple preset fields. The work order system has multiple preset rules, each preset rule including multiple hierarchical fields and preset risk levels. The field values ​​of the hierarchical fields corresponding to each preset risk level are different. Each preset risk level is associated with multiple key fields, and the hierarchical fields and key fields belong to the preset fields. The method includes:

[0006] Select a target rule from multiple preset rules, and determine the hierarchical field of the target rule as the first field;

[0007] In response to selecting a target resident identifier from multiple candidate resident identifiers, the target resident information corresponding to each of the preset fields is obtained from the data lake based on the target resident identifier. The target risk level is determined based on the target rule and the first resident information corresponding to the first field. The key field corresponding to the target risk level is determined as the second field.

[0008] A target work order is created based on the target resident information. The first resident information is displayed based on a preset first style, and the second resident information corresponding to the second field is displayed based on a preset second style.

[0009] According to some embodiments of the present invention, before selecting a target rule from a plurality of preset rules, the method further includes:

[0010] A rule list is constructed in the visualization interface, wherein each column of the rule list corresponds to a preset risk level, and each row corresponds to the classification field of a preset rule and the key field under each preset risk level;

[0011] When a rule to be edited is selected from the rule list, the preset fields other than the hierarchical fields and the key fields of the rule to be edited are determined as candidate fields. Each candidate field is displayed outside the rule list. The hierarchical fields and the key fields corresponding to the rule to be edited are unlocked. In response to a drag operation based on any preset field in the visualization interface, the dragged preset field is added to the released hierarchical fields and the key fields, or the preset field dragged out of the rule list is determined as the candidate field.

[0012] Alternatively, in response to the rule creation instruction on the visualization interface, each of the preset fields is displayed outside the rule list, a new rule is created in the rule list, and in response to the drag operation, the corresponding hierarchical field and the key field are added to the new rule.

[0013] According to some embodiments of the present invention, the work order system has a first API, which has preset formats corresponding to each of the preset fields. The system retrieves target resident information corresponding to each of the preset fields from the data lake based on the target resident identifier, including:

[0014] The first API is configured based on the target resident identifier and the first field, so that the first API determines the preset field other than the first field as the third field and determines the target format corresponding to each of the first fields.

[0015] The first API performs a data acquisition operation based on the target resident identifier and the first field to obtain the first resident information from the data lake;

[0016] Based on any of the first resident information, the first API is used to determine the target format according to the corresponding first field, and the first resident information is verified based on the target format;

[0017] Once each piece of information for the first resident has passed verification, the data acquisition operation is performed via the first API based on the target resident identifier and the third field to obtain the remaining target resident information from the data lake.

[0018] According to some embodiments of the present invention, the data lake includes multiple data partitions, each data partition is associated with multiple partition resident identifiers, each data partition is configured with each preset field, and the data acquisition operation includes:

[0019] A field set is constructed using the first API, wherein the field set includes all of the first field, or all of the third field;

[0020] A target query instruction is constructed based on the target resident identifier and the field set, and the target query instruction is sent to the data lake so that the data lake determines the data partition to which the target resident identifier belongs as the target partition, and obtains the corresponding target resident information from the target partition based on the field set.

[0021] According to some embodiments of the present invention, the work order system further includes a second API, and after creating a target work order based on the target resident information, the method further includes:

[0022] The current first resident information is determined as the reference resident information, and the second API is configured based on the target resident identifier, the first field, and the reference resident information;

[0023] The second API is used to periodically obtain the first resident information based on the target resident identifier and the first field;

[0024] When the second API detects that the reference resident information corresponding to the same first field is different from the newly acquired first resident information, it generates a risk update instruction;

[0025] In response to the risk update instruction, the target risk level is redefined based on the target rule and the newly acquired first resident information;

[0026] The target work order is updated based on the redefined target risk level.

[0027] According to some embodiments of the present invention, after creating a target work order based on the target resident information, the method further includes:

[0028] Based on the target risk level and the first field, a first follow-up account is determined from multiple preset follow-up accounts, wherein each preset follow-up account is associated with at least one preset risk level, and each preset risk level is associated with multiple preset fields;

[0029] The target work order is assigned to the first follow-up account;

[0030] The target work order is generated based on the communication feedback information entered by the first follow-up account.

[0031] According to some embodiments of the present invention, the target work order is transferred based on the communication feedback information entered by the first follow-up account, including:

[0032] When the communication feedback information is used to characterize the failure of contact, the target processing time of the target work order is determined based on a preset duration, and the target work order is reassigned based on the processing time.

[0033] Alternatively, if the communication feedback information contains any second follow-up account, the target work order is assigned to the second follow-up account, and the communication feedback information is displayed in the first style on the target work order.

[0034] Secondly, embodiments of the present invention provide a work order management device based on multi-system linkage, including at least one control processor and a memory for communicatively connecting with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to perform the work order management method based on multi-system linkage as described in the first aspect above.

[0035] Thirdly, embodiments of the present invention provide an electronic device including a work order management device based on multi-system linkage as described in the second aspect above.

[0036] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing computer-executable instructions, the computer-executable instructions being used to execute the work order management method based on multi-system linkage as described in the first aspect above.

[0037] The work order management method based on multi-system linkage according to embodiments of the present invention has at least the following beneficial effects: A target rule is selected from multiple preset rules, and the hierarchical field of the target rule is determined as a first field; in response to randomly selecting a target resident identifier from multiple candidate resident identifiers, target resident information corresponding to each of the preset fields is obtained from the data lake based on the target resident identifier; a target risk level is determined based on the target rule and the first resident information corresponding to the first field; and the key field corresponding to the target risk level is determined as a second field; a target work order is created based on the target resident information; the first resident information is displayed based on a preset first style; and the second resident information corresponding to the second field is displayed based on a preset second style. According to the technical solution of embodiments of the present invention, the target risk level of a resident can be assessed using the first resident information, and the second resident information can be dynamically determined based on the target risk level. Different display styles enable follow-up personnel to quickly locate the first and second resident information from the follow-up work order, improving the readability of the follow-up work order and increasing follow-up efficiency. Attached Figure Description

[0038] Figure 1 This is a schematic diagram of a work order system provided in one embodiment of the present invention;

[0039] Figure 2 This is a flowchart of a work order management method based on multi-system linkage provided in another embodiment of the present invention;

[0040] Figure 3 This is a schematic diagram of a configuration preset rule provided in another embodiment of the present invention;

[0041] Figure 4 This is a structural diagram of a work order management device based on multi-system linkage provided in another embodiment of the present invention. Detailed Implementation

[0042] Embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0043] In the description of this invention, it should be understood that the orientation descriptions, such as up, down, front, back, left, right, etc., are based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limiting this invention.

[0044] In the description of this invention, "several" means one or more, "multiple" means two or more, "greater than," "less than," and "exceeding" are understood to exclude the stated number, while "above," "below," and "within" are understood to include the stated number. The use of "first" and "second" in the description is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly indicating the number of indicated technical features, or implicitly indicating the order of the indicated technical features.

[0045] In the description of this invention, unless otherwise explicitly defined, terms such as "set up," "install," and "connect" should be interpreted broadly, and those skilled in the art can reasonably determine the specific meaning of the above terms in this invention in conjunction with the specific content of the technical solution.

[0046] This invention provides a work order management method, apparatus, device, and medium based on multi-system linkage. The work order management method includes: selecting a target rule from multiple preset rules, and determining the hierarchical field of the target rule as a first field; responding to randomly selecting a target resident identifier from multiple candidate resident identifiers, obtaining target resident information corresponding to each of the preset fields from the data lake based on the target resident identifier, determining a target risk level based on the target rule and the first resident information corresponding to the first field, and determining the key field corresponding to the target risk level as a second field; creating a target work order based on the target resident information, displaying the first resident information based on a preset first style, and displaying the second resident information corresponding to the second field based on a preset second style. According to the technical solution of this invention, the target risk level of a resident can be assessed using the first resident information, and the second resident information can be dynamically determined based on the target risk level. Different display styles allow follow-up personnel to quickly locate the first and second resident information from the follow-up work order, improving the readability of the follow-up work order and increasing follow-up efficiency.

[0047] First, refer to Figure 1 , Figure 1 This is a schematic diagram of a work order system provided in an embodiment of the present invention. In this embodiment, the work order system 10 is communicatively connected to a data lake 20. The data lake 20 includes multiple preset fields. The work order system 10 is configured with multiple preset rules. The preset rules include multiple hierarchical fields and preset risk levels. The field values ​​of the hierarchical fields corresponding to each preset risk level are different. Each preset risk level is associated with multiple key fields. The hierarchical fields and key fields belong to the preset fields.

[0048] It should be noted that the work order system 10 can be developed based on a Product Management System (PMS). The data lake 20 communicates with the work order system 10. The work order system 10 saves all collected data to the data lake 20 and stores it by field. In this embodiment, the preset fields are all the data fields required by the work order template. The preset fields can be all the fields stored in the data lake 20, or they can be some of the fields, as long as the preset fields can meet the requirements of the work order template. The preset fields can be work order-related data fields, such as... Figure 1 The terms "age of the bill", "amount owed", "occupation", and "resident's name" shown are not specified here.

[0049] It should be noted that this embodiment uses 10 preset rules in the work order system, and each preset rule corresponds to the same preset risk level, for example... Figure 1 As shown, each preset rule includes high-risk, medium-risk, and low-risk levels. Of course, corresponding risk levels can be added or removed. We won't impose many restrictions on the number of risk levels or the criteria for classification here, as long as different preset rules apply the same set of risk levels. Within the same preset rule, different risk levels correspond to the same grading fields, but the corresponding field values ​​are different. This allows for risk level classification based on the field values ​​of the grading fields, which will not be elaborated upon further here.

[0050] It should be noted that different preset rules can have the same or different grading fields. If two preset rules have the same grading fields, the field values ​​for each risk level will be different. For example, two preset rules might be "High Standard Overdue Payment Rule" and "Low Standard Overdue Payment Rule," both including the "Overdue Amount" field. The "High Standard Overdue Payment Rule" might have a field value greater than 10,000 for the high-risk level, while the "Low Standard Overdue Payment Rule" could have a value greater than 5,000, and so on. If different preset rules have the same grading fields, at least one field value will be different, thus distinguishing different grading standards. For example... Figure 1 As shown, the grading fields for "High Standard Overdue Payment Rule" and "Occupational Risk Follow-up" are different. "High Standard Overdue Payment Rule" focuses more on the amount of overdue payment, while "Occupational Risk Follow-up" focuses more on whether the resident's occupation and income can afford the overdue payment. Different preset rules select different grading fields according to actual needs, thereby realizing different grading rules.

[0051] It should be noted that the fields required to be displayed may differ for different preset risk levels. For example, for residents at high risk levels, a larger amount of resident information needs to be considered when formulating a follow-up strategy, while for residents at low risk levels, less resident information is required, and a simple reminder may suffice. Based on this, this embodiment sets different key fields for different preset risk levels. These key fields represent the resident information that must be displayed in the target work order under that preset risk level, in addition to the classification fields. For example... Figure 1 As shown, the key fields for high-risk levels include "Occupation," "Family Income," and "Whether a Loan is Available," while "Whether a Loan is Available" is omitted for medium-risk levels, and so on. Both key fields and tiered fields are preset fields, and they are mutually exclusive to avoid displaying the same content repeatedly in the target work order.

[0052] Reference Figure 2 , Figure 2 The flowchart illustrates a work order management method based on multi-system linkage, as provided in this embodiment of the invention. This method includes, but is not limited to, the following steps:

[0053] S10: Select the target rule from multiple preset rules and determine the hierarchical field of the target rule as the first field.

[0054] It should be noted that after logging into the work order system, the system can display various preset rules through a visual interface. The follow-up personnel can select a target rule from multiple preset rules according to the follow-up needs, and the work order system will automatically determine the hierarchical field corresponding to the target rule as the first field.

[0055] For example, such as Figure 1 As shown, the property management department determined that the high-standard overdue payment rule would be used as the target rule for this follow-up visit based on management needs. After logging into the work order system, each follow-up visitor selected "high-standard overdue payment rule" as the target rule, which triggered the work order system to set the "age of overdue payment" and "amount of overdue payment" as the first fields.

[0056] S20, in response to selecting a target resident identifier from multiple candidate resident identifiers, obtaining the target resident information corresponding to each preset field from the data lake based on the target resident identifier, determining the target risk level based on the target rule and the first resident information corresponding to the first field, and determining the key field corresponding to the target risk level as the second field.

[0057] It should be noted that after selecting the target rule, the work order system displays multiple candidate resident identifiers. Each candidate resident identifier corresponds to a follow-up user. In order to improve the efficiency of the follow-up, each follow-up person selects one target resident identifier at a time. After generating the target work order and completing the follow-up operation, the next target resident identifier is selected to execute the technical solution of this embodiment. This will not be repeated hereafter.

[0058] It is worth noting that this embodiment configures a rule engine in the work order system. Preset rules are configured in the rule engine. After the follow-up personnel select the target rule, the rule engine automatically calls the first field of the target rule to obtain data and determine the risk level. The independent rule engine can simplify the configuration of the work order system. Once the preset rule is configured, it can be reused, which improves the convenience of configuration.

[0059] It should be noted that in this embodiment, the target resident identifier and target rule are sent to the rule engine. The rule engine obtains the target resident information of all preset fields from the data lake according to the target resident identifier based on the request initiated by each follow-up visitor. Then, it filters out the first resident information based on the first field and runs the target rule to compare the first resident information with the field values ​​of each preset risk level. The target risk level of the current follow-up resident is determined in each preset risk level of the target rule.

[0060] It should be noted that since the key fields corresponding to each preset risk level are different, after determining the target risk level, the key field of the target risk level is determined as the second field, and the target resident information corresponding to the first and second fields is determined as the information that residents need to pay attention to under the target risk level. This allows for flexible adjustment of the resident information specially displayed in the target work order according to the resident's risk level, thereby improving the readability of the target work order.

[0061] For example, such as Figure 1 As shown, the target household identifier selected in the work order system 10 is "Household A". The rule engine is configured according to "Household A" and "high standard arrears rule". The rule engine obtains the target household information corresponding to "Household A" from the data lake 20. The first field includes "age" and "arrears amount". The corresponding first household information is "1 year" and "500" respectively. The rule engine determines the target risk level as low risk level based on the above information, and thus determines the key field "family income" as the second field.

[0062] S30: Create a target work order based on the target resident information, display the first resident information based on the preset first style, and display the second resident information corresponding to the second field based on the preset second style.

[0063] It should be noted that, according to the description of the above embodiments, the preset fields correspond to all the contents required by the work order template, that is, the target resident information is all the contents of the work order template. Creating a target work order based on the work order template is a technique well known to those skilled in the art, and the method of creating the work order will not be described in detail here.

[0064] It should be noted that after determining the second field, the target resident information corresponding to the second field is determined as the second resident information. In this embodiment, the first resident information is displayed in the target work order using the first style, the second resident information is displayed using the second style, and the remaining target resident information can be displayed using the third style.

[0065] It is worth noting that the first and second resident information in this embodiment are determined based on target rules and different resident dynamics. Therefore, it is impossible to configure a work order template for each resident. Only a general work order template can be used. The content layout of the general work order template must be pre-configured. Therefore, when there are multiple first and second resident information, it is difficult to ensure that the first and second resident information of each resident are displayed in the same area. It is very likely that multiple first and second resident information are displayed in a scattered manner in the target work order interface. Based on this, this embodiment does not adjust the display position of each target resident information in the target work order, but displays the first resident information, second resident information and other information in different styles, so that the follow-up personnel can visually identify the first resident information used for risk assessment and the second resident information that needs to be used for key follow-up visits.

[0066] For example, such as Figure 1 As shown, the first style is bold text, and the second style is italic text. After creating the target work order, the first resident's information is displayed in bold text. Even if the "Age of Payment" and "Amount in Arrears" are not displayed adjacently, the follow-up personnel can quickly identify the bold text visually, thereby quickly locating the first resident's information in the target work order and determining the basis for assessing the user's risk level. Similarly, the follow-up personnel can quickly identify the italic text visually and quickly locate the second resident's information in the target work order, which will not be repeated here.

[0067] In another embodiment, before performing step S10, the following steps are included, but are not limited to:

[0068] S01, Construct a rule list in the visual interface, where each column of the rule list corresponds to a preset risk level, and each row corresponds to a preset rule's classification field and key fields under each preset risk level;

[0069] S02, when a rule to be edited is selected from the rule list, the preset fields other than the hierarchical fields and key fields of the rule to be edited are identified as candidate fields, each candidate field is displayed outside the rule list, the hierarchical fields and key fields corresponding to the rule to be edited are unlocked, and in response to the drag operation based on any preset field in the visualization interface, the dragged preset field is added to the released hierarchical fields and key fields, or the preset field dragged out of the rule list is identified as a candidate field;

[0070] S03, in response to the rule creation command in the visual interface, displays each preset field outside the rule list, creates a new rule in the rule list, and adds the corresponding hierarchical fields and key fields to the new rule in response to the drag operation.

[0071] It should be noted that before creating a target work order, preset rules can be created or modified in the work order system. After logging into the work order system, administrators can select the relevant configuration options to enter the visual interface, build a rule list in the visual interface, and complete the editing and creation of preset rules through visual operations.

[0072] It should be noted that different preset rules correspond to the same risk level. In this embodiment, each column in the rule list corresponds to a preset risk level, and each row corresponds to a grading field for a preset rule and key fields under each preset risk level. The grading field and key fields can be displayed on separate lines, such as... Figure 3 As shown, the rule list includes three columns: high risk level, medium risk level, and low risk level. Each row corresponds to a preset rule, and each row corresponding to a preset rule is further divided into two smaller rows. The first row corresponds to the grading field. Since the grading fields for each preset risk level are the same, only the conditions for the corresponding field values ​​differ, the grading fields can be displayed using merged cells. The key fields corresponding to each preset risk level are different, for example... Figure 3 As shown, the key fields for high-risk levels in Rule 1 include occupation, household income, and loan status; the key fields for medium-risk levels include occupation and household income, and so on.

[0073] It should be noted that after visualizing the various preset rules through a rule list, a rule to be edited can be selected by clicking on it, unlocking its hierarchical and key fields to make it editable. Simultaneously, candidate fields are displayed outside the corresponding rule list. Since these candidate fields are preset fields other than the hierarchical and key fields, each preset rule can have different candidate fields, enabling dynamic display of candidate fields based on different preset rules.

[0074] It should be noted that after displaying the candidate fields, including the key fields and hierarchical fields of the rules to be edited, all the preset fields are already displayed in the visualization interface. In this embodiment, the fields are configured by dragging. For example, a candidate field can be dragged into the hierarchical field to make it a new hierarchical field, or a key field can be dragged out of the corresponding preset risk level so that it is no longer identified as a key field, or when a key field is dragged into the hierarchical field, all preset risk levels will delete the corresponding key fields to ensure that they are not displayed repeatedly. The dragging operation can effectively simplify the operation and improve the visualization, thereby improving the efficiency of rule editing.

[0075] It should be noted that, similar to editing, a create button can be configured in the visual interface to trigger the rule creation command. At this time, various preset fields can be displayed outside the rule list, and a new row can be added to the rule list as a new rule. The configuration of hierarchical fields and key fields can be achieved through the same drag-and-drop method as described above, which will not be repeated here.

[0076] Additionally, in one embodiment, reference is made to Figure 1 The work order system has a first API, which has preset formats for each preset field. In step S20, the target resident information corresponding to each preset field is obtained from the data lake based on the target resident identifier. This includes, but is not limited to, the following steps:

[0077] S211, Configure the first API based on the target resident identifier and the first field, so that the first API determines the preset fields other than the first field as the third field, and determines the target format corresponding to each first field;

[0078] S212, the first API performs a data acquisition operation based on the target resident identifier and the first field to obtain the first resident information from the data lake;

[0079] S213, based on any first resident information, determine the target format through the first API according to the corresponding first field, and verify the first resident information based on the target format;

[0080] S214, once the information of each first resident has been verified, perform a data acquisition operation based on the target resident identifier and the third field through the first API to obtain the remaining target resident information from the data lake.

[0081] It should be noted that in this embodiment, a first API is built into the work order system, and the preset format of each preset field is set in the first API. After each follow-up visitor selects the target resident identifier and target rule, the first API is configured based on the target resident identifier and the first field. The first API first identifies the preset fields other than the first field as the third field. Since the target resident information has a large amount of data, this embodiment obtains the target resident information in two steps through the first API.

[0082] The first API first retrieves the first resident information from the data lake based on the first field. It then performs format validation on the more important first resident information in the target work order. This ensures the data integrity of the first resident information and verifies the reliability of communication with the data lake. It can retrieve the first resident information with the correct format from the data lake. After the validation is passed, the first API can then retrieve the remaining information from the data lake based on the third field.

[0083] Additionally, in one embodiment, reference is made to Figure 1 The data lake comprises multiple data partitions, each associated with multiple resident identifiers. Each data partition has a predefined field. The data acquisition operations in steps S212 and S214 include:

[0084] S221, construct a field set through the first API, wherein the field set includes all of the first field, or includes all of the third field;

[0085] S222, construct a target query instruction based on the target resident identifier and field set, and send the target query instruction to the data lake so that the data lake determines the data partition to which the target resident identifier belongs as the target partition, and obtains the corresponding target resident information from the target partition based on the field set.

[0086] It should be noted that in this embodiment, the data lake is divided into multiple data partitions, each corresponding to a community. The resident identifiers of the same community are stored in the data partition as the partition resident identifiers, thereby achieving data isolation between different communities and enabling unified follow-up visits through the work order system.

[0087] For example, such as Figure 1 As shown, the data lake 20 includes a first data partition 21 and a second data partition 22. Both the first data partition 21 and the second data partition 22 include all the preset fields. The partition user identifier stored in the first data partition 21 is different from that in the second data partition 22.

[0088] It should be noted that the first data retrieval operation of the first API is based on the first field, and the second is based on the third field. Therefore, during the first data retrieval operation, the field set includes all of the first field, and during the second data retrieval operation, the field set includes all of the third field. For the sake of describing the traversal, the following explanation will assume that the field set includes all of the first field.

[0089] It should be noted that the first API first constructs a target query instruction based on the target resident identifier and field set. The data lake first traverses each data partition to determine the target partition based on the target resident identifier, and then obtains the corresponding target resident information from the target partition.

[0090] In addition, in one embodiment, the work order system also has a pre-defined second API. In step S30, after creating a target work order based on the target resident information, the system further includes, but is not limited to, the following steps:

[0091] S31, determine the current first resident information as the reference resident information, and configure the second API based on the target resident identifier, the first field, and the reference resident information;

[0092] S32, periodically obtain the first resident information based on the target resident identifier and the first field through the second API;

[0093] S33, when the second API detects that the reference resident information corresponding to the same first field is different from the newly acquired first resident information, a risk update instruction is generated;

[0094] S34, in response to the risk update instruction, redetermines the target risk level based on the target rules and newly acquired first resident information;

[0095] S35, Update the target work order based on the redefined target risk level.

[0096] It should be noted that after creating a target work order, the current first resident information is recorded in the second API as reference resident information, and associated with the corresponding target resident identifier and the first field. The data acquisition cycle is preset in the second API, for example, set to one day, so that the second API can periodically update the data starting from the day after the target work order is generated. The specific cycle can be set according to actual needs.

[0097] It is worth noting that the target work order is used for follow-up visits. After the follow-up visits, it is possible that the resident will pay the outstanding fees, or new arrears may be incurred. Therefore, this embodiment uses a second API to compare the newly acquired first resident information with the reference resident information, for example, comparing... Figure 1The outstanding amount shown is used to generate a risk update instruction when it changes. Based on the technical solution of the above embodiment, the target risk level is redefined. If the target risk level remains unchanged, only the corresponding target resident information is updated in the target work order. If the target risk level changes, the key fields also change accordingly. Therefore, it is necessary to redefine the second resident information based on the new key fields and display the latest second resident information in the target work order using the second style. This embodiment sets up a second API in the work order system to automatically track data changes in the target work order, improving the timeliness of work order processing.

[0098] In another embodiment, after step S30 is performed, the following steps are included, but are not limited to:

[0099] S41, determine the first follow-up account from multiple preset follow-up accounts based on the target risk level and the first field, wherein each preset follow-up account is associated with at least one preset risk level, and each preset risk level is associated with multiple preset fields;

[0100] S42, assign the target work order to the first follow-up account;

[0101] S43, based on the communication feedback information entered by the first follow-up account, the target work order is transferred.

[0102] It should be noted that this embodiment conducts risk assessment on residents based on the first resident's information. Different target risk levels, and different information related to those risk levels, require different communication skills during follow-up visits. For example, some follow-up personnel are more adept at follow-up communication after risk assessment based on occupation, while others are more adept at follow-up communication after risk assessment based on outstanding payments. Therefore, this embodiment sets at least one preset risk level and preset field for each preset follow-up account. After generating a target work order, a suitable first follow-up account can be matched based on the target risk level and the first field, thereby improving the success rate of follow-up visits.

[0103] It should be noted that after assigning a target work order to the first follow-up account, the target work order can be automatically routed upon receiving the communication feedback information entered by the first follow-up account. For example, if the communication feedback information records that the outstanding payment has been completed, the target work order will be automatically closed and archived. This embodiment pre-sets multiple types of feedback information routing strategies in the work order system. After the follow-up personnel select the corresponding communication feedback information, it will be automatically routed according to the corresponding routing strategy, improving work order management efficiency.

[0104] In another embodiment, step S43 specifically includes, but is not limited to, the following steps:

[0105] S431, when communication feedback information is used to characterize contact failure, the target processing time of the target work order is determined based on the preset duration, and the target work order is reassigned based on the target processing time.

[0106] S432, when the communication feedback information records any second follow-up account, the target work order is assigned to the second follow-up account, and the communication feedback information is displayed in the first style on the target work order.

[0107] It should be noted that when communication feedback information is used to indicate contact failure, it can be determined that the resident cannot be contacted. In this embodiment, the target processing time of the target work order is determined according to the preset time. After the target processing time is reached, the target work order is reassigned, which can realize the automatic flow of the target work order. Follow-up visits are usually not continuous events, so the preset time is usually long, such as one day or one week. If only the same first follow-up account can continue to perform the follow-up visits, the first follow-up account may be affected by the large number of work orders, thus affecting the timeliness of the follow-up visits. Therefore, in this embodiment, the work order is reassigned after the target processing time is reached, thereby improving the efficiency of work order processing.

[0108] It should be noted that when the communication feedback information includes a second follow-up account, it indicates that the target work order needs to be handled by a follow-up personnel with a different position or rank. For example, if the overdue payment collection changes from property management collection to lawyer's letter collection, the second follow-up account needs to be changed to a legal-related follow-up personnel. After the target work order is sent to the second follow-up account, it will be displayed in the same way to ensure that the other follow-up personnel can also quickly grasp the key information visually. At the same time, it is more important for the follow-up personnel to know the content of the first style. Therefore, this embodiment displays the communication feedback information in the first style in the target work order to increase the importance of the communication feedback information.

[0109] like Figure 4 As shown, Figure 4 This is a structural diagram of a work order management device based on multi-system linkage provided in one embodiment of the present invention. The present invention also provides a work order management device based on multi-system linkage, comprising:

[0110] The processor 401 can be implemented using a general-purpose central processing unit (CPU), microprocessor, application specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.

[0111] The memory 402 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 402 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 402 and is called and executed by the processor 401 to implement the work order management method based on multi-system linkage of the embodiments of this application.

[0112] Input / output interface 403 is used to implement information input and output;

[0113] The communication interface 404 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0114] Bus 405 transmits information between various components of the device (e.g., processors 401 and 402, input / output interface 403 and communication interface 404);

[0115] The processor 401 and device 402, input / output interface 403 and communication interface 404 are connected to each other within the device via bus 405.

[0116] This application also provides an electronic device, including the work order management device based on multi-system linkage as described above.

[0117] This application embodiment also provides a storage medium, which is a computer-readable storage medium, storing a computer program. When the computer program is executed by a processor, it implements the above-described work order management method based on multi-system linkage.

[0118] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof. The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate, and may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0119] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically include computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0120] The above provides a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of the present invention.

Claims

1. A work order management method based on multi-system linkage, characterized in that, The method is applied to a work order system that communicates with a data lake. The data lake includes multiple preset fields, and the work order system has multiple preset rules. Each preset rule includes multiple hierarchical fields and preset risk levels. The field values ​​of the hierarchical fields corresponding to each preset risk level are different. Each preset risk level is associated with multiple key fields, and the hierarchical fields and key fields belong to the preset fields. The method includes: Select a target rule from multiple preset rules, and determine the hierarchical field of the target rule as the first field; In response to selecting a target resident identifier from multiple candidate resident identifiers, the target resident information corresponding to each of the preset fields is obtained from the data lake based on the target resident identifier. The target risk level is determined based on the target rule and the first resident information corresponding to the first field. The key field corresponding to the target risk level is determined as the second field. A target work order is created based on the target resident information. The first resident information is displayed based on a preset first style, and the second resident information corresponding to the second field is displayed based on a preset second style. The first style is bold font, and the second style is italic font.

2. The work order management method based on multi-system linkage according to claim 1, characterized in that, Before selecting a target rule from multiple preset rules, the method further includes: A rule list is constructed in the visualization interface, wherein each column of the rule list corresponds to a preset risk level, and each row corresponds to the classification field of a preset rule and the key field under each preset risk level; When a rule to be edited is selected from the rule list, the preset fields other than the hierarchical fields and the key fields of the rule to be edited are determined as candidate fields. Each candidate field is displayed outside the rule list. The hierarchical fields and the key fields corresponding to the rule to be edited are unlocked. In response to a drag operation based on any preset field in the visualization interface, the dragged preset field is added to the released hierarchical fields and the key fields, or the preset field dragged out of the rule list is determined as the candidate field. Alternatively, in response to the rule creation instruction on the visualization interface, each of the preset fields is displayed outside the rule list, a new rule is created in the rule list, and in response to the drag operation, the corresponding hierarchical field and the key field are added to the new rule.

3. The work order management method based on multi-system linkage according to claim 1, characterized in that, The work order system has a first API, which has preset formats corresponding to each preset field. Based on the target resident identifier, it retrieves the target resident information corresponding to each preset field from the data lake, including: The first API is configured based on the target resident identifier and the first field, so that the first API determines the preset field other than the first field as the third field and determines the target format corresponding to each of the first fields. The first API performs a data acquisition operation based on the target resident identifier and the first field to obtain the first resident information from the data lake; Based on any of the first resident information, the first API is used to determine the target format according to the corresponding first field, and the first resident information is verified based on the target format; Once each piece of information for the first resident has passed verification, the data acquisition operation is performed via the first API based on the target resident identifier and the third field to obtain the remaining target resident information from the data lake.

4. The work order management method based on multi-system linkage according to claim 3, characterized in that, The data lake includes multiple data partitions, each data partition is associated with multiple partition resident identifiers, and each data partition is configured with a preset field. The data acquisition operation includes: A field set is constructed using the first API, wherein the field set includes all of the first field, or all of the third field; A target query instruction is constructed based on the target resident identifier and the field set, and the target query instruction is sent to the data lake so that the data lake determines the data partition to which the target resident identifier belongs as the target partition, and obtains the corresponding target resident information from the target partition based on the field set.

5. The work order management method based on multi-system linkage according to claim 3, characterized in that, The work order system also has a pre-defined second API. After creating a target work order based on the target resident information, the method further includes: The current first resident information is determined as the reference resident information, and the second API is configured based on the target resident identifier, the first field, and the reference resident information; The second API is used to periodically obtain the first resident information based on the target resident identifier and the first field; When the second API detects that the reference resident information corresponding to the same first field is different from the newly acquired first resident information, it generates a risk update instruction; In response to the risk update instruction, the target risk level is redefined based on the target rule and the newly acquired first resident information; The target work order is updated based on the redefined target risk level.

6. The work order management method based on multi-system linkage according to claim 1, characterized in that, After creating a target work order based on the target resident information, the method further includes: Based on the target risk level and the first field, a first follow-up account is determined from multiple preset follow-up accounts, wherein each preset follow-up account is associated with at least one preset risk level, and each preset risk level is associated with multiple preset fields; The target work order is assigned to the first follow-up account; The target work order is generated based on the communication feedback information entered by the first follow-up account.

7. The work order management method based on multi-system linkage according to claim 6, characterized in that, The target work order is processed based on the communication feedback information entered by the first follow-up account, including: When the communication feedback information is used to characterize the failure of contact, the target processing time of the target work order is determined based on a preset duration, and the target work order is reassigned based on the processing time. Alternatively, if the communication feedback information contains any second follow-up account, the target work order is assigned to the second follow-up account, and the communication feedback information is displayed in the first style on the target work order.

8. A work order management device based on multi-system linkage, characterized in that, It includes at least one control processor and a memory for communicatively connecting to the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, the instructions being executed by the at least one control processor to enable the at least one control processor to perform the work order management method based on multi-system linkage as described in any one of claims 1 to 7.

9. An electronic device, characterized in that, It includes the work order management device based on multi-system linkage as described in claim 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing a computer to execute the work order management method based on multi-system linkage as described in any one of claims 1 to 7.

Images