IEEE 2755.1-2019 pdf download
IEEE 2755.1-2019 pdf download.IEEE Guide for Taxonomy for Intelligent Process Automation Product Features and Functionality.
4. Licensing and consumption models
Software Based Intelligent Process Automation technology is a new and ditTerent type of software platform in that it does not inherently contain codified business logic as most enterprise applications do. For example, when purchasing an application for managing finance or supply chain, the app contains “pie-built” logic for the automation of common transactions and processes in that function. It is further configurable or customizable to meet business needs.
Intelligent Process Automation products are dit1rent in that they do not inherently contain any business logic. They are designed as general purpose digital software platforms tbr creating. storing, and deploying “applets’ that contain codified business logic. These applets can access any kind of existing application, website, or data repository that any person with access pri ikges in the enterprise can. It follows, then, that the type and variety of business logic that might be contained in a configured applet is nearly infinite.
This mode of consumption is diflircnt from an operating system and different from a typical business application. Deploying an Intelligent Process Automation product does not address any specific business problem or opportunity, and does not inherently process anything for the business. It is only after installing the Intelligent Process Automation platform and using the included tools to create an applet (or sliat may ariously be called a “hot” or “robot” or ‘automation.” depending on scale) that the Intelligent Process Automation platform begins to perform business pnwcsses and deliver value.
When purchasing an Intelligent Process Automation platform product. the enterprise is essentially buying a toolsct that enables future configuration and deployment of independent applets. The scope. breadth and complexity of a deployed appict currently possesses no generally acknowledged measure of capacity.
Some in the industry may describe a unit of process executional capacity in terms of what may be performed by a platform license. Others may describe a unit of capacity based on the computational sue of the hardware on which the applet is running. Still others may dcscrihc a unit of capacity in terms of the specific configured process automation.
When ealuating a purchase of an Intelligent Process Automation platform, therefore, careful consideration must be given to that product’s licensing model, and relative executional potential pt, unit of cost, with cost bdiig a combination of license and hardware.
The usc of the term platform when talking about Intelligent Process Automation products is intentional. In most typical Intelligent Process Automation platforms, the buyer is getting at least four fundamental capabilities:
ContIg. build, test capability
Management console
Run-time or execution units
Orchestration or business logic interpreter
Some platforms may also include some level of intelligence capability in the form of machine learning functionality.
Each specific use case or process that a business may consider automating will be different; hence the number of process steps, tasks, or applications involved will vary. Similarly, platforms vary in how the business will be charged for the exccutional impact of a given applet. Ikpcnding on the platform and licensing model, then, different strategies exist to maximiic the “work” done by a unit of cost (license plus hardware).
At present, there arc many licensing and consumption models and model continue to change as pmducts evolve. Three exampks follow:
a) The Iiccn%c may be tied to a piece of computing hardv arc and thus, the total work capacity is highly dependent on the size of thc hardware.
h) The license may he constrained to running a single contigured production automation at a time, making scheduling and applet run-time op(imi7ation key drivers of the total work available.
C) Costs for work performed may he calculated by the actual run-time and computational load incurred by a specific configured production automation, imiIar to a consurnplion-ba.scd mainframe cost model.
Due to the variable nature of the cost models inherent in a product (and its manufacturer’s business model), careful attention should be paid to understanding not just the cost of the initial platform acquisition. hut how on-going run-time costs will build as the use of the production automation grows.
