What word or phrase does every IT Leader hate to hear? What's the coolest thing that's ever been done with our Middleware products? IT Uncensored is a showcase of thought leadership about all aspects of IBM Middleware from your perspective. These experts get real about middleware—and themselves.
Impact Day 2: A composable business runs on composable processes
Delaney Turner 270003RQ8K Delaney.Turner@ca.ibm.com | | Tags:  bpm ibmimpact
1 Comments | 3,620 Visits
Marie Wieck's message to attendees on day 2 of IBM Impact was simple: a composable business runs on composable processes and those processes drive - or are driven by mobile.
Citing findings from the IBM Institute for Business Value, Wieck said composable business processes rest on four components:
Evidence of all four working together came in the form of Scott Megill, co-Founder and CEO of Coriell Life Sciences, whose genomic health care solution rests in large part on IBM software. Winner of the 2014 IBM Entrepreneur of the Year Award, Corielle is taking advantage of the falling cost of genome sequencing to offer healthcare providers access to the world's leading experts in genomic interpretation, while delivering the concise clinical data they need for patient care.
The Coriell Life Sciences "ecosystem" allows healthcare providers, patients and payors to take advantage of the available sequencing technology while carving out and interpreting only that data needed for immediate use and securely storing the data in the GeneVault for future interpretation.
Corielle is also a powerful example of IBM's increasing and increasingly successful outreach to young developers. "IBM isn't just for the big multinationals anymore," said Megill.
Rationale and resources for going mobile
Later in the day, IBM Product Manager for Business Process Manager Deepak Elias supplied the rationale and provided resources for adding a mobile dimension to BPM.
First, he cited a Forrester Research report projecting 8X growth in mobile process reinvention (to $7.6 billion) and 2X growth in mobile application development services (to $5.6 billion) by 2015.
Next, he used the example of a snowed-in airport and the resulting flight cancellations to show how mobile-enabled processes could help an airline allay or even prevent travellers' invective on the front lines while managing through the disruption on the back end. For example:
Without this industry veneer, Elias' idea boils down to two key concepts: Patterns and Benefits. Any organization, regardless of industry, would be wise to explore them.
Relevant Mobile Patterns include:
Relevant business Benefits include:
Connecting the two lie enabling processes. For example:
"A mobile-enabled smarter process can act like the grownup in the room," said Elias. "It can give you the ability to respond to and manage outcomes in changing situations across multiple stakeholders."
Going mobile in the enterprise with James Taylor
My last session featured longtime enterprise decision management analyst James Taylor in a session entitled The Mobile Enterprise: Driving the Need for Better Decisions & Smarter Processes. (Get the slides here!)
User expectations have changed, said Taylor. Mobile is increasingly consumers' primary channel for interacting with organizations. Many expect a better experience on their phone than in the store. Further, as evidenced by the BYOD movement, employees increasingly want to work remotely and on their own schedules.
Hence, the new requirements for the mobile enterprise:
The New Backend
Unfortunately, said Taylor, most back-end systems are "woefully inadequate" to respond to these requirements. Where mobile apps encourage personalization, most legacy enterprise apps are built for standardization and repeatability. They offer neither localization awareness nor personalized user experiences.
The biggest problem, said Taylor, was that on their own they don't help us make better decisions. "They're actually dumb as posts."
For example: they can't automate or anticipate the intersection of every conceivable aspect of a mobile experience. Does location matter? Yes. All the time? Maybe. Further, it's not enough for an app to simply present or summarize data. The mobile form factor forces the system to know which data matters and why.
Much like a banking or retail app, the successful enterprise mobile app delivers an experience that's localized, personalized, guided and data-driven.
So how do we get there? Taylor provided three steps:
"Excellence in mobile requires systems that make decisions."
Tomorrow I'll explore what's new in IBM BlueWorks Live. Until then, follow #IBMImpact to stay in touch!