Performance Analytics concepts

Performance Analytics uses terms and concepts that can differ from industry norms due to the unique nature of the ServiceNow platform.

Note:

Performance Analytics is used by other applications, such as Benchmarks. The information below describes the core Performance Analytics functionality. For information about other applications that use Performance Analytics, refer to the documentation for those applications.

Performance Analytics includes the following concepts and components:

Key components

Indicators

(KPIs) define a performance measurement taken at regular intervals of a business service, an activity, or organizational behavior. These performance measurements result in a series of indicator scores over time. Businesses track these scores to measure current conditions and to forecast trends.

Technically, an indicator combines a data set and a data aggregate, such as Count, along with optional conditions.

Key characteristics of indicators include:

• Indicator scores can be generated automatically from a set of records defined in an indicator source, entered manually, or calculated from other indicators.
• Indicator scores can be viewed or analyzed in Platform Analytics data visualizations and KPI Details. In the Core UI, view them in the Analytics Hub or in widgets on dashboards.

For convenience, you can organize indicators thematically into an indicator group.

Synonyms: Metrics, business metrics, KPIs

Breakdowns and elements

enable you to group or filter indicator scores by a qualitative attribute such as Priority, Category, or Assignment Group. You can apply a breakdown on the Analytics Hub, in KPI Details, and on dashboards.

For example, you can look at the Number of Open Changes by Assignment Group. Or you can see the Number of New Changes by Priority.

The values for each breakdown are called breakdown elements. For example, the Priority breakdown may have the elements Critical, High, and Low. Breakdowns are categorized as automated, manual, or external, depending on where these elements come from. Automated breakdown elements are specified in breakdown sources. Manual breakdowns have their elements entered manually to define an organization. Lastly, an external breakdown specifies the JDBC data source and SQL statement for retrieving breakdown elements.

You cannot apply more than two levels of breakdown to an indicator.

Synonyms: dimensions, drill-downs

Data collector

is the engine that takes periodic snapshots of your process tables and stores them in the Scores and Snapshots tables. You can set up data collector jobs to run automatically according to a schedule. Usually set a job schedule to match the frequency in the indicator source. One job usually generates scores for multiple indicators that use the same indicator source. You can also set up jobs that run manually, such as historical jobs, which you run only when collecting data for a new indicator.

Classic Visualizations

Analytics Hub

is an exploratory view of indicators, used for more detailed analysis. It lets you see trends, predictions, breakdowns, and associated records for a specific indicator. Set on the indicator record whether that indicator is to be included in the Analytics Hub .

The Analytics Hub was previously named the Detailed Scorecard.

Responsive dashboards in the Core UI

are collections of multiple Performance Analytics, reporting, and other widgets, arranged in a logical view for the audience. Dashboards can be responsive or non-responsive. To create or share a responsive dashboard, you need at least one role, but this can be any role. You can drag to move and resize widgets on responsive dashboards. Non-responsive dashboards use less flexible drop zone layouts, and require Performance Analytics roles to view, create, and edit.

Time series

can refer to either of the following items:

• A type of widget that aggregates and shows multiple scores of an indicator collected over a period. See Time series widgets.
• A statistical function applied to collected indicator scores over a time period in the Analytics Hub or in a widget, also called an aggregator. See Applying time series aggregations.

Targets

are goals your organization wants to achieve, operationalized as indicator scores. Targets enable you to visualize the difference between the desired score at a certain date and the actual score of an indicator.

A target can be personal or global. A personal target is visible only to the user that created it and appears as a light line. A global target is visible to all users and appears as a dark line. Personal targets appear only on the Analytics Hub, whereas global targets appear on the Analytics Hub and time series widgets.

Thresholds

define a normal range of scores for an indicator and alert you when certain events occurs, such as when a score reaches an all-time high or low.

When a threshold is triggered, the instance generates an email notification. This message is associated with the indicator and the message is directly available via the Analytics Hub.

