Purisma Terminal Release Impacts Many Companies’ EIM Strategies
With the announcement that Purisma 4.5.2 will be the final release of the product, D&B Purisma customers are being forced to reevaluate their EIM/MDM strategies and components. This is the final version of Purisma to be developed and deployed, undoubtedly causing many unknowns and some angst for those who have invested a great deal of time and money in establishing Purisma as an integral component of their EIM architecture. But before quick judgments are made regarding the impact of Purisma’s terminal release, it is important to know that there are options for those running PDH.
The ideal option for Purisma users is to make the switch to the tool that is leading the industry in the MDM space: Informatica’s MDM Hub. With data quality and ETL capabilities built into the tool, as well as tight integration capabilities with Informatica’s suite of EIM products (including Powercenter and IDD), Informatica MDM is a fail-safe option for many companies to continue achieving their tactical and strategic Enterprise MDM goals.
Infoverity has some of the most experienced Purisma architects and services professionals in the industry, having worked with the product for over 5 years since version 1.6.5. Our team has a proven track record, having delivered solutions in the Master Data, Data Quality and Governance, and Information Management spaces. We can custom tailor a transition for any company that is looking for answers about the future of their Purisma Data Hub. In addition to our extensive Purisma background, Infoverity has deep MDM experience and is closely aligned with Informatica’s professional services team.
Infoverity has developed three solution strategies to help guide Purisma customers through shifting to Informatica’s MDM platform. These solutions will allow companies to leverage the investment they have made in Purisma, while gaining a first-class MDM platform for the future.
- Solution 1 – Hot swap Purisma, convert all established hierarchies and golden records within Purisma over to Informatica MDM.
- Solution 2 – Retire Purisma, and re-match and re-master your data with Informatica MDM’s robust matching engine and built-in cleansing and standardization utilities.
- Solution 3 – Continue utilizing Purisma’s matching engine and algorithms, but establish Informatica MDM as the system of record for all maintenance and dissemination of master data to downstream systems.
Solution 1: Retire Purisma but Maintain Historical Matches in MDM
This is Infoverity’s recommended solution. This solution minimizes implementation costs for making the switch from Purisma to MDM, and leverages the investments that have been made in Purisma. In this solution strategy, years’ worth of matching and stewardship results will be absorbed into Informatica MDM. Existing hardware can be used to stand up Informatica MDM. Informatica MDM becomes the centralized master data hub and any manual data stewardship and dissemination of data to downstream systems would be managed through MDM.
Why this solution:
- All past matching results and stewardship efforts will be preserved in MDM.
- Eliminate cost of supporting two systems as well as not having to pay for all new hardware.
- Move toward a Party Model, enabling multi domains (contact, product, etc.).
- Continue leveraging all the D&B data purchased over time.
Cons to this solution:
- This solution strategy would maintain the existing matches from Purisma while also building the matching design in MDM for ongoing data enrichment and matching. Future data within MDM will be matched by Informatica MDM tuned engines/algorithms, which may lead to slight differences in golden record results.
- Lose built-in integration with D&B Optimizer that is provided by Purisma. Custom integration would need to be built to continue automated daily/weekly/monthly loads of D&B data.
Solution Architecture:
Remove source system integration and sunset Purisma Data Hub.
Solution 2: Retire Purisma and Re-match with Informatica MDM
This solution strategy is the most inexpensive way to transition from Purisma to Informatica MDM. This strategy retires Purisma completely and transitions to MDM’s matching/merging routines and re-mastering in a faster, scalable solution. Informatica MDM becomes the centralized hub for ongoing matching, governance and dissemination of master data to downstream systems.
Why this solution:
- Eliminate cost of supporting two systems as well as not investing in new hardware.
- Start fresh with Informatica MDM, ensuring consistent matching results through the entire dataset.
- Convert all D&B data purchased over time into the new MDM platform.Move toward a Party
- Model, enabling multi domains (contact, product, etc.).
Cons to this solution:
- Doesn’t persist all matches and stewardship results from Purisma into Informatica MDM.
- Lose built-in integration with D&B Optimizer that is provided by Purisma. Custom integration would need to be built to continue automated daily/weekly/monthly loads of D&B data.
Solution Architecture:
Start Fresh:
Re-match and re-master all data utilizing Informatica MDM.
Solution 3: Continue Utilizing Purisma Matching Engine & Establish MDM as Central Hub
This solution is a good fit for customers who are comfortable with the match rules and hierarchies they have built in Purisma, and want to continue utilizing and trusting a vested solution Purisma would continue to be where all automatic matching occurs. An integration layer would be designed and built to push all auto-matches to Informatica MDM, with fuzzy matching occurring in MDM on all candidate records identified previously. At that point, MDM would become the centralized master data hub and any manual data stewardship and dissemination of data to downstream systems would be managed through MDM.
Why this solution:
- Comfortable with all Purisma Auto-Matches and wants to continue to utilize Purisma’s matching.
- Automated process of sending/receiving data through the DnB Optimizer process remains. (Informatica MDM does not have an automated process out-of-the-box for integrating with Optimizer).
- Additional cleansing on relationships by fuzzy matching in Informatica on all non-auto-matched records from Purisma.
- Move toward a Party Model, enabling multi domains (contact, product, etc).
- Continue leveraging all the D&B data purchased over time.
Cons to this solution:
- Managing and sustaining two systems (Purisma and Informatica MDM), which can be costly when paying for the support and maintenance of both systems.
- Additional hardware costs for implementing Informatica MDM on its own platform (Database and Servers).
- Maintains the existing matches from Purisma while also building the matching design in MDM for all future data enrichment and matching capabilities. Future data within MDM will be matched by Informatica MDM tuned engines/algorithms, which may lead to slight differences in golden record results.
- Must still maintain a contract with D&B for data enrichment.
Solution Architecture:
Steve Ruff
Senior Consultant
SRuff@infoverity.com
