Mobile Erp Integration

Debt collector TCM Belgium handles 30.000 claims yearly. ThinkNexT developed a mobile app integrated with their ERP system allowing agents on the road online and offline access to claims. Due to this change, the amount of visits doubled to 360 claims per month.

TCM Belgium

case-tcmTCM Belgium collects consumer and commercial debt claims in Belgium and 140 countries. They are the only ones to offer such a broad geographical coverage. Due to their constructive approach most claims are solved amicably without legal action. Read more on www.tcm.be

Tablet app

tcm-ipad-mediators2ThinkNexT developed an app for iPad in order to streamline the process for agents on the road. In preparation, an agent downloads the claims to visit that day to the iPad, based on geographical and priority criteria. Once downloaded, all data is available offline. The claims are subsequently visualized on the map. During a visit, the agent shows the various invoices and related information to the debtor. The outcome of that visit is subsequently entered in the app, together with a signature of the debtor, and sent to the server as soon as a connection to the internet is available.
tcm-ipad-mediators1

Server component

The server component handles all communication with the apps and is integrated with TCM’s ERP system. It is a layered architecture meaning that the ERP system is essentially unaware of this newly added functionality.

Mobile technology

The mobile app is developed for iPad iOS version 7. App deployment is done through the Enterprise Program enabling fast in-house deployments. Communication with the server is done through REST webservices (JSON).

Application technology

All ThinkNexT applications are Java based. They use the Tapestry web framework in combination with Hibernate for database connectivity. Hibernate allows us to build our applications on top of any type of database whether that is MySQL, MSSQL, Oracle or others.

Reliability

Transactionality is implemented on the level of jobs: either a job succeeds and all data is changed consistently or it fails and the data is rolled back to the previous consistent state. That approach follows the unit of work pattern. Import and export of file based data is implemented using a two-phased commit protocol.

Monitoring

The application is being centrally monitored by our custom monitoring system Logness. Logness monitors application availability and stores the application logs. Automated pattern analysis is performed on error and warning logs. This allows us to preemptively solve problems.