How varian medical_customized_sap_screens_in_hours

May 14, 2012

[ Learn how Varian Medical customized
SAP screens in hours, not months
Jason Jester (Varian), Sebastian Steinhauer (SAP)

[ Learning Points
 Learn how to significantly reduce the time to
personalize SAP screens
 Discover how to improve end-user satisfaction
and enhance their productivity
 See why this solution is so easy to use and
requires no knowledge of back-end systems

Real Experience. Real Advantage. 2

[ Jason Jester

 Jason is an IT manager at Varian Medical Systems. He
manages a global SAP team that supports the SD, VC,
PS, and GTS modules. Jason is a SAP Certified
consultant with 13 years of SAP experience in the area of
ABAP Development, Variant Configuration, Sales &
Distribution, Project System, and Global Trade Services,
along with 10+ years of experience in the high tech and
medical device industry.


[ Sebastian Steinhauer

 Sebastian manages a development team in SAP’s
Imagineering group. He has been at SAP for 5 years,
focused on development efforts that help SAP customers
solve problems that span disparate solution areas. He has
been in the software industry for 10 years.


[ Varian Medical Systems has a global presence

 Over 5,500
employees
 Market Cap: $7.51B
 Revenue: $2.6B


[ Our goal is to save 100,000 more lives each year

 To explore and develop
radiation technology that
protects and saves lives
 Our goal is to save 100,000
more lives each year
 We equip the world with new
tools for fighting cancer, taking
X-ray images, and protecting
our borders


[ We treat cancer patients with advanced radiation
therapy
 World's leading manufacturer of medical devices and software for
treating cancer with radiation therapy
 More than 6,000 of Varian's medical linear accelerators for cancer
radiotherapy are in service around the world, treating tens of
thousands of patients per day


[ Long-term and evolving SAP landscape
 SAP R/3 first implementation in 1994 at version 2.1
 ECC 6.0 Re-Implementation Go-Live: Jan 2009
 Expanded Footprint
 BI – Business Intelligence
 GTS – Global Trade Services
 CRM – Customer Relationship Management
 HR – Human Resources
 MES – Manufacturing Execution System
 PLM – REACH/RoHS
 PLM – Electronic CAD Integration


[ Business challenges: integrating and automating
processes


[ GUI personalization at Varian Medical Systems
Why was it important for Varian to customize the
GUI?
 Reduce complexity and confusion with some SAP
transactions
 Set default values and then hide the fields for fields with static
values
 Hide fields which are never used
 Organize fields in a manner which better supports some of our
business processes
 Increase end-user efficiency by making information more
accessible
 Quick “Filters” with some standard transactions
 Quick Excel exports
 Ability to create a “cockpit” or “quick launch” buttons to allow users
to more easily follow standard business processes

[ Planned use cases for Personas
1. Map business processes to transactions to create
business process “cockpits”
2. Map users/roles to specific “flavors” to help streamline
their work
3. Simplify SAP screen design
4. Increase productivity with filters and other user tools


[ Customization process at Varian Medical Systems
Software Systems Drag &
Development Analyst Drop
Skills Skills Simplicity
Level of Customization

Edit
Transactions,
Workflows

Build Forms,
Merge
Transactions “Personas”

Modify UI

Months Weeks Days Hours

Time to Deploy


[ Personas co-development timeline
May SAPPHIRE NOW proof-of-concept
2011
Aug 2011 Imagineering fellowship start

Oct 2011 First demo – development snapshot

Dec 2011 Initial deployment

Jan 2012 Scripting, filtering, conditional
formatting
Mar 2012 NWBC integration


[ Personas value spans IT and the business
 helps IT Managers
reduce the time to modify SAP screens,
increase business user efficiency,
improve business user satisfaction, and
centralize administration of screen changes
 helps Business Users
create a modern, aesthetically pleasing UI to
access the right information for their job,
personalize screens to fit their working style, and
reduce the cost of personalizing the user
experience


[ Demo


[ Architecture
Server “Cloud”
Client
(ON PREMISE) (ON DEMAND)

Browser “RIVER”

http

SAP Web GUI
(dynpro)

ITS

SAP
http SAP Personas
Netweaver SAP Personas
ABAP Personalization
(dynpro)
http Data
(REST)

SAP GUI
(dynpro)
DIAG


[ How to roll it out
 Kernel upgrade
 Start with a single transaction and a small user group
 Groom the transaction and identify key users
 Allow key users to create a “flavor”
 Provide a direct link for the transaction
 Integrate direct link in your communication or NWBC
 Unlock it as SAPGUI alternative
 Monitor user behavior in the system and focus on most
used transactions first
 Groom transaction flavors and allow key users to
personalize
 Gradually unlock edit mode
 Constantly monitor flavors and user flows

[ Analytics and administration


[ Use cases – data entry


[ Use cases – data lookup


[ Use cases – “lean ERP”


[ Benefits to IT

Reduced time-to-deploy
• Lower cost from less complexity and no
need for programming
Improved business user satisfaction
• Personalized screens to maximize
productivity with minimal visual clutter
Centralized administration
• Profiles for users and groups
• Control over all changes with ability to
roll-back

22

Real Experience. Real Advantage.

[ Benefits to business users

Personalized screens
• No technical skills required
• Less IT involvement means faster screen
modification
Improved productivity
• Focus on only the information you need
with minimal visual clutter
• Do your job better, faster, with fewer

$ errors
Lower cost of personalization
• No need for expensive development
resources

[ Benefits to Varian
 Collaboration  Influence Product
Varian was able to Features
work with a very Varian was able to
senior team of SAP suggest key features
Product Developers to make the GUI more
“usable” for the end-
user
Many of these
recommendations
made it into the
product


[ Deployment – What went right?
Co-Innovation Process:
1. Short Development Lifecycle for incorporating requested
features
2. Cloud deployment model made it easy to install and did
not require anything else to re-install for v2.0
3. The team was able for focus on key improvement to the
most challenging transactions
4. Project Scope expanded from only GUI display changes
to include End-User productivity enhancements


[ Lessons learned
 SAP wants to hear your feedback – and they will listen to
it
 Have the right expectations for early-stage co-innovation
 There will be bugs, but SAP will fix them quickly
 Functionality will be incomplete at first, but rapidly evolve
 Involve a variety of roles in the process
 Different groups have different needs (IT vs. business
users)
 Discussions help prioritize needs vs. wants
 Add the context to your feature requests
 Knowing why you need it helps the design process


[ Summary
 Personas helps both IT and end-users personalize
screens
 Role-based approach optimizes individual productivity
 Cloud-based deployment model assures current version


[ Where to learn more

 SAP Community Network (www.sdn.sap.com)

Sebastian Peter Spielvogel
Steinhauer Product Marketing
Product Owner


[
 Thank you for participating.
Please remember to complete and return your
evaluation form following this session.
For ongoing education on this area of focus, visit the
Year-Round Community page at www.asug.com/yrc
]
[ SESSION CODE:
0901


How varian medical_customized_sap_screens_in_hours

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to How varian medical_customized_sap_screens_in_hours

Similar to How varian medical_customized_sap_screens_in_hours (20)

More from Peter Spielvogel

More from Peter Spielvogel (20)

Recently uploaded

Recently uploaded (20)

How varian medical_customized_sap_screens_in_hours