Goals Introduction

Currently, the only goal available is the Data Owner’s Election. Data Owners are responsible for protecting the data within a specific resource. Administrators use the Goals process so that those who are the most knowledgeable regarding the use of a specific resource can elect (via a crowd sourcing process) the most suitable data owners for a specific resource.

Note: The right to view the Goals tab is assigned by default only to the administrator capability.

A running goal refers to each determination of a data owner of a resource in a crowd sourcing process, while a goal refers to a collection of all the determinations of data owners of resources in a crowd sourcing process. Therefore, a goal is a collection of activities.

For example, if the goal is to determine the identity of the data owners for five business resources in a file server application, that goal consists of five running goals – one for each resource.

The goal lifecycle stages are:

Goal creation

First, an administrator creates goal activities, specifying the goal type, application, scope, and settings.

Goal is Pending for Execution

After goal creation, but before the system sends emails to participants, an administrator checks the goal status, including the goal participants selected, and the data owner candidates selected, to validate successful goal creation.

Election

After goal execution, participants (who were decided upon in the creation process) vote for data owners.

Appointment

Reviewers review the selected data owners (unless the administrator choses the automatic selection of data owners).

Completed

A goal is completed when all the goal activities have been completed (for example, all data owners have been assigned).