How-tos
Step-by-step instructions.
No section
-
Code Contribution Process
- This document describes the process that must be observed by PillarOne code contributors. Besides technical steps, it contains explanations and reasoning.
-
Recommended IDEA Setup
- Develop with pleasure: IDEA offers a lot of features for the developer. This document contains only a short lists of recommended settings and a very useful plugin.
Model Developer
-
Setup an IDEA project for PillarOne RiskAnalytics
- To easily browse and work on the PillarOne sources we recommend setting up a project in an IDE (integrated development environment). As the PillarOne sources are mainly Groovy and Java classes, we recommend IDEA, which currently has the best Groovy support.
-
Setup an IDEA project for PillarOne RiskAnalytics as of v1.1
- To easily browse and work on the PillarOne sources we recommend setting up a project in an IDE (integrated development environment). As the PillarOne sources are mainly Groovy and Java classes, we recommend IDEA.
-
Add another distribution
- The current distribution library contains the following distributions: Normal, Lognormal, Pareto, Uniform, Piece Wise Linear, Piece Wise Linear Empirical, Poisson, Negative Binomal.
-
Executing a Test Class in IDEA
- During development it is really useful to execute single test classes or even debug them in order to bashing bugs.
-
MySQL DB set up
- Out of the box, the RiskAnalytics installer comes with a Derby DB backend; no DB configuration needed. To increase the performance of the backend, one should use a comprehensive database product. We describe how to set up MySQL as a RiskAnalytics backend.
-
Project Setup in IDEA for Business Logic Development
- In order to work on the business logic of PillarOne.RiskAnalytics we recommend to properly setup an IDE (integrated development environment).
-
Setup an IDEA project for PillarOne (OUTDATED)
- To easily browse and work on the PillarOne sources we recommend setting up a project in an IDE (integrated development environment). As the PillarOne sources are mainly Groovy and Java classes, we recommend IDEA, which currently has the best Groovy support.
-
Start PillarOne.RiskAnalytics on a Webserver from within IDEA
- For testing purposes a developer may need to run PillarOne.RiskAnalytics on a webserver.
-
Write a Model
- A model is a flexible net of components and describes the relations between business objects. Models are kept separate from the parametrization, structure, result templates and results.
-
Write a Parameter File
- Parameters are kept separate from the model, its structure and the results.
-
Write a Structure
- The structure file defines a visual hierarchy of the models for the user interface representation. The concept of the structure files is not yet final!
Model User
-
How to use the PODRA Model
- The PODRA Model is designed to do non-life primary insurance risk analysis. Components are the gross portfolio (underwriting information and claims generators), the company structure and the reinsurance covers. By running simulations the model can be evaluated. Premiums, provisions and claims on different levels can be analysed. Possible uses are risk analyses, portfolio optimization and reinsurance structuring.
Installation
-
Install the server version of PillarOne.RiskAnalytics
- This how-to explains how to install PillarOne.RiskAnalytics on a Windows machine running in the server mode. Linux users should be able to abstract and apply similar steps for their OS. The server version provides additional multi user functionality.
-
Manual Plugin Download During Software Installation
- Depending on firewall settings plugins can't be downloaded by the installer itself.
-
MySQL DB set up
- Out of the box, the RiskAnalytics installer comes with a Derby DB backend; no DB configuration needed. To increase the performance of the backend, one should use a comprehensive database product. We describe how to set up MySQL as a RiskAnalytics backend.

