Before my digression last posting into a perspective on ECM systems integrators … I was describing the characteristics of trusted ECM repositories (see Step 1 – Can You Trust Your Repository?). Picking up from there …
Since choosing the right repository or content storage location is so important, how can we objectively evaluate the repositories we have? Use this scoring model to assess and designate your content storage options (including ECM repositories) as Trusted Content Repositories (TCRs)
Level 0 – is missing key capabilities like security, basic content services and APIs. This category represents file shares, CDs and other relatively unsecure locations. These environments are flexible and useful but the missing capabilities cause us to lose confidence (or trust) in the content we keep there. Imagine building an application that delivers critical documents only to have an end-user delete the underlying files.
Level 1 – Missing key capabilities like repository governance and lineage. This category represents SharePoint, wikis and blogs and other environments with user controlled governance. These environments are fantastic for collaboration and are easy to deploy but are missing essential capabilities when the environment itself can’t be properly governed and secured in accordance with IT standards (including the ability to meet SLAs). Imagine building an application that depends on critical documents only to have an end-user retire the SharePoint site that used to content the needed documents or records.
Level 2 – Missing a few key capabilities to instrument and automate workflows like event management and content federation. This category represents most ECM repositories from major vendors like IBM, EMC, OpenText and selected others. The missing capabilities enable us to have confidence the right documents are designed as “trusted” so they can be found, automated and consumed with confidence.
Level 3 – Has all of the key capabilities. This is the optimal level for trusted content applications. Only IBM FileNet P8 has all of these characteristics today.
Remember … if you can’t trust your repository you can’t trust what is in it, can you? Critical content must be stored in Trusted Content Repositories … it’s that simple. Next time we’ll explore what it takes to create and maintain trusted content. In the mean time, leave me your feedback on the model.