The following information describes how you can avoid typical problems caused by different handling of process data in PPM and Optimize.
Further information about how to use webMethods Optimize can be found in the documentation Administering webMethods Optimize.
Handling of time stamps for process data
In Optimize a process step comprises several ProcessStepInstanceChange events (PSIC events), which can be recorded and displayed independently of one another. For example, PSIC events can be created at the beginning or at the end of the step. They each receive their own time stamps, to which the relevant business data is assigned.
By contrast, in PPM the process step is the smallest entity, which is not assigned more than one value for each property. PPM assigns all business data to the time of the process step. When using the wm_process template, this is the end time. Thus, depending on when the business data in an event occurs, the time stamp for the measure in Optimize may differ from that in PPM.
To obtain identical data in both products as far as possible, configure the process in such a way that the business data is only sent at the end of a process step.
Handling of multiple PSIC events in a process step
Because it merges multiple PSIC events, PPM uses only the last attribute value for a process step. This means that, under some circumstances, data points are not displayed in PPM, specifically if multiple events in a process step contain business data of the same type and field or a single PSIC event contains several different data points with the same business data event type and field.
To obtain identical data in both products as far as possible, configure the process in Optimize in such a way that the business data is only sent at the end of a process step.
Handling of identical fields in multiple process models
If a particular field in EDA events is used in multiple process models in Optimize, PPM creates only a measure, a dimension, or an attribute for this field and only registers this with one process type.
It is normally sufficient in PPM to manually register the measures, dimensions, or attributes with those process types, with which they were not automatically registered by the wizard.
Uniqueness of display names
In Optimize, specific analyses are normally restricted to individual event maps. If measures or dimensions from multiple event maps are listed together, the name of the event map is available as an additional differentiating feature. In PPM there are no event maps, and analyses can contain a mixture of all measures and dimensions of a process type. If names of measures in Optimize are identical and they can only be distinguished using the event map, in PPM two identically named measures appear and they are difficult to differentiate.
Use unique names for measures and dimensions when creating event maps in Optimize. Alternatively, use CTK to change the names for PPM measures and dimensions after they have been created by the wizard. To do this, open the Dimensions and measures module in CTK and click the Set language-specific names button in the toolbar. Enter your changes.
Handling of identical dimension attributes in multiple event maps
If an attribute of a dimension is used in multiple event maps in Optimize, a separate dimension is created in PPM for each usage. The dimensions in PPM normally all have the same name.
We recommend changing the names for PPM dimensions using CTK after they have been created by the wizard. To do this, open the Dimensions and measures module in CTK and click the Set language-specific names button in the toolbar. Enter your changes.