The core principles of a Level 4 system make it uniquely positioned to deliver data-sharing capability up, down, and across the supply chain.
With the U.S. Drug Supply Chain Security Act—the deadline for pharmaceutical companies and CMOs to deploy full-scale serialization—scheduled for enactment this November, and a similar EU mandate just two years away in 2019, comprehensive serialization efforts are in full swing on both sides of the Atlantic.
A complete serialization solution is composed of various software and hardware components, each focused on an area of responsibility referred to as a ‘Level.’ According to ISA95, there are five levels of track, trace, and serialization technology, consisting of Levels 0-4.
The most effective and comprehensive serialization solutions support the requirements of all levels of technology, connecting challenges at the plant/site levels with the enterprise level.
What Is a Level 4 System?
While Levels 0-3 are connected to plant/site operations, Level 4 is referred to as the “Enterprise Level.” These sorts of Cloud-based solutions can be thought of as a viewing portal into a specific portion of the overall supply chain.
From manufacturing to dispensation, the full gamut of stakeholders benefits from sharing information at various points throughout a product’s lifespan. The core principles of a Level 4 system make it uniquely positioned to deliver data-sharing capability up, down, and across the supply chain.
Essentially, a Level 4 system consists of a variety of functional areas for handling an assortment of business processes, global compliance, inter- and intra-organizational connectivity, reporting, identity access management, application programming interfaces, and other enterprise-level functions.
A best-in-class Cloud serialization and traceability solution should use multiple standard data exchange protocols, exchange patterns, data security, and data integrity techniques.
Perhaps the most accurate and succinct definition of a Level 4 system is that it manages the business-focused activities of manufacturing, warehousing, and distribution.
What Are the Elements of a Level 4 Solution?
User Interface: The user interface (UI) must be clean, crisp, modern, and responsive to the existing system’s dimensions—meaning it should be 100 percent responsive for mobile phone usage and “scale up” for large monitor displays.
Centralized Location: A chief concern at Level 4 is providing functional areas to handle business logistics. Centralization and secure connectivity is a must. It is common for various user and system roles within a given organization to require access to various functional areas or APIs provided by Level 4.
For example, warehouse and distribution center workers will need to perform business processes on data collected at the packaging line (Level 2) and aggregated by a site-level system (Level 3). Before these workers can do their jobs, Level 3 must send relevant data to Level 4.
In this scenario, without a proper Level 4, warehouse workers and distribution center workers would be operating on different networks and unable to share important data. Therefore, the Level 4 system is centrally located and accessible by authenticated and authorized users and systems.
Security: Identity Access Management (IAM) plays a critical role in this requirement. Not all actors—whether human or electronic—will have the same access to Level 4 functionality and API operations. A secure Level 4 will use multi-factor authentication (MFA), certificates, API keys, and https, at a minimum.
Electronic Signature: FDA Regulation CFR 21 Part 11 clearly states that all changes within systems dealing with pharmaceutical operations must record electronic signatures for any changes made to the data. This mandate likely will also be included in pending EU stipulations.
Auditing: It is critical that all Level 4 actions taken by any actor (human or electronic) is audited. Audits include actor identifiers, dates and times, underlying objects changed, and values before and after change.
Centralized Logging: This describes the ability to collect and centralize logs from site-wide Level 3 systems as well as the Level 4 system itself, and to provide insight into that data. Centralized logging provides valuable, system-wide usability metrics and faster problem resolution.
Centrally locating logs is the first step toward using newly mined data for competitive production/business advantages.
Message Intermediation: Level 4 is where message interoperability between two or more systems occurs, transforming AJAX into XML, XML into CSV, or one XML format into another XML format before data is moved to another system.
How Do Level 4 Systems Help Ensure Global Compliance?
Government laws and regulations come and go, and are subject to changes. DSCSA, SFDA, Turkey, Europe, Argentina, Brazil, South Korea, and India all have very different requirements. Therefore, a certain amount of flexibility must be factored into any system—Level 4 or otherwise—to meet these demands.
Some governments require systems to send properly formatted data directly to a central system. Others take a more manual approach, such as (S)FTP. Whatever the case, the Level 4 system must be able to accommodate. Regardless the workflow scenario, there must be a suitable facility within Level 4 to record actions.
Here, the ability to inspect the aggregation of a batch/lot or object identifier, such as an SSCC or SGTIN, is vital. This process entails a variety of identifiers, including:
- Disposition
- Packaging level (pallet, case, item, etc.)
- Genealogy (children, parent, grandparent, etc.)
- Last known location (GLN or LAT. LONG. Pinned on a Mapping API)
- Current Location (GLN or LAT. LONG. Pinned on a Mapping API)
Serial Numbers Management: Although Level 4 isn’t the primary stage for recording product serial numbers, some degree of serial number management at Level 4 is useful—depending on the specific serialization recording system being utilized.
For example, if a manufacturer uses a solution from Adents Supervisor, this system would be its “system of record” for serialization numbers. Here, it is useful for the Level 4 solution to review serial number ranges in order to inspect and audit Supervisor’s issuance of serial numbers.
It is also desirable to have the Level 4 system configure serial numbers and communicate new and updated information back to the Level 3 system.
Business Processes: Any Level 4 system should be able to execute business processes, defined as any problems that a customer must solve in order to be compliant with government regulations and/or their own standard operating procedures. Examples include packing, shipping, disaggregation, global compliance reporting, printing, and sending/receiving files or data to and from other systems.
Label Printing: In a warehouse or distribution center, it is not uncommon for labels to get destroyed, or for rework to occur requiring additional label printing. Therefore, a Level 4 solution that assures compliance must accommodate instances of both reprinting and, should a revised serial number be required, new label printing.
Reporting: Reports are always a requirement in any enterprise level software system, and can be thought of in two classes: industry reports and customer driven reports.
The Cloud Fit and Level 4
There are advantages to deploying any modern system to the Cloud, including high availability, unlimited scalability, durable storage, database management (including identity access segregation), and metrics mining (i.e. big data) capabilities.
All of these features and capabilities are desirable in any enterprise application. The Cloud makes them a reality with very little effort and at a tremendous cost savings when compared to onsite physical hardware alternatives.
Data integrity, security, and resiliency benefit greatly from built-in features of the Cloud infrastructure. Data centers thousands of miles apart can be set up in minutes. Multiple data centers ensure data is protected from loss, and is available to all dependent applications. Backing up, restoring, and ensuring consistency among data centers is clean and concise.
Another benefit of the Cloud is the maturation of DevOps. Building, testing, and deploying software on the Cloud can follow predictable and repeatable processes that were not easily achievable just a few years ago. Principles and practices of solid DevOps methodologies ensure a high level of quality and dependability.
About the Authors
Christophe Devins is the CEO and co-founder of Adents and has more than 30 years of experience in coding, product identification, and traceability. Chuck Sailer is a serialization solutions expert with more than 20 years of supply chain and track and trace experience.
This feature story can also be found in the September/October 2017 issue of Pharmaceutical Processing.
Follow Pharmaceutical Processing on Twitter, Facebook, and LinkedIn and subscribe to our YouTube channel for updates on the latest pharmaceutical and biopharmaceutical manufacturing news!