BPM for Mobile, Mobile for BPM
•
4 likes•2,209 views
Scott Francis is the CTO of BP3 Global, a company that accelerates process innovation through business process management (BPM) solutions. The document discusses incorporating mobile into BPM and outlines some issues with retrofitting mobile. It proposes rethinking mobile BPM by using responsive user interfaces, hybrid apps, and REST APIs. The document also provides examples of how different types of processes and user needs might determine the best implementation interface.
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (7)
Similar to BPM for Mobile, Mobile for BPM
Similar to BPM for Mobile, Mobile for BPM (20)
More from BP3 Global, Inc.
More from BP3 Global, Inc. (9)
Recently uploaded
Recently uploaded (20)
BPM for Mobile, Mobile for BPM
- 1. Scott Francis CTO @sfrancisatx BPM for Mobile Mobile for BPM
- 2. BPM for Mobile, Mobile for BPM Thank You! Scott Francis | Co-Founder & CTO | BP3 Global @sfrancisatx www.bp-3.com/blogs Scott brings over 18 years of experience in the Software and Services business to BP3. Since 2007 he's helped grow BP3 over tenfold in revenue and personnel, by building the best team in the business. Scott comes to BP3 from Lombardi - one of the principle software providers in the BPM space and the precursor to IBM BPM - where he was Chief Architect and Director of Technical Services. @BP3BPM www.bp-3.com www.bp-3.com/blogs BP3 accelerates process innovation by simplifying BPM solutions and software experiences: implementations, mobile, cloud, and solution-oriented R&D. © 2012 BP3 Global Inc. All Rights Reserved.
- 3. BPM for Mobile, Mobile for BPM Mobile is Everywhere Surrounded: We are surrounded by huge increases in mobile adoption Pressure: With dramatic growth there is pressure to incorporate mobile into BPM or lose the chance to incorporate process methods in mobile Fueled by Fear of missing opportunity The predominant approach: Retro-Fit Mobile into BPM implementations © 2012 BP3 Global Inc. All Rights Reserved.
- 4. BPM for Mobile, Mobile for BPM What’s Wrong with Mobile BPM? Firehose of information . . . JUST LIKE EM AIL M ixing Processes and Notifications From Multiple Processes Too much info! New Tasks Reminders Notifications Everything Mixed Together in one View Not filtered/focused No unique process context/value enough We already have this problem, and it is called Email © 2012 BP3 Global Inc. All Rights Reserved.
- 5. BPM for Mobile, Mobile for BPM What’s Wrong with Mobile BPM? Re-using Desktop HTM L - Ignoring the Device! IGNORING DEVICE IGNORING DEVICE CAPABILITIES CONSTRAINTS Touch Controls... Screen Size Camera Screen orientation Accelerometer Connectivity Location (GPS) Typing Connectivity (LTE) It is Like a 3270 Terminal for your iPhone © 2012 BP3 Global Inc. All Rights Reserved.
- 6. BPM for Mobile, Mobile for BPM It Doesn’t Have to be this Way Rethinking BPM for M obile Opportunities RESPONSIVE UI HYBRID APPS REST APIs Adapt UI to the Leverage native Process-specific size of the screen capabilities Context baked into APIs Adjust UI to the Opportunity to deal orientation of the with constraints screen Touch interfaces even in HTML © 2012 BP3 Global Inc. All Rights Reserved.
- 7. BPM for Mobile, Mobile for BPM Drivers of Implementation Interface COST/CONNEC TYPE OF DEVICE TION TIME IMPLEMENTATION AUDIENCE USER TYPE INTERFACE EXTERNAL POWER HIGH (Customer) HOMOGEN NATIVE (Partner) FREQUENT HYBRID MEDIUM HYBRID INTERNAL (Employee) OCCASIONAL HETROGEN LOW HTML 5 © 2012 BP3 Global Inc. All Rights Reserved.
- 8. BPM for Mobile, Mobile for BPM Complexity vs. Value BUDGET/VALUE NATIVE HYBRID HTML5 REQUIREMENTS INFREQUENT TOUCH FREQUENT GPS POWER USE CONTROLS USE NOTIFICATIONS USE COMPLEX DEVICE RESPONSIVE SECURE BARCODE SPECIFIC UI DISTRIBUTION SCANS INTERFACE © 2012 BP3 Global Inc. All Rights Reserved.
- 9. BPM for Mobile, Mobile for BPM Typical Oil & Gas Process - Cementing Services Classify Prep Proposal Test Slurry Execute Job 1 New Job 2 Evaluate Risk 3 Order Materials 4 Prepare Invoice Primary Process Flow = HTML5 - Many screens, used by 17 Functional Roles - Many users may only need to interface with BPM once a month - Most screens must be functional on a mobile device, yet there are no requirements to use mobile device features like camera, location, etc. Materials Ad-Hoc = Hybrid Lab Ad-Hoc = Native - Most screens are required to be functional on - Used by 2 Functional Roles mobile and desktop devices - Users will spend their whole day in the app - Bar codes scanning is required on request - Test result entry requires only a tablet interface fulfillment - Frequent loss of connectivity © 2012 BP3 Global Inc. All Rights Reserved.
- 10. BPM for Mobile, Mobile for BPM Materials Request Subprocess Create a Request on the Desktop - Fulfill it on an iPhone © 2012 BP3 Global Inc. All Rights Reserved.
- 11. DEMONSTRATION Hybrid iPhone app with ad-hoc requirements © 2012 BP3 Global Inc. All Rights Reserved.
- 12. BPM for Mobile, Mobile for BPM Key Takeaways • Users/Customers demand Mobile apps • Ideally: one UI across desktop, tablet, phone • Trend is toward HTML5, Responsive UIs • Hybrid/Native apps bridge the gap • State of the art keeps evolving • Building UI in a single IDE (in this case, Process Designer) © 2012 BP3 Global Inc. All Rights Reserved.
- 13. BPM for Mobile, Mobile for BPM Thank You! Scott Francis | Co-Founder & CTO | BP3 Global @sfrancisatx www.bp-3.com/blogs Scott brings over 18 years of experience in the Software and Services business to BP3. Since 2007 he's helped grow BP3 over tenfold in revenue and personnel, by building the best team in the business. Scott comes to BP3 from Lombardi - one of the principle software providers in the BPM space and the precursor to IBM BPM - where he was Chief Architect and Director of Technical Services. @BP3BPM www.bp-3.com www.bp-3.com/blogs BP3 accelerates process innovation by simplifying BPM solutions and software experiences: implementations, mobile, cloud, and solution-oriented R&D. © 2012 BP3 Global Inc. All Rights Reserved.
Editor's Notes
- Create Materials Request (desktop) - record set of additives that are necessary for a given job Fulfill Materials Request (iPhone) - Look through the request, identify that the request is complete, scan the shipping container with the bar code scanner, ship Each request can be fulfilled through multiple shipments - this is where the “All Delivered” gateway comes in. if a request is not fulfilled through a given shipment more tasks are generated to complete the request fulfillment
- Need a better presentation of these ideas. third column is the summation of the issues in the first two...
- 1. image to be replaced with an ibm based screenshot 2. the first column is all “ignoring capabilities” 3. second column is all “ignoring constraints” 4. last column is the punchline - like a 3270 for your iphone
- Now - how do we approach solution - 1. Responsive UI- solve for the biggest constraint: screen size 2. Solve for second biggest complaint : rich touch interface 3. Hybrid apps to address native capabilities - bar scanning, GPS, accelerometer, etc. 4. APIs to put actions into process context (no “setData, getData style calls”) - example “startClassifyProject” “completeClassifyProject” or ... “callCab” for the Uber App
- Cementing Services : ---------------------------- Classify Project - Risk, Proposals, Materials, Lab Tests, etc will all be different depending on the type of project ... Some possible types are: Conventioal, High Pressure High Temperature, Deepwater. Proposal Approval - the contract detailing a given cementing services engagement Risk Eval - Depending on the location of the project, type of project, and other variables risk will be drastically different. The level of risk determines the needed competency of project team members and possible need for executive sponsorship. Job readiness meeting - formal evaluation of being ready for a given job (includes evaluation of material requests and lab tests completed up to this point) Execute Job - upload all documentation associated with executing a job: permits, time cards, on-site signed contracts, etc Send project summary to client - a summary of what was done and how long it took - last step before invoicing the client Prepare invoice and close - potentially an integration to some sort of billing system. materials - requesting and shipping materials for a given job examples: cement, water, and most importantly additives. additives include compounds like accelerators (shorten the setting time for cement) and retarders (do the opposite of accelerators. the types and amounts of additives will be different for each project depending on a wide range of variables from well types to environmental conditions the set of additives necessary for a given job is determined by lab testing
- Create Materials Request (desktop) - record set of additives that are necessary for a given job Fulfill Materials Request (iPhone) - Look through the request, identify that the request is complete, scan the shipping container with the bar code scanner, ship Each request can be fulfilled through multiple shipments - this is where the “All Delivered” gateway comes in. if a request is not fulfilled through a given shipment more tasks are generated to complete the request fulfillment
- Create Materials Request (desktop) - record set of additives that are necessary for a given job Fulfill Materials Request (iPhone) - Look through the request, identify that the request is complete, scan the shipping container with the bar code scanner, ship Each request can be fulfilled through multiple shipments - this is where the “All Delivered” gateway comes in. if a request is not fulfilled through a given shipment more tasks are generated to complete the request fulfillment
- Create Materials Request (desktop) - record set of additives that are necessary for a given job Fulfill Materials Request (iPhone) - Look through the request, identify that the request is complete, scan the shipping container with the bar code scanner, ship Each request can be fulfilled through multiple shipments - this is where the “All Delivered” gateway comes in. if a request is not fulfilled through a given shipment more tasks are generated to complete the request fulfillment