DADAccounting

These days, you might even call it "use test": Bringing the models down to earth, making the results lived by management, having an impact on decision making, getting booked in the financial statements. 

After having completed the actuarial work, the parameters set, the results understood, it comes to bringing these numbers to the real life. Whereas it might be more obvious e.g. for technical reserves set, one thing also holds true for the risk model as a whole: Use test. 

I see two applications:

• Actuarial numbers letting the company know how much risk is associated with a specific element of their portfolio.
  Steering Risk Appetite must be based on numbers we trust and understand.
• Smooth transition of results in a tool to templates provided by other systems:
  What about adjusting the result tree view to any given output form? Such as reproducing the MIS, or at least, providing numbers in the exact format needed for the import into the MIS tool.

The first is not to be implemented in a tool such as RiskAnalytics only, but in the processes of a company. The second is. Have a look at https://issuetracking.intuitive-collaboration.com/jira/browse/PMO-1033 how we envision this!

I've already tested it and I like it as much as those of you who saw the demonstration at the community event in St.Gallen.

Markus M.

(This is the last of four DADA updates.)