Learn how you can achieve full GxP compliance when moving to SAP S/4HANA in the AWS Cloud. In the session, you’ll hear learnings and best practices for securing FDA approval in order to fully reap the benefits of cloud transformation.
Good afternoon everyone.
I want to thank our hosts AWS for their willingness to have us speak about achieving GxP Compliance when implementing S/4HANA solutions on AWS.
My name is Remon Hogguer, I work for Capgemini within SAP Life Sciences and am here with my colleague Jason Hatch who is part of our Cloud Hosting Team
During this session we want to give you an update on how we deliver S/4HANA in a validated environment leveraging AWS.
We will show you who we are approaching these life sciences projects using an accelerated pre-packaged solution with an integrated validation approach
We will review a recent life sciences client implementation use case where we have implemented S4H 1610 on AWS in a validated environment
We will discuss our relationship with AWS and our joint capabilities
I will start with explaining Capgemini's evolution of dealing with LS customers. Going back 12 years or so <NEXT SLIDE>
We started looking at some of the key things that are really prevalent across life sciences industry comprising of Biotech, Pharmaceuticals and Med Devices.
One thing we saw is LS will continue to be subjected to continual change. The industry pace the pace of change is high and it will not slow down.
Challenges: like GxP, batch tracking, serialization, UDI, CAPA, new biz models (no cure no pay), pressure on price (e.g. medication)
So how do we address these challenges for all LS customers implementations, multiple towers that were to be addressed:
Need establish and implement a robust digital ERP core
How? Using LSPath, a pre-packaged, SAP certified, solutions that has documentation content (test scripts, process flows, etc.)
We use a design by acception approach to implement fast (why wont it work?)
Need to embed validation as part of delivering the programs and we incorporated those in our LSPath footprint
How? By deliberately acquiring a validation company. Then by integrating validation approach and template deliverables into our project methodology and approach.
The effort of integrating document management requirements to ensure product quality, patient safety, and data integrity into the program approach is something which is challenging
Need to be able to deploy these systems at predictably cost (lower), reducing the risk to the business, and with more predictable outcomes
Need to be able to support these solutions post go-live
On the next slide you see how we see how we currently position our LSPath solution.
You have probably see a version of this Intelligent Enterprise before and.
Accelarate: Our goal is to have LSPath be the accelerator to the LS Intelligent Enterprise
Reduce business risk: It should reduce implementation risk with pre-delivered content,
More predictable outcomes / lower cost to implement
On the next slide we’ll be discussing our GAMP 5 validation method for CFR – 21, part 11, it is a set of documentation management requirements to ensure patient safety, product quality and data integrity in manufacturing.
Gamp 5 Good Automated Manufacturing Practice, refers to a set of industry best practices for automated systems.
Essence is risk based CSV; the higher the risk, the greater the degree of validation and control is needed
We begin each project with the assessment of the system requirements to determine its risk level (based on system type and intended use).
For systems that fall under the CFR-21, part 11 policy, we:
Include requirements that correspond to the regulations that are in scope (these requirements are spelled out in our QA-controlled CFR-21, part 11 policy)
List regulations that do / do not apply to the system in the scope section of the requirement specifications.
Test those requirements including all others during OQ and PQ testing phases.
Test installation / technical requirements within IQ testing AWS
Gathering requirements – our LSPath solution comes with ~2,000 requirements out of the box.
Gamp 5 essentially is a validation method for CFR - 21, it is a set of documentation management requirements to ensure patient safety, product quality and data integrity in manufacturing.
On the next slide I want to walk you thru the Cantel Medical use case a client that went live with S4H 1610 early Feb 2019 on AWS
Point to Highlight
LSPath
Scope: manufacturing, finance, service, procurement, warehousing, order management, distribution and quality
Validation Services
Hosting on AWS
AMS
I will give the word to Jason who can tell us more around our AWS relationship and capabilities next.