You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem statement
Right now, individual assets can be added to a BIA, and recovery parameters can be added for each. This is fine if the asset is in fact an individual system. However, I have business processes defined as primary assets, which again have underlying dependencies of various systems (supporting assets). E.g., "customer service" > ITSM tool, email, knowledge base, etc. While it would theoretically be possible to define a recovery target for the whole process, it would be difficult to document and test the whole process at once, and additionally, in real life, this would cause redundant work (if a system is used by multiple processes).
Expected behavior
Would it be possible roll up the recovery parameters of the various systems into the shared upstream dependency? Maybe the recovery parameters could be moved into the asset details, just after the RTO/RPO/MTD, which would be a good fit?
This discussion was converted from issue #4050 on April 28, 2026 17:39.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Problem statement
Right now, individual assets can be added to a BIA, and recovery parameters can be added for each. This is fine if the asset is in fact an individual system. However, I have business processes defined as primary assets, which again have underlying dependencies of various systems (supporting assets). E.g., "customer service" > ITSM tool, email, knowledge base, etc. While it would theoretically be possible to define a recovery target for the whole process, it would be difficult to document and test the whole process at once, and additionally, in real life, this would cause redundant work (if a system is used by multiple processes).
Expected behavior
Would it be possible roll up the recovery parameters of the various systems into the shared upstream dependency? Maybe the recovery parameters could be moved into the asset details, just after the RTO/RPO/MTD, which would be a good fit?
Mock
n/a
Additional context
n/a
Beta Was this translation helpful? Give feedback.
All reactions