LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestras Condiciones de uso y nuestra Política de privacidad para más información.
LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestra Política de privacidad y nuestras Condiciones de uso para más información.
These screencams were just here in case the WiFi didn’t hold up and I couldn’t do that demo live! However, there’s one here I’d like to show you anyway. Remember the service order display screen, this one – type in the order number, hit display and you get this. The information on this screen actually comes from several different places. This video shows the IW33 transaction in SAPgui, and how you need to drive it to get to everything shown in this one screen.
I mentioned earlier that we were looking for all of these things from Personas, and in this project we found all of them. Compared to developing something similar in, say, WebDynpro, Personas development was much quicker, because you are building on top of existing already working SAPgui transactions. And for the same reason, testing is quicker and easier. We built a training course to cover the necessary Estates functionality in standard SAP and it ran for 2 hours, and almost certainly many users would need to sit it twice! The Personas version runs for just one hour, and could actually be shorter still. By half way through, the users are already exploring the system on their own. And these are generally users who have no previous experience of SAP at all. Even some of our long-standing intensive SAPgui users, people very confortable with using SAP, choose to use this interface sometimes because it is simply quicker for them.
During the process of building all of this, I ended up pushing the product rather further than it was originally designed for, and as a result SAP asked me if I would be interested in being involved in the process of building the next version. They were looking for somebody who would be able to properly stress test the product before it was released, and to provide feedback on product capabilities. Naturally I said yes! I’m going to hand over to Sebastian now, to talk about the co-innovation process, the new version of Peronas and give you a demo.
Old architecture: silverlight client, two channels to the backend
Screen shot of Personas 3.0
This approach allowed to focus on the themes of this release: Tighter integration with Web GUI (SAP GUI for HTML) More powerful scripting Improved performance Further usability improvements Advanced properties easier to access Integration with SAP roles, security
Show all the cool stuff U of W scenario User view: flavor changing Building screens Scripting Flavor maintenance
SAP Imagineering, working with customers, co-innovation
In summary, then...
When we decided to go with Personas we were looking for a way to improve our user’s experience of SAP without needing a huge investment in infrastructure or expertise. I believe we found that. My experience is that the development process with Personas is much shorter than building similar things with other technologies. Most of the time in a Personas project is spent in the design process, and especially involving users in that process. And if you do that well, you end up with something the users really like. Certainly our users are much happier using the Estates dashboard I’ve shown you than they were using standard SAPgui transactions.
The new version has much more powerful scripting and automation features that should make it possible to build even more streamlined processes. I’m looking forward to seeing what I can do with it!
Thank you for listening. Are there any more questions?
One final thing – please fill in the feedback survey on the mobile app.
University of Warwick Personas Co-Innovation Project
Orange County Convention Center
Orlando, Florida | June 3-5, 2014
SAP Screen Personas Co-Innovation Project
Steve Rumsby (University of Warwick)
Sebastian Steinhauer (SAP)
This presentation contains information about an unreleased version of software.
This document, or any related presentation and SAP's strategy and possible future
developments, products and or platforms directions and functionality are all subject to change
and may be changed by SAP at any time for any reason without notice.
The information in this document is not a commitment, promise or legal obligation to deliver
any material, code or functionality.
University of Warwick
Founded in 1965
Financials (FI, CO, MM, SD, PS) live on R/3 4.0B in 1999
Service Management live in 2000
Upgrade to 4.7 in 2004
Upgrade to ERP6 EHP5 in 2013
Upgrade to ERP6 EHP7 in 2014
SAP Usage & History
SAP Screen Personas
Improving User Experience
Planned orders 9k
Reactive orders 40k
Campus area 700
Personas Project – Estates
Amount of training required
Number of process steps
Number of Clicks
Number of Screens
Cost codes Purchase orders
Helpdesk Service order
Reduced development time
Perfect for design thinking/agile techniques
User involvement is critical
Reduced testing time
Underlying SAPgui transactions have to be tested anyway
Very little extra Personas testing needed
Reduced training time
Training course for estates reduced in length by 50%
Increased user satisfaction
“It’s been my first time seeing or using SAP and I found it very
easy and straightforward.”
“This is so easy. Is it even possible to make a mistake?”
Build on proven components
Tight integration into core SAP components
Rendering using the SAP GUI for HTML
Separation of concerns – Simple and Powerful
Theming – create once, use everywhere
Scripting – powerful scripting API
Editing – individual changes per screen
Personas 3.0 – The next Generation
SAP Imagineering works with SAP customers to explore
disruptive technologies, business models, and market
opportunities across different topics as well as new markets
that SAP may serve in the future.
Productivity through Personalization
Simplify for individuals and improve overall productivity
Build on existing investments
Use existing GUI transactions
Improve situation instead of replacing
Co-innovation leads to successful innovation
Customers know best what they need
Help, listen, share
Using Personas for personalization results in
reduced testing, development and training time
Personalization leads to increased user satisfaction
The new version of Personas is tighter integrated
into core SAP components and provides much more
powerful scripting and personalization capabilities
THANK YOU FOR PARTICIPATING
Please provide feedback on this session by completing
a short survey via the event mobile application.
SESSION CODE: 0703
For ongoing education on this area of focus,