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 individuals who are most knowledgeable about the use of a specific resource can elect (via a crowd sourcing process) the most suitable data owners for that resource.

Note

By default, the ability to view the Goals tab is assigned only to users with administrator capabilities.

Running Goal vs Goal

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

For example, if the goal is to identify the data owners for five business resources in a file server application, that goal would consist of five running goals — one for each resource.

The goal lifecycle stages are:

Goal Creation - An administrator creates goal activities, specifying the goal type, application, scope, and settings.

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

Election - After goal execution, participants (who were selected in the creation process) vote for data owners.

Appointment - Reviewers review the selected data owners, unless the administrator opts for automatic selection of data owners.

Completed - A goal is considered completed when all goal activities have been completed (e.g., when all data owners have been assigned).