Component specification user-defined components

Different baseline correction methods vary with respect to the both the properties of the baseline component d and the means of determining the constant k. One of the simpler options, baseline ojfset correction, nses a flat-line baseline component (d = vector of Is), where k can be simply assigned to a single intensity of the spectrum x at a specific variable, or the mean of several intensities in the spectrum. More elaborate baseline correction schemes allow for more complex baseline components, such as linear, quadratic or user-defined functions. These schemes can also utilize different methods for determining k, such as least-squares regression. 

The input of the problem requires total analytically measured concentrations of the selected components. Total concentrations of elements (components) from chemical analysis such as ICP and atomic absorption are preferable to methods that only measure some fraction of the total such as selective colorimetric or electrochemical methods. The user defines how the activity coefficients are to be computed (Davis equation or the extended Debye-Huckel), the temperature of the system and whether pH, Eh and ionic strength are to be imposed or calculated. Once the total concentrations of the selected components are defined, all possible soluble complexes are automatically selected from the database. At this stage the thermodynamic equilibrium constants supplied with the model may be edited or certain species excluded from the calculation (e.g. species that have slow reaction kinetics). In addition, it is possible for the user to supply constants for specific reactions not included in the database, but care must be taken to make sure the formation equation for the newly defined species is written in such a way as to be compatible with the chemical components used by the rest of the program, e.g. if the species A1H2PC>4+ were to be added using the following reaction ... 

Setting the limits for determining whether the instrument is still within acceptable performance criteria should be entirely the responsibility of the end user. The vendor can assist in providing guidelines as to how the instrument should function on delivery, but the operational qualification is intended to determine whether the instrument is still operating to within the specifications which the user defined upon purchase. For example, if the intended analysis is quantitation of a main component in a drug formulation, then detector noise which affects sensitivity may be of lesser importance than injection precision. Conversely, where the instrument is used for impurity determination, especially where the reported data is (area/area) %, then sensitivity and therefore detector noise may be of more importance than injector precision. If limits are indicated by the manufacturer, then these may be used directly if appropriate, but the user should be aware that the decision is his or hers. The limits for an OQ/PV should not... 

LASy instruments are defined in terms of an initial waveform, a rule for the cellular automaton (referred to as the transition rule) and envelopes for amplitude and pitch. The system provides tools for the individual specification of these components so that the user can build their own library of waveforms, rules and envelopes (Figure 8.16). Instruments are either created by combining components selected from these libraries or from scratch on a window, where the user can set up all these parameters at once (Figure 8.17). 

Figure 8 depicts our view of an ideal structure for an applications program. The boxes with the heavy borders represent those functions that are problem specific, while the light-border boxes represent those functions that can be relegated to problem-independent software. This structure is well-suited to problems that are mathematically either systems of nonlinear algebraic equations, ordinary differential equation initial or boundary value problems, or parabolic partial differential equations. In these cases the problem-independent mathematical software is usually written in the form of a subroutine that in turn calls a user-supplied subroutine to define the system of equations. Of course, the user must write the subroutine that defines his particular system of equations. However, that subroutine should be able to make calls to problem-independent software to return many of the components that are needed to assemble the governing equations. Specifically, such software could be called to return in-... 

Functional Requirements. Based on the user requirements, more detailed functional requirements can then be defined. Take as an example a gradient HPLC system with UV-Vis detection required to run a stability-indicating method. The functions of each of the hardware and software components required to perform the tasks in the user requirements should be specified. The functional specifications typically include ... 

Has the maximum number of injections for an analytical run been defined This is a critical component if 100 vials are routinely injected in a run, the system cannot be tested with a run of only 10 samples as a user has not demonstrated adequate size. The specification must match the use of the system, including replicate injections. 

Every in vitro method should be detailed in the developer laboratories using Standard Operating Procedures (SOPs) covering all essential components and steps of the method. The SOP(s) should be sufficiently defined and described and should include the rationale for the test method, a description of the materials needed, such as specific cell types, a description of what is measured and how it is measured, a description of how data will be analyzed, acceptance and decision criteria for evaluation of data, and what are the criteria for suitable test performance. All limitations, e.g., lack of metabolic competences (presence of phase 1 and phase 2 biotransformation activities) or absence of critical transporters, should be included in the in vitro method description. In general, the in vitro method should not require equipment or material from a unique source. This may not be always possible for particular in vitro test systems or other components of the method in which case a license agreement between the provider and a recipient/user may be required. For complex and/or specialized equipment, the equipment specifications and requirements should also be described. Acceptance criteria for measurements carried out on the equipment should also be provided where applicable (e.g., for analytical endpoint determinations, linearity and limits of detection should de detailed) [2],... 

Acceptance criteria can be defined as the list of requirements that must be satisfied prior to the user accepting delivery of the product, where the product refers to the in vitro method and the user to the validation body, the regulatory body, or an end-user s test facility. Acceptance criteria should be defined for key components of the test method such as the in vitro test system and the endpoint measurement. For defining such criteria the in vitro test system must have a specific functionality, which can be measured. Examples of acceptance criteria for endpoint measurements are linearity or limit-of-detection. An example of an equipment requirement is balance or pipette sensitivity. Acceptance criteria are used to assess the functioning of the in vitro method and/ or of various stages/parameters of the method. These need to be defined up front so that performance of the in vitro test system can be monitored on a regular basis. 

The application objects layer of the CIM Framework architecture provides additional functionality, extending the common components to make a complete MIES. This layer, which is identified but not specified, enables MIES suppliers and users to define product-specific and site-specific application objects and components that use and extend the CIM Framework common components to implement MIES functions that meet business needs. 

---