1

P a

r t

n e

r f

o r

P u

b l

i s h

e r

s

Integrating Online Business Processes

or

“The Next IT Explosion V 2.0”

Moscow3 October 2006

G. WolfChief Technology Officer

Klopotek AG

2

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

This session is to explain why integration of back office ERP software and your website will become a MUST

3

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

Supply chain integration needs

Plan Produce Promote Sell Distribute Post distr

ERP

DigitalDAP

DAM / Content Mangmt

DARDAD

Editorial & Production

Marketing & Sales Order Processing

Physical Warehouse

Shop

Portal

Shop

4

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

The fairy tale of standalone online subscriptions

5

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

Standalone online subscriptions

How this usually works

Technical arguments:

1. Access control where the content is!

2. Buy an access control software or CMS with this feature

3. Add the subscription information (start, end, number of users, ….)

4. That’s it

5. Invoices? Renewal? Marketing? Customer Care? Finance? A customer service department problem!

6

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

Standalone online subscriptions

How this usually works

Social environment:

1. The website is smart, new and the developers are young and cue (they drink Caribbean Espresso)

2. The ERP is old-fashioned, boring, and there is only one developer left who speaks Cobol (filter coffee)

3. The ERP cannot do this

4. The ERP people do not understand the Web!

5. Communication is so complicated (with filter coffee drinkers), we can do this alone

7

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

And the result?

A workflow break between separated ordering and access control End user cannot shop and use the acquired subscription

instantly Authorization manually to be sync’ed with order status

(start, end, renewed, cancelled, …) – likely never in sync Or (if ordering is implemented in the content access system)

No blended products business models Good chance for wrong price, tax, charge calculation Substandard customer service due to separate system

information Duplication of technical processes, e.g. interfaces to finance

In any case, never a complete and consistent view on the business with the customer

8

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

The better approach

ERP – Content web site integration:

Enhance your ERP with online products and blended products

Authentication and content access on the website

Authorization, subscription and orders in the ERP

Real time back office integration with AAA

Web services, or

Real-time message driven

9

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

Product Planning

Production Planning

ProductionCMS

Sales Order Processing

Ware-house

Manage-ment

Web Portal Web self care

Web CMS

Web Shop

The fairy tale of the SOA

10

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

The brave new SOA world

„Integrate everything with a mouse click“

„Graphical workflow description“

„Assign web services“

Customized workflow and usability

Finished!

Ok, we have to migrate some older application to SOA first…

11

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

What is SOA?

SOA is

“A paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations.”

(OASIS Organization for the Advancement of Structured Information Standards)

12

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

“[it is]…the creation of automation logic in the form of services. Like other design paradigms, service-orientation provides a means of achieving a separation of concerns.“

(Wikipedia)

What is SOA?

13

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

What is SOA?

“There is no widely-agreed upon definition of service-oriented architecture other than its literal translation „that it is an architecture that relies on service-orientation as its fundamental design principle. […]

(Wikipedia)

14

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

What is SOA?

SOA is style, not a technology and not a standard

SOA is so generic that it can be used for everything and nothing

but

there are standards to implement SOA (e.g. SOAP, WSDL, UDDI, WS-BPEL, …)

These standard make it much easier to integrate systems

So, besides the useful for software architects, it is a considerable approach to integrate systems

17

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

The fairy tale of „production management with a CMS“

18

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

Let‘s do it in the CMS!

How this usually works

1. Production management = workflow

2. Our CMS is a workflow management tool

3. Product metadata is a simple attachment of fields to the content

4. Let’s implement production planning in the CMS

19

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

The truth

Editorial and production is equally content management and metadata processing

Editorial has a calculation and decision making process which takes place, before any content is created…

Production needs a process planning and monitoring tool

Production needs a price calculation tool

Production needs a supplier database, a bibliography database, an author database, … function to create letters, export the schedules to suppliers, …

Rights sales, Rights acquisition, Contracts, Royalty accounting, … all important, but has nothing to do with content

20

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

The better approach

Integrate a strong metadata backoffice planning software with a CMS

1. Editorial and production planning in the planning software. Metadata workflow in the planning software (calculation, scheduling, decision making, product planning, addresses, communication, …).

2. Content and Content workflow (versioning, building, storing, finding…)

3. Link between bibliographic metadata and related contents

21

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

New challenge „digital assets“ workflows (DAD, DAR, …)

22

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

Digital Asset Distribution and Order Fulfillment

DAP DAM DARDAD

CMS

Workflow

Peer review

Content compilation and construction

CMS

Store

Find

Mass data

Make available

CMS

Classify

Find

Make available

Added value and service

forward

CMS

Find

Promote

Sell

23

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

Digital Asset Distribution and Order Fulfillment

Can your order fulfillment software deal with DAD?

DAP DAM DARDAD

Order fulfilment booksellerWarehouse

11

2

24

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

Digital Asset Distribution and Order Fulfillment

Can your order fulfillment software deal with DAD?

DAP DAM DARDAD

Order fulfilment booksellerWarehouse

1

2

3

25

P a

r t

n e

r f

o r

P u

b l

i s h

e r

s

Conclusion?

26

P a

r t

n e

r

f o

r

P u

b l

i s h

e r

s .

Conclusion

1. The time for non-integrated publishing software dinosaurs is over

2. The time for too many and too small niche solution is over

3. Reduce the number of core application, but integrate those

4. Don‘t let the technology vendors tell you that you need this all

5. The same data in different systems is bad. The same function in different system is worse

6. Use already integrated publishing software solutions, e.g. for editorial and production, or for contracts and rights and royalties

…and integrate those with website, cms and finance…

27

P a

r t

n e

r f

o r

P u

b l

i s h

e r

s

Thank you.

www.klopotek.com

Klopotek is the leading supplier of international standard software and consulting services for publishers.