Supply chain visualization and control

Abstract

The system and technology realize supply chain visualization. As an item moves in the supply chain, data about the item may be obtained, where the data includes event data that identifies a particular item at a particular location in the supply chain at a particular time. As at least a portion of the item moves in the supply chain, the data may be analyzed to generate information. A visualization of the information may be provided, and the visualization may be used to identify one or more changes to be made in at least a portion of the supply chain to improve the at least a portion of the supply chain.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to and the benefits of U.S. Provisional Patent Application (Application Number: US 63 / 355,538) filed on June 24, 2022, the entire contents of which are incorporated herein by reference. Background Art

[0002] Items pass through various points in the supply chain between product producers and consumers. For example, an item might be created at a first location, a factory, and then shipped to a warehouse at a second location. The product might then be shipped to a retail store at a third location and ultimately sold to a consumer. Summary of the invention

[0003] This specification describes technologies related to supply chain visualization, which is achieved by using data generated when items move through a supply chain. The visualization can be used to identify changes that need to be made in the supply chain to improve the supply chain.

[0004] Generally, one or more aspects of the subject matter described in this specification may be embodied in one or more methods (and one or more non-transitory computer-readable media tangibly encoding a computer program operable to cause a data processing device to perform operations) comprising: acquiring data about items as the items pass through a supply chain, wherein the data includes event data that identifies a specific item at a specific location in the supply chain at a specific time; analyzing the data to generate information as at least a portion of the items pass through the supply chain; and providing a visualization of the information that can be used to identify one or more changes to be made in at least a portion of the supply chain to improve that at least a portion of the supply chain.

[0005] One or more aspects of the subject matter described in this specification may also be embodied in one or more systems comprising: a data processing device comprising at least one hardware processor; and a non-transitory computer-readable medium encoded with instructions configured to cause the data processing device to perform the following operations: obtain data about the items as they pass through a supply chain, wherein the data includes event data that is used to identify specific items at a specific location in the supply chain at a specific time; analyze the data to generate information as at least a portion of the items pass through the supply chain; and provide a visualization of the information that can be used to identify one or more changes to be made in at least a portion of the supply chain to improve the at least a portion of the supply chain.

[0006] Certain embodiments of the subject matter described in this specification can achieve one or more of the following advantages. These systems and techniques can provide supply chain visibility, leveraging event data collected as products move through the supply chain to provide a full range of actionable knowledge in real time. These systems and techniques can use data generated by end-to-end serialization to evaluate supply chain performance. In certain implementations, these systems and techniques can leverage real-time and historical data to provide information and alerts, pre-packaged reports, dashboards, strategic identification of trends and potential threats, and a testing environment accessible to multiple users of the supply chain. Visualization of information can be used to identify changes that need to be made in the supply chain to improve the performance of the supply chain.

[0007] In certain implementations, these systems and technologies can provide deep insight and refined management of the supply chain, saving time in determining the root cause of production issues and sending notifications to users when production events that need to be resolved or handled occur. In certain implementations, these systems and technologies can provide visualization capabilities to improve production line throughput, enable faster and more accurate corrections, and minimize downtime or losses. In certain implementations, these systems and technologies can perform anti-counterfeiting and product authentication. For example, the system can prevent products from being diverted at distributors, confirm product authenticity at retailers, and enable engagement and cultivate brand loyalty at the customer end. In certain implementations, these systems and technologies can use end-to-end item tracking data to generate information to help manufacturers track and trace products throughout the supply chain.

[0008] In some embodiments, these systems and technologies can obtain data collected for serialization regulatory purposes, and can use the data collected for regulatory purposes to determine the performance of the supply chain. In some embodiments, these systems and technologies can use existing data collectors, cameras, scanners, and sensors in the supply chain, and do not require the addition of special data collectors or special sensors. In some embodiments, these systems and technologies can perform full-stack (L1-L4) serialization and can be quickly deployed in regional production lines, sites, or enterprises to meet the regulations of the region. These systems and technologies can be configured to meet any unique needs of supply chain partners and are cost-effective, comprehensive, and packaging equipment-independent. These systems and technologies can provide seamless, standardized communications between supply chain partners, including manufacturers, packagers, distributors, retailers, wholesalers, and customers. Other advantages can include advanced visualization and customizable dashboards to meet different user roles, real-time global monitoring and visualization capabilities that allow users to conduct comprehensive supervision no matter where they are, combined with data-driven insights to encourage continuous improvement and smart, proactive response to potential disruptions, integrated anti-counterfeiting measures, and real-time optimization of production line performance.

[0009] The details of one or more embodiments of the subject matter described in this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the invention will become apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 An example of a system that may be used to provide visualization of supply chain information is shown.

[0011] Figure 2 An example of a production line is shown.

[0012] Figure 3 is a flow chart illustrating an example of a process for providing supply chain information visualization.

[0013] Figure 4 An example of serialization levels is shown.

[0014] Figure 5 An example of supply chain information is shown.

[0015] Figure 6A-6B An example of a dashboard for displaying deactivation events is shown.

[0016] Figure 7A-7B An example of a dashboard for packaging line utilization and performance is shown.

[0017] Figures 8A-8C An example of a dashboard showing sequence number pool status and sequence number allocations.

[0018] Figures 9A-9B Example of a dashboard showing packaging batch / lot details.

[0019] Figures 10A-10B An example of a dashboard is shown.

[0020] Fig.11 An example of a single viewpoint system / platform is shown. DETAILED DESCRIPTION

[0021] Sometimes, improvements need to be made to one or more parts of a supply chain. For example, a plant manager may want to increase the output of a production line. By addressing high downtime, poor performance, and low quality, production efficiency can be improved. By addressing high downtime, poor performance, and low quality, production efficiency can be improved. When the changes to be made are known, improvements to existing infrastructure or processes may be the preferred option. Many companies do not have the information needed to identify improvements to be implemented, let alone effectively track production losses. A key reason is the cost and difficulty of obtaining data in the supply chain and actionable insights from that data.

[0022] Figure 1An example of a system that can be used to provide visualization of supply chain information is shown. Figure 1 An environment 100 is shown that includes a supply chain visualization and control system 102 , a network 104 , and a supply chain 106 .

[0023] A supply chain is a series of processes involved in the production and distribution of items (e.g., goods or products). A supply chain can include multiple locations through which items pass. For example, a supply chain 106 includes a manufacturer 108, a distributor 112, a retailer 116, and a consumer 118. Items 110 (e.g., products) manufactured and packaged by the manufacturer 108 move through the supply chain 106. During manufacturing, items can move from different sites of the manufacturer 108. After manufacturing, the items 110 can be shipped by one or more distributors 112 to one or more retailers 116. Retailers 116 can sell the items 110 to one or more consumers 118. In some implementations, distributors can send items to wholesalers, and wholesalers can send items to retailers.

[0024] As items 110 move through supply chain 106, supply chain 106 may generate data 120 about items 110. Different events may occur at each location in the supply chain. Data 120 may include event data that identifies the status of a particular item at a particular location in supply chain 106 at a particular time. For example, events that may occur at each location in the supply chain (e.g., manufacturer, packager, distributor, wholesaler, and retailer) may include activation, deactivation, packaging, shipping, quality assurance (QA) sampling, receiving, unpacking, destruction, and distribution.

[0025] In some embodiments, data 120 may include batch-based events, machine-based events, or a combination of the two. Batch-based events may include starting a batch, pausing a batch, resuming a batch, and ending a batch. Machine-based (e.g., packaging site management server / computer) events may include machine available, user logged in, maintenance mode, machine in batch (active), offline / power off. Some events may be sent in batches (e.g., batch-based), and some single events (e.g., health and heartbeat messages, alarms, and alerts) may be sent when they occur. Events may include time interval data (e.g., health and heartbeat messages).

[0026] In some embodiments, data 120 about items can include counts of used and deactivated items for a snapshot in time and / or associated with a portion of a supply chain. An activation event describes an item that appears in a supply chain. For example, an activation event occurs when an item is manufactured, an item passes inspection, an item is determined to be good, or a wholesaler receives a package. A deactivation event describes when an item is removed from the supply chain, an item fails inspection, or an item is rejected. For example, a deactivation event occurs when a defective item is discarded or when a customer purchases a product at a retail store.

[0027] In some embodiments, the number of enabled and disabled items can be obtained from production line inspection data collected by sensors installed on the production line.For example, events occurring at the manufacturer 108 can include events occurring on the production line. Figure 2 An example of a production line 200 is shown. The production line may include various equipment for manufacturing and / or packaging articles. For example, the production line 200 includes a descrambler 202, a filler 204, a labeler 206, a case packer 208, a box labeler and a radio frequency identification (RFID) verification machine 210 and a palletizer 212. There are many other variations of the production line 200. In addition, various scanners 218, one or more RFID readers 220, etc. can be installed on the production line 200. The number of used and deactivated articles can be obtained from the inspection data collected on the production line 200 by sensors installed on the production line 200, such as one or more cameras 214, one or more printers 216 (e.g., one or more laser printers 222), one or more handheld scanners or cameras.

[0028] Return to reference Figure 1 In some embodiments, the data 120 for each location can be generated by a server at that location. For example, data related to packaging can be generated by a packaging batch / site management server. The packaging site management server can coordinate the data and can send the data (e.g., as a list of events) to the system 102. The events of the packaging site management server can trigger the server to send more information to the system 102.

[0029] Data associated with a packaging batch may include batch identification (e.g., batch number, expiration date, product, manufacturer, site, line), events (e.g., start, pause, resume, end; time; running, paused, used), containers (packing level, name), counts (dedicated, deactivated, packed, unpacked, items per interval), deactivation details (container level, reason, location), batch control variables, serial number assignments (assigned, used, returned), etc. In some examples, data associated with a packaging site may include geographic location, manufacturer, product, line, and serial number pool status.

[0030] In some embodiments, data about items 120 can be collected through an item processing stream (IPS). IPS can be implemented using one or more details in U.S. Patent No. 8,190,279, which is hereby incorporated by reference in its entirety. In some embodiments, data 120 may include data and timestamps for each item inspected on the packaging line. Each time an item is inspected as passed or failed (e.g., used / disabled), a timestamp is obtained. Data may include packaging batches, one batch at a time. Data may include packaging levels, whether cartons, bales, or pallets. Data may include information related to grouping items together and the average number of items per minute. Data may include the number of items moving on the packaging line at any given time during the production process. In some embodiments, the data may be stored in a database.

[0031] The supply chain visualization and control system 102 may be a real-time supply chain monitoring and control system for monitoring and controlling the supply chain. The supply chain visualization and control system 102 obtains data 120 about items through a network 104. The network 104 may be a private network, a public network, a virtual private network, a wired or wireless network, etc. In some implementations, the network 104 may be a global communication network, and the system 102 may obtain data 120 about items through the global communication network when the items pass through a wide range of areas and regions.

[0032] As the items 110 pass through the supply chain 106, the system 102 processes data 120 about the items and generates information 128 about the supply chain 106. The system 102 may use data analytics (e.g., machine learning and artificial intelligence) to process the data 120. The information 128 may include one or more analyses and / or indicators 130 of at least a portion of the supply chain. For example, the information 128 may include deactivation information, serial number pool information, packaging line performance information, and packaging batch information. In some examples, the information 128 may include batch deactivation profiles, packaging batch alarms, packaging batch events, power failures, and audit logs. In some implementations, the system 102 may include predictive analytics capabilities. Using the power of machine learning algorithms and artificial intelligence, the system can not only process historical data, but also predict future trends based on this data. It can predict potential disruptions in the supply chain so that preventive measures can be taken to keep things running smoothly. These predictions can be part of the information 128 generated by the system.

[0033] The system 102 can provide visualization of information. In some embodiments, the system 102 can generate at least one dashboard 132, which organizes and displays the information 128 of the supply chain. For example, the dashboard 132 can provide a view of the packaging site hierarchy, serialization and batch data, and production line details in a single source (e.g., a data visualization system). In some embodiments, the system 102 can manage supply chain data, including product serialization for supply chain operations using standard codes, non-standard codes, or a combination of the two. The dashboard 132 can include information related to production (by site, product, manufacturer), deactivation details (by site, product, manufacturer), batch summary (e.g., production line manager batch summary report), serial numbers assigned by batch, packaging site management server serial number pool status, packaging production line, activation, deactivation, parts per minute across multiple batches, and batch runtime profile performance from start to finish. More examples of dashboards are described below in conjunction with Figures 6-10. In some embodiments, the visualization of information can include multiple views, for example, production view with work orders, notification / browser view, and node view. In some embodiments, multiple views can be displayed in multiple dashboards.

[0034] In some embodiments, a key component of the dashboard 132 may be a real-time alert system. In some embodiments, the system 102 may generate alerts based on predictive analytics, which may highlight potential disruptions or anomalies in the supply chain. The system 102 may provide a proactive approach to managing the supply chain, alerting relevant stakeholders to potential issues before they become major problems. In addition to predicting potential disruptions, the system 102 with predictive analytics capabilities may also predict future resource requirements. The system 102 with this predictive resource management capability may use trained machine learning models to estimate the demand for raw materials, labor, and capacity at each stage of the supply chain based on historical and real-time data. This proactive approach enables supply chain managers to optimize resource allocation, prevent bottlenecks, and reduce waste, thereby improving the overall efficiency and sustainability of supply chain operations.

