Defining Your Strategy

To define your strategy, use the Strategy Component (BC_COMPONENT_DFN), Strategy KPIs (BC_COMPNT_KPI), and Strategy Cause and Effect (BC_CAUSE_EFFECT1) components.

This topic discusses how to:

(Optional) Establish additional perspectives.
Create a strategy tree.
Define strategy components.
Associate KPIs with components.
(Optional) Define component cause and effect relationships.

Pages Used to Define Your Strategy

Page Name	Definition Name	Navigation	Usage
Tree Manager	PSTREEDEFN	select Tree Manager, then select Tree Manager select Scorecards, then select Define Strategic Goals, then select Strategy Tree	Create a strategy tree.
Strategy Component	BC_COMPONENT_DFN	select Scorecards, then select Define Strategic Goals, then select Strategic Components, then select Strategy Component Appears automatically when you add or edit strategy tree nodes.	Define a strategy component and specify its assessment method.
Strategy Component - Attachments	BC_COMPONENT_DFN2	select Scorecards, then select Define Strategic Goals, then select Strategic Components, then select Attachments	Associate attachments (any file type that is accessible through a URL) with a strategy component. You can view the file when you monitor the scorecard.
Strategy KPIs	BC_COMPNT_KPI	select Scorecards, then select Define Strategic Goals, then select Strategic Comp's KPI Set	Specify the KPIs that belong to a strategy component.
Strategy Cause and Effect	BC_CAUSE_EFF	select Scorecards, then select Define Strategic Goals, then select Cause and Effect Set	Indicate how a component influences other components.

(Optional) Establishing Additional Perspectives

In addition to perspectives that are delivered, you can define additional perspectives by adding translate values to the PERSPECTIVE_TYPE field. To define a new perspective:

Open the PERSPECTIVE_TYPE field definition in PeopleSoft Application Designer.
Open the field properties for PERSPECTIVE_TYPE.

You can also right-click and select Field Properties, or press Alt+Enter.
From a record field definition window, right-click the field, and select View Translates from the shortcut menu.
Select the Translate Values tab.

The Translate Values dialog box shows existing values for the field and enables you to add, change, or delete values. In the Last Updated section, the system displays information such as date, time, and user ID about the last update for the selected translate value.
Click Add to define a new value.
Enter the field value, effective date, long name, and short name for the new perspective.
Click OK to save your new perspective value.

Tree Manager Page

Use the Tree Manager page (PSTREEDEFN) to create a strategy tree.

Navigation

select Tree Manager, then select Tree Manager
select Scorecards, then select Define Strategic Goals, then select Strategy Tree

To create a strategy tree:

Create a new tree.

Use the BALANCED_SCARD structure, or make sure that the structure that you use meets the requirements for a strategy tree. Set the Use of Levels field to Strictly Enforced.
Define the tree levels.

You should consider using three: vision, strategic thrusts, and CSFs. The levels VISION, STRATEGY, and CSF are provided with the sample data.
Insert the tree nodes, starting with the root node.

Remember that the root node represents your organization's vision.
Complete the Strategy Component page for each node.

Strategy Component Page

Use the Strategy Component page (BC_COMPONENT_DFN) to define a strategy component and specify its assessment method.

Navigation

select Scorecards, then select Define Strategic Goals, then select Strategic Components, then select Strategy Component
Appears automatically when you add or edit strategy tree nodes.

Image: Strategy Component page

This example illustrates the fields and controls on the Strategy Component page. You can find definitions for the fields and controls later on this page.

Component Type

Select the type of strategy component to define. The type should correspond to the level of the strategy tree that it is on. Options are Critical Success Factor, Strategic Thrust, and Vision.

Approval Required

Select to require that the owner approve any manual changes to the assessment results for this strategy component.

This field is available for entry only if the Approval Required check box is selected on the Options page.

Owner ID

Select the individual who is primarily responsible for this component.

Perspective Type

Select the perspective within which to categorize this component.

The system uses this information to display component assessments grouped by perspective type.

Cause-Effect Map

Select the image that represents the cause-and-effect relationship for this component. This appears on the Strategy Detail - Strategy Map page when you view this component.

