Procedia Computer Science · 2013 · 37 citations · 6 references
EngineeringSystems EngineeringFault-tolerant SystemsSystem DynamicsSystems ArchitectureBackup SystemsRedundancy ManagementRedundancy TechniquesReliable System DesignResilient System DesignDynamic StabilityRedundancy DesignRedundancy EngineeringRedundant Systems DesignSystem RedundancySystem ResilienceSystem-of-systems ModelingSystems Resilience
Resilience— the capacity to recover from disturbances with minimal impact on stability— is hard to quantify in heterogeneous, geographically distributed SoSs, where traditional reliability and backup redundancy are impractical, prompting consideration of reactive recovery after failure and proactive adaptation to gradual degradation that can trigger configuration changes before failure. The study quantitatively evaluates how re‑tasking remaining systems to compensate for a constituent’s performance loss—termed stand‑in redundancy—and develops two concepts for its implementation, enabling decision‑makers to assess the resilience impact of different SoS architectures. The authors present a method that identifies feasible alternative SoS configurations by balancing performance recovery with implementation cost, thereby quantifying the effect of stand‑in redundancy on resilience.
Resilience is the ability of a system or organization to react to and recover from disturbances with minimal effect on its dynamic stability. While the resilience of system-of systems (SoSs) depends on the reliability of their constituent systems, traditional reliability approaches cannot adequately quantify their resilience. Given the heterogeneity and often wide geographic distribution of SoS constituent systems, inclusion of backup redundant systems for a SoS is usually impractical and costly. In this paper, we quantitatively assess the impact of compensating for a loss of performance in one constituent system by re-tasking the remaining systems. We call this “stand-in redundancy”, and we develop two concepts to implement stand-in redundancy in a SoS. First, reactive resilience deals with performance recovery after a system failure has occurred. We provide a method to determine feasible alternative SoS configurations based on performance level recovery and cost of implementation. Second, proactive resilience takes into account the gradual degradation of systems over time. The corresponding reduction in SoS performance could initiate a forcible transition to a different SoS configuration before actual failure of the system. These concepts, and their resulting upstream effects on development costs and risks, can be used by decision-makers to quantitatively assess the impact on resilience of different SoS architectures and their inherent ability to resist failures throughout the SoS lifecycle.
6
Architecting principles for systems-of-systems
Mark W. Maier · Systems Engineering · 1998 · 2.2K citations