[0035] System users can use visualization of information to identify one or more changes to be made in the supply chain to improve the supply chain. For example, counts can be used to identify high-level deactivations and analyzed using deactivation reasons, which may depend on the role within the company. Configuration is to obtain serial numbers from a master source. For example, the number of available serial numbers can be visualized, and during serial number configuration, users can avoid duplication based on the visualization. The packaging site management server can obtain the master set and deactivated sets managed by the system 102. Factory production personnel can use the dashboard to deactivate. For example, when a product is discarded, factory production personnel can analyze the reasons for its deactivation based on the dashboard. In some implementations, the system 102 can integrate blockchain technology to enable secure data sharing across the supply chain.

[0036] As another example, information technology (IT) personnel and serialization management can use the serial number pool and allocation dashboard. Sometimes, it is difficult to know when a serial number is empty. Although the system can send an email notification to the relevant user, the person receiving the email may not respond or may be on vacation. The present system and technology can ensure that there are enough serial numbers to run production. For example, in China, serial numbers are purchased from the government. A serialization management user or production line manager may notice that a specific production line with a pool of 100 serial numbers is empty, but multiple products and packaging levels are configured to start production. If the user attempts to run production on any of these products, they will not be able to start the batch because the serial number is empty. The present system and technology can ensure that anyone can see at any time that a serial number is low or empty and be able to notify someone before it affects production.

[0037] The real-time supply chain visualization and control system 102 provides supply chain visibility, thereby providing a full range of actionable knowledge in real time. When an item 110 passes through the supply chain 106, event data 120 is generated. Event data 120 includes, but is not limited to, collecting and storing critical data with timestamps. End-to-end serialization generates data 120 that can be used to evaluate supply chain performance. Therefore, the system 102 can provide practical insights and connectivity from the beginning of deployment. In some implementations, the system 102 can process real-time data and historical data, and can generate information and alerts, pre-packaged reports and dashboards, strategic identification of trends and potential threats, and test environments accessible to multiple users.

[0038] Figure 3 is a flow chart illustrating an example of a process 300 for providing supply chain information visualization. For example, Figure 1System 102 in the supply chain may perform process 300. As the item moves through the supply chain, data about the item is obtained 302. In some embodiments, the data may include event data that identifies a specific item at a specific location in the supply chain at a specific time. For example, system 102 may obtain event data through network 104 that identifies a box of toys that was unpacked at distributor 112 at a first time on a specific day and repackaged and shipped to a retailer at a later time that day.

[0039] In some embodiments, the system 102 can process unstructured data, which may come from a variety of sources, such as feedback, emails, machine logs, technician reports, customer inquiries, and internal communications. The system 102 uses advanced natural language processing (NLP) techniques to process this unstructured data and extract information related to supply chain performance. The extracted information can then be converted into a structured format and incorporated into the overall supply chain data 120. In this way, the system 102 can provide a more holistic and comprehensive view of supply chain performance that includes not only quantitative data, but also qualitative insights drawn from the unstructured data.

[0040] In some embodiments, the system can obtain the collected item data from the existing packaging site server and packaging line management system instead of installing a separate data collection device and data history server. This can reduce costs and improve the efficiency of implementing the supply chain visualization and control system 102. In addition, the system can further optimize the data collection process by integrating edge computing devices deployed in the packaging site server and packaging line management system. These edge computing devices can directly obtain and process data at the source, eliminating the need for separate data collection devices. The acquired data can be securely transmitted to the system 102, ensuring real-time access to accurate and up-to-date information about supply chain performance.

[0041] In some embodiments, data about items may include counts of used and discontinued items for a snapshot in time and / or associated with a certain portion of a supply chain. In some embodiments, data about items may include counts of used and discontinued items during packaging and / or from a specific station. In some embodiments, counts may be obtained from inspection data collected on a production line by sensors installed on the production line. For example, referring to Figure 1 and Figure 2, the system 102 can obtain the number of items that have been put into use and out of use at one or more parts of the production line 200 (e.g., at the decoder 202, at the filler 204, at the labeler 206, etc.) over a period of time. The counts can be obtained from the camera 214 and / or the label scanners 218 and 220 installed on the production line 200. In addition, the system 102 can implement advanced computer vision algorithms to analyze the collected visual data and accurately identify and count the items that have been put into use and out of use. These computer vision algorithms can utilize deep learning techniques to accurately identify and track the progress of items on the production line. By incorporating computer vision capabilities, the system 102 enhances its ability to provide real-time and reliable information about supply chain performance.

[0042] In some embodiments, the system can receive serialized data of items from a computer located at a production facility, a packaging facility, a distribution facility, or a combination thereof. The computer can be a dedicated computer system or a smart phone. Serialization is the process of tracking and tracing items from the point of manufacture to the point of sale. Using advanced decoding algorithms, these unique identifiers can efficiently and accurately locate and track the status of individual products as they pass through the supply chain. It can be a process of assigning a unique identifier to each item, which is used to track and trace items throughout the supply chain. For example, a manufacturer can attach a tag 140 (such as a barcode, a quick response (QR) code, or any other suitable symbol) to the packaging of a product. System 102 can use a tag 140 to track and trace items moving in a supply chain 106 by generating serialized data. Serialized data can include a globally unique serial number assigned to an item 110 moving through a supply chain. For example, serialized data of drugs in a global supply chain can help prevent drug counterfeiting, simplify regulatory compliance processes, and protect patients. In some implementations, serialized data can include ingredients, parts, components, products, packaging, seals, or any data related to a packaging line.

[0043] In some embodiments, serialized data can be generated at various levels. Using Internet of Things (IoT) technology, sensor data and metadata from various points in the supply chain can be collected at high-frequency intervals. Subsequently, the time-stamped data collected and stored in the cloud can be used for real-time analysis and long-term historical analysis, thereby facilitating immediate decision-making and long-term strategic planning. In some embodiments, serialized data can be generated by a serialization module. In some embodiments, the serialization module can be included in the system 102, and the system 102 can perform serialization and generate serialized data. In some embodiments, serialized data can be generated by one or more computers at one or more locations in the supply chain. For example, serialized data of item 110 can be obtained at the manufacturer 108, the distributor 112, the retailer 116, or at the manufacturer 108, the distributor 112, and the retailer 116 at the same time. In addition, the system 102 can use advanced data aggregation technology to integrate serialized data from various sources to ensure a unified and comprehensive understanding of the serialization status of items throughout the supply chain. By integrating data from multiple points, the system 102 can more accurately and reliably represent the serialization performance of the supply chain.

[0044] In some implementations, the serialized data of an item can be Figure 4 The levels shown in . Figure 4 An example of serialization levels is shown. In some implementations, the system is architected with a modular design to provide tailored functionality to each user group while maintaining cohesion and seamless communication between all components. Advanced access control and data partitioning techniques are used to ensure that each stakeholder (e.g., manufacturer, packer, distributor, retailer, or end consumer) receives only the relevant, role-specific data required to perform their function effectively and efficiently. This promotes transparency where necessary while maintaining confidentiality where required. Serialization levels include Level 1 (device), Level 2 (line), Level 3 (site), and Level 4 (enterprise). Other implementations may include more than Figure 4 In more or less levels of examples. In level 1, serialization data of an item can be obtained from manufacturing equipment through interface interaction with existing or new packaging equipment. In level 2, serialization data of an item can be obtained from production line equipment, and system 102 can track the serialization data integrity of an entire packaging batch or batch. In level 3, the serialization data of an item can include event data, site-level master data, serial number management data, event reporting data, and data for offline serialized packaging operations. In level 4, the serialization data of an item can include connection data, which can be used to comprehensively track and trace the item and ensure compliance integration. In addition, system 102 can implement a data synchronization mechanism between different serialization levels to maintain data consistency and provide an accurate representation of the serialization status of the supply chain.

[0045] In some embodiments, the serialization level may include component level, bale level, case level, pallet level, or a combination thereof. In some embodiments, the system may support multiple serialization workflows to meet various packaging scenarios and serialization requirements at component level, bale level, case level, and pallet level. For example, at the component level, the serialization data may include one or more of the following data: carton printing and verification operations, bottle labeling operations, manual printing and scanning operations, bottom / top code association of bottles, third-party camera interface, etc. At the bale level, the serialization data may include one or more of the following data: labeled bales, virtual bales, bale group reading, bale infeed reading, integrated bale label printer, remote bale label printer, etc. At the case level, the serialization data may include one or more of the following data: automatic case packer, manual case packing operation, semi-automatic case packer, manual printing and scanning (no aggregation), layer packaging, case infeed reading, etc. At the pallet level, the serialization data may include one or more of the following data: manual palletizing, automatic palletizing, end-of-line information, central information, etc.

[0046] Thus, instead of relying on multiple suppliers for full stack serialization at the serialization level, full stack serialization at all levels can be performed by a serialization module from the same supplier. A serialization module can include a configurable library of solutions, can be packaging equipment agnostic, such as with retrofit capabilities, and / or can include reusable validation packages, such as templates, assessments, traceability. A serialization module can provide pricing transparency, such as providing full project scope pricing rather than partial project scope pricing.

[0047] In some implementations, the system may receive item authentication data and end-to-end item tracking data from computers throughout the supply chain via a global communications network. In addition, the system 102 may integrate blockchain technology to ensure the integrity, security, and traceability of items in the supply chain. Each item may be assigned a unique, unchangeable identifier that is recorded on a decentralized and secure blockchain ledger. This ensures that the information associated with each item is unchangeable, thereby providing a reliable and verifiable record of each item's journey in the supply chain, thereby enhancing trust among stakeholders and effectively eliminating counterfeiting and unauthorized changes. The computer may be a dedicated computer system or a smartphone. Item authentication data may be used to verify the identity of items moving in the supply chain. End-to-end tracking data may be used to identify the location of an item at a specific time as it moves in the supply chain. In some implementations, one or both of the item authentication data and the end-to-end item tracking data may be an electronic fingerprint 124. A computer at each location in the supply chain may perform authentication on the item and may generate corresponding item authentication data for that location. A computer at each location in the supply chain may track items and may generate item tracking data. Item tracking data generated at locations in the supply chain can be combined to generate end-to-end item tracking data. The supply chain can involve locations in different parts of the world. Network 104 can be a global communication network, and computers throughout the supply chain can send item authentication data and end-to-end item tracking data through the global communication network.

[0048] In some implementations, the system 102 may include a production line management system, and the system 102 may obtain end-to-end item tracking data from the production line management system. The production line management system may be implemented using one or more details in U.S. Pat. No. US 8,190,279, which is hereby incorporated by reference in its entirety. The production line management system may be used to uniquely identify items and allow them to be tracked through the supply chain, thereby minimizing diversion and counterfeiting, while supporting visual inspection and I / O operations, which further supports the packaging of serialized and non-serialized products. The system may use, for example, optical character verification (OCV), optical character recognition (OCR), barcodes, printing and general quality inspections, and combinations of other technologies that are apparent to those skilled in the art based on the disclosure herein to provide accurate real-time inspection results.

[0049] In some embodiments, the system can identify items by generating an electronic fingerprint from a captured image of a mark on the item using computer image processing. For example, the system 102 can obtain an electronic fingerprint 124 from a supply chain. The electronic fingerprint can include a mark, a batch number, an expiration date, a product identification, or a combination thereof. In some implementations, the electronic fingerprint can be a digital representation of a printed variation of a distinct mark that distinguishes the item. For example, the mark 140 on the item 110 can have a unique variation due to the formation of a symbol on the item, such as due to the use of a specific printer. The present system and technology can be implemented using one or more details in U.S. Patent No. 10,061,958, which is incorporated herein by reference. The system 102 can use advanced image recognition algorithms and machine learning models to accurately analyze the electronic fingerprint and match it with reference data, thereby facilitating the effective identification and verification of items in the supply chain.

[0050] System 102 can use an electronic fingerprint-based authentication process to identify item 110. For example, manufacturer 108 can create an electronic fingerprint 124 that includes a unique product signature. Since each item 110 can have a unique electronic fingerprint 124, each item can have a non-additive and non-forgeable unique identity. For example, during packaging and transportation, the electronic fingerprint 124 can be associated with a pallet and a shipper. Manufacturer 108 can send the electronic fingerprint 124 to a secure cloud server of system 102 via network 104. System 102 can save the electronic fingerprint 124 in a secure cloud server that can be connected to system 102. When another location in the supply chain receives the item, the device at that location can authenticate the received item. For example, a distributor, retailer, or customer can use a smartphone, computer, or other device to effectively perform instant authentication. The device can capture an image of the received item and send the image to a secure cloud server. The secure cloud server can perform identity authentication using the saved electronic fingerprint 124, for example, by comparing the saved electronic fingerprint with the fingerprint information obtained from the image. Using the above-mentioned authentication process, the system can perform anti-counterfeiting and product authentication. For example, the system can prevent product diversion at distributors, can confirm product authenticity at retailers, and can enable engagement and foster brand loyalty at the customer end.

[0051] As at least a portion of the item moves through the supply chain, the data is analyzed 304 to generate information. For example, the system 102 can process the data 120 about the item 110 and can generate the supply chain information 128. As at least a portion of the item 110 moves through the supply chain 106, the system 102 can analyze event data for events occurring at different locations in the supply chain and can generate the supply chain information 128 for the corresponding locations. In some implementations, as the item 110 moves through the supply chain, the system 102 can continuously receive additional data about the item and can generate updated information using the additional data.

