Nintex RPA
Automate repetitive interactions with software through robotic process automation. RPA can be considered for tasks in which people repeatedly carry out the same system actions.
When to consider it
Begin with a stable, clearly described activity and examine its exceptions. Assess whether an API integration, a workflow or a software robot best fits the task.
Where Nintex RPA fits in an automation plan
Nintex RPA is relevant when people repeatedly interact with software to carry out a defined activity. Examples to assess include moving information between screens or following the same sequence of system actions. The activity should be understood well enough to identify its normal route and exceptions.
A robot does not remove the need for process ownership. Someone still needs to decide what should happen when information is missing, a screen changes or an action cannot complete. These conditions influence the design and the support needed for the automation.
Compare robots, workflows and integrations
Before selecting Nintex RPA, compare the available approaches. An API integration may provide a direct connection to a system. A workflow can coordinate decisions and tasks. RPA addresses interactions through software interfaces, and may form part of a wider process.
For a licensing discussion, describe the applications, task frequency, expected volume and exception cases. Also identify who will operate and maintain the automation. We can provide a licensing proposal after clarifying the requirements. Feasibility, implementation services and support arrangements are scoped separately.
Licensing and next steps
We provide licensing discussions and proposals for Nintex RPA. The feasibility and delivery of a particular automation require a separate assessment.
Licence packaging, availability and terms are confirmed in the proposal.
