Abstract: Methods, devices, and non-transitory computer readable media that add interoperable BOTs to a stored BOT inventory. Each of the BOTs is associated with a BOT type, has a common structure, and automates at least a portion of an enterprise process. Assembly rules are obtained. Each of the assembly rules includes one or more constraints for inclusion of one or more of the BOTs in one or more of a plurality of workflows based on the one of the BOT types associated with each of the one or more of the BOTs. The workflows are assembled based on one or more the assembly rules. Each of the workflows comprises a subset of the BOTs and each BOT of the subsets of the BOTs is included in one or more of the workflows based on at least one of an associated functionality, performance, or service level. FIG. 2
Claims:WE CLAIM
1. A method for creating automated dynamic workflows of interoperable BOTs, the method comprising:
adding, by an enterprise BOT management computing device, a plurality of interoperable BOTs to a stored BOT inventory, wherein each of the BOTs is associated with one of a plurality of BOT types, has a common structure, and automates at least a portion of an enterprise process;
obtaining, by the enterprise BOT management computing device, a plurality of assembly rules each comprising one or more constraints for inclusion of one or more of the BOTs in one or more of a plurality of workflows based on the one of the BOT types associated with each of the one or more of the BOTs; and
assembling, by the enterprise BOT management computing device, the plurality of workflows each comprising a subset of the BOTs based on one or more the assembly rules, wherein each BOT of the subsets of the BOTs is included in one or more of the workflows based on at least one of an associated functionality, performance, or service level.
2. The method of claim 1, wherein:
each BOT of the subset of the BOTs for one of the workflows is included in the one of the workflows based on an associated functionality; and
at least one BOT of the subset of the BOTs for the one of the workflows is configured to select during execution a target BOT of the subset of the BOTs for the one of the workflows based on an output data type of output data generated by the at least one BOT of the subset of the BOTs for the one of the workflows and an input data type of input data for the target BOT of the subset of the BOTs for the one of the workflows.
3. The method of claim 1, wherein each BOT of the subset of the BOTs for one of the workflows is included in the one of the workflows based on an associated performance, and the method further comprises:
assembling, by the enterprise BOT management computing device, a plurality of test workflows based on a set of the assembly rules, each of the test workflows comprising a plurality of the BOTs having a same subset of the BOT types;
evaluating, by the enterprise BOT management computing device, each of the plurality of the BOTs during execution of the test workflows using test data to generate a BOT maturity value for each of the plurality of the BOTs; and
assembling, by the enterprise BOT management computing device, the one of the workflows to include at least one of the plurality of the BOTs having a highest associated one of the BOT maturity values for each BOT type in the same subset of the BOT types.
4. The method of claim 1, wherein:
each BOT of the subset of the BOTs for one of the workflows is included in the one of the workflows based on an associated service level;
each BOT of the first and second portions of the subset of the BOTs is configured to determine when a solution to a received request can be provided based on a generated confidence score, wherein the one of the workflows comprises at least a first level comprising the first portion of the subset of the BOTs having an associated first service level and a second level comprising the second portion of the subset of the BOTs having a second service level;
at least one BOT of the first portion of the subset of the BOTs is further configured to transfer the request to one BOT of the second portion of the subset of the BOTs, when the determining indicates that a solution to the request cannot be provided; and
at least one BOT of the second portion of the subset of the BOTs is further configured to provide resolution data to each BOT of the first portion of the subset of the BOTs, when the determining indicates that a solution to the request can be provided.
5. The method of claim 1, further comprising:
evaluating, by the enterprise BOT management computing device, each of the workflows during execution to generate a workflow performance value for each of the workflows, wherein the workflow performance value is based at least in part on a BOT maturity value for each BOT of the subset of the BOTs included in each of the workflows; and
outputting, by the enterprise BOT management computing device, one or more of the workflow performance values.
6. The method of claim 5, further comprising:
obtaining, by the enterprise BOT management computing device, a plurality of reward values, a plurality of penalty values, and a total number of serviced requests for each of the BOTs; and
generating, by the enterprise BOT management computing device, the BOT maturity value based on a difference between a sum of all of the reward values and a sum of all of the penalty values divided by the total number of serviced requests for each BOT of the subset of the BOTs included in each of the workflows.
7. An enterprise bot management computing device, comprising memory comprising programmed instructions stored in the memory and one or more processors configured to be capable of executing the programmed instructions stored in the memory to:
add a plurality of interoperable BOTs to a stored BOT inventory, wherein each of the BOTs is associated with one of a plurality of BOT types, has a common structure, and automates at least a portion of an enterprise process;
obtain a plurality of assembly rules each comprising one or more constraints for inclusion of one or more of the BOTs in one or more of a plurality of workflows based on the one of the BOT types associated with each of the one or more of the BOTs; and
assemble the plurality of workflows each comprising a subset of the BOTs based on one or more the assembly rules, wherein each BOT of the subsets of the BOTs is included in one or more of the workflows based on at least one of an associated functionality, performance, or service level.
8. The enterprise bot management computing device of claim 7, wherein:
each BOT of the subset of the BOTs for one of the workflows is included in the one of the workflows based on an associated functionality; and
at least one BOT of the subset of the BOTs for the one of the workflows is configured to select during execution a target BOT of the subset of the BOTs for the one of the workflows based on an output data type of output data generated by the at least one BOT of the subset of the BOTs for the one of the workflows and an input data type of input data for the target BOT of the subset of the BOTs for the one of the workflows.
9. The enterprise bot management computing device of claim 7, wherein each BOT of the subset of the BOTs for one of the workflows is included in the one of the workflows based on an associated performance, and the one or more processors are further configured to be capable of executing the programmed instructions stored in the memory to:
assembling, by the enterprise BOT management computing device, a plurality of test workflows based on a set of the assembly rules, each of the test workflows comprising a plurality of the BOTs having a same subset of the BOT types;
evaluating, by the enterprise BOT management computing device, each of the plurality of the BOTs during execution of the test workflows using test data to generate a BOT maturity value for each of the plurality of the BOTs; and
assembling, by the enterprise BOT management computing device, the one of the workflows to include at least one of the plurality of the BOTs having a highest associated one of the BOT maturity values for each BOT type in the same subset of the BOT types.
10. The enterprise bot management computing device of claim 7, wherein:
each BOT of the subset of the BOTs for one of the workflows is included in the one of the workflows based on an associated service level;
each BOT of the first and second portions of the subset of the BOTs is configured to determine when a solution to a received request can be provided based on a generated confidence score, wherein the one of the workflows comprises at least a first level comprising the first portion of the subset of the BOTs having an associated first service level and a second level comprising the second portion of the subset of the BOTs having a second service level;
at least one BOT of the first portion of the subset of the BOTs is further configured to transfer the request to one BOT of the second portion of the subset of the BOTs, when the determining indicates that a solution to the request cannot be provided; and
at least one BOT of the second portion of the subset of the BOTs is further configured to provide resolution data to each BOT of the first portion of the subset of the BOTs, when the determining indicates that a solution to the request can be provided.
11. The enterprise bot management computing device of claim 7, wherein the one or more processors are further configured to be capable of executing the programmed instructions stored in the memory to:
evaluate each of the workflows during execution to generate a workflow performance value for each of the workflows, wherein the workflow performance value is based at least in part on a BOT maturity value for each BOT of the subset of the BOTs included in each of the workflows; and
output one or more of the workflow performance values.
12. The enterprise bot management computing device of claim 11, wherein the one or more processors are further configured to be capable of executing the programmed instructions stored in the memory to:
obtain a plurality of reward values, a plurality of penalty values, and a total number of serviced requests for each of the BOTs; and
generate the BOT maturity value based on a difference between a sum of all of the reward values and a sum of all of the penalty values divided by the total number of serviced requests for each BOT of the subset of the BOTs included in each of the workflows.
Dated this 21st day of March, 2016
Swetha SN
Of K&S Partners
Agent for the Applicant
, Description:FIELD
This technology relates to methods for creating dynamic workflows of interoperable application components, referred to as BOTs, which automate portions of enterprise processes, and devices thereof.
| # | Name | Date |
|---|---|---|
| 1 | Form 9 [21-03-2016(online)].pdf | 2016-03-21 |
| 2 | Form 5 [21-03-2016(online)].pdf | 2016-03-21 |
| 3 | Form 3 [21-03-2016(online)].pdf | 2016-03-21 |
| 4 | Form 18 [21-03-2016(online)].pdf | 2016-03-21 |
| 5 | Drawing [21-03-2016(online)].pdf | 2016-03-21 |
| 6 | Description(Complete) [21-03-2016(online)].pdf | 2016-03-21 |
| 7 | abstract201641009861.jpg | 2016-03-24 |
| 8 | REQUEST FOR CERTIFIED COPY [28-03-2016(online)].pdf | 2016-03-28 |
| 9 | 201641009861-Power of Attorney-170516.pdf | 2016-07-19 |
| 10 | 201641009861-Form 1-170516.pdf | 2016-07-19 |
| 11 | 201641009861-Correspondence-F1-PA-170516.pdf | 2016-07-19 |
| 12 | REQUEST FOR CERTIFIED COPY [04-11-2016(online)].pdf | 2016-11-04 |
| 13 | 201641009861-FER.pdf | 2020-03-05 |
| 14 | 201641009861-OTHERS [24-06-2020(online)].pdf | 2020-06-24 |
| 15 | 201641009861-FER_SER_REPLY [24-06-2020(online)].pdf | 2020-06-24 |
| 16 | 201641009861-DRAWING [24-06-2020(online)].pdf | 2020-06-24 |
| 17 | 201641009861-CORRESPONDENCE [24-06-2020(online)].pdf | 2020-06-24 |
| 18 | 201641009861-COMPLETE SPECIFICATION [24-06-2020(online)].pdf | 2020-06-24 |
| 19 | 201641009861-CLAIMS [24-06-2020(online)].pdf | 2020-06-24 |
| 20 | 201641009861-ABSTRACT [24-06-2020(online)].pdf | 2020-06-24 |
| 21 | 201641009861-US(14)-HearingNotice-(HearingDate-13-12-2022).pdf | 2022-11-22 |
| 22 | 201641009861-POA [01-12-2022(online)].pdf | 2022-12-01 |
| 23 | 201641009861-FORM 13 [01-12-2022(online)].pdf | 2022-12-01 |
| 24 | 201641009861-Correspondence to notify the Controller [01-12-2022(online)].pdf | 2022-12-01 |
| 25 | 201641009861-AMENDED DOCUMENTS [01-12-2022(online)].pdf | 2022-12-01 |
| 26 | 201641009861-Written submissions and relevant documents [26-12-2022(online)].pdf | 2022-12-26 |
| 27 | 201641009861-PETITION UNDER RULE 137 [26-12-2022(online)].pdf | 2022-12-26 |
| 28 | 201641009861-FORM 3 [26-12-2022(online)].pdf | 2022-12-26 |
| 29 | 201641009861-PatentCertificate28-03-2023.pdf | 2023-03-28 |
| 30 | 201641009861-IntimationOfGrant28-03-2023.pdf | 2023-03-28 |
| 1 | 201641009861_26-02-2020.pdf |