Federated Virtual Universal Can You Have It All

The many dimensions of Content Integration No Content Mgmt Control Content Mgmt Control Accessed outside a Dctm Application Accessed within a Dctm Application Stored in a Stored outside Dctm a Dctm Repository Repository © Copyright 2009 EMC Corporation. All rights reserved. 3

Customer Scenario: Application in the Cloud Current State: Use salesforce.com - want to manage & secure the content files involved in selling process Insufficient content mgmt functionality Prefer to keep files behind your firewall Solution Content Services for Salesforce CRM Others: Leverage integration based on CMIS © Copyright 2009 EMC Corporation. All rights reserved. 4

Integrations  Content Services for Salesforce CRM  Content Services for SAP  Content Services for SharePoint  Content Services for EMC Centera  Content Services for NetApp SnapLock  Content Services for BEA Portal © Copyright 2009 EMC Corporation. All rights reserved. 5

Benefits of a Standardized Repository Standardized repository infrastructure  Can present a single, simplified architecture to manage  Simplifies system administration  Benefits of efficient reliable storage for all applications Common repository  Easier to share between applications - benefits of unified repository to non-dctm apps  Facilitates search / eDiscovery  Facilitates policy mgmt  Easier to migrate between versions, when content is in one place © Copyright 2009 EMC Corporation. All rights reserved. 6

Levels of Control Content management enabled repository  Can add security & retention  No matter which application creates, you can put the content mgmt controls on it  Can scale up level of control without migration or integration concerns © Copyright 2009 EMC Corporation. All rights reserved. 7

Virtual Content Management Accessed outside a Dctm Application Accessed No Content within a Dctm Mgmt Control Application Content Mgmt Stored in a Stored outside Control Dctm a Dctm Repository Repository © Copyright 2009 EMC Corporation. All rights reserved. 8

Driver: Governance, Risk & Compliance  Customer A has 500 different repositories, 23 billion objects – Want to manage from a single control point – Retention for compliance – Hold for legal support – Disposition for cost management © Copyright 2009 EMC Corporation. All rights reserved. 9

Driver: New, Improved applications  Customer B wants single point of access for End users  Want new applications to draw from multiple existing systems – Legacy users of legacy apps need not change  The application would move content across repositories © Copyright 2009 EMC Corporation. All rights reserved. 10

How VCM works (Not Federated)  The master system is like a dispatcher  We track virtual objects which include pointers to source systems – Source systems: ECM systems, ERP systems, File Share drives  Direct operations to source repositories through an adaptor layer – Currently offer native adaptors provided by partner  Search, check in and out, version…content remains in place © Copyright 2009 EMC Corporation. All rights reserved. 11

Elements of our Virtual Content Management CRAWLER / MONITOR SCHEMA MAPPING •Proxy Objects •Schema Mgmt •Metadata Mgmt •Operations •In‐place or Copied META CATALOG Adaptor Framework •Search •Versioning •Discovery •Locking •Classification •Retention © Copyright 2009 EMC Corporation. All rights reserved. 13

Standards based integrations  Structured: SQL  Semi-structured: XQuery  Unstructured: CMIS  CMIS is a standard for integrating with ECM systems – Eliminates adapter risk because most will support CMIS – Will be adopted by ECM vendors and non-ECM vendors – Won’t need an SI for upgrades  Tie it all together: XProc –For when you need to combine both sources in a single application © Copyright 2009 EMC Corporation. All rights reserved. 14

Benefits of Virtual Content Management  Migrate if and when cost effective – Could leave in place forever – VCM creates a buffer so can migrate over time – Minimal impact on business operations – Use old and new systems simultaneously  Not federated – which has too many dependencies  Governance, Risk & Compliance  New Applications built on the shoulders of others © Copyright 2009 EMC Corporation. All rights reserved. 15

MDM “Entities”  Documents get meaning from their relation to something defined by data  “Entities” give context and relevance to data – Lung x-ray Patient name – Invoice Supplier name – Loan application Customer name  Entities can be described with different terminology which causes conflicts – Financial/Credit: Card Holder, Member, Customer – Medical: Patient, Client, Member © Copyright 2009 EMC Corporation. All rights reserved. 17

Standardize Instances Susan Hong Susan Smith Susan Smith 110 51st Street 110 51st Street 26 Suburban Lane Apt. 3 Apt. 3 Stamford, CT New York, NY New York, NY © Copyright 2009 EMC Corporation. All rights reserved. 19

MDM brings consistency and accuracy Content management + MDM = accuracy and efficiency Documentum FileNet Home Grown General Practice Blood Lab X-Ray Dept. Member Donor Patient © Copyright 2009 EMC Corporation. All rights reserved. 20

Use Case: NY City Current state: Customer has 6 agencies managing healthcare information Each Borough has and needs independent systems Different CM vendors  Different data models Information duplication  Different vocabularies Goals: Needs solutions that work across Agency boundaries Manage information from umbrella solutions Improve data quality & consistency Provide single point of policy management Unify vocabulary Add new functionality in a consistent way © Copyright 2009 EMC Corporation. All rights reserved. 21

Use Case: Leading Global Data Provider Current state: Data provider in multiple industries Data stored in different geographical silos Data stored in RDBMS & CMS systems No single data model Native applications serve local data Goal: Build centralized solution to discover relevant information across silos and manage it Add collaboration and BPM Improve data quality © Copyright 2009 EMC Corporation. All rights reserved. 22

Business Drivers for Data/Content Integration (Gartner)  Run The Business – Improves the accuracy of business process – improves business user decision making  Growing the Business – Single view of customer helps to understand customers – Master product data can speed time to market  Transforming the Business – Foundation for modeling and simulation from different organizational perspectives – Clean information can be shared with external partners – Not sufficient by itself, but without it transformation strategies are too hard or too expensive © Copyright 2009 EMC Corporation. All rights reserved. 23

MDM Hype Cycle  Organizations have a fundamental need to have one validated record of a patient, citizen, customer, or product to enable greater organizational efficiencies, meet compliance and grow revenue opportunities. Gartner’s hype cycle for Master Data Management states:  Through 2012, 70% of SOA projects in complex, heterogeneous environments will fail to yield expected business benefits unless MDM is included.  Through 2012, due to the lack of a sufficiently business-oriented approach, appropriate governance and accompanying metrics structure, 60% of MDM programs will be regarded as failures. © Copyright 2009 EMC Corporation. All rights reserved. 24

Get Involved with EMC CMA Communities Why should you join?  Collaborate and share best practices  Shape the direction of future EMC products  Network with innovators across the globe, 24/7 Join now by going to: community.EMC.com/go/Documentum community.EMC.com/go/SourceOne developer.EMC.com/Documentum developer.EMC.com/XMLtech community.EMC.com/community/labs/d65 © Copyright 2009 EMC Corporation. All rights reserved. 26

Federated Virtual Universal Can You Have It All

0 comments

Notes on slide 1

Favorites, Groups & Events