Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: @CloudExpo, Java IoT, Microservices Expo, Containers Expo Blog, Agile Computing, @DXWorldExpo

@CloudExpo: Article

Cloud Platforms: The Crucial Foundation | @CloudExpo #IoT #Microservices

How a cloud environment can offer the flexible resources, elastic scalability and system reliability

Cloud Platforms: The Crucial Foundation to Safeguard the Pharmaceutical Supply Chain

In today's pharmaceutical supply chain, counterfeit activity is thriving. As pharma companies have expanded target markets and outsourced production over the last decade, the supply chain has become increasingly global, virtual, and vulnerable. Illicit activity has thrived, and patients have suffered, with hundreds of thousands dying each year from counterfeit and contaminated drugs.

More than 40 countries have responded with new laws that regulate prescription medications as they travel through the supply chain. While this is a quantum leap forward for patient health, the implications for supply chain stakeholders, from pharmaceutical companies and their contract manufacturing partners to the pharmacies that serve patients are daunting: they must master each country's disparate track and trace requirements; create a system architecture capable of generating, managing, and storing what will be unprecedented volumes of regulated data; and figure out how to efficiently exchange that data with hundreds to tens of thousands of direct and indirect supply chain partners.

In the process, traditional technology will be put to the test. Traditional, on-premises data center and enterprise software infrastructure will prove incapable of meeting the enormous data management and transactional processing demands that compliance will introduce. Cloud computing networks offer the only practical solution for this challenge.

This article will discuss the how a cloud environment can offer the flexible resources, elastic scalability and system reliability required to meet compliance regulations and patient safety protections necessitating the tracking and tracing of medications through every step of the supply chain.

From Local to Global: Increasingly Virtual and Vulnerable
Emerging market demand for medicines has skyrocketed in the past decade and a better understanding of patient health has driven a parallel growth of increasingly specialized medicines. In response, the pharmaceutical supply chain has shifted from predominantly a local presence, with local pharmaceutical companies producing medicines for the local market, to a truly global supply network linking diverse members across multiple continents to serving global patient populations. On this global network now flows an increasingly broad range of medicines, driving pharmaceutical companies to virtualize many operations and establish complex new supply relationships in order to reach and serve a global, increasingly diverse market.

Many have built relationships with local contract manufacturers, pharmaceutical companies and third-party logistical organizations for production and distribution efficiencies. These partnerships have allowed them to decrease fixed costs, improve agility and enhance access to the global market by cost-effectively producing and distributing product around the world. This growth creates vulnerability as a longer supply chain with more changes of possession and ownership from drug manufacturing to patient dispensation creates more opportunity for counterfeiting and diversion.

The true scope of counterfeiting - which encompasses everything from inactive or incorrect ingredients to drugs with high levels of contaminants or fake packaging - is unknown, but the World Health Organization (WHO) estimates that between 1% and 10% of drugs sold around the world are impacted, and the overall worldwide sale of counterfeit drugs is valued at more than $75 billion a year. The cost to patient safety: immense.

The Response: Track and Trace Regulation
In response to increasing drug integrity concerns, more than 40 countries from the U.S., China, India, South Korea, Brazil and the members states of the European Union have introduced track and trace laws to identify, track, and verify product as it passes through the supply chain. By 2019, more than 75% of the world's prescription medications will be protected by legislation. From a patient health perspective, this is unequivocally good news.

For the industry, however, these diverse regulations introduce a web of challenges. While most regulations involve some combination of generating and managing serial numbers for each unit of drug product, tracking product through the supply chain, verifying data and transactions at various points in the network, and reporting associated events to government authorities, no two countries in the world have passed the same requirements or mandated the same information formats. This is particularly problematic when you consider that globally tens of billion units of drug product are produced and distributed annually across a global supply network made up of well over one million members.

Global Track and Trace Breaks Traditional Enterprise Approaches
Track and trace compliance demands test - and surpass - the limits of what traditional technology and enterprise infrastructures can manage in two key areas: big data management, and trading partner integrations. Let's look at what a mid-sized pharmaceutical company serving the United States market may face under the Drug Supply Chain Security Act (DSCSA). Our model company may produce 50 million units of drug product annually for the U.S. market. All 50 million units need unique serial numbers generated along with the 1 million cases that they are packed in. Each serialized unit will generate an average of 5 serialized events needing to be managed, resulting in 255 million serialization transaction events and more than 255 gigabytes of compliance data at 1 kilobyte per event annually. Across a 10 year record retention period, the company would be faced with securely managing over 2.5 billion compliance events and over 2.5 terabytes of compliance data.

The network challenges are just as daunting. A mid-sized company may use a dozen or more contract partners to augment internal sites to produce their serialized products for different markets. All of these sites and their different serialization line management systems need to be integrated with across multiple transactions. Even more difficult are the downstream network connection challenges. Dozens to hundreds of direct trading partners, including wholesale distributors, repackagers and dispensers need to be connected for lot-level traceability and serialized product data exchange as products are sold, distributed, returned and verified during investigations. Add in the requirement to receive and respond to serialized product verification requests from thousands of indirect trading partners such as independent pharmacies and the pharmaceutical manufacturer faces an unprecedented challenge. This intricate, highly connected serialized supply network will now need high performance electronic connections over which millions of transactions and gigabytes of compliance data will flow.

The U. S. DSCSA example is just one of the many scenarios facing multi-national pharmaceutical companies. All in all, an in-house infrastructure to support this network ecosystem would be prohibitively expensive and complicated from a capital, personnel, and expertise perspective. Because of the dynamic nature of global track and trace regulations, companies making large capital investments in their physical IT infrastructure also take on unacceptable risks as regulatory environments and their related data management requirements may change on a yearly or even quarterly basis.  Given the volume and complexity of required partner connections, an individual, point-to-point approach built upon traditional enterprise infrastructures using standard SQL database is just not feasible. This is why Life Sciences must look to the cloud for a solution.

