IP Library › Granted Patent US 10,713,110
Granted Patent B2
US 10,713,110 · App. 15/937,193 · Granted Jul 14, 2020

Automated issue detection and resolution framework for enterprise resource planning

Inventors: Emmanuel Benbinuto Antonio (Mandaluyong, PH); Darwin Endaya Flores (Pampanga, PH); Joseph Christian Policarpio Tamayo (Pasig, TW); John Carlo Canlubo De Guzman (Laguna, PH); Raye Willson Paez Raymundo (Cavite, PH)
Assignee: Accenture Global Solutions Limited
G06F11/0793G06F11/0706G06F11/0751G06F11/302G06F11/3003G06F11/3495G06Q10/0631H04L9/3226G06F8/60
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,713,110
App. No.
15/937,193
Filed
Mar 27, 2018
Granted
Jul 14, 2020
Kind
B2
Art Unit
2114
USPC
714/15
Abstract

In some possible implementations, an operations platform may include one or more memories; and one or more processors, communicatively coupled to the one or more memories, to: monitor a client platform without interacting with a user interface of the client platform; detect an issue associated with the client platform based on monitoring the client platform; determine whether the operations platform has access to a bot to resolve the issue; generate the bot when the operations platform does not have access to the bot; and deploy the bot with regard to the client platform to resolve the issue, wherein the bot is configured to resolve the issue without interacting with the user interface of the client platform.

Claims (72)

1. An operations platform, comprising:

one or more memories; and

one or more processors, communicatively coupled to the one or more memories, to:

monitor a client platform without interacting with a user interface of the client platform;

detect an issue associated with the client platform based on monitoring the client platform;

determine that the operations platform does not have access to a bot to resolve the issue;

identify, based on determining that the operations platform does not have access to the bot to resolve the issue, first bot and a second bot that correspond to the issue;

generate the bot by combining the first bot and the second bot,

wherein the one or more processors, when generating the bot, are to:

generate the bot by modifying code of at least one of the first bot or the second bot; and

deploy the bot with regard to the client platform to resolve the issue,

wherein the bot is configured to resolve the issue without interacting with the user interface of the client platform.

2. The operations platform of claim 1 , wherein the client platform is associated with an enterprise resource planning system.

3. The operations platform of claim 1 , wherein the bot is an initial bot and the issue is a first issue; and

wherein the one or more processors are further to:

receive an instruction to deploy a subsequent bot associated with a second issue; and

deploy the subsequent bot to resolve the second issue.

4. The operations platform of claim 3 , wherein the one or more processors are further to:

receive security information in association with the instruction,

the security information including an encrypted bot identifier for the subsequent bot; and

wherein the one or more processors, when deploying the subsequent bot, are to:

deploy the subsequent bot based on the security information.

5. The operations platform of claim 3 , wherein the one or more processors are further to:

perform a handshake before receiving the instruction; and

wherein the one or more processors, when deploying the subsequent bot, are to:

deploy the subsequent bot based on a result of the handshake.

6. The operations platform of claim 3 , wherein the second issue is a user-originated issue.

7. The operations platform of claim 6 , wherein the subsequent bot is configured to resolve the issue without interacting with the user interface of the client platform.

8. A method, comprising:

monitoring, by an operations platform, a client platform based on a monitor instruction;

detecting, by the operations platform, an issue associated with the client platform based on monitoring the client platform;

determining, by the operations platform, that the operations platform does not have access to a bot to resolve the issue;

identifying, by the operations platform and based on determining that the operations platform does not have access to the bot to resolve the issue, a first bot and a second bot that correspond to the issue,

generating, by the operations platform, the bot by combining the first bot and the second bot,

wherein generating the bot comprises modifying code of at least one of the first bot or the second bot; and

deploying, by the operations platform, the bot with regard to the client platform to resolve the issue,

wherein the bot is configured to resolve the issue without interacting with a user interface of the client platform.

9. The method of claim 8 , further comprising:

providing, for analysis, information that is gathered based on monitoring the client platform.

10. The method of claim 8 , further comprising:

performing analysis with regard to information that is gathered based on monitoring the client platform.

11. The method of claim 8 , further comprising:

receiving an instruction to deploy the bot,

wherein the instruction is received from an external device that is external to the client platform.

12. The method of claim 11 , wherein the external device is associated with a component associated with the operations platform, and wherein the instruction is provided with security information that is generated by the component.

13. The method of claim 8 , wherein the client platform is monitored without interaction with the user interface of the client platform.

14. The method of claim 8 , wherein the bot is initial bot, and wherein the method further comprises:

receiving an instruction to deploy a subsequent bot for resolving a user-originated issue,

wherein the instruction is received via an application programming interface of the operations platform; and

deploying the subsequent bot to resolve the user-originated issue.

15. The method of claim 14 , wherein the user-originated issue cannot be detected by monitoring the client platform.

16. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors of an operations platform, cause the one or more processors to:

identify an issue associated with a client platform that is capable of being resolved using a bot,

wherein the identification of the issue is based on one of:

information obtained by monitoring the client platform, or

receiving an instruction to execute the bot to resolve the issue;

determine that the bot is not accessible or not locally stored;

identify, based on determining that the bot is not accessible or not locally stored, a first bot and a second bot that correspond to the issue,

generate the bot by combining the first bot and the second bot,

wherein the one or more instructions, that cause the one or more processors to generate the bot, cause the one or more processors to:

generate the bot by modifying code of at least one of the first bot or the second bot; and

execute the bot with regard to the client platform to resolve the issue,

wherein the bot is configured to resolve the issue without interacting with a user interface of the client platform.

17. The non-transitory computer-readable medium of claim 16 , wherein the client platform comprises an enterprise resource planning platform.

18. The non-transitory computer-readable medium of claim 16 , where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

provide, for analysis, the information obtained by monitoring the client platform.

19. The non-transitory computer-readable medium of claim 16 , wherein the one or more instructions, when executed by the one or more processors, cause the one or more processors to:

receive the instruction in association with security information,

the security information being received from an external device that is external to the client platform, and

the security information being generated or provided by a component, associated with the operations platform, that operates on the external device.

20. The non-transitory computer-readable medium of claim 19 , wherein the instruction identifies the first bot and the second bot and wherein the security information includes a token that corresponds to the operations platform and the component.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 28, 2018
From: ANTONIO, EMMANUEL BENBINUTO; FLORES, DARWIN ENDAYA; TAMAYO, JOSEPH CHRISTIAN POLICARPIO; DE GUZMAN, JOHN CARLO CANLUBO; RAYMUNDO, RAYE WILLSON PAEZ
To: ACCENTURE GLOBAL SOLUTIONS LIMITED
Reel/Frame 045373/0178 →
Continuity (1)
Related Publication 20190303232A1 · Oct 3, 2019