Faster and more efficient processes by combining BPM and Mobile – yes we can!

Sebastian Faulhaber | Red Hat

Schnellere und effizientere Prozesse mit Mobile und BPM - aber sicher! Faster and more efficient processes by combining BPM and Mobile – yes we can!

Year 2000

11%

Year 2013

93%

It’s a Changing World “By 2017, 70% of mobile professionals will conduct work on personal, smart, mobile devices using at least one form of application containment.” Gartner Nov 2014

“39% of all companies and 48% of larger companies are finding it difficult to distribute mobile applications to their workers' devices, and around a half are struggling to apply consistent security policies to their mobile assets.” Yankee 451 Nov 2014

From Systems of Record to Systems of Engagement

What others are saying...

Bringing service excellence and customer service to a new level

INSURANCE FACTORY FOR CLAIMS PROCESSING

Multi-Channel Input Scan & Detect

Manual takeover in case of error

Automatic Processing through BPM engine

€

3rd Party Eval SW

A new generation of healthcare

Quelle: www.wikipedia.de

Opportunities for Human Centric BPM / Case Management

●  BENEFITS: ●  New dimension of customer service ●  Customer gains transparency on process

●  e.g. Call Center (Case Handling) ●  e.g. Customer Self-Service ●  e.g. Process Portal

Opportunities for Straight Through Processing

●  BENEFITS ●  Even higher Automation Rate & faster processes ●  Drive process efficiency

●  e.g. Claims Processing in insurance industry ●  Automated processing of applications (e.g. for a

bank account)

The mobile maturity journey

SETTING THE STAGE WHAT YOU SHOULD THINK ABOUT

When thinking about mobile you have to consider a lot!

Architecture of traditional JEE Applications

Traditional Applications Everything happens in the AppServer

Mobile Architecture Similar to known architectures of JEE

Native Android / iOS / Windows Phone

•  Native libraries allow direct access to device specific features

•  FAST! Games are possible •  Use of platform specific

processes (gradle, ant etc.) •  Best for native looking and

behaving Apps

•  Developers need to work with platform specific languages like ObjectiveC, Java, C# etc.

•  Every platform has its own IDE and processes

•  No developer can be an expert on every platform

BENEFITS DRAWBACKS

•  Apache Cordova abstracts the complexity of creating mobile apps for different target devices

•  Cordova allows access to target device specialties like camera or GPS

•  Cordova allows users to create device independant UIs via HTML5 and CSS3 and JavaScript

•  Best for Business / Enterprise Apps

•  Apache Cordova does not allow all the special device specific capabilities

•  Slower than native Apps. Impossible to create Game-like Apps

•  Need of special UI libraries to make the look „native“

•  Extensive JavaScript KnowHow needed

BENEFITS DRAWBACKS

•  Writing everything for every platform in C# and .NET

•  Visual Studio and .NET framework for those who like it

•  Commercial framework (done by the original MONO developers)

•  Quite „native“ look and feel

•  Visual Studio and .NET framework for those who don‘t like it

•  It comes with its own developer workflow (based on Visual Studio)

•  Again... .NET and C#???

BENEFITS DRAWBACKS

Expect more devices....think of millions!

BPM API

Think of cloud techniques for the middle tier!!!

Store and forward / Queueing

You need to think beyond Java in the cloud tier

Mobile imposes new security aspects

Transport Level Security

Data security on device?

API Management is crucial

Source: http://theburningmonk.com/2014/08/red-white-push-continuous-delivery-at-gamesys-social/

What about the state in your BPM engine?

Short Running Processes Briefly persisted Long running processes

😀 😨 😭

Additional layer of abstraction needed (mBaaS)

BPM API

You don‘t want to have a tight coupling here!

Establishing a common build

process is not easy

Last but not least...expect organizational challenges

Mobile projects typically have a different set of stakeholders!

Mr. IT Marketing Agency

SUMMARY SO FAR

* With some specialities concerning state handling (process instances)

1.  BPM is “just” another backend system*

2.  Most challenges arise from mobile aspects

CASE STUDIES

•  Forms-based workflow solution for field service workers in the UK

•  Rolling out to 10,000+ workers

•  Video, photo, location & signature capture

•  Ease of integration with backend systems

Work Order Management

A strategic solution for workforce mobility across the business

Mobilising the work of 15,000-20,000 mobile employees Integrating with 200+

backend systems

Securely distributing 300-400 mobile applications and solutions to support: •  Process automation •  Field force automation •  Emergency response •  Health and safety •  Real time reporting and analytics •  Asset management

Rail Infrastructure Provider: Improving Workforce Productivity

30

Customer Service •  Customers able to access information regarding services performed on their installed base of elevators

anywhere, anytime •  Secure login and authentication in the cloud to access, view & monitor to work order level •  Secure integration with TKE RSS and other social feeds •  On premise deployment

KEY TAKEAWAYS

Think about a mobile application development platform approach ** / *** •  Abstracts variety of different OS and frameworks •  Provides processes for versioning, build management •  Brings together all stakeholders and enables

collaboration •  Establishes a standardized approach

** Gartner Rule of three ***otherwise you will reinvent the wheel, definitely

Use mBaaS concepts •  DataStorage API •  Device Syncing and caching

Features •  Push Notification Abstraction •  Online / Offline Workflow •  Integration with social networking •  Secure connectivity to legacy

systems •  Automated REST based APIs •  And all of that hosted on premise

or in the cloud like a PaaS •  Agile delivery of updates

Think about scaling massively •  Make use of cloud techniques •  Make use of async techniques to protect your BE

systems (e.g. store and forward)

Be flexible about the UI framework •  This area is evolving rapidly, expect frequent changes •  UI framework should not be imposed by mobile

platform

Cloud based mobile application Platform approach

Backend

Systems

Backend Systems

mBaaS Shared Business

Services

Authentication

Encryption

Offline API

Centralized Mobile API with Core Services

...

Mobile Client

Devices

iOS, Android, Windows Phone et al

HTTPS

Local encrypted Data store

Recommended architectural approach

BPM API

Red Hat is working hard to repeat the story of Linux

for Mobile

https://www.redhat.com/de/technologies/mobile/application-platform

NOW IT‘S YOUR TURN!

LET‘S CHANGE THE WORLD WITH MOBILE

AND BPM! I would love to hear your feedback! – NOW or later. J

E-Mail: sebastian.faulhaber@redhat.com

Twitter: @faulhaber_it