Network-based Cloud Platforms Are the Only Way to Meet Emerging Needs
In order to succeed in the new global, virtual, and regulated landscape, the Life Sciences supply chain needs a new data exchange model and supporting platform that can scale to manage trillions of objects and transactions, and handle seamless exchange of this data amongst global supply chain partners that number over a million worldwide. Plus, as personalized medicine, patient regimen compliance and other patient engagement programs are developed across the industry, this platform will need to connect to the billions of patients globally receiving medicines. The industry needs a platform that can facilitate communications, generate efficiencies, guarantee compliance and protect information - and do all of that in a cost-effective manner.

Cloud computing infrastructures such as Amazon's AWS Cloud, utilizing global, on-demand data and transaction processing resources, ticks all of the requisite boxes. Yet, cloud environments come in several different flavors, so it's important to understand which design and configurations will meet emerging challenges facing the industry.

Public vs. Private
A private cloud - dedicated to only your company - offers limited elasticity within your private data center, while a public cloud is a true utility computing model. For the reasons of scalability, along with solid disaster recovery and security, a public cloud model makes the most sense to support the pharmaceutical supply chain.

Single, Multi-, and Network-Tenant Environments
In the new pharmaceutical regulatory environment, understanding the attributes of single-, multi-, and network-tenant clouds is critical to a company's ability to exchange required data with their full complement of internal sites, supply and trading partners. The goal is to find the right infrastructure that supports the necessary data, transactional and connectivity requirements.

A single-tenant architecture is a legacy approach that creates a separate software instance and supporting infrastructure for each customer and their data. This type of architecture will not support sharing compliance data with many partners or evolving regulations which necessitate regular updates.

In a multi-tenant setup, a single instance of software and the infrastructure serves multiple parties. Multi-tenancy is a step forward from single tenancy, but it does not explicitly facilitate connectivity and communication between companies.

Network-Tenancy for Mission-Critical Life Sciences
Network tenancy is a whole new dimension that builds on multi-tenancy, but was expressly created to meet the challenges of today's Life Sciences companies.

The fundamental purpose of a network-tenant environment is to enable interactions and share business processes across multiple companies on the network, establishing a new dimension of collaboration with existing partners and allowing for discoverability of new partners within a directory structure.

In a network-tenant solution, interactions with other companies are a paved road and a singular process: you integrate into the network once, and can then interact with everyone. Network tenancy also provides data translation and transportation, enabling seamless information exchange in a regulatory world with incomplete standards and diverse corporate data preferences. Think of it like the Interstate highway or the electrical grid ensuring free flow across the network while enabling diverse entities to join.

Service providers distribute software updates to all network residents simultaneously, insuring that all companies remain in compliance as regulations continue to evolve. Network tenancy builds on the security protocols of multi-tenancy, protecting data and the private network interactions while enhancing interoperability and business growth by adding new forms of public discovery and inquiry across the network similar to those seen in consumer networks like LinkedIn. Well-defined network tenant platforms add additional layers of security by invoking a rigorous process of vetting new members prior to adding them to the network.

Specifically for Life Sciences, network tenant platforms must go one step further. The systems deployed must be designed to meet regulatory requirements in areas like validation while ensuring overall system integrity and reliability as critical medicines are produced and distributed. The platform and the processes used to build solutions on the platform must minimize and isolate change that impact validated systems while providing detailed IQ and OQ artifacts to support validation testing on new platform releases. In addition, inherent fail-over and redundancy must be designed in from the start for both data management and transaction processing.

Done right, network tenancy enables residents to share compliance-related business processes with diverse global supply and trading partners; seamlessly exchange data in a world without format standards; accommodate the massive scale demands of global serialization; and grow their businesses by supporting global supply relationships and discovery of new prospective partners. It also lays the foundation for new business value as any one network member now has global connection and reach to leverage for new forms of supply planning and patient engagement. It is the only solution that can accommodate the evolving needs of the fast growing Life Sciences supply chain.

Choosing the Right Solution for Success
By 2017, the global prescription drug market is projected to grow to $1.2 trillion, up from $900 billion in 2014. Counterfeit activities are also poised to accelerate. The stakes are high - and there's no question that network tenant cloud platforms not only change the game but are a necessary unpinning for this highly regulated and fast evolving environment.

As outlined here, a public, network-tenant cloud environment that offers flexible interoperability and global elasticity will support businesses as they roll-out serialization and track and trace solution. It will make connecting with global trade partners and exchanging data as simple as integrating to the platform once, and then interoperating with everyone. It will create a global network for collaboration and enable the smallest emerging biopharma or street corner pharmacy to enjoy the same global computing firepower and capabilities as the largest global pharmaceutical company.

The right platform will also level the playing field in terms of technical resources will support tighter financial accountability. Most importantly, though, the right networked-cloud environment is the only way to comprehensively track medications through every step of the supply chain, and truly protect patient safety.

More Stories By Brian Daleiden

Brian Daleiden is Vice President of Industry Marketing at TraceLink, a company focused on helping pharmaceutical manufacturers, distributors and dispensers deliver safe prescription medicines to patients everywhere with the largest track and trace network in the Life Sciences industry. In this capacity, he leads the company’s thought leadership, global regulatory analysis and market education programs that help industry stakeholders understand and respond to emerging regulatory, business and technical requirements.

Brian holds an MBA from Vanderbilt University and a BS from the University of Wisconsin. Brian can be reached at [email protected]

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.