How To Use Content Services To Modernize Your Enterprise
•
1 recomendación•70 vistas
The document discusses implementing information management strategies through content services. It defines enterprise content management and information governance, and describes how content services provide a platform to access these through APIs. The document cautions that past strategies failed when they were too ambitious and did not bring all elements together. It recommends starting information modernization with content services by addressing existing problems gradually with an agile mindset, as governance and management strategies are still important.
Recomendados
Recomendados
Más contenido relacionado
Similar a How To Use Content Services To Modernize Your Enterprise
Similar a How To Use Content Services To Modernize Your Enterprise (20)
Más de Laurence Hart
Más de Laurence Hart (14)
Último
Último (20)
How To Use Content Services To Modernize Your Enterprise
- 1. Implementing Information Management By Addressing Challenges One At A Time Laurence Hart, CIP Director, TeraThink How to Use Content Services to Modernize Your Enterprise August 28, 2018
- 2. 1 Enterprise Content Management (ECM) 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. Information Governance (InfoGov) The overarching and coordinating strategy and tactics for all organizational information. It establishes the authorities, supports, processes, capabilities, structures, and infrastructure to enable information to be a useful asset and reduced liability to an organization, based on that organization’s specific business requirements and risk tolerance. Historic Definitions Copyright © 2018 TeraThink Corporation
- 3. 2 Enterprise Content Management (ECM) 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. Information Governance (InfoGov) The overarching and coordinating strategy and tactics for all organizational information. It establishes the authorities, supports, processes, capabilities, structures, and infrastructure to enable information to be a useful asset and reduced liability to an organization, based on that organization’s specific business requirements and risk tolerance. Historic Definitions Copyright © 2018 TeraThink Corporation
- 4. 3 Content Services Is… The How Of ECM And InfoGov, Not The What A Platform Accessed Through APIs Best Suited For Government And Large Enterprises
- 5. 4
- 6. 5
- 7. 6
- 8. Federated Repositories Repository to Repository Application to Repository
- 9. 8 Things Didn’t Go As Planned… Waterfall Failed Went Too Big, Too Fast Modeled The World Never Brought It All Together
- 10. 9 Copyright © 2018 TeraThink Corporation
- 11. 10
- 12. 11
- 13. 12 Must Be Cautious As… Information Governance & ECM Still Matter Agile Is More Than A Process Modernization Takes Time, Don’t Rush It
- 14. 13 Copyright © 2018 TeraThink Corporation
- 15. 14 Content Services Opens New Possibilities… Content Analytics Transparent Information Governance Gradual Migration Of Information
- 16. 15 Content Services Are Not New, Just Evolved You Still Need To Have A Strategy In Place First An Agile Mindset Is Not Optional You Should Start With An Existing Problem
Notas del editor
- Discuss the Hype of the Content Services from Gartner.
- InfoGov comes from the IC, ECM comes from me. LOTS OF WORDS
- Strategy is important. So are the processes, requirements, and everything else. None of this goes away or changes. ECM may be a dated term but it has always worked best when it was a Strategy
- And when we talk large enterprises, we are talking Government Opened in 1827 in Washington County, MD
- Content Services Are more that a tech. It is a strategy for implementing these complex systems. An Approach For Implementing A Content Management System. The beauty is that as your needs evolve, the abilities can evolve. This isn’t a one size fits all situation. This is an approach where we definitely see the creation, retrieval, update, and delete of content.
- However we can add transformation, image recognition, auto-classification, and records management behind the scenes Services have been around for a while in concept but the maturity of how has changed dramatically.
- Needed a restart in some ways so it could be built upon. Many versions before and since
- Back in 2009, I was demonstrating the CMIS standard at the AIIM Conference as part of the iECM Committee effort. The Application to Repository use case is really what we are talking about except we are redefining the Interface to be more business centric and the repo is built in a new manner Of course the CMIS Interface is an orchestration layer that manages everything. Routes the necessary information to the key components
- CMIS mostly got token support. Open source, like Nuxeo and Alfresco, strongly supported but most checked the box As for ECM… Too big too soon. Waterfall Model the world Everything on one platform We didn’t bring it ALL together The industry is ready for change
- The industry is ready for change
- Talk about the flexibility of the cloud. It isn’t new but it is evolving to be more flexible. Cloud has led to DevOps. While technical, this has made it easier build and grow Agile is replacing waterfall in the broader mainstream. MVPs and slowly growing is important This is all important
- Things have worked when they were custom. These are custom chocolates. One set vanilla, habaneros, and a flavored gin. These were picked to meet a flavor palette. User interfaces need to be developed to meet a specific task. Apparently we’ve learned that we have to create something people can use readily. Training is fine but 50 page manuals on how to use a system need to go away We are moving away from Excel spreadsheet. Old-school JAD sessions and new, creative, ways to garner feedback are making it easier to determine what has to be done
- Yes and No. Really only useful for larger enterprises because there is a critical mass of complexity that need to be met before it really has value. Also stress how it doesn't replace ECM or InfoGov. The goal is to get out of the cycle of the new system every few years. Bringing you full circle from the old Washington Monument to the new. More polish. Better architecture. Better Everything. Started 20 years later and took 40 years to finish
- API approach. Things are much more mature now Put together what you need, when you need it. Not everything at once. (and rarely this cool) API development. Pull all the services together. Content Services are both a consumer and a provider Uber and Lyft isn’t a lot of code. Google maps, payment services like Paypal, It can also be incorporated into other applications like event apps and drink tracking apps. Works with other information systems but can bubble up into ServiceNow just as well as custom apps.
- Yes and No. Really only useful for larger enterprises because there is a critical mass of complexity that need to be met before it really has value. Also stress how it doesn't replace ECM or InfoGov. The goal is to get out of the cycle of the new system every few years. Bringing you full circle from the old Washington Monument to the new. More polish. Better architecture. Better Everything. Started 20 years later and took 40 years to finish
- Stress that even if narrow in scope, understanding the entire domain will help so