We are redefining validation….continuously!
You can save more than 75% of your cloud app validation spend.
You can compress your validation timelines by more than 50%.
You can stop worrying about the never ending patches and releases. Instead you can enjoy the new features of your favorite cloud app while increasing your productivity.
xLM’s Continuous Validation is a managed service. It is designed to provide end to end validation service for your cloud app like Veeva, TraceLink, ServiceNow, ServiceMax, Jira and many more…
Our managed service is based on our sophisticated technology platform specifically designed for cloud app validation. It is designed to handle all three layers (IaaS, PaaS, SaaS).
Our managed service is built on a robust QMS that is compliant with 21 CFR Part 11, Annex 11, ISO 9001:2015, ASTM E2500.
Cost Effective (over 75%)
Timeline Compression (over 50%)
Low Ongoing Costs
Reduces Compliance Risk
Increases Test Coverage
Increases Data Integrity Assurance
Full Coverage for Patches & Updates
Full Coverage for all Layers - IaaS, PaaS, SaaS
Complies with 21 CFR Part 11 / Annex 11
Built-in Robust Testing Strategies
Integrated Risk and Traceability
Built-in Support for Historical Test Data Analysis
Adaptive Framework designed to accommodate frequent requirement changes.
Life science companies that use cloud apps (SaaS) in their GxP operations. Such cloud apps include Veeva, TraceLink, ServiceNow, Jira, ServiceMax, CloudByz, AO Docs and many more..
Life science companies that use IaaS/PaaS - AWS, Microsoft Azure, Google Cloud.
Life science companies that use the DevOps model.
Many life-science companies are asking the question “Can I move my GxP workloads into the public cloud?” Answering “yes” to this question leads to another question: “What toolset do I need to qualify the various IaaS/PaaS services that are constantly changing?”.
Our customers are leveraging our robust framework that we call TestOps. TestOps provides an end to end automation for continuously qualifying any IaaS/PaaS service running on AWS or Azure.
The main objective of this post to answer the following questions. I know a picture is worth a thousand words and so I will do this with illustrations.
Can "Validation" and "DevOps" be used in the same sentence (like vCD - Validated Continuous Delivery)?
Is DevOps a viable model for validated apps in GxP Environments?
How can one ensure the "validation fidelity" in a DevOps environment?
What are the key steps involved in continuously validating a ServiceNow App?
One has to bear in mind that the underlying IaaS and PaaS infrastructure is constantly changing. In fact, the Cloud App itself is continuously changing. In the new cloud world, it does not make any value-sense to pin to an "ancient" version. Thus this Continuous Validation Framework is designed to mitigate these risks and ensure that your ServiceNow app is maintained in a validated state.
I very frequently get asked whether Azure Platform-as-a Service (PaaS which includes Serverless Architectures) can be qualified as well? Surprisingly, this question is asked even by Azure users who agree that Azure IaaS can be qualified. In this blog post I will provide a prescriptive guide to intelligently qualify Azure PaaS and maintain it in a qualified state (QS).
The million dollar question is "Can Microsoft Azure be qualified?". In this blog post I will provide a prescriptive guide on not just "how to qualify", but also how to maintain the qualified state intelligently.
The million dollar question is "Can AWS be qualified?". In this blog post I will provide a prescriptive guide on not just "how to qualify", but also how to maintain the qualified state intelligently.
FDA put out its DRAFT guidance on Data Integrity and Compliance with cGMP in April 2016. This guidance is important because we come to understand FDA's thinking on Data Integrity.
Any Track and Trace Enterprise application is a complex implementation which has many interfaces. What are the requirements of a validation toolset for such an application? Let us take a look..
The question is "Can Amazon AWS or Microsoft Azure be qualified so that I Life Science companies can run validated apps on it?"
Cloud releases updates and changes at such great velocities that leaves all validation specialists continuously wondering on how to qualify it. Traditional strategies including GAMP 5 was never designed to address continuous changes. These models were designed for a "waterfall" world and not an "agile" one. It is not possible to qualify an infrastructure where changes are released without release notes with such an outdated mindset and toolset.
This blog post is Part 3 in this series. What are the key process steps involved in continuously validating a Cloud App?
This blog post is Part 2 in this series. What are the key steps involved in continuously validating a Cloud App? (click here for Part 1).
The above diagram depicts the key elements of a Continuous Validation Program for a Cloud App. One has to bear in mind that the underlying IaaS and PaaS infrastructure is constantly changing. In fact, the Cloud App itself is continuously changing. In the new cloud world very rarely you are given the option of pinning to an "ancient" version. Thus this Continuous Validation Framework is designed to mitigate these risks and ensure that your cloud app is maintained in a validated state.
What do you need to implement a true continuous validation platform for a Cloud App? This series of blog posts will answer this question. This blog post is Part 1 in the series and covers the infrastructure required to implement this platform.
Not a day goes by without a client posing this question: Can Amazon AWS or Microsoft Azure be qualified so that I can run my apps on it? Here is a 9 Step systematic answer to this very popular question....
ATLANTA — October 2, 2019 — AODocs, the only business process platform tightly integrated with Google Drive, releases AODocs for Life Sciences, a modern, intelligent Quality Management System (QMS) to address FDA and GxP compliance in Life Sciences organizations.