The document outlines lessons learned from implementing Hill-Rom's Oracle-based ELM system, emphasizing the importance of specialized knowledge and careful planning to ensure a smooth integration. Key considerations include simplifying the system structure, managing data conversion efficiently, and establishing effective training strategies to minimize disruption. Recommendations also stress limiting customizations and ensuring robust post-implementation support to enhance long-term success.

1. Lessons Learned in Kenneth Petty
Implementing Hill-Rom, Senior Project Manager
&
PeopleSoft ELM 9.0 Chris Kirsanoff
Oracle Consulting, Solution
Director

2. Oracle Safe Harbor
The following is intended to outline our general product
direction. It is intended for information purposes only, and
may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing
decision. The development, release, and timing of any
features or functionality described for oracle's products
remains at the sole discretion of oracle.

3. Hill-Rom
Leading worldwide manufacturer/provider
of medical technologies and services
• Patient support systems
• Safe mobility and handling solutions
• Non-invasive therapeutic products
• Medical equipment rentals
• Information technology solutions
Mission
Every day, around the world, we enhance
outcomes for patients and their caregivers
www.hill-rom.com

4. Hill-Rom Products & Services
Patient Support Systems Health Information Technology
Frames & Therapeutic
NaviCare ® Patient Nurse Alerts and
Integrated Surfaces Surfaces and
Safety Suite Communication
Support Systems
Patient Environment Medical Equipment
Therapy Delivery
AP & Furniture Management Services
Surgical Respiratory
Support Systems Care

5. Agenda
• Why is ELM different
• DIY or Hire an Implementation Partner
• Key Design Considerations
• Data Conversion
• Integration
• Testing
• Training

6. Why is ELM different?
• Scope of users
o Everyone in the company uses it
o Vast continuum of technical savvy among users
o Intermittent use by user community
• Specialized terminology for ELM
o Programs, Catalog Items, Activities, etc.
• Understanding of the specialized technologies
o AICC, SCORM, Integration Broker
• “Training shouldn’t be required for a training
system!”

7. DIY or Hire a Partner
• Specialized Knowledge Required
o You must have specialized experience in order to be
successful or you will pay more in the long run.
How to install
Highly configurable – need expertise in translating
your needs and process into the system
AICC and SCORM troubleshooting
Integration Broker
o Not every “PeopleSoft person” knows what you need to
know to set up ELM
o Look for people familiar with your release of ELM

8. DIY or Hire a Partner – Lessons Learned
• We hired a partner to assist.
o Make sure they have done ELM Implementations in the
version you are installing – not just the partner but the
individuals you will be employing.
• Don’t short-change post go-live support
o Have a SME stay on to assist in troubleshooting. Need
experience in troubleshooting AICC and SCORM
eLearning content, and handling general system
operations. Valuable time to train you.

9. Key ELM Implementation Decisions
• Learning Environments (how will the system be administered?)
• Learner Groups (how will learners access content?)
• Internal Learners and External Learners
• Catalog Structure (how will you define courses, classes, programs, etc.?)
• Reporting
• Security
• Data Conversion
• Business Processes
• Customizations

10. Key ELM Implementation Decisions –
Lessons Learned
• Keep it simple!
o We went with a single learning environment for all 23
countries and all employees and contractors
o One learning environment for all external learners.
o Catalog needs to be rationalized and strive to keep it as
flat as possible. Time invested here pays big dividends.
o We did not implement supplemental learning to start
o We have it as an intranet-accessible only application
o We allow browsing of the catalog, self-assignment, and
do not use manager approvals

11. Key ELM Implementation Decisions –
Lessons Learned
• If you suspect you will use Asian languages have the
database built using UTF8 instead of ASCII. The
“Standard” install is for English and using ASCII
code set.
• Limit the number of languages you install based
upon those you need and will have content/users for.
o The Verity index builds a separate index file for each
language installed and if you install 8 languages it will take
8x as long to build as if you installed only one.
o The multiple languages implementation requires you install
patches and bundles made for multiple languages and
increases the testing permutations.

