Building new robots
From process analysis to go-live. With clear rules for exceptions, logging and documentation, so you know what the robot does.
UiPath specialist for robots that keep working
Does your organisation use UiPath (a platform for software robots), or are you considering it? I build new robots, make existing robots stable and take care of support. With the process as the starting point, not the robot.
What you can hire me for
Making existing robots stable
Does a robot stop often? I find the cause: screen recognition, timing, missing error handling or the process itself. Then I make it robust.
Support and further development
Monitoring, changes after updates of your applications and extensions when your process changes. Also for robots that someone else built.
Setting up Orchestrator well
Orchestrator is the UiPath management program where you schedule and follow robots. I set up queues, credentials, schedules and alerts so you can see what happens and where something goes wrong.
Where UiPath is strong, and where it is not
UiPath is strong at rule-based work in existing screens, especially when a system has no usable integration. A robot then works like an employee, only faster and without typing errors.
A robot can be started by an employee (attended RPA) or run automatically without anyone having to be present (unattended RPA). It follows predefined rules. On an error or exception it can stop, send an alert or put the case to an employee. The run stays traceable.
If a system has a good integration (an API: a fixed entrance through which software talks to other software), that is often more stable. I advise what works best for your process. That can be UiPath, an integration, or a combination of both.
A good fit for a UiPath robot
- Screens of your ERP (business system) without a usable integration
- Customer and supplier portals
- Email, PDF and Excel as input
- Fixed checks and reports