Skip to Content

In the ASUG’s user experience webcast on July 11th, 2018, Cristin Charbonneau, from Canadian Blood Services, presents her success story: “How Fiori designs boost user productivity, improve quality and save lives.”

Cristin began with an overview about the products and services Canadian Blood Services offers, including fresh blood products, plasma protein products, organ and tissue donation and transplantation, stem cell and cord blood, and diagnostic services. She explained some usability challenges she faced with repetitive actions in certain transactions, such as the MIGO transaction, where users needed to enter the same information manually, several times. She also described screen clutter in the SAP GUI that slowed users down with extra tabs and unused information.

 

Cristin’s solution was to simplify the WebGUI screens with SAP Screen Personas, centered on the identifier of a cord blood unit. She provided a more intuitive search feature for users, and eliminated keystrokes and manual entry of data, by passing serial numbers and repetitive data entry with JavaScripting.

 

Cristin used Fiori-like tiles and user experience for consistency. With four portal pages developed for SMEN providing an intuitive experience for each of the user roles (display only view, medical director, general user, and distribution), users can switch to any portal they desire and will receive access to different parts of the transactions.

She shared two examples of simplified transactions including MIGO and QE51N.

 

For the MIGO transaction, scripting was used to pass key, static data to MIGO, eliminating manual entry. This eliminated clicking through three tabs to reveal a custom “user data” tab for cord blood unit receipts. Furthermore, scrapping a final product with its associated components used to take 15-20 minutes and was simplified to mere seconds. The JavaScripting used to search for and automatically populate MIGO screens with components from scrapping also reduced transcription errors. Searching for information was also simplified with the addition of the barcode scanner, instead of having the user write down inspection lot numbers.

 

For the QE51N transaction, Results Recording, Cristin used JavaScripting to pass inspection lot numbers to QE51N from the portal screen, eliminating manual data entry. She also hid toolbars, buttons, headers, tabs and columns that weren’t needed and was able to rename columns as well.

 

Some transactions have multiple flavor iterations to simplify different scenarios.

 

For the Facilities Building Management, SAP Screen Personas was used to combine Plant Maintenance functional locations and equipment with Quality Management inspection process, delivering functionality with the Fiori-inspired portal. The SMEN pages displayed a list of all buildings the user is responsible for as a Facilities Manager or a Facilities Administrator, and provided the ability to record inspection outcomes by eliminating paper-based checklists. This resulted in simplified access to building, equipment and inspection results.

The reporting flavor allowed for ready access to current health of buildings and grounds. This improved efficiency by entering building metadata once and updating it only when required. Finally, using JavaScripting, SAP Screen Personas also provided dynamically built graphical representations of health of buildings and grounds, allowing management to forecast future capital expenditures.

 

Watch the full replay (ASUG membership required).

 

If you are inspired to save a life:

 

The audience had several questions about the SAP Screen Personas deployment:

# Question Answer
1 How long does it typically take to deploy a “standard” Fiori app? About one to two months
2 Is there any barcode scanning to reduce read and transcription errors? Yes! Receiving of the cord, use barcode on label for transactions with MIGO transaction. At end of posting process, idea of unit being generated by system, pop out a label with barcode.
3 Are you retrieving the ECC data through OData services and if yes, did you have to build most? SAP Personas doesn’t use OData.
4 Is it possible to issue cord blood through MIGO to customer partial quantities multiple times? Did you quantify cost or time savings? We automated many of the steps for the process. No cost savings, but time savings for the scrapping process went from 20 minutes down to 30 seconds.
5 How did you involve the end users in designing the screens? Two subject matter experts, one for each manufacturing site and a business analyst for gathering requirements. Cristin stuck to Fiori Style Guide with the screen size being wider than 1200, header and footer, keep icons in same spot, but allow users to tell what fields weren’t being used and to label differently.
6 What training did the end users receive and how did they react? The business analyst gave user training and users picked it up well.
7 How did you and your team become experts in SAP Screen Personas? What training did you take? First Cristin and her colleague went to Dallas and took the Introduction to Development for Screen Personas. There was a lot of self-teaching using the forum to come up with solutions. Finally, they took the openSAP Using Screen Personas for Advanced Scenarios, which was the most helpful.
8 Are you able to change the flavor based on any available data? Yes, they have depending on what information is available.

 

For the SAP Screen Personas team and ASUG UX SIG, Brooke Drury.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply