“Publishing in the Cloud” just sounds cool, doesn’t it? There are so many options for SaaS implementations within a publishing operation of ANY size and at a fraction of the cost of many enterprise systems, migrating to the cloud seems like a no-brainer – especially for small and mid-size publishers. No matter your size however (even if you’re a one-man show), change is never easy and cost is only one consideration when making a systems-oriented transition. In this session, Michael Covington, Director of Digital Content, David C Cook, will quickly walk you through the challenges, pitfalls, benefits and opportunities of adopting cloud-based business processes as a small to mid-size publisher. This session will help publishers better understand why and when cloud-based solutions make sense (and when they might not) for small to mid-size publishers.

1. 7.26.12
Legacy is a f*&r letter word
getting past embedded technology and embracing a
service-oriented architecture
Michael Covington, David C Cook www.davidccook.org, michael.covington@davidccook.com

2. 1 2 3 4 5 6
Leaving
Becoming When SaaS Final
Me DCC the
SaaSy Stinks Thoughts
Legacy

3. Why should we listen to this guy...
...and so much more
Husband/Dad
DCC
Practitioner
Bookseller
Me
Industry wonk Consumer
CBA
BISG
ECPA

4. Who is Dave?

5. Define the terms
Outdated, embedded technology, which in most
Legacy cases is on-premises, requires intensive ongoing
I/T support and breeds pockets of “tribal
knowledge”.
Service A culture that embraces efficiency without
compromising quality - where cost and
Oriented productivity live in harmony with one
Architecture another.
The business processes which support the
Publishing actual process of publishing.

6. Some examples
christianmanuscriptsubmissions.com
Rights & Royalties Administration
ECPA TMW/Content Services
Pubtrack/Pubnet

7. Becoming ‘SaaSy’

8. Why SaaS?
1 Lower upfront $$$
Please
hold yo
ur app
2 Scaleable lause
3 Less need for I/T
4 Better support
5 Less “Tribal Knowledge”

9. When does SaaS stink?
an do that.. .for a cost
AKA “We c
1 Lower upfront $$$
1 Rigid
2 Scaleable
2 Not secure
3 Less need for I/T
3 Doesn’t play w/others
4 Better support
4 Stinky people
5 Less “Tribal Knowledge”
5 No SLA!

10. How SaaSy is DCC?
ERP
(JD Edwards)
C+
Rights &
Productivity Royalties
(MS Exchange) (That’s Rights;
Bookmaster)
D.A.D.
Production (Firebrand CS, Analytics
Eloquence, (IBM Cognos,
(Firebrand) NetGalley, PubTrack)
Ingram)

11. Can we embrace a SOA?
Does it do what we need?
Does it create efficiencies?
What’s the true cost?
Can I get buy in?
Will they promise to perform?

12. THANK YOU!