Priority #2 MTN Planning Component

Priority #2 MTN Planning Component

MTN - Plan Creation and Plan Analysis:

Planning tool that assists JICO in designing a new, or modifying an existing MTA and runs a connectivity analysis

Password, user profile protected for creation and editing - JICO/designees

a)      Selectable permissions for others, with a read only default

2)      Conducts analysis based on long-haul and point-to-point communications and standard RF propagation characteristics, considering local environmental factors such as weather and terrain masking for friendly order of battle capabilities to include:

a)      Link 11 HF/UHF

b)      Link 16 UHF

c)      SADL

d)     VMF/CNR waveforms

e)      Satellite connectivity for data and voice (UHF, SHF, EHF)

f)       Surveillance radar propagation

3)      Conducts analysis for both NTR and ETR networks

4)      Identifies where relays are required to ensure connectivity

5)      Provides a moving, 3D visual depiction of connectivity analysis incorporating level 2 DTED for terrain depiction (i.e., displays connectivity of aircraft as it flies the length of its orbit/tasking)

6)      Able to import an existing Link 16 Network .jjl file to run message, connectivity analysis

a)      Able to select, filter and add participants for analysis

b)      Able to modify unit/platform locations, altitudes etc. for analysis

7)      Able to import OPTASK COMMs; compatible with all USMTF versions

8)      Able to import ATO/ACO to support analysis

a)      Compatible with the most current and all previous USMTF versions

b)      Able to filter/select overlays for unit and orbit locations

9)      Runs line of sight (LOS) connectivity analysis scenarios against simulated denied (jamming) environments

10)  Able to create connectivity graphic from program analysis that can be cut and pasted into slides for downloading and distribution (ex: Power point, Google earth, etc.) via AF Enterprise email

11)  Able to record, store, retrieve and distribute multiple MTA/MTN plans/analysis to distant users

12)  Produces reports based on network connectivity analysis with sortable, filterable fields

a)      Includes track count lists

b)      Includes track lists

13)  Products, reports and recordings must be in format interoperable (Ref: MIL-STD 6016D Section 3 paragraph 3.3) with other AOC/AF Enterprise systems allowing for import, export and emailing

14)  Maintains updateable data base of current M series/ J series/K series implementations by platform

a)      Password protected for JICO/Designees

b)      updateable via download with an option for manual updates by authorized operators (ICO) in REMARKS section (objective)

c)      Identification of data base update source, with date stamp of input

d)     Compatible with eSMART databases

e)      Hyperlinks to service Capabilities and Limitations databases

MTN Planning - OPTASK LINK:

Provides ability for user to import, create, edit, validate and export an OPTASK LINK message in machine-parseable USMTF B.1.01.11 format (threshold)

15)  Able to import and export existing OPTASK LINKs for editing, saving and redistribution on SIPRNET and/or coalition IP networks

16)  Compatible with all versions of OPTASK LINK from 2006 baseline to current version

17)  Compatible with Automated Message handling System (AMHS) to allow for distribution of OPTASK LINK

18)  Ability to read OPTASK COMMS document and be able to use/adapt frequency and crypto authorizations for use in the OPTASK LINK

19)  Ability to develop OPTASK LINK using an "expert" or "wizard" functionality in an Information Exchange Requirement (IER) style format

20)  Ability to create a database of unit capabilities (which links they are capable of, terminal/radio types, Terminal Base Addresses (TBAs), IPs/ports, etc. and points of contact information) to be used to populate required OPTASK LINK fields

21)  Provides examples of properly formatted fields and field parameters, for OPTASK LINK version used

22)  Validates OPTASK LINK for properly completed/formatted fields, providing user alerts for errors

23)  Alerts operator to conflicting or duplicate data: e.g. IUs, track blocks, IP assignments

24)  Breaks out unit/platform data from an OPTASK LINK into a downloadable, editable, selectable view (ability to sort and filter as well as select which columns to view and in what order) spreadsheet by :

a)      Platform strength (numbers)

b)      Unit

c)      Platform type

d)     PU/RU/JU (both individual or in IU pools of multiple assignments)

e)      Call sign

f)       Variable Message Format (VMF)/Combat Net Radio (CNR) Unit Reference Number (URN)

g)      VMF/CNR IP Addresses

h)      VMF/CNR Data Link Addresses

i)        JU Block for network enabled weapons (NEW)

j)        Primary & Alternate controller for NEW

k)      Track Blocks, with calculations for octal track capacity

l)        Forwarding Track Blocks, with calculations for octal track capacity

m)    Load file, option and sequence

n)      Location/Orbit

o)      Links Duty

p)      Terminal Base Addresses

q)      Remarks section - updateable by operator

r)       Unpopulated fields are displayed, but left blank on spreadsheet

25)  Spreadsheet must be in format interoperable (Ref: MIL-STD 6016D Section 3 paragraph 3.3) with other AOC/AF Enterprise systems allowing for import, export and emailing.

Interoperable with MTN Monitoring & Analysis component - OPTASK LINK created by Planning component can be imported by MTN Monitoring & Analysis component to allow for OPTASK LINK compliance monitoring and alerts