[0052] For example, the system 102 can use the end-to-end item tracking data to generate information that helps manufacturers track and trace products through the supply chain. The information 128 generated using the end-to-end item tracking data can include serial number usage, disposition event information (disposition counts, by batch and product / material), serial number pool status, serial number allocation, European Medicines Verification System (EMVS) status, Verification Router Service (VRS) activity, material / product configuration, job queue performance, and distribution rankings.

[0053] In some implementations, the system may analyze data about at least a portion of the items that are moving through the supply chain, and may analyze historical data about another portion of the items that have completely moved through the supply chain, have been discarded before completely moving through the supply chain, or both. For example, a manufacturer may convey three items 110 (pallets) through the supply chain 106. The first pallet has completely moved through the supply chain and is sold to a consumer 118. The second pallet is discarded at a retailer 116 and has not yet completely moved through the supply chain. The system 102 may save historical data 126 about the first pallet and the second pallet, for example, in a database installed on a computer. The system 102 may receive data about a third pallet as the third pallet moves through the supply chain. The system 102 may analyze data about the third pallet moving through the supply chain, and may analyze historical data 126 about the first pallet, the second pallet, or the first pallet and the second pallet.

[0054] In some embodiments, the generated information may include deactivation information, serial number pool information, packaging line performance information, and packaging batch information. Figure 5 Examples of supply chain information are shown, including discontinuation information 502 , serial number pool information 504 , packaging line performance information 506 , and packaging batch information 510 .

[0055] A visualization 306 of information is provided, and the information can be used to identify one or more changes to be made in at least a portion of the supply chain to improve at least a portion of the supply chain. The visualization can include reports, charts, thresholds, indicators, tables, trends, etc. In some implementations, the visualization can include one or more dashboards 132 displaying the information. For example, referring to Figure 5 , charts and graphs under each type of information (eg, deactivation information 502, serial number pool information 504, packaging line performance information 506, and packaging batch information 510) may be visualizations of the information.

[0056] This information can be used to identify one or more changes made in at least a portion of the supply chain to improve at least a portion of the supply chain. A portion of the supply chain can be, for example, a single location or a collection of two or more locations. Changes to the supply chain can be, for example, to increase the output and / or efficiency of the production line by calculating and tracking production losses, reducing downtime, improving equipment performance, improving product quality, etc. For example, a batch configuration change of a manufacturer can reduce the number of outage events that occur at the manufacturer. In some embodiments, the system can provide analytical visualizations across multiple sites, production lines, production and packaging levels, such as packaging batch statistics. Visualization can show patterns that are not obvious by viewing a single good manufacturing practice (GMP) or regulatory report. For example, patterns such as how production line speed affects the production of substandard products or a decline in production line efficiency at similar times of the day only become apparent when comparing weeks and months of data in the same view. In some embodiments, the system 102 can also use machine learning algorithms based on historical data and real-time data to predict future situations in the supply chain, such as potential bottlenecks, inefficiencies, or failures. This predictive function can suggest preventive measures to avoid predicted supply chain problems, thereby providing a more robust and uninterrupted supply chain. Additionally, in some embodiments, the system can estimate the optimal production rates for different production lines based on the supply chain's past performance, current status, and future trends. This can provide valuable insights for optimizing efficiency and throughput while minimizing potential problems.

[0057] For example, Fig. 7A Visualizes information about the average number of parts per minute (PPM). Parts can be cartons, labels, boxes, or other packaging related items. Average PPM provides an overall average for all produced items. Packaging lines are designed to run at a specific rate. Fig. 7AThe dashboard in shows the average PPM for batches being run on the packaging line. When the PPM is low, the line is running slowly and that is a cause for concern. There could be many issues on the line that could be causing a low PPM. When the PPM is low, this is an indication that the line and batch need further investigation, especially if the low average PPM is occurring continuously or repeatedly. When the PPM is high and the number of outages is high, the line is running too fast and causing too many outages. This is an indication that the line needs to be redesigned. Therefore, the three data points for each batch on the packaging dashboard (PPM, In Use, Outages) can provide further insight into anomalies in one area compared to other areas.

[0058] Based on analysis of average PPM and stop counts, users can determine if a packaging line is running too fast or too slow. For example, through the interface, users can take corrective action by adjusting production speeds to optimize efficiency and minimize stop items. In addition, the system can leverage predictive capabilities to predict whether a packaging line will run too fast or too slow in the future. It can do this by processing historical and real-time data through machine learning algorithms. Predictive analytics can then guide users to make proactive adjustments to optimize line speeds to preemptively address efficiency and stop item issues. As another example, users can investigate root causes, such as equipment failure or component failure. Through the interface, they can create maintenance requests, schedule equipment repairs, or order replacement parts to resolve issues and ensure smooth operations.

[0059] In some embodiments, a user of the system 102 can determine at least a portion of the changes that need to be made to the supply chain to improve the at least a portion of the supply chain. In addition, the system 102 can proactively predict potential changes that need to be made in the supply chain to improve its efficiency and throughput. The prediction can be derived from historical and real-time data analysis using machine learning algorithms. Thus, the system helps users make smart proactive changes to reduce the occurrence of supply chain disruptions. In some embodiments, the system 102 can display recommended changes to at least a portion of the supply chain that may improve at least a portion of the supply chain. Fig. 10B is an example dashboard that displays a summary of notifications. The notification summary can be used to improve the supply chain. For example, a user can review failed notifications to take corrective actions. As another example, the system can recommend one or more corrective actions to improve a portion of the supply chain.

[0060] In some embodiments, the system can send different dashboards to display (i) downtime events for sites, products, and packaging lines, (ii) serial number pool status and serial number assignments, (iii) packaging line utilization and performance, and (iv) packaging batch / lot details, including setup, run time, events, counts, and downtime reasons. In some embodiments, the system can send different dashboards to display production details, including cleaning, maintenance, setup, material loading, and material delays.

[0061] Figure 6A-6B An example of a dashboard for displaying outage events is shown. The Outage Dashboard visualizes outage events for sites, products, and packaging lines. Fig. 6A is a sample dashboard for displaying a decommissioning summary for a period of time, such as from January 1, 2018 to December 31, 2022. The decommissioning summary displays the following: top sites based on the number of decommissioning events; top products based on the number of decommissioning events; top lines based on the number of decommissioning events; and the number of decommissioning events by month for each specified year. Fig. 6A Displays the top ten stations, top ten products, and top ten routes by deactivation events. Fig. 6A A bar chart showing the annual deactivation events by year and month is also displayed. The bar chart can provide interactive input to the dashboard. When the bar chart is selected, the data in the three boxes above can be filtered based on the selected month.

[0062] Figure 6B is an example dashboard of outage events by line and package level, showing the reasons for the outage events and their corresponding products, lines, packages, locations, and counts. With respect to outage events by line and package level, the following may be displayed: Outage reasons by line, product, and package level; Top line based on outage event counts. In some embodiments, the outage dashboard may include yearly outages and outage event trends. With respect to yearly outages, the following may be displayed: Outage reasons by line, product, and package level; Outage event counts by month for each specified year. With respect to outage event trends, the following may be displayed: Outage reason counts; Outage reasons by hour; Outage reasons by minute.

[0063] Figure 7A-7B An example of a dashboard showing packaging line utilization and performance. A packaging line is a physical structure that includes a physical conveyor belt, packaging machines, printers, cameras, and / or computers. The Packaging Line Performance dashboard visualizes packaging line utilization and performance. Fig. 7A is an example dashboard showing packaging line performance, including the average parts per minute (PPM) by batch, the number of items consigned by batch, and the number of items retired by batch. Fig. 7ADashboards in can provide drill-down, point-and-click visibility into batch PPM throughput, allowing performance normalization using such cross-batch data. Fig. 7A The dashboard shown in is useful for users who are responsible for packaging line automation engineering and production planning, responsible for packaging lines, overall packaging line installation, architecture within a site, replacing equipment, performing upgrades, scheduling software and hardware upgrades. Users can view the operation of the line, find low performing batches / lines that are not running to optimal specifications, which need to be upgraded or improved, and can conduct research to improve the productivity of the line / batch.

[0064] Figure 7B is an example dashboard showing packaging line utilization based on month and year and a timeline of batch activity on a selected line. In some embodiments, the dashboard can include information on multiple lines and their production data by connecting and merging cross-line data, thereby providing useful conclusions for multiple lines. In some embodiments, the dashboard for a packaging line can include batch performance profile commissioning and batch performance profile deactivation. Regarding batch performance profile commissioning, the item commissioning trend based on date / time by packaging level can be displayed for the selected batch. Regarding batch performance profile deactivation, the item deactivation trend based on date / time by packaging level can be displayed for the selected batch.

[0065] Figures 8A-8C An example of a dashboard showing the serial number pool status and serial number allocations. The Serial Number Pool Dashboard visualizes the serial number pool status and serial number allocations. Fig. 8A and 8B is an example of a dashboard that displays serial number pool status details, which can be updated per time period (e.g., every 24 hours). The serial number pool details displayed include threshold, available, used, and allocated serial numbers, and are displayed by site, manufacturer, product packaging level, and format. Users are able to filter by site, manufacturer, product, and allocation status. Figure 8C is an example dashboard for displaying serial number allocation information, including site, batch, start date, product, package, format, serial number strips allocated and consumed, and utilization percentages. Allocated, consumed, and returned serial numbers are displayed by site, batch, batch start date, product, package level, and format. Users can filter by processing date, site, product, line, and batch. In some embodiments, the allocated and consumed serial numbers can be displayed graphically by site, batch, batch start date, product, package level, and format. Users can filter by processing date, site, product, line, and batch.

[0066] Figures 9A-9BAn example of a dashboard showing the details of a packaging batch / lot number. A packaging batch is a batch of a product. For example, whenever a product is obtained from a pharmacy and has a batch expiration date on it, the batch number is the packaging batch of all products packaged for that particular production batch / lot number. The packaging batch information dashboard visualizes packaging batch / lot number details including setup, run time, events, counts, and reasons for discontinuation. Fig.9A is an example of Page 1 of a Batch Summary Report for a specific batch. The report contains summary information for the selected processed batch. The user can filter by Processing Date, Site, and Start Date for the selected batch. Fig.9A Displays batch summary details such as input and outage counts for different container types (e.g., cases and bottles), aggregate counts, and outage events by container type. For example, batch summary details can display the following for a selected batch: site, line, manufacturer, product; times when the batch started, paused, and ended; batch run time; batch pause time; number of items used, outages, aggregated, and fingerprinted by package level; and number of outage events by package level and outage reason.

[0067] Fig. 9B is an example of Page 2 of a Batch Summary report for a specific batch and displays a list of Batch Control Variables (LCVs). Regarding the Batch Summary for Loss Control Variables, the following can be displayed for the batch selected in the Batch Summary Details section: Batch Control Variables that have values; and Batch Control Variables that are not applicable.

[0068] In some embodiments, the system can send different dashboards to display the vaults of key documents. There may be a large number of documents related to the setup and operation lines of the supply chain. The system can determine the location where archives, project documents, printer templates, programmable logic controller (PLC) programs, equipment configurations, or any type of files are saved and organized, and the location can be a single secure location. For example, the system can store archives and project-related documents in a single location. Files can be tagged with change control numbers or user-defined tags for faster searching through the dashboard's user interface. For example, the dashboard can include personalized filters to display the required information. Custom tags can be created on individual documents, and the publishing status can be updated on individual documents. Users can view file details and create links to external reference documents.

[0069] In some embodiments, the system can collect and centralize data about multiple production lines and sites. The system can provide actionable reports on production line operations of manufacturing and packaging facilities. The real-time supply chain visualization and control system can provide pre-configured reports and / or the ability to develop custom reports.

[0070] In some embodiments, the system can identify 308 trends and potential threats based on predetermined thresholds associated with at least one of the outage information, the serial number pool information, the packaging line performance information, and the packaging batch information. Fig. 8A , the system can obtain a predetermined threshold of serial number count for each product type and each packaging type (e.g., carton or box). The system can compare the available serial numbers to the threshold to determine the potential threat of insufficient available serial numbers.

[0071] In some embodiments, the system can generate an interactive graphical view for visualizing data related to the serial number pool. For example, the graphical view can be a geographical representation, such as a world map. The serial number pool can represent a serial number inventory, and the serial number inventory can be obtained from a government agency or a trading partner. For example, the system can obtain packaging data that focuses on meeting GMP and regulatory packaging requirements. Validation work can focus on the accuracy of these data to meet these requirements, so that packaging sites and production lines remain operational. Some validation work may be costly and time-consuming. Using the systems and techniques described herein, site servers and packaging line systems can be modified to keep pace with regulations, and packaging operations can generate and collect data for GMP and regulatory requirements. Therefore, the present system and technology can use the collected data for serialization regulatory purposes, and the performance of the packaging line can be determined using the data collected for regulatory purposes.

[0072] In some embodiments, the visualization can include a serialization number pool visualization including count data for assigned serialization numbers based on site, manufacturer, product, and packaging, used serialization numbers, available serialization numbers, deactivated serialization numbers, serialization formats, serialization number count thresholds, and a visual indicator to indicate whether the available serialization numbers are above or below the serialization number count threshold. Fig. 8A 801, manufacturer 802, product 804, and packaging 806, count data for assigned serialization numbers 816, used serialization numbers 814, available serialization numbers 812, deactivated serialization numbers, d serialization formats 808, and count data for serialization number count thresholds 810, and visual indicators 818 for indicating whether the available serialization numbers are above or below the serialization number count threshold. In some implementations, the serialization number count threshold may be a predetermined value set by a customer. For example, the serialization number count threshold 810 may be a predetermined value set by a customer.

