Serialization. All Product delivered by Supplier to Lannett shall meet serialization requirements, as outlined in the Drug Supply Chain Security Act (Title II of the Drug Quality and Security Act) signed into law on November 27, 2013. Requirements include, but are not limited to, the addition of Product identifiers imprinted on each sellable unit, on each homogeneous case and on each pallet intended to be introduced in the United States market. Unique product identifiers will include a national drug code, serial identifier (provided by Lannett), lot number, and expiration date. Serial numbers must be aggregated from item to case and case to pallet.
Serialization. All Product delivered by Seller to Lannett shall meet serialization requirements, as outlined in the Drug Supply Chain Security Act (Title II of the Drug Quality and Security Act) signed into law on November 27, 2013 and provide data to support Product traceability as deemed necessary by Xxxxxxx. Requirements include, but are not limited to, the addition of unique Product identifiers Global Trade Item Number (“GTIN”), Serial Number (“SN”), Lot of batch number (“LOT”), expiration date (“EXP”) imprinted on each sellable unit, the same unique Product identifiers mentioned above and Quantity (“QTY”) are required on each homogeneous case and Serialized Shipping Container Code, 18-digit (“SSCC18”) on each pallet intended to be introduced in the US market. Serial numbers must be aggregated from unit to case and case to pallet. Reporting of serial number and aggregation data is required to coincide with finished goods shipment and must conform to data exchange format and connectivity specifications supported by TraceLink. 106569863.v1
Serialization. All deliverable Products shall be serialized with regard to the base part number. No two deliverable Products shall have the same serial number. Serial numbers shall remain the same regardless of configuration changes subsequent to acceptance testing. Serial numbers of Products returned and subsequently not resubmitted shall not be re-assigned.
Serialization. SerializationInfoEnumerator respectively its corresponding Contract Wizard class CW_SERIALIZATION_INFO_ENUMERATOR implement Current. However, they do not return an object of type SYSTEM_OBJECT but of type SERIALIZATION_ENTRY. Normally, this is a legal redeclaration since SERIALIZATION_ENTRY is a subtype of SYSTEM_OBJECT. The problem is that SERIALIZATION_ENTRY is expanded and the compiler states a non conforming signature of the redeclaration. Error code: VDRD(2) Type error: redeclaration has non-conforming signature. What to do: make sure that redeclaration uses signature (number and types of arguments and result) conforming to that of the original. Class: CW_SERIALIZATION_INFO_ENUMERATOR Redefined feature: current_: expanded CW_SERIALIZATION_ENTRY From: CW_SERIALIZATION_INFO_ENUMERATOR Precursor: current_: SYSTEM_OBJECT From: IENUMERATOR
Serialization. The Parties agree and acknowledge that the Falsified Medicines Directive (Directive 2011/62/EU) as amended by Directive 2001/83/EC and the European Commission delegated regulation (EU) 2016/161 of 2 October 2015 (“Delegated Regulation”) supplementing Directive 2001/83/EC of the European Parliament and of the Council by laying down detailed rules for the safety features appearing on the packaging of medicinal products for human use (“Serialization”), are applicable on the sale and distribution of the Product in the Territory. The Parties shall adhere to the legal requirements applicable in the Territory in connection with Serialization. SUPPLIER shall provide DISTRIBUTOR with Product with a unique identifier, tamper-evident seals and all other mandatory master data as further detailed in the Delegated Regulation (e.g. 2D-Data matrix Code, Human readable). DISTRIBUTOR shall register and pay any and all fees, [***] where necessary, associated with the Serialization of the Product at the German Medicines Verification System (securPharm e.V.), the ACS PharmaProtect GmbH, the Informationsstel le fir Arzneispezialitaten (IFA) GmbH and any other relevant agency for Serialization in the Territory, [***]. SUPPLIER or its designated onboarding partner with EMVO (the European Medicines Verification Organisation) shall upload the relevant master data relating to DISTRIBUTOR and its Designated Wholesaler.
Serialization. For NATO, there are two acceptable methods or Constructs of serialization:
Serialization. Licensee agrees to include version, release and serial numbers embedded in the object code for each copy of each Software Product it produces, as instructed by Licensor or as mutually agreed.
Serialization. 7.1 Marketing Authorization Holder will be responsible and bear the costs for the implementation of the Falsified Medicines Directive (Directive 2011/62/EU) and the new delegated act on the safety features (Commission Delegated Regulation (EU) 2016/161 - "the Delegated Regulation") that may impact on the product information and the marketing authorization dossier. In particular, placing of safety features, a unique identifier (UI) carried by a 2-D barcode and an anti-tampering device (ATD), on the packaging of prescription medicines and certain non-prescription medicines for the purposes of authentication and identification. In addition, the Marketing Authorization Holder will be responsible of uploading the UI of the units marketed in the EU into the correspondent national repository called National Medicine Verification Systems (“NMVS”) that will be connected to the centralized European Medicine Verification System (“EMVS”).
Serialization. The attributes (axis ranges, colors, text, etc.) and underlying data for graphs can now be saved and restored from a serialization file. The function WGSavePage saves the contents of a page, all graphs within the page, and all objects created in each graph, to a file. The page can be reloaded from the file using the function WGRestorePage. When the WGRestorePage function is called to restore a graph, there is no guarantee that the pointers and handles of the new graph are restored to their original values. All new handles and pointers are allocated when the graph is recreated. The WGSetObjUserID function provides a means of retrieving the handles of the graphical objects in the new, restored graph. This function writes a unique ID to the structure of the specified graphical object. This ID is saved as part of each objects current state when a graph is saved using the WGSavePage serialization function. Zooming
Serialization. The major enhancement for K40D is support for the use of serialized supplies. Initially, the developer and photoconductor will support this feature. Each of these assemblies will include a computer-readable serial number tag. The printer AVPCL reads the unique electronic serial number of each serialized supply after power up, after a cover is opened or closed and at periodic intervals during power-on. If the serial number has been changed, the date and time of the change, the usage count, and the new serial number will be logged to non-volatile RAM on the AVPCL and to the printer's hard disk. This information will be accessible from the front panel so that customers or service personnel may inspect it. Also, the printer displays warning messages on the operator panel as a supply approaches its rated life and once the rated life has been exceeded. Supplies with this serialization and counter capability are also known as `SmartSupplies'. The serializer chip has enough memory (battery backed-up) to contain a number of fields of information. Information stored in the supply's memory includes a serial number, a printer-compatibility code, a supply-compatibility code (to determine compatibility between the developer and photoconductor), factory-set life limits in both cycles and images, and variable fields for current cycle and image counts. The AVPCL reads and writes serializer information and RIGS software code interprets and presents it to the user. Because supplies, especially PC frames, are often swapped between printers, the usage count is stored in non-volatile RAM on the supply. This count will be the one used to determine the life of the supply. In order to ensure that this enhanced functionality is operable, non-serialized supplies (developers and photoconductors) will not be supported in K40D. The table below describes which supplies will support serialization and K30/K31 compatibility. TABLE 8-1 SUPPLY COMPATIBILITY ------------------------ ----------------- ---------------- --------------------- -------------------- DOWNWARD COMPATIBLE UPWARD COMPATIBLE SERIAL NUMBER PRINT COUNT TO K30/K31 FROM K30/K31 ------------------------ ----------------- ---------------- --------------------- -------------------- Toner No No Yes Yes ------------------------ ----------------- ---------------- --------------------- -------------------- K40D XL PC frame Yes Yes No No ------------------------ ----------------- ---------------- --------------------- --------------...
