Case Study Healthcare
Post-Go-Live Managed Services for a Tier 1 Healthcare Informatica Estate
Ongoing L2/L3 support, application maintenance, and application development across a tier 1 healthcare customer's Informatica, B2B, and cloud data stack
8x faster root-cause resolution · ~100 GB storage reclaimed · ~25% performance improvement
Summary
aiDataWorks delivers post-go-live managed services — Support Operations, Application Maintenance, and Application Development — for a tier 1 healthcare customer across a stack spanning Informatica PowerCenter, ILM/Data Archive, B2B Data Exchange and Managed File Transfer, Oracle, IBM MQ, Salesforce Cloud, and AWS. The customer's own team handles first-line (L1) support; aiDataWorks owns L2/L3. Under this ongoing engagement, aiDataWorks resolved three production issues: out-of-order file processing failures in B2B Data Exchange, slow partner file processing caused by an unmanaged error-event archive backlog, and a broken SMTP configuration blocking email notifications. Each was resolved through targeted root-cause analysis and fixes — a pacing/staging workflow, a one-time archive cleanup with a new review process, and an SMTP reconfiguration — delivering faster resolution times, fewer recurrences, roughly 100 GB of storage reclaimed, and a roughly 25% performance improvement versus the customer handling these issues internally.
The challenge
- Out-of-order file processing in B2B Data Exchange. When multiple incoming partner files arrived at the same time, DX events fired concurrently and issued overlapping, out-of-order database queries against the same tables, putting processing sequence and data integrity at risk.
- Slow partner file processing from an archive backlog. Error-state DX events with file attachments were excluded from ILM archiving, so the repository kept growing unchecked, which in turn slowed down partner file processing through B2B Data Exchange.
- SMTP notifications silently failing. The B2B server could not send email notifications because an obsolete SMTP configuration — left over from a prior upgrade's metadata migration — was still in place across Informatica PowerCenter and the B2B applications.
The solution
How we built it
File-ordering fix: a pacing workflow
- Routed incoming partner files to a staging location instead of processing them directly on arrival.
- Built a scheduled batch workflow — a "pacing profile" — that delivers one file at a time, oldest-first, to preserve processing order.
- Eliminated the overlapping, concurrent database queries that were causing DX events to fail when multiple files landed simultaneously.
Archive backlog cleanup and performance recovery
- Ran root cause analysis and traced the slowdown to error-state DX events with file attachments being excluded from ILM archiving.
- Identified and marked stale ILM jobs stuck in "Error" state to unblock the archive project.
- Executed a one-time archive cleanup and defined a going-forward review process for error events so the backlog cannot recur unmanaged.
SMTP root-cause and reconfiguration
- Ran root cause analysis on the B2B server's failure to send email notifications.
- Traced the fault to an obsolete SMTP configuration left over from an earlier platform upgrade's metadata migration.
- Corrected the SMTP configuration across Informatica PowerCenter and all B2B applications to restore notification delivery.
Outcomes
- File-ordering recurrence dropped from 3 prior occurrences to 1, with corrective-action time cut from an estimated 8 days to 2 days.
- The archive backlog issue was root-caused in 2 hours versus an estimated 12 hours, and corrective action took 0.5 days versus "a few days" of self-directed effort.
- The SMTP configuration fault — which the customer's own resources could not root-cause — was corrected in 0.25 days once aiDataWorks traced it to the leftover migration setting.
Solving something similar?
We will walk your current data landscape and show you what a governed customer view would take.