The Matrix: Remixed BPM + SOA = Results-Oriented Architecture Linus Chow Charles “Flip” Medley Clay Richardson

The Problem There is an “operational disconnect” between Business and IT Business missions demands more capable systems and greater automation from IT IT wants more resources to support efforts to build better solutions Both want to do the right thing and work together, but…

There is an “operational disconnect” between Business and IT

Business missions demands more capable systems and greater automation from IT

IT wants more resources to support efforts to build better solutions

Both want to do the right thing and work together, but…

The Blue Pill: Business “ I need situational awareness tools that can give me the information to do my job…” “ I need the tools to execute my missions as quickly & efficiently as possible”

“ I need situational awareness tools that can give me the information to do my job…”

“ I need the tools to execute my missions as quickly & efficiently as possible”

The Red Pill: IT “ I need detailed use cases so I can build the right solution…” “ I need the resources to do my job… people, processes, and infrastructure.” “ I’ll build it and come back to you with a finished product…”

“ I need detailed use cases so I can build the right solution…”

“ I need the resources to do my job… people, processes, and infrastructure.”

“ I’ll build it and come back to you with a finished product…”

The Common Questions “ What am I supposed to do?” “ How many resources am I being allocated to accomplish this task?”

“ What am I supposed to do?”

“ How many resources am I being allocated to accomplish this task?”

Are you fighting with your solutions? Poorly implemented “solutions”: May not solve the original problem(s) the business is facing Adds cost and complexity Limits the business’ ability to do its job well Lack the flexibility to cope with change

Poorly implemented “solutions”:

May not solve the original problem(s) the business is facing

Adds cost and complexity

Limits the business’ ability to do its job well

Lack the flexibility to cope with change

Have we been here before? BPM is not BPR! “ Let’s refine your org charts…” “ Let’s analyze your processes and then we’ll make some recommendations…” “… and good luck implementing them after we leave!” “… and we’re not going to show you how to enact those recommendations, since that’s not our area of expertise.” BPM is about enabling business agility by insinuating the business in to every element of the development lifecycle Keep the focus on getting results!

BPM is not BPR!

“ Let’s refine your org charts…”

“ Let’s analyze your processes and then we’ll make some recommendations…”

“… and good luck implementing them after we leave!”

“… and we’re not going to show you how to enact those recommendations, since that’s not our area of expertise.”

BPM is about enabling business agility by insinuating the business in to every element of the development lifecycle

Keep the focus on getting results!

Have we been here before?

Have we been here before? SOA is not a technology-centric approach: “ Thanks to OO we can make systems that mimic your business concepts…” “ Now that we have CORBA …” “ Java will allow us to…” “ Now that we have web services …” SOA is all about finding and building reusable services from your IT application infrastructure These services can be leveraged directly by your BPM processes.

SOA is not a technology-centric approach:

“ Thanks to OO we can make systems that mimic your business concepts…”

“ Now that we have CORBA …”

“ Java will allow us to…”

“ Now that we have web services …”

SOA is all about finding and building reusable services from your IT application infrastructure

These services can be leveraged directly by your BPM processes.

SOA: Baseline

SOA: Orchestrate

SOA: Compose

SOA: Results

SOA + BPM BPM is a foundational component of an SOA The big secret: SOA = BPM + … BPM encourages a results-oriented focus encourages best practices and reuse of artifacts across mission stakeholders

BPM is a foundational component of an SOA

The big secret: SOA = BPM + …

BPM encourages a results-oriented focus encourages best practices and reuse of artifacts across mission stakeholders

SOA + BPM = Results

Results-Oriented Architecture Service Infrastructure Application Infrastructure Service Service Service Service Service Service BPM End-Users Community Community Community Solution Governance IT Asset Governance Service Governance Enterprise Security Infrastructure Service Bus Service Management Service Registry Service Repository

Results-Oriented Process Engage stakeholders throughout the mission context during the development process Propagate design artifacts across the entire mission context Maintain the visibility of all artifacts across missions to promote reuse

Engage stakeholders throughout the mission context during the development process

Propagate design artifacts across the entire mission context

Maintain the visibility of all artifacts across missions to promote reuse

“This time, it’s going to be different…”