Revisiting ECM in a 2.0 World
•
2 j'aime•738 vues
When ECM was first conceived, people created content, it was published, and then nothing else happened until it was time to update the content. Then came the 2.0 world. The world at large went from consuming content to interacting with content. This was a new mindset for the Content Management world. Instead of one author, or a few authors working together, content now evolves over the course of years through the input of any number of people. Discussions about content have become information worth capturing. The line between structured and unstructured information is fuzzy and no longer back and white. The need to share all of this information has also increased dramatically. This is the slides from the Gilbane Boston, 2010, session that looked at these challenges, and more, outlining how to leverage new technologies and architectures to prepare Enterprise Content Management for the next decade.
Recommandé
Recommandé
Contenu connexe
Plus de Laurence Hart
Plus de Laurence Hart (11)
Dernier
Dernier (20)
Revisiting ECM in a 2.0 World
- 1. Revisiting “Enterprise” Content Management in a 2.0 World Laurence Hart Washington Consulting, Inc. December 2010 1 See Speaker Notes
- 2. Why Listen? Information Management 15+ years Document Management Records Management Enterprise Content Management Web Content Management XML Collaboration (Grandfather of Enterprise 2.0) Digital Asset Management AIIM Interoperable Committee CM Pros, Chair Standards Group Author, Word of Pie http://wordofpie.com http://twitter.com/piewords Director, Technology Solutions, Washington Consulting, Inc. 2 See Speaker Notes
- 3. 3 My content growing, evolving, and expanding. Cloud brings rain or hope? See Speaker Notes
- 4. In the Beginning 4 See Speaker Notes
- 5. Then Came Scanning 5 See Speaker Notes
- 6. Followed by Process 6 See Speaker Notes
- 7. And Everything Else Email Management Web Content Management Digital Asset Management Collaboration Records Management 7 See Speaker Notes
- 8. Email Management Content Applications Web Content Management Digital Asset Management Collaboration Records Management ECM Project ECM Project ECM Project Process Services External Interfaces (SOAP, WS-*, RSS, REST, RPC…) The ECM Platform Content Services Library Services Enterprise Content Management (ECM) is the strategies, methods and tools used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. ECM tools and strategies allow the management of an organization's unstructured information, wherever that information exists. - AIIM Website, November 2010 Grand Unifying Theory Define ECM CCA Analytics Forms Reports 8 See Speaker Notes
- 9. Two Problems 9 See Speaker Notes
- 10. For Example U.S. Citizenship and Immigration Service Over 1 million new legal immigrants per year Average storage per file, 70 MB Keep for 99 years 75+ TB/year with ZERO back-file conversion Over 16 million benefit claims per year Everything is audited Multiple agency access 10 See Speaker Notes
- 11. Two Outcomes 11 See Speaker Notes
- 12. Web 2.0 Conversational Web 1.5 Transactional Meanwhile Web 1.0 Informational ECM Content Management ECM 12 ECM See Speaker Notes
- 13. Dev/Test Design/Dev Why the Lag? Req/Design ECM Release Cycle Req/Dev/Design/Dev… Internet Generation Year One Year Two Year Three 13 See Speaker Notes
- 14. Focus on the User The Ether Tags: Proposal, Widgets, Draft, XYZ Inc Share: Mary(Partner)/Edit Tags: Approved Share: XYZ-Purchasing /Read 14 See Speaker Notes
- 15. Simple Access 15 See Speaker Notes
- 16. Simple Access 16 See Speaker Notes
- 17. Most Overused Word 17 See Speaker Notes
- 18. 3-Step World Conquest 18 See Speaker Notes
- 19. Map of the Future Omnipresent Content Management Features Architecture 19 See Speaker Notes
- 20. Map of the Future Omnipresent Content Management Features Architecture 20 See Speaker Notes
- 21. Map of the Future Omnipresent Content Management Old Guard Features Challengers “We Matter” Architecture 21 See Speaker Notes
- 22. The Change Enterprise Content Management (ECM) is a strategy for the coordinated management of all content throughout an organization, allowing for people and systems to find and use content from within any business context. Omnipresent Content Management (OCM) is the coordinated management of all content throughout the world, allowing for people and systems to find, use, and share content from within any context. 22 See Speaker Notes
- 23. You Ready? Twitter: @piewords Blog: http://wordofpie.com Email: lhart@washingtonconsulting.com 23 See Speaker Notes
Notes de l'éditeur
- A #CMSHaiku to set the tone.
- There was paper, and there was a lot of it. (Still is)
- Now we put the paper onto the digital network, but it just saved a few trees, but we still printed, signed, and scanned back into the network.
- We took advantage of the electronic and re-vamped our processes.
- There was more than Transactional Content Management/Document Management. Other systems popped-up, and then they started to be linked together. Eventually everything became a Record and one-way integrations became two-way.
- The idea of ECM was to unify the technology and make life simpler. It works well in theory, but it is complex, growing, and difficult to implement successfully.Formal definitionAdd a platformPlug-in the applicationsAdd interfaces to talk to other applicationsNeed to use best practices as ECM implementations fail regularlyAdd new features as they are identified
- Meanwhile, content was growing exponentially and users grew on both sides of the firewall. Large “ECM” installations can quickly become mired in solving the technical issues of managing storage, data, and users, while not focusing on the business problem.While all those Content Management features have been added, there have been 2 massive problems building.More Content to ManageLots of users to manageMore unmanaged content than there was when I started in this profession35 Zettabytes by 2020 (2010 IDC Report) http://www.datacenterknowledge.com/archives/2010/05/04/digital-universe-nears-a-zettabyte/3.5 billion Library of CongressesGiga->Tera->Peta->Exa->Zetta->Yotta
- 10TB ~1 Library of CongressThis example can readily push the limits of even the most robust technology solutions out there. Keep in mind, this is just ONE type of content at U.S. CIS.
- The sheer complexity of implementing these systems, can take their toll on Content Management experts.
- The evolution of the Web, the consumer technology world. Improved interface increases expectations, increases content/data generated/collected, and the sheer number of users has increased as well.Conversations take place across boundariesManaging that interaction, live interactions cannot be “Approved” firstScale is growingThe Management of Enterprise Content has not evolvedFocus in the Internet is on the User, need it at workEnable conversations and collaboration without boundaries
- “Enterprise” software has long development cycles between major releases. This is okay as you don’t want to upgrade some of those systems within your organizations every six months. On the flip side, innovation is increasingly difficult as those systems grow in size and complexity. For example, SharePoint 2010 still looks shiny, but how will it look in 2-3 years when the next version is nearing release?Where is the Agility?Stable platform, SaaS, enables innovation on the application layerConsumers no longer have to worry about migrations, upgrades….
- Steve finishes a proposal and saves it. During the process, some tags are applied (manually and/or automatically) and he marks it for sharing. Mary is automatically notified and reviews the proposal. Once done, she adds an Approved tag and Shares it with XYZ’s Purchasing department. No email, no sending of links, no concern over what system everyone happens to use by default.Tagging can manual, automatic when analytics are smarterThis all nice, but why does it matter?Not necessarily the “cloud”, blend of Internet, Intranet, and LocalIf we don’t have to worry about the Management of Content (because it just happens), we can solve the user’s problems
- Need to have both content AND Identities in the Ether. Do not confuse identity with personal information. There won’t be one single source for either. Trust is a factor, and not everyone will trust/like Microsoft, Google, Facebook, or Apple.This isn’t the generic “cloud”. This is Software as a Service. UI and Services.This isn’t centralized, this is coordinated.
- Reasons for separate systemsInter-connect, then they aren’t “silos”, they are part of the solutionOpen standards can leave the silos, but make them accessible
- The key here is that the complete system appears as one system to people. Think about email. There are lots of different systems, but people work within one system and collaborate with everyone regardless of the system they use. Users are aware of different systems, may choose which system they use, but on a day-to-day basis, it doesn’t matter. Why can’t Content Management be like that.Store, Link, AbstractA single, Federated/Virtual repository.Work with anyone, anywhereOpen Standards are criticalDNS system, “Where is Laurence’s Content?”Leverage power of the “cloud” for Content Analytics, build that tagging
- For lack of a better term, let’s call it Omnipresent Content Management (OCM). It is ever-present, pervasive, and everywhere. People won’t think about the system, they’ll just do their work. There are two basic types of vendors, established vendors with the needed feature set and young vendors with the necessary “cool” architecture. Not all are heading in towards OCM, but some in each set of vendors are heading there now.They are in a race to get there, whether they realize it or not. Claiming the mindshare by arriving first will be critical to vendors that want to “lead” in the future (3-5 years). I expect only 1 of the “Old Guard” to successfully make the transition. It doesn’t mean that the others will fold, but they will lose their leader status in the industry.
- ECM is still relevant, but it is just a strategy. You still need to manage your content, but it doesn’t need to be centralized. Standards, such as the new Content Management Interoperable Services (CMIS) standard, will allow the separate systems to work together without having to spend all the time writing integrations and policies.OCM is an extension. The lessons learned from ECM will apply. Standards are even more critical, but the same ones can be used. The goal is lofty, but it will let us get back to working and collaborating without thinking about any of the mechanisms.