##Risk Description

= Risk Description =

## Detailed description of this risk and its possible implications.
## E.g. If one of the car's tires suffers a puncture, we may run off the road.

Planets will probably not have the preservation services and framework ready by the time we need them.

Furthermore, there is some fear that we may not get the output we need - e.g. that no running preservation framework will exist at the end of Planets, or that the framework does not suit our needs. However, the Planets project will at least provide some useful knowledge about digital preservation which still will be a help to the DOMS project, but it will of course cause a major delay in the project if we will have to implement all the preservation functionality by ourselves.

== When to react? ==

## When must we respond to the risk? E.g. When the event occurs or already when we see the warning signs?
## E.g. We must react if we hear a hissing sound.

== Reaction ==

## Detailed description of how to react on the risk and which actions to take, if it is imminent.

## There exists 4 basic reactions:
## 1: Accept the risk.
## 2: Eliminate the cause to the risk.
## 3: Mitigate the probability or the consequence of the risk.
## 4: Delegate the risk to another party, e.g. by outsourcing it or take out insurance for it.

## E.g. We accept the risk and change the tire if we suffer a puncture.

It is probably acceptable that we wait sometime for the final output of Planets, if it is not ready when we need it. We can probably delay the final preservation tasks to a later time.

However, if Planets does not produce a working framework, we will have to reevaluate the options.

== Responsible Persons ==

The below persons are responsible for continuously monitoring and acting on this risk:

## Add a bullet list with links to the wiki pages of the responsible persons here:
## E.g.
## * [:JohnDoe: John Doe]