Abstract: Disclosed herein is a method and system for dynamically integrating a plurality of BOTs. The method comprises creating the plurality of BOTs offering one or more automated services, wherein each of the plurality of BOTs has a common BOT structure comprising one or more field parameters. One or more predefined functions are assigned to each of the plurality of BOTs, wherein at least one of the one or more predefined functions comprises a function value. A maturity score for each of the plurality of BOTs is determined based on the one or more field parameters and the function value upon assigning the one or more predefined functions to each of the plurality of BOTs. Finally, the plurality of BOTs are integrated by synchronizing data amongst the plurality of BOTs based on the maturity score. Fig. 2
Claims:WE CLAIM:
1. A method for dynamically integrating a plurality of BOTs, the method comprising:
creating, by a process automation system, the plurality of BOTs offering one or more automated services, wherein each of the plurality of BOTs has a common BOT structure comprising one or more field parameters;
assigning, by the process automation system, one or more predefined functions to each of the plurality of BOTs, wherein at least one of the one or more predefined functions comprises a function value;
determining, by the process automation system, a maturity score for each of the plurality of BOTs based on the one or more field parameters and the function value; and
integrating, by the process automation system, the plurality of BOTs by synchronizing data amongst the plurality of BOTs based on the maturity score.
2. The method as claimed in claim 1, wherein the one or more field parameters comprises at least one of a BOT identification (ID) number, BOT name, BOT type, BOT type version, BOT version, BOT group name, BOT state, source file format, source file name, source file path, data version, algorithm used for processing data, BOT status, frequency of requests to the BOT, time period of the requests, reward points and penalty points, last synchronization date, last synchronization status, BOT maturity, publish topics of the BOT, subscription topics of the BOT, last published event message, last received event message, association property, work flow property, source BOT ID, target BOT ID and deploy instance count of the BOT.
3. The method as claimed in claim 1, wherein assigning the one or more predefined functions to each of the plurality of BOTs further comprises updating at least one of the one or more predefined function values upon handling of an event by a BOT from the plurality of BOTs.
4. The method as claimed in claim 3, wherein the one or more predefined functions includes at least one of starting the BOT, stopping the BOT, assembling the BOT, deploying the BOT, detecting the maturity score of the BOT, assigning the maturity score of the BOT, detecting the rank order of the BOT, assigning the rank order of the BOT, verifying the BOT, checking state of the BOT, checking the status of the BOT and assigning the threshold values of frequency, time and total number of the reward points and the penalty points.
5. The method as claimed in claim 1, wherein the maturity score for each of the plurality of BOTs is determined when the number of requests handled by each of the plurality of BOTs individually is higher than a predefined number of requests.
6. The method as claimed in claim 5, wherein determining the maturity score for each of the plurality of BOTs is based on the number of requests handled by each of the plurality of BOTs, the number of reward points and the number of penalty points assigned to each of the plurality of BOTs.
7. The method as claimed in claim 1, wherein the plurality of BOTs are synchronized when at least one of the maturity score, the frequency of requests and the time period of the requests associated with one of the plurality of BOTs is higher than a predefined maturity score, predefined frequency of requests and predefined time period of the requests respectively.
8. The method as claimed in claim 1, wherein communication between each of the plurality of BOTs is established using at least one of an event message service model and one or more communication Application Program Interfaces (APIs) associated with each of the plurality of BOTs.
9. A process automation system for dynamically integrating a plurality of BOTs, the process automation system comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, causes the processor to:
create the plurality of BOTs offering one or more automated services, wherein each of the plurality of BOTs has a common BOT structure comprising one or more field parameters;
assign one or more predefined functions to each of the plurality of BOTs, wherein at least one of the one or more predefined functions comprises a function value;
determine a maturity score for each of the plurality of BOTs based on the one or more field parameters and the function value; and
integrate the plurality of BOTs by synchronizing data amongst the plurality of BOTs based on the maturity score.
10. The system as claimed in claim 9, wherein the one or more field parameters comprises at least one of a BOT identification (ID) number, BOT name, BOT type, BOT type version, BOT version, BOT group name, BOT state, source file format, source file name, source file path, data version, algorithm used for processing data, BOT status, frequency of requests to the BOT, time period of the requests, reward points and penalty points, last synchronization date, last synchronization status, BOT maturity, publish topics of the BOT, subscription topics of the BOT, last published event message, last received event message, association property, work flow property, source BOT ID, target BOT ID and deploy instance count of the BOT.
11. The system as claimed in claim 9, wherein the instructions cause the processor to assign the one or more predefined functions to each of the plurality of BOTs by updating at least one of the one or more predefined function values upon handling of an event by a BOT from the plurality of BOTs.
12. The system as claimed in claim 11, wherein the one or more predefined functions includes at least one of starting the BOT, stopping the BOT, assembling the BOT, deploying the BOT, detecting the maturity score of the BOT, assigning the maturity score of the BOT, detecting the rank order of the BOT, assigning the rank order of the BOT, verifying the BOT, checking state of the BOT, checking the status of the BOT and assigning the threshold values of frequency, time and total number of the reward points and the penalty points.
13. The system as claimed in claim 9, wherein the instructions cause the processor to determine the maturity score for each of the plurality of BOTs when the number of requests handled by each of the plurality of BOTs individually is higher than a predefined number of requests.
14. The system as claimed in claim 13, wherein the maturity score for each of the plurality of BOTs is determined based on the number of requests handled by each of the plurality of BOTs, the number of reward points and the number of penalty points assigned to each of the plurality of BOTs.
15. The system as claimed in claim 9, wherein the instructions cause the processor to synchronize the plurality of BOTs when at least one of the maturity score, the frequency of requests and the time period of the requests associated with one of the plurality of BOTs is higher than a predefined maturity score, predefined frequency of requests and predefined time period of the requests respectively.
16. The system as claimed in claim 9, wherein each of the plurality of BOTs communicate using at least one of an event message service model and one or more communication Application Program Interfaces (APIs) associated with each of the plurality of BOTs.
Dated this 17th day of March, 2016
SWETHA S.N
OF K & S PARTNERS
AGENT FOR THE APPLICANT , Description:TECHNICAL FIELD
The present subject matter is related, in general to process automation, and more particularly, but not exclusively to a method and system for dynamically integrating BOTs.
| # | Name | Date |
|---|---|---|
| 1 | Form 9 [17-03-2016(online)].pdf | 2016-03-17 |
| 2 | Form 5 [17-03-2016(online)].pdf | 2016-03-17 |
| 3 | Form 3 [17-03-2016(online)].pdf | 2016-03-17 |
| 4 | Form 18 [17-03-2016(online)].pdf | 2016-03-17 |
| 5 | Drawing [17-03-2016(online)].pdf | 2016-03-17 |
| 6 | Description(Complete) [17-03-2016(online)].pdf | 2016-03-17 |
| 7 | REQUEST FOR CERTIFIED COPY [19-03-2016(online)].pdf | 2016-03-19 |
| 8 | abstract201641009412 .jpg | 2016-03-23 |
| 9 | 201641009412-Power of Attorney-170516.pdf | 2016-07-19 |
| 10 | 201641009412-Form 1-170516.pdf | 2016-07-19 |
| 11 | 201641009412-Correspondence-F1-PA-170516.pdf | 2016-07-19 |
| 12 | REQUEST FOR CERTIFIED COPY [03-11-2016(online)].pdf | 2016-11-03 |
| 13 | 201641009412-FER.pdf | 2020-01-14 |
| 14 | 201641009412-FORM 3 [02-07-2020(online)].pdf | 2020-07-02 |
| 15 | 201641009412-FER_SER_REPLY [02-07-2020(online)].pdf | 2020-07-02 |
| 16 | 201641009412-US(14)-HearingNotice-(HearingDate-23-02-2023).pdf | 2023-02-02 |
| 17 | 201641009412-POA [09-02-2023(online)].pdf | 2023-02-09 |
| 18 | 201641009412-FORM 13 [09-02-2023(online)].pdf | 2023-02-09 |
| 19 | 201641009412-Correspondence to notify the Controller [09-02-2023(online)].pdf | 2023-02-09 |
| 20 | 201641009412-AMENDED DOCUMENTS [09-02-2023(online)].pdf | 2023-02-09 |
| 21 | 201641009412-Written submissions and relevant documents [10-03-2023(online)].pdf | 2023-03-10 |
| 22 | 201641009412-PETITION UNDER RULE 137 [10-03-2023(online)].pdf | 2023-03-10 |
| 23 | 201641009412-FORM-26 [11-03-2023(online)].pdf | 2023-03-11 |
| 24 | 201641009412-PatentCertificate08-02-2024.pdf | 2024-02-08 |
| 25 | 201641009412-IntimationOfGrant08-02-2024.pdf | 2024-02-08 |
| 1 | search_31-12-2019.pdf |