Alfresco is bringing their Alfresco Days series of events back to D.C. again on May 23. The 2019 Alfresco Government Summit focuses on generating discussions around leveraging Alfresco as a platform in the cloud. Specifically, as an open source content services platform living in AWS.
TeraThink will be there again this year to talk about how we make content services work using Alfresco in AWS. We have been leveraging the content services platform (CSP) approach to deploying enterprise content management (ECM) for a few years. During that time, we’ve learned a lot of lessons. We will be bringing that expertise to the Application Platform Revolution Panel moderated by Alfresco founder John Newton.
Before the 23rd, I want to take a few minutes to giving you a preview of some of the thoughts we will be sharing.
A few weeks back, I spoke on an Information Coalition webinar with Nick Inglis about getting Beyond the Hype of Content Services. We discussed content services and tried to separate the reality from the hype. If you been following, there is a lot of hype out there and has been since Gartner stopped tracking ECM (enterprise content management) and switched to content services. This has fed people’s instinct to equate content services with ECM. Many vendors and consultants are now taking their marketing messaging and simply substituting one term for the other. Even more distracting are people that reflexively reject content services because they assume the person using the term is just doing a term swap.
The truth is that content services is not ECM. It is an approach to implementing solutions that support an ECM strategy and providing sound information governance. Content services doesn’t eliminate the need for an ECM strategy or information governance. In fact, if you don’t have a strategy or proper governance, you might end up addressing the wrong things.
You still need a plan. To determine how to implement it, you need to know what content services is and how it can make a difference.
Another year and another AIIM Conference in the bag. It was a good year as the industry seems to be slowly coming to the realization that while content is a problem, the solution is to solve the business problem, not necessarily the content problem.
The industry entered AIIM17 with a debate over whether Content Services or Enterprise Content Management (ECM) should be the default name for the industry. The speakers, and attendees, basically uttered a massive, “Who cares?” We are solving problems and learning how to make sure that not just information can be found. Valuable information can be found.
There has been talk of creating enterprise content management (ECM) platforms for years. They typically do not live up to the hype or expectations. The upfront investment typically required dooms most projects before they deploy their first business solution. It has reached the point where if an organization wants to implement ECM I typically walk away if I cannot persuade them otherwise.
That doesn’t mean that the need for ECM platforms don’t exist. Given the ever increasing creation of content today, it is even more important to be able to rapidly solve content-centric problems without creating numerous content silos. What is needed is an alternate approach to gaining the benefits of an ECM platform without forcing a big-bang approach to ECM with its large upfront investment.
The answer is to pick an ECM system the same way an organization picks a database system. Choose based upon the system’s ability to scale and meet the needs of the organization. An open API (application programming interface) allows the exposure of content services that can be used to add content capabilities to other applications and to build new solutions. Being open allows an organization to move forward without worrying information being bound to that system forever.