Six Myths About Serialization

Manostaxx

Six Myths About Serialization

Author: Kurt Wieditz, Director/Team Leader Contract Manufacturing
Contributing author: Lora Peknik-Graham, Pfizer CentreOne CentreOne Business Development Manager

It’s coming
The global countdown to serialization compliance is well underway. Early adopters, such as Turkey and Argentina, required serialization as early as 2010, and were followed by others such as India, China and Korea.  Over the next three years, many other major markets will require adherence to their own serialization requirements, including the United States and the European Union. Expect that by 2018, serialization mandates will govern most of world’s drug supply. Biopharmaceutical companies that don’t comply will find it impossible to market their drugs in countries that have instituted serialization regulations.
Despite looming deadlines and risk to on-market drugs, many companies lag in serialization planning and implementation. With regulators shifting dates, some may have waited for the dust to settle before moving forward. Others may have delayed due to cost concerns or simple lack of knowledge about how to create an effective serialization program.
This article discusses six myths about serialization and what you need to know to move forward toward global compliance.
Myth #1: There’s plenty of time … Let’s wait and see
If you are supplying the U.S. market, you probably know that by November 2017, all biopharmaceuticals sold in the United States must include a:

  • Global Trade Item Number (GTIN)
  • Serial number
  • Lot number, and
  • Expiration date, encoded both in a 2D data matrix barcode, as well as in a human readable form.

If you have at least started your serialization project, it’s not too late to achieve compliance by the deadline — but you have to move quickly. Because initial serialization projects rarely go completely as planned, expect the total endeavor to take approximately 18 to 22 months:
Compliance planning:  6-8 months
Deployment:  12-14 months

There is a lot to do; you have no time to lose.

Myth #2: Serialization is simply setting up your packaging lines with some bar code printers and scanners
Line-level print and verification systems are fundamental to a serialization program, but they are only the first link in the serialized supply chain. The printer receives serial numbers from the line-lev¬el controllers, and the verification systems read and report the commissioned serial numbers back. This is the start of the serialized data flow. It then cascades up through a series of servers/control¬lers ultimately ending up in a secure, cloud-based repository. From this repository, products can be either authenticated or used to track and trace their movements through the supply chain.
Serialization master data is another important element of comprehensive serialization program. This is the common thread that binds the different systems up and down the supply chain that will be exchanging and referencing the serialization data. This data must be perfectly aligned in all systems. If a single data element is not aligned, data will not flow from one system to another.
Myth #3: Just give the serialization project to the packaging engineering team. They’ll get it done.
While engineering plays a key role in implementing a serialization program, they provide only one element of what must be a cross-functional team effort for you to achieve success. That means active leadership at the top of the organization down to precise orchestration at the floor level. One model for consideration:
Program governance: provides oversight, guidance, points of escalation and leadership visibility

  • Executive sponsor: Overall champion of the serialization program, generally executive manufacturing leadership. Underscores importance of project success to the executive leadership team. Sponsors the program and receives routine communication about progress, impacts to business as well as any potential issues.
  • Program governance committee: Confirms/endorses overall program scope, approves program resourcing levels and monitors program threats and risks. Meets quarterly to approve scope changes; monitor and mitigate program risks; and secure program resources and investment.
  • Supply chain security leadership team: Takes a holistic view of enhancing the security of products as they flow across supply chains, from sourcing of materials to delivery of finished goods. Serialization is a key supply chain security tool, but its coordination with other supply chain security tools is the focus of this team.

Program operations: creates program plans and drives execution of planned activities

  • Serialization project management office (PMO) steering team: Oversees implementation of the serialization program across the company’s internal and external supply network. Establishes core program strategies and monitors program plans.
  • PMO program leads: Accountable for a successful implementation of the serialization program with minimal disruption to drug supply. Manage day-to-day operations of the programs under¬way on the packaging lines; and drive the activities of multiple work streams being performed by numerous cross-functional teams, including finance, logistics, quality, supply planning, capital controls, and supply network enablement.

Implementing a serialization program in any size organization requires commitment and collaboration across the company. Entrusting only one team with the job will lead to failure.
Myth #4: One size fits all

Continue at:
The text above is owned by the site bellow referred.
Here is only a small part of the article, for more please follow the link

Leave a Reply

Your email address will not be published. Required fields are marked *