Kirona’s solution comprises two major components: software that identifies a job and the best person to do that job, and a mobile platform that effectively disseminates this information. The solution captures information about the job posting, then automatically dispatches the data through mobile applications to match jobs to employees as efficiently as possible. Every day, approximately 60,000 users process potentially millions of jobs that include dozens of individual transactions and complex scheduling requirements.
In the majority of cases, Kirona serves as a conduit for the data, rather than owning it. Accordingly, the company’s “secret sauce” is rapid integration of data from complex CRMs, ERPs, and EDRMS from Oracle, SAP, and other third parties into its scheduling system. As Kirona quickly expanded its business, it began working with a local Council that needed a more efficient way to manage scheduling for property maintenance engineers.
The Council’s proprietary back-office system incorporated a legacy third-party application that the Kirona team needed to access. While the legacy system did have some Application Programming Interfaces (APIs) in place, the original solution vendor proposed a prohibitively expensive fee to provide access to them. Recognizing that it would encounter similar issues with prospective clients in the near future, Kirona launched a search for a solution that would connect and create APIs in a non-invasive manner. A critical requirement for the new system was the ability to integrate data from all standard data sources such as Oracle, IBM, and Salesforce.com, and capture this data without compromising the business logic in the original system.
- Rapidly scaled business to become a dominant player in mobile workforce automation
- Averaged 25 percent increase in client efficiency, enabling clients to complete more jobs and improve customer satisfaction
- Saved some clients £100,000+ on product implementations and delivery of job services
- Data integration and orchestration of downstream systems
Want to learn more?
We ultimately selected Rocket API because of its ‘provenance.’ Rocket had completed thousands of implementations, proving the technology was repeatable and robust enough to manage what we saw as a small window to position ourselves as the dominant player in a rapidly emerging market.