You must create the image in another application and add it to the image repository using PeopleSoft Application Designer.

Assessed Using

Select the assessment method for this component. Options are:

Best Case: Uses the best score that is attained by any strategy component in the level directly beneath.

Worst Case: Uses the worst score that is attained by any strategy component in the level directly beneath.

Most Frequent: Uses the most-often received score that is attained by the strategy components in the level directly beneath.

Weighting: Uses the relative weights and the associated weight scale for the KPIs that are attached to this component. Weighting can only be used with strategy components at the lowest level branch (terminal node) of the strategy tree. Use weighting when several KPIs are attached to a strategy component and you want to specify the relative importance of each KPI.

Tie Breaker

Specify how to score components that use the assessment method Most Frequent in the event of a tie (for example, equal numbers of multiple assessments, such as two greens and two reds).

Specifying Attachments

Access the Strategy Component - Attachments page to include any attachments with this component.

By completing this page, when you view this component on a scorecard, the Attachments link is enabled on some pages. When you click the attachments link, the system lists the report IDs that are specified in the attachments grid. The attachment can be any file type that you can access with a URL, such as streaming video, audio, or a website. For example, you could enable employees to view a video of an executive from your organization. Report IDs must be set up in PeopleSoft Warehouse.

Report ID

Select a file to associate with this component.

This file must be established in the Reports Metadata table (PF_META_RPT_TBL). In the report metadata setup, the report launch path should always be a URL, not the physical path to the file. For example, these are valid report launch path entries:

http://mydomain/reportpath/myfile.type
http://www.peoplesoft.com/reports/myreport.xls
ftp://ftpserver/reportpath/myfile.type
ftp://ftp.peoplesoft.com/reports/myreport.xls
gopher://gopherserver/reportpath/myfile.type
gopher://gopher.peoplesoft.com/reports/myreport.xls

When you use Microsoft Excel files, and other file types, the system opens the specific file.

Note: You should use reports that are static in nature because the report ID is defined by report metadata, which must be updated whenever a report is modified.

Strategy KPIs Page

Use the Strategy KPIs page (BC_COMPNT_KPI) to specify the KPIs that belong to a strategy component.

Navigation

select Scorecards, then select Define Strategic Goals, then select Strategic Comp's KPI Set

Image: Strategy KPIs page

This example illustrates the fields and controls on the Strategy KPIs page. You can find definitions for the fields and controls later on this page.

Specifying KPIs for Weighted Components

Weight Scale ID

If the component uses weighting to determine its assessment, select the defined weight scale upon which to base results.

KPI ID

In the KPIs grid, select the KPIs that are associated with this component.

Weight Factor Allocation

For each KPI, enter its relative weight (percentage based).

The total of all the KPI weight factors must equal 100.

Distribute Weight Evenly

Click to populate the Weight Factor Allocation field equally among all KPIs within the grid.

Specifying KPIs for Components Using Other Assessment Methods

KPI ID

In the KPIs grid, insert the KPIs that are associated with this component .

(Optional) Strategy Cause and Effect Page

Use the Strategy Cause and Effect page (BC_CAUSE_EFF) to indicate how a component influences other components.

Navigation

select Scorecards, then select Define Strategic Goals, then select Cause and Effect Set

Image: Strategy Cause and Effect page

This example illustrates the fields and controls on the Strategy Cause and Effect page. You can find definitions for the fields and controls later on this page.

This page is optional. By completing it, you can see a cause-and-effect view of the components of a scorecard, through which you can navigate to help analyze and interpret assessment results. The affected component does not need to be on the same strategy tree. This enables you to view the detail about a component that affects this strategy, but isn't necessarily part of it.

To define which components the current component affects, and how it affects them, add rows in the Impacted Components grid and complete these fields:

Component ID

Select a component that is affected by the current component.

Cause-and-effect relationships should be between the same component types; for example, between two CSFs, but not between an ST and a CSF.

Impact Type

Specify how each component in the grid is affected by the current component. Options are:

No Impact: Select if the component doesn't affect it directly, but might have some relationship that you want to track.

Positive Impact: Select if the component improves its outcome.

Negative Impact: Select if the component worsens its outcome.