This selection brings up a window with a list of communication
- Create Link - Links are the
lowest level method of specifying communications. This capability
permits the user to define specific connections between two assets.
While giving the user great control over the communications network,
it's very tedious. Note that not all links need to be manually
created; JFORCES will create links where it can infer the need for the
link. Most notably, this is done from every asset with a defined
command and control structure (or in the case of air defense assets, a
derived C2 structure) to it's command element.
- Delete Link - The inverse of creating a
- Create Star - This interface permits a
range of similar communications links to be re created simultaneously.
The good news is that this interface is most manageable in
small-to-moderate scenarios. For larger scenarios the interface gets
so loaded with options the human controls become very slow.
- Define Bands - This interface permits
users to specify communications bands and their maximum utilization.
If these bands are not defined communications between two assets is
limited only by the communications link capacity linking them. With
these bands communications can be limited by theater (and non military)
uses. In addition, these bands provide a framework for analyzing the
communications capabilities of the entire system.
- Define Default Loadings -
This permits the user to initialize data supporting the bandwidth
analysis. The user can limit the amount of bandwidth in any of the
defined bands to less than 100% to represent non-military uses.
- Click on any of the above hyperlinks for more information.
Selection causes the Communications
Definition Form to appear, initially devoid of data. The normal
approach to defining a communications link (or route) is as follows:
- The user selects a source for the communications. He does this
using the top half of the interface to pick an asset from either the
map or a list. Details for using this interface are found here.
- The user selects the communications suite to be used for
transmission from the "Xmit" line. If you hit the button and an empty
list appears, there are no communications suites on this platform type.
Go back to Database Prototyping and add a communications suite to the
platform before proceeding.
- Verify the 1- versus 2-way communications and the Data Division
options are set correctly.
- When the transmission communications suite was selected another
asset column appeared on the interface (Example).
This is the next destination. This can proceed indefinitely (here is an example
with three elements to get information from a B-52 to Offut). In
JFORCES descriptions the connection between any two adjacent assets is
referred to as a "Link" and the entire communications approach is a
- When done the user saves the data - NOTE: the interim steps are
not saved in the database, so nothing is saved until the user chooses
The user has some other options,
for example he can choose to reuse a previously defined communications
link from any asset by selecting the "Review Existing Links" from this
interface and double-clicking on any selection. If this window is
empty there are no predefined links for this asset so a new one will
need to be created.
The links defined either in the above "Create Link" option or the
"Create Star" option can be deleted through this interface. Choosing
this option causes the Communications
Reduction Form to appear. All links are presented along with
- Xmit Site
- Xmit Name
- Dest Site
- Dest Name
- Dest ID
Each may be deleted by clicking on Delete Selections.
This is a quick way to generate a number of similar links from a
selected asset. Selection causes the Define
Communications Star Form to appear. The user needs to:
- Select the central asset (the one logically in the middle of a
star architecture) in the He does this using the top half of the
interface to pick an asset from either the map or a list. Details for
using this interface are found
- Specify the transmission communications suite (this is the one on
the selected asset) on the line entitled: "Server Xmit". If the
presented comm suite list is empty there are no communications suites
on this platform type. Go back to Database Prototyping and add a
communications suite to the platform before proceeding.
- Select the communications suite used as a receiver on the other
assets from the line entitled "Client Rcvr:". Note that this title is
misleading when 2-way communications are selected; in this case both
selected suites are assumed to be both transmitters and receivers. Note: Occasionally I forget which
communications suite is on which platform. The easy way to review this
information is to use "Scenario Defn->Scenario
Evaluation->Subsystem Review by Type" and then select Communications
Suites. This provides a rundown of all communications suites on all
platforms currently in this scenario.
- At this point the lower part of the interface changes (example) to show all assets in this
scenario with the selected client subsystem. Select as many as you
want to link to.
- Verify the 1- versus 2- way option and the data division option
are correctly set
- Click on Save. The system will generate the required links.
This interface permits users to
specify communications bands and their maximum utilization. If these
bands are not defined communications between two assets is limited only
by the communications link capacity linking them. With these bands
communications can be limited by theater (and non military) uses. In
addition, these bands provide a framework for analyzing the
communications capabilities of the entire system. This choice presents
the Define Comm
Bands Form to the user along with all Currently Defined
Comm Bands. Each Band is listed by:
- Min. Freq (MHz)
- Max. Freq (MHz)
- Avail. Bandwidth (BPS Equivalent) Note: BPS is Bits per
All data listed may be changed or
New Bands may also be
created by selecting the Add button. When selected, the Define
Comm Bands Form appears.
Define Default Loadings
This selection presents the Default
Comm Loadings Form that lists the % Bandwidth Available for
Scenario. In this example, the are three types of communications
listed (VHF_SINGARS,HF,UHF) but when you use it the named bands might
be different because they are the bands defined above.The
available bandwidth for military operations in each of these Comm Bands
may be set/reset via a sliding scale bar in place for each. These
values represent the percent of the total bandwidth (defined in the
"Define Bands" interface, above) available for scenario use. In
addition default scenario loadings by assets is defined within this
interface on the next two lines. These loadings are:
Both of these are measured in bits per seconds and are used for default
band loading. The reason the communications are limited to non-ISR is
the ISR loading comes from the JFORCES sensor model. If you believe
there are additional ISR loadings that JFORCES is not addressing,
increase these two values accordingly.
- Typical non-ISR Comm traffic Per Radio Precombat
- Typical non-ISR Comm traffic Per Radio In Combat