Dynamic batch limit validation method
The data conformance tracking system addresses the inefficiencies in compliance monitoring by automatically associating data points with time-specific restrictions, ensuring accurate and efficient regulatory compliance in dynamically changing environments.
Patent Information
- Application Number
- JP2021536326
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-07-22
- Filing Date
- 2019-12-20
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2039-12-20
AI Technical Summary
Existing methods for monitoring compliance in data collection for manufactured products are tedious and prone to errors, often failing to meet regulatory requirements for data integrity and accuracy, particularly in dynamically changing regulatory environments.
A data conformance tracking system that automatically associates data points with corresponding restrictions based on valid time intervals, allowing for real-time analysis and alerting, and seamlessly updates limits to ensure compliance with current regulations without manual intervention.
Ensures accurate and efficient compliance monitoring, reducing the risk of product wastage and resource misuse by applying the correct restrictions at the right time, thus enhancing data integrity and regulatory adherence.
Smart Images

Figure 0007579785000001 
Figure 0007579785000002 
Figure 0007579785000003
Abstract
Description
[Technical field]
[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to U.S. Provisional Application No. 62 / 782,920, filed December 20, 2018, entitled “DYNAMIC BATCH CONTROL VERIFICATION,” and U.S. Provisional Application No. 62 / 876,990, filed July 22, 2019, entitled “DYNAMIC BATCH CONTROL VERIFICATION,” both of which are incorporated herein by reference in their entireties.
[0002] (Technical field) FIELD OF THE DISCLOSURE This disclosure relates generally to monitoring and analyzing suitability in data collection, and more specifically to dynamically applying restrictions to collected data. [Background technology]
[0003] Manufactured products, such as pharmaceuticals, food and beverage products, and other products produced through chemical and other processes, often must meet certain specifications, e.g., regulatory specifications, internal specifications, etc. There may be specifications regarding limitations on certain components of the product (e.g., impurity percentages, chemical composition, identity characteristics, etc.). Product specifications may depend on various factors, e.g., the type of product, the target market, environmental impact, cost, etc. For example, a pharmaceutical product may have different limitations than a candy bar, and a product for children may have different requirements than a product for adults. During a production or experimental run, a company tests various chemical ingredients and compositions against a product batch or run to evaluate whether those ingredients fall within certain limitations that correspond to the specifications or parameters.
[0004] Applicable limits may be set by a company (e.g., to limit costs, ensure purity, desired performance), by a regulatory agency (e.g., to ensure safety, limit environmental impact), or by a third party stakeholder (e.g., an investor). For example, a company may set limits for various parameters as targets during manufacturing of a product. As another example, a regulatory agency sets limits for various parameter values to ensure that each batch of a product is of sufficient quality. A batch meets established targets and / or regulations when the parameter values of the batch are within the prescribed limits. Limits may change over time due to changing regulatory regimes, product changes, etc., such that batches analyzed at different times may have different applicable limits.
[0005] Regulatory agencies impose strict requirements on companies to manufacture products that meet certain standards and restrictions (e.g., based on health, wellness, and human, animal, and environmental safety.) To meet these requirements, companies must monitor their products and processes at all stages of development and collect, organize, and analyze data related to the imposed requirements.
[0006] As an example, the Food and Drug Administration (FDA) of the U.S. Department of Health and Human Services requires that product sampling and testing plans meet a set of standards to ensure that drug batches meet appropriate specifications and statistical quality control criteria as a condition of their approval and release. For example, drug manufacturing must use methods, equipment, and control procedures evaluated as adequate to maintain drug identity, strength, quality, and purity.
[0007] In addition, regulatory agencies have imposed certain requirements on data management to ensure data integrity. Data integrity requires that data be complete, consistent, and accurate. Especially with the increasing use of computerized systems, many regulatory schemes require that there are some controls in place on data to prevent unauthorized access or modification. For example, the Drug Good Manufacturing Practices (CGMP) released by the FDA require measures to ensure data protection for any computerized system. For example, the CGMP guidance recommends that there be records of any data changes made, previous entries, who made the changes, and when the changes were made.
[0008] Traditional methods of monitoring compliance in data collection require tedious manual entry and comparison of data or require programming skills. For example, companies often organize data into Excel spreadsheets and manually enter the data and applicable restrictions associated with the time the data was collected. Such manual entry is difficult as batches and these applicable restrictions can be numerous. Furthermore, such manual entry often does not meet government mandates for data integrity because the data cannot be properly tracked and stored.
[0009] The information contained in this Background section of the specification, including any references cited herein and any explanation or discussion thereof, is included for technical reference purposes and should not be considered as subject matter by which the scope of the present invention is limited. [Prior art documents] [Patent documents]
[0010] [Patent Document 1] U.S. Provisional Application No. 62 / 782,920 [Patent Document 2] U.S. Provisional Application No. 62 / 876,990 Summary of the Invention [Problem to be solved by the invention]
[0011] The technology disclosed herein generally relates to a system for tracking the relevance of collected data. [Means for solving the problem]
[0012] In one embodiment, a method for validating data by a data conformance tracking system is disclosed, the method includes the steps of receiving at least one data point from a computer element, the data point corresponding to data collected from sampling of at least one parameter during a batch run of a product and including time stamp data, determining constraint information corresponding to the at least one parameter, the constraint information including at least one constraint associated with the at least one parameter and having an associated valid value range, storing the at least one data point and the constraint information, receiving an analysis request from a user device, analyzing the stored constraint information and applying the constraints to selected data points, and displaying an analysis output.
[0013] In another embodiment, a method for updating dynamic limits in a data compliance tracking system is disclosed, the method includes the steps of receiving a new limit and a change reason associated with the new limit from a first user device, sending an approval request to a second user device, where a user of the second user device has a satisfactory privilege level, receiving approval of the new limit from the second user device, determining a validity interval for the approved new limit, generating a new limit entry, where the new limit entry includes the new limit and the associated validity interval, storing the new limit entry in memory, and updating a status of the previous limit stored in memory to obsolete.
[0014] In yet another embodiment, a method is disclosed for providing select data conformance feedback to a user in real time, the method including receiving a data value from a batch run of a product, determining that the data value is approved, determining that the approved data value is associated with an active alert, the active alert being for a restriction or rule associated with the data value, evaluating conformance of the approved data value with the restriction or rule, and sending an alert notification to the user indicating conformance of the approved data value with the restriction or rule based on the evaluation.
[0015] This Summary is provided to introduce in a simplified form a selection of concepts further described herein below. This Summary is not intended to identify key elements of the invention or to delineate the scope of the invention. A more extensive expression of the features, details, utilities, and advantages of the invention is provided in the following specification of various embodiments of the invention, as illustrated in the accompanying drawings, and as defined in the appended claims. [Brief description of the drawings]
[0016] [Figure 1] FIG. 1 is a block diagram illustrating an example of a data compatibility monitoring system. [Diagram 2] 2 is a schematic block diagram of a computing device that may represent one or more components of the system of FIG. 1. [Diagram 3] 2 is a flow diagram illustrating a method for analyzing data based on corresponding constraints within the data suitability monitoring system of FIG. 1. [Figure 4] 2 is a flow diagram illustrating a method for updating limit values in the data compliance monitoring system of FIG. 1. [Figure 5A] FIG. 2 is a diagram illustrating an example of a database structure of the system of FIG. [Figure 5B] FIG. 2 is a diagram showing another example of a database structure of the system of FIG. 1. [Figure 6] FIG. 13 illustrates a user interface that allows selection between different restriction categories. [Figure 7] FIG. 13 illustrates a user interface for adjusting standard limit data. [Figure 8] FIG. 13 illustrates a user interface for adjusting target control limit data. [Figure 9] FIG. 13 illustrates a user interface that provides additional information regarding adjustments to either the specification limit data or the target control limit data. [Figure 10] FIG. 13 illustrates a user interface for adjusting the constraint status displayed for either the specification constraints or the target control constraints. [Figure 11] FIG. 13 illustrates a user interface displaying changing restrictions over time and for different markets. [Figure 12] FIG. 1 illustrates a user interface displaying a control chart for a single parameter. [Figure 13] FIG. 13 illustrates a user interface displaying a single batch of information used to generate data for one or more control charts. [Figure 14] FIG. 13 illustrates a user interface displaying a segmented control chart of a single parameter showing changes in constraints over time. [Figure 15] 15 illustrates a user interface displaying limit data changes for the parameters displayed in the segmented control chart of FIG. 14 in tabular form. [Figure 16] FIG. 13 illustrates a user interface displaying a control chart with a single market restriction. [Figure 17] FIG. 1 illustrates a user interface displaying a process capability chart for a single market. [Figure 18] FIG. 13 illustrates a user interface displaying a control chart with restrictions for multiple markets. [Figure 19]FIG. 13 illustrates a user interface display for adjusting specification limits displayed on a control chart. [Figure 20] 1 is a flow diagram illustrating a method of batch filtering. [Figure 21] 1 is a flow diagram illustrating a method for restriction filtering. [Figure 22] FIG. 1 illustrates a user interface displaying an interactive control chart with a graphic displaying metadata associated with a data point. [Diagram 23] 1 is a flow diagram illustrating a method for sending an alert to a user. [Figure 24] FIG. 13 illustrates a user interface displaying a home screen that provides access to a user's alert preferences. [Diagram 25] FIG. 25 illustrates the user interface of FIG. 24 displaying a home screen with an Alerts tab open for customizing alerts. [Figure 26] FIG. 13 illustrates a user interface displaying an Analysis tab that allows a user to customize one or more rules and / or constraints for a selected parameter. [Figure 27] FIG. 27 illustrates the user interface of FIG. 26 displaying an Analysis tab with customized rules and specification limits for selected parameters. [Figure 28] FIG. 27 illustrates the user interface of FIG. 26 displaying an Alerts tab that allows a user to customize one or more alerts for a selected parameter. [Figure 29] FIG. 1 illustrates an example alert sent to a user by the system of the present disclosure. [Diagram 30] FIG. 25 illustrates the user interface of FIG. 24 displaying a home screen with a quick access charts tab open for quick access to subscribed charts. [Diagram 31] FIG. 13 illustrates a user interface displaying an analysis screen for viewing information specific to a subscribed chart. [Diagram 32] FIG. 23 illustrates the user interface of FIG. 22 displaying an interactive control chart with a graphic displaying alert metadata associated with a data point. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0017] The disclosed systems and methods provide a mechanism for associating multiple constraints with data collected for one or more parameters (e.g., chemical composition, tracked values, etc.) for multiple batches or products, etc. As an example, during a product run or experiment (e.g., pharmaceutical development), several batches of product can be produced through one or more chemical processes. The batches can have one or more constraints associated with them, such as purity constraints, desired ranges for certain chemical properties (e.g., alcohol percentage, pH, temperature), and / or ranges of chemical composition at various stages of the process. Data points or values for the batches can be collected via instruments (e.g., temperature probes, pH probes, flow meters, pressure sensors, spectrophotometers, etc.) connected to the process line and / or via automatic or manual sampling during the process. The values can be entered into a database either automatically and / or manually by a user.
[0018] A batch value or data point typically includes one or more corresponding limits or thresholds (e.g., maximum, minimum) that are acceptable (that is, values that fall within certain regulatory requirements or are required for accuracy according to a product standard or recipe). The data conformance tracking system of the present disclosure automatically associates the corresponding limits with values or data points, such that data points and values are validated against the given limits regardless of when the validation is reviewed or performed.
[0019] In some embodiments, the data conformance tracking system includes a batch or data point database and a limit database. The data point or value database receives and stores collected data points or values for various parameters or characteristics. The data point database can receive information directly from a computer or other device (e.g., an instrument) or from a user who inputs values into the system. The data points can include value metadata about the circumstances surrounding a particular sampling. For example, the metadata can include a timestamp indicating the date and / or time that the sample or batch resulting in the collected data point was tested. The limit database stores limit values for various parameters for applicable validity time intervals (e.g., effective time windows). The validation window or validation interval includes a start time / date for a particular limit and, optionally, an end date or ongoing time / date for a particular limit. The system of the present invention enforces non-overlapping validity date ranges for a given parameter (or combination of parameter, sub-product, and market). Where limit values may change over time, the limit database may collect and store various limit values and their applicable validity time intervals without affecting the storage or data integrity of the data points in the various databases.
[0020] Given the structure of the data point database and the constraint database, an analysis can be performed within the system of the present invention to determine the suitability or analyze the success of one or more batches corresponding to a desired outcome without separate identification of the applicable constraints in effect at the time of the run. For example, when analyzing the data, the system of the present invention automatically applies the defined constraints to batches produced during the corresponding constraint validation window.
[0021] The system of the present invention can replace old or invalid restrictions with new restrictions as they are established, helping to prevent inadvertent destruction of batches based on outdated information. Such new restrictions can have various effective time windows in which they can be applied. The system of the present invention can apply the new restrictions to batches produced within the new time windows. The system of the present invention can automatically apply restrictions based on the time the batch was produced and chart this relationship between batches and restrictions in a graphical format.
[0022] In one embodiment, when retrieving data for analysis or other output to a user, the data compliance tracking system retrieves the desired data points for analysis, retrieves the corresponding value metadata including time stamp information, and then analyzes the limit database to determine the applicable limit values for each data point stored in the data point database. The limit values are then applied to each data point or value, and these values can be graphically displayed in a control chart (or other statistical tool) or otherwise analyzed with the exact limit applied, such that data corresponding to the effective limit at the time the batch was processed is analyzed, rather than the current limit in force for the particular parameter or characteristic. This allows for an accurate reflection of whether the parameter or characteristic is and / or was valid at the time of production, rather than analyzing values under standards that are not in effect at this time. Thus, the user can determine whether the collected data is or was within the prescribed limits and therefore complies with the regulations imposed at the time of data collection. This helps alleviate problems associated with conventional systems that do not monitor and update limits resulting in unnecessarily wasted product, wasted resources, etc.
[0023] The disclosed system allows for filtering of both batches and restrictions, and displays the appropriate batches and applicable restrictions to the user. There may be several batches of a product produced throughout the manufacturing process. Each batch may have several restrictions associated with it. For example, a batch may have a number of associated parameters (e.g., temperature, pH, toxicity, etc.), and each parameter may have a number of restrictions. For example, each parameter may have different restrictions based on existing authorities (e.g., company or one or more regulatory agencies), co-products (e.g., packaging or concentration), restriction date range or status, market, and a variety of other factors (e.g., user-defined factors that may affect the parameter value). The system of the present invention can quickly and efficiently filter the batches and restrictions to apply the desired restrictions to the appropriate batches.
[0024] The disclosed system provides a verifiable means for complying with data integrity regulations associated with product quality control. The system of the present invention links data and context to facilitate and satisfy government requirements for data processing for quality control while maintaining data integrity and verifiable / trackable changes to various constraints and data values. Furthermore, the system of the present invention provides a way for average users without computer programming expertise to organize and analyze data in a consistent, reliable, and valid manner, avoiding user errors associated with manual entry spreadsheets (e.g., Excel). The system of the present invention does not require user configuration, rather, users can create process definitions, enter regulatory and target control constraints, enter batch data, and simply monitor compliance.
[0025] Additionally, the system of the present invention allows the user to receive automatic alerts when a batch is run and limits are exceeded or based on other user set preferences, such as when new data values are entered. This alert functionality allows the user to closely monitor processing, helps ensure that batches are running properly, and allows the user to correct problems in processing as they occur, rather than after the fact.
[0026] The system of the present disclosure will now be discussed in detail with reference to the figures. FIG. 1 is a block diagram illustrating an example of a data compatibility tracking system 100. The system 100 includes a user device 106 that can communicate with one or more instruments 108a-n. The system of the present invention can also include a server 102 and one or more databases 110 that can communicate with the user device 106 and / or the instruments 108a-n. Each of the various components of the compatibility tracking system 100 can communicate with each other directly or indirectly, such as via a network 104. Thus, each of the components can send and receive data from other components in the system. In many instances, the server 102 can act as an intermediary for some of the components in the system 100.
[0027] Network 104 can be virtually any type or combination of types of communication systems that transmit data via either wired or wireless mechanisms (e.g., WiFi, Ethernet, Bluetooth, cellular data, etc.). In some embodiments, certain components in the adaptive tracking system 100 can communicate via a first mode (e.g., Bluetooth) and others can communicate via a second mode (e.g., WiFi). In addition, certain components can have multiple transmission mechanisms and be configured to communicate data in two or more ways. The configuration of network 104 and the communication mechanisms of each of the components can be varied as desired.
[0028] The server 102 includes one or more computing devices that process and execute information. The server 102 may include its own processing elements, memory components, etc., and / or may communicate with one or more external components (e.g., other memory storage) (examples of computing elements that may be included in the server 102 are disclosed below with respect to FIG. 2). The server 102 may also include one or more server computers interconnected with each other via a network 104 or another communication protocol. The server 102 may host and execute some of the processes performed by the system 100.
[0029] The user devices 106 can be any of various types of computing devices, such as, for example, a smartphone, a tablet computer, a desktop computer, a laptop computer, a set-top box, a gaming device, a wearable device, etc. The user devices 106 provide output to and receive input from a user. For example, the user devices 106 can receive restrictions and collected data from a user and output compliance information, alerts, and other notifications to the user. The type and number of user devices 106 can be varied as desired.
[0030] The instruments 108a-n can be any type of instrument or technology used to create, sample, and test products. For example, the instruments 108 can be any instrument used to perform an assay (e.g., a cell counter, a mass spectrometer, an NIR probe, etc.). As another example, the instruments 108 can be sensors that can monitor one or more parameters (e.g., temperature, pressure, pH, electrical, motion, etc.).
[0031] The one or more databases 110 can be any database linked to a user. For example, the database 110 can be an internal database used directly by a company, or the database 110 can be an external database. For example, a company can have access to an external database associated with a regulatory agency. For example, the database can be associated with the U.S. Food and Drug Administration, the European Medicines Agency, the Veterinary Medicines Agency, the World Health Organization, the Health Products Regulatory Agency, or a similar regulatory agency. The database 110 stores compliance information, including specification limits for specific chemical ingredients or compositions, processes, etc.
[0032] A schematic block structure of a computing device that may be used with the system 100 or integrated into one or more of the components of the system 100 is shown in Figure 2. For example, the server 102, the user device 106, the appliances 108a-108n, and / or the database 110 may include one or more of the components shown in Figure 2 and use one or more of these components to perform one or more of the operations disclosed in the methods 200, 250, 500, and 550. With reference to Figure 2, the computing device 150 may include one or more processing elements 152, an input / output interface 154, a network interface 156, one or more memory components 158, a display 160, one or more external devices 162, and a power source 164. Each of the various components may communicate with one another via one or more buses, wireless means, or the like.
[0033] Processing element 152 is any type of electronic device capable of processing, receiving, and / or transmitting instructions. For example, processing element 152 can be a central processing unit, a microprocessor, a processor, or a microcontroller. In addition, it should be noted that select components of computer 150 can be controlled by a first processor and other components can be controlled by a second processor, and that the first and second processors may or may not communicate with each other.
[0034] Memory component 158 is used by computer 150 to store instructions for processing element 152 as well as data such as collected data points (e.g., batch data), time information, limit values, etc. Memory component 158 can be, for example, magneto-optical storage, read-only memory, random access memory, erasable programmable memory, flash memory, or a combination of one or more types of memory components.
[0035] Display 160 provides visual feedback to a user and may optionally operate as an input element to enable a user to control, operate, and calibrate various components of computing device 150. Display 160 may be a liquid crystal display, a plasma display, an organic light emitting diode display, and / or a cathode ray tube display. In embodiments in which display 160 is used as an input, display 160 may include one or more touch or input sensors, such as capacitive touch sensors, resistive grids, etc.
[0036] I / O interface 154 allows a user to input data into computer 150, as well as providing input / output for component 150 to communicate with other devices (e.g., server 102, appliances 108a-n, other computers, speakers, etc.). I / O interface 154 may include one or more input buttons, a touch pad, etc.
[0037] The network interface 156 provides communication between the computer 150 and other devices. For example, the network interface 156 allows the server 102 to communicate with the instruments 108a-n over the network 104. The network interface 156 includes one or more communication protocols, such as, but not limited to, WiFi, Ethernet, Bluetooth, etc. The network interface 156 may also include one or more hardwired components, such as a Universal Serial Bus (USB) cable. The configuration of the network interface 156 varies depending on the type of communication desired and can be modified to communicate via WiFi, Bluetooth, etc.
[0038] External device 162 is one or more devices that can be used to provide various inputs to computer device 150, such as a mouse, microphone, keyboard, trackpad, etc. External device 162 can be local or remote and can be varied as desired. Power source 164 can be any power source (e.g., wall power, battery, etc.) that enables computer 150 to function.
[0039] 3 is a flow diagram illustrating a method for analyzing data based on corresponding constraints in the data compatibility tracking system 100. The method 200 begins at operation 202, when the server 102 receives one or more data points or values. The data points may correspond to data collected from a test or sample of a particular batch of product (e.g., pharmaceutical product). Typically, the batch sample or test is parameter specific, i.e., the sampling is based on one or more parameter values of the batch, such as, for example, temperature, pH, concentration of a particular substance or impurity, viscosity, viability, hardness, dissolution, etc. In another example, a tester may test multiple parameters in one sampling. The collected data may include one or more parameter values and may include metadata associated with the context of the sampling. 13, the batch data 350 may also include a batch ID number or name 352 (e.g., identifying the batch to which the value applies), timestamp information 354 (e.g., the time and / or date corresponding to the time and / or date the batch was sampled or created), a batch status 356, and any applicable co-products 358 or markets 360. The batch data 350 may include a reference URL 362 or attachments 364 to provide additional information / results regarding the batch.
[0040] The batch data 350 can be manually entered into the system 100 by a user or can be automatically uploaded to the system 100 as it is collected. For example, values can be detected via one or more of the instruments 108a-n of the system 100. As an example, a thermometer can be used to detect and input temperature values of a particular batch sample. One or more of the instruments 108a-n can be in communication with the server 102 and can transmit the collected batch data to the server 102 directly or through the network 104. The data values can be received directly from the instruments 108a-n or from a computing device or storage in communication with the instruments 108a-n or can receive information from the instruments 108a-n (e.g., via a bulk data upload). Timestamp information can also be recorded directly by the instruments 108a-n when the values are recorded and uploaded to the server 102 directly or through the network 104. Alternatively, a computing device in communication with the instruments 108a-n can record the time the data values were collected and upload the timestamp information to the server 102. In yet another example, timestamp information for when the batch data is uploaded (eg, indicating the time the batch was entered into the system) may be entered into the system 100 automatically or manually.
[0041] After operation 202, the method 200 proceeds to operation 204 where the server 102 determines restriction information. The restriction information may relate to validity criteria set by a regulatory agency, thresholds set by a user, and the like. For example, a regulatory agency or a user may set maximum values, minimum values, or ranges for one or more parameters that correspond to a safe or acceptable product for a particular market. Such maximum values, minimum values, or ranges are restrictions. If the parameter value exceeds the maximum value, falls below the minimum value, or falls outside the range set by the regulatory agency and / or user, the parameter value does not comply with the restrictions imposed by the regulatory framework or the user. However, if the parameter value falls below the maximum value, above the minimum value, or falls within the range set by the regulatory agency and / or user, the parameter value complies. The restriction information may also be product specific in the case that different quality attributes may be applicable depending on the product. In this manner, the restriction information may be based on various factors, such as, for example, clinical experience with a particular product.
[0042] The restriction information may be entered by a user or may be retrieved from one or more databases 110. As an example, the restriction information may be entered by a user via a user device 106. The user may interact with a user interface, such as the interface 300 shown in FIGS. 6-19 and 22. The user may select a restriction category 302, such as a standard 304 or a goal 306, as shown in FIG. 6, for example. The standard 304 may be defined by a regulatory body and the goal 306 may be defined by a user, or may be based on statistics, recipes, or objectives. For example, the specification 304 limit may change in response to a regulatory body's determination of safety or environmental friendliness (e.g., setting a minimum limit value). The specification 304 limit may be related to a product (e.g., controlling ingredients listed behind a drug product). As an example, the specification 304 limit may change based on changes in raw materials. As another example, the specification 304 limit may be set for a parameter in a process based on process development, validation studies, and / or FDA submission.
[0043] On the other hand, the target 306 limits can be set by the user based on the user's goal objectives. Alternatively, the target 306 limits can be based on statistics indicating typical values (e.g., average values) for a particular parameter. For example, the target 306 limits can be control limits statistically derived from baseline batches or previous experience. The target 306 limits can be process related (e.g., controlling the operating range of an actual manufacturing process). The target 306 limits can extend over multiple batches. The target 306 can often be changed more quickly than the specification 304 limits.
[0044] As shown in Figures 7 and 8, both the specification 304 and the target 306 can be defined by both upper and lower limits, whereby the limits are defined by ranges. However, it is contemplated that the specification 304 and the target 306 can be defined by either minimum or maximum values. The specification 304 and the target 306 can include various unit operations or sub-categories 308 (e.g., Extended, N-1, Prod, Harvest, ProA, VI, CEX, AEX, VF, UF / DF, FF, BOS, among others, as shown in Figure 7). As shown in Figures 8-11, each sub-category 308 includes a particular parameter 310. For either the specification 304 or the target 306, the user can select a parameter 310 to adjust the limits associated therewith. The user can enter the specification 304 limits based on limit data collected from the database 110, or the system 100 can be configured to automatically pull limit data from the database 110. A user may also enter goal 306 limits based on user preferences (e.g., goals) or statistical data obtained from database 110. Alternatively, system 100 may be configured to automatically pull statistical data from database 110 and apply it to goal 306 limits.
[0045] After operation 204, the method 200 proceeds to operation 206. In operation 206, the system 100 stores the collected data and constraint information. This information may be stored in a separate and organized manner. For example, the system 100 may store the data in a table. As an example, the system of the present invention stores the data and constraint information in various storage databases or systems. FIG. 5A illustrates an example of a storage system 270 of the system 100. As shown, the storage system 270 includes a data point storage or value database 272 and a constraint storage database 274. The data point storage database 272 stores data points (e.g., batch data) collected for one or more parameters. In the embodiment illustrated in FIG. 5A, the data point storage system 272 includes a number of data points 275a-g collected for the parameter temperature. The data points 275a-g include a parameter value 276 and a timestamp 278. In this example, the temperature value 276 is recorded in degrees Celsius and the timestamp 278 indicates both the date and time the value was sampled. The timestamp information can be determined automatically based on the time the value was entered into storage, when the value was collected, when the batch to which the value corresponds was run, and the like.
[0046] The restriction storage database 274 stores restriction values for various valid time intervals 280 for one or more parameters 310. In the embodiment shown in FIG. 5A, the restriction storage database 274 includes multiple restriction entries 285a-h for the parameter temperature. In the illustrated example, each restriction entry 285a-h includes a valid value range 286 having minimum 282 and maximum 284 temperature values in Celsius, and an associated valid time interval 280. The restrictions (e.g., value range 286) may vary across the valid time interval 280. As shown, there are no overlapping valid time intervals 280 such that a time interval (e.g., a single date) does not have more than one restriction entry 285a-h (or, in this example, more than one value range 286).
[0047] 5B illustrates another example of a storage system 600 of the system 100. As shown, the storage system 600 includes a batch database 602 and a restriction database 604. The batch database 602 stores batch data associated with various batches 606. The batch database 602 can be a single database or can be split across several databases. As shown, the batch database 602 includes a batch identification database 602a and a batch value database 602b. The batch identification database 602a allows for identification of the batch 606 based on an identifier (e.g., letters, numbers, etc.), an applicable market 608, and a production date 610. As shown, three batches 606 having identifiers B101, B102, and B103 are stored in the batch database 602. Each batch 606 has an associated market 608 and production date 610. As shown, batch 606B101 was manufactured on February 1, 2018 at 1:55 PM and is associated with the US market 608, batch 606B102 was manufactured on February 8, 2018 at 11:06 AM and is associated with the European market 608, and batch 606B103 was manufactured on February 15, 2018 at 4:54 PM and is associated with the US market 608.
[0048] The batch value database 602b may be associated with the batch identification database 602a and may include one or more parameters 612 of each batch 606, as well as a recorded value 614 for each parameter 612. As shown, the batch value database 602b includes the parameters 612 temperature and pH, and their respective values 614. As shown, each batch 606 (e.g., B101, B102, B103) has a recorded temperature and pH value.
[0049] The limit database 604 stores limit data for one or more parameters based on various valid time intervals. The limit database 604 can be a single database or can be split across several databases. As shown, the limit database 604 includes a specification limit database 604a and a target control limit database 604b. The specification limit database 604a can include various specification limit entries 616a-g. As shown, the specification limit entries 616a-g include a valid from date 620, a valid to date 622, a parameter 612, a limit category 624, a type 628, a lower limit 630, and an upper limit 632. The specification limits can vary based on the limit category 624. The limit category 624 can include a particular market (e.g., as shown), a co-product, or any broad category that may affect the limit (e.g., product type, equipment used, test environment, etc.). In the illustrated example, the specification limits are applicable for the parameters 612 temperature and pH and for the US and European markets. The type 628 can indicate an issuing authority. For example, a type 628 release can be required by a regulatory body, such as the FDA. As another example, a type 628 action can be issued internally, such as by a company. A specification constraint can have a lower limit 630 value, an upper limit 632 value, or both (e.g., a constraint range).
[0050] The target control limit database 604b can include various target control limit entries 618a-e. As shown, the target control limit entries 618a-e include a valid from date 620, a valid to date 622, a parameter 612, a limit category 624, and a limit value 634. The target control limit can vary based on the limit category 624 in the same manner as described above with respect to the standard limits. In the illustrated example, the target control limits are applicable to the parameters 612 temperature and pH and for the US and European markets. The limit value 634 can include a lower limit value, an upper limit value, or both (e.g., a limit range). For example, as shown, the limit value 634 includes values for a lower control limit (LCL), a lower warning limit (LWL), a lower inner limit (LIL), an upper inner limit (UIL), an upper warning limit (UWL), and an upper control limit (UCL).
[0051] After operation 206, the method 200 proceeds to operation 208 where the system 100 receives an analysis request, which may be a request for validation of the collected data. For example, a user may want to know if a particular batch complies with sampling time specifications and / or targets. To determine if the batch complies, the user submits the analysis request via the user device 106. The analysis can be virtually any type of relationship between the collected data points and associated constraints, such as a chart request. For example, the user may select a parameter 310 (e.g., temperature) and request that the system 100 plot the parameter data points against the associated constraints in a graphical plot known as a control chart 314, as shown in FIGS. 12, 14, 16, and 18. As another example, the user may request other outputs, such as overlaid line plots, box and whisker plots, bar plots, etc. For example, the user may request that various specification constraints be plotted on such outputs.
[0052] After operation 208, method 200 proceeds to operation 210, where server 102 analyzes the stored data points and restrictions to apply applicable restrictions to the selected data points. As an example, server 102 may filter one or both of the stored data points (e.g., batch data) or restriction data based on a user selection, as discussed in more detail below with respect to FIGS. 20 and 21. As another example, with respect to FIG. 5A, system 100 may use storage system 270 to map restrictions to data points 275a-g based on time information. In this example, system 100 automatically correlates each data point 275a-g with its corresponding restriction entries 285a-h, such as by associating a valid time interval 280 with a timestamp 278. For example, the system of the present invention may analyze the timestamp to determine the applicable valid time interval, and then apply the restriction to each data point with reference to the restrictions corresponding to the applicable valid time interval. In this manner, the constraint database can act as a lookup table for the data value database when retrieving an analysis, ensuring that the correct constraints are applied to the data compared to relying on user-entered constraints at the time of analysis.
[0053] In this manner, when data points 275a-g are associated with restriction entries 285a-h, system 100 can then determine if data points 275a-g matched the time of recording (or apply other analysis). For example, data point 275a has a timestamp 278 of 1:55 PM on February 6, 2018. This timestamp 278 corresponds to valid time interval 280 1 / 18-3 / 3 / 18 because date 2 / 6 / 18 is within this range. This valid time interval 280 then corresponds to restriction entry 285a. In this manner, system 100 can determine that data point 275a is correlated to restriction entry 285a with value range 286 between 4.5°C-5.5°C. The temperature value 276 of data point 275a is 5.2°C, which falls within value range 286 4.5°C-5.5°C of restriction entry 285a. Because data point 275a falls within value range 286 of restriction entry 285a, system 100 will determine that data point 275a was in compliance when it was recorded or collected on 2 / 6 / 18 at 1:55 PM.
[0054] As another example, data point 275c and data point 275d both recorded the same temperature value 276 of 5.5° C. However, in this example, one of these data points 275c-d is in compliance and the other is not, as compliance may vary depending on the applicable restrictions in force at the time the data was recorded. In this example, data point 275c was recorded on 5 / 3 / 18 at 3:04 PM and falls within the valid time interval 280 3 / 4 / 18-6 / 4 / 18 corresponding to restriction entry 285b having a value range 286 of 4.4° C.-5.4° C. Data point 275d was recorded on 8 / 22 / 18 at 12:26 PM and falls within the valid time interval 280 7 / 16 / 18-10 / 21 / 18 corresponding to restriction entry 285d having a value range 286 of 4.6° C.-5.6° C. The 5.5° C. temperature value 276 falls within the constraints of constraint entry 285d, which has a value range 286 of 4.6° C.-5.6° C., but falls outside the constraints of constraint entry 285b, which has a value range 286 of 4.4° C.-5.4° C. Thus, data point 275d meets its corresponding constraint entry 285d and data point 275c does not meet its corresponding constraint entry 285b.
[0055] In another example, data point 275e recorded a temperature value 276 of 4.8° C. at 4:54 PM on 10 / 22 / 18. This data point 275e falls within a valid time interval 280 10 / 22 / 18-12 / 1 / 18 that corresponds to a restriction entry 285e having a value range 286 of 4.8° C.-5.7° C. In this example, both the date of the timestamp 278 and the parameter value 276 match the end values of the valid time interval 280 or the limit value range 286. For example, the date 10 / 22 / 18 of data point 275e matches the first date 10 / 22 / 18 that starts the valid time interval 280 of restriction entry 285e. This date is considered to fall within the valid time interval 280 of restriction 285e, which causes restriction entry 285e to be applied to data point 275e. The temperature value 276 of data point 275e, 4.8°C, meets the minimum value 282 of 4.8°C in the constraints of constraint entry 285e. The minimum value 282 is considered to be within the constraints, which causes the temperature value 276 of data point 275e to be within the constraints. The system 100 would therefore determine that data point 275e was in compliance with the recorded time.
[0056] The valid time interval 280 shown in this example is an interval of several months, although generally any time frame can be used. For example, the valid time interval 280 could span several hours, days, or years. Additionally, although the constraints shown in this example are value ranges 286, it is contemplated that the constraints could be a single value, such as a minimum or maximum threshold.
[0057] As yet another example, with reference to FIG. 5B, the system 100 can map restrictions to batches using the storage system 600. The arrows shown in FIG. 5B represent an example mapping of batches to restrictions. The system 100 can first identify applicable batches 606 (e.g., based on user selection) based on batch identification information (e.g., as shown in the batch identification database 602a). For example, the system 100 can identify the batches 606 based on the batch identifier (e.g., B101, B102, B103), the batch market 608 (e.g., United States, Europe), and / or the batch production date 610. In the illustrated example, the system 100 identifies the batch 606 B101, which was produced on February 1, 2018 at 1:55 PM and is associated with the United States market 608.
[0058] Once the system 100 has identified the applicable batch 606, the system 100 may then associate the batch 606 with its applicable parameters 612 and values 614 (e.g., as shown in batch value database 602b). For example, as shown, batch 606B101 is mapped to parameter 612 temperature having a value 614 of 5.27 based on identifier B101, as indicated by arrow 636a. Batch 606B101 is also mapped to parameter 612 pH having a value 614 of 7.8 based on the same identifier B101, as indicated by arrow 636b. At this stage, the batch 606 is associated with an identifier, market 608, production date 610, parameter 612, and parameter value 614, although it is contemplated that the batch 606 may be associated with other metadata based on the context surrounding the batch 606 as well.
[0059] The system 100 can map the batch 606 to one or more respective constraints based on various factors that associate constraints with the batch 606. For example, the mapping can be based on the batch production date 610, the market 608, and / or the parameters 612. For example, as shown, the batch 606B101 is mapped to various target constraint entries 618b, d in the target control constraint database 604b, as indicated by the arrows 638a, b. As an example, the batch 606B101 is mapped to the target control constraint entry 618b, as indicated by the arrow 638a. The batch 606B101 is mapped to the target control constraint entry 618b because the batch 606B101 production date 610 falls within a valid time interval defined by the valid from date 620 and the valid to date 622, and the market 608 and parameters 612 match the constraint category 624 and parameters 612 of the target control constraint entry 618b. Batch 606B101 manufacturing date 610 February 1, 2018 falls within the validity time interval defined for target control limit entry 618b, which has a validity start date 620 of January 1, 2018 and a validity end date 622 of February 5, 2018. The US market 608 and temperature parameters 612 also match the limit category 624 (US market) and parameter 612 (temperature) of target control limit entry 618b. Thus, system 100 determines that batch 606B101 is associated with limits 634 LCL 5.4, LWL 5.5, LIL 5.6, UIL 5.8, UWL 5.9, and UCL 6.0. The temperature value 614 5.27 associated with batch 606B101 falls within the LCL-UCL range of 5.4-6.0, outside the LWL-UWL range of 5.5-5.9, and outside the LIL-UIL range of 5.6-5.8. Thus, the system 100 can determine that batch 606B101 complies with the control limits but does not comply with the warning and inner limits.
[0060] As shown, batch 606B101 is also mapped to target control constraint entry 618d, as indicated by arrow 638b. In this example, batch 606B101 is mapped based on production date 610 and parameter 612. Batch 606B101 is mapped to target control constraint entry 618d because batch 606B101 production date 610 falls within the valid time interval defined by valid from date 620 and valid to date 622, matching parameter 612. As shown, target control constraint entry 618d is parameter 612pH that matches parameter 612pH from batch value database 602b. Batch 606B101 production date 610 02 / 01 / 2018 falls within the valid time interval defined for target control constraint entry 618d, which has a valid from date 620 of 01 / 01 / 2018 and a valid to date 622 of 02 / 05 / 2018. The target control limit entry 618d has only one control limit associated with it. The control limit 634 range for the target control limit entry 618d is 7.1-8. The pH value 614 of 7.8 associated with batch 606B101 falls within this range. Thus, the system 100 can determine that batch 606B101 is in compliance with the applicable control limits.
[0061] As shown, batch 606B101 is also mapped to various specification constraint entries 616b, c, e, and f in specification constraint database 604a, indicated by arrows 640a, b, c, and d. In this example, system 100 matches (or filters) by production date 610, parameter 612, and market 608. System 100 could filter first by parameter 612, second by production date 610, and third by market 608, or system 100 could filter in any other order. In one example, system 100 filters first by parameter 612. In this example, system 100 could search specification constraint database 604a for any constraints related to one parameter 612 associated with batch 606B101, temperature. As shown, specification constraint entries 616a-d all relate to temperature.
[0062] Next, in this example, the system 100 can filter these specification restriction entries 616a-d by the manufacturing date 610. The system 100 can search these specification restriction entries 616a-d for valid from dates 620 and valid to dates 622 that include the manufacturing date 610 of February 1, 2018 for batch 606B101. In this example, the system 100 determines that the specification restriction entries 616a-c all include the manufacturing date 610 of February 1, 2018. The specification restriction entry 616a has a valid from date 620 of January 1, 2018 without a valid to date 622. The absence of a valid to date 622 means that the restriction is currently applicable (e.g., valid until the present). In this case, February 1, 2018 is within the date range from January 1, 2018 to the present. This is also the case for the specification restriction entry 616c, which has the same date range. Standards restrictions entry 616b has an effective start date of January 1, 2018 and an effective end date 622 of February 5, 2018, which also includes February 1, 2018.
[0063] In this same example, the system 100 may continue to filter the specification constraint entries 616a-c by market 624. The system 100 searches for markets 624 that match the market 608 of the batch 606B101. The market 608 of the batch 606B101 is the United States. As shown, the specification constraint entries 616b, c are both associated with the market 624, the United States. As shown, the arrow 640a maps the batch 606B101 to the specification constraint entry 616b and the arrow 640b maps the batch 606B101 to the specification constraint entry 616c. Thus, two specification constraints are associated with the parameter temperature of the batch 606B101. The two specification constraint entries 616b, c associated with the batch 606B101 are associated with two different types of constraints 628. Specification limit entry 616b is associated with type 628 release and specification limit entry 616c is associated with type 628 action. Specification limit entry 616b has a lower limit 630 value greater than 5.10 and no upper limit 632 value (e.g., indicating the limit is a minimum). The temperature value 614 of 5.27 associated with batch 606B101 is greater than 5.10 indicating batch 606B101 complies with the applicable release limit for parameter temperature. Specification limit entry 616c has a lower limit 630 value greater than or equal to 5.5 and an upper limit 632 value less than 6.0 (e.g., indicating the limit is a range). The temperature value 614 of 5.27 associated with batch 606B101 is less than the lower limit value 630 greater than or equal to 5.5, causing the temperature value 614 to fall outside the limit range. Thus, batch 606B101 does not comply with the applicable action constraints for the parameter temperature.
[0064] The same processing method can be performed on other parameters 612 associated with batch 606. For example, the same filtering process can be performed on parameter 612 pH associated with batch 606B101. Following the same processing sequence, system 100 can search specification limit database 604a for any constraints related to parameter pH. As shown, specification limit entries 616e-g all relate to pH.
[0065] Next, in this example, the system 100 can filter these specification limit entries 616e-g by production date 610. The system 100 can search these specification limit entries 616e-g for a valid from date 620 and a valid to date 622 that include the production date 610 of February 1, 2018 for batch 606B101. In this example, the system 100 determines that specification limit entries 616e,f encompass the production date 610 of February 1, 2018. The date February 1, 2018 falls within the date range of January 1, 2018 - February 5, 2018 for specification limit entry 616e, and the date range of January 1, 2018 to present for specification limit entry 616f. The date February 1, 2018 does not fall within the date range of February 6, 2018 to present for specification limit entry 616g, so specification limit entry 616g is removed and will not be considered further.
[0066] In this same example, the system 100 can then filter the specification limit entries 616e,f by market 624. The system 100 searches for markets 624 that match the market 608 United States for batch 606B101. As shown, specification limit entries 616e,f are not associated with any market 624. In this case, the system 100 can determine that there is a match between batch 606B101 and specification limit entries 616e,f based on the production date 610 and parameters 612. As shown, arrow 640c maps batch 606B101 to specification limit entry 616e and arrow 640d maps batch 606B101 to specification limit entry 616f. Thus, two specification limits are associated with the parameter pH for batch 606B101. The two specification limit entries 616e,f associated with batch 606B101 are associated with two different types of limits 628. Specification limit entry 616e is associated with type 628 release and specification limit entry 616f is associated with type 628 action. Specification limit entry 616e has a lower limit 630 value greater than or equal to 7.05 and an upper limit 632 value less than or equal to 8.00. The pH value 614 of 7.8 associated with batch 606B101 falls within the limits range, indicating that batch 606B101 complies with the applicable release limits for parameter pH. Specification limit entry 616f has a lower limit 630 value greater than or equal to 7.25 without an upper limit value 632. The pH value 614 of 7.8 associated with batch 606B101 is greater than 7.25, indicating that batch 606B101 complies with the applicable action limits for the parameter pH.
[0067] 5A and 5B, the system 100 can use a database as a lookup table to coordinate the data points or batch data to their respective constraints. In another embodiment, the system 100 can use an algorithm in conjunction with the database to link the constraints to the batch. For example, the algorithm can execute a process flow to populate the data that is correlated in the chart.
[0068] After operation 210, the method 200 proceeds to operation 212, where the system 100 outputs the analysis or other analysis related to the analysis request. For example, the system 100 may output a display graph showing the association between the constraints and the data points and / or a conformance determination (i.e., whether the data point is within the associated constraint). This information may be output in the form of a chart or table. For example, the information may be output in a graphical format as shown in FIGS. 12, 14, 16-19.
[0069] FIG. 12 illustrates an example of a control chart 314 for a single parameter 310. In this example, the parameter 310 Temperature (° C.) is shown with various data points (e.g., labeled MAB_001-MAB_020) collected from different batches 318. Two different types of limits associated with these data points are also shown on the graph as lines, both above and below the data points. Although two types of limits are displayed in this example, it is contemplated that only one limit can be displayed or more than two limits can be displayed. The different limits displayed can correspond to one or more target limits, one or more specification limits, a specific issuing authority (e.g., company or regulatory body), a specific sub-product, a specific market, etc. As shown in FIG. 12, a first limit is displayed with a valid value range 324 defined by the space between a minimum line 320 and a maximum line 322. In this example, the minimum line 320 represents a lower warning limit (LWL) and the maximum line 322 represents an upper warning limit (UWL). A second limit is shown having a valid value range 330 defined by the space between the minimum line 326 and the maximum line 328. In this example, the minimum line 326 represents the lower control limit (LCL) and the maximum line 328 represents the upper control limit (UCL). In this case, both displayed limits are the same for all data points and the limit lines 320, 322, 326, 328 extend across the entirety of the chart. Although only two limits, the warning limit and the control limit, are shown, other limits are contemplated. As an example, another limit can be displayed, such as an inner limit having a lower inner limit (LIL) and an upper inner limit (UIL). Such limits, LWL, UWL, LCLmUCL, LIL, and UIL, can fix the control chart limits, especially when the data distribution is not normal and the control limits are not symmetrical about the mean value.
[0070] In the example shown in FIG. 12, the temperature data points fall within the minimum and maximum lines 320, 322, or within the valid value range 324, and between the minimum and maximum lines 326, 328, or within the valid value range 330. Thus, the data points are within the respective limits and the batch 318 is compliant with respect to the temperature parameter 310. As shown in the key 332 next to the chart 314, the rule violations 334 result in the data points being displayed with a different shape (e.g., diamonds in this example), although other physical distinctions between the rule violations and other points are also possible, such as different colors (e.g., red vs. black). The rule violations 334 mean that the data points are not within the limits. In other words, the data points are above the maximum value (e.g., above the maximum value line 322 or the maximum value line 328) or below the minimum value (e.g., below the minimum value line 320 or the minimum value line 326). However, in this example, all of the data points are within both constraints, thereby indicating no rule violation 334 (and all of the data points have the same shaped circle in this case).
[0071] FIG. 14 shows an example of a segmented control chart 316 for a single parameter 310. A segmented chart 316 or multiple constraint charts can occur when the applicable constraints of a parameter change over time. In FIG. 14, the control chart 316 contains the same data points from batch 318 shown in FIG. 12 and the same two constraint types are plotted. However, in this example, the values of both constraint types changed when batches 318 MAB_011-MAB_020 were collected. In this example, the constraint lines 320, 322, 326, 328 do not extend across the entire chart, instead, there are two sets of constraint lines or segments, 336, 338, reflecting the change over time from the constraints from a first segment 336 (having valid value ranges 324a, 330a) to the constraints in a second segment 338 (having valid value ranges 324b, 330b). In other words, one or more of the chart axes may be modified to be extended to incorporate the additional range indicated by the changed constraints.
[0072] For example, continuing with reference to Figure 12, batches 318MAB_001-MAB_010 have a first set of constraints as indicated by line 336, one constraint having a valid value range 324a between a minimum line 320a of about 21.7°C and a maximum line 322a of about 22.2°C, and another constraint having a valid value range 330a between a minimum line 326a of about 21.6°C and a maximum line 328a of about 22.3°C. Batches MAB_011-MAB_020 have a second set of constraints as indicated by line 338, one constraint having a valid value range 324b between a minimum line 320b of 22.7°C and a maximum line 322b of 23.3°C, and another constraint having a valid value range 330b between a minimum line 326b of 22.55°C and a maximum line 328b of 23.45°C. In this example, all of the data points for batches 318 MAB_001-MAB_010 are within both valid value ranges 324a, 330a of the first set of constraint lines 336, indicating that all of batches 318 were in compliance with regulations at the time batches 318 were sampled. However, not all of the data points for MAB_011-MAB_020 are within the second set of constraint lines 338. The data points for batch 318 MAB_015 are below both minimum constraints indicated by lines 320b and 326b, and therefore are not within valid value ranges 324b or 330b. The data points are displayed as different shapes (diamonds) (or different colors, e.g., red) to indicate these rule violations 334. In this case, all of batches 318 except batch 318 MAB_015 were in compliance with the regulations that were in place at the time batches 318 were sampled. On the other hand, batch 318MAB_015 did not comply with the regulations that were in effect at the time it was sampled as indicated by rule violation 334. Although only two segments are shown in the illustrated segmentation chart, reflecting two different limit values across two different valid time intervals, more than two segments reflecting different limit values across different valid time intervals are contemplated.
[0073] Conventional tools cannot plot values with different constraints as shown in FIG. 14. Instead, two separate analysis plots must be run, one with a first batch of values with a first constraint and a second with a second batch of values with a second constraint. However, these two charts take a long time to generate, are inefficient, and do not provide the user with a holistic assessment of the parameter's performance compared to the single multiple constraint chart shown in FIG. 14. This type of multiple constraint analysis is possible due to the reference relationship between the values and the constraints, allowing a separate evaluation of the values compared to the constraints and / or applying the constraints on the back end of the plot.
[0074] FIG. 15 illustrates, in tabular form, the changing restriction data for each segment 336, 338 shown in the segmentation control chart 316 of FIG. 14. The first row illustrates the first segment 336 and the second row illustrates the second segment 338 displayed in the segmentation control chart 316. The rows include the relevant restriction information for each segment 336, 338, such as the effective start date 376, restriction category 374, status 394, and value 382. As shown, the effective start date 376 for the first segment 336 is from October 1, 2018. The first segment 336 restriction has been marked as obsolete, meaning that the restriction is no longer applicable to the batch data currently being collected. The next segment 338 restriction is marked as current and has an effective start date 376 of November 7, 2018. The second segment 338 renders the previous segment 336 obsolete, meaning that the effective start date of the first segment 336 is a date before the effective start date 376 of the second segment 338. In other words, the first segment 336 has an effective start date of November 6, 2018, a date before the effective start date of November 7, 2018 of the second segment 338. The effective time interval of the first segment 336 is October 1, 2018 to November 6, 2018, and the effective time interval of the second segment 338 is November 7, 2018 to the present. With respect to the segmented control chart 316 of FIG. 14, all of the batches 318 associated with the first segment 336 (e.g., MAB_001-MAB-010) were collected some time between October 1, 2018 and November 6, 2018, and all of the batches 318 associated with the second segment 338 (e.g., MAB_011-MAB_020) were collected on or after November 7, 2018, when the temperature parameter limit value was changed.
[0075] The format of the output can be adjusted based on user preferences. For example, a user may wish to view the output for a single market. Restrictions can vary depending on the market. For example, the United States may have different regulations than Europe. A batch may comply with the regulations of one market but not a different market. As shown in FIG. 16, data points are shown in the diagram with respect to the restrictions imposed at the time in the European market. The same restrictions apply to each batch 318 labeled BDS_001-BDS_017 (as indicated by the single displayed segment), indicating that each batch 318 was sampled within the same valid time interval. In this case, three types of restrictions are displayed. Two of the restrictions shown have a value range, and the third restriction shown has an upper (or maximum) value. For a data point to comply with the third restriction, the data point must be below the upper limit value. One constraint has a value range 324 with a minimum line 320 and a maximum line 322, another constraint has a value range 330 with a minimum line 326 and a maximum line 328, and a third constraint has a maximum line 340. In this case, the data points are all within the value ranges 324, 330 and below the maximum line 340, thereby making them all compliant with the European regulations at the time. As shown, a graph icon 342 labeled "USA" is located just below the European market chart. In this example, a user can select the USA icon 342 to view the same data points against one or more constraints imposed at the time on the US market.
[0076] Alternatively, several market restrictions and the performance of a particular characteristic or parameter in those markets can be displayed on the same chart. For example, as shown in FIG. 18, the control chart 314 can include restrictions 340a,b for two or more markets. In this example, both European and US market restrictions 340a,b are shown. In this case, the restrictions 340 shown are ceilings, the US imposed restrictions 340b are approximately 2% and the European imposed restrictions 340a are approximately 3%. In this way, the user can ensure compliance with the applicable markets that the user plans to enter with the tested product. In the example shown, the data points must be below the ceilings to be in compliance. All of the data points are below the European ceiling line 340a and have a release restriction of 3.0. In other words, all of the data are in compliance with this restriction for the EU market. However, the data points associated with batch 318BDS_018 are placed above the US ceiling line 340b. In other words, batch 318BDS_018 is not suitable for the US market with the upper release limits of 2.0. Batch 318BDS_018 is suitable for the European market but not for the US market.
[0077] 17 illustrates another chart format that can be output by the system 100. In this example, data is displayed in a single market (EU) process capability chart 400. Such a process capability chart 400 shows the variability of a process compared to an acceptable operating range. The process capability index provides a statistical indicator that reflects the ability of a particular process to produce an output within established specification limits.
[0078] Additional user preferences can be incorporated into the charts 314, 316 by adjusting the display options 402 as shown in FIG. 19. For example, the user can selectively activate various rules 403 displayed in the chart 314 by turning them on or off. The rules 403 can be used to detect uncontrollable conditions including non-random variations. By detecting such non-random variations, the user can initiate an investigation of possible causes to reduce the risk of future batch defects. The user can adjust the number of points in the rule definition to achieve the right balance between spurious signals and missing true non-random variations. In the illustrated example, rules 5-8 are turned on.
[0079] As another example, the user can adjust the lines 404 and limits 406 displayed on the chart 314. As an example, the user can turn on or off the data lines 408 (e.g., connecting data points) or the center line 410 (e.g., showing the average value of the limits) in the chart 314. In the illustrated example, all lines 404 remain on (displayed in the chart 314). As another example, the user can turn on or off various limits 406, such as the control limits 412, the warning limits 414, the inner limits 416, and the specification limits 418. In the illustrated embodiment, there are three different specification limits 418 and only one limit is turned on and shown on the chart 314. As shown, the user can also turn on or off OOS (out of scope) violations. For example, the user can request to see a visual cue when a limit is exceeded and can turn on a flag for OOS violations. Toggle switches 422 are used to turn on and off various display preferences. For example, toggle switch 422 in the right position means the display preference is on and toggle switch 422 in the left position means the display preference is off. It is contemplated that other buttons or indicators to indicate this on / off function may also be used.
[0080] The output control charts (e.g., as shown in Figures 12, 14, 16-19) can be interactive, allowing the user to select various points in the chart to determine the data underneath. For example, the user can select on a new limit value or specific data point and view the associated change reason and any reference URLs or attachments that can indicate to the user why the limit was changed or who made the change. In this manner, the user can also view the real-time history of any limits associated with each data point. The user can also select individual data points on the chart to view the original batch metadata (e.g., the information shown in Figure 13) for the selected data point.
[0081] FIG. 22 illustrates an example of an interactive output control chart. As shown, the control chart 450 has a number of interactive data points. A user can hover a cursor over a data point and / or select the data point to view metadata associated with the data point. For example, when a user hovers over or selects a data point, a text box or other graphic 452 is displayed that provides information related to the data point. The graphic 452 can indicate parameters associated with the data point and can include tabs that separate the data into categories. As shown, the graphic 452 indicates that a parameter 454, temperature, is associated with the data point. The graphic also includes four tabs with categories "Details" 456, "Specification Limits" 458, "Target Limits" 460, and "Batch Metadata" 462. The details category 456 can include information related to the data point, such as the value and trend of the data point. For example, this information can indicate whether the data point is an outlier (e.g., does not fit or conform to the trend of other data points, i.e., exceeds or is outside applicable limits).
[0082] The details category 456 may also include space to enter additional information. For example, a user may update information about the batch associated with the data point. The user's information and the time of entry are recorded and associated with the data entry. The standard restrictions 458 and target restrictions 460 may include restriction information (e.g., issuing agency, market, etc.) associated with the data point. The batch metadata 462 may include information about the circumstances surrounding the batch associated with the data point. For example, the batch metadata 462 may include a batch identifier, market, production date, parameters, and parameter values associated with the data point. It is contemplated that one or more of the information shown in FIG. 13 may be included in the batch metadata 462. By providing easy access to information about the data points, such a graphic 452 may allow a user to quickly review batch and conformance data without having to run separate reports or analyses outside of the chart. Additionally, by providing the ability to enter and review changes for each data point, the graphic 452 provides additional data integrity.
[0083] As shown in FIG. 22, the target constraints category 460 is selected within the graphic 452 and includes information about the target constraints associated with the data point, including the parameter value, co-product, market, parameter class, validity interval (e.g., valid from and valid from date), value, reference URL, attachments, comments, change reason, and status. As shown, the parameter associated with the target constraint is temperature, which matches the parameter associated with the data point 454. The parameter class is WC-CPP. The constraint is valid from January 5, 2019 to present. The constraint has a mean value of 23, an ST standard deviation of 0.12, and an LT standard deviation of 0.15. The user has written a comment and change reason section. For example, the user can enter a comment when there is an update to the constraint. This information can also include the user identification and the time the user updated the constraint. The status of the constraint is shown as current. The same or similar information can be included by the Standard Constraints tab. It is contemplated that the user may also upload a reference URL, attachments, and comments on any of the tabs to provide additional information in this category. Where the interactive graphics 452 are presented by a segmented control chart, it is contemplated that the interactive data points and graphics 452 may be used with any graphical output, such as, for example, the control charts 314 shown in Figures 12, 16, 18, and 19.
[0084] In another embodiment, the analysis can be output in the form of a table. For example, each data point can be displayed in a table with its corresponding constraints. In one embodiment, the table can indicate the compliance status of each data point. For example, the table can indicate whether each data point was in compliance with the regulations or objectives at the time the data point was collected. In other words, the table can indicate whether each data point was within its associated constraints. This information can be conveyed to the user by yes (indicating compliance) / no (indicating non-compliance), by color coding (e.g., green for compliance and red for non-compliance), or by any other means for distinguishing compliance from non-compliance.
[0085] In some embodiments, the system of the present invention may also regulate and / or track limit variations to ensure integrity within the system. FIG. 4 is a flow diagram illustrating a method for updating limit values within the data compliance tracking system 100. The method 250 begins at operation 252, where the server 102 receives new limit values, such as via referencing a database, receiving from a user device, or other type of input. Limit values for a particular parameter or set of parameters may be entered into the system 100 as they change over time. For example, a regulatory body may change criteria based on new research findings (e.g., research findings on parameter values considered safe, environmentally friendly, etc.), or a user may change limits based on new goals (e.g., a company may change its goals if it faces new expenses, acquires new investors, changes its business plan, etc.). As limits change, new limit values may be entered into the system 100.
[0086] In one example, the limits are automatically updated based on updates to the associated database 110. For example, the database 110 can be associated with a regulatory agency, and the limit information can be retrieved directly from the database at set intervals (e.g., weekly, quarterly) or when an update occurs (e.g., push retrieval or on-demand). The limit information can be automatically loaded into the system 100 when the limit information is updated in the database 110 (e.g., dynamically if the limit information changes). Alternatively, the system 100 can periodically check the database 110 for limit updates at a particular interval. For example, the system 100 can check for updates hourly, daily, weekly, monthly, yearly, or within any other interval. The system 100 can retrieve the updated limit information from the database 110 when a change is detected and store the limit information in the limit storage database 274.
[0087] Alternatively, a user may update the limits in system 100. For example, a user may adjust the limits to meet new goals set by a company, process changes, protocol changes, manufacturing changes, composition or component changes, etc. As another example, a user may monitor limits set by a regulatory agency and add new or updated limits to system 100.
[0088] With reference to FIG. 11, a user may view information regarding various restrictions for different parameters, where the displayed restriction information may include restriction category (e.g., applicable market) 374, effective from date 376, status 394, and restriction value 382. In the illustrated example, there are three restriction entries 396a-c for parameter 310 Aggregation (%). Status 394 indicates whether the restriction is the most recent restriction or has been discontinued. With reference to FIG. 10, a user may control the status 394 displayed for each parameter. For example, a user may selectively view restrictions that are discontinued, current, future, draft, pending, or rejected, or any other status as requested.
[0089] A restriction can be revoked when the "expiry" date of the restriction is in the past. In other words, the restriction cannot be applied to the current data collected, and conversely, the restriction only applies to historical data collected previously. Current restrictions, on the other hand, can have an open "expiry" date or a "expiry" date set in the future, and are currently applicable to any data collected in real time. Future restrictions have an effective start date that starts at some point in the future, indicating that the restriction only applies to data collected from a future date further in time. Draft restrictions are new restrictions entered by a user that have been saved by the user but not submitted. In other words, the new restrictions are incomplete and are not yet valid active restrictions. Pending restrictions are new restrictions entered by a user that have been submitted for approval to a user with a satisfactory privilege level. The restrictions are not valid until approved by a higher-level user. Rejected restrictions are new restrictions entered by a user that have been sent to a higher-level user for approval, but have been rejected by the higher-level user for some reason as an invalid or inappropriate change. A rejected limit is not a valid limit.
[0090] Continuing with FIG. 11, both obsolete and active restrictions have been selected for the European and US markets. If the user is only interested in compliance with the European market, the user would look at the first data entry 396a, which provides restriction information for the European market. The aggregate (%) restriction information for the European market indicates that the most recent effective restriction having a release value lower than or equal to 3.0 is effective from October 1, 2018. In other words, the user can only use the limit value 382 lower than or equal to 3.0 to determine the compliance of batches sampled on or after October 1, 2018. The user cannot use the limit value 382 lower than or equal to 3.0 to determine the compliance of batches sampled before October 1, 2018. If the user is only interested in compliance with the US market, the user would look at the second and third restriction entries 396b, c, which provide restriction information for the US market. As shown, the limit in second limit entry 396b is obsolete and the limit in third limit entry 396 is current. If the batch was sampled between October 1, 2018 and November 29, 2018, the limit in second limit entry 396b less than or equal to 2.0 will apply to the batch. If the batch was sampled on or any time after November 30, 2018, the limit in third limit entry 396c less than or equal to 2.5 will apply to the batch.
[0091] The user can view this restriction information to determine if the limit needs to be updated. The user can enter a new limit by selecting the most recent restriction on. In FIG. 11, the right round icon 398 can be selected to access the limit update menu 370. As shown in FIG. 7-9, the limit update menu 370 can include various adjustable parameters 310. For example, the user can adjust the applicable sub-product 372, market 374, effective from date 376, expiration date 378, and limit value 382 of the new restriction. For example, the new limit can only apply to a specific market 374. The user can enter the date that the limit 382 was issued (e.g., by a regulatory body or by the company) as the effective from date 376, meaning that the new limit applies from this date onwards. The user can enter an expiration date 278 if there is a known date after which the limit 382 will no longer be applicable, but the user can leave this value blank to indicate that the limit 382 is currently in effect. If the expiration date 378 is left blank, it may be automatically updated when a new limit value is entered into the system 100, as discussed in more detail below. The new limit value 382 may be entered as an upper limit value, a lower limit value, or a range 286 that includes minimum 282 and maximum 284 values. The valid from 376 to expiration date 378 indicate the valid time interval 380 of the limit value 382.
[0092] After operation 252, the method 250 proceeds to operation 254 where the server receives the reason for the change or other validation or commentary. As shown in FIG. 9, upon entry of the new limit value 382, the user may enter a reason for the change 388. This feature ensures that the change is legitimate (e.g., due to regulatory or company-wide changes) and not arbitrary, while also assisting in the documentation of changes throughout the history of the production process. In traditional systems such as Excel, limit changes are not tied to any particular reasoning, justification, etc., as long as they are reflected in the system. Thus, in some cases, temporary or unforeseen limit changes may not be detected and propagated through the data.
[0093] The system of the present invention can be configured to accept multiple formats of data, such as a reference URL 384 or attachment 386, and / or text input that provides additional assistance in changing the restriction. For example, the user can provide a screenshot or URL from a website or database that indicates the regulatory agency that issued the restriction change. As another example, the restriction changes can be listed manually or as an item that can be uploaded to the system 100. If the user can easily see the reasoning behind the current restrictions and track their history, these features enhance the validity of the data validation process and facilitate compliance with any data collection standards imposed by regulatory agencies. After the user has entered all the relevant information regarding the new restriction, the user can save 390 the draft (e.g., if the user requests additional information) or submit 392 the information.
[0094] After operation 254, method 250 proceeds to operation 256 where server 102 determines whether the change requires approval from another user. For example, either the type of change or the type of user who made the change may dictate the need for approval from another user before the change can be entered into the system. As an example, the type of change may trigger the need for approval regardless of the user who entered the change. For example, changes to certain types of constraints (e.g., goal constraints, standard constraints, warning constraints, control constraints, inner constraints, etc.) may require approval from a second user. Whether approval is required for a particular change may vary based on an "approval required" configuration setting. This setting may be adjusted based on user preferences.
[0095] As another example, a user's privilege level may dictate whether approval of another user is required. Users may have varying levels of authority within the system 100. For example, some users may have a low level of authority and other users may have a high level of authority. A user with a high level of authority may have a satisfactory or essential privilege level to automatically make changes, and a user with a low level of authority may request approval of another user for the changes. A low level of authority may allow a user to view data within the system 100 and enter new data for approval. A high level of authority may allow a user to review data and enter new data into the system 100, review new data entered into the system by a low level user, and approve, disapprove, or reject new data entered by a low level user. In some embodiments, a user may have varying levels of authority with respect to different constraint categories or parameters. For example, a user may have authority to change either the objectives or the standard constraints, but not both. A user with a high level of authority (e.g., an administrator or approval role) has a satisfactory privilege level and a low level user does not. A user may establish an account on the system 100 with a username and password or other authentication (e.g., biometric, etc.). The system 100 may associate a user's authority level with the user's username, identifier, account number, etc. Based on the account accessing the system to enter changes, the system 100 may determine the user's authority level and determine if the user has a satisfactory privilege level, for example, the system of the present invention may look up the user's privilege level and then compare it to a lookup table of allowed privilege levels or titles to effect automatic changes to restrictions. The privilege level may vary based on restriction type, parameters, actions, etc.
[0096] If another user's approval is not required (e.g., the user has a satisfactory privilege level), method 250 proceeds to operation 260 where server 102 determines whether approval is to be granted. For example, if a high-level user enters a new limit value with a reason for the change and hits submit, approval is implied and the new limit value is accepted by system 100. If the user's privileges are high enough but no justification for the change is provided, system 100 may reject the change.
[0097] If approval of another user is required (e.g., the user does not have a satisfactory privilege level), method 250 proceeds to operation 258 where system 100 sends an approval request to the applicable user (e.g., a user with a satisfactory privilege level or a user with supervisory authority). For example, system 100 can determine that an account is associated with a lower level user who does not have a satisfactory privilege level, or that the user is entering a change to a type of restriction that requires approval of another user. When the user submits a new limit along with a reason for the change, system 100 sends an approval request to an account associated with the higher level user. For example, this account can include an inbox, and system 100 can generate a message in the higher level user's inbox. The message can include a button or link for the higher level user to approve or reject the changed limit. The higher level user can review the change, including the reason for the change and any referenced URLs or attached information, and decide whether to approve or reject the limit change.
[0098] After operation 258, the method 250 proceeds to operation 260, where the system 100 determines whether approval is given. The system 100 receives input from a high-level user approving or rejecting the restriction change. This input can be in the form of a message, a button selection, a checkmark, etc. Additionally or alternatively, the system 100 can analyze the input justification data from the approval request to validate the change. For example, for some parameters, the system of the present invention can analyze the new restriction value for the likelihood of identifying printing errors or other input errors or other benchmark characteristics. As another example, the system 100 can analyze the approval request to ensure that comments are included, or that certain parameters require additional supporting documentation to be changed (e.g., a specified value can require a link to the corresponding specification), and so on. Thus, operation 260 can include user verification evaluations, as well as formatting, checklist items, and the like, all as part of the analysis before indicating approval.
[0099] If approval is not given, method 250 proceeds to operation 262, where the new limits are rejected and method 250 ends. For example, when a high-level user rejects a limit change, the new limits are not entered into system 100 but are instead discarded. A message may be sent to the lower-level user (if the limit change was originally entered by a lower-level user) indicating that the changes were rejected.
[0100] If approval is given, method 250 proceeds to operation 264 where a validity interval is determined. System 100 generates a validity interval based on the valid "from" date entered by the user to the expiration date. If the expiration date is blank, the validity interval is extended to the current date. The validity interval is associated with the restriction and stored as metadata associated with the restriction.
[0101] After operation 264, the method 250 proceeds to operation 266 where the new limit value is stored as a new limit entry. For example, the new limit value may be stored in the limit storage database 274 or 604. In this example, both the new limit value 286 and the validity interval 280 are stored. The new limit value also populates a new limit entry for the particular parameter on the user interface. For example, as shown in FIG. 11, a new limit entry 396 is created under the third limit entry 396c. In this example, if the limit was changed for the US market, the new limit entry 396 would display Market: US and its status would be current with the validity start date entered by the user. If for some reason the value of the new limit is determined to be incorrect after being approved and / or entered into the system 100, the limit information may be de-approved by a high-level user (e.g., a user with a supervisory role) so that the limit information (e.g., value and / or validity interval) may be revised or corrected and resubmitted for approval.
[0102] After operation 266, the method 250 proceeds to operation 268. The status of the previous restriction is updated. In the example discussed above with respect to FIG. 11, the system 100 changes the status of the previous third restriction entry 396c from current to obsolete upon entry of the new restriction. Instead, the new restriction has a status of current. The previous third restriction entry 396c also generates an expiration date that is a date before the validity start date of the new entry. For example, if the new entry has a validity start date of January 1, 2019, the previous third restriction entry 396c generates an expiration date of December 31, 2018. In this way, the restrictions do not have any overlapping validity intervals. After operation 268, the method 250 ends.
[0103] In some embodiments, a processing element 152, such as an element running on a server or in a cloud-based network, executes one or more algorithms to determine batches and constraints for one or more specified parameters. Batch and constraint filtering by the system 100 helps a user more quickly sort through hundreds or thousands of batches and constraints when attempting to analyze a particular selection of batches and constraints. As shown in FIG. 20, the processing element 152 can execute an algorithm having a method 500 of batch filtering. The method 500 begins with an operation 502 where a unit action is determined based on a selected parameter. For example, the selected parameter may be temperature, pH, viscosity, etc. A unit action is a broad category that can be applied to a set of batches. For example, a unit action may be a product to be tested, a process, or some other experimental or manufacturing related factor. A list 308 of exemplary unit actions is shown in FIG. 7. Each of these unit actions 308 may be defined by a user.
[0104] After operation 502, the method 500 proceeds to operation 504 where a batch associated with the unit operation is determined. For example, a unit operation that is a product may have several batches produced over time when the product is manufactured. Any batches associated with this particular product may be determined in operation 504. After operation 504, the method 500 proceeds to operation 506 where the processing element 152 determines if there is an associated co-product (e.g., if the user selected one or more values from the co-product list). The multiple batches associated with the unit of operation may vary with the co-product. A co-product may be any variation in a product. For example, the concentration of a particular ingredient or drug may be slightly changed to produce a different co-product. As another example, the packaging or casing of the product may be varied (e.g., a drug may be in pill form as one co-product and in liquid form as another co-product). As yet another example, the size of the product may be varied for different co-products. The user may enter the co-product or leave the co-product blank when entering the batch information. A batch has an associated co-product if one has been entered. As shown in Figure 13, the co-product 358 associated with the particular batch 352 shown is 75 mg / mL vials.
[0105] If operation 506 determines that there is an associated co-product (e.g., the user selected one or more values in the co-product list), the method 500 proceeds to operation 508, where the batches are limited to those batches that have the selected co-product value. For example, if the system 100 filters batch MAB_020 352 shown in Figure 13, the system 100 determines that there is an associated co-product 358 and limits the batches to those that have the co-product 358 (e.g., 75 mg / mL vial). Any batches that do not have the same co-product value (e.g., 75 mg / mL vial) are eliminated.
[0106] After operation 508, the method proceeds to operation 510, where the processing element 152 determines whether there is an associated market value (e.g., whether the user selected one or more values in the market list). If no associated co-product is determined in operation 506, the method 500 proceeds directly to operation 510. Various batches stored within the system 100 may have different applicable markets (e.g., United States, Europe, Canada, etc.). For example, a batch may be generated with a particular market in mind, and the market may be entered into the batch data when the batch is entered into the system 100. As shown in FIG. 13, the particular batch 352 displayed is associated with the United States market 360.
[0107] If operation 510 determines that an associated market value exists (e.g., the user selected a market value from a list), method 500 proceeds to operation 512, where the batches are limited to those batches that have the selected market value. For example, if system 100 were to filter batch MAB_020 352 shown in Figure 13, system 100 would determine that there is an associated market 360 (USA) and would limit the batches to those that have a US market. Any batches that do not have the same market (USA) would be removed.
[0108] After operation 512, the method of the present invention proceeds to operation 514 where the processing element 152 determines whether there is a variable constraint category (e.g., a target constraint category) for the unit operation (e.g., whether the user has selected one or more values within the variable constraint category). If it is determined in operation 510 that there is no associated market value, the method 500 proceeds directly to operation 514. The variable constraint category may include any additional variable differences between batches. For example, the batches may differ based on the circumstances surrounding the batch, such as different test environments, equipment used, etc. The limit values may be different for each batch based on these variable differences. As an example, different equipment may result in varying limit values. For example, different equipment may have different efficiencies, sterility, capacity, etc. The optimal limits for products or processes using different equipment may differ based on the physical capacity of the equipment. In this example, the equipment type or ID may be the variable constraint category. The variable constraint category may be user defined or otherwise saved for the new type of constraint. For example, a user may input a category label (e.g., a type of equipment) and the parameters required for this category, and the system 100 determines whether a batch exists that has the particular category label and / or parameters required for the category entered by the user.
[0109] If there are various restriction categories defined for the unit operation at operation 514, method 500 proceeds to operation 516 where the batch is limited to batches having the selected various restriction category and associated value. For example, if the user enters the category "equipment" as the various restriction category and "steel" as the value, the system of the present invention will limit the batch to batches that have steel equipment entered in the batch information. Any batches that do not have steel equipment will be eliminated.
[0110] After operation 516, method 500 proceeds to operation 518 where a batch range filter is applied. If operation 514 determines that there are no different restriction categories defined for the unit operation, method 500 proceeds directly to operation 518. The batch range filter filters the batches based on date. For example, the batch range filter can filter the batches based on the last N batches generated, the batches generated from the last N days (or weeks, months, or other time period), or the batches within a particular date range. After operation 518, method 500 proceeds to operation 520 where N batches are determined. Any batches generated during the selected time frame are selected, and batches generated outside the selected time frame are excluded. The result is a particular number of selected batches, N.
[0111] As another example, the processing element 152 may execute an algorithm having a method 550 for determining associated constraints for a given batch having specified parameters. The algorithm may apply to both target constraints and specification constraints. The method 550 begins with operation 552 where a specified batch and associated batch date are determined. Batches may be collected over time, whereby each batch may have a respective date when it was sampled. For example, as shown in FIG. 13, batch MAB_020 352 has a batch date 354 of 11 / 16 / 2018 at 15:13. After operation 552, the method 550 proceeds to operation 554 where a specified parameter is determined. A batch may have one or more associated parameters. Each parameter may have different constraints and associated values. A user may select a particular parameter for which the user would like to monitor the suitability of the data. For example, the user may select temperature, pH, viscosity, etc., depending on the parameter the user would like to review.
[0112] After operation 554, method 550 proceeds to operation 556 where all constraints for the specified parameters are determined. Each parameter has one or more constraints associated with it, and may have one or both of standard constraints and target constraints. In operation 556, processing element 152 determines all target constraints, all standard constraints, or both. After operation 556, method 550 proceeds to operation 558 where only approved constraints are selected, and pending, draft, and rejected constraints are removed. In other words, only constraints that have been previously approved by a user with the specified privilege level are selected.
[0113] After operation 558, method 550 proceeds to operation 560 where only restrictions that have a status of current or obsolete are selected. For example, as shown in Figure 10, a user can filter by status 394 by selecting on the statuses desired to be displayed (e.g., current and obsolete) and selecting off the statuses to be hidden (e.g., future, draft, pending, and rejected). Only restrictions that are current (e.g., have no expiration date) or obsolete (e.g., have an expiration date in the past) will be displayed.
[0114] After operation 560, method 550 proceeds to operation 562 where only restrictions within a particular date range are selected. For example, if a user wants to review current restrictions, the user may select a restriction with a target effective start date that is on or before the batch date and has no "expiry" date. As another example, if a user wants to review obsolete restrictions, the user may select a restriction with a target effective start date that is on or before the batch date and has an "expiry" date that is on or after the batch date. In either case, the selected date range includes the batch date in order to apply the restrictions to a particular batch.
[0115] After operation 562, method 550 proceeds to operation 564 where processing element 152 determines whether there are any restrictions with similar co-products and market values. For example, if the batch has both a co-product and a market value associated therewith, processing element 152 determines whether there are one or more restrictions with the same two established values as in the batch. As another example, if the batch has a co-product value but not a market value, processing element 152 determines whether there are one or more restrictions with the same co-product value but not a set market value. As an additional example, if the batch has a market value but not a co-product value, processing element 152 determines whether there are one or more restrictions with the same market value but not a set co-product value. As yet another example, if the batch does not have a co-product value or a market value, processing element 152 determines whether there are one or more restrictions with no co-product value or no market value.
[0116] If there are restrictions with similar co-product and market values, the method 550 proceeds to operation 566 where a restriction with such a value is selected. If there are no restrictions with similar co-product and market values, the method 550 proceeds to operation 568 where a restriction that does not have a value set for the co-product and market is selected. After either operation 566 or operation 568, the method 550 proceeds to operation 570 where the processing element 152 determines whether there are different restriction categories for the batch. The different restriction categories can be defined by the unit operation or by individual batches. For example, a single unit operation can have different restriction categories defined that apply to all batches within the unit operation. For example, the unit operation can have a different restriction category "equipment" and all batches have a value set to "equipment". Alternatively, each batch can have different restriction categories defined that are unique to it.
[0117] If there are no different restriction categories for the batch, the method 550 ends. This is the typical path when the applicable restrictions are standard restrictions as opposed to target restrictions. If there are different restriction categories for the batch, the method 550 proceeds to operation 572 where the processing element 152 determines whether there are any restrictions with different restriction category values that match the batch metadata value. By way of example, a user may define one or more different restriction categories and different restriction values stored in the system 100. In this manner, such restrictions may be associated with a batch that has a particular value for the defined different restriction categories. For example, a batch may have a value of "steel" for the different restriction category of "equipment". A particular restriction may only be applied to batches sampled with steel equipment. If there are any restrictions with such matching values, the method 550 proceeds to operation 574 where such restrictions are selected and the method 550 ends. If there are no restrictions with such matching values, the method 550 proceeds to operation 576 where a restriction that does not have a different restriction category configured is selected and the method 550 ends.
[0118] The disclosed system can include one or more alerts or user notifications that provide the user with select information, which can be provided in real-time as data is received and analyzed by the system. For example, an alert can provide information on data values entered into the system for various parameters or characteristics related to the batch. An alert can provide the user with real-time feedback on new data entered into the system. For example, an alert can provide real-time feedback of values that do not meet one or more constraints or violate one or more rules, and / or when new data values are entered into the system of the present invention. This alert functionality allows the user to easily monitor the progress and performance of a batch without having to constantly monitor a database. This alert can also quickly identify problems within a batch run, such as a particular parameter failing a constraint, which allows the user to act to correct chemical, mechanical, and / or electrical problems during the processing run that can help "save" the batch. Conventional data tracking and adaptation systems do not include an alert functionality, which forces the user to constantly check a database, preventing the user from monitoring multiple batches simultaneously and / or accomplishing other work functions while monitoring the batches.
[0119] 23 is a flow diagram illustrating a method 700 of utilizing the system 100 to initiate and send an alert to a user, such as one or more user devices. The method 700 may be stored as an algorithm or programming instructions in a memory and executed by a processing element, etc. The method 700 begins at operation 702, where a data value is received into the memory, such as by being entered into the system as described with respect to FIG. 6, at operation 202 of the method 200, which may be manual, automatic, or some combination of the two. For example, the data value may be received directly, e.g., by the user device 106, from a computer or other device (or instrument or sensor) or from a user entering a value into the system, or may be retrieved from a database. The data value may correspond to one or more parameters of the batch that are detected or tracked during the batch run.
[0120] After operation 702, method 700 proceeds to operation 704 where the system determines whether the data value is approved. For example, certain data may be automatically approved when entered, while other data may require approval by a user with a sufficient privilege level. For example, the system may determine, for example, at operation 256 of method 250, whether approval of another user for changes entered into the system is required in a manner similar to that described with respect to FIG. 4. As another example, certain data (e.g., parameters) may be configured to be automatically approved. For example, a user (e.g., a supervisor) may configure certain data to not require approval (e.g., by setting the data to auto-approval and not marking the data as requiring approval, etc.). When the system determines that a data value entered into the system does not require approval, the data is automatically approved. The system of the present invention may store such configurations in memory for use when analyzing approval of new data entered into the system. For example, the system of the present invention may store a predefined list of approved data, data that does not require approval, and / or data that requires approval. In some cases, data may be approved based on the value of the data falling within a particular value range or being above or below a certain threshold, based on parameters, based on the user entering the value (e.g., privilege level), etc.
[0121] In some embodiments, if the data conforms to required parameter level configurations, the data can be approved automatically or by a user. For example, a particular parameter can be a numeric or text value. In this example, in order for the data to conform, the data value must be a numeric or text value. For example, if the data is configured as a number, text cannot be entered, or if the data is configured as text, numbers cannot be entered. In these examples, if text is entered when a number is required, the parameter level configuration will be violated. As another example, a predefined list of valid values for a particular parameter can be stored by the system. In this example, if the data falls within the predefined list of valid values, the data conforms to the parameter level configuration, but if the data falls outside the predefined list of valid values, the parameter level configuration will be violated. In these examples, the data cannot be approved if the parameter level configuration is violated. For example, data that would otherwise be automatically approved will not be approved if the parameter level configuration is violated. Alternatively, if approval is not required and the data does not violate the parameter level configuration, the data will be automatically approved.
[0122] If the data value is not approved, method 700 proceeds to operation 706, where approval is obtained for the data value. For example, if the data value requires approval and the value does not violate a parameter level configuration, the data is set to pending (e.g., requiring approval from a user). For example, the server may send an approval request to a user (e.g., a supervisor) with a sufficient authority level.
[0123] If the data value is approved, either at operation 704 or operation 706, the method 700 proceeds to operation 708 where the server determines whether an alert associated with the approved data value is set to activate. A user may configure one or more alerts via a user interface. For example, FIGS. 24-28 show exemplary user interfaces for customizing alerts in the disclosed system. As shown in FIG. 24, the user interface 700 includes a home screen 752 that provides access to a "My Alerts" tab 754. The "My Alerts" tab 754 provides user information on active alerts. For example, as shown, there are no active email alerts set up for the current user. A user may select a link 756 labeled "Get Started" and / or an Access tab 758 on the "My Alerts" tab 754 to set up a desired alert. For example, FIG. 25 shows the "My Alerts" tab 754 opened by selecting the Access tab 758, which allows a user to customize one or more alerts.
[0124] Alerts can be created by select users with defined privileges, for example, in some cases, alerts can only be created by a parameter administrator or a system supervisor. For example, a parameter administrator can have special system privileges that allow access to a restricted user interface that allows the parameter administrator to set up alerts for various situations. For example, a parameter administrator can set up one or more alerts for one or more categories based on, for example, site, product, batch, batch date, unit operation, parameter, rule violation, limit violation, etc. For example, an alert can be configured to be sent to a user when a received data value is from a particular site where a batch is being run, is received during a particular time window, is for a particular parameter, violates one or more rules, or exceeds one or more limits.
[0125] In some embodiments, the creation of alerts can be managed by process definition configuration (e.g., configured at the parameter level) and can be included in the metadata of the parameter. For example, FIGS. 26-28 show an exemplary user interface for a user (e.g., a parameter administrator) to customize alerts via a process definition screen 772. For example, a user can access the process definition screen 772 by selecting a process tab 774. A user can customize various analyses and alerts for different parameters. For example, as shown in FIG. 26, by selecting a parameter 776, a user can access a process definition box 778 for the parameter 776. As shown, the process definition box 778 includes an analysis tab 780 and an alerts tab 782. In FIG. 26, the analysis tab 780 is selected, allowing a user to customize one or more rules and / or constraints. In other words, a user can select the rules or constraints that the user wants to apply to a particular parameter. The rules or constraints in a process definition for a parameter can be set up in advance (e.g., by a parameter administrator or a system supervisor). For example, as shown in FIG. 26, rules 784 1-5 and specification constraints 786 1-2 are set up in the system in advance and can be adjusted by the user. As shown, the user can customize one or more rules 784 of an individual chart 788 and / or MR chart 790 by turning on or off the rules 784 via a toggle 792, button, or another selection mechanism. The user can further customize one or more specification constraints 786 by selecting an option from a drop-down bar 794. As shown in FIG. 27, the user has turned on rules 784 1 and 2 by moving the toggle 792 to the right and selected "Action" from the drop-down bar 794 for the specification constraint 786 1 of the parameter 776 SCR. The user can save the customized analysis 780 settings by selecting the save button 796.
[0126] FIG. 28 shows that the Alerts tab 782 has been selected, which allows the user to customize one or more alerts for the selected parameter 776. The user can turn on or off the alerts for the selected parameter. As shown, the user can turn on an active alert 800 for the selected parameter 776 by moving a toggle 798 (or selecting a button or other selection mechanism). When an active alert is turned on, the system of the present invention determines whether one or more alerts are associated with the parameter. If an alert is associated with the parameter, the system of the present invention stores the alert information in a database, for example, as metadata associated with the parameter. As shown in the exemplary Alerts tab 782, the user can customize the alerts by chart type 802 (e.g., individual or I-MR), batch range 804 (e.g., receive alerts for the last X number of batches), co-product 806, and / or market 807. Other alert customizations are also contemplated, for example, alerts can be set based on parameter class (e.g., CPP (critical processing parameter)), CQA (critical quality attribute), etc. The user can select the save button 808 to save the customized alert 782 settings.
[0127] As shown in FIG. 32, a user may view alert information associated with a parameter via an interactive output control chart displayed on user interface 300, for example as discussed with respect to FIG. 22. As shown, control chart 450 includes interactive data points that allow metadata to be viewed by hovering a cursor over the data point and / or selecting the data point. As shown, when a user hovers over or selects a data point, the system of the present invention displays a text box or graphic 452 that provides information related to the data point. This graphic includes tabs "Details" 456 and "Batch Metadata" 462, as discussed with respect to FIG. 22, and tab "Alerts" 463. In this example, the Alerts tab 463 is selected, displaying alert information associated with the selected data point for parameter 454 Osmo. In this example, the alert information includes an alert timestamp 465 (e.g., indicating the time the alert was sent), a chart type 467, a chart value 469, a rule set name 471, a rule number 473, and a rule description 475, each of which is associated with a particular alert configured for parameter 454 osmo, for example, as discussed with respect to FIGS. 26-28.
[0128] A user may subscribe to or activate various alerts based on user preferences. For example, a user may only request to receive alerts for certain products and may activate alerts for those products. As an example, a user may wish to receive restriction and / or rule alerts for certain products and may activate alerts for such conditions. The system of the present invention may store user preferences individually (e.g., stored as preferences in a user account specific to the user) and / or may store a list of users (e.g., an email list) that subscribe to each alert. In some embodiments, a supervisor or system administrator may assign an alert to one or more users who subscribe to the alert. In these embodiments, the users assigned to the alert may, in some cases, turn the alert on or off depending on their individual user preferences.
[0129] As shown in FIG. 25, a user can subscribe to or activate various alerts via a home screen 752 and a “My Alerts” tab or bar 754. By selecting an Access tab 758, a user can view one or more customizable alerts. The alerts accessed via the Access tab 758 can include a list of alerts created by a parameter administrator, alerts to which the user has subscribed, and / or alerts assigned to the user. In the example shown in FIG. 25, a user can turn on (activate) or turn off (deactivate) predefined alerts 760 and / or run rule alerts 762 for different sites 764, products 766, and unit operations 768. A user can turn on alerts for all unit operations 768 or a subset of unit operations 768. As shown, a user can turn on and off alerts via a toggle 770, although other selection mechanisms (e.g., buttons) are contemplated. In the illustrated example, the user has moved the toggle 770 to the right to turn on both the prescriptive alerts 760 and the run rule alerts 762 for the product 766A-Mab generated at the Cambridge site 764 associated with a subset 768 of unit operations including Prod, ProA, VI, and CEX. Other alerts are turned off by leaving the toggle 770 to the left. Thus, the user can only receive alerts for triggered alerts (e.g., triggered unit operations). In some embodiments, the user can customize the format and / or destination of the alerts. For example, the user can prefer to receive alerts or notifications via email, text, website link, etc. Alternatively, the format and / or destination of the alerts can be customized by the system administrator.
[0130] Continuing with reference to FIG. 23, if the server determines at operation 708 that the active alert is not associated with the approved data value, method 700 ends. If the server determines at operation 708 that the active alert is associated with the approved data value (e.g., based on the user's saved alert preferences), method 700 optionally proceeds to operation 710, where the server evaluates the conformance of the approved data value based on the selected analysis. In cases where the alert is associated with an analysis, such as rule violation or conformance to a restriction, the server evaluates whether the approved data value violates an applicable rule or conforms to an applicable restriction. For example, as shown in FIG. 27, rule 1 and rule 2 are the activated analyses. In this case, when the user activates the rule alert, the user will receive alerts for rules 1 and 2. In this example, at operation 710, the server evaluates the conformance of the approved data value with rule 1 and rule 2, e.g., whether any rule has been violated. As another example, the server can evaluate the conformance of the approved data value with one or more restrictions.
[0131] After operation 708, or optionally after operation 710, the method 700 proceeds to operation 712 where an alert is sent to the user. For example, the alert may be an email, a text message, an application notification, etc. FIG. 29 illustrates an example email alert 810 sent by the server to the user device 106 based on the triggered alert. The alert may be sent to any users who have subscribed to the particular alert. In some embodiments, the alert may also be sent to a supervisor who may selectively subscribe to the alert in some cases. The alert may provide various information of the received data value. For example, the alert may provide product, process, and batch information. In cases where the server has evaluated the conformance of the data value (e.g., as determined in operation 710), the alert may also include information of conformance of the received data value. As shown in FIG. 29, email alert 810 provides site 812, product 814, batch ID 816, batch date 818, unit operation 820, phase 822, replication table 824, parameters 826, results 828, and rule violation 830 information for a particular received data value. The subject line 832 of the email alert 810 can indicate the type of alert. As shown, the type of alert is a control chart alert for site Basel for product Utopium. The email alert 810 indicates to the user that rule 5 (3 points of row increase or decrease) has been violated for product Utopium at the Basel site for batch VI-07 recorded on November 7, 2019. In this example, the user has subscribed to alerts for rule violations (e.g., violation of rule 5). While the current embodiment illustrates an alert providing text information, it is contemplated that the information can also be provided as a chart (e.g., a chart described herein) or a data table.
[0132] The home screen may also provide quick access to one or more charts. For example, a user may choose to monitor and review charts for a particular product, sub-product, batch, site, parameter, market, etc. Instead of sorting through large amounts of data (e.g., multiple products), a user may subscribe to one or more charts. For easy retrieval of subscribed charts, a user may save a particular chart in a quick access location. For example, as shown in FIG. 24, the home screen 752 may include a "My Charts" tab or bar 834. A user may select an access tab 836 in the "My Charts" tab 834 to quickly view charts for a particular product, sub-product, batch, site, parameter, market, etc. For example, FIG. 30 shows the "My Charts" tab 834 opened by selecting the access tab 836, which allows a user to view saved or frequently viewed charts. For example, as shown in FIG. 31, a user may save a chart by selecting a save icon or button 838 (other icon shapes other than a circle are contemplated in this case). As shown, the user can also mark a chart as a favorite or favorite chart by selecting a favorite icon or button 840 (in this case a star, other icon shapes are possible). As shown in FIG. 30, the saved chart appears in the My Charts tab 834 for quick retrieval. In the example shown, the favorite chart 846 (with the selected star) appears at the top of the list of charts in the My Charts tab 834. It is also contemplated that a server can monitor chart views and save charts that have a certain number of views (e.g., more than a few thousand views) to the My Charts tab 834 for quick retrieval.
[0133] As shown in FIG. 30, the home screen 752 displays charts to which the user has subscribed. The charts displayed can be for a specific product (e.g., when a product is selected) or all products (e.g., when all products are selected). For example, as shown, all charts to which the user has subscribed (e.g., all products 842) are displayed when toggle 844 on the home screen 752 is selected (although other selection mechanisms are contemplated). The charts can be categorized into various categories, such as by product (as shown), site, batch, parameter, market, etc. The user can select a chart in the list to view the chart and associated data. As shown in FIG. 30, the user has selected favorite chart 846 to view chart 848 and associated data, such as restriction data 850 and fit. In this case, favorite chart 846 is an individual chart of product GF time. The user can select chart 848 to view the analysis module if the user created a chart and subscribed to chart 848. For example, after selecting chart 848, analysis screen 852 is displayed as shown in FIG. 31. The analysis screen 852 provides additional information such as parameters 854, chart type 856, batch range 858, batch category 860, etc. As mentioned above, a user can hover the cursor over and / or select a data point to view metadata associated with the data point (e.g., batch information).
[0134] conclusion The techniques described herein may be implemented as logical operations and / or modules in one or more systems. The logical operations may be implemented as a sequence of processor-implemented steps commanded by a software program executing in one or more computer systems, as interconnected machine or circuit modules within one or more computer systems, or as a combination of both. Similarly, the descriptions of various component modules may also be provided in terms of the operations performed or effected by the modules. The resulting implementation is a matter of choice dependent on the performance requirements of the system(s) implementing the described techniques. Accordingly, the logical operations making up the embodiments of the techniques described herein are referred to variously as operations, steps, objects, or modules. Furthermore, it should be understood that the logical operations may be performed in any order, unless expressly claimed otherwise or a particular order is inherently required by the claim language.
[0135] In some implementations, an article of manufacture is provided as a computer program product that causes initialization of operations in a computer system to perform procedural operations. One implementation of a computer program product provides a non-transitory computer program storage medium that is readable by a computer system and that encodes a computer program. It should further be appreciated that the described techniques can be used in dedicated devices independent of personal computers.
[0136] The above specification, examples, and data provide a complete description of the structure and use of exemplary embodiments of the invention as defined in the claims. Although various embodiments of the claimed invention have been described above with a certain degree of particularity, or with reference to one or more individual embodiments, those skilled in the art may make numerous modifications to the disclosed embodiments without departing from the spirit or scope of the invention as claimed. Accordingly, other embodiments are contemplated. All matter contained in the above description and shown in the accompanying drawings is to be construed as illustrative of specific embodiments and not as limiting. Changes in detail or structure may be made without departing from the basic elements of the invention as defined in the appended claims. [Explanation of symbols]
[0137] 100 Data Compliance Tracking System 102 Server 104 Network 106 User Devices 108a 108n equipment 110 Database
Claims
1. 1. A method for validating data through a data conformance tracking system, comprising: receiving, by a processor, at least one data point from a computer element, the data point corresponding to data collected from a sampling of at least one parameter during a batch run of a product and including time stamp data; determining, by the processor, constraint information corresponding to the at least one parameter, the constraint information including at least one constraint associated with the at least one parameter and having an associated valid value range; storing, by the processor, the at least one data point and the restriction information; receiving, by the processor, a request for analysis from a user device; analyzing, by the processor, the stored restriction information to apply a first restriction to selected data points based on the analysis request from the user device, the selected data points having associated metadata including a market associated with the selected data points; analyzing, by the processor, the stored restriction information to determine restrictions associated with the market, the determined restrictions to be applied to the selected data points; displaying, by said processor, an analysis output; The method includes:
2. the analysis output is displayed as a chart showing the relationship between the selected data points and the applied constraints.
2. The method of claim 1 .
3. The step of analyzing the stored restriction information to apply a first restriction to the selected data points comprises: determining, by the processor, time values of the selected data points; analyzing, by the processor, the constraint information to determine an applicable valid time interval for the selected data points based on the time value; applying, by the processor, restrictions associated with the applicable valid time interval to the selected data points; The method of claim 1 , comprising:
4. The selected data points have associated therewith metadata, the metadata further including parameters and a manufacturing date, and analyzing the stored constraint information to apply a first constraint to the selected data points comprises: analyzing, by the processor, the stored constraint information to determine one or more constraints associated with the parameter; analyzing, by the processor, the stored restriction information to determine at least one restriction of the one or more restrictions associated with the manufacturing date; The method of claim 1 , comprising:
5. receiving, by a processor, second data points from a computer element, the second data points corresponding to data collected from testing a second batch of the product; analyzing, by the processor, the stored constraint information to apply a second constraint to second selected data points; displaying, by the processor, an analysis output indicating the selected data points associated with each constraint, wherein the applied constraint and the second applied constraint are different; The method of claim 1 further comprising:
6. the applied constraints are the constraints in effect at the time the at least one data point was originally generated; The method of claim 1.
7. the applied constraint has an associated limit value; The method further comprises: comparing, by the processor, the selected data points to the associated limit values; determining, by the processor, that the selected data points violate the applied constraints based on the comparison; displaying, by the processor, the violation as part of the analysis output; The method of claim 1 further comprising:
8. The method of claim 7 , wherein the associated limit value comprises a range of valid values having a maximum valid value and a minimum valid value.
9. determining that the selected data points violate the applied constraints includes determining, by the processor, that the selected data points are outside the valid value range. The method according to claim 8.
10. the associated limit value comprises a maximum valid value, and determining that the selected data point violates the applied limit comprises determining, by the processor, that the selected data point exceeds the maximum valid value. The method according to claim 7.
11. the associated limit value includes a minimum valid value, and determining that the selected data point violates the applied limit includes determining, by the processor, that the selected data point is below the minimum valid value. The method according to claim 7.
12. receiving, by the processor, a user selection of the selected data points; determining, by the processor, the associated metadata for the selected data points, the metadata relating to at least one of batch identification information, process, or product information for a batch run of the product; displaying, by the processor, metadata associated with the selected data points; The method of claim 1 further comprising:
13. receiving, by the processor, an update to the constraint information corresponding to the at least one parameter, the updated constraint information including a new constraint value and a new associated valid value range associated with the at least one parameter; storing, by the processor, the updated restriction information in a memory; updating, by the processor, a status of the at least one restriction to obsolete; Further comprising: analyzing the stored restriction information to apply restrictions to the selected data points includes analyzing the stored updated restriction information to apply the new restrictions to the selected data points. The method of claim 1.
14. receiving, by the processor, a quick search request from a user device to search one or more stored analysis outputs stored in a quick search location; displaying, by the processor, information related to the one or more stored analysis outputs; receiving, by the processor, a selection of information related to one of the one or more stored analysis outputs; displaying, by said processor, an analysis output relating to said selected information; The method of claim 1 further comprising:
15. determining, by the processor, that the at least one data point is acknowledged and associated with an active alert; if the at least one data point is determined to be acknowledged and associated with an active alert, sending, by the processor, an alert notification to the user device indicating that the at least one data point was received; The method of claim 1 further comprising:
Citation Information
Patent Citations
Management system for chemical substance included in product individual
JP2007172290A
Method and apparatus for monitoring a product during shipping, storage and use
US20020082787A1
Dynamic batch limit validation
US62782920P0
Dynamic batch limit validation
US62876990P0
History management method and warehousing / delivery management method
WO2004036472A1
