Scheduling center system based on service request

Abstract

The invention relates to the technical field of business scheduling, in particular to a business request-based scheduling center system, which comprises a demand management end, a management auditing end, a scheme generation end and an operation end, and is characterized in that the demand management end generates a demand service list according to an external business request; the management auditing end allocates a corresponding scheme generation end according to the demand service list and sends the demand service list; the scheme generation end generates an implementation scheme according to the demand service list; and the demand management end allocates the implementation scheme to the corresponding operation end for execution. Aiming at the problem of poor management effect of an operation and maintenance platform in the prior art, in the scheme, a demand management end, a management auditing end, a scheme generation end and an operation operation end are arranged in a system according to different role distribution of an operation team, and a corresponding operation and maintenance scheme circulation strategy is formulated; the operation and maintenance scheme is well designed and implemented by designing different role tasks.

Description

Technical Field

[0001] The present invention relates to the technical field of business dispatching, and in particular to a dispatching center system based on business requests. Background Art

[0002] As domestic enterprises' informatization and digital transformation deepens, the application scope of big data platforms in governments and enterprises has also grown explosively. In this process, how to manage the external demand of big data platforms and the efficient and orderly internal work, and quantify and control the platform's operating costs and operating results during the management process, has become a new problem faced by big data platform managers.

[0003] In the prior art, there are already operation and maintenance solutions designed for big data systems. For example, Chinese patent CN201911386466.9 discloses a big data operation and maintenance management platform, including a control node and multiple sub-nodes, each of which has a pre-built python operation and maintenance library and is responsible for the operation and maintenance of one or more big data components. The control node can provide the operation mode of the big data component cluster to the outside world and send operation instructions to each node; each sub-node calls the python operation and maintenance library to perform corresponding operation and maintenance operations on the target big data component according to the big data component operation and maintenance operation instructions sent by the control node; wherein, the python operation and maintenance library includes multiple groups of operation and maintenance operation scripts and is used to provide a unified application programming interface for each operation and maintenance operation, and each operation and maintenance operation script is encapsulated using the pyhton language. The differences in specific operation and maintenance operation modes of different operating systems can be shielded, simplifying the writing of operation and maintenance operation scripts, which is conducive to reducing the complexity of the system, the difficulty of development, and the complexity of maintenance work.

[0004] For another example, Chinese patent CN202311136892.3 discloses an operation and maintenance method and system based on a big data automated operation and maintenance platform. The operation and maintenance method based on the big data automated operation and maintenance platform includes real-time collection and recording of various performance data of operation and maintenance platforms in various places; data preprocessing and data analysis based on the various performance data of operation and maintenance platforms in various places collected to obtain characteristic data of influencing factors; establishing the prediction model based on the characteristic data of influencing factors and history; real-time collection of various performance data of local operation and maintenance platforms; the operation and maintenance method and system based on the big data automated operation and maintenance platform can more intelligently update the usage of operation and maintenance platforms in various regions in real time, collect errors and alarm data in each platform, and update them to each operation and maintenance platform, so as to realize real-time data collection of operation and maintenance platforms, and real-time supervision of the stable operation of operation and maintenance platforms, and can give early warning based on the actual changes in various performance data.

[0005] However, during the actual implementation process, the inventor discovered that this type of technical solution had the problem of poor management effect during application. Summary of the invention

[0006] In view of the above problems existing in the prior art, a dispatch center system based on business requests is now provided.

[0007] The specific technical solutions are as follows:

[0008] A dispatch center system based on business requests, including interconnected demand management end, management review end, solution generation end, and operation end:

[0009] The demand management terminal generates a demand service order according to an external business request;

[0010] The management and review end allocates the corresponding solution generation end according to the service demand form and sends the service demand form;

[0011] The solution generation end generates a solution implementation plan according to the service demand sheet;

[0012] The demand management end allocates the implementation plan to the corresponding operation end for execution.

[0013] On the other hand, the demand management end includes:

[0014] A request receiving module, wherein the request receiving module receives the service request;

[0015] A field extraction module, the field extraction module is connected to the request receiving module, and the field extraction module extracts key fields from the business request;

[0016] A service order filling module, the service order filling module is connected to the field extraction module, and the service order filling module generates the demand service end according to the key fields.

[0017] On the other hand, the management and audit end includes:

