Tag Archives: MDM hub
Informatica World 2013 is right around the corner, and I’m eager to tell you about all we have planned. This year, MDM will play a prominent role, as you can see by the sheer number of MDM-related sessions presented by Informatica customers, partners, and employees.
Here are just a few highlights:
Are you accelerating your company’s project delivery needs?
Many Fortune 500 and Global 500 companies understand that their mission-critical data must be managed, so if you are a developer with the desire to work faster and better you should think about Informatica University Training and Certification.
Why? Because you can establish yourself as a key resource with the skills and experience to 1) ensure a trusted view of your organization’s business data, 2) to accelerate your company’s project delivery needs, or just 3) to demonstrate that you have the needed skills to provide your business the right information at the right time. (more…)
Our customer executives delivered some inspiring presentations at our recent Informatica World conference on how master data management (MDM) is enabling strategic business imperatives such as increasing revenue by making more relevant cross-sell offers, improving regulatory compliance with more effective reporting, and streamlining key business processes such as order-to-cash to improve the customer experience. A big thank you to all the presenters for sharing their stories!
These innovative companies are using MDM to better leverage their business-critical data about customers, products, channel partners, suppliers, employees and so on to do two things: 1) enable strategic imperatives or 2) solve pressing business problems. If you were at Informatica World this year, but were unable to attend these MDM customer sessions, you can get access to the presentations online by searching for these titles. (more…)
If you’ve wondered exactly what type of impact master data management (MDM) can have on improving B2B sales here’s a terrific opportunity to find out first hand!
I’m delighted to announce that Kodak, the multibillion-dollar global imaging company, will be joining us for a must-attend webinar on how it’s using a multidomain MDM solution to enable customer centricity and empowering its sales, marketing and customer service teams with access to a single customer view. (more…)
A few months ago we blogged MDM for the Business Masses, where we speculated that custom data governance applications for MDM would be the next step to enable business users to directly create and consume master data. We saw further evidence of this through Dan Power’s white paper detailing how proactive data governance – MDM hub as a system of entry – would be the next wave to benefit organizations looking to take the next step in their MDM journey.
It is exactly with this in mind that we released Siperian Business Data Director (BDD), a configurable data governance application that provides an intuitive, business-user focused, and easy-to-use interface by leveraging the Siperian MDM Hub services and MDM solution components. Since then our customers and partners have been busy using BDD in a variety of ways such as integrating with custom widgets and bringing in data from sources outside of the hub so that business users can view everything from within a single user interface through the BDD.
At the upcoming Siperian Masters User Conference scheduled for Tuesday and Wednesday, October 20-21 at the Hyatt Regency, Princeton, New Jersey, there will be a session where some of the most innovative BDD configurations and integrations will be showcased. The best, as voted on by a panel of judges and the audience, will receive the first ever coveted Gooey Award.
This contest, apart from being fun and interesting, highlights the fact that the most successful implementations for MDM come from adaptable and configurable platforms that allow an organization to gradually extend their MDM deployments as their business needs change. Throughout their MDM journey, they can also learn and benefit from best practices encapsulated as MDM solution components (BDD specific or otherwise) thereby ensuring their success.
Putting an MDM Hub in place can help make system integration easier and less costly. The reason behind this is simple: a system integration strategy that relies on a single data model, to which all the systems involved refer, is much less complex than one that is based on point-to-point integration. The Hub becomes a sort of Rosetta Stone, and the data model on which it’s based is the target of the system integration. Getting data into the hub – transforming it, cleansing it, standardizing it – is a fundamental part of any Siperian implementation. Getting the data out of the hub and into downstream systems is equally important in order for them to benefit from the corrected information and to allow business users to leverage the data operationally.
The biggest hurdle to overcome in getting golden copy data into the systems that require it is authoring and maintaining the transformation definitions. Regardless of transport mechanism – batch, JMS, SOAP, etc – the data will have to be transformed so that the format and values are usable by the receiving system. If the number of receiving systems is large and heterogeneous – and in some cases there are hundreds or even a few thousand such systems – then creating the transformation definitions and keeping them up-to-date is a substantial task. While there is no silver bullet that will magically solve the problem with a single click, there are some tools and techniques that can help decrease the effort and cost required:
Use a Transformation Discovery Tool: These tools work by first profiling the source and the target data stores (which means you have to have some data in your Hub, as well as in the destination). After profiling, they look for what are called “binding conditions”. A binding condition ties together a set of attributes in the source system with a set of attributes in the target system, with a high probability of representing the same information. Once a binding condition is defined, the tool determines the logic that will transform the source data into the destination. The output varies with the tool, but is usually either expressed in pseudo-code, or in SQL. When the number of downstream systems is high, and especially if the data model is complex, using a tool to help define the “guts” of the transformations can save a tremendous amount of time and money, when compared to doing it by hand.
Have a Single Transformation Platform: This may seem obvious, but a surprising number of system integration efforts end up being implemented piecemeal – each receiving system implements its own set of adapters in whatever language and using whatever application-specific tools it has on hand. This has the extremely undesirable effect of scattering the transformation logic throughout an organization, which makes maintenance and management of the integration a nightmare. To avoid this, keep all of the transformation in a single platform, with a single authoring environment, and preferably a single execution environment. Not only will this greatly decrease the complexity and cost of maintaining the downstream data syndication, it will also provide the possibility of reusing transformation and validation logic whenever possible.
Once the golden copy arrives at its downstream destination, the operational system can leverage it through the normal application interfaces and processes. There are some who might ask if it is appropriate to update the downstream records, or if alternative business processes or interfaces should be used directly against the Hub itself. All of these are good questions and once again speak to the criticality of having a Hub that can provide these options, if and when business needs dictate. Transformation is a continuous process, not only for your data, but for your business as well.
So you’ve finally managed to convince everyone who has a stake that building this MDM Hub is the right thing to do. You have the data ready to be loaded from a variety of applications (sources) and you are even preparing to provide a business user interface (See MDM for the Business Masses, It’s Time) to access the data. Then you get that bone chilling thought that reverberates down to your spine, are you going to be able to manage all of the authentication and authorization of the various new users of the Hub? Of course, you could issue new userids and passwords, that seems simple enough and Single Sign On seems appropriate. But can you really map all the roles and “rules of visibility” to data that belonged to Fred in the CRM system, while ensuring that Jane who only was able to see back office details in the ERP system continues to be similarly restricted in her view of the new combined master data?
Fortunately, most mature MDM platforms are expected to handle fine-grained security down to the cell level as well as having multiple ways of defining role assignments. Furthermore, your security infrastructure team would most likely have already been part of the MDM evaluation process and ensured that the MDM Platform can integrate with the incumbent security systems/infrastructure of choice. Finally that new MDM Platform you are using gives you comprehensive history and lineage of its master data for maintaining complete audit trails, which again allows you to further reduce risk and improve regulatory compliance.
Whew! You wake up in a cold sweat realizing it’s just a dream, everything is fine nothing to worry about; all this was included as part of the evaluation process … thanks to that blog post you read way back when …