Some of the new ideas have grown out of established risk management disciplines in financial institutions such as Audit and Market Risk, while others are drawn from activities as diverse as healthcare and the space industry.
As we go along, we'll explain the new concepts that are driving operational risk management, hear from some Expert Witnesses, and offer links to key information points on the web.
But general definitions are less useful when a manager or regulator tries to do something about enterprise-wide operational risk - such as improve operational risk controls across the board, or reserve capital against operational risk.
Counting something, or controlling it, means putting a line around it. Soon, regulators and RAROC analysts will need to decide whether to include, say, strategic business risks or reputational risk in their allocation of regulatory and enterprise-wide capital.
And managers will need to know whether their assessment of operational risk in a business line should include, say, the risk of a trader misunderstanding a sophisticated financial model. Some experts are sure model risk should be included, while others are sure it forms a more natural component of market risk - the button below maps out some other tricky boundary clashes.
Definitions developed by industry bodies and regulators have some practical advantages, so let's take a closer look at the components of operational risk as defined by the London-based British Bankers Association - a body that has been active in developing standard approaches to operational risk.
For the BBA, "Operational risk is the risk of direct or indirect loss resulting from inadequate or failed internal processes, people, and systems or from external events."
Processes of a more or less formal kind surround many of the risky activities of a bank. Some are routines performed by humans while others are part of the core infrastructure of the institution. The button below lists some key processes surrounding a capital markets trader.
Connecting a discrete set of actions into a procedure, and than a formal process, offers huge benefits to financial institutions - as it does to manufacturing industries - in terms of scaling, risk control and standardisation.
Processes also help to defuse risk by institutionalising skills that would otherwise reside in a single individual. But processes can make a firm vulnerable in other ways.
Few employees understand a complex bank process as a whole, so the implications of sloppiness or breakdowns in the process chain are often unclear. And devious individuals find a process easier to exploit than a savvy manager because there's no immediate "sense check" of their actions.
Meanwhile, because turning a procedure into a process is usually associated with an increase in business line volumes and notional amounts at the expense of profit margins, processes tend to concentrate and leverage any existing operational risks. If something goes wrong, it goes wrong big time.
This cycle continues as processes speed up and are automated using the institution's computer systems - automation tends to improve consistency but it does not guarantee that the underlying process is structurally safe.
In financial institutions, most processes are designed with audited fail-safes and checking procedures. These might be built into the process itself or take the form of independent monitoring by risk control groups such as Compliance.
But because processes interact with other risky variables - the external environment, business strategy, people - it's difficult to sound the all clear. For example, are the fail-safes and "checks and balances" of the process appropriate now that the firm has opened offices in a new jurisdiction?
Given the new products a firm has introduced, could the firm suffer a massive loss if a step in the procedure is compromised? Does the process efficiently manage transactions that are exceptions to the norm, or are staff barely coping? Is risk information flowing from the process to decision-makers speedily enough to match market developments?
These questions help to show why the problem of risk managing processes has become more urgent over the over the last ten years as the rate of change in the financial industry has accelerated.
Institutions have automated processes, re-engineered them after mergers and acquisitions, and adapted them to improvements in industry-wide infrastructure and communications capabilities. Increasingly, banks have been rewarded with high margins for entering immature markets where, by definition, safe processes are not yet established.
They have also extended their activities overseas - beyond the easy reach of their established process infrastructure and monitoring capabilities.
And they have introduced new processes to monitor underlying processes - New Product Approval Process and formal Technology Audits being only two examples.
The direct physical impact of these risks is insurable. But payouts cannot compensate for an interrupted relationship with a customer, or for the effect on future business plans or staff.
The problem of ensuring that a business can continue despite a physical catastrophe - business continuity - has evolved into a small industry.
Major banks now spend millions of dollars each year to ensure that, if disaster strikes, they can relocate within hours to a functional version of their main or trading offices - complete with IT systems that are constantly primed with back-up data from the bank.
But this cannot remove the vulnerability of institutions to public or financial market infrastructure. A recent and dramatic example of this was the systems failure at the London Stock Exchange in the summer of 2000 which prevented the exchange from opening.
Fundamental social and technological trends can also threaten institutions - from a rise in general fraud to sustained attacks on corporate web sites by external hackers and fraudsters.
In the summer of 2000, the UK's financial services regulator Howard Davies echoed the concerns of regulators around the world when he claimed that banks systems were being "probed for weaknesses hundreds of times a day"- and that there was sometimes insufficient segregation between the internal systems of banks.
But regulators are themselves a source of external risk. An unforeseen shift in the regulatory or political environment can ruin the profitability of an institution, or leave it vulnerable to catastrophic litigation.
But most of these functions have responsibility for specific risks, services or business lines. They cannot give a firm a wide-angle view of its operational risks.
The reasons why institutions and experts think this wider view is important tend to vary according to individual priorities. But the most pressing are the efficient monitoring of critical risks across an organisation, the interaction of risks, risk measurement and the efficient use of capital, and corporate support for risk-reducing investments at business-line level.
Other firms have extended the remit of internal audit to include operational risk management, arguing that their audit group has to hand the skills, infrastructure and manpower to take action on operational risk.
Some firms report that giving internal audit a wider remit makes the function more efficient. Rather than simply ensuring that the proper reporting and control procedures are in place in each unit, audit can take a more active view of risk/reward and reduce duplicated checks and controls.
Whatever the framework, taking the wider view means bringing together information about risk in a consistent fashion so that corporate management and the specific owners of the risk can take action. The button opposite offers easy access to some of the new information management tools that are being marketed to help managers do this more efficiently.
One interesting aspect of these tools is that by making approaches to operational risk control and measurement more consistent within and across firms, they also make it easier for firms to benchmark their risk standards and publish this information to external audiences of regulators, investors - and key customers.
Seeing the wood for the trees - critical dependencies and what-if scenarios
One approach to identifying operational risk is to look for critical dependencies in people, processes, systems and external structures. Once identified, the dependencies can be managed or engineered away by adding fail-safes and system redundancies.
This approach is commonsensical, and has the great advantage that the risk of an event happening does not have to be measured in any quantitative way. It simply has to be identified as critical to the safety of the firm or process.
Many of the formal ideas that have come into the financial industry for system and process analysis have their roots in engineering - appropriately enough, given the increasing dependence of financial institutions on technology.
For example, some consulting firms now specialise in identifying the critical dependencies in power, communication and security systems - such as the failure of a critical power line, cable or firewall. Click the dependency diagram opposite to read how our next Expert Witness tracks back to a specific critical risk.