[0073] In some embodiments, the system may include a predictive analytics module that is capable of leveraging historical data to predict future trends, potential failures, and successes in various aspects of operations. The predictive analytics module may leverage machine learning algorithms and statistical models to provide predictive insights based on data on outage events, packaging line utilization, serial number pool status, and packaging batch / lot details. The predictive module may provide, for example, predictions of potential outage events, expected serial number assignments, expected production line performance, and expected packaging batch / lot details. By enabling this foresight, the system allows users to take proactive steps to mitigate potential problems or seize favorable trends, thereby improving the efficiency, productivity, and cost-effectiveness of operations.

[0074] For example, Fig. 8A The Allocated column 816 shows how many sequence numbers have been set aside but not used, and should not exceed the "Available" value. Fig. 8A The triangle in the is an indicator that the "available" value is above or below the "threshold". When the indicator is a downward triangle, the customer can purchase more serial numbers. When the indicator is an upward triangle, the customer does not need to purchase more serial numbers. It may take some time to purchase serial numbers, especially when the serial numbers are provided by regulatory or government agencies. Therefore, the system and technology can provide visibility of procurement needs in advance to ensure the efficiency and smoothness of the supply chain. In some embodiments, the system may include an alert mechanism that can issue warnings in response to detected anomalies or potential problems in operations. The alert mechanism can analyze data collected from outage events, packaging line utilization, serial number pool status, and packaging batch / lot details, and issue alerts to relevant personnel in real time when significant deviations from expected patterns or thresholds are identified. For example, a sharp increase in outage events, a sudden drop in packaging line performance, or a significant decrease in available serial numbers in the pool may trigger an alert. These alerts can prompt rapid intervention and correction, thereby mitigating operational disruptions and maintaining productivity and efficiency.

[0075] In some embodiments, the system may send different sets of information about a particular item to two or more of the manufacturer, packager, distributor, retailer, and end consumer. Figure 1 , the system 102 may send information 122 of the item to two or more of the manufacturer 108, the packager, the distributor 112, the retailer 116, and the end consumer 118. For example, the system 102 may send out-of-service information of a pallet of items to the manufacturer 108 and the distributor 112. As another example, the system may send a dashboard of packaging information to the distributor, who may understand the efficiency and utilization of its packaging operations.

[0076] In some embodiments, the system can generate an interactive graphical view of an organization's sites, environments, data sources, machines and site servers, and packaging line systems. Fig. 10Ashows an example dashboard that includes an interactive graphical view of an organization's sites, environments, data sources, machines, site servers, and packaging line systems. For example, lines and equipment can be combined and displayed in Fig. 10A A management view is shown. A graphical scene can help visualize an organization (e.g., a company) and its local assets, such as machines and site servers used for development (including engineering and QA testing) and product management. Fig. 10A One or more inspector controls are displayed on the right side of the dashboard. The inspector controls can provide commands (e.g., diagnostic commands) as well as health and heartbeat information. Through the dashboard, the system can issue commands to nodes, components, or modules of the packaging line system. For example, a diagnostic command can be sent to a node to run a diagnostic program and send the results back to the system. As another example, an archive command can be sent to a node to create a backup of its configuration and return the backup file to the system.

[0077] Fig. 10B Another example dashboard is shown that includes an interactive graphical view. Fig. 10B The Enterprise Notifications dashboard is shown, which provides visibility into operations on the supply chain managed by an organization, including production lines. For example, notifications can be quickly sent to operators via text message. The dashboard includes personalized filters for viewing successful or failed notifications. Viewers of the dashboard can focus on failed notifications so that corrective action can be taken. The dashboard includes an inspector control on the right. The inspector control can provide status change details on the Notes tab to aid in troubleshooting.

[0078] In some embodiments, the interactive graphical view may include representations of equipment installed on an organization's production line. Equipment displayed in the user scenario of the graphical user interface may include cameras, printers, barcode scanners, and sensors installed on the production line. For example, the interactive graphical view may include representations of cameras, printers, barcode scanners, and sensors installed on an organization's production line. Figure 2 An example of a production line 200 is shown. Different types of equipment, such as cameras 214, printers 216 (e.g., laser printer 222), scanners (e.g., handheld scanner 218 and RFID encoder / reader 220), and sensors (e.g., camera 214, temperature sensor, light sensor, or motion sensor) can be installed on the production line 200. The system 102 can display a visualization of representations of the equipment in the production line in an interactive graphical view. Fig. 10A An example dashboard containing an interactive graphical view of an organization's local assets is shown. The equipment installed on production line 200 may be Fig. 10A The “local assets” represented in .

[0079] The present systems and techniques provide end-to-end serialization and in the process generate data that can be used to analyze overall equipment effectiveness (OEE). In the example, OEE is a best practice metric that indicates how well a manufacturing operation is utilized compared to its full potential. To achieve this, key performance losses and bottlenecks are identified to calculate and improve OEE. The OEE methodology measures line productivity based on three key performance indicators: 100% availability (no downtime), 100% performance (as fast as possible), and 100% quality (no error output). OEE is a standard method for measuring manufacturing productivity and consists of three key performance indicators (KPIs): availability, performance, and quality. Availability evaluates actual versus planned production time. Performance considers actual versus theoretical maximum line rate. Quality addresses the ratio of good products produced to total products. The systems and techniques described herein can also provide real-time monitoring of line key performance indicators (KPIs) for packaging operations. This allows KPIs such as production speed, equipment downtime, and product quality to be continuously tracked and analyzed, providing immediate insights for performance improvements.

[0080] A best-in-class manufacturing plant might achieve an 85% OEE rate. Many companies don’t have the information needed to calculate, let alone track it effectively. A key reason is the cost and difficulty of acquiring data and the time it takes to make an impact. Only when data is tangible and easily accessible can improvements be made to increase productivity.

[0081] OEE tools can provide accurate data about a site's major production losses. By identifying the factors that contribute to downtime, poor performance, and poor quality, corrective actions can be prioritized. Before implementing a continuous improvement program, OEE is typically 50%-60%. With tools that allow incremental changes over time based on facts, manufacturers can achieve OEE levels of 85%. Manual OEE solutions, such as having operators fill out worksheets, are inexpensive and quick to implement, but the data is often unreliable and difficult to integrate. On the other hand, complex OEE solutions from industrial automation vendors can take months or years to design and implement, require significant investments, and require large-scale production downtime.

[0082] However, the main disadvantages of relying solely on OEE are the lack of granularity of the metrics provided by the OEE standard and the focus on specific equipment rather than the entire production line. In addition, OEE formulas typically rely on the assumption that the production line or production machine runs the packaging operation around the clock. That is, the OEE calculation assumes that equipment utilization is continuous and constant. Therefore, the OEE calculation needs to be improved and adapted to packaging operations where, for example, a packaging line may run twice a week. A typical OEE calculation applied to such a packaging line may falsely indicate equipment inefficiency because the equipment is idle five out of seven days a week. In this case, the OEE results are obscured by the typical practice in packaging lines (the equipment is not always in use).

[0083] For example, a standard OEE software solution may be useful to senior management to track whether total production has dropped from 85% to 82%, but the metric or score is too vague to provide insight or context into why the score changed. The systems and techniques described in this specification can reduce or eliminate such problems by providing insight and granularity to save time in determining the root cause of production issues, handle events as they occur, notify users when production events occur that need to be handled or resolved, thereby improving production, enabling corrections to be made faster and more accurately, and minimizing downtime or losses. The systems and techniques described herein provide interactive graphical views that facilitate visualization and data interpretation. This allows users to explore and analyze OEE metrics in an intuitive manner, providing context and facilitating the identification of the root causes of production issues. Detailed real-time data collection and storage capabilities, including timestamps for items inspected on the packaging line, enable accurate tracking and analysis of events, enabling proactive decision making and timely corrective actions.

[0084] Complying with serialization regulations is more than just putting a serial number on a package. At the line level, there are complexities such as manual vs. automated lines, existing vs. new lines, and packaging equipment diversity from various original equipment manufacturer (OEM) solutions in the industry. At the site and enterprise level, electronic serialized product data not only needs to match the physical item, but it can also be tracked through the supply chain through multiple channels and handle supply chain events such as returns, damage, recalls, etc. Serialization is now a four-level software stack. Finding a vendor that can provide a full range of bottom-up device and line-level software as well as integrated top-down enterprise and site-level software can be challenging. The systems and technologies described in this specification facilitate a single-vendor approach to address these levels and ensure tight integration of solutions, facilitate data communication, and reduce overall project risk.

[0085] The product serialization and supply chain management software / system described in this specification can reduce risk and enable rapid deployment through solution standardization. This system and technology implements a serialization solution that can meet short-term and long-term needs. The product serialization and supply chain management software / system is scalable as the business grows, regulations change, and the company enters new markets. The product serialization and supply chain management software / system can provide off-the-shelf, configurable products without relying on customized or ordered components. This system and technology implements a modular approach that is productized, configurable, and scalable. It is considered a Good Automated Manufacturing Practice (GAMP) and complies with the International Society of Pharmaceutical Engineers published in 2008 5: Risk-based approach to compliant GxP computerized systems. In the example, the product serialization and supply chain management software / system is a Class 4 configuration product. The design elements of its configurable serialization software can be assembled and re-adjusted to quickly adapt to changing requirements. In contrast, custom solutions are rigid and therefore difficult and costly to modify. When requirements change, it may be necessary to re-engage suppliers and incur expensive rewrite, revalidation and retraining costs - but this is not the case with the product serialization and supply chain management software / system described here. The product serialization and supply chain management software / system can include a solution library. A solution library is a library of pre-packaged modules that meet various packaging scenarios and serialization specifications and support multiple serialization workflows.

[0086] Successful serialization, especially for items produced in large quantities, involves the integration of multiple systems, including enterprise software, printer or label technology, reader systems, and production machinery to apply and verify unique serial numbers. Serialization allows for the identification of products. For many consumer packaged goods, especially those with a long shelf life, individual units are essentially interchangeable. In this case, identifying the product type is sufficient to identify any instance of the product, absent other supply chain considerations. Other products, including perishables and regulated products such as pharmaceuticals, gain a higher level of differentiation by assigning batch or lot numbers. Batch numbers distinguish a group of products (up to a few thousand units) from units in other batches.

[0087] The use of batch numbers allows for some additional controls. Other attributes, such as expiration dates, can be associated with batches. Assuming that batch numbers are captured and reported at points along the supply chain, it is conceivable that products in a batch could be tracked as they move through the distribution system. The designation of batches can also facilitate some controls in the supply chain, including reverse logistics efforts such as recalls.

[0088] In an example, the present systems and techniques are able to identify individual units. To further differentiate between product instances, each item can be assigned a unique serial number. In the past, economics supported such efforts only for high-ticket items such as appliances, consumer electronics, or automobiles. However, as related manufacturing technologies have evolved, assigning numbers to low-cost items has become possible. In parallel with this development, some industries have become subject to regulations to use unit serialization, particularly the pharmaceutical industry. Technologies for storing, communicating, and sharing serial numbers have also evolved to complement the use of these numbers.

[0089] Unique serial numbers can achieve the same metrics as lot numbers, but of course at a more granular level. Serialized objects can be assigned expiration dates, each individual object can be tracked in the supply chain, and recalls can be made based on individual serial numbers. The value of serialization increases when any entity in the supply chain (from manufacturer to distributor to retailer to end user) can read the serial number and identify the object, as supported by the present system and technology. Contemporary serialization efforts often employ standardized methods for attaching serial numbers (via barcodes, 2D symbols, or radio frequency identification (RFID)) and the format of the serial numbers themselves. These standards pave the way for simplified reporting, tracking and tracing, and other improvements in product distribution and sales. The systems and technologies described in this specification facilitate detailed real-time data collection and storage, including time stamps, to ensure accurate tracking and tracing of products using serial and lot numbers. The real-time, cloud-based system collects and analyzes critical data for smooth operation and visualization, enabling seamless reporting, track and trace capabilities, and enhanced supply chain management. The interactive graphical views provided by the system make it easy to visualize and interpret the collected data, allowing users to draw useful conclusions and make informed decisions.

[0090] Sometimes, packaging line data is disconnected. For example, an organization that provides supply chain security and brand protection can gain insight into all aspects of the supply chain. In the example of an organization, network connectivity from enterprise systems to Level 3 packaging site management servers can be observed, but little visibility into Level 2 line managers and Level 1 machine interfaces and vision systems can be seen. Essentially, each line is isolated from each other. The systems and techniques described in this specification can reduce or eliminate such issues.

[0091] In the example, this system and technology enables serialization of pharmaceutical products to support various global regulatory requirements introduced in the past few years. In the example, the real-time supply chain insight system can provide a full range of actionable knowledge in real time to maximize operational excellence. The real-time supply chain insight system collects and stores critical data with minimal effort so that it can be accessed when and wherever it is needed. This allows for smoother operations on the packaging line. It is also a cloud-based environment that is easy to implement and maintain.

