Processing KPIs and Scorecards

This chapter provides an overview of key performance indicator (KPI) and scorecard processing and discusses how:

• Process KPIs.

• Process scorecards.

See Also

Streamlining Processing with Jobstreams

Understanding KPI and Scorecard Processing

This section discusses:

• Engines used.

• Delivered jobstreams.

• KPI processing.

• Scorecard processing.

After KPI and scorecard setup is complete, processing takes place through PeopleSoft EPM. This section assumes that you are already familiar with run controls, jobstreams, and process scheduler. Review your PeopleSoft EPM Foundation and PeopleTools documentation if these are unfamiliar terms.

This chapter provides an overview of both the KPI and scorecard processes. KPIs must be processed prior to processing scorecards. However, be aware that if you process scorecards using the delivered jobstreams, you may not need to run the KPI Analyze jobstream independently, as it is included in the BC_ANALYZE jobstream for scorecard assessment.

The scorecard and KPI processes both use several different PeopleSoft Application Engine programs. This section lists the engines used and the jobstream definitions that we provide with the system. These jobstreams are used to initiate the processing from PeopleSoft EPM.

Engines Used

PeopleSoft Enterprise Performance Management applications use engines to run each process. Engine metadata is delivered with the system; unless you're revising the application you shouldn't need to modify it. This metadata stores information about the various PeopleSoft Application Engine programs that are used within an engine. The following table lists the delivered engines that are used by PeopleSoft Scorecard when processing KPIs and scorecards using the delivered jobstreams and their associated jobs:

The Merge engine is used by many applications within the PeopleSoft Enterprise Performance Management suite. It moves enriched data from temporary tables into the final permanent tables for use as input for other processes. In most jobstreams, the Merge engine is the last job. (The exception to this rule is when you use the POST job last in the jobstream.) During processing, data is copied into temporary tables. When processing is complete, the final tables are updated.

Delivered Jobstreams

Each main engine is associated with a job ID using the Job Metadata page. Jobs are associated with a jobstream using the Jobstream page. A job must be unique across all jobstreams, so if you require additional jobstreams, you first need to create new jobs to use in each jobstream. The following table lists each batch process, the delivered jobstream, and the engines and job IDs that are used in that jobstream:

KPI Processing

The KPI Analysis jobstream (KP_ANALYZE) resolves the value of key performance indicators, evaluates the KPI dimension members against their targets, and assigns the achieved assessment. Based on the business rules that you associate with a KPI, each KPI is given an assessment, or rating, that you use to identify out-of-tolerance conditions or performance opportunities. KPI Analysis is a batch process that you initiate by submitting a run control request. This process comprises several PeopleSoft Application Engine programs. You specify which business unit, scenario, and fiscal year and period ranges to process.

Note. You don't need to run the KPI Analysis jobstream by itself if you use the BC_ANALYZE jobstream to run the scorecard assessment process, because it includes the KPI_ANALYZ engine. However, you may want to run KPI Analysis independently when initially establishing your KPIs to verify that they are set up correctly.

The KPI Analysis jobstream consists of these general steps (this is a simplified description of what actually occurs):

1. The system retrieves the KPI data elements that are used from the PeopleSoft EPM tables.

2. The system retrieves the appropriate data, using the SQL built by the data element definitions and related calculation definitions.

3. The system calculates the KPIs:

   • For calculated KPIs, the engine uses the SQL that is generated from the assigned calculation ID to process and calculate the data and determine the results.

   • For those KPIs that are derived from other KPIs (defined by the KPI Type field on the KPI Definition page), the values for the source KPIs are determined first; then the derived KPIs are assigned those values.

     Source KPIs are not assessed in the current run; they must be previously assessed for use with derived KPIs.

   • Manual KPIs are not calculated.

     You must enter their values prior to running KPI analyze or scorecard assessment.

   • For KPIs that have a dimension tree defined (hierarchical KPIs), the system calculates the values for each node.

4. The system determines assessment results for each KPI dimension member:

   • The system retrieves and calculates the target value for each KPI dimension member.

   • Each KPI dimension member is evaluated against its target, or the default target table, and given the appropriate assessment ID based on the target rules.

5. If any composite KPIs are defined, then the system calculates and assesses the composite KPIs.

6. The system determines and processes any actions that are required (sends emails or populates worklists) as a result of the assessment.

7. KPI information is published (if the option is selected on the KPI Options page).

8. When the process is complete, the information is merged from temporary tables to these permanent fact tables: KP_KPI_CALC_F00, KP_KPI_ASMT_F00, KP_DATAVALS_F00, and KP_TRGTVALS_F00.

The system uses the following tables during KPI analysis processing:

Note. This does not include the supporting PeopleSoft EPM tables that the system accesses: the scenario tables, the calendar tables, the metadata tables (record, tablemap, datamap, constraint, engine metadata, job metadata, jobstream metadata), record suite tables, process tables, and so on.

Scorecard Processing

The delivered jobstreams for processing scorecards are:

• BC_ANALYZE.

  Assesses KPIs and scorecards, which determines the scores for the components of a scorecard. You must run this prior to viewing a scorecard.

• BC_ASSESS

  Assesses only scorecards.

  Typically you will use this jobstream only when you've made changes to scorecards, but not the underlying KPIs. If the KPI data has also changed you should run BC_ANALYZE to process both KPIs and scorecards.

