Overview of CMIS in June 2010

3,344 views

Published on

An updated overview on the Content Management Interoperability Services standard after the release of the 1.0 version. Discusses where it stands, uses, benefits, Industry support to-date, and planning for the future.

Published in: Technology
0 Comments
8 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,344
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
85
Comments
0
Likes
8
Embeds 0
No embeds

No notes for slide
  • The key is the domain model and the agreement between vendors on what that model is. The Interfaces(bindings) will come and go over time, but the model is the foundation and strength of the standard.
  • There is more to the standard than hype. There will always be silos, sometimes for very good reasons. CMIS can bridge those silos and do much more as well.
  • This is the generic overview of how CMIS works. More specific examples will follow.
  • This example shows the traditional unified repository model. While that may exist, a hybrid approach of these three use cases is to be expected in most environments.
  • Hyland is working on it, but to-date, no announcement has been made.
  • Overview of CMIS in June 2010

    1. 1. Overview of Content Management Interoperability Services Standard June 2010
    2. 2. Overview Introduction What is the CMIS Standard? How CMIS can be used Benefits of CMIS Level of Industry support Future of CMIS 2
    3. 3. Washington Consulting At A Glance “Our Mission is to solve our clients’ most important business problems.” Business Founded 2003 Management and information technology consulting Headquartered in the Washington D.C. Area Wholly owned subsidiary of Alion Science & Technology Difference Highly skilled, educated and credentialed staff Balanced mix of Federal, commercial, and non-profit clients Our consultants live in the communities they work 3
    4. 4. Basic History of CMIS 2005 – iECM Committee begins discussing need for a new standard ODMA: Desktop dependent WebDAV: Limited capability Java Content Repository: Technology specific, API-base 2006 – EMC, IBM, and Microsoft leave the iECM Committee and begin developing CMIS 2008 – Initial proposal drafted by EMC, IBM & Microsoft Reviewed by Alfresco, Open Text, Oracle, SAP Draft was unveiled and released to OASIS 2008 – The OASIS CMIS Technical Committee formed 2009 – CMIS 1.0 released for public comment 2010 – CMIS became an official standard 4
    5. 5. What is CMIS? Content Defines a Content Management Management domain Interoperability model and set of interfaces, such as Web Services Service and REST/Atom, that can be used by applications to work with one or more Content Management repositories/systems. 5
    6. 6. There Has Been Some Hype No More Silos!!! 6
    7. 7. Mandatory Technical Slide 7
    8. 8. Three Fundamental Use Cases Repository to Repository Content repositories talk directly to each other Initial use case, breaking down silos Examples: Publishing, Records Management Application to Repository Applications that use content are plugged-into a content repository to handle all content services Examples: Collaboration/Enterprise 2.0, Enterprise software (BPM/CRM/ERP), Generic interfaces, Composite Content Applications Federated Repository Applications that talk to many repositories while presenting a single interface to the user Ex: Federated Search 8
    9. 9. Repository to Repository For example, managing content in a central Records Repository 3) Are records 1) Create are managed in documents Records repository CMIS 2) Documents are CMIS Content Records Repository Interface Interface Repository Declared as Records. 9
    10. 10. Application to Repository Using the best content application for the job against a shared Content Management system not shuffling content between systems. Instead of this… Resumes Proposals HR System: CRM System: Collaboration Resumes, Proposals, System: Proposal, Offer Resumes Deliverables Letters HR Content CRM Content Project Content Repository Repository Repository 10
    11. 11. Application to Repository …You can have this. CRM System: Proposals, Collaboration HR System: System: Proposal, Resumes Resumes, Deliverables Offer Letters CMIS Interface Content Repository 11
    12. 12. Federated Repository Federated repositories is interacting with multiple repositories as if they were one repository, such as conducting search for eDiscovery Search Manage Content Content Content Content Repository Repository Repository Repository 12
    13. 13. Federated Repository: iECM Demo 1. User conducts search 2. Federator sends request out 3. Repositories execute search and return results 4. Federator merges results 5. User acts on results iECM CMIS Search Federator (California, US) CMIS CMIS CMIS CMIS CMIS Interface Interface Interface Interface Interface Alfresco Documentum Nuxeo IBM eXo Repository Repository Repository Repository Repository (United Kingdom) (Amazon Cloud) (France) (Amazon Cloud) (Eastern Europe) Try it: http://www.aiim-iecm.org 13
    14. 14. Who will benefit from CMIS? CMIS can bring maturity to a fragmented industry and accelerate its growth Enterprises Unlock content without sacrificing investment Gain business flexibility, agility, & insight Developers Reduce development & maintenance cost Increase addressable market Users More content becoming accessible Cheaper & more abundant applications/tools Repository Vendors Increase demand for repository technology Create a horizontal market opportunity 14
    15. 15. Industry Support Large Content Management vendor support base Support: IBM, EMC, Open Text, Microsoft, and Alfresco Missing (so far): Hyland, Autonomy, and HP Microsoft support SharePoint 2010 as both a repository and application Released as part of SharePoint Administrator Toolkit Open Source Content Management support Chemistry project provided open source implementation All supporters of previous Java Content Repository standard will be able to claim CMIS compliance Next step is application builders 15
    16. 16. Future of CMIS Work on version 2.0 has begun Increased Records Management support Support for Semantic functionality New interface for Web 2.0 applications Ability to have domain models Real work begins in the Fall Waiting for experience to build Give people time to digest version 1.0 16
    17. 17. Summary Content Management Interoperability Services Official OASIS standard now Planned evolution to stay relevant Defines Content Management Domain Model Content model the same across all bindings/implementations Web Services and Atom bindings are ways to access model, not defining part of standard CMIS is not the lowest common denominator Defines functionality that is needed Some parts are optional to provide for a greater ecosystem It is in use now 17
    18. 18. Questions and Answers Thank You 1577 Spring Hill Road, Suite 450 Vienna, VA 22182 Phone: 703-752-3531 Laurence Hart Director, Technology Solutions lhart@washingtonconsulting.com 18
    19. 19. About the Speaker Laurence Hart is a Director of Technology Solutions for Washington Consulting, Inc. and the author of the blog "Word of Pie". Over his 15+ years in the Information Management industry, he has led a wide-range of efforts including content digitization, Records Management, BPM, and Collaboration for both the commercial and public sectors. Recently, Laurence has been focused on helping organizations in assessing, defining, and building their Information and Content Management strategies. Laurence has worked with a wide variety of vendors over the years and is sure that the list will continue to change. He is an active member of AIIM, the Enterprise Content Management association, where he is leading efforts to validate the new Content Management Interoperability Services (CMIS) standard, having spoken at multiple industry conferences on the topic. 19

    ×