[0092] The systems and techniques can provide real-time production visualization showing what is happening in production, including showing active production lines and specific product batches that are running. Fig. 10A shows a sample dashboard that includes an interactive graphical view of an organization's local assets, such as sites, environments, data sources, machines, site servers, and packaging line systems. As a part (such as a carton) is created, Fig. 10AA real-time production visualization in shows progress. For example, 10,000 cartons have been created, and the view refreshes in real time to reflect the additional cartons created, as well as the number of rejected parts (e.g., 1,000 rejected cartons), which is also refreshed in real time. The visualization automatically updates counts from the production line system in real time or near real time (e.g., every minute). The visualization can show counts generated during a production line inspection. This type of real-time visualization can also be streamed to a large television screen or kiosk, and can automatically refresh and scroll through all production lines so that users on site can all see a real-time production view. The systems and techniques described in this article provide detailed real-time data collection and storage, including timestamps, to enable visualization of real-time production progress and quality indicators. The interactive graphical view presents an organization's packaging line system in an easy-to-understand manner and allows real-time monitoring of production activities. Users can track the manufacturing process of parts such as cartons and monitor the number of rejections in real time, enabling them to identify production problems and take corrective actions in a timely manner. Real-time production visualization improves transparency and supports effective decision-making to optimize operations.

[0093] Fast Moving Consumer Goods (FMCG) plants, such as food manufacturers with five production lines, producing 10 to 300 items per minute, and low to medium profit margins, can benefit from standard OEE software solutions. However, these software solutions can be time-consuming and costly to install, and it can take a significant amount of time to accumulate enough data to draw any useful conclusions. In addition, operator training is critical once the OEE tool is in place. Without their support to input downtime reasons, etc., managers can get OEE statistics but not the insights needed to make the most relevant changes. The systems and techniques described in this fact sheet can reduce or eliminate such problems. Data can be collected for a week and then reviewed with the OEE vendor to assess whether the configuration needs to be adjusted. Once the setup looks correct, the tool can be run for at least a month so that a realistic picture can be presented, as OEE can vary by day, employee, and shift. Using the systems and techniques described in this fact sheet, graphs indicating areas of production loss can help prioritize solutions based on impact, cost, and ease of execution. If done properly, the value of this system and technique can be apparent in 3-6 months.

[0094] The present systems and techniques can provide production line management and can further support manual case labeling, centralized palletizing, and parent-child association. Production line management can include commissioning and decommissioning of products, support for printers, barcode scanners, and RFID readers operating in serialized mode, real-time management of user-defined services, real-time process and product quality checks, generation of production and serialization reports, and the ability to run serialized and non-serialized products on the same packaging line. Typically, the performance of packaging and similar production lines is managed based on global consistency goals for production line results. For example, a programmable logic controller (PLC) can be programmed to ensure that all items passing through that production line have consistent results on a certain aspect of the production line.

[0095] However, this management and design hierarchy that targets only global consistency does not allow for rapid deployment of process updates and / or new equipment and makes line modifications costly and time consuming. Furthermore, the steps in a typical process for consumer packaging have historically not been integrated in accordance with this global consistency goal, that is, the steps are unrelated from a management and design perspective, except that each step contributes to the goal of global consistency of line results. This lack of integration has historically produced satisfactory results for many lines and will continue to produce satisfactory results as long as the sole goal of the line is to produce all outputs that are identical. However, if the outputs need to be consistent, but must also be unique, i.e., uniquely tracked, identified, and / or given a series of unique attributes, such as serializing the line outputs, then traditional non-integrated line management and design tools no longer produce acceptable or cost-effective results. In the examples, serialization refers to a unique identifier used on a saleable packaging unit or a processing unit. The serial number can be independent or can be associated with product information, such as a batch, product ID, expiration date, or manufacturing date. The systems and techniques described in this specification can reduce or eliminate such problems.

[0096] The present systems and techniques provide an integrated production line management and design system and method. The systems and methods are integrated in at least the following respects: they allow for unique and highly specific interrelationships between detailed, hierarchical aspects of the systems and methods and between more specific detailed aspects discussed below as items, processes, and flows.

[0097] The system and technology provide supply chain visibility, providing a full range of actionable knowledge in real time that can be used to maximize operational excellence across the supply chain. As products move through the supply chain, they generate event data that drives a multitude of process improvement opportunities. The Real-Time Supply Chain Insight System is an out-of-the-box solution that provides actionable insights and connectivity from the start of deployment. In the example, the Real-Time Supply Chain Insight System provides real-time and historical product data. In the example, the Real-Time Supply Chain Insight System provides enterprise control and visibility for packaging, serialization, anti-counterfeiting and compliance deployments. The Real-Time Supply Chain Insight System visualizes actionable insights across the entire production environment at any time, covering production lines, sites and geographies, and provides an up-to-date graphical view of the environment that is available and accurate. The interactive graphical browser allows the selection of a node and the ability to view the node's health information, including all child nodes and their availability. The Real-Time Supply Chain Insight System enables end-to-end visibility to identify key indicators that can be used to build, measure and improve performance from manufacturing to market. The Real-Time Supply Chain Insight System provides a data-driven, real-time supply chain insight system.

[0098] In some embodiments, the present systems and techniques may include a single point of view system / platform that is a single point of view for monitoring and managing the environment (e.g., packaging site management server, fingerprint system, anti-counterfeiting and product authentication system, and any supported third-party solutions). The single point of view system / platform unlocks previously inaccessible data in the current state to provide visibility and intelligence about systems and operations. The present systems and techniques generate schematic diagrams of sites and production lines, showing the cloud environment and packaging site management server, production line manager, and machine interface and vision system deployed in real time. In addition, the present systems and techniques generate reports that compare production and duration of production lines or batches in real time.

[0099] Fig.11 An example of a single point viewpoint system / platform 1100 is shown. Fig.11 Examples of system architecture components are shown, including product serialization and supply chain management software / system, packaging site management server 1102, product serialization and supply chain management software / system line manager 1104, product serialization and supply chain management software / system machine interface and vision system 1106, and industrial coding traceability software.

[0100] The packaging site management server 1102 provides batch / lot handling operations, packaging work order management, serialization management, and notification to the Level 4 system. The line manager 1104 provides the packaging line operator interface, line setup, and data collection for serialized and non-serialized packaging operations. The machine interface and vision system 1106 provides packaging line vision inspection, equipment communication, and reject tracking on the packaging line.

[0101] exist Fig.11 In the example, the components can perform the following functions. (1) Node (Packaging Site Management Server, Line Manager, Machine Interface and Vision System, Industrial Coding Traceability Software); (2) Real-time Product Serialization and Supply Chain Management Software / System Batch / Lot Production Tracking; (3) Health and Heartbeat provide node status details; (4) Software Management provides accurate version information and recommended update / upgrade paths as well as access to release notes; (5) Diagnostic commands run node-specific diagnostic utilities and return results to a single point of view system / platform; (6) Vault Archive commands create configuration archives and upload files directly to a central storage system; (7) User-defined, company and site graphical scenarios to visualize Deployment, including production browser; (8) Package site management server package work order status to track new, disabled, active and completed work orders; (9) Package batch / lot status to track active, suspended and completed batches / lots, debug and deactivation counts for completed batches / lots, including package site management server notification management; (10) Verify completed batch / lot counts and manually trigger package site management server notifications; (11) After receiving level 4 confirmation, the automated workflow moves from one notification rule to the next notification rule; (12) For each notification file in the rule set, perform Notifications 2.0 for fingerprinting system acknowledgement or negative acknowledgement; (13) Quickly identify one pallet from many that failed to be processed; (14) Notification summary browser allows users to quickly find failed (unable to send by the packaging site management server) or unconfirmed (sent by the packaging site management server but failed to process at level 4) notifications, including administrator controls; (15) Real-time supply chain insights system-specific permissions to limit user access to the browser and commands; (16) Scope policies to limit access to specific sites (aka packaging site management servers); (17) Global settings to collect data from eligible product serialization and supply chain management software / systems 9.0+ packaging site management servers; (18) 21CFR Part 11 Regulatory compliance audit logs, including on-demand information; (19) enabling / disabling data collection on individual packaging site management server site servers; (20) remote procedure call data transfer to speed up data transfer with minimal impact on the packaging site management server (e.g., minutes instead of hours); (21) publishing 5 sets of product serialization and supply chain management software / system dashboards in the online data visualization system; and (22) managing data visualization system user accounts in the online data visualization system. In some examples, dashboards published in the online data visualization system and data visualization system user accounts are managed in the online data visualization system, such as implemented using embedded dashboards. Examples of dashboards are as described above in conjunction with Figure 5-1 0 shown.

[0102] In some examples, the system can start with a single point of view system / platform agent. The single point of view system / platform agent sends information from connected nodes. The single point of view system / platform 1100 is designed to use the same network communication paths that already exist between the packaging site management server 1102, the production line manager 1104, and the machine interface and vision system 1106. The agent is installed on each node in the network to enable operation-related up and down platform communications. The agent is a passive low priority service that does not interfere with the main software or communications of the packaging site management server, production line manager, and machine interface and vision system.

[0103] In some implementations, systems and techniques may include one or more agents 1108, 1110, and / or 1112 on a line manager 1104 and a machine interface and vision system. A centralized agent may be installed on each line manager and machine interface and vision system. The line managers and machine interface and vision systems are not designed to access a centralized storage cloud, but need to connect to a packaging site management server.

[0104] In some embodiments, the agents 1108, 1110, and / or 1112 installed on the line manager and machine interface and vision system use port 9999 by default for communication. The port number can be changed during the initial installation of the agent. In some embodiments, the agent on the packaging site management server system can be installed on each packaging site management server system. The agent on the packaging site management server responds to time intervals (e.g., heartbeats), system alerts or escalations (e.g., health status), command results (e.g., run diagnostics, send notifications), or messages from the underlying agent (e.g., line manager or machine interface and vision system) by publishing HTTPS messages to the single point of view system / platform.

[0105] In some embodiments, the systems and techniques may include a single point view system / platform server certificate (SSL). The single point view system / platform provides a server certificate for deployment. An agent installed on the packaging site management server authenticates the web server using the server-side certificate.

[0106] In the example, the single point of view system / platform is configured to obtain real-time health and status information based on logical groupings of organizations, sites, environments, cloud resources, and data sources. Users with the designer role can perform configuration and publish defined logical groupings (called scenarios). Users with the operator role can approve and manage these scenarios.

[0107] Data sources can be representations of systems that are not directly registered with the Single Point of View system / platform. Data sources are added to the topology to enhance visibility of system interactions. Examples: Enterprise Resource Planning (ERP), Manufacturing Execution System (MES), Warehouse Management Solution (WMS). Site servers can be Single Point of View system / platform resources that are registered with a specific instance of the Single Point of View system / platform. For example, a packaging site management server can be a Single Point of View system / platform resource.

[0108] A cloud can represent a cloud resource registered in a specific instance of a single viewpoint system / platform. For example, a fingerprint system or an anti-counterfeiting and product authentication system can be a registered cloud resource, represented by a suitable cloud icon in the system visualization. Environments can facilitate logical separation between test, stage, or production environments. Creating multiple environments allows for testing and refinement before going into production. An environment can consist of various assets, such as clouds, site servers, and data sources. Defined environments are used to create sites.

[0109] Sites can represent physical locations where products are manufactured, or they can represent larger physical locations broken down into smaller, more manageable components. Examples: Princeton, New Jersey, East New York, West New York. Sites need to be defined to create organizations. Organizations can represent business units in a large company. Organizations are defined to create scenarios. Scenarios can allow real-time health and status information to be displayed through logical groupings of organizations, sites, environments, cloud resources, and data sources. Scenarios are ready to use once they are configured, published, and approved.

[0110] The Single View System / Platform can include security and other administrator functions. This details the logical security functions of the Single View System / Platform. In the example, system access can be restricted through group / permission / user control. Access to the Single View System / Platform can be controlled through a group, permission, and user configuration system. There are three predefined roles in the Single View System / Platform: Administrator, Designer, and Operator. The Administrator role is responsible for managing and maintaining system security. Designers define and configure nodes and assets that can be monitored and managed. Operators can manage, monitor, and handle functions such as the Production Browser, Vault, Scene Management and Viewing, and Enterprise Notifications.

[0111] Groups can have a combination of roles, while individual roles have a list of permissions that can be enabled / disabled to allow strict access control. Individual users are assigned to defined groups. Creation, deletion, and modification of groups and users are managed by users with the Administrator role.

[0112] In the example, system access can be restricted by scope. Single point of view systems / platforms can be further controlled by creating scope policies. Users with the Administrator role can define nodes that can be viewed and managed by groups. For example, if a company has two sites, one group of users can be set to only have access to one site, and another group to only have access to the other site.

[0113] Audit Explorer allows users with an Admin role to view system access and changes made to the system by Admin functions, including login / logout, create / delete users, and security policy updates. Entries include timestamp, change, change initiator, and old / new values ​​if applicable. Users can filter, sort, and export entries to a csv file.

[0114] In the example, the File Storage Utilization section allows users with an Administrator role to monitor a single point of view system / platform storage allocation and usage by category and owner. Users can filter the detailed display of stored documents by multiple parameters such as file format, location, date added, and owner. Once displayed, records can be searched and sorted.

[0115] The single point of view system / platform enterprise notification feature provides users with access to the Notification Rules Browser and the Notification Summary Browser. These two browsers allow users to view and manage Wrapper Site Management Server notifications without having to log into the Wrapper Site Management Server.

[0116] The Notification Rules Browser allows users with the Operator role to search, view, and process preconfigured notification rules for a selected batch. Users can create filters and display notification rules based on multiple parameters such as date added, notification rule status, node, and product. Users can view all preconfigured notification rules for a selected batch. Only ended batches are displayed. Paused or ongoing batches may not be available.