• BC_OVRASMT

  Applies manual assessments.

  When viewing scorecards, you can override the assessments if you have the appropriate security. This jobstream updates the scorecard by applying the manually entered assessments and reevaluating the scores for each component.

Scorecard Assessment

During scorecard assessment processing, these steps occur:

1. The system calculates and assesses KPIs.

   (This depends on which scorecard assessment jobstream you run. Of the jobstreams that we provide, BC_ANALYZE does this step because it includes the KPI_ANALYZ engine; BC_ASSESS does not.)

2. The system generates scorecards for each user and role user that is specified on the distribution list.

3. The system scores each strategy component, based on the assessment method that is defined on the Component Definition page.

4. The system merges the information from temporary tables to these permanent fact tables: BC_ASSESS_F00 and BC_PRSPCTV_F00.

The following diagram provides an overview of process flow for scorecard assessments, which includes creating personal scorecards, loading strategy tree nodes, getting scorecard users, getting KPIs and dimension members for all scorecards, getting KPI calculation and assessment values, assessing the lowest level scorecard components, assessing the parent component levels, and assessing perspectives.

Process flow for scorecard assessment

These tables are used during processing:

This lists only those tables that are used by scorecard assessment. The tables that are affected by KPI assessment are listed in the KPI processing section.

Note. This list does not include the supporting PeopleSoft EPM tables that the system accesses: the scenario tables, the calendar tables, the metadata tables (record, tablemap, datamap, constraint, engine metadata, job metadata, jobstream metadata), record suite tables, process tables, and so on.

Manual Assessments

If you enter manual assessments when viewing a scorecard, run the Apply Manual Assessments jobstream (BC_OVRASMT) to apply those assessments and update your strategy component scores.

During manual assessment processing, these steps occur:

1. The system updates the KPI assessment using the manual assessment values.

2. The system reevaluates the strategy components.

3. The system merges the information from temporary tables to these permanent fact tables: BC_ASSESS_F00, KP_KPI_OVRD_F00, KP_KPI_ASMT_F00, and BC_PRSPCTV_F00.

The following tables are used during processing:

Note. This list does not include the supporting PeopleSoft EPM tables that the system accesses: the scenario tables, the calendar tables, the metadata tables (record, tablemap, datamap, constraint, engine metadata, job metadata, jobstream metadata), record suite tables, process tables, and so on.

See Also

KPI Processing

Assessment Methods

Processing KPIs

This section provides an overview of KPI run groups and discusses how to:

• Define KPI run groups.

• Run KPI processing.

Understanding KPI Run Groups

KPI run groups enable you to define a subset of KPIs to process. You can opt to use a KPI run group when you process KPIs to save processing time. Typically you will use KPI run groups during the implementation phase when you are setting up your KPI definitions and want to validate them by running the KPI Analysis process and reviewing the results. If you do not use a KPI run group when processing KPIs, then all KPIs that satisfy the input run parameters are processed.

To define the KPIs that compose a KPI run group, you can use a combination of one or more of the following:

• A constraint that is based on the KPI Definition table.

• A specific individual KPI.

• A KPI family.

Pages Used to Process KPIs

Defining KPI Run Groups

Access the KPI Run Group page (Key Performance Indicators, Administration, Calculate, KPI Run Group).

Build SQL

Click to update the SQL for a KPI run group that uses a constraint. This is only required if the constraint definition that is used for the KPI Run Group has been modified. When you initially create a KPI run group that uses a constraint, when you save the definition the system generates the appropriate SQL for the constraint. However, if you subsequently modify the constraint definition that is used for a KPI Run Group, you must click this button to update the associated SQL because the Save button will be unavailable. See Running Mass Compile.

Create New Constraint

Click this link to access the Constraint page in Add mode, where you can add a new KPI-based constraint to associate with this KPI run group. See Setting Up Constraints.

To specify the KPIs that compose the KPI run group, add rows within one or more of the following grids:

KPI Constraints - Constraints Tab

KPI Constraints - Audit Details Tab

KPI Families

KPIs

Running KPI Processing

Access the Run KPI Processing page (Key Performance Indicators, Administration, Calculate, Calculation and Assessment).

Jobstream Type	This field is unavailable for entry, and contains Single Period as the engine can be run only for a single period.
Business Unit and Scenario	Specify the business unit and scenario to process.
Year and Period	Specify the fiscal year and period for which to calculate and assess KPIs.
KPI Run Group	Optionally, select a KPI run group to limit processing to a subset of KPIs. To establish KPI run groups, use the KPI Run Group page. See Defining KPI Run Groups.
Jobstream ID	This field contains KP_ANALYZE, which is the delivered jobstream for processing KPIs.

Processing Scorecards

This section discusses how to run scorecard processing.

Pages Used to Process Scorecards

Running Scorecard Processing

Access the Run Jobstream page (Scorecards, Administration, Assessments, Scorecard Assessment) or Run Multiple Jobstream page (EPM Foundation, Job Processing, Update/Run Jobstreams, Run Multiple Jobstream), depending on your requirements.

Complete the run parameter fields:

Warning! Do not select the As Of Dated Jobstream check box. This is not supported for Scorecard applications. If you select this option, your results will be incorrect.