HOPEX Aquila Doc FR

HOPEX UAF > Operational Viewpoint > Operational - Structure > Describing Operational Performers

Describing Operational Performers

An Operational Performer is a skill or grouping of skills of interest for the enterprise.

A Operational Domain is a grouping of Operational Performers and their associated Operational Activities on the conjunction of two main criteria. 1. Their need in accomplishing one or more Capabilities. 2. The common skills and functionalities required to accomplish these Capabilities.

Accessing the list of Operational Performers

To access the list of Operational Performers:

From the Operational navigation menu, select Structure.

The list of Operational Performers connected to the current enterprise appears.

Operational Performer properties

The Characteristics properties page of a Operational Performer provides access to:

• its Owner, by default on creation of the Operational Performer, the current enterprise.

• its Name,

• the text of its Description.

• its Owned Realizations

For more details on fulfillments, see Capability Fulfillment.

With HOPEX UAF, an operational performer is described by the following pages:

• the Required Abilities page is used to specify a list of skills and functionalities required by the business.

For further details, see Personnel Constraints.

• the Usage page, which provides access to the components owning the current object.

• the Performed Process page, which provides access to the operational activities executed.

• The Reporting page provides access to the Realizations of an architecture building block and its components,

For more details on use of a breakdown report, see Handling a Breakdown Report

• the Diagram page is used to manage the Operational Performer diagrams:

• Operational Performer Structure Diagram,

• Operational Performer Tree Diagram,

• Scenario of Operational Flow Diagram.

Operational Performer Structure Diagram

The Operational Performer Structure diagram describes the components of the Operational Performer and the connections between components. It thus describes:

• the Operational Roles,

An Operational Role represents the configuration of a Operational Performer within another one.

• access points: service points and request points.

A service point is a point from which a system receives a request from another system and provides the requested service.

A request point is a point by which an agent requests a service from potential suppliers.

For more details on service points and request points, see Describing Service and Request Points.

• service interactions

A Service Interaction represents an interaction for service purpose between entities in a specific context inside or outside a company. These entities can be enterprise org-units, applications, activities or Personnel Functions, as well as external org-units. The content of this interaction is described in an Interface.

For more details on service interactions between components, see Creating a Service Interaction from a diagram.

Operational Performer Tree Diagram

The Operational Performer Tree diagram describes the tree structure of the Operational Performer. Such diagram describes the current Operational Performer and its sub-Operational Performers.