Find a Security Clearance Job!


Defense Automated Warning System [DAWS]

The Defense Automated Warning System [DAWS] is the DoDIIS core application for Indications and Warning (I&W). DAWS is a legacy system that is destined to become part of the Migration Defense Intelligence Threat Data System (MDITDS). It provides a suite of tools to support monitoring, analyzing, and reporting within the I&W community plus an assortment of other capabilities to support the current intelligence mission. DAWS provides I&W analysts the tools necessary to determine if enemy-initiated hostilities may be imminent. Hostilities include terrorism, diplomatic tensions, on through to full nuclear exchange. The data necessary for this notification may be received from minutes to hours, to days, or longer, prior to the initiation of hostilities. Because of the potential for very short notice, it is imperative that an analyst have an automated tool such as DAWS to assist them in existing or potential threats.

DAWS is a sophisticated intelligence data handling system which provides the I&W community analysts with a highly effective applications suite to expedite analysis of all-source intelligence. All Unified and Specified (U&S) commands make daily decisions on the appropriate posture of their forces, based upon the current threat. The force posture options include changes in alert status to improve response times, relocation of assets to increase warning time, and launch under positive control. These decisions are based upon the best assessment of enemy capabilities and demand sophisticated and timely intelligence.

DAWS supports the receipt, processing, profiling, archiving and generation of intelligence messages. It also provides tools to display facility and order-of-battle data and plot it on maps. DAWS is a client-server application that runs on servers and workstations provided by the sites. The client-server design enables operation over very low-bandwidth communication lines between the server and workstations.

DAWS is a collection of programs that communicates over a local area network to make the job of the warning analyst easier. Many of the I&W handbook items are built into this system to provide timely and accurate I&W reporting and informational displays. The automation comes into play on the DAWS server in the way in which newly received I&W messages are processed and parsed, updating the I&W data base within seconds of message receipt.

Text messages are the primary means of communications within the intelligence community, and they provide a record of communications. DAWS provides direct review of current Indications and Warning (I&W), priority, and other user specified intelligence message traffic. The DAWS System Status window provides access to these message queues and displays the number of messages available for your review for each queue. Access to a list of messages on a queue and the message itself can be displayed. The System Messages Window displays broadcast messages from the DAWS server, such as when a historical query has completed or when an I&W command changes a WATCHCON or indicator status value.

Priority Queue. The DAWS Priority queue catches messages of significant priority or special type (as defined in the Config/msg_cat configuration file). By default the priority queue receives the message priorities of ECP (Y), FLASH Override (Z), and CRlTlC (W). It will also catch CRITIC type messages even if the priority is not 'W.'

I&W Queue. The DAWS I&W queue captures the Defense I&W System report types. Any incoming Defense I&W System report is placed on the I&W queue.

Attention Queue. The DAWS Attention queue is fed by messages that match message profiles.

Press Queue. Press message traffic is processed separately from military intelligence message traffic. Like the Attention queue, traffic is directed to the press queue by matching press message profiles.

The Message Requirements Profile Editor is used to specify what requirements must be met for a message to match a profile. There are six message requirements fields which may be used in building a profile. They are: Originators, Message Types, Communication Lines, Areas of Interest, Dominate Profiles, and the Keyword Tree.

DAWS contains "message handling" software because warning information is communicated in formatted message traffic and thus messages need to be received and processed prior to, or as part of warning information analysis. SACWARNS and DAWS were not developed with the message handling system MAXI in mind because watch personnel required access to warning tools and intelligence message traffic from a single workstation. MAXI was not available on workstations when SACWARNS was developed.

DAWS Message Front End [DMFE] is a subset of the DAWS. It includes only those pieces necessary to perform message handling functions. DMFE includes the following components from DAWS: Message Pipeline; Profiling System; Historical Query System; and Outgoing Message Generation and Release. The I&W-specific portions of DAWS are eliminated -- they are simply not used and are typically deleted by the administrator to save space.

DMFE was conceived as a result of a 1991-92 Rome Laboratory study, funded by DIA, investigating the impacts of transitioning DODIIS products to the Defense Message System (DMS) environment. Using the DAWS message support as a point of departure, the message handling software within DAWS was de-coupled from the rest of the DAWS applications into a "stand-alone" product suitable for the DMS study. The effort was called Defense Message System Intelligence Prototype (DMSIP). Two software products/concepts came out of DMSIP: 1) DMFE (the traditional "message handler") and 2) Message Toolkit (the notion of a product which processes incoming message traffic and sends data onto backside applications). DMFE is being used by operational sites because of a technology pull, not a Rome Laboratory technology push.

Rome Laboratory delivered the first Department of Defense (DoD) Intelligence Information System (DoDIIS) automated Indication and Warning (I&W) system to Defense Intelligence Agency (DIA) in the Fall of 1992, and to United States (US) Central Command (USCENTCOM) in the Spring of 1993. DAWS is currently installed at eight sites:

  • US Central Command (USCENTCOM) MacDill AFB, FL

  • Defense Intelligence Agency (DIA) Pentagon, Washington, D.C.

  • US European Command (USEUCOM) Patch Barracks, Stuttgart, Germany

  • US Pacific Command (USPACOM) Hickam AFB, HI

  • US Southern Command (USSOUTHCOM) Quarry Heights, Panama City, Panama

  • US Space Command (USSPACECOM) Cheyenne Mountain/Peterson AFB, CO

  • US Strategic Command (USSTRATCOM) Offutt AFB, NE

  • US Transportation Command (USTRANSCOM) Scott AFB, IL

The DAWS Message Front End (DMFE) is currently installed at three sites:

  • Air Force Technical Application Center (AFTAC) Patrick AFB, FL

  • Alaskan Command (ALCOM) Elemendorf, AK

  • PACOM ADP Support Site - Japan (PASS-J) Yokota Air Base, Japan

DAWS is designed in the spirit of the Intelligence Data Handling System (IDHS) open architecture and operates across multiple UNIX based platforms under multiple workstation configurations. Rome Laboratory developed DAWS with full user group participation, to serve as the DoDIIS core product for I&W. DAWS is open system compliant, therefore, it easily integrates into already existing computer environments based upon the client-server, open systems architecture. The system has been developed primarily for the I&W mission, however, current intelligence missions can utilize DAWS effectively. DAWS consists of government owned software and commercial off-the-shelf (COTS) software running on COTS hardware.

The DAWS Message Front End (DMFE) System provides client-server based tools to support basic "messge handling features" such as receipt, processing, archiving, dissemination, retrieval, display, and data extraction. Using the Defense Automated Warning System (DAWS) message support module as apoint of departure, the message handling software within DAWS was de-coupled from the rest of the DAWS applications into a "stand-alone" product. DMFE can be used as a traditional "messge handler" and Message Toolkit (the notion of a product which processes incoming messge traffic and sends data to backside applications). DMFE is a sold message handler that has proven itself at many sites in the DoD community for a number of years. The DoDIIS Management Board (DMB) has recommended DMFE be used at small to medium size sites.

Join the mailing list

Unconventional Threat podcast - Threats Foreign and Domestic: 'In Episode One of Unconventional Threat, we identify and examine a range of threats, both foreign and domestic, that are endangering the integrity of our democracy'

Page last modified: 28-07-2011 00:48:43 ZULU