A threshold can be personal or global. A personal threshold is visible only to the user that created it and appears as a light gray dotted line. A global threshold is visible to all users and appears as a dark gray dotted line. Personal thresholds appear only on the Analytics Hub for an indicator, while global thresholds appear on both the Analytics Hub and time series widgets.

Widgets

in Performance Analytics are reusable visualizations of indicator scores. For example, a widget can display the evolution of an indicator over time, how an indicator can be broken down, or how several indicators look side by side. Many variations are possible. Widgets are visible only when added to a dashboard.

Other concepts

Aggregate/Aggregation

can refer to either of the following functions:

• The Performance Analytics function of aggregating, or collecting, indicator scores over time. The indicator configuration includes the frequency with which indicator scores are collected.
• Statistical functions applied to collected indicator scores over a time period. For example, you can apply a 3-month SUM to indicator scores. Aggregation functions can be added either in the indicator form or later in the the Analytics Hub or widget. Aggregation functions in the Analytics Hub or widget are named time series.

Breakdown mappings

specify the relationships, or 'map,' breakdowns to indicator sources. A breakdown mapping either specifies a field on the indicator source or specifies a script that queries the indicator source. The latter is sometimes called a scripted breakdown mapping, and a breakdown with such a mapping is called a scripted breakdown.

Breakdown sources

specify which unique values, called breakdown elements, a breakdown contains. A breakdown source is defined as a set of records from a table or database view or as a bucket group. Multiple breakdowns can use the same breakdown source. For example, instead of seeing ALL assignment groups for the Number of Open Changes indicator, you can limit the element list to just those groups that are part of the change process by configuring the Breakdown Source.

Bucket groups

are used to recategorize data so it can be used as a breakdown, for example by grouping a range of values into discrete buckets.

To work with a bucket group, create a breakdown source that uses Bucket [pa_buckets] as the facts table and specifies the bucket group in a condition. If a breakdown built on this source uses a breakdown mapping with a script, the breakdown groups the values that the script returns into buckets. If the breakdown mapping specifies a field instead of using a script, the breakdown groups the values of the mapped field into buckets.

In the data architecture, bucket groups are defined in Bucket Group [pa_bucket_groups] records and buckets in Bucket [pa_buckets] records. Each Bucket [pa_buckets] record contains a Bucket Group field that is a reference to a Bucket Group [pa_bucket_groups] record.

Day

A day in Performance Analytics is always defined as 24 hours. Performance Analytics does not use the concept of 'business days.'

Indicator sources

are data sets consisting of filtered records from one table or database view. An indicator source configuration specifies a table, such as Incident [incident], conditions for filtering records from that table, and a frequency that you base on the conditions. An indicator source cannot specify a rotated table. Multiple indicators can use the same indicator source. Data collection jobs query the database once for each indicator source. Thus, all indicators that use the same indicator source get data from the same point in time.

Typically, an indicator tracks the situation on a certain date. The indicator source conditions usually include a date-related filter, such as [Opened][on][Today]. Indicators collected less frequently might specify a larger date range, such as [Closed][on][This month].

Scripted breakdown

is a breakdown that uses a script to query the indicator source as its breakdown mapping.

Snapshots

are the lists of records (sys_ids) that are collected at the time that the scores for those records are collected. A snapshot is made only for automated indicators with Collect records selected.

The snapshot/list of records can be retrieved in the Analytics Hub.

Snapshots are kept for the main indicator and for first-level breakdowns. Second-level breakdown snapshots are derived as an intersection of the two first-level breakdown snapshot lists.

• Put a Spotlight on records
  Use the Spotlight feature to illuminate records that you might overlook.
• Try out Complimentary Performance Analytics for Incident Management
  Complimentary Performance Analytics for Incident Management is a limited version of Performance Analytics that is included in the base system, enabling you to become familiar with the functionality. Subscribe to Performance Analytics for complete functionality.