Fault tolerance requirements of tactical Information Management systems

Information Management (IM) services provide a powerful capability for military operations, enabling managed information exchange based on the characteristics of the information that is needed and the information that is available, rather than on explicit knowledge of the information consumers, producers, and repositories. To be usable in tactical environments and mission critical operations, IM services need to be resilient to faults and failures, which can be due to many factors, including design or implementation flaws, misconfiguration, corruption, hardware or infrastructure failure, resource intermittency or contention, or hostile actions. This paper presents a reference model for representing the performance and fault tolerance requirements of IM services in tactical operations. A Joint Close Air Support operation is described using this representation and the viability of canonical fault tolerance techniques are examined for a given deployment.

[1]  Rebecca Grant Operation Anaconda: An Air Power Perspective , 2005 .

[2]  Darrel D Whitcomb,et al.  Combat Search and Rescue in Desert Storm , 2012 .

[3]  Ray M. Ceralde Red Zones: Improving the Enemy Ground Force Situation Display in Digital Battle Command and Control Systems , 2005 .

[4]  G. M. Brown,et al.  Attitude and articulation control for the Cassini spacecraft: a fault tolerance overview , 1995, Proceedings of 14th Digital Avionics Systems Conference.

[5]  Ricardo Jiménez-Peris,et al.  Exactly Once Interaction in a Multi-tier Architecture , 2005 .

[6]  Steve Vinoski,et al.  Advanced Message Queuing Protocol , 2006, IEEE Internet Computing.

[7]  Philippe Kruchten,et al.  Architecture blueprints—the “4+1” view model of software architecture , 1995, TRI-Ada '95.

[8]  Joseph P. Loyall,et al.  Dynamic Quality of Service Management for Multicast Tactical Communications , 2011, 2011 14th IEEE International Symposium on Object/Component/Service-Oriented Real-Time Distributed Computing.

[9]  Robert G. Hillman,et al.  Joint Battlespace Infosphere: Information Management Within a C2 Enterprise , 2005 .

[10]  W. Marsden I and J , 2012 .

[11]  Philippe Krutchen,et al.  Architectural blueprints--the '4+1' view model of software architecture , 1995 .

[12]  Christopher D. Gill,et al.  Comparing and contrasting adaptive middleware support in wide-area and embedded distributed object applications , 2001, Proceedings 21st International Conference on Distributed Computing Systems.

[13]  Joseph P. Loyall,et al.  Evaluating QoS-enabled information management services in a Navy operational context , 2011, Defense + Commercial Sensing.

[14]  Richard Mesic,et al.  Courses of Action for Enhancing U.S. Air Force Irregular Warfare Capabilities: A Functional Solutions Analysis , 2010 .

[15]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[16]  Joseph P. Loyall,et al.  A distributed real-time embedded application for surveillance, detection, and tracking of time critical targets , 2005, 11th IEEE Real Time and Embedded Technology and Applications Symposium.

[17]  Yair Amir,et al.  The Spread Wide Area Group Communication System , 2007 .

[18]  Rob Grant,et al.  Phoenix: SOA based information management services , 2009, Defense + Commercial Sensing.