Dependencies often arise out of the interplay between business plans, process design and system architecture - which means that senior managers and business line managers must be involved in risk identification as well as risk management solutions.
And because a disaster would affect the whole firm, senior managers need to understand enough about the risks and their relationships to take the right decision.
It's not just a question of identifying physical dependencies. Many firms have begun to bring together groups of experts to discuss all the various risks in their part of a financial business line or process.
These structured discussions are different from most traditional forms of risk audit in financial institutions because they concentrate not on checking control procedures, or on the filling in of periodic reports, but on risk identification, the promotion of risk awareness in business line personnel, and detailed risk scenario building.
Risk scenarios are important because they help managers to work through what might happen if a particular mishap occurred. These "what if" scenarios are often simply descriptive and hypothetical. But some institutions are experimenting with more formal, quantitative techniques that model firms as systems.
The approaches include applying the latest scientific ideas on network topologies and complexity theory.
At the moment, though, it's difficult to apply this kind of sophisticated analysis to whole firms - so it's mainly being used to track down dependencies in specific business lines and processes.
The data game - more questions than answers
When a risk threatens a whole firm, and can be removed simply and cheaply, decision-making is easy. But some decisions demand hard numbers.
It costs money to install redundant systems - how much should be spent? If the chosen means of managing the risk is to reserve capital, how much capital is required? If a company decides to insure itself, how does it assess whether a high premium is worth paying?
It's difficult for firms to answer these questions - and move through the risk management decision cycle we identified earlier - without first answering three questions that depend upon data.
- How frequent are the events that generate each specific risk?
- How costly will any loss event be if it occurs?
- How likely is it that risk control efforts will reduce either of these numbers?
These questions are similar to those asked by market and credit risk specialists. But operational risk is a more difficult nut to crack because of the paucity of data, the many different frequencies and severities of loss, the multiple categories of risk that have to be considered, and the difficulty of linking a loss event to a single cause.
As our next Expert Witness explains, some key concepts here are expected, unexpected and catastrophic types of event. These concepts can help managers compare the character of risk profile associated with different business lines, and they also help explain part of the data problem.

