One of the promises made to companies moving to DITA was the portability of content and flexibility in the approach to future system choices. Years after deploying solutions, many companies are still struggling to make their investment work the way they want and deliver the benefits promised. Other more mature industries have a more pragmatic approach to core systems with regular reviews and the ability to embrace change, what can we learn from this? Changing your CCMS needn’t be the herculean task you fear and may help you actually achieve the functionality you have always been promised. Bluestream have taken companies on this journey and developed a comprehensive methodology to ease the path.

1. Evaluating your CCMS
is it time for a replacement?
what can we learn from other industries?
Rik Page - Bluestream

2. It’s all about Me!
• Sales and Marketing Director at Bluestream
• Structured content since 2002
• Experience also gained in unstructured document
management
• Worked in the banking sector

4. 2005

6. 13 years on have you
reviewed your CCMS?

7. Yet you’ve replaced
countless other systems
• CRM
• Accounting systems
• Website platform
• ERP
• PLM
• Marketing

8. And replaced other things
• Mobile phone
• Laptop
• Car
• House
• Partner

9. Why not a CCMS
• Fear
• Cost
• Effort
• Will it deliver
• Frying pan to fire

10. Maybe you don’t need to?

11. The approach taken by banks

12. Core Banking System Evolution
Source Capgemini Coe Banking Systems Survey

13. External
• Regulatory Compliance
• Customers
• Competition
Internal
• Product and channel growth
• Legacy System Management
• Cost Reduction
Drivers for Change

14. • Operations
– Streamline processes
– Increase
interoperability
– Eliminate manual
operations
– Enable out-sourcing
of non-core
operations
• Technology
– Optimize costs
– Reduce maintenance
costs with legacy
systems
– SOA
– Build multi-channel
capability
• Business
– Reduce time to
market
– Improve compliance
– Generate sales
opportunities
– Enhance flexibility
– Consistent multi-
channel experience
Objectives

15. Building the Business Case
Define Business
Case
Set Business
Strategic Goals
Qualitative
Analysis
Quantative/
Financial
Analysis
Positive
Business
Case
Pursue
Transformation
Continue with
current system
NoYes
NoYes
Market Share
Product Portfolio
Customer Base
Operating Cost
Business Benefits
Customer Benefits
Strategic Gains
Implementation Costs
Maintenance Costs
Cost-benefit Analysis
ROI Analysis
Stakeholder
Buy-in

16. Benefits of Core Banking
System Transformation

17. How do you assess your system?

18. CCMS Evolution
Modular systems
which can be fully
integrated with 3rd
party tools such as
ERP, CRM, PLM.
Able to deliver print
and online content
to any device or
platform in any
language.
In–house developed
software with
limited functionality
Large expensive
systems with closed
APIs.
Light weight systems
with limited
functionality

19. Step One
Perform a quick sanity check
• Current performance
– Is it delivering all you want?
• The future
– Can it meet your future needs?
• Support
– Are you receiving the desired level of support
• Cost
– Is it cost effective

20. Step Two
Recognise your knowledge

21. • Operations
– Streamline processes
– Increase
interoperability
– Eliminate manual
operations
– Enable out-sourcing
of non-core
operations
• Technology
– Optimize costs
– Reduce maintenance
costs with legacy
systems
– SOA
– Build multi-channel
capability
– Integrate with other
systems
• Business
– Reduce time to
create content
– Improve compliance
– Generate sales
opportunities
– Enhance flexibility
– Consistent multi-
channel experience
Step Three
Build your requirements list

22. Step Four
Build the business case
Define Business
Case
Set Business
Strategic Goals
Qualitative
Analysis
Quantative/
Financial
Analysis
Positive
Business
Case
Pursue
Transformation
Continue with
current system
NoYes
NoYes
Market Share
Product Portfolio
Customer Base
Operating Cost
Business Benefits
Customer Benefits
Strategic Gains
Implementation Costs
Maintenance Costs
Cost-benefit Analysis
ROI Analysis
Stakeholder
Buy-in

23. Step Five
Develop your Use Cases
• Existing work
– Visit what works with current system
• Desired
– Address problems with current system

24. Step Six
Evaluate and Select
• Evaluate as a team
• Use your own content
• Score each Use Case
• Use a MOSCOW rating system
– Must have
– Should have
– Could have
– Won’t have

25. Step Seven
Deployment
• Development of integration
• Testing
• Dedicated team
• Support from new vendor
• Parallel or cut-over?
• Defined KPIs
• Review

26. Benefits of
CCMS Transformation

27. Conclusion
• You don’t need to put up with inefficient systems
• A change of CCMS can improve productivity
• Reduce costs
• Provide a superior foundation for future developments
• Other industries accept change

28. Questions