[0018] A generating end storage module, wherein the generating end storage module stores a plurality of the scheme generating ends;

[0019] An allocation module, wherein the allocation module is connected to the generation end storage module, and the allocation module selects the solution generation end and sends the demand service form.

[0020] On the other hand, the management and audit end also includes:

[0021] A solution review module, wherein the solution review module receives the implementation plan output by the solution generation end;

[0022] The solution review module reviews the implementation plan, and sends the implementation plan to the demand management end when the review is passed.

[0023] On the other hand, the demand management end also includes:

[0024] An operation terminal storage module, wherein the operation terminal storage module stores a plurality of the operation terminals;

[0025] A work order splitting module, the work order splitting module is connected to the operation end storage module, and the work order splitting module splits the implementation plan to obtain multiple operation work orders corresponding to the operation end;

[0026] A work order sending module, wherein the work order sending module is connected to the work order splitting module, and the work order sending module sends the operation work order to the operation operation end.

[0027] On the other hand, the operation end includes:

[0028] A work order recording module, wherein the work order recording module generates a completed work order after completing the operation work order;

[0029] The demand management end also includes:

[0030] A first verification module receives the completed work order and generates a first review result.

[0031] On the other hand, the solution generation end includes:

[0032] The second verification module receives the completed work order when the first audit result is passed and verifies it according to the implementation plan to generate a second audit result.

[0033] On the other hand, the management and audit end includes:

[0034] A third verification module receives the completed work order and generates a third verification result when the second verification result is passed.

[0035] The above technical solution has the following advantages or beneficial effects:

[0036] In response to the problem of poor management effect of operation and maintenance platform in the existing technology, in this solution, the demand management end, management review end, solution generation end, and operation operation end are set up in the system according to the different role allocations of the operation team, and a corresponding operation and maintenance solution flow strategy is formulated. By designing different role tasks, better design and implementation of the operation and maintenance solution can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The embodiments of the present invention will be described more fully with reference to the attached drawings, which are provided for illustration and description only and are not intended to limit the scope of the present invention.

[0038] Figure 1 is an overall schematic diagram of an embodiment of the present invention;

[0039] Figure 2 is a schematic diagram of a request receiving module in an embodiment of the present invention;

[0040] Figure 3 This is a schematic diagram of an allocation module in an embodiment of the present invention;

[0041] Figure 4 A schematic diagram of a solution review module in an embodiment of the present invention;

[0042] Figure 5 This is a schematic diagram of a work order sending module in an embodiment of the present invention;

[0043] Figure 6 This is a schematic diagram of a work order recording module in an embodiment of the present invention;

[0044] Figure 7 Schematic diagram of a second verification module in an embodiment of the present invention;

[0045] Figure 8 Schematic diagram of the third verification module in an embodiment of the present invention. DETAILED DESCRIPTION

[0046] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0047] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other.

[0048] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments, but they are not intended to limit the present invention.

[0049] The present invention comprises:

[0050] A dispatch center system based on business requests, such as Figure 1 As shown, it includes the interconnected demand management terminal 1, management review terminal 2, solution generation terminal 3, and operation terminal 4:

[0051] Demand management terminal 1 generates demand service orders according to external business requests;

[0052] The management and review terminal 2 allocates the corresponding solution generation terminal 3 according to the service demand form and sends the service demand form;

[0053] The solution generation terminal 3 generates a solution implementation plan according to the service request form;

[0054] The demand management end 1 distributes the implementation plan to the corresponding operation end 4 for execution.

[0055] Specifically, in response to the problem of poor management effect of operation and maintenance platforms in the existing technology, in this solution, according to the different role allocations of the operation team, the demand management end 1, the management review end 2, the solution generation end 3, and the operation operation end 4 are set up in the system, and a corresponding operation and maintenance solution circulation strategy is formulated. By designing different role tasks, better design and implementation of the operation and maintenance solution can be achieved.

[0056] Specifically, the demand management terminal 1 is used to connect to the business requests on the user side. The business requests usually correspond to the operation and maintenance requirements of different big data platforms. The demand management terminal 1 designs this part of the business requests to form a corresponding demand service order.

[0057] Subsequently, the management and review end 2 reviews the demand service order to determine whether the corresponding business request is a normal demand. If it is a normal demand, it is transferred to the corresponding solution generation end 3 for processing.