[0117] Once a packaging batch is selected, the notification rules associated with that packaging batch can be retrieved and displayed. Batch data such as product name, batch start and end times, and manufacturer are displayed. In addition, notification rules are displayed in the order in which they are configured. Each notification rule displays the rule name and status. The status indicates where that rule is in the notification life cycle. Notification rules can have the following states: 1) Ready to send; 2) Pending (the notification rule is waiting for the previous notification rule to complete); 3) In progress (the packaging site management server is delivering the message); 4) Sent (the packaging site management server has successfully completed processing of the notification rule); 5) Failed (an error occurred while sending the message from the packaging site management server); 6) Completed (a status set by the user to indicate that processing of the current notification rule has completed).

[0118] Notifications can be submitted. In the example, users can submit notifications in the order they are configured. If multiple notification rules have been configured for a processed batch, only the first notification rule is set to the Ready state. All other notification rules are set to the Pending state. Additionally, a user with permission to execute the Send command can select a notification rule that is in the Ready state and submit it by selecting the Send command. Submitted notification rules enter the In Progress state and then the Sent state if successful. Otherwise, the Failed state can be displayed. After the first notification rule configured for a batch is processed, if a second notification rule has been configured for the batch, the state of the second notification rule is changed to Ready.

[0119] Users can manually update the status of notification rules. Users with permission to execute the "Update Status" command can manually update certain statuses of notification rules. For example, "In Progress", "Complete", and "Failed" can be changed back to "Ready" for resubmission. Log entries are created for all notification status changes. Log entries contain: user who made the change, date / time the change occurred, old value / new value.

[0120] Users can download the notification files generated by each notification rule. The Notification Summary Browser allows users with the Operator role to search and view submitted notification rules. Operator role users are also able to manually update the status of submitted notification rules and download the notification files generated by each submitted notification rule. In some implementations, an integrated anomaly detection and resolution system provides real-time monitoring of system behavior. The anomaly system leverages artificial intelligence and machine learning algorithms to identify and flag deviations from normal system behavior as anomalies. Upon detecting an anomaly, the system initiates an internal investigation process and takes initial corrective action. The anomaly system also generates a detailed report of the anomaly for users with the Administrator or Designer roles to take further action. This enables the platform to maintain high performance and security by identifying and resolving potential issues in a timely manner.

[0121] The single point of view system / platform can include scenarios and custom views. A scenario is a logical grouping of organizations, sites, environments, cloud resources, site servers, and data sources that displays real-time health and status information. Once a user with a designer role publishes a scenario, a user with an operator role can approve or reject the published scenario.

[0122] Users with the Operator role can also set an approved scenario as the default or withdraw it. Approved scenarios that are set as default can be displayed on the dashboard. Users with the Operator role can create personalized views of published scenarios that focus on the areas of most interest in the organization's topology. Once a custom view is created and saved, it can be set as the default view to display on the dashboard. Users with the Operator role can refine published scenarios and custom views by node, upgrade, status, software version, supported versions, and current updates.

[0123] Dashboards (e.g. Figure 1 The dashboard in 132) can display published scenarios or custom views set as default. Users with the operator role can see the following information on the dashboard: 1) Packaging line utilization for each site server along with packaging line details; 2) A graphical overview of the entire topology; 3) A list of all nodes and their status (online / offline); 4) System status (normal, warning, critical) status (online / offline), system messages (e.g., alarms), details of space and CPU utilization for each node; and 5) Software version - actual version versus supported version and current version.

[0124] Users can select diagnostic commands to generate downloadable files of detailed system-level utilization and health information for troubleshooting purposes. Single Point of View System / Platform Vault Browser provides centralized management of production artifacts (e.g., PDFs, drawings) that describe and / or support the manufacturing process. This allows users to save and organize archives, project documents, printer templates, PLC programs, equipment configurations, and other installation files in one secure location. The Vault Browser allows users with operator privileges to perform the following functions:

[0125] Users can upload files of any format. When uploading files, users can associate those files with identification and description information. Each file is also assigned a status (e.g., Draft, Verified, Approved). Users can upload files with the same name and save those files as different versions of the same file. Each file version has associated fields that can be updated. Users can create filters and display files based on multiple parameters such as date added, file status, associated subjects, and file owner. Users can add any applicable comments to each file. Users can add any reference links to related files stored outside the vault.

[0126] Users can modify the fields associated with each file. In addition, Users can view a list of uploaded documents and their associated identifying and descriptive information, including: 1) general information entered when the file was initially uploaded; 2) each version of the file and associated fields; 3) any applicable comments entered by the User for the file; and 4) any reference links to related files stored outside of the vault. Users can download files and view the contents. Individual file versions can also be downloaded. Users can delete uploaded files. Individual file versions can also be deleted.

[0127] The Production Browser allows users with the operator role to monitor production activities by viewing the status of packaging batches and work orders for all sites. Users can create filters to display packaging batches or work orders. The displayed information can be further filtered by multiple parameters, such as node, product, date and status of packaging batch / work order.

[0128] When viewing work orders and packaging batches, the displayed records can be sorted by name and status. Packaging batches have the following statuses: 1) In Progress - the packaging batch is active; 2) On Hold - the packaging batch is on hold; 3) Completed - the packaging batch is ended or closed. Work orders have the following statuses: 1) Ready - the work order has been used and is available on the Packaging Site Management Server; 2) In Progress - the work order has been used to start a packaging batch and the batch is active; 3) On Hold - the packaging batch related to this work order is on hold; 4) Completed - the packaging batch related to this work order is ended or closed, therefore, this work order is completed; 5) Disabled - the work order on the Packaging Site Management Server is disabled and the line manager cannot use it to start a batch; 6) Cancelled - the work order on the Packaging Site Management Server has been deleted. Details of completed packaging batches are available.

[0129] In some embodiments, systems and techniques may include Fig.11 Functions performed by components in the stack. The process starts with the operator list sending and the single point view system / platform receiving the archive command. All commands include a command and a node address. After receiving the archive command, the single point view system / platform performs a "record event audit log and request console". Responses related to the user and status are recorded. If a payload is provided, a file can also be recorded. After completing the "record event", the single point view system / platform sends a command to the node agent (wrapper site management server). The process of sending messages up and down the stack can be similar; however, the command (downward) and the payload (upward) may be different.

[0130] For the real-time supply chain insight system, nodes, production browsers, packaging site management server notification management, administrator controls, and on-demand information are provided. In the example, nodes (e.g., packaging site management servers, production line managers, machine interfaces and vision systems, industrial coding traceability software) include the following: Real-time product serialization and supply chain management software / system batch / lot production tracking; Health and heartbeat provide node status details; Software management provides accurate version information and recommended update / upgrade paths and access to release notes; Diagnostic commands run node-specific diagnostic utilities and return results to the single point of view system / platform. Vault archive commands create configuration archives and upload files directly to the single point of view system / platform vault. User-defined, company and site graphical scenarios are used to visualize deployments.

[0131] In the example, the Production Browser includes the following: Packaging Site Management Server Packaging Work Order Status to track new, disabled, active, and completed work orders; Packaging Batch / Lot Number Status to track active, suspended, and completed batches / lots; and use counts and deactivation counts available for completed batches / lots.

[0132] In the example, the Packaging Site Management Server notification management includes the following: Verify completed batch / lot number counts and manually trigger Packaging Site Management Server notifications; Automated workflow moves from one notification rule to the next upon receiving a Level 4 confirmation; Fingerprint system confirms or unconfirms Notification 2.0 for each notification file in the rule set. Quickly identify one of many pallets that failed to process; Notification Summary Browser allows the user to quickly find failed (Packaging Site Management Server could not send) or unconfirmed (Packaging Site Management Server sent but Level 4 failed to process) notifications.

[0133] In the example, administrator controls include the following: Real-time Supply Chain Insights system-specific permissions to restrict user access to browsers and commands; scoped policies to restrict access to specific sites (aka packaging site management servers); global settings to enable data collection from qualified Product Serialization and Supply Chain Management Software / System 9.0+ packaging site management servers; and 21 CFR Part 11 audit logs to ensure regulatory compliance.

[0134] In the examples, the information on demand (IOD) includes the following: enable / disable data collection on a single packaging site management server site server; remote procedure call data transfer to speed up data transfer with minimal impact on the packaging site management server (e.g., minutes instead of hours); 5 sets of product serialization and supply chain management software / system dashboards published in an online data visualization system, where the data visualization system user account is managed by the online data visualization system. In some examples, the dashboard is an embedded dashboard. In the examples, the dashboard is embedded in a single point of view system / platform web user interface page. In the examples, the dashboard is hosted and accessed externally from a third-party website (e.g., a data visualization system).

[0135] In the example, the dashboard is the IOD dashboard. The IOD dashboard leverages pre-built cross-product data reports to provide insight into production. The IOD dashboard can be viewed through the data visualization system analysis platform. The dashboard can be pre-configured to include global production, packaging batch details, serial number assignments, serial number pool status, and packaging line performance profiles. The pre-configured dashboards are published and easily accessible through a browser on any workstation or mobile device.

[0136] In some embodiments, the visualization may include a production dashboard. For example, the system may provide a production report. The report may include the number of batches processed and items used / discontinued by site, line, product, and packaging level. Users can filter by processing date, site, product, and line. The report may be divided into five sections: site production summary, product production summary, line summary, annual production summary, and production details. For site production summary, the following are displayed: top sites based on the number of batches processed; top sites based on the number of items used; top sites based on the number of items discontinued. For product production summary, the following are displayed: top products based on the number of batches processed; top products based on the number of items used; top products based on the number of items discontinued. For line summary, the following are displayed: top lines based on the number of batches processed; top lines based on the number of items used; top lines based on the number of items discontinued. For annual production summary, the following are displayed: number of processed batches calculated by month for each specified year; number of items used calculated by month for each specified year; number of items discontinued calculated by month for each specified year. For production details, the following are displayed: number of products calculated by site, line, packaging level, and status.

[0137] Single Point of View The system / platform documentation repository contains information about software, hardware, and reference material. The repository consists of the Information Center, Support Center, and Training Center. All user roles have access to the repository. In addition, users can upload applicable files and use a folder structure to manage them.

[0138] The Information Center contains a library of technical documents that include general information, product information, and GAMP information. General information includes: Version Compatibility Matrix: Users are able to determine software version compatibility between components (such as Line Manager / Machine Interface and Vision System) and the Packaging Site Management Server; Blog: Users can access supply chain related blogs; Regulatory: Users can access industry related regulatory information; Webinars: Users can access supply chain related webinars; and White Papers: Users can access industry related white papers.

[0139] Product information includes: Device Drivers: users can access detailed technical guides for configuring IPS printer drivers; Hardware: users can access hardware specifications, certifications, and drawings; Operation Manuals: users can access operation manuals for non-technical users; Release Notes: users can access detailed information about the latest software updates and patches; Setup Manuals: users can access setup manuals for software and device configuration; Solution Briefs: users can access a Packaged Integrated Module (PIM) library with easy-to-follow workflows; Technical Guides: users can access detailed technical guides for configuring IPS blocks and understanding the product; and Vision: users can access detailed technical guides for configuring the Vision tool.

[0140] GAMP information includes: Requirements Traceability Matrix (RTM) / User Requirement Specification (URS): Users have access to User Requirement Specifications and Traceability Matrix; and Verification Qualification (VQ): Users have access to Installation and Operational Qualification documents.

[0141] For example, Support Center contains information related to system maintenance, including case history, renewal information, software, and customer support. Case history enables users to browse open and closed customer support cases and case metrics for the current and last year. Renewal information enables users to track license renewal information. The software enables users to view details of new software versions and patches, and users can also download the latest version. Customer support enables users to send requests to customer service and technical support.

[0142] In the example, the training center contains information related to training courses and videos, including training schedules, unrestricted videos, and subscription videos. Training schedules enable users to view available training schedules and details. Unrestricted videos enable users to view training videos included in their maintenance contract. Subscription videos enable users to view specialized online training after subscribing. Single-view systems / platforms can incorporate AI-driven content discovery and recommendation engines. This feature enhances the system / platform's ability to personalize user experience. Using machine learning and natural language processing algorithms, the engine can analyze users' activity patterns within the platform, including the types of files they access, the nature of the support cases they raise, or the training content they interact with. The engine then uses these patterns to recommend the most relevant and helpful content to each user, including but not limited to technical documentation, tutorials, webinars, white papers, or previously closed support cases. As user activity data accumulates, the recommendation engine can continuously learn and improve its recommendations, thereby improving the accuracy and personalization of user content discovery.

[0143] Some manual solutions, such as having operators fill out worksheets, are low cost and quick to implement, but the data is often unreliable and difficult to integrate. On the other hand, complex solutions offered by industrial automation vendors can take months or years to design and implement, requiring significant investment and large-scale production downtime. Then, once the solution is built, it needs to run for months to collect enough data. There are other boxed kits that provide similar functionality, but the end user needs to design, configure, test, and debug before going into production. The systems and techniques described in this specification can reduce or eliminate such problems. The systems and techniques provide packages with components that can be integrated together to meet specific needs. The real-time supply chain insight system discussed in this specification supports use with other products and therefore does not rely on custom integration.

