HOPEX IRM > HOPEX Enterprise Risk Management > Managing Risks > Contextualizing Risks
Contextualizing Risks
Contextualizing a risk consists in defining its scope. Different types of components can be included in the scope.
To contextualize a risk:
*In the properties of a risk, expand the Scope section and connect objects in the relevant tabs.
• Entities concerned by the risk. For more details, see Managing 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.
*Defining entities on risks is a pre-requisite to risk assessment. See also Preparing the Assessment Work Environment.
• Business Processes and Organizational Processes exposed to the risk. For more details, see Managing Processes.
*A business process represents a system that offers products or services to an internal or external client of the company or organization. At the higher levels, a business process represents a structure and a categorization of the business. It can be broken down into other processes. The link with organizational processes will describe the real implementation of the business process in the organization. A business process can also be detailed by a functional view.
*An organizational process describes how to implement all or part of the process required to make a product or handle a flow.
• Objectives and Requirements expected related to risk management. For more details, see Consulting Requirements.
*An objective is a goal that a company or 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 met within the context of a project. This project can be a certification project or an organizational project or an information system project.
• Applications: for more details, see Managing Applications.
*An application is a set of software tools coherent from a software development viewpoint.
• Business Lines: for more details, see Managing Business Lines.
*A business line is a skill or grouping of skills of interest for the enterprise. It corresponds for example to major product segments, to distribution channels or to business activities.