Control Attributes
CUBE Controls have additional data fields to capture information accurately and ensure easy identification and comparison. These attributes include:
- Control Name
- Control Owner
- Control Type
- Control Frequency
- Control Automation
- Control Theme
- Products
Control Name
The Control Name should be concise and clearly state the control's goal in 3-7 words. It should also logically end with 'Review' or 'Monitor' to facilitate easy understanding without having to read the description.
Control Owner
The Control Owner field specifies the business area responsible for owning and operating the control. It should not contain the names of individuals or specific role titles. Examples of values used in the Control Owner field from Global Markets are listed below:
- Front Office
- Operations
- Technology
- Product Control
- Finance Control
- Compliance
- Market Risk
- HR
- Legal
Control Type
Customers have various Control Types in their data, but CUBE research identifies the most common ones as 'Prevent' and 'Detect'. CUBE may add more Control Types as the network and industry evolve.
Control Frequency
Control Frequency determines the frequency at which a control is operated. There is a wide range of customer frequencies used, and these values can be converted to CUBE values using the table found in the Appendix that shows customer values and how CUBE interprets them. CUBE's frequencies are:
- Real time
- Event-Driven
- Daily
- Weekly
- Bi-weekly
- Monthly
- Quarterly
- Semi-Annually
- Annually
Control Automation
The Control Automation attribute reflects the level of automation for the control across Customers matched with the CUBE control. It can have four values: Manual, Semi-Automated, Automated, or Insufficient Network Data. 'Insufficient Network Data' is used if the 2 or more rule is not met.
Control Theme
CUBE assigns one or more Control Themes to each control to group them into cross-business and cross-Index views. The Control Theme attribute represents the high-level activities related to the CUBE control. For instance, if a customer wants to find payments-related CUBE Controls and their own associated controls across the investment bank, they can select 'Payments' from the list of CUBE Control Themes.
Control Theme is CUBE SME-driven and can cover multiple CUBE Processes. CUBE identifies Themes based on the business function and subject matter of the control. Refer to the Appendix for Control Theme field values.
Product
Controls can be generic, such as training, or product-specific. The Product fields enable data to be aggregated and analysed for these specifics. CUBE applies four Product fields to its controls, namely:
- Asset Class
- Trading Type
- Settlement Type
- Instrument Type
Each CUBE Control must have a value for each of these fields, which are listed in the Appendix. The values are chosen through an SME review of the CUBE Control and matched customer controls.