Azure Qualification

xLM for TestOps - Continuous Qualification for AWS/Azure

xLM for TestOps - Continuous Qualification for AWS/Azure

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.

A Step-by-Step Guide to "continuously" Qualify Microsoft Azure PaaS and Serverless Architectures

A Step-by-Step Guide to "continuously" Qualify Microsoft Azure PaaS and Serverless Architectures

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). 

Continuous Qualification for AWS or Microsoft Azure - How is it done?

Continuous Qualification for AWS or Microsoft Azure - How is it done?

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.