Concept: Hierarchies and Organizations in People Analytics

When you configure People Analytics for the worker and hiring pipelines, you select which fields to include in the application. Workday groups the hierarchy and organization-related fields into these categories:

Primary Hierarchy

Secondary Hierarchy

Organization Details

Workday makes the hierarchy categories and target field names generic to give you flexibility when deciding which hierarchies that you assign to each category. When deciding which hierarchies to use, consider how they affect the rest of the application.

The hierarchies and organizations you include in People Analytics determine:

How Storyteller groups data into different combinations of dimensions for analysis. Workday uses each field value as a dimension for grouping and analyzing data before aggregating metrics.

How Workday enforces contextual security in the application. When you select either the Primary Hierarchy or Secondary Hierarchy for security, Workday uses all source fields mapped in that category for constraining viewer access to data. The hierarchy that you specify for security must be a valid Prism securing entity. See Concept: Security in People Analytics.

Which dimensions to display to application viewers. The Level 1, Level 2, and Level 3 target fields that you include from both hierarchy categories will display as application filters to viewers. See Concept: Refining in People Analytics.

The target fields that you configure in the Primary Hierarchy and Secondary Hierarchy categories must be identical in the worker and hiring pipelines. Make sure that you:

Select the same or compatible source fields.

Include the same target fields in each pipeline.

Enter the same display name.

Hierarchy Requirements

The hierarchies you use for the Primary Hierarchy and Secondary Hierarchy must meet these requirements:

Level consistency. Every child node of a particular parent must be at the same level.

Single hierarchy. Child nodes can only have 1 parent.

Population consistency. The worker population can be assigned to 1 hierarchy only. No duplicates are allowed.

When you configure constrained access to People Analytics using either the Primary Hierarchy or Secondary Hierarchy, the hierarchy must also meet these requirements:

Security consistency. Users must be constrained at the specified levels in the hierarchy you use for security. Example: You specify Primary Hierarchy for security and map source fields to the Level 1, Level 2, and Level 3 target fields. Users must be constrained at the levels specified for Level 1, Level 2, and Level 3. Any user constrained at lower levels won't see any focus insights in the application.

Supported hierarchy type. The hierarchy must be one of these types:

Business Unit Hierarchy

Company Hierarchy

Cost Center

Cost Center Hierarchy

Custom

Custom/Financial

Custom/Staffing

Location Hierarchy

Region

Region Hierarchy

Supervisory

The Assigned Organization Target Field

Workday uses the data in the Assigned Organization target field to determine which organization the worker is currently assigned to. Typically, this is Supervisory Organization. People Analytics automatically detects changes due to a reorganization. It ignores focus insights that result from workers being reassigned to different organizations, presenting significant focus insights in the application.

Target Field Descriptions

The Primary Hierarchy category includes these target fields:

Target Field	Notes
Assigned Organization	The organization that is assigned to the primary position of the worker or the primary position of the job requisition. Select a field that accurately reflects the current organization assigned to or associated with a worker or job requisition. Typically, this is Supervisory Organization, but in rare cases might be a different organization type, such as a custom organization or Cost Center.
Level 1	The 1st level of the hierarchy that you want to analyze. Typically, this is the 2nd level from the top of the organization, 1 level below the CEO. The field you select must be in the same organization hierarchy as the Assigned Organization.
Level 2	The 2nd level of the hierarchy that you want to analyze. Typically, this is the 3rd level from the top of the organization, 2 levels below the CEO. The field you select must be in the same organization hierarchy as the Assigned Organization. When you opt into the level below this level, you must opt into this level, too.
Level 3	The 3rd level of the hierarchy that you want to analyze. Typically, this is the 4th level from the top of the organization, 3 levels below the CEO. The field you select must be in the same organization hierarchy as the Assigned Organization.

The Secondary Hierarchy category includes these target fields:

Target Field	Notes
Level 1	The 1st level of the hierarchy that you want to analyze. Typically, this is part of a geographical hierarchy, such as market region.
Level 2	The 2nd level of the hierarchy that you want to analyze. Typically, this is part of a geographical hierarchy, such as country. When you opt into the level below this level, you must opt into this level, too.
Level 3	The 3rd level of the hierarchy that you want to analyze. Typically, this is part of a geographical hierarchy, such as city. When you constrain access to the application data using the secondary hierarchy, then this level must be associated with the worker, and you must opt into this field.

The Organization Details category includes these target fields:

Target Field	Notes
Organization Level	The number of levels down from the top level of the organization in the primary hierarchy to the worker’s level. Applies to the worker pipeline only.
Management Level	The management level of the worker or the job profile on the job requisition.
Cost Center	Cost center (or equivalent) used for reporting. If you use Cost Center as the primary or secondary hierarchy, then you can select a field from a different organization that Workday can use for providing more details on the worker or job requisition.
Company	Company name or ID of the company. Applies to the worker pipeline only.