Off to AIIM 17 to Catch Up on the ECM Industry

Sunrise over the beach in Flagler Beach, Florida, near Orlando, site of the 2017 AIIM ConferenceNext week I will be representing Dominion Consulting at the annual AIIM Conference. AIIM is returning to Orlando after a three-year hiatus. A lot has changed in the industry since the last trip to Orlando. Even the events in the last year have changed the space quite a bit. EMC will not be present and any Documentum presence will be at the OpenText booth. An interesting cloud-based Records Management vendor from last year, RecordLion, was just bought by Gimmal. There will also be many discussions over Content Services versus ECM as the new label for the industry.

As always, the most valuable part of the AIIM Conference will be the exchange of ideas taking place between sessions and over refreshments. Another year of new experiences gained and lessons learned that the community can combine into success for everyone.

What’s in a Name?

There has been a lot of discussion about Gartner’s decision to reclassify their magic quadrant for Enterprise Content Management (ECM) as Content Services. Here at Dominion, we view the terms as complementary. ECM is the overall content management strategy and Content Services is a means to achieving ECM goals for larger firms.

Why larger firms? ECM, as it was originally envisioned, is hard. It required a massive investment to lay the groundwork for all content in the organization. When scanning older documents was taken into account, the investment to achieve the mystical vision of everything on one platform was challenging.

Content Services faces similar hurdles for organizations. While cloud providers like Box can remove the need to architecture scale, there is now a need to create unique user applications. This is no small hurdle for many organizations. Many vendors are providing frameworks for building user interfaces. It remains to be seen how flexible they are.

Here at Dominion, we are big fans of the Content Services approach to building content-centric applications. Whether we leverage Open APIs or CMIS (Content Management Interoperability Services), the approach works. With the user experience separated from the underlying content technology, one team can focus on solving the business problem while another makes sure that the content engine handle the information needs.

Exchanging Ideas

I would love to hear your thoughts on this topic. It is an interesting one that we’ll be exploring in depth over time. I haven’t even brought data, the other half of the information equation, into the conversation. When you consider the broader needs of Information Governance, the conversation really get interesting.

I will be in Orlando all week and I plan to spend it talking to people. You can reach me at any time through Twitter. We can discuss this or any of the industry developments.

If you can’t make it, feel free to leave your thoughts below.

0 1005

Trackbacks for this post

  1. […] industry entered AIIM17 with a debate over whether Content Services or Enterprise Content Management (ECM) should be the default name for […]