2

Imagine!

Earlier this month our Managing Director for Informatica in ASEAN, Suganthi Shivkumar, wrote an article entitled “Data Integration Helps Achieve Business Goals”.

I have reposted it here with permission from CXOToday.

Data Integration Helps Achieve Business Goals
Imagine a world where IT is perfectly aligned with the business. Accurate, relevant information flows freely throughout the enterprise, driving timely decisions and actions. The IT infrastructure is flexible and designed for reuse ensuring that companies don t just respond to changing business requirements and competitive pressures, but stay ahead of them. And in an ideal world, IT delivers real, measurable value to the business, supporting key goals such as:

  • Growing revenue. Companies have a comprehensive understanding of their customers. A 360-degree view of customers provides the insight and knowledge needed to drive sales, marketing, and customer service. By accurately anticipating customer needs, companies increase their cross-sell rates and improve customer retention.
  • Streamlining business operations. Business operations run smoothly and efficiently, and noncore functions are outsourced. Reliable, timely information is readily available to support business processes, no matter which system or organizational boundaries those processes traverse. And the data across processes are synchronized, ensuring consistency in business operations and visibility across the enterprise.
  • Ensuring regulatory compliance. Organizations have a single version of the truth to report to regulators and auditors, reducing the compliance burden. Information sources and changes are automatically documented to provide an audit trail, ensuring absolute confidence in the quality and accuracy of the information. In an ideal world, IT organizations are agile and highly responsive to changing business requirements. They provide solutions that align with strategic business goals, delivering measurable business impact. They rationalize their IT infrastructure. With increased efficiency, they coordinate efforts across the enterprise to reduce overall costs and deliver more with less.

Battling Data Fragmentation & Its Impact

But this is the real world. Strategic business initiatives often trigger one or more major IT projects implementing a single view of customer, synchronizing multiple operational systems to support an end-to-end business process, or consolidating multiple applications to reduce costs.

IT organizations struggle to deliver against the requirements of the business. They’re inhibited by the brittleness and complexity of their existing IT systems and infrastructure. And they don t have resources to spare most efforts are dedicated to keeping the lights on.

What’s a key cause of these problems?

Data fragmentation.
Data resides in disparate silos throughout the enterprise. For example, customer data may be scattered over dozens if not hundreds of different applications, databases, and legacy systems.

These silos may have sprung up organically, as different business units implemented their own projects independently, or they may have been acquired via a merger. Either way, organizations of all sizes combat the proliferation of data silos. The content, quality, structure, and definitions of the data in these silos are as variable as the silos themselves. Users lack confidence that the data they need to run the business is comprehensive and accurate. Without a single view of relevant data and a consistent understanding of its meaning enterprise-wide, different groups or systems may produce different answers to the same questions based on their own versions of data. Moreover, as business complexity grows, timelines accelerate, and data volumes increase, the problem of data fragmentation becomes more difficult to solve.

Data fragmentation impedes efforts to grow revenue, increase operational efficiency, or ensure regulatory compliance. Putting enterprise data to work to achieve business goals means addressing the data fragmentation problem. To ensure that business decisions and operations are based on trustworthy, timely, holistic information, almost every initiative calls upon IT to access, integrate, and deliver data.

Accessing data alone is no easy trick. Data can be found throughout the enterprise, in multiple disparate systems and in many different formats. Data is scattered everywhere on the mainframe, in databases, in obscure legacy systems, in spreadsheets on desktops, in enterprise resource planning (ERP) applications, on message queues, in files.

Data then has to be cleansed, aggregated, and validated, and put into a form that is meaningful to the applications and users who need it. In today s stringent regulatory environment, data also needs to be governed properly. Organizations must track and document where their data came from, how it has changed, and who has changed it to meet audit requirements of such regulations as Sarbanes-Oxley. And the security of data must be ensured throughout the whole process.

So what’s the solution?

Data integration.

Data integration allows organizations to access all their fragmented data, create an accurate and consistent view of their core information assets, and easily leverage these assets across the enterprise to drive business decisions and operations.

Unlike application integration, which is focused on transaction management and process integration, data integration resolves the complex issues that arise out of data fragmentation. These issues include poor data quality, inconsistencies in the structure and meaning of data, and inadequate data governance.

Organizations are using data integration in many different ways to drive business value. They are implementing real-time reporting and analysis to optimize minute-by-minute operational, as well as strategic, decisions. They are using data integration to migrate data into new applications, or implement master data management. They are also using data integration to synchronize data across operational processes and systems, and to create flexible, reusable data services.

Managing Data Integration Across An Enterprise

The Costs of Complexity:

Organizations should look to data integration technologies that can be used across a broad range of initiatives, including data migration, data consolidation, data synchronization, data warehousing, and the establishment of data hubs and data services. But functionality alone is insufficient to address the full scope of data fragmentation in most enterprises.

