Defining risk characteristics
To access characteristics of a risk:
1. From the list of risks, click the Properties icon related to the risk.
The Overview property page appears.
2. Click the Characteristics tab.
*You can display (or hide) tabs using the button.
The Characteristics property page appears.
*You can display (or hide) sections using the Manage sections button.
Defining risk characteristics 
In the Characteristics section, you can fill the following elements:
Identification Code
Name
Risk severity (Major box)
Risk owner
*By default the owner is the user who created the risk.
Risk Identification Mode
Risk Description
Status
*This field cannot be modified. It is automatically filled by the Workflow related to the risk.
Defining Risk responsibilities 
In the Responsibilities section, you can assign a level of responsibility to different persons.
Specifying Responsibilities
To assign a level of responsibility to the persons concerned by the risk:
*Create responsibility assignations in one of the following tabs:
Responsible
Accountable
Consulted
Informed
Responsibility levels
The proposed responsibility levels are as follows:
 
Responsibility
Explanation
Responsible
Persons responsible for execution of required actions.
Accountable
Persons reporting on progress of planned actions and making decisions.
There is only one "Accountable" for each action.
Consulted
Persons consulted as first priority before an action or decision.
Informed
Must be informed after an action or decision.
 
Defining the Scope of a Risk 
In the Scope section, you can connect objects to the risk or see the objects connected to the risk.
The risk can be connected to the following objects:
Objects from process hierarchy such as Process Categories, Processes and Operations.
*A process category defines a group of processes. It is linked to a Process Map or a higher level Process Category. It regroups several Processes and/or other categorized elements (e.g. Value Streams, Applications). It serves as an intermediate categorization level in the process hierarchy, so as to provide a guided and progressive access to finer grained processes.
*A process is a set of operations performed by org-units within a company or organization, to produce a result. It is depicted as a sequence of operations, controlled by events and conditions. In the BPMN notation, the process represents a sub-process from the organizational point of view.
*An operation is an elementary step in process executed by an org-unit. It cannot be broken down. An operation can be industrial (manufacturing a component), logistical (receiving a delivery), or can involve information processing (entering an order).
Entities
*An entity can be internal or external to the enterprise: an entity represents an organizational element of enterprise structure such as a management, department, or job function. It is defined at a level depending on the degree of detail to be provided on the organization (see org-unit type). Example: financial management, sales management, marketing department, account manager. An external entity represents an organization that exchanges flows with the enterprise, Example: customer, supplier, government office.
Objectives and Requirements expected related to risk management.
*An objective is a goal that a company/organization wants to achieve, or is the target set by a process or an operation. An objective allows you to highlight the features in a process or operation that require improvement.
*A requirement is a need or expectation explicitly expressed, imposed as a constraint to be respected within the context of a project. This project can be a certification project, or an enterprise information system organization or modification project.
Applications,
*An application is a software component that can be deployed and provides users with a set of functionalities.
Business Lines
*A business line is a high level classification of main enterprise activities. It corresponds for example to major product segments or to distribution channels. It enables classification of enterprise processes, organizational units or applications that serve a specific product and/or specific market.
Defining risk typology, causes and consequences 
In the Analysis section, you can fill the following elements:
Risk types
*A risk type defines a risk typology standardized within the context of an organization.
Risk factors
*A risk factor is an element which contributes to the occurrence of a risk or which triggers a risk. Several Risks can originate from a same Risk Factor Examples: the use of a hazardous chemical product, the complexity of an application, the size of a project, the number of involved parties, the use of a new technology, the lack of quality assurance, the lack of rigor in requirements definition…
Risk consequences
*A risk consequence can be positive or negative. It is associated with a type, which enables its characterization, for example: image, environment, employees.
Associated Risks