1 / 16

Information Flow: Tactical Network Design and Bandwidth Management

Information Flow: Tactical Network Design and Bandwidth Management. University XXI Texas A&M University University of Texas United States Army. Agenda. Introduction Motivation Collaboration People Background Tactical Communications Network Command Posts Army Battle Command Systems

briancurtis
Download Presentation

Information Flow: Tactical Network Design and Bandwidth Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Information Flow: Tactical Network Design and Bandwidth Management University XXI Texas A&M University University of Texas United States Army

  2. Agenda • Introduction • Motivation • Collaboration • People • Background • Tactical Communications Network • Command Posts • Army Battle Command Systems • Problem and Requirements • Implementation • Conclusion Texas A&M University - U.S. Army

  3. Introduction - Motivation • The United States Army wants to improve the use of information systems to achieve tactical advantage over potential adversaries • Various information systems are already deployed with Army units, and as the Army modernizes its forces and updates its doctrine, new uses for these existing information systems are developed • Simultaneously, the Army is investigating applications of new and emerging information technologies in the tactical arena • These new capabilities and new systems place increasing and uncoordinated demands on the tactical data network, resulting in a bandwidth management crisis Texas A&M University - U.S. Army

  4. Introduction - Collaboration • Force XXI • The U.S. Army’s vision of future heavy-force combat • Focus on information dominance • University XXI • Cooperative effort between Texas A&M University, The University of Texas, and the U.S. Army • Apply the fruits of academic knowledge, experience, and research in information systems to the military domain “Know your enemy, know yourself, and in a hundred battles you will never be in peril.” - Sun Tzu Texas A&M University - U.S. Army

  5. Introduction - People • The Principal Researchers represent a unique convergence of military and information technology experience • LTC John M. D. Hill - Armor Officer, Simulation, Graphics and GUIs, Planning Support Systems • LTC Curtis A. Carver, Jr. - Signal Officer, Networks, Adaptive Information Systems • MAJ John R. “Buck” Surdu - Infantry Officer, Acquisition Corps, Simulations, Planning Support Systems • Dr. Udo W. Pooch - Former Marine Corps, extensive experience in Simulation, Networks, Information Systems • Mr. Willis Marti - Former Army, extensive Information Systems implementation experience Texas A&M University - U.S. Army

  6. Background - Tactical Communications Network Communications Architecture (MSE) • Mobile Subscribe Equipment (MSE) components and links • Node Center (NC) • Large Extension Node (LEN) • Small Extension Node (SEN) • V1 model • V2 model • High-Speed MUltipleXer Card (HSMUX) Texas A&M University - U.S. Army

  7. Background - Command Posts Tactical Entities MAIN REAR • Three division command posts plus a support command: • Assault CP (DTAC) - two SENs • Main CP (DMAIN) - two SENs • Rear CP (DREAR) - connects through the LEN • Division Support Command - connects through the LEN • Three Maneuver Brigades plus two separate brigades • Each Brigade TOC and Brigade Rear CP gets one SEN • Three Separate Battalions (MI, ADA, Signal) • Each get one SEN Texas A&M University - U.S. Army

  8. Background - Army Battle Command System (ABCS) MCS MCS MCS ASAS AFATDS CSSCS Information Systems • “A system of systems” - merged stovepipes • Maneuver: Maneuver Control System (MCS) • Intelligence: All Sources Analysis System (ASAS) • Fire Support: Advanced Field Artillery Tactical Data System (AFATDS) • Logistics: Combat Service Support Computer System (CSSCS) • Air Defense: Air and Missile Defense Planning and Control System (AMDPCS) • Others Texas A&M University - U.S. Army

  9. Put it all together … Tactical Entities MCS MCS MCS ASAS AFATDS CSSCS Communications Architecture (MSE) MAIN REAR Information Systems Operational Conditions Texas A&M University - U.S. Army

  10. The Problem • There is no mechanism for prioritizing the information flows or for determining the best allocation of available communication system resources to support particular operational conditions. • There is no ability to examine the impact of new capabilities or new information systems • High-resolution network simulation are too low-level and don’t account for the flows from information systems • Can’t attribute network traffic to specific flows between information systems. • Can’t afford to send the Division communications structure, Command Posts, and information systems to the field every time an experiment is desired. Texas A&M University - U.S. Army

  11. The Requirements • The planners need a tool for designing the tactical data network to meet the expected data bandwidth requirements of current and future battlefield information systems. • This tool must be able to simulate the flows on the data network over time for different communications configurations and different operational conditions • The tool must have a good model of the information flows to be able to predict network performance. Texas A&M University - U.S. Army

  12. The Implementation - Summary • Component Modeling • Tactical Data Network at the message aggregate level • ABCS Systems as flow producers • Tactical Entities change missions based on operational condition • The Information Flow Drivers - between systems • Routinely generated information flows • For example, ASAS database download every two hours • Other information flow patterns • Modeled as distributions, table-lookup, or burst schedule. • Statistics Visualization and Capture • Planner can observe the effects of changes on the overall system and “drill-down” to detailed statistical information. Texas A&M University - U.S. Army

  13. The Implementation - Summary • Flexibility • Segregation of Information Systems, Tactical Entities, and Communications Network • Flow drivers are parameterized to allow configuration of each flow, and the system allows for replacement by more accurate models as real data is captured • The planner can use the graphical user interface to change the setup of any component in the system Texas A&M University - U.S. Army

  14. Screen Capture Texas A&M University - U.S. Army

  15. Conclusion • The Information Flow tool will enable planners to rapidly determine viable configurations based on actual mission requirements and current systems capability • New and proposed systems can be added to the model and planners can determine the effects on the overall system • This will result in more effective utilization of the available bandwidth and assist in determining prioritization of information flow in the future Texas A&M University - U.S. Army

  16. Questions? • If we have time … fire away! • Otherwise: • http://www.cs.tamu.edu/people/ { hillj | carverc | surdu } • http://www.cs.tamu.edu/faculty/pooch • { hillj | carverc | surdu | pooch }@cs.tamu.edu Texas A&M University - U.S. Army

More Related