09.02.2015 Views

Cloud Computing and SOA Convergence in Your Enterprise: A Step ...

Cloud Computing and SOA Convergence in Your Enterprise: A Step ...

Cloud Computing and SOA Convergence in Your Enterprise: A Step ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Value of BPM for the <strong>Cloud</strong>s 139<br />

Value of BPM for the <strong>Cloud</strong>s<br />

What does BPM br<strong>in</strong>g to the cloud comput<strong>in</strong>g table It is really another<br />

complete layer on the stack, over <strong>and</strong> above on-premise or cloud-based systems.<br />

Or, to be more specific:<br />

A s<strong>in</strong>gle <strong>in</strong>stance of BPM typically spans many <strong>in</strong>stances of systems, onpremise<br />

or cloud-based.<br />

BPM def<strong>in</strong>es a master application (or applications) that has visibility<br />

<strong>in</strong>to many encapsulated services <strong>and</strong> <strong>in</strong>formation.<br />

BPM leads with a process model, moves <strong>in</strong>formation among applications,<br />

<strong>and</strong> <strong>in</strong>vokes <strong>in</strong>ternal services <strong>in</strong> support of that model.<br />

BPM is <strong>in</strong>dependent of the services. Changes can be made to the processes<br />

without hav<strong>in</strong>g to change the source or target systems, on-premise<br />

or cloud-based.<br />

BPM is strategic, leverag<strong>in</strong>g bus<strong>in</strong>ess rules to determ<strong>in</strong>e how systems<br />

should <strong>in</strong>teract <strong>and</strong> better leverage the bus<strong>in</strong>ess value from each system<br />

through a common abstract bus<strong>in</strong>ess model.<br />

Let’s walk through a simple example. Let’s say you want to build a model<br />

airplane, <strong>and</strong> you have three ma<strong>in</strong> processes:<br />

1. The process of cutt<strong>in</strong>g the parts.<br />

2. The process of assembl<strong>in</strong>g the parts.<br />

3. F<strong>in</strong>ish<strong>in</strong>g the airplane (pa<strong>in</strong>t<strong>in</strong>g <strong>and</strong> attach<strong>in</strong>g the decals).<br />

These are the higher-level processes; of course, many processes will be<br />

conta<strong>in</strong>ed <strong>in</strong>side these processes.<br />

In the terms of BPM, we can def<strong>in</strong>e the three ma<strong>in</strong> processes as<br />

1. Cut parts.<br />

2. Assemble parts.<br />

3. F<strong>in</strong>ish airplane.<br />

And we have to build these processes on top of three source <strong>and</strong> target<br />

systems:<br />

1. Inventory (SAP; on-premise)<br />

2. Sales (Salesforce.com; application-as-a-service, storage-as-a-service)<br />

3. Manufactur<strong>in</strong>g (Amazon AWS; <strong>in</strong>formation-as-a-service)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!