12. Key ELM Implementation Decisions –
Lessons Learned
• Limit customizations.
o With few exceptions the issues that have arisen have been in
our customizations.
o The benefits must be weighed against the costs in time and
money, not just for the initial set-up but for years of on-going
support.
• We have external learners and internal learners
o Internal learners are all employees and contractors
These are in our HRMS system
o External learners are people who take training on our
products at our training facilities
These are not in our HRMS system

13. ELM Data Conversion
• Conversion Strategy
o How will converted data be used?
o “Live” catalog data or Supplemental learning?
o Specific content or users?
o Specific dates?
• What Data?
o Learning Catalog (Courses, Classes, Instructors, etc.)
o Learners/Transcripts
o Supplemental Learning
o Compliant Content (AICC/SCORM) structure files

14. ELM Data Conversion – Lessons Learned
• Data Conversion?
o We had to do it. We are regulated by the FDA and
information on our employees training must be maintained in
detail.
o Don’t do it if you can avoid it as will take much longer than
you will plan. (2-3x as long is our experience)
o Your data is not as clean as you think and when you
undertake this you will find out
o Recommend using ETL Staging Tables Run in through
Component Interface (CI) method.
o Do many test runs and take several days or even weeks to
use the application with the converted data fully to uncover
issues.

15. ELM Data Conversion – Lessons Learned
• Data Conversion?
o Converted all our eLearning content (302 AICC
courses, we had no SCORM content at the time) and
needed to test all of them in the new environment to be
certain they worked. The process was straightforward
and only 37 needed troubleshooting. The testing took
quite awhile.
o Brought over entire Learning Catalog
Learners
Programs
Catalog Items
Activities
Transcripts/Rosters

16. ELM Integration
Human
Resources
Person/Org Data
Competencies
AICC/SCORM
ELM Integration Layer
Content Vendors
Integration Broker
Financials
LDAP / SSO
ChartFields PeopleSoft Enterprise
Learning Management
Chargebacks e-Mail Server
Webcast
Calendar
Credit Card

17. Common ELM Integrations
• HRMS • AICC/SCORM Content
o Person/Org Data • Webcast System
o Competencies
• LCMS
• Sources of
External Learners • Credit Card
Authorization
• Financials
• LDAP
• Portal
• Single Sign-On

18. ELM Integrations Methods
• Batch / Flat-File
• Enterprise Integration Points
• Component Interface
• Web Services / XML

19. ELM Integration – Lessons Learned
• LDAP Integration
o Straightforward and WELL worth the work.
o Easiest if all network IDs are similar format and all ELM
users log in to their computers.
o 400% drop in calls for password resets once
implemented.
• Interface to HRMS
o We have integrated to PeopleSoft HCM 9.1 and it
provisions new learners and updates learner status
using Web Services
o Also had it integrated to JDE-HR prior to PeopleSoft
using automated FTP and Batch processing.

20. ELM Testing – Lessons Learned
• Plan Lots of Time
o At least three Test-Fix-Test Cycles as a minimum
o Test Converted Data as “early” as possible and as often
as possible – more is better.
o Build Test Data – a lot of test data
o Need time for full process to happen to test all
system events (assign training – let time pass –
complete some and not others – drop and add – then
let it expire and check rosters, reports, All Learning
page for the various learners and various statuses)

21. ELM Testing – Lessons Learned
• Plan Lots of Time
o Spend lots of time on reports that will be used for
compliance or employee performance.
o Don’t rush it! Bugs found once you go live will be
remembered for years to come.
o A brilliant success is for people to say nothing.

22. ELM Training – Lessons Learned
• We developed eLearning in six languages and
rolled out to the company two weeks before the
system went live
• Plan on lots of questions
• Communicate that a change is coming
o Give value proposition and “What is in it for me?”
o Make clear the path you want them to follow
o Use as many channels as possible
E-mail newsletters, posters, lunch-n-learns, etc.

23. ELM Training – Lessons Learned
• Enlist the learner as an ally-ask them to help
you.
• Remember-this is not their “real job” they want
as little training as possible in the fastest fashion
possible
o Be brief – be brilliant – be gone
• Learners don’t want a training system that
requires lots of training to use.

25. Please provide feedback on this
session by completing an
online evaluation.
Go to
http://ohug.ezsession.com
and enter Abstract ID 247932 .