| CPC G05B 19/41835 (2013.01) [G05B 2219/31368 (2013.01)] | 14 Claims |

|
1. A method for enabling automation templates as a service for data processing by utilizing one or more processors and one or more memories, the method comprising:
presenting, at a client device of a user, a set of automation templates available for selection based on various attributes of a profile of the user, wherein differing sets of automation templates are presented to different users;
receiving, at the client device, a selection of an automation template among the set of automation templates available for performing an automation request, wherein the set of automation templates includes each of an inputs form template, a variables template, a rules/formats template, and a reference data template;
in response to the selection, retrieving, from a cloud system and via a catalog service, the inputs form template corresponding to the selected automation template,
wherein the inputs form template includes data parameters and destination information corresponding to the selected automation template,
wherein the catalog service provides three sets of operation application programming interfaces, including a request management application programming interface, an automation templates application programming interface, and an execution application programming interface,
wherein the request management application programming interface associates automation requests with automation templates, associates the automation requests with executions, searches for the automation requests, check status for the automation requests, and trigger creation, submission and completion notification for the automation requests,
wherein the request management application programming interface includes information corresponding to active automation requests, the information corresponding to the active automation requests including at least requesting user identification, a security/access level of the user, designated data sources, time of the automation requests, and history of previous automation requests,
wherein the automation templates application programming interface fetches automation template inputs form attributes, retrieve automation template variables, retrieve automation template rues/formats attributes, and create, read, update and delete (CRUD) for reference data, and
wherein the execution application programming interface includes an ingestion node, a processing node, a results node and logs node, triggers a data ingestion process, triggers storage and/or transfer of resulting data, triggers an automation process including validation, transformation, calculation and arrangement, and read/write logs;
receiving, at the client device, a plurality of inputs to be inputted to the inputs form template;
submitting, at the client device and to the cloud system, the inputs form to trigger an automation execution based on the selected automation template and the inputs form;
generating, at the cloud system, a status flow indicating each of an estimated time of completion of the automation execution, a position in automation queue, expected start time, a current status of the automation request, and a percentage/amount of completion;
performing, at the cloud system, data ingestion based on one or more input data sources specified in the inputs form and pre-defined set of rules specified in the selected automation template, wherein the data ingestion includes transportation of data from various data sources to a storage medium where the data can be accessed, used and analyzed;
updating, at the cloud system, logs to reflect the performed data ingestion;
executing, at the cloud system, an automation process based on a pre-defined set of calculations, transformations, and/or arrangements specified in the automation template;
pushing, at the cloud system, results of the executing based on destination information specified in the inputs form and the pre-defined set of rules specified in the automation template;
updating, at the cloud system, the logs to reflect the pushing of the results;
updating, at the cloud system, a status of the automation request;
sending, by the cloud system and to the client device, a notification of the pushing of the results; and
updating, at the cloud system, the logs to reflect the updating of the status.
|