DECOMMISSIONING CASE : SIEBEL UCM TO INFORMATICA MDM HUB

Transcription

1 DECOMMISSIONING CASE : SIEBEL UCM TO INFORMATICA MDM HUB People Arhis Decommission Factory Team provides comprehensive end to end services to decommission Siebel Universal Customer Master application (UCM) by using Informatica Master Data Management (MDM). Our team is specialized in providing project planning, execution and support, enabling your organization to replace the Siebel UCM within budget and time. We work with our clients to follow their legal, regulatory, and governance requirements in order to eliminate the legal repercussions associated with the lost or invalidated data. We have been implementing both Siebel UCM and Informatica MDM for years. Professionals with high level of experience of both enterprise applications are dedicated throughout the project lifecycle. Our team will not only replace the old system, but also an enhanced data management experience exceeding it. Technology Informatica MDM is enterprise software that is specialized in acquiring, cleansing, enriching, consolidating, federating, and governing data across many disparate systems. It helps your organization to improve data quality by delivering the "golden record" or "Best Version of Truth" record. The multidomain model design supports multiple business data entities reside in a single MDM system. The concept of platform MDM solves other master data related business problems using the same MDM platform. The application is domain and data model independent. It allows organizations to flexibly define their own data model, generate logic and functionality based on this defined model, and provide support to configure the GUI based on the functionality. This feature lowers the total cost of ownership and shortens the time to value. In the master data hub, such as customers, hierarchies and relationships are sometimes complex. Informatica MDM supports complex relationships and hierarchies such as organisational relationships and consumer relationships. Because MDM is the foundation technology that provides reliable data, any changes made to the MDM environment will ultimately result in changes to the dependent SOA services and consequently to the SOA applications. Informatica MDM can automatically generate changes to the SOA services whenever its data model is updated with new attributes, entities, or sources. This will protect the higher level SOA applications from any changes made to the underlying MDM system. The ability to integrate data quality (profiling, cleansing, and monitoring) within the MDM system is important to

2 enhance the value of data assets. Before you start the project, you need to understand the content, quality, and structure of your source data. Data profiling at different source data (including Siebel UCM) enables data stewards and data warehouse administrators to quickly discover and analyze all data anomalies in the system before data migrated. This process greatly increases the speed to value from the decommissioning implementation. Because data cleansing enhances the accuracy of data, provides completeness, and promotes trustworthiness of the data at the source, it improves the consistency of the data within the MDM system. Once source data enters the MDM system, it undergoes data quality processing, including validation, correction, and standardization. With integrated data quality, Informatica MDM stores the complete history of the data before and after it is cleansed. Informatica MDM provides different deployment modes to fit your organization: on premise, cloud, and hybrid. We will assist you to choose and deploy the appropriate mode which is suitable for you. Standardised Methodology Discovery Analyse Design Build Deploy Support Discovery: Define Vision & Scope for the New Informatica MDM. The solution team will visit the high level requirements implemented. Identify the key master data entities and attributes. Review the source and target systems to be integrated with Informatica MDM. Identify possible gaps or pre requisites information used by Siebel UCM and Informatica MDM. Analyse: The team will gather detail requirements and produce the new requirement specification. The focus will be on Data Quality Audit. Non master data entities in used will be identified. By reviewing the current application, new Data Quality issues (current pain points) may be addressed. Thereby, additional requirements will be produced. The study also includes the data availability & processing dependencies, and confirm total volumes and expected delta volumes. To identify UCM customized table(s) if any Existing matching rules Master data life cycle Survivorship rules

3 Real time / batch interfaces with UCM Design: In this stage, the team will propose the new design application according to the requirement specification. Both physical and logical data model will be produced. The technical design document will be provided for client confirmation. The Party data model is pre built in Informatica MDM, which has all common UCM master data entities and attributed defined. This would lower the initial data modelling effort. The data model will be easily adjusted to accommodate any UCM customized table/columns. For data loading, Informatica MDM landing and staging tables will replace Siebel EIM tables to map the source data to target model. The standard Informatica Data Director user interface will be designed to replace the Siebel User Interface. If there is any current data issues, they will be addressed by the new proposed solution. If the Siebel UCM is integrated with any third party applications, a new solution will be proposed. Build: Modify pre built Informatica MDM tables, create Data Cleansing rules, build trust settings based on UCM Survivorship rules, match rules from UCM IIR configuration, create Hierarchy / affiliation management rules from UCM Customer Hierarchy. The existing system interfaces will be replaced by Informatica MDM System Integration Framework. Unit Test will be conducted to ensure the outcome of the match results are same (if not improved) as per the original matching. A migrated system cannot be put into use without proper testing. The team will setup a complete environment for system testing and user acceptance testing. During the system test, any system anomalies will be detected and corrected before migrating to full production environment. All related third party software will be thoroughly tested. During the user acceptance test, business users will be executing a number of test cycles with their business scenarios in order to accept it as the future system. Users can compare the test result between Siebel UCM and the new Informatica MDM.

4 Deploy/ Migration: Deploy to new production environment and convert all data from the old system to the new one. Source Systems 1.. N i d bl Enterprise Service Bus customized table Siebel Application Server customized table Informatica Service MDM Application Server identify any UCM i d bl Siebel Tables Export EIM Direct Landing Prebuilt Mappings Staging To identify any UCM customized Load To identify any UCM customized table Informatica Base Tables IIR Server (Matching) Migrate Matching Rules Informatica Matching Engine

5 Post-Implementation Support Support: In addition to your decommissioning project, you might need Arhis to assist you in your application maintenance In sourcing your data operations Based on its experience, Arhis has developed a unique model for supporting its clients once the MDM hub is live. This model goes beyond the usual beliefs that have been applied for years by large integrators and is based on the following (non exhaustive) findings: MDM systems are complex because they encompass many applications, people and processes Outsourcing (systems and support) to a third party is not the solution : o Loss of in house skills in a strategic domain (data) o Data security issues o Skills issues o Often language issues o SLA not respected o Painful contract discussions What initially appeared as a cost effective solution results in increased operational overhead and lack of agility of the information system Arhis approach is natural: Arhis approach combines Insourced Staff and our expertise center (The Arhis MDM Factory). Insourced personal is usually local staff, dedicated to the client support which is involved early in the project cycle. Therefore, when the MDM system is running live, the local support team is knowledgeable and ready to support. The MDM Factory provides key and deep expertise, but only when needed. The SLA are respected, the handover from project to operations is frictionless and natural Arhis is supporting many live MDM systems using insourced staff and it has proven to be the best way to manage efficient application maintenance