Historically, IT organizations have approached data integration on a project-by-project basis. Depending on the needs of their specific project, one IT team might use an extract transform- load (ETL) tool. Another team might hand-code scripts, in conjunction with enterprise application integration (EAI). Yet another might use an application vendor s tools.

Over time, the result is a proliferation of one-off data integration technologies. The wide range of data integration approaches results in a complex, brittle IT infrastructure that s extremely costly to manage. As IT organizations take on new initiatives such as outsourcing a business function the complexity only increases.

Today, many organizations are adopting a common, enterprise approach to data integration one that leverages a unified platform, is built on shared services, and supports competency centers.

Such shifts are often part of a larger movement to rationalize the IT infrastructure, with the goal of reducing costs and increasing agility. Also, today s increasingly strict regulatory environment demands a more consistent approach to data integration and data governance. Organizations need to ensure they provide consistent answers to questions from regulators, and they need to properly document all data to certify its validity.

Approach: Integration Competency Center

Every data integration project is different and includes many variables – such as data volumes, latency requirements, IT infrastructure, and methodologies.
Integration Competency Centers (ICCs) have emerged as a best practice for enterprise data integration. ICCs are an organizational approach designed to increase agility and reduce implementation costs by promoting reuse, sharing best practices and resources, and establishing common processes and standards for integration. ICCs facilitate cross-enterprise collaboration and coordination for global IT teams, including both internal and external resources such as systems integrators and outsourcers.

Conclusion
While many organizations are migrating to an enterprise-wide approach to data integration, almost no one can afford a high risk, big bang implementation. It is critical that data integration evolves over time, with an incremental rollout focused on delivering urgent business requirements now, while laying the foundation for an enterprise-wide data integration infrastructure for the long term.

The author is MD, South Asia of Informatica

FacebookTwitterLinkedInEmailPrintShare
This entry was posted in Data Integration, Governance, Risk and Compliance and tagged , , , , , , . Bookmark the permalink.

2 Responses to Imagine!

  1. Charles Heiser (Don) says:

    While I agree with everything written here, I submit that a fundamental component was omitted from the paper. While many organizations are establishing Integration Competency Centers (ICC), most are underfunded to accomplish what needs to be accomplished. One of the reasons IT has such a difficult time integrating data is the funding model used by their firms. Logically, it makes all the sense in the world to establish an ICC but when it comes time to open the wallet, few step forward. As I’m sure many are aware, the financial benefits of an ICC are not normally realized in the first year. It takes time to demonstrate the value of the ICC and frankly, dollars must be spent before dollars can be saved. Since many companies use an annualized budget cycle, it is often difficult to get funding for something that won’t realize any benefits in the year funded. While establishment of an ICC will be positive for the Enterprise, the line of business(s) being asked to fund this effort may see little benefit to their bottom line.

    Having lived this challenge, I believe the best way to maintain some level of funding while at the same time, driving the Enterprise to seamless integration of data is a blended model. Using this model, individual projects that don’t necessarily support the Enterprise view will be supported. Chargebacks for those projects will include all pro-rated costs to develop and operate the projects as well as a percentage overhead fee. This overhead fee will be used to pay for the growth/expansion of the ICC (People, Process and Tools) as the ICC is tasked for more Enterprise level integration activity.

    The main roadblock with this model is the Finance and Accounting rules in place at the firm. In many firms, IT is a non-profit organization so the notion of a fee to internal lines of business is a foreign (and often forbidden) concept. To make this happen, a close partnership with Finance is critical along with Senior Executive support.

  2. As Don rightly points out, funding issues are the bane of integration. He also highlights some of the reasons why it is so challenging. The article certainly could have addressed this point at a high level, but it is such an important topic that it deserves a separate write-up.

    The ICC book by John Schmidt and David Lyle lists 7 competencies that an ICC must have in order to operate indefinitely – Financial Management is one them. It is a surprise to some people that it is on the list, so I’m glad that Don pointed out the importance of this dimension.

    In fact, John and David added a lot more detail to the 7 competencies in 2008 which is now available to Informatica customers and partners through the Velocity methodology. Interestingly, of the 7 ICC competencies, Financial Management is the longest document and contains the most detailed practices in order to overcome the challenges that Don mentions.

    In terms of finance and accounting rules being a major roadblock – I agree. The advice from the ICC experts on this issue is twofold. First, establish a close partnership with Finance to work with the current policies and practices in the short term. Second, take a long-term perspective and work with senior leaders to change the policies in ways that more effectively support a lean and agile organization.

    Changing policies is not easy (or quick), but the Velocity methodology addresses this dimension also by providing prescriptive principles and practices on the role of ICC staff as organizational change agents.

    You can find out more about the Velocity methodology from our web-site, or by contacting Informatica.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>