[0058] After the solution generation end 3 generates the corresponding implementation plan according to the demand service order, the demand management end 1 will review and assign the implementation plan to the corresponding operation operation end 4 for execution, thereby achieving better operation and maintenance management effects.

[0059] In one embodiment, Figure 2 As shown, the demand management terminal 1 includes:

[0060] A request receiving module 11, wherein the request receiving module 11 receives a service request;

[0061] A field extraction module 12, the field extraction module 12 is connected to the request receiving module 11, and the field extraction module 12 extracts key fields from the business request;

[0062] The service order filling module 13 is connected to the field extraction module 12, and the service order filling module 13 generates a required service order according to key fields.

[0063] Specifically, in order to achieve a better effect of generating a demand service form, in this embodiment, firstly, the business request is received by the request receiving module 11. Since the business request comes from different operation and maintenance systems, it has different data sources and data formats, such as the remark text content filled in by the user. The field extraction module 12 extracts key fields from the business request, for example, extracts the corresponding fault code for the fault type message, generates a text summary for the text content through the semantic recognition model, etc. Finally, the service form filling module 13 generates a standardized demand service form based on the key fields, which is convenient for subsequent reading and review.

[0064] In one embodiment, Figure 3 As shown, the management audit terminal 2 includes:

[0065] A generating end storage module 21, the generating end storage module 21 stores a plurality of scheme generating ends 3;

[0066] The allocation module 22 is connected to the generation end storage module 21, and the allocation module 22 selects the solution generation end 3 and sends the service demand form.

[0067] Specifically, in order to achieve better operation and maintenance effects, in this embodiment, a generation end storage module 21 is set in the management and audit end 2. The generation end storage module 21 connects multiple solution generation ends and stores the corresponding working status respectively, and then updates the working status through heartbeat messages.

[0068] In the actual processing process, the allocation module 22 selects the solution generation terminal 3 and sends the demand service form. Specifically, the solution generation terminal 3 is first screened according to the service category pre-marked on the demand service form and the attributes constructed corresponding to the solution generation terminal 3 to obtain the qualified solution generation terminal 3, and then the solution generation terminal 3 that can actually execute the demand service form is determined according to the working status for allocation.

[0069] In one embodiment, Figure 4 As shown, the management and audit terminal 2 also includes:

[0070] A solution review module 23, which receives the implementation plan output by the solution generation end;

[0071] The solution review module 23 reviews the implementation plan, and sends the implementation plan to the demand management terminal 1 when the review is passed.

[0072] Specifically, in order to achieve a better control process of the operation and maintenance plan, in this embodiment, a plan review module 23 is also set in the management review terminal 2. When the plan generation terminal 3 initially generates an implementation plan, it first flows back to the management review terminal 2, and the implementation plan output by the plan generation terminal 3 is received and reviewed by the plan review module 23, mainly to determine the feasibility of the implementation plan and whether the demand service order can be completed. After confirmation, the implementation plan is sent to the demand management terminal 1, so as to achieve a better management effect.

[0073] In one embodiment, Figure 5 As shown, the demand management terminal 1 also includes:

[0074] The operation end storage module 14 stores a plurality of operation ends;

[0075] The work order splitting module 15 is connected to the operation end storage module 14, and the work order splitting module 15 splits the implementation plan to obtain multiple operation work orders corresponding to the operation end;

[0076] The work order sending module 16 is connected to the work order splitting module 15 , and the work order sending module 16 sends the operation work order to the operation operation terminal 4 .

[0077] Specifically, in order to achieve a better operation and maintenance process, in this embodiment, an operation terminal storage module 14 is also configured in the demand management terminal 1 to store multiple operation terminals 4, and the storage information includes fixed attributes and idle states of the operation terminals 4.

[0078] When an implementation plan to be executed is received, the work order splitting module 15 splits the implementation plan to obtain multiple operation work orders corresponding to the operation operation terminal 4, and then the work order sending module 16 identifies the fixed attributes and idle status of the operation operation terminal 4, and sends the operation work order to the available operation operation terminal 4 to perform the corresponding operation.

[0079] In one embodiment, Figure 6 As shown, the operation terminal 4 includes:

[0080] The work order recording module 41 generates a completed work order after completing the operation work order;

[0081] The demand management terminal 1 also includes:

[0082] The first verification module 17 receives the completed work order and generates a first verification result.