[0144] The following are some example features of a single point of view system / platform. For example, a single point of view system / platform includes an organizational topology. An organizational topology can be a graphical view of the organization, sites, environments, data sources, and site servers, as well as packaging line systems. A single point of view system / platform includes real-time system status. Real-time status enables on-demand access to status and health information of connected systems (nodes). Real-time status enables determination of system status as available (e.g., out of batch or idle), active (e.g., active batch), or offline. Real-time status enables viewing of system status (maintenance, warning, or critical) and related messages, such as the number of active packaging alarms or system error conditions. A single point of view system / platform includes user-defined views. In a user-defined view, users create personalized views based on the organizational topology and can interact with nodes to get real-time status updates or perform actions. A single point of view system / platform includes online technical documentation. Access to a library of technical documentation, including technical guides, setup manuals, and operation manuals organized by solutions and topics. A single point of view system / platform includes online regulatory updates. Online regulatory updates include established regulations and their impact on the solution. The Single Perspective System / Platform includes GAMP document templates such as VQ, URS, and Traceability Matrix templates for deploying solutions. The Single Perspective System / Platform includes Customer Support Case History. For example, Customer Support Case History is online. This allows the status of open cases for one site or all sites to be checked and closed cases to be reviewed. The Single Perspective System / Platform includes Account Renewal Information. Renewal information includes renewal dates and information on annual fees for support maintenance and / or SAAS (Software as a Service). The Single Perspective System / Platform includes Training Schedules and Videos. For example, upcoming training courses can be found and course descriptions can be reviewed. Unlimited training videos can be viewed. Users can choose to have full access to all training videos.

[0145] Here are some more example features of a single point of view system / platform. For example, a single point of view system / platform includes software downloads. In the example, full and patch installation packages can be downloaded from a secure location. A single point of view system / platform includes secure file storage and sharing. In the example, files are saved in a secure location and only accessible to predetermined individuals. For example, files can be shared with customer support or a project team instead of being shared via email. A single point of view system / platform includes on-demand diagnostics. For example, initiate diagnostics on a remote system and view the results from a different location. The diagnostic results can be sent to customer support for faster assistance. A single point of view system / platform includes scope policies. Create and assign scope policies to restrict user access to specific sites. Even when viewing corporate-level scenarios, users can only see data from permitted sites. A single point of view system / platform includes embedded operating system (OS) security update (KB) status. A list of applied security updates for line-level systems can be viewed. The list is based on the published KB updates for the provided embedded OS systems. A single point of view system / platform includes a vault. Vault enables archives, project documents, printer templates, PLC programs, device configurations or any type of file to be saved and organized in one secure location. Files can be tagged with change control numbers or user-defined tags for faster searching. Reference links can be added to related files stored outside the vault. Single Point of View System / Platform includes Packaging Batch and Work Order Status. Monitor production based on batches or work orders. Filter by status such as Ready, In Progress, Paused, Completed, Disabled or Cancelled. Notes provide details on production status changes. View production quantities for completed batches and work orders (In Service, Deactivated…). Single Point of View System / Platform includes Enterprise Notification Management. In the example, the Packaging Site Management Server notification is initiated manually without logging into the Packaging Site Management Server. Notification Summary Browser enables quick search of failed notifications. Third-party confirmation of processed notifications can be confirmed. Single Point of View System / Platform includes IOD. History can be used to improve the future by leveraging cross-product data to gain insight into production. Dashboards include global production, packaging batch details, serial number assignments, serial number pool status and packaging line performance profiles. The single point of view system / platform includes a customer data pool. The customer data pool allows direct access to a centralized data repository outside of the live solution database. The single point of view system / platform includes serialized and non-serialized system support. In the example, operational intelligence is not limited to serialized systems.

[0146] Here are some more example features of the Single Point of View system / platform. For example, the Single Point of View system / platform includes a roadmap item. In the example, the Single Point of View system / platform includes event subscriptions that allow subscriptions to predefined system events to receive notifications when an alarm is triggered. The Single Point of View system / platform includes user defined alarm policies. Create custom alarm triggers for event subscriptions, "e.g. if the line is down for 15 minutes, then generate an alarm". The Single Point of View system / platform includes alarm categories and priorities. Line level alarms are grouped into categories and priorities are set for each group. Assign user roles that can respond to each group. Alarm triggers are generated based on the alarm priority. The Single Point of View system / platform includes serial number pool monitoring. Serial number pools are monitored across the organization. Check for available serial numbers against a packaging site management server or fingerprint system. The Single Point of View system / platform includes devices added to user scenarios. Production line equipment such as cameras, printers, PLCs are added to the main scenario, providing more detailed information at a glance. The Single Point of View system / platform includes line equipment events and status: Line equipment information is added to the available status information. The single point of view system / platform includes a packaging line log. The line manager log allows line operators to enter information during packaging batches / lots. Supervisors, maintenance and quality personnel can view and comment on the log from their desks. The single point of view system / platform includes document and data retention policies. The platform enables manufacturers to make their line and site operations fully serialization ready, enabling compliance with all existing and future regulations across multiple sites around the world and can follow configured corporate retention policies.

[0147] Here are some more example features of a single point of view system / platform. For example, a single point of view system / platform includes batch record history integration: Serialization and batch history data are integrated into a centralized data storage location. Manual local system data archiving and purge can be eliminated. A single point of view system / platform includes audit trail integration. 21CFR Part 11 is integrated into an organization's centralized data storage. Manual local system data archiving and purge can be eliminated. A single point of view system / platform includes integration utilities for packaged site management servers. Integration of history data from legacy systems. Manual utilities are used to migrate history data from packaged site management servers running software. A single point of view system / platform includes configuration version control. Provides automatic version control of configuration profiles. Software versions are recorded with configuration profiles to provide improved management. A single point of view system / platform includes automatic change detection. Notify line operators of unauthorized changes before a batch is started. Configure policies to approve or deny batch starts by role. Notifications are generated when unauthorized configurations are in production. A single point of view system / platform includes configuration profile management. Configuration profiles are stored in a central repository. Access to archives is controlled to prevent restoration of outdated or unapproved configurations. Archives are created directly into the archive repository as needed. Single Perspective System / Platform includes Software Update Scheduling: Authorized users can schedule software updates to be executed on their local system without the need for emails, downloads, or USB sticks. Stakeholders can be notified of pending software updates. Single Perspective System / Platform includes Import / Export of Device Configuration Settings. Device (e.g., printers, scanners, etc.) settings, firmware, and templates are saved as part of the configuration archive. The scope depends on the features supported by the device. Single Perspective System / Platform incorporates third-party data in analytics. In the example, data is integrated from other sources to get an overview. In the example, the overview identifies patterns that create delays or bottlenecks within the organization. Single Perspective System / Platform includes automatic configuration backups. Configuration backups are created at predetermined intervals, such as at the end of each batch or at a predetermined date / time. This ensures up-to-date backups for faster disaster recovery. Backups are stored differently than configuration archives and have their own retention policies. Single Perspective System / Platform includes Site Database Backups. Site Database backups are scheduled for disaster recovery. The Single Perspective System / Platform includes a spare parts catalog and inventory. This enables people to understand what spare parts are available and where they are located. Part numbers can be quickly identified to order replacement parts. Spare parts catalogs can be updated. The Single Perspective System / Platform includes disk imaging. In the example, create a full disk image to speed disaster recovery. Schedule automatic imaging, or generate disk images on demand. The Single Perspective System / Platform includes virus scan reporting. In the example, perform a virus scan, and view and save a virus scan report. The results are saved with the configuration archive. The Single Perspective System / Platform includes step-by-step recovery walkthroughs.Step-by-step recovery walkthroughs can include documentation and video assistance on restoring different system types. Single Point of View System / Platform includes device-level backup. Device-level backup can include backup settings, firmware, and templates for printers, scanners, PLCs, and other line equipment. Device backup can be used to restore replacement equipment to the same settings as the original equipment. Single Point of View System / Platform includes central packaging master data management. Packaging master data is centrally distributed to sites. Partial master date information is imported from multiple sources for complete definitions. Single Point of View System / Platform includes central packaging work order management. Packaging work orders can be imported, created, scheduled, and released for execution. The status of work orders can be controlled to prevent incomplete work orders from running. Stop or pause requests for active work orders can be issued remotely. Line operators are notified on the local system. Additional features of the Single Point of View System / Platform include enhanced data integrity verification. The system can verify the integrity of serialization and batch history data using a combination of checksums and encrypted graph hashing algorithms. This ensures that data consolidated to a centralized data storage location has not been tampered with during storage, transmission, or processing. This can greatly help ensure the security of audit trail consolidation and eliminate the need for manual archiving and purging.

[0148] The systems and technologies included here include serialization, which can be easily adapted to new requirements while protecting line throughput, data integrity, and system security. Serialization architecture is provided, as well as important considerations and criteria for evaluating potential serialization solutions. There are three main goals when implementing serialization: (1) Ensure the integrity of data as it moves between enterprise, plant, line, and machine levels. (2) Maintain packaging line throughput without costly and time-consuming interruptions. (3) Maintain a secure information technology system.

[0149] Provides two-way communication. Adding serialization technology requires new packaging processes at various sites that should be accommodated by the enterprise information technology (IT) infrastructure. Serialization solutions enable effective communication between the packaging and IT environments. Enabling this two-way communication provides a new control system layer. This new layer acts as a gateway through which data flows. Data management between the enterprise and the packaging line is critical to all serialization initiatives because it protects data integrity at the enterprise level while ensuring integrity throughout the packaging line.

[0150] Total cost of ownership (TCO) includes the cost of software, hardware, system integration, revalidation and production line efficiency, as well as the cost of supporting global serialization promotion. When developing a serialization strategy and controlling TCO, companies can consider the following technical criteria: Productized serialization solutions can be quickly installed after purchase, thereby improving the efficiency and speed of production line setup; Scalable serialization solutions are easy to expand; Configurable software design elements can be assembled and re-adjusted to quickly adapt to changing needs without rewriting code; Turnkey software solutions can effectively handle change control management; Manage communication links between critical levels of backward compatibility between software versions; Use proven standard interfaces to establish open communication between external systems and devices; Reduce deployment time by leveraging previous experience and established use cases rather than a "learn by doing" approach.

[0151] Considerations at specific levels are as follows. At the enterprise level, ERP / MES considerations include: How to manage digital format conversions between the plant and the enterprise? How to minimize network interruptions to ensure packaging throughput? Is a third party responsible for providing the tools necessary to maintain data integrity? If so, what other roles do they play? How to support offline and post-batch operations? Considerations at the plant level (MES) include: How to manage new national specifications? How to manage constant changes in existing legislation? Is a third party responsible for code changes? How easy is it to add / change products in the existing serialization solution? Considerations at the line level (supervisory control and data acquisition) include: Is the packaging line isolated or insulated from changes at the plant and enterprise levels? How does the serialization solution affect line efficiency? Does the serialization solution manage the production line or only the serialization equipment? Considerations at the machine level (PLC and equipment) include: What impact will changes in the equipment have on the production line management system? How many unique human-machine interface (HMI) displays does the serialization solution have? Does the serialization solution actively track the status of items throughout the production line process?

[0152] Supervisory Control and Data Acquisition (SCADA) is a system of hardware and software components used to monitor and control industrial processes, infrastructure, and facilities. SCADA systems collect real-time data from various sensors and devices, provide control commands to remote equipment, and display the collected data to operators for monitoring and decision making. HMI refers to a user interface or graphical interface that allows humans to interact with machines, equipment, or software systems. HMI provides a visual representation of system status, data, and controls, allowing operators to effectively monitor and control the system. HMI can include touch screens, buttons, indicators, and other interactive elements to facilitate user interaction.

[0153] A major consideration between the factory level and the line level is: Which teams are responsible for maintaining communication between each level? Communication can be established using two-way communication as described above. Offline and post-batch operational considerations are: How to manage and support offline, post-batch, rework, QA, and centralized palletizing? In the example, the packaging site management server operates at the factory level with serialized product tracking. In the example, the line manager operates at the line level with serialized product tracking. In the example, the machine interface and vision system operate at the machine level. In the example, the packaging execution system integrates all packaging line information systems, including visual inspection, line management, performance indicators, and serialization. In some embodiments, the systems and technologies can be integrated with Internet of Things (IoT) devices and sensors deployed throughout the supply chain to collect real-time data on various parameters, such as temperature, humidity, vibration, or location. The system can use this fine-grained real-time data to monitor the condition of items in the supply chain, enabling proactive identification and resolution of potential issues that may affect product quality or safety.

[0154] In some embodiments, systems and techniques may include serialized product tracking. Serialization may be performed on a machine, on a production line, off-line, in a factory, or a combination of these. For example, serialization on a machine may include device communications: settings, alarms, counters; fixed and variable text formats; real-time download of printer templates and data; print verification: batch, expiration date; product inspection: tilt, position, presentation, content; component verification and commodity code; real-time product inspection and result release. Serialization on a production line may include program management supervision; number management completed in real time on a packaging line; support for multiple devices in multiple configurations; contain batch numbers and expiration dates as well as global trade item numbers (GTIN) and serial numbers; support multiple data carrying and verification and matching; manage aggregation processes; support manual and automated packaging use cases. Offline serialization may include: ensuring aggregate integrity for all "out-of-batch" use cases; managing rework, quality assurance (QA) sampling, and QA inspections for damaged products; managing central palletizing, pallet reconfiguration, and quality assurance operations; tracking and recording serialized products until the point of notification; managing label printing to replace damaged labels. Serialization in the factory can include various notification triggering methods to support unattended operation; automatic configuration for unattended operation; automatic number conversion for configuration and notification; minimization of packaging line verification when updating IT systems; prevention of packaging line interruptions due to network loss; providing a single IT interface for all packaging lines; and near real-time communication with packaging lines.

