The three classes of Component Content Management Systems (CCMS) are Class 1, Class A, and Class Green. Each has its purpose and ideal use-case. None is better or worse than the other two.
Eric reviews each of these types and provide real-world scenarios (drawn from actual CCMS RFPs) where conference attendees will choose which class of CCMS is best suited to each. Eric’s talk will help the audience understand the characteristics of each class of CCMS, and help them gain real-world experience in applying these characteristics.
Presented November 27, 2018, at Quadrus Conference Center for Information Development World 2018.
2. THE THREE CLASSES OF CCMS
INFORMATION DEVELOPMENT WORLD 2018
ERIC KUHNEN
3. A CCMS DOES FIVE THINGS
Definition What This Means
Manages content at a component level Unique ID for each XML element (i.e., “component”)
Stores only one copy of a component One copy of each XML element, referenced by others
Tracks Component lifecycle Each XML element has its own versioning and history
Tracks Component lifecycle
Each XML element has metadata for
- Creator Date/Time
- Approval State
- Shared State
Preserves component relationships Warns before breaking XML-to-XML linkages
#idw2018
5. User Experience
• Authoring and Review user experience
• Nomadic Authoring user experience
• Subject-matter experts user experience
• Mobile Device user experience
• Documentation pertinent to
• Sophisticated Authors
• Reviewers
• Mobile Device users
Scaling and Administration
• System Scaling
• High Availability/Disaster Recovery
• Site Replication
• Reporting
• Authentication
• Administration
• Access Control
• Cloud and non-Cloud Best Practices
• Implementation Best Practices
CCMSS VARY BY…
#idw2018
6. THE CLASS A CCMS
Author and Reviewer user experiences
A single DTD or XML vocabulary
File-level access controls (i.e., “Read” and “Write”)
Basic workflow (Edit, Review, Translate, Publish, Archive)
Integration with a single composition engine
Administrative overrides and capabilities
Built-in reports
#idw2018
7. Wizard-driven, no-coding merge-conflict resolution
Search/replace operations
Attribute-level filtering for “view” and “export”
Element-level, sub-file referential integrity
Support for LDAP and Windows Active Directory
Nomadic Authoring
User roles/permissions
Concurrent users
Report-writer interface
Drag-n-drop user experience
Multiple composition engines
Full and incremental back-up
THE CLASS 1 CCMS
Author and Reviewer user experiences
A single DTD or XML vocabulary
File-level access controls (i.e., “Read” and “Write”)
Basic workflow (Edit, Review, Translate, Publish, Archive)
Integration with a single composition engine
Administrative overrides and capabilities
Built-in reports
#idw2018
8. Support for hundreds of users connecting from across multiple geographies around the world
Capacity to store millions of XML and non-XML components
Maintain a consistent performance profile as the scale of the deployment increases
Exactly the same product binaries in both SaaS and non-SaaS offerings
No pseudo-SaaS through remote-access or virtual-desktop technologies
SaaS tools in non-SaaS offering
Software service versus hosted
Support for Single-Sign-On
Mobile Device user-experience
SME User Experience
Multi-user file update
Restrictions on key operations
Wastebasket file-recovery
DTD-neutral implementation
HA/DR configuration
Data replication to other sites
24x7 support option
Wizard-driven, no-coding merge-conflict resolution
Search/replace operations
Attribute-level filtering for “view” and “export”
Element-level, sub-file referential integrity
Support for LDAP and Windows Active Directory
Nomadic Authoring
User roles/permissions
Concurrent users
Report-writer interface
Drag-n-drop user experience
Multiple composition engines
Full and incremental back-up
THE CLASS GREEN CCMS
Author and Reviewer user experiences
A single DTD or XML vocabulary
File-level access controls (i.e., “Read” and “Write”)
Basic workflow (Edit, Review, Translate, Publish, Archive)
Integration with a single composition engine
Administrative overrides and capabilities
Built-in reports
#idw2018
9. Case Study Alpha
• Supplier to the US Department of Defense
• 74 requirements presented like this:
• 1.1.1, Link management
• The system structural validity checks shall include checks for
completeness, broken links/associations, and orphan data.
• 8 paragraphs (about 1½ pages) covering:
• Business Drivers
• Expectations
• Operational environment
Case Study Beta
EXERCISES
• High-tech software supplier
• 71 requirements presented like this:
• 6.3.5, Version control that suits our delivery model
• Due to the number and frequency of our product releases,
we must have the ability to have topics and ditamaps for
specific product versions. Not only is this necessary for our
packaging and delivery processes, but it is also key for
successful reuse.
• 14 paragraphs (about 2 pages) covering:
• A description and problems with existing systems, tools,
processes
• Project objectives
#idw2018
Pause on this screen. People vote after opinions are expressed.
The three classes of a CCMS deal with ideals for usability
Class A sets a baseline utility. Write down something you think should be in the baseline utility for a CCMS that I didn’t include.
Class 1 adds a second layer of utility. It’s not that these are nice-to-have features. Instead, these are capabilities required for a specific operating environment.
Class Green increases the level of utility. Disagreements with these allocations?
If you have previous experience with CCMSs, you’ll find that none of the 20+ commercial systems fits neatly into any one class. The point of classification, though, is to help the market calibrate its needs and its budgets.
This leads me to the problem of expressing those needs <click> so you can buy what you need.
Which class CCMS fits best with Case Study Alpha? What do you think of the RFP snippet? <REVEAL Alpha’s characteristics>
Which class CCMS fits best with Case Study Beta? What do you think of the RFP snippet? <REVEAL Alpha’s characteristics>
Ideals versus Reality: CCMS systems don’t fall neatly into one of these three categories. However, a system that doesn’t support the five functions of a CCMS cannot manage information components at scale. It will look great in demonstrations, but it won’t scale. CISCO experience.
Wants versus Needs: take stock of your needs. If you’re starting out, you don’t need disaster-recovery or high-availability; those are very expensive add-ons. Focus on the user experience instead. If you’re mature in your use of XML information components, think about scalability and administration. Young, good looking systems look work great when you’re managing 100 items in a POC, but you’ll want to shoot the vendor when it crawls like a sick dog with 1,000,000 items. STMICRO experience.
Technology versus Partnership: you might select on technology, but you buy on relationships. Figure out a way to test vendors for what kind of partner they are. How are there references? What do they say when they talk about things going wrong? When things go wrong—and they *always* go wrong at some point—you want to trust that the person on the other end of the phone is in the fight with you.