Take the case of a failure to process a transaction of some kind. In institutions that process large volumes of transactions, these failures are relatively frequent. Firms are likely to be able to gather significant data on the more common low-impact costs associated with these breaks - fines, penalties, reimbursement to customers or counterparties, cost of mending the transaction, and so on.
Other kinds of medium-impact risk, such as significant bank fraud, are more difficult for banks to analyse because they do not have enough data on loss and frequency within the institution to support a valid statistical analysis. This is not always because data do not exist - sometimes it's a question of availability and quality.
For example, in the US bank fraud and money laundering data is already gathered systematically by the regulatory authorities. But it was only in October 2000, after pressure from industry associations, that the US Treasury's Financial Crimes Enforcement Network indicated it might publish the data periodically in association with the American Banking Association.
It is not yet clear whether the data will be released with enough contextual detail to make it useful for quantifying the risk of different kinds of fraud in different kinds of institutions.
For many kinds of medium-frequency, medium-impact risk, however, there are simply no readily available databases of loss. So one of the most exciting developments in operational risk is the emergence of banking industry initiatives to solve this problem.
In the summer of 2000, the British Bankers Association announced that over 20 financial firms were joining together to collect data on operational risk events. By autumn 2000, some of the firms were actually supplying their internally collected data to the BBA, using the association's standard categorisation of loss and risk types.
The BBA pools the data and removes any identifying tags before republishing the complete dataset to contributing banks.
A similar venture, MORE, has been set up by Connecticut-based risk consultancy NetRisk, with the support of industry associations and various Canadian and US banks.
The most important feature of both these efforts is the attempt to produce a rich but standard set of data that will help banks quantify risk and link it to root causes, while at the same time preserving bank confidentiality.
These initiatives should help the banking industry to put numbers against the operational risks that are frequent and also those that are unexpected. But they will not solve the problem of the most extreme and infrequent events.
Extremely high impact, but low frequency, risks pose a different kind of problem. This kind of loss is difficult to conceal from shareholders, and is often reported in the press, so some data is publicly available. Bringing this data together in a consistent form is a significant task, but a number of consultancies - listed in our Operational Risks Tools button above - offer such public loss databases as packages.
But the real problem is that, even at an industry level, there are not enough extreme events of a particular type to allow the statistical modelling of their frequency or severity. Most firms respond to these extreme risks through attempting to prevent them or by insuring against them, rather than by reserving specific amounts of capital against them.
But they can't be ignored in the numbers game, or institutions will be building a blind spot for the most deadly risks of all. The regulators are also keen that these risks are accounted for in the total levels of capital available to the financial industry.
One of the cutting-edges of operational risk research is therefore the application of a body of theory known as Extreme Value Theory to the scarce data that is available on catastrophic risks. Although highly technical, EVT offers some hope that it will become possible to put meaningful figures against the risk of massive operational failure.
But EVT cannot help solve a more fundamental data problem. Data takes time to collect and it often has to be aggregated across institutions to make the sample large enough for statistical analysis.
Some experts point out that aggregate historical data cannot help banks identify the risks specific to their institution, or the risks that are lie in wait over the horizon of the data sample.