[0083] Specifically, in order to achieve better control and management of operation and maintenance operations, a work order recording module 41 is also set in this embodiment. The work order recording module 41 will record the corresponding debugging information when the operation terminal 4 performs the operation, and generate a completed work order according to the debugging information after completing the operation work order. Subsequently, the completed work order is transferred to the demand management terminal 1, and the first verification module 17 receives the completed work order and generates a first audit result to determine whether the split work order is executed. If the acceptance fails, it will be returned to the operation terminal 4 for re-execution.

[0084] In one embodiment, Figure 7 As shown, the solution generation terminal 3 includes:

[0085] The second verification module 31 receives the completed work order when the first audit result is passed and verifies it according to the implementation plan to generate a second audit result.

[0086] Specifically, in order to achieve better control and management of operation and maintenance operations, in this embodiment, a second verification module 31 is also set in the solution generation terminal 3. The second verification module 31 receives the completed work order when the first audit result is passed, and then checks the debugging information in the completed work order according to the implementation plan, determines whether the content reflected in the debugging information meets the expected results of the implementation plan and generates a second audit result. When the second audit result passes, it is circulated, and when it fails, it is returned to the operation terminal 4 for re-execution.

[0087] In one embodiment, Figure 8 As shown, the management audit terminal 2 includes:

[0088] The third verification module 24 receives the completed work order and generates a third verification result when the second verification result is passed.

[0089] Specifically, in order to achieve better control and management of operation and maintenance operations, in this embodiment, a third verification module 24 is also set in the management audit terminal 2. The second verification module 31 receives the completed work order when the second audit result is passed, and then checks the debugging information in the completed work order according to the implementation plan to determine whether the content reflected in the debugging information meets the expected results of the implementation plan and generate a third audit result. When the third audit result passes, it is circulated, and when it fails, it is returned to the operation operation terminal 4 for re-execution.

[0090] During implementation, the above circulation process can be reflected in the following steps:

[0091] Step 1: Use the requirements administrator account to log in to the tool, select the [Service Order Creation] menu under the [My Workstation] directory to enter the service order management page.

[0092] Step 2: Click the [Create New Service Order] button on the right side of the service order management page.

[0093] Step 3: Fill in the service ticket information form.

[0094] Step 4: Mount the service plan.

[0095] Step 5: Click the [Confirm Submission] button.

[0096] Step 6: Use the administrator account to log in to the tool, select the [To-do Service Desk] menu under the [My Workstation] directory, and enter the To-do Service Ticket Management page.

[0097] Step 7: Click [View Details] on the right side of the pending service order.

[0098] Step 8: Click the [Select Service Ticket Responsible Person] button.

[0099] Step 9: Select the service ticket manager.

[0100] Step 10: Click the [Start Operation] button to start operating the service order.

[0101] Step 11: Log in to the tool using the technical manager account responsible for the service order, select the [To-do Service Desk] menu under the [My Workstation] directory, and enter the To-do Service Ticket management page.

[0102] Step 12: Click [View Details] on the right side of the pending service order.

[0103] Step 13: Fill in the solution description and upload the solution file.

[0104] Step 14: Click the [Submit] button and the management will review the plan document.

[0105] Step 15: Use the management account to log in to the tool, select the [To-do Service Desk] menu under the [My Work Desk] directory, enter the To-do Service Ticket Management page, and click the [View Details] button or [Approval Return] button on the right side of the service ticket for the pending plan. If it is returned by approval, the technical manager needs to resubmit the plan file for approval.

[0106] Step 16: Click the [Approved] button and let the demand administrator split the service order and distribute the operation work order.

[0107] Step 17: Use the demand administrator account to log in to the tool, select the [To-do Service Desk] menu under the [My Workbench] directory, enter the to-do service order management page, and click the [View Details] button on the right side of the service order to be split.

[0108] Step 18: Click the [Add Work Order] button.

[0109] Step 19: Associate the secondary directory and the service specification.

[0110] Step 20: Click the [Click to select the undertaker] button to specify the undertaker's operation operator.

[0111] Step 21: Fill in other information of the operation work order.

[0112] Step 22: Click the [OK] button to send the operation work order.