[0155] In some embodiments, the machine interface and vision system can include high-speed vision processing and a full set of vision tools for pharmaceutical packaging, which have the following features: dynamic grayscale processing or normalized correlation; user-friendly statistical training process; print verification, label tilt, placement, presentation, content, component verification, commodity code; and tight productized interoperability with line managers. Tight productized interoperability with line managers can achieve the following goals: reduced risk integration between different suppliers; user access control of vision functions and vision; display of operating mode status from a single user interface; viewing of multiple vision inspections from a single interface; single point of user access control and security integrated with active directory; and single point setup of all vision inspections from the line manager at the beginning of a batch.

[0156] In some implementations, the systems and technologies can provide the following benefits and advantages, including: making the right decisions about digital management, ensuring data flow is productized for packaging, ensuring the correct data entering the supply chain, designing use cases through configuration (rather than code development), eliminating the cost risk of integrating random vision technology with production line management software, and expanding and maintaining without system integration. The overall solution is ready to deploy globally, providing consistency across sites and providing a consistent training method for packaging and IT personnel.

[0157] In some embodiments, the machine interface and vision system can provide a broad set of vision tools, including optical character verification (OCV), optical character recognition (OCR), barcode verification (BCV), and print quality verification (PQV), which can supplement general quality inspection functions such as measurement, object presence, shape, defects, quantity, and color. The machine interface and vision system product can include audit logs to ensure process control, quality and regulatory compliance. It also performs equipment setup, recipe-driven workflow, reject station management, and control of intelligent inline devices (printers, barcode scanners, and checkweighers) to ensure integrated quality control.

[0158] The machine interface and vision system can include the following features: Easy to deploy and use; Provides higher accuracy and greater yield due to its "true" OCV function; Excellent visual inspection speed; Can use color and monochrome images in any combination; Advanced performance for single character recognition inspection; One-time font training library; Simplifies training and ensures consistency across all packaging operations because inspections are performed from a single, consistent and intuitive user interface. The machine interface and vision system product specifications are as follows: Supports an unlimited combination of inspection types from a single camera frame; Inspection rate is 3,600 parts per minute (maximum); Up to 4 acquisitions in the basic system; and supports the most diverse cameras on the market and expands to control up to 12 camera ports.

[0159] The embodiments of the subject matter and functional operations described in this specification may be implemented in digital electronic circuits, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in a combination of one or more of them. The embodiments of the subject matter described in this specification may be implemented using one or more computer program instruction modules encoded on a computer-readable medium for execution by a data processing device or for controlling the operation of the data processing device. The computer-readable medium may be a manufactured product, such as a hard drive in a computer system or an optical disk sold through a retail channel, or an embedded system. The computer-readable medium may be acquired separately and then encoded with one or more computer program instruction modules, such as transmitting one or more computer program instruction modules via a wired or wireless network. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, or a combination of one or more of them.

[0160] The term "data processing apparatus" covers all devices, apparatus and machines for processing data, including, for example, a programmable processor, a computer or a plurality of processors or computers. In addition to hardware, the apparatus may also include code that creates an execution environment for the computer program in question, such as code constituting processor firmware, a protocol stack, a database management system, an operating system, a runtime environment, or a combination of one or more of them. In addition, the apparatus may employ a variety of different computing model infrastructures, such as Web services, distributed computing, and grid computing infrastructures.

[0161] A computer program (also referred to as a program, software, software application, script, or code) may be written in any suitable programming language, including compiled or interpreted languages, declarative or procedural languages, and may be deployed in any suitable form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file containing other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to a related program, or in multiple coordinated files (e.g., a file storing one or more modules, subroutines, or portions of code). A computer program may be deployed and executed on a single computer or on multiple computers located at a single site or distributed across multiple sites and interconnected by a communications network.

[0162] The processes and logic flows described in this specification may be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be performed by, and the apparatus may be implemented as, a special purpose logic circuit, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0163] Processors suitable for executing computer programs include, for example, dedicated microprocessors. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include or be operably coupled to receive data from or transmit data to or both of one or more mass storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks. However, a computer does not have to have such a device. In addition, a computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device (such as a universal serial bus (USB) flash drive), to name a few. Devices suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices, including, for example, semiconductor storage devices, such as EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0164] To provide interaction with a user, embodiments of the subject matter described in this specification may be implemented on a computer having a display device (e.g., an LCD (liquid crystal display) display device, an OLED (organic light emitting diode) display device, or other monitor) for displaying information to the user, and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices may also be used to provide interaction with a user; for example, feedback provided to the user may be any suitable form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any suitable form, including acoustic, voice, or tactile input.

[0165] A computing system may include a client and a server. The client and the server are usually far from each other and usually interact through a communication network. The relationship between the client and the server is generated by a computer program running on a corresponding computer and having a client-server relationship with each other. The embodiments of the subject matter described in this specification can be implemented in a computing system, which includes a back-end component, such as a data server, or includes a middleware component, such as an application server, or includes a front-end component, such as a client computer with a graphical user interface or a web browser, through which a user can interact with the implementation of the subject matter described in this specification, or any combination of one or more such back-ends, middleware or front-end components. The components of the system can be interconnected by any suitable digital data communication form or medium (such as a communication network). Examples of communication networks include local area networks ("LAN") and wide area networks ("WAN"), the Internet (e.g., the Internet) and peer-to-peer networks (e.g., self-organizing peer-to-peer networks).

[0166] Although this specification contains many implementation details, these details should not be interpreted as limitations on the scope of what is claimed or may be claimed, but rather as descriptions of features of specific embodiments of the disclosed subject matter. Certain features described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. In addition, although features may be described as working in certain combinations or even initially claimed, in some cases one or more features in the claimed combination may be cut out of the combination, and the claimed combination may be directed to a sub-combination or a variant of a sub-combination. Therefore, unless otherwise expressly stated, or unless the knowledge of a person of ordinary skill in the art clearly indicates, any feature of the above-described embodiments may be combined with any other feature of the above-described embodiments.

[0167] Similarly, although the operations are depicted in a particular order in the figures, it should not be understood as requiring that the operations be performed in the particular order shown or in sequential order, or that all of the operations shown be performed, to achieve the desired result. In some cases, multitasking and / or parallel processing may be advantageous. In addition, the separation of various system components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated into a single software product or packaged into multiple software products.

[0168] Thus, certain embodiments of the present systems and techniques have been described. Other embodiments are within the scope of the following claims. For example, the steps recited in the claims can be performed in a different order and still achieve the desired results. Example

[0169] Although the present application is defined in the appended claims, it will be appreciated that the invention may also (additionally or alternatively) be defined according to the following examples:

[0170] Example 1: A method comprising: capturing data about items as they move through a supply chain, wherein the data includes event data identifying a particular item at a particular location in the supply chain at a particular time; analyzing data to generate information as at least a portion of the item moves through the supply chain; and A visualization of information is provided that can be used to identify one or more changes to be made in at least a portion of a supply chain to improve at least a portion of the supply chain.

[0171] Example 2: The method of Example 1 further comprises identifying the item by using computer image processing to generate an electronic fingerprint from a captured image of a marking on the item.

[0172] Example 3: A method according to Example 1 or Example 2, wherein the data about the items includes counts of used and discontinued items for a time snapshot and / or related to a portion of a supply chain, and wherein the counts are obtained from inspection data collected on the production line by sensors installed on the production line.

[0173] Example 4: A method according to any of the preceding examples, wherein obtaining comprises: receiving serialization data for the item from a computer located at a production facility, a packaging facility, a distribution facility, or a combination thereof; and Item authentication data and end-to-end item tracking data are received from computers throughout the supply chain via a global communications network.

[0174] Example 5: The method according to any of the preceding examples, wherein the analysis comprises: analyzing data about at least a portion of an item moving through a supply chain; and Analyze historical data about an item that has moved completely through another portion of the supply chain, an item that was discarded before moving completely through the supply chain, or both.

[0175] Example 6: A method according to any of the preceding examples, wherein the analysis includes generating information including deactivation information, serial number pool information, packaging line performance information, and packaging batch information.

[0176] Example 7: A method according to any of the preceding examples, wherein providing includes sending different dashboards to display (i) deactivation events for sites, products and packaging lines, (ii) serial number pool status and serial number allocation, (iii) packaging line utilization and performance, and (iv) packaging batch / lot details (including settings, run time, events, counts and deactivation reasons).

[0177] Example 8: The method according to any of the preceding examples further includes identifying trends and potential threats based on predetermined thresholds associated with at least one of the deactivation information, the serial number pool information, the packaging line performance information, and the packaging batch information.

[0178] Example 9: A method according to any of the preceding examples, wherein providing includes generating an interactive graphical view for visualizing data related to a serial number pool, wherein the serial number pool represents a serial number inventory, and the serial number inventory is obtained from a government agency or a trading partner, and the visualization includes a serial number pool visualization including count data of assigned serial numbers, used serial numbers, available serial numbers, deactivated serial numbers, serialization formats, serial number count thresholds based on site, manufacturer, product, and packaging, and a visual indicator for indicating whether the available serial numbers are above or below the serial number count threshold, wherein the serial number count threshold is a predetermined value set by a customer.

[0179] Example 10: The method of any of the preceding examples, wherein providing includes sending different sets of information about a particular item to two or more of a manufacturer, a packager, a distributor, a retailer, and an end consumer.

[0180] Example 11: A method according to any of the preceding examples, wherein providing includes generating an interactive graphical view of the organization's sites, environments, data sources, machines, site servers, and packaging line systems.

[0181] Example 12: A method as in any of the preceding examples, wherein the interactive graphical view includes representations of cameras, printers, barcode scanners, and sensors installed on the organization's production lines.

[0182] Similar operations and processes as described in Examples 1 to 12 may be performed in a system including at least one process and a memory communicatively coupled to at least one processor, wherein the memory stores instructions that, when executed, cause at least one processor to perform the operations described in any one of Examples 1 to 12. In addition, a non-transitory computer-readable medium may also be implemented that stores instructions that, when executed, cause at least one processor to perform the operations described in any one of Examples 1 to 12.

Claims

1. A method comprising: capturing data about an item as it moves through a supply chain, wherein the data includes event data identifying a particular item at a particular location in the supply chain at a particular time; analyzing said data to generate information as at least a portion of said items move through said supply chain; and A visualization of information is provided that can be used to identify one or more changes to be made in at least a portion of the supply chain to improve the at least a portion of the supply chain.

2. The method of claim 1 further comprising identifying the item by generating an electronic fingerprint from a captured image of a marking on the item using computer image processing.

3. The method according to claim 2, wherein: The data about the items includes counts of used and discontinued items for a time snapshot and / or associated with a portion of the supply chain, and wherein the counts are obtained from inspection data of the production line collected by sensors installed on the production line.

4. The method according to claim 2, wherein: The acquisition includes: receiving serialization data for the item from a computer located at a production facility, a packaging facility, a distribution facility, or a combination thereof; and Item authentication data and end-to-end item tracking data are received from computers throughout the supply chain via a global communications network.

5. The method of claim 2, wherein the analyzing comprises: analyzing data regarding at least a portion of the items moving in the supply chain; as well as Historical data is analyzed regarding another portion of the item that has completely passed through the supply chain, historical data for items that were discarded before completely passing through the supply chain, or both.

6. The method of claim 1, wherein the analyzing comprises generating information including out-of-service information, serial number pool information, packaging line performance information, and packaging batch information.

7. The method of claim 6, wherein the providing includes sending different dashboards to display (i) outage events for sites, products, and packaging lines; (ii) serial number pool status and serial number allocation; (iii) packaging line utilization and performance, and (iv) packaging batch / lot details including settings, run time, events, counts, and outage reasons.

8. The method of claim 6, further comprising identifying trends and potential threats based on predetermined thresholds associated with at least one of the outage information, the serial number pool information, the packaging line performance information, and the packaging batch information.

9. A method according to any one of claims 1-8, wherein the providing includes generating an interactive graphical view for visualizing data related to a serialization number pool, wherein the serialization number pool represents a serialization number inventory, and the serialization number inventory is obtained from a government agency or a trading partner, and the visualization includes a serialization number pool visualization, the serialization number pool visualization including count data of assigned serialization numbers based on site, manufacturer, product and packaging, used serialization numbers, available serialization numbers, deactivated serialization numbers, d serialization formats, a serialization number count threshold, and a visual indicator for indicating whether the available serialization numbers are above or below the serialization number count threshold, wherein the serialization number count threshold is a predetermined value set by a customer.

10. The method of any one of claims 1-8, wherein the providing comprises sending different sets of information about a particular item to two or more of a manufacturer, a packager, a distributor, a retailer, and an end consumer.

11. The method of any one of claims 1-8, wherein said providing comprises generating an interactive graphical view of an organization's sites, environments, data sources, machines and site servers, and packaging line systems.

12. The method of claim 11, wherein the interactive graphical view includes representations of cameras, printers, barcode scanners, and sensors installed on a production line of the organization.

13. A system comprising: A data processing device comprising at least one hardware processor; and A non-transitory computer-readable medium encoding instructions configured to cause the data processing device to perform the method of any one of claims 1-12.

14. A non-transitory computer readable medium encoding instructions operable to cause a data processing apparatus to perform the method of any one of claims 1-12.

Images