Document Page: First | Prev | Next | All | Image | This Release | Search
File: aabvb_29.txt
c. Command and Control Tools - Battle Staff Management System (BSMS)
(1) Background: The BSMS was highly reliable during the course of
Desert Shield/Storm. It was used extensively in communication with other
control centers and in transmitting the daily situation report. Use in
communicating with command was limited.
(a) Command did hot use the system because of the limited
audience (terminals) and the Wide range of addresses required on most
messages.
(b) Command policy required response to levies/queries in the
same media of receipt.
(c) In those instances where we (a control center) Requested
information from Command through BSMS, follow-up through WWMCCS was required
to get a response.
(2) Action Taken: Other communications media were used.
(3) Action Required: Command option: Enlarge BSMS network, retain
for local use, discontinue network but retain this TEMPEST-certified
equipment for processing classified plans and communications.
d. Information Channel
(1) Background: Information channel is not standardized. 0n a base
with CBPO servicing multiple MAJCOM units, directions need to come from one
source as designed--the parent MAJCOM of the PRC. Servicing CBPOs were
receiving numerous directions and requests from different MAJCOMs without the
parent MAJCOM being informed or aware of the situation. The massive flow of
information without proper coordination created confusion at base level and
isolation for the parent MAJCOM. The directions sent mixed signals which
complicated and delayed timely actions required to properly support the
deployment. Additionally, needed manpower was used to accomplish many
unneeded tasks. Our resources could have been tatter used if the base Level
had one director (MAJCOM) to work with.
(2) Action Required: Different MAJCOMs, other than the parent
MAJCOM of the servicing CBPO, should coordinate any Request for additional
information, i.e., departure reports and contingency reports, through the
parent MAJCOM. Procedures should be established for flowing information up
and down the chain and also keep all affected offices as addresses.
e. Changes to TED Tasking/Requirements After He Member Deployed
(I) Background: Numerous amendments to TDY orders were required due
to late message flow or incomplete/changed requirements, i. e., , TDY Length
changed from 30 to 90, 179, and 358 days; Group Travel was added to remarks
fiscal year 9I fund cite was added.
28
Document Page: First | Prev | Next | All | Image | This Release | Search