UiPath Automation Programme for a Listed Italian Multi-Utility

Between 2020 and 2025 we built and operated a managed programme running 20+ UiPath robots, built on the full UiPath Automation Cloud. An in-house Centre of Excellence owned it, with monitoring, reporting and leadership reviews every quarter. Four of the flows give a sense of its breadth.

1. Reviewing security alerts

• No alert skipped. The robot picks up Darktrace alert reports from the mailbox where they land, extracts the attachments and splits every alert into its fields: severity, model, link, port, and the source and destination IP.
• Each alert queued separately. Alerts become individual items in an Orchestrator queue, so every one is checked, retried and logged independently.
• Every IP looked up. External addresses go to VirusTotal and IBM X-Force Exchange to find recorded threats and the country of origin. A whitelist covers addresses known to be safe, and a backup geolocation service steps in when needed.
• Fixed rules for escalation. The robot escalates an alert when the source or destination sits outside the EU, when either one has recorded threats, or when the alert matches a Darktrace model under watch, for example FTP, Tor downloads, Pastebin, BitTorrent, cryptomining or denial of service.
• Reporting to administrators. IT security receives escalations as formatted HTML emails. Daily processing and alert reports record every alert, and exceptions go to their own log.

2. Collecting telecom invoices

• One robot for five operators. Using credentials stored in Orchestrator, the robot signs in to six portals belonging to five telecom operators, covering each line type and company account. It then fetches invoices and technical documentation as CSV and PDF files.
• No duplicates. It checks what has already been filed, unpacks zipped downloads and renames every file to a single convention.
• Filed where finance can use it. Documents were stored in the finance document repository and, in a later phase of the programme, in ServiceNow.
• Timed to billing. It runs monthly or bimonthly depending on the portal. The process owner gets a run report and notification emails in Italian, business exceptions included.

3. Checking fuel cards

• Pulling the transactions. The robot downloads all corporate fuel-card refuelling transactions from the customer portal run by the supplier.
• Four automatic tests. It keeps fuel lines only, orders them by plate and date, and tests each for wrong mileage, the mileage gap between fill-ups, price and average consumption.
• Anomalies sent to HR. Two reports come out, one listing every checked transaction and one with the anomalies only. Both get saved, and the owners receive them by email.

4. Allocating fuel costs

• Statements parsed automatically. The robot reads PDF fuel statements from two suppliers and pulls out the plate and amount for each vehicle.
• Each cost lands with its company. Every transaction is matched with existing cost data and entered into the template of whichever group company the vehicle belongs to, for seven companies in total.

Programme-wide

• An in-house Centre of Excellence. We established it as the body running the programme, covering the pipeline, standards, ownership and the connection to leadership.
• All of UiPath Automation Cloud. Queues, credentials and assets in Orchestrator, Action Center for steps that need a person, and Document Understanding with AI for processes built around documents.
• A single build standard. Robotic Enterprise Framework, configuration files, a split between business and system exceptions, exception logs with screenshots, and test harnesses.
• Governance and monitoring. Reporting from a monitoring system, plus quarterly sessions with leadership to review the programme and choose the next improvements.

Stack