MIT Case Study: Learning how to work smarter at PSP Investments


Published on

Jeanne Ross, Director at MIT Sloan School of Management and author of "Enterprise Architecture as Strategy" wrote this case study about my work at PSP.

Published in: Technology, Business
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • “Level 1 BFM describes roles, main tasks and data elements, types, and stewardship. A level 1 process starts and ends within a single function of the BFM and consumes and produces information from/for other processes in other functions. This insures clear process segmentation and isolation.” “The BIM initial derivates element set was design by Mike Bennett in 2007. With PSP’s support, Mr. Bennett then expanded this work into the EDM council semantic repository.”
  • Comment from PSP: For easier access to information, we prefer SQL views, which all reporting tools support (including ad-hoc reports from Microsoft Office and SharePoint) to web services which often require IT to deploy specific software to users before they can access it
  • This is the Public Markets function. Processes in red have projects attached to them. Top row is target (process) architecture. Bottom row is the enterprise data bus; space between shows data movement into and out of enterprise data bus. Middle (big) row shows that systems don’t cross processes, in general, and that they don’t directly feed each other data.
  • MIT Case Study: Learning how to work smarter at PSP Investments

    1. 1. The Information Based Organization: Learning how to work smarter at PSP Investments<br />November 12, 2010<br />This research was made possible by the support of CISR sponsors and patrons.<br />Peter Reynolds, Cynthia Beath and John Mooney contributed to this research. <br />
    2. 2. Working smarter through information managementat PSP Investments<br />Public Sector Pension Investment Board of Canada, founded 2000<br />Fiscal Year 2010 Net Assets C$43.6B<br />Statutory goals: manage funds in the best interests of contributors and beneficiaries, maximizing investment returns without undue risk of loss<br />How PSP works smarter:<br />Focus on clean data enterprise-wide as PSP moves from a diversified to a coordinated operating model<br />Need to understand full portfolio to manage exposure risk, evaluate opportunities, and measure performance to be effective at active investment management<br />Need accurate and consistent financial reporting<br />Need consistent transaction and position data for business unit level analysis and decision making<br />Enablers: <br />Enterprise architecture: business function model, business information model, and enterprise data bus as part of a Service-Oriented Architecture<br />Organization structure and roles: governance, data stewardship, business integration team and data quality & optimization team<br />
    3. 3. Enterprise architecture models enable separation of processes, information and roles<br />Business function model (BFM)<br />Details six business functions, each with a process owner: public markets; private markets; investments; finance & treasury; process and information management; and enterprise support<br />Defines business function boundaries, process decomposition, and process governance; each business function has a process owner<br />Shows what information is produced and consumed in each process, ensuring process segmentation and isolation<br />Business information model (BIM) <br />includes top-level information domains, with clear boundaries and data governance model. <br />Shows how applications are used to perform tasks in BFM. <br />All business cases must specify how a project impacts BFM and BIM<br />
    4. 4. Examples of top level of Business Function Model and Business Information Model<br />Source: PSP internal documents, used with permission<br />
    5. 5. Enterprise data bus supports PSP’s data focus<br />Enables data cleaning via PSP rules at the source, so each type of data exists in only one version and is usable by everyone<br />Only master data moves between systems<br />Decouples data from systems and processes, simplifying changes in any of them<br />Implemented via reusable information services using SQL; supported by all reporting tools<br />Different from a typical data architecture in which all data goes to a data warehouse, which leads to a complex logical database interface and tightly coupled systems, processes and data.<br />Raw data<br />Clean-<br />sed data<br />Master data<br />Capture, ensure accuracy and timeliness <br />Apply semantic and quality rules<br />
    6. 6. High Level BFM : processes, systems and datarelationships for one function<br />Source: PSP internal documents, used with permission<br />
    7. 7. PSP’s organization for working smarter<br />Governance committees for each of the six business functions<br />Project governance in accordance with target architecture<br />Portfolio prioritization  which data is cleaned and mastered next<br />Data quality and optimization team – across the organization<br />Monitors data quality<br />Fixes exceptions as per PSP rules<br />Business integration unit – outside of IT<br />Data governance (prior experience showed IT should not be responsible for this)<br />Oversight of process governance<br />Has credibility to work with both IT and business groups<br />Data stewards are accountable for a given piece of information. Is “last gate”: person who must say the data is right; often the producer.<br />Example: transaction data: trader writes raw transaction, counterparty vets it to make it a master executed transaction, and back office transforms it into a confirmed transaction. Different entities, so different data, and different stewards, even though in most cases the physical data about the transaction is unchanged. <br />External data (e.g. Bloomberg) has no steward, as PSP can’t fix its errors<br />
    8. 8. Working smarter in practice<br />Engage the business to define information needs<br />Proactively explain why data, drilldown, and analysis is important, focusing on real cases<br />Manage the business’s expectations on timeframes<br />“Feed” data to the organization<br />COO requests ad-hoc reports for complex situations that uses data that he knows exists<br />Show the value of clean data for speedy reports<br />E.g., response time if ad-hoc reports had clean data is 10x faster<br />Make sure the infrastructure is reliable<br />If IT can’t keep systems running, they can’t be trusted to implement the new architecture and data capabilities<br />
    9. 9. Benefits to PSP of working smarter<br />Clean, transparent, consistent data entered only once reduces operational risks<br />Lower data cleaning and maintenance costs, fewer external data sources, and reuse of services that expose the data reduce operational costs<br />Fully encapsulated processes, data and systems, which can then be optimized independently increase business agility<br />More efficient and effective risk management removes need to add staff even as the organization grows<br />New types of risk analysis are possible with the proper data<br />Systems are up more because a major cause of failure was bad data<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.