[0113] Step 23: Use the operation operator account to log in to the tool, select the [To-do Service Desk] menu under the [My Work Desk] directory, enter the To-do Service Order Management page, click the [Operation Information] button on the right side of the To-do Service Order to start implementing the operation work order. If the operation cannot be performed, click the [Reject Work Order] button, and the demand administrator will need to reassign it to other operation operators for processing.

[0114] Step 24: Upload delivery documents.

[0115] Step 25: Use the demand administrator account to log in to the tool, select the [To-do Service Desk] menu under the [My Workbench] directory, enter the to-do service order management page, and click the [View Details] button on the right side of the to-do service order.

[0116] Step 26: Click the [Details] button to start accepting the delivery documents submitted by the operation operator. You can also click the [Failed Acceptance] button to reject the delivery documents and have them modified and optimized by the operation operator. Or close or delete this operation work order.

[0117] Step 27: Click the [Acceptance Passed] button and have the technical manager submit all the delivery documents of the service order.

[0118] Step 28: Use the demand administrator account to log in to the tool, select the [To-do Service Desk] menu under the [My Workbench] directory, enter the to-do service order management page, and click the [View Details] button on the right side of the to-do service order.

[0119] Step 29: Click the [Submit Deliverables] button.

[0120] Step 30: Click the [Confirm Submission] button to submit the service order delivery documents to the management for review.

[0121] Step 31: Use the management account to log in to the tool, select the [To-do Service Desk] menu under the [My Work Desk] directory, enter the To-do Service Order Management page, and click the [View Details] button or [Approval Return] button on the right side of the service order for the deliverable to be reviewed. If it is returned by approval, the technical manager needs to resubmit the service order delivery documents and resubmit it for approval.

[0122] Step 32: Click the [Approved] button to complete the service order.

[0123] Step 33: Score and evaluate the completion of the service order.

[0124] The above are only preferred embodiments of the present invention, and are not intended to limit the implementation methods and protection scope of the present invention. Those skilled in the art should be aware that all solutions obtained by equivalent substitutions and obvious changes made using the description and illustrations of the present invention should be included in the protection scope of the present invention.

Claims

1. A dispatch center system based on business requests, characterized in that: It includes the interconnected demand management end, management review end, solution generation end, and operation end: The demand management terminal generates a demand service order according to an external business request; The management and review end allocates the corresponding solution generation end according to the service demand form and sends the service demand form; The solution generation end generates a solution implementation plan according to the service demand sheet; The demand management end allocates the implementation plan to the corresponding operation end for execution.

2. The dispatch center system according to claim 1, characterized in that: The demand management end includes: A request receiving module, wherein the request receiving module receives the service request; A field extraction module, the field extraction module is connected to the request receiving module, and the field extraction module extracts key fields from the business request; A service order filling module, the service order filling module is connected to the field extraction module, and the service order filling module generates the required service order according to the key fields.

3. The dispatch center system according to claim 1, characterized in that: The management and audit end includes: A generating end storage module, wherein the generating end storage module stores a plurality of the scheme generating ends; An allocation module, wherein the allocation module is connected to the generation end storage module, and the allocation module selects the solution generation end and sends the demand service form.

4. The dispatch center system according to claim 1, characterized in that: The management and audit end also includes: A solution review module, wherein the solution review module receives the implementation plan output by the solution generation end; The solution review module reviews the implementation plan, and sends the implementation plan to the demand management end when the review is passed.

5. The dispatch center system according to claim 1, characterized in that: The demand management end also includes: An operation terminal storage module, wherein the operation terminal storage module stores a plurality of the operation terminals; A work order splitting module, the work order splitting module is connected to the operation end storage module, and the work order splitting module splits the implementation plan to obtain multiple operation work orders corresponding to the operation end; A work order sending module, wherein the work order sending module is connected to the work order splitting module, and the work order sending module sends the operation work order to the operation operation end.

6. The dispatch center system according to claim 5, characterized in that: The operation end includes: A work order recording module, wherein the work order recording module generates a completed work order after completing the operation work order; The demand management end also includes: A first verification module receives the completed work order and generates a first review result.

7. The dispatch center system according to claim 6, characterized in that: The solution generating end includes: The second verification module receives the completed work order when the first audit result is passed and verifies it according to the implementation plan to generate a second audit result.

8. The dispatch center system according to claim 7, characterized in that: The management and audit end includes: A third verification module receives the completed work order and generates a third verification result when the second verification result is passed.

Images