Tactical Edge Characterization Framework Volume 1: Common Vocabulary for Tactical Environments

By Dr. Fatma Dandashi , Jeffrey Higginson , James Hughes , Wilson Narvaez , Dr. Marwan Sabbouh , Salim Semy , Dr. Beth Yost

Many Service Oriented Architecture (SOA) approaches in common use today presume the availability of reliable, consistently available networks that provide limitless bandwidth and little or no latency.

Download Resources


PDF Accessibility

One or more of the PDF files on this page fall under E202.2 Legacy Exceptions and may not be completely accessible. You may request an accessible version of a PDF using the form on the Contact Us page.

Many Service Oriented Architecture (SOA) approaches in common use today presume the availability of reliable, consistently available networks that provide limitless bandwidth and little or no latency. Because this is often not the case in Department of Defense (DoD) tactical environments, current development methods may not provide reliable capability to users in such environments. Virtually any mission capability or thread that projects force will inevitably touch one or more edge users. DoD programs responsible for delivering capabilities to the tactical edge include Future Combat Systems, Consolidated Afloat Network and Enterprise Services, Special Operations Command, etc. The tactical edge is also affected by DoD acquisition agents such as the Electronic Systems Center and the Space and Naval Warfare Systems Center. This Tactical Edge Characterization Framework provides a common vocabulary that defines the conditions and identifies the disadvantaged users at the tactical edge.