NEYNL SAP Network Meeting

1
NEYNL SAP Network Meeting

• Experiences from SAP Implementation in South
  Tyneside
• 26th July 2005

2
Agenda

• Introduction
• Why implement SAP as an early adopter?
• Profile to date
• Lessons learned
• Benefits achieved / prospected
• Plans for further SAP rollout

3
Why implement SAP as an early adopter?

• Easycare already pilotted
• Sap Awareness based upon Easycare tool
• Liquid Logic selected as electronic solution
• Genuine enthusiasm to be involved in NPfIT
• NHS focus local acute trust reluctant to engage
  with SAP
• Excellent partnership working already in
  existence
• Care pathway already identified

4
Profile to date

• Go live on 28/02/2005
• Slow take up of the SAP system during the first
  couple of weeks after go live
• Floorwalking support focused initially on correct
  first logon
• Technical issues to be resolved
• Issued remaining end users with a smartcard
• Current SAP usage 157 registered
• 40 actual
• 450 assessments

5
Profile to date

• Still slow take up in some teams
• Social Care
• Technical issues with Citrix Thin Client PCs
• Mop up training required
• Double entry
• Primary Care
• Mop up training required (SAP is only used when
  referrals are received online
• Health Care Trust - ? Commitment , understanding
  of benefits

6
Lessons Learned (1/3)

• Delay in go live due to
• Criteria for the code of connection could not be
  fulfilled in time within the council. This was
  due to the following issues
• N3 connection was delivered late
• No local experience in the installation and
  configuration of the strong authentication
  software on the firewall
• Delay in end user registration due to the
  following issues
• Engagement of the RA Manager in other
  responsibilities
• Inability or reluctance of some staff to attend
  for registration

7
Lessons Learned (2/3)

• Recommendations to new SAP deployments
• In order to enable the project locations to gain
  a better understanding of the required change, a
  demo system should be used during business change
  meetings.
• The LSP should revise the TTT approach. This
  should include the following
• Use of a training environment for both TTT and
  end user training instead of application
  simulations
• Revise training materials for relevance to the
  end user audience and for reusability during end
  user training
• Provide the LSP training with more local
  background information before the start of TTT

8
Lessons Learned (3/3)

• Recommendations to new SAP deployments
  (continued)
• Council sites are recommended to start the
  necessary actions to obtain code of connect as
  early as possible.
• Project teams should start as soon as possible
  with the definition and the set up of an RA
  organisation to ensure end user registration can
  start early on in the project. This will allow
  sufficient contingency to deal with any technical
  issues to address the unavailability of staff to
  have their registration completed (e.g. due to
  sickness).

9
Benefits achieved / prospected

• Sharing of information
• Information in one place , easy access
• Understanding of roles and responsibilities
• Client becomes the focal point of their
  assessment
• Staff feel more informed of client
• Supportive of team working

10
Plans for further SAP rollout

• 2 rollout stages planned provisionally

2005
2006
May
Jun
Jul
Aug
Oct
Dec
Jan
Sep
Nov
Feb
Mar
Stage 1 147 users Other locations in the STDH, 2
GP practices, East Neighbourhood Services,
Continuing Care Nurse assessors
Upgrade projects to P1R2a and P1R2b
Stage 2 96 users All other Social Care locations