text: Chapter 12
  ADA Data and Communications Architecture
  This chapter discusses the ADA data and communications architecture and how it
  connects with the joint AMD organizations. It includes information on connectivity
  specified for the joint, interorganizational, multinational AMD elements, and ADA
  organizations, echelons, and systems capable of connecting directly to the major AMD
  networks. The intent is to show the connectivity that supports the doctrinal linkages
  discussed in the previous chapters.
  MAJOR NETWORKS
  12-1. The major networks addressed are the AMD supporting networks for the joint, interorganizational, and
  multinational elements, link 16, and LandWarNet. LandWarNet is discussed in terms of its radio frequency
  connections and internet protocol connections.
  12-2. Networks that span ADA echelons and joint, interorganizational, and multinational links using
  multiple types of interfaces require special skills to plan, coordinate, install, operate, and maintain. Personnel
  who perform this mission have extensive experience and detailed technical training. To support the AMD
  operational networks, an interface control officer is positioned at the corps, division, AAMDC, and ADA
  brigade levels. The interface control officer is responsible for planning data links for early warning
  dissemination within the area of operations. The Army interface control officer, in the G-6 staff, coordinates
  with ADA units, the Army AMD network design facility, and the joint interface control officer to plan the
  network design with the information exchange requirements that have been provided by subordinate units
  and the command. The interface control officer manages and coordinates the entire multi-link interface for
  supporting units and works with the joint interface control officer for connectivity into the larger joint,
  interorganizational, and multinational networks. The G6, normally from the AAMDC, deploys an interface
  control officer, as necessary, to the joint interface control officer’s location to integrate Army AMD assets
  into the tactical data link architecture.
  AMD SUPPORTING NETWORKS
  12-3. The AMD supporting networks includes the many tactical data links and unique connections
  throughout the joint, interorganizational, and multinational community. Link 16, though not included below,
  is also an AMD supporting networks; it is discussed and shown separately due to its significance. The AMD
  networks support development of the air picture with situational understanding, intelligence activities,
  planning, operations, and engagement operations with threat position information and firing guidance. Some
  of the networks are legacy networks for U.S. joint forces but are still in use with multinational forces.
  However, some joint forces currently retain the capability to enter or monitor the legacy networks to maintain
  connectivity with joint, interorganizational, and multinational organizations and elements.
  12-4. Examples of legacy AMD supporting networks still in use on some platforms are link 11 (also known
  as tactical data link-A), link 11B (also known as tactical data link-B), PADIL, forward area air defense data
  link (FDL), and the Army tactical data link 1. The Command and Control Battle Management and
  Communications (C2BMC) network is used to integrate the BMDS. The cooperative engagement capability
  (CEC) network is a newer network used by the U.S. Navy. These networks are discussed briefly below.
  12-5. Link 11 is a secure, half-duplex, netted digital link that provides a network for exchanging tactical data
  between subscribers at either 1,364 or 2,250 bits per second. It is normally operated in a roll call or polling
  mode, using either high frequency or ultra-high frequency communications. It is controlled by a net control