HOPEX Risk Mapper : HOPEX Risk Mapper : Risk Treatment and Controls : Controls : Control Implementation
   
Control Implementation
Installation of a control frequently consists of checking that a management rule (constraint) is effectively applied, either manually or by an IT program.
*A constraint is a declaration that establishes a restriction or business rule that must be applied on execution of processing.
You can specify the management rules associated with a control in the Management Rules tab of its properties page.
The control can be implemented by:
a process: this can be the business process on which the control is implemented or it can be a risk preventive business process (example: "Account manager training" to prevent the "Overselling" risk)
*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 operation: this is the operation on which the control is executed.
*An operation is a step in a process, executed by an org-unit within the context of an activity. An operation can be industrial (manufacturing a component), logistical (receiving a delivery), or can involve information processing (entering an order). An operation can be subdivided into elementary tasks.
It is possible to specify processing that will implement the control or the management rules associated with the control. You can specify control implementation means in the Characteristic tab, Scope section.