##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.

Currently it looks like IT maintenance department does not agree with us about the need for active bit preservation. However, active bit preservation is a crucial TDR requirement and thus crucial to the success of the DOMS project in the long run. However, this issue is not a focus area in the beginning of the project, thus, the initial consequence estimate of this risk will be low.

The storage currently provided by the IT department is more along the lines of tradition backup.

BCD is aware of the problem, and it is expected that something will be done.

== 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.

For a start we accept the risk, but later in this project we will have to focus on this issue when the time is ready to concentrate on fulfilling the requirements to obtain a TDR certification.

The elimination of this risk is more a political issue than a practical issue, as it is technically feasible to perform active validation of the binary data stored. However, this does not come for free so we will probably have to engage BCD in the negotiations with the IT department and other relevant departments to get this into place.

== 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]