The insurer's customers upload their policy documents and get served without the system slowing down.
The insurer wanted customers, from small farmers to car makers, to send in documents and get timely service on their vehicle, health, travel and home cover.
What changed
What stood in the way.
- Thousands of insured people uploaded documents and images every day, and the old Documentum system was slow to store, import and show them, with intermittent downtime.
- Documentum had dropped support for DB2, and the 60 TB of live data had to move with zero downtime; other providers had declined the project.
- 60TBof data migrated (as reported)
- 100%system uptime during the migration (as reported)
- 0%data loss (as reported)
What we built.
- An upgrade of the Documentum content server from D7.2 to D 20.2 and of WebTop to 20.2, tested in a copy of production with a backup and rollback plan.
- A migration of 60 TB from DB2 to Oracle 19c, with fields mapped by hand in a local copy and moved by an in-house utility to keep the data intact.
- Archived data moved to Oracle on AWS RDS and connected to the new Documentum servers, lowering storage cost.
- Captiva capture that reads PAN cards, application forms and vehicle images and indexes details such as PAN and registration numbers.
- Links to the insurer's CRM, SOAP services moved to REST APIs, and one year of support.
- EMC Documentum
- Oracle 19c
- AWS RDS
- Captiva
- Java/J2EE
What this work shows about us.
A mission-critical 60 TB live system was moved and upgraded without stopping the business (as reported).
Policy documents, identity cards and vehicle photos are captured, indexed and found quickly, which is what customer service runs on.
Want to migrate a large database from DB2 to Oracle like this? Tell us what you want to change. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with the right team.
Start your plan ↗If we built it today, with AI.
This work came before today's AI. If the leading Indian general insurer asked us now, this is what we would add, step by step.
An agent would read each upload as it arrives, tell the customer at once if a PAN card or vehicle photo is unclear or missing, and file the rest. The capture rules still index every document.
An agent would gather the policy, the photos and the forms for a motor claim into one file and list what is still needed for the claims handler. Handlers still decide every claim.
Where this work fits.
- InsurersYour policyholders are meant to get the cover they need, and get paid when they claim, without chasing anyone.
- Insurance marketplaces & operationsPeople find and buy the cover they need, and get paid when they claim, without chasing.
- First Abu Dhabi Bank (FAB)First Abu Dhabi Bank's customers get their credit approvals, loans and cheques processed without waiting on paper.
Facts and figures from the project records; nothing added.
Want this for your business?
Tell us what you run or what you're building. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with a senior AI engineer.
Send us a note instead
An AI agent. This prototype uses prepared answers and sends nothing.
We use essential cookies to run this site. With your consent we also use analytics cookies to see which pages help. Privacy policy