Process Model. The spatial process {M(s)}, with M(s) = (M1(s), ..., MQ(s))’ is multivariate and can be modeled in different ways (Xxxxxxx et al. 2010). We adopt an approach based on kernel basis functions (see, e.g., Xxxxxx, 1998) and we suppose that:
Process Model. The process model characterizes the spatio-temporal deviation process Mt(s). Once we determine Mt(s), an important interest will be to estimate the more appropriate time-invariant systematic bias ̃(s) for the study period as an average of Mt(s), i.e., ̃(s)= ∑t=1:T Dt(s)/T. The spatio-temporal process Mt(s) is driven by a large-scale spatial component that changes stochastically but smoothly in time and a site-specific component. The spatial large-scale component at time t is represented by a linear combination of p spatial kernel functions {k(s) : k = 1,…, p} as in Xxxxxx (1998), i.e., ∑k=1:p k(s) t,k where t,k is the coefficient parameter for kernel k. The whole formulation is given by Mt(s) = (s)’ t +t(s) (3.4) t = t-1 +t (3.5) t(s) = t-1(s) + t(s) (3.6) where (s) = {1(s), …, p(s)} and t = (t,1 , …, t,p)’. The number of kernels p is chosen to be much less than the number of spatial data points n. The choice of the kernels is further discussed in section t
Process Model. 12 2.1.1 Multi-staged development....................................................................... 12 2.1.2 Individual Release Projects.................................................................... 12 2.1.3 Risk Management................................................................................ 12 2.1.4
Process Model. Garver will develop and analyze a process model for PCW utilizing the GPS-X process software package. The GPS-X process model will be calibrated to the existing facilities and process data and will be used to confirm existing treatment capacity as well as be extended to simulate the process alternatives necessary for any identified capacity expansion. The modeling steps will include: • Garver may recommend optional limited additional project-specific sampling to help improve the process model calibration. Costs for this sampling and analysis will be the responsibility of the Client. • Simulation of the existing facilities, • Determination of the existing plant biological treatment capacity, • Identification of process re-configurations and operational schemes and estimation of their advantages and disadvantages (not to exceed two alternatives) and • Identification of additional biological volume and configuration to effectively meet plant treatment objectives for up to two alternatives. Upon completion of the process model, Garver will develop a draft technical memorandum (TM 3) of the methodology used in developing the model and the results. Garver will deliver copies via digital .PDF and three printed hard copies for Client review. Following review, Garver will conduct a workshop (Workshop 3) and present the model and its results. Workshop 3 will be conducted via web conference to minimize travel required. The Client has the option of travelling to a Garver office to participate, or Garver will coordinate with the Client’s IT staff to facilitate the web conference. Garver will issue minutes to summarize Workshop 3, and incorporate comments from the Client into the final TM 3 as appropriate.
Process Model. Each interaction between customer and provider consists of one or more processes which are modeled using workflow concepts. Our process model which is compatible to WfMC terms is depicted in figure 5. Processes consist of activities. To enable hierarchical decomposition a process itself is an activity. An activity needs resources to be executed on and data to work with. Both are abstract representatives to be mapped later on. Activities can generate events, e.g., for inter–process communication, synchronization of concurrent paths or for exception handling. Events are also triggers for other processes. Additionally, the current state must satisfy pre–conditions before an activity is executed and the state must satisfy post–conditions after finishing the execution. Conditions are used for guaranteeing a consistent state before and after the execution of an activity. Events and data of the process as well as system data like current time can be used in conditions. The so far defined parts of the process are highly reusable because all information is service-oriented, while the following mapping is customer dependent. The data needed by activities are mapped to variables and triggers generates mapped to mapped to properties. Properties represent values which are defined in the SLA. Variables are highly dynamic values which are exchanged through an interface between customer and provider at run time. An example for dynamic values are the user data in the authorization process while the maximum authentication time is a property. The resources used by activities are mapped to interfaces. The definition of interfaces hides the implementation details. A resource representing a role can be mapped to a technical interface, e.g. defined by a telephone number, or to an individual contact person. An important information in a service level agreement are constraints. In combination with properties they specify the service level. Constraints consist of rules with parameters which are also defined in the service level agreement. Rules can refer to values of variables, properties and system data as well as events. An example is “the overall delivery time of local email may not exceed n minutes during business hours”, where “n minutes” and “business hours” are parameters of the constraint.
