Charta is on Google Play: practise on the go. Get the app
Charta

Summarize the features of sound data architecture and IT infrastructure, along with good practice in risk reporting.

FRM® Part I · Foundations of Risk Management · Principles for Effective Data Aggregation and Risk Reporting · FRM1.FR.7.d

The idea

Principle 2 requires data architecture and IT infrastructure that fully support aggregation and reporting, in normal times and in times of stress or crisis. Sound design means integrated data taxonomies and architecture across the banking group, documented definitions, named data owners, and as little manual intervention as possible. Principle 3, on accuracy and integrity, adds that a bank should strive for a single authoritative source of risk data for each type of risk. Good reporting practice has five features. Reports are accurate and precise. They are comprehensive across all material risk areas, including forward-looking and stress information. They are clear and useful for each recipient, balancing data, analysis and commentary. Their frequency matches the need and rises in stress, and they go to the right people with confidentiality preserved. Common mistakes are designing only for normal conditions and sending the same report to everyone. Exam point: infrastructure must work under stress, and reports must be tailored to the user.

A practice question

From the question bank, with the reason each wrong option is wrong.

Which of the following is a feature of sound risk data architecture?

  1. Each business line maintaining its own data definitions in order to preserve flexibilityWhy not: Separate definitions block firm-wide aggregation. Integration and common definitions are required.
  2. Integrated taxonomies and architecture across the group, with documented definitions and authoritative sources - correct
  3. Reliance on manual spreadsheet adjustments by analysts to reconcile data coming from different systemsWhy not: Manual adjustments increase error and delay. Sound design minimises manual intervention.
  4. Several competing sources for each data element, so that users may choose the one they preferWhy not: Soundness calls for a single authoritative source for each element, not several competing ones.

Sound architecture is integrated across the group, with common taxonomies, documented definitions, authoritative sources and little manual intervention.

A harder one

A bank's report to the board runs to 200 pages of tables with no commentary, and members find it hard to see the key risks. Which reporting principle is most directly breached?

  1. Accuracy, since the numbers in the tables must be wrong if the board cannot interpret themWhy not: The stem does not say the figures are wrong. The problem is presentation and usefulness.
  2. Distribution, since the report has not been sent to the people entitled to receive itWhy not: Nothing suggests it went to the wrong people. It reached the board but is hard to use.
  3. Clarity and usefulness, since reports should be easy to understand yet comprehensive and tailored to the recipients - correct
  4. Frequency, since a long report implies that it is produced too rarely to be usefulWhy not: Length is not a sign of frequency. The issue is design, not timing.

Risk reports should be clear and useful: understandable, balanced between data, analysis and commentary, and tailored to the recipient. A mass of tables without commentary fails that.

The hardest tier

A risk report is accurate, comprehensive and clear. However, it is circulated to a wide list that includes staff with no need for the sensitive data, and the risk committee receives it only after its meeting. Which reporting principle is most directly breached?

  1. Comprehensiveness: the report should cover all of the material risk areas of the bank, by entity and risk typeWhy not: The stem says the report is comprehensive. The failure lies in who receives it and when.
  2. Distribution: reports should reach the relevant parties on time with confidentiality maintained - correct
  3. Clarity and usefulness: the content should be understandable to the people who receive the reportWhy not: The stem says it is clear. The problem is circulation and confidentiality.
  4. Accuracy: the figures should be reconciled and validated before releaseWhy not: The stem says the report is accurate, so this is not the failing.

The distribution principle requires reports to reach the right people on time, with confidentiality preserved. A late and over-broad circulation breaches it even though content is sound.

In the app: 6 practice questions on this outcome, spaced review that brings it back before you forget it.

Start free →

More in Principles for Effective Data Aggregation and Risk Reporting