One platform, 35% fewer agent calls.
TasWater's legacy APIs were exposed to the Log4J vulnerability and its integration platform was nearing end of life. J4RVIS ran the modernisation: migrated the platform, hardened the APIs, and stood up self-service that took a third of the call volume off the agents in week one.
- 35%
Reduction in agent-handled calls (first week, via IVR)
- 24/7
Self-service for account balance and due date
- Log4J
Vulnerability remediated across the API estate
The starting position.
TasWater provides water and sewerage across Tasmania. Its legacy APIs were exposed to the Log4J vulnerability and needed urgent remediation. The integration platform, MuleSoft CloudHub 1, was nearing end of life. An inefficient CI/CD process was slowing every deployment, and the combination put service continuity at risk. This was security and stability first: fix what was exposed, then modernise the foundation under it.
What we did.
J4RVIS ran a modernisation programme that removed the security exposure, moved the platform to a supported version, and added self-service for customers.
Closed the Log4J exposure
Hardened and patched the APIs to remove the vulnerability.
Migrated the platform
Moved CloudHub 1 to CloudHub 2, off the end-of-life version and onto supported infrastructure.
Rebuilt the pipeline
Stood up a Jenkins-based CI/CD pipeline so deployments stopped being the bottleneck.
Integrated billing
Connected the Gentrack e-billing system to enterprise systems.
Added self-service
Deployed an IVR solution so customers can check account balance and due dates without an agent.
Team and method
Delivered and run as a managed-services engagement, with ongoing support and monitoring for continued security and performance.
What actually changed.
| Before | After | |
|---|---|---|
| Log4J exposure | Open across the legacy API estate | Patched and hardened, remediated across the estate |
| Integration platform | MuleSoft CloudHub 1, nearing end of life | CloudHub 2, on supported infrastructure |
| Deployments | An inefficient CI/CD process slowing every release | A Jenkins pipeline, so deployment stopped being the bottleneck |
| Balance and due-date questions | Answered by an agent, in business hours | IVR self-service, 24/7, with 35% fewer calls to agents in week one |
