GSS Summary and Capabilities Matrix - FINAL.pdf

DRAFT

Further dissemination only as directed by AFLCMC/HNAI (Case #HNAI-XX-XXX Applies) or DoD higher authority.

Administrative/Operational Use; 26 January 2016. Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

U.S. GOVERNMENT INFORMATION IS FURNISHED TO THE GOVERNMENT OF COUNTRY UPON THE CONDITION THAT IT WILL NOT BE RELEASED TO ANOTHER NATION WITHOUT SPECIFIC AUTHORITY OF THE DEPARTMENT OF THE AIR FORCE OF THE UNITED STATES, THAT IT WILL BE USED FOR MILITARY PURPOSES ONLY, THAT INDIVIDUAL OR CORPORATE RIGHTS ORIGINATING IN THE INFORMATION, WHETHER PATENTED OR NOT, WILL BE RESPECTED, THAT THE RECIPIENT WILL REPORT PROMPTLY TO THE UNITED STATES ANY KNOWN OR SUSPECTED COMPROMISE, AND THAT THE INFORMATION WILL BE PROVIDED SUBSTANTIALLY THE SAME DEGREE OF SECURITY AFFORDED IT BY THE DEPARTMENT OF DEFENSE OF THE UNITED STATES. ALSO REGARDLESS OF ANY OTHER MARKINGS ON THE DOCUMENT, IT WILL NOT BE DOWNGRADED OR DECLASSIFIED WITHOUT WRITTEN APPROVAL OF THE ORIGINATING U.S. AGENCY. THIS DATA IS FOR INFORMATION ONLY.

NO US GOVERNMENT COMMITMENT TO SELL, LOAN, LEASE, CO-DEVELOP OR CO-PRODUCE DEFENSE ARTICLES OR SERVICES IS IMPLIED OR

INTENDED.

GSS Model A (Derived from Updated GSS draft version 20220531_V3)

Model Summary

Total Capabilities 113 (100%)

Total Required Capabilities

93 (82%)

Total Optional Capabilities

20 (18%)

Total Requirements 342 (100%)

Total Required Requirements

294 (86%)

Total Optional Requirements

48 (14%)

Total Threshold Requirements

232 (68%)

Total Objective Requirements

72 (21%)

Total Not Required Requirements

38 (11%)

Total Not Available Requirements

0 (0%)

GSS Features

Model Minimum Attributes

Characterization Single User, Link 16 Test Set, Simulator, Scenario Generator, Data Reduction Capability

Workstations One

GES MIDS LVT or JTRS, Ethernet/IP, local terminal control panel, Commercial GPS

Cost Model Low (Under $50k for applications)

Training Required Low

Networking Features Supports LAN and WAN IP interconnections with direct IP connect to Terminal

HMI Effective for a Training Function. Message constructions easy; however, time consuming, Graphics Display Commercial Maps, limited filters, limited symbol sets, pairing lines, Minimal Declutter Mechanisms

Link 16 Compatibility Message Formats to a single or multiple baselines, minimal transactional compliance

Alert Features Basic

Interconnection Capability IP and JREAP-C at minimum

Forwarding Features Objective

Data Recording DERG or other recording standard

Data Reduction Time ordered reports

Terminal Initialization Capability to view and edit IDSs

Advanced C2 Functions Objective

Psuedo Track Required

Range Training Operator Objective

Report Generators Canned reports of various Link messages

Online Help Objective

Detection of Link Anomalies

Upgradable to multi-terminal without replacement of entire GSS unit

Multi-Terminal Capability Upgradable to multi-terminal without replacement of entire GSS unit

Full GSS WAN Objective

Cyber User access controls

Required Model Capabilities

A. Unit Configuration (Common) (Total Capabilities: 4 | Total Requirements: 13)

THRESHOLD Capabilities for Unit Configuration (Common) (Total Threshold Capabilities: 4 | Total Threshold Requirements: 13)

A1. GPS operation (data and time hack for continuous operation) (Threshold Capability Includes 5 Requirements)

SHALL[24] The GSS TU SHALL[24] include a GPS receiver and SHALL[25] provide time/location data to the host (TWS) and a 1 Pulse Per Second (1PPS) synchronization pulse to the terminal, conditioned to the correct voltage and wave characteristics according to the respective terminal ICD.

SHALL[25] SHALL[25] provide time data to the host (TWS) and a 1 Pulse Per Second (1PPS) synchronization pulse to the Link 16 terminal(s), conditioned to the correct voltage and wave characteristics according to the respective terminal ICD or ICS.

SHALL[42] The GSS SHALL[42] include a UPS capability to provide power conditioning during normal usage, and uninterrupted power for a period of 5 minutes during power loss.

SHALL[74] The GSS TWS SHALL[74] provide wiring to connect to the GPS receiver that is located in the primary TU.

SHALL[110] The GSS SHALL[110] include a 1 PPS, 1Hz GPS receiver capable of providing the terminal in the TU with 1 Pulse per Second signal and also provide precise GPS time and location information compatible with the TWS and RU software.

A2. Power requirements and cords compatible with customer country's electrical infrastructure (Threshold Capability Includes 2 Requirements)

SHALL[89] The GSS computers SHALL[89] include the power connectors (plugs), inverter or converter necessary to transition from the customer’s native infrastructure power to computer power.

A3. GSS software by default runs from a user account without administrator privileges. (Threshold Capability Includes 1 Requirement)

SHALL[40] The GSS computers SHALL[40] be configured to allow the operation of the GSS software from a non-privileged (i.e. no administrator rights) operating system account.

SHALL[6410] The GSS SHALL[6410] ensure only authenticated users, devices and services are allowed access to, or interconnection with the GSS or its subsystems.

B. Unit Configuration (TU) (Total Capabilities: 12 | Total Requirements: 45)

THRESHOLD Capabilities for Unit Configuration (TU) (Total Threshold Capabilities: 10 | Total Threshold Requirements:

34)

B1. Transportable Transit Case with integrated 19" rack – MIDS LVT (Threshold Capability Includes 9 Requirements)

SHALL[15] The GSS TU SHALL[15] mount the terminal(s), in one or more, two-man lift transportable cases with a manageable weight as defined in MIL-STD-1472.

SHALL[16] SHALL[16] have labeling on the case exterior which displays the weight and dimensions in both English and metric measurements as well as a two-man lift warning. (Note: Lift capacity will be determined with the terminal LRUs removed).

Commented [EM1]: What is the difference between this and 24?

Commented [MCW2R1]: This provides the NTP to the TWS/RU units for the software.

Commented [MCW3]: Why the duplication?

Commented [EM4R3]: What is this shall even saying?

And why is it needed?

Commented [MCW5R3]: This is cyber security and system security best practice whereby the user software can run without administrator or root privileges. Running with admin/root privileges is extremely dangerous.

Commented [EM6]: “be capable” is a huge loop hole. Is it being mounted in a transportable case of not?

Commented [MCW7R6]: This has not been a problem in 15 years of using the original TRD, but I will modify the language.

Commented [EM8]: Lift capacity - why? Do we have a requirement to have LRUs removed?

Commented [MCW9R8]: On ruggedized transportable cases, you need to ensure that people know how many people are needed to safely move the equipment, the weight is listed in part to ease shipping/transportation, especially if it is going to be loaded on a plans for deployment.

SHALL[20] The GSS TU SHALL[20] operate with the terminal installed and operating with noise levels at or below 60 dBA at 1 meter.

SHALL[33] The GSS TU SHALL[33] incorporate a three position rotary switch to change power states of the terminal between "OFF", "Standby" and "ON".

SHALL[985] The GSS TU SHALL[985] include a cable grounded to the TU chassis capable of being connected to the grounding connector on the terminal(s) and remote power supply if it has a grounding point.

SHALL[986] The GSS TU SHALL[986] have secure mountings for all ancillary items within the transportable case or data cabinet.

SHALL[996] The GSS SHALL[996] include a network switch providing 12 or more 100/1G (or faster) ports with a SFP slot for fiber connectivity, natively compatible with 50Hz or 60Hz frequency 100-240 VAC power and the applicable IEC C-13 power cable.

B2. Power converter for MIDS LVT (Threshold Capability Includes 1 Requirement)

SHALL[18] The GSS TU SHALL[18] include the power connectors (plugs), inverter or converter necessary to transition from the local infrastructure power to terminal power.

B3. Cooling equipment for MIDS LVT terminal (Threshold Capability Includes 1 Requirement)

SHALL[37] The GSS TU SHALL[37] include a cooling capability sufficient to meet cooling requirements of the MIDS LVT as defined in the MIDS terminal hardware specification.

B4. Safety shutdown for thermal conditions (Threshold Capability Includes 1 Requirement)

SHALL[41] The GSS TU SHALL[41] provide protection for dangerous thermal levels within the terminal and incorporate a safety shutdown to cut power to the terminal.

B5. Link 16/MIDS compatible Notch Filter (Threshold Capability Includes 3 Requirements)

SHALL[26] The GSS TU SHALL[26] include dual frequency notch filters for the 1030 MHz and 1090 MHz bands to prevent leakage into the Identification Friend or Foe (IFF) reserved frequencies.

SHALL[992] The GSS TU SHALL[992] incorporate an internal bracket to accommodate mounting the notch filter.

SHALL[993] The GSS TU SHALL[993] supply all necessary patch cables to connect the notch filter in-line with the RF antenna line.

B6. LRU Interconnect Wiring for the MIDS LVT Terminal (Threshold Capability Includes 4 Requirements)

SHALL[35] The GSS TU SHALL[35] include all required LRU interconnect wiring for the MIDS Terminal and the Remote Power Supply (RPS) of the MIDS LVT.

Commented [EM10]: All the equipment should be grounded, right?

Commented [MCW11R10]: Yes, but this is a different requirement. Many vendors neglect to put the terminal grounding plug ground connection in. It is being specifically called out for that reason.

Commented [EM12]: What in the world are “all ancillary items”? How can anyone meet this requirement?

Commented [MCW13R12]: Ancillary items are any vendor delivered components which may be outside of the case otherwise. Before this requirement was in place, things like notch filters and such were just plopped on top of the case and it was messy and dangerous.

Commented [EM14]: This for TWS or TU? (Section issue)

Commented [MCW15R14]: Where is the switch is should be left to the vendor. I have removed the TU/TWS specification.

Commented [EM16]: Different from 89?

Commented [MCW17R16]: The TU power supply for the terminal(s) requires a higher amperage plug often times Commented [EM18]: How does the GSS TU know the thermal level in the terminal? Why isn’t this a terminal ...

Commented [MCW19R18]: The terminal reports the thermal override via a discrete feedback signal. The cooling ...

Commented [EM20]: The “if” creates a loophole?

Commented [MCW21R20]: Not all terminal types use the L band, thus the original wording. I have removed the L ...

Commented [EM22]: Needed?

Commented [MCW23R22]: YES!

Commented [EM24]: This really should be defined…..

How can this shall be analyzed, costed, met?

Commented [MCW25R24]: The whole point of this reduced SRD document is to provide the vendors an option ...

Commented [EM26]: I don’t know what MT and RPS is…..

Is it defined anywhere? We assume vendors know…>?

Commented [MCW27R26]: MT=MIDS Terminal, RPS=Remote Power Supply. Both are now spelled out, but ...

SHALL[988] The GSS SHALL[988] include necessary adapters for proper terminal installation to include a 90[degrees] N-male adapter for the MIDS primary antenna connection, and a HN-N adapter for the secondary MIDS antenna connection.

SHALL[990] The GSS SHALL[990] include 50 watt attenuation and termination for the MIDS antenna port B to completely dissipate any signal; on an the MIDS terminal.

B7. Crypto fill port on the TU external control panel (Threshold Capability Includes 1 Requirement)

SHALL[926] The GSS TU SHALL[926] include on the control panel a crypto fill port compatible with the Type-1 cryptographic Data Transfer Device (DTD) fill cable approved for use in the country in which it will be operated.

B8. Two PTT Link 16 digital voice channels and associated controls. (Threshold Capability Includes 7 Requirements)

SHALL[927] The GSS TU SHALL[927] provide all necessary wiring and circuitry to provide two Link 16 digital "push to talk" (PTT) voice channels from the TU chassis.

SHALL[928] The GSS TU SHALL[928] include a PTTT Link 16 voice channel control panel.

SHALL[929] SHALL[929] an independent volume control for each of the two voice channels.

Requirement SHALL[929] is included within Requirement SHALL[928]

SHALL[930] SHALL[930] an independent H-250 handset connector for each voice channel.

Requirement SHALL[930] is included within Requirement SHALL[928]

SHALL[931] SHALL[931] an ON/OFF toggle switch for each of the two voice channels.

Requirement SHALL[931] is included within Requirement SHALL[928]

SHALL[994] SHALL[994] a speaker and microphone wired and mounted to the TU chassis.

SHALL[995] SHALL[995] Noise cancelling headset and microphone capable of being remoted 20 meters from the TU chassis.

B9. MIDS Support Port Interface (Threshold Capability Includes 2 Requirements)

SHALL[27] The GSS TU SHALL[27] provide wiring to connect to the terminal support port to allow compatibility with diagnostic support tools such as the Diagnostic Support Tool (DST).

SHALL[45] The GSS TU SHALL[45] provide a powered AUI to 10BaseT Ethernet transceiver inside the case to support diagnostic support tools.

B10. MIDS Ethernet Interface (Threshold Capability Includes 2 Requirements)

SHALL[50] The GSS TU SHALL[50] be able to be physically separated from the TWS by at least 10 meters.

SHALL[212] The GSS SHALL[212] be capable of packet inspection (“packet sniffing”) the Ethernet interface between the host and the terminal with the ability to process received data relevant to all GSS functions.

Appropriate alerts may apply to processed data.

Commented [EM28]: Both of these are required for install? (100% of the time?)

Commented [MCW29R28]: Depends on the vendor design for the system, but in most cases, yes. This squabbling over pennies though.

Commented [EM30]: Where are these installed? I am thinking that all these ‘include’ but not install shalls are odd.

Commented [MW31R30]: This normally attached to the terminal antenna port B as described. The installation is done by the operator when they put the terminal in the TU.

Commented [EM32]: Not defined

Commented [MW33R32]: What’s not defined? This appears quite clear to me.

Commented [MELCUAA34]: Does it need to be a ‘toggle’

Commented [MW35R34]: Yes, operators may have gloves on.

Commented [MELCUAA36]: Both 994 and 995 are required?

And 20 meters?!

Commented [MCW37R36]: Yes, but removed the 20m requirement for the speaker and microphone.

Commented [MELCUAA38]: Why does the TU need to provide a connection to the MIDS radio? Isn’t the one on radio sufficient?

Commented [MCW39R38]: The terminal has a data bus connection and a support port connection. They are separate but both are necessary. Removing this capability would be a terrible disservice to the customer.

Commented [MELCUAA40]: ‘capable’

Commented [MCW41R40]: Changed wording.

Commented [MELCUAA42]: Appropriate alerts may…?

Commented [MCW43R42]: The alerts are defined in the alerts section

OBJECTIVE Capabilities for Unit Configuration (TU) (Total Objective Capabilities: 1 | Total Objective Requirements:

2)

B11. Noise Emissions at 1 m are below 60 dBA (Objective Capability Includes 2 Requirements)

SHALL[20] The GSS TU SHALL[20] operate with the terminal installed and operating with noise levels at or below 60 dBA at 1 meter.

SHALL[21] The GSS TU SHALL[21] allow the use of variable speed fans which can exceed 60 dBA during startup and when the ambient room temperature exceeds 27[degrees]C.

NOT REQUIRED Capabilities for Unit Configuration (TU) (Total Not Required Capabilities: 1 | Total Not Required Requirements: 9)

B12. Rack Mounted, 19" rack – MIDS LVT (Not Required Capability Includes 9 Requirements)

SHALL[32] The GSS TU SHALL[32] be capable of mounting a MIDS LVT in a data cabinet which conforms to the following: 48 or more inches high, by 24 inches wide by 42 inches deep, in a 4 post, standard 19” data rack configuration, with caster wheels rated for 500+ lbs., metal mesh or ventilated doors, solid metal side panels, ventilated metal top. A heavy-duty sliding shelf installed with terminal, cooling fan, electrical controls mounted to it for easy terminal exchange. A 3U sliding drawer for storage, keyed locks for the front and rear doors and a locking mechanism to prevent unauthorized terminal removal.

C. Unit Configuration (TWS) (Total Capabilities: 7 | Total Requirements: 17)

THRESHOLD Capabilities for Unit Configuration (TWS) (Total Threshold Capabilities: 4 | Total Threshold Requirements*: 6)

(This capability is one option in the mutually exclusive choice between the following capabilities: C1, C2, C3, C4) C3. Desktop Computer (Threshold Capability Includes 3 Requirements)

• Note 12. For mutually exclusive choices: If one is a THRESHOLD, the other must be downgraded to Not Required.

SHALL[4] The GSS applications SHALL[4] be hosted in a standard desktop computer.

C5. Noise Emissions at 1m are below 55 dBA (Threshold Capability Includes 1 Requirement)

SHALL[72] The GSS chassis SHALL[72] operate at sound levels not exceeding 55 dBA at 1 meter.

C6. Backup Hard Drive with Duplicate Bootable Image (Threshold Capability Includes 1 Requirement)

SHALL[57] The GSS TWS SHALL[57] prevent all read and write operations to the backup hard drive during normal operations.

C7. Display, mouse and keyboard cables to remote the TWS user from the TWS computer at least 3 meters (Threshold Capability Includes 1 Requirement)

Commented [MELCUAA44]: How was this arrived at?

MIL-STD-882? 1474?

Do we have any system safety requirements?

Commented [MCW45R44]: MIL-STD 1472 defines human operator safety items and we reference this mil-std here and many other places in the TRD/SRD

Commented [MELCUAA46]: ‘capable’. Table 4?

Commented [MCW47R46]: I fixed this in the last version I sent you. I copying over the change from that version.

Commented [MELCUAA48]: Again, why? (I believe 65 is the office environment number?

Commented [MCW49R48]: Ever work for an 8 hour shift next to a vacuum cleaner running?

Commented [MELCUAA50]: ‘normal’?

Commented [MCW51R50]: Yes, normal, not reduced functionality, due to an error or recovery from an error.

SHALL[58] The GSS TWS SHALL[58] provide display, mouse and keyboard cables to allow the user to be at least 3 meters from the TWS.

NOT REQUIRED Capabilities for Unit Configuration (TWS) (Total Not Required Capabilities: 1 | Total Not Required Requirements*: 5)

(This capability is one option in the mutually exclusive choice between the following capabilities: C1, C2, C3, C4) C1. Transportable Transit Case with integrated 19" rack (Not Required Capability Includes 5 Requirements)

• Note 12. For mutually exclusive choices: If one is a THRESHOLD, the other must be downgraded to Not Required.

SHALL[5] The GSS applications SHALL[5] be hosted in a 19" rack mounted computer.

SHALL[6] The GSS applications SHALL[6] be hosted in a transportable case with a maximum two-man lift manageable weight as defined in MIL-STD-1472.

SHALL[7] SHALL[7] have labeling on the case exterior which displays the weight and dimensions in both English and metric measurements, as well as a two-man lift warning.

(This capability is one option in the mutually exclusive choice between the following capabilities: C1, C2, C3, C4) C2. 19" Rack mounted configuration (Not Required Capability Includes 3 Requirements)

• Note 12. For mutually exclusive choices: If one is a THRESHOLD, the other must be downgraded to Not Required.

SHALL[5] The GSS applications SHALL[5] be hosted in a 19" rack mounted computer.

(This capability is one option in the mutually exclusive choice between the following capabilities: C1, C2, C3, C4) C4. Laptop Computer (Not Required Capability Includes 3 Requirements)

• Note 12. For mutually exclusive choices: If one is a THRESHOLD, the other must be downgraded to Not Required.

SHALL[3] The GSS applications SHALL[3] be hosted in a laptop computer.

F. Ground Support System TWS (Features) (Total Capabilities: 2 | Total Requirements: 2)

FA. Operational Modes (Total Capabilities: 2 | Total Requirements: 2)

THRESHOLD Capabilities for Operational Modes (Total Threshold Capabilities: 2 | Total Threshold Requirements: 2)

FA1. Operational Mode as Host Mode (HM) (Threshold Capability Includes 1 Requirement)

• Note 3. Capability to connect to the terminal as a typical host, over the MIL-STD-1553B or Ethernet interface and executing the Host functions according to the platform Types specified in the MIDS or Class 2 ICDs.

• Note 14. There are many derived requirements that roll up into this capability that are specifically listed elsewhere and not included here.

SHALL[114] SHALL[114]: shows the terminal interfaces that the GSS supports in HM.

Note: References to the parent LVT includes the variants (e.g. LVT-1 includes LVT-4 and LVT-6;

SHALL[114]: Host Mode (HM) Table 7 shows the Note: Table 7 references the parent LVT whic

Commented [EM52]: Should we define what this limits is? What section?

Commented [MCW53R52]: Without knowing the vendor’s design, this would be impossible. That’s why Mil- Std 1472 is referenced.

Commented [EM54]: I believe labeling is also defined in 1472?

Commented [MCW55R54]: ok

Commented [EM56]: Table? Update to remove older versions of terminal?

Commented [MCW57R56]: Revised.

LVT-2 includes LVT-11). Ground Support System Host Mode Interface Requirements Requirement HM Interface Requirements Data Bus ICD Requirement SHALL[114] includes the following Requirements: SHALL[120], SHALL[133], SHALL[135], SHALL[136], SHALL[137], SHALL[138], SHALL[139], SHALL[143], SHALL[144], SHALL[146], SHALL[147], SHALL[148], SHALL[149], SHALL[150], SHALL[152], SHALL[153], SHALL[156], SHALL[157], SHALL[158], SHALL[159], SHALL[160], SHALL[161], SHALL[162], SHALL[163], SHALL[164], SHALL[165], SHALL[166], SHALL[167], SHALL[168], SHALL[169], SHALL[170], SHALL[171], SHALL[172], SHALL[173], SHALL[174], SHALL[176], SHALL[181], SHALL[182], SHALL[183], SHALL[185], SHALL[187], SHALL[190], SHALL[191] and LVT-6; LVT-2 includes LVT-11). Table Requirements Requirement HM Interface Requir Requirement SHALL[114] includes the followin

SHALL[135], SHALL[136], SHALL[137], SHALL[13

SHALL[147], SHALL[148], SHALL[149], SHALL[15

SHALL[158], SHALL[159], SHALL[160], SHALL[16

SHALL[166], SHALL[167], SHALL[168], SHALL[16

SHALL[174], SHALL[176], SHALL[181], SHALL[18

SHALL[191]

FA2. Administrative Functions to password protect the TWS/RU Configuration (Threshold Capability Includes 1 Requirement)

SHALL[979] The administrative function SHALL[979] be protected by password and able to be executed at any TWS/RU system.

I. Ground Support System Terminal Management (Total Capabilities: 9 | Total Requirements: 51)

THRESHOLD Capabilities for Ground Support System Terminal Management (Total Threshold Capabilities: 7 | Total Threshold Requirements: 45)

I1. Initialization and Control (Threshold Capability Includes 25 Requirements)

• Note 8. Capability to initialize a terminal with a tool generated network design load and then apply typical terminal control parameters to achieve net entry or reset functions within the terminal

SHALL[133] The GSS SHALL[133] accept initialization data in electronic media from the Network Design Cell

SHALL[134] SHALL[134] pass the initialization data to the Link 16 terminal according to the protocols established in the ICD

SHALL[137] The GSS SHALL[137] provide nonproprietary templates that display the initialization data items in human readable form that is decipherable without the assistance of an ICD.

SHALL[138] The GSS SHALL[138] additionally display initialization data words in hexadecimal.

SHALL[140] The GSS SHALL[140] be able to use [File types and sources of initialization data sets for the MIDS LVT family of terminals include] locally generated files

SHALL[146] The GSS SHALL[146] provide the capability to perform individual initialization data changes to the terminal by individual item, or as a group of items (e.g., full time slot block).

SHALL[147] The GSS SHALL[147] allow the operator to send initialization data changes to the terminal as hexadecimal word inputs by block and word address.

SHALL[148] The GSS SHALL[148] allow the operator to send nonzero data changes in hexadecimal to the terminal for words that are not defined within the respective host ICD.

Commented [EM58]: How does this compare to cyber requirements?

Commented [MCW59R58]: This has little to do with cyber. This is restrict certain functions to people who have the appropriate knowledge and permissions.

Commented [EM60]: This entire section seems like gold plated functions…. Required?

Commented [MCW61R60]: YES

Commented [EM62]: What electronic media?

Commented [MCW63R62]: Normally a zip file on a CD, flash drive, etc.

Commented [MW64]: Remove the space between “non proprietary”

Commented [EM65]: What?

Commented [MCW66R65]: Fixed.

Commented [EM67]: Why do we want this capability?

(and 147, 148, 149, 150….)

Commented [MCW68R67]: This is to refine/fix load files and diagnose terminal/network issues locally. This is necessary.

SHALL[149] The GSS operator SHALL[149] be capable of setting any initialization field to any value that fits within the field, even undefined values.

SHALL[150] The GSS SHALL[150] allow the operator to set initialization data parameters to valid values that are marked "Not Used" for a specified Platform, e.g., "Not Used by F-15."

SHALL[151] For FDL terminal applications, the GSS SHALL[151] provide special initialization data word templates for data parameters implemented in the FDL terminal but not specified in F-15 ICD.

SHALL[152] The GSS SHALL[152] [Provide individual user controls to invoke terminal and network control items to include] set and reset Net Time Reference (NTR)

SHALL[153] The GSS SHALL[153] set JTIDS time of day (JTOD).

SHALL[154] (Note: A choice exists for the following requirements: SHALL[154]; SHALL[155]) The GSS SHALL[154] accept operator input for the JTOD input setting

SHALL[155] (Note: A choice exists for the following requirements: SHALL[154]; SHALL[155]) SHALL[155] accept one instance of GPS time biased by an offset as the source for the input to the JTOD.

SHALL[156] The GSS SHALL[156] show JTOD reported from the terminal on a first tier status line on the monitor.

SHALL[157] The GSS SHALL[157] [Provide individual user controls to invoke terminal and network control items to include] set Start Net Entry (SNE), Net Entry Reset (NER), Navigation Reset (NAVR), and IPF Reset.

SHALL[158] The GSS SHALL[158] [Provide individual user controls to invoke terminal and network control items to include] set all Radio COMM modes

SHALL[159] The GSS SHALL[159] [Provide individual user controls to invoke terminal and network control items to include] set all TDMA modes

SHALL[160] The GSS SHALL[160] [Provide individual user controls to invoke terminal and network control items to include] set Long Term Transmit Inhibit (LTTI)

SHALL[161] The GSS SHALL[161] [Provide individual user controls to invoke terminal and network control items to include] set all Interface Protection Feature (IPF) modes

SHALL[162] The GSS SHALL[162] [Provide individual user controls to invoke terminal and network control items to include] set date though both Initialization Data Change or special input carrier, e.g., Terminal Input Message (TIM) 7, if available

SHALL[163] The GSS SHALL[163] [Provide individual user controls to invoke terminal and network control items to include] set Organizational User Type

SHALL[164] The GSS SHALL[164] [Provide individual user controls to invoke terminal and network control items to include] set Restart Use Current, and Restart Load Use Defaults

Commented [EM69]: Not familiar with FDL (what is it)?

And why F-15 specific?

Commented [MCW70R69]: FDL = Fighter Data Link terminal (aka LVT-3), only the F-15 uses this terminal generally.

Commented [MW71]: Space after comma missing

Commented [EM72]: One instance?

Commented [MCW73R72]: You can’t use multiple time offsets to create multiple simultaneous networks with the same crypto.

Commented [EM74]: What is a first tier status line?

Commented [MCW75R74]: The TRD had multiple tiers of status and alerts.

SHALL[165] The GSS SHALL[165] [Provide individual user controls to invoke terminal and network control items to include] calculate and set the Current Crypto Period Designator (CCPD).

SHALL[166] The GSS SHALL[166] [Provide individual user controls to invoke terminal and network control items to include] set External Time Reference (ETR) parameters.

I2. Status Monitor (Threshold Capability Includes 10 Requirements)

SHALL[135] The GSS SHALL[135] monitor the status of the terminal initialization.

SHALL[136] The GSS SHALL[136] show the initialization status on a first tier status line on the monitor.

SHALL[167] The GSS SHALL[167] show the Net Entry status on a first tier status line on the monitor.

SHALL[169] The GSS SHALL[169] display a live red/green status for all terminal alerts.

SHALL[171] The GSS SHALL[171] show a progress indicator for all operator commands to the terminal that invoke a terminal process that takes more than 5 seconds to respond.

SHALL[172] The GSS SHALL[172] display System Time (if different from JTOD).

SHALL[190] The GSS SHALL[190] alert the operator when faults are detected on the bus such as "bus fail," and also "busy" or "late" response faults if they occur more frequently than once every two hours.

SHALL[191] The GSS SHALL[191] alert the operator when the GSS terminal receives control or change directives over the air.

SHALL[192] SHALL[192] display all relevant information on the control changes to the operator.

I3. Monitor All Terminal Status Words (Threshold Capability Includes 1 Requirement)

• Note 9. Capability to extract and format the terminal status data and present it to the operator.

SHALL[168] The GSS SHALL[168] provide the operator the capability to request/monitor any terminal status word in hexadecimal.

I4. Prepare, edit, save locally generated NDL (Threshold Capability Includes 2 Requirements)

SHALL[139] The GSS SHALL[139] provide the capability to import, edit, search by text string and save initialization data files locally on the GSS host computer.

SHALL[140] The GSS SHALL[140] [File types and sources of initialization data sets for the MIDS LVT family of terminals include] locally generated files

I5. Execute and Evaluate BIT (Threshold Capability Includes 1 Requirement)

SHALL[170] The GSS SHALL[170] provide the operator the capability to initiate Built In Test (BIT) and display the terminal responses.

I6. Display Terminal Generated message statistics (Threshold Capability Includes 2 Requirements)

SHALL[187] The GSS SHALL[187] poll terminal statistics and display the terminal statistics in a dynamically updating list on a periodic 12 second basis.

Commented [EM76]: This shall is repeated three times?

Commented [MCW77R76]: SHALL 140 defines an specification used in three capabilities.

Commented [EM78]: Do we require BIT capability?

Commented [MCW79R78]: YES

Commented [EM80]: Terminal statistics = ?

12 seconds, why?

Commented [MCW81R80]: As defined in terminal ICD.

SHALL[424] The GSS SHALL[424] poll the terminal and report ongoing terminal transmission statistics in Host Mode.

I7. Implement External Time Reference (ETR) for terminal (Threshold Capability Includes 4 Requirements)

SHALL[173] The GSS SHALL[173] receive external time from a GPS receiver compatible with military time standards

SHALL[174] The GSS SHALL[174] provide the ETR message to the terminal using the appropriate input message in accordance with the ICD.

SHALL[175] The GSS SHALL[175] channel the 1 Hz pulse immediately from the receiver to the terminal

SHALL[1024] The GSS SHALL[1024] channel the time data to the terminal within 400ms.

OBJECTIVE Capabilities for Ground Support System Terminal Management (Total Objective Capabilities: 2 | Total Objective Requirements: 6)

I8. Provide Full Operator Controls over common carrier header data and implement loopback ID process. (Objective Capability Includes 5 Requirements)

SHALL[182] The GSS SHALL[182] provide the operator full control over all Link 16 common carrier headers for all four message categories: an individual message, a message type (e.g., J3.2), a message group (e.g., J2.x), all messages.

SHALL[184] SHALL[184] alert the operator for messages not transmitted with their terminal reported fault code.

SHALL[185] The GSS SHALL[185] provide the capability for the operator to select specific messages for status reporting

SHALL[186] the GSS SHALL[186] report the JTOD time-stamped history of all status items on the selected message to the operator beginning with the initial placement of the message on the terminal bus.

I9. Generate Terminal 12 second statistics in NEM (Objective Capability Includes 1 Requirement)

• Note 13. These capabilities have been added to the original Capabilities Matrix, because they correspond to either essential requirements for a quality product, or to derived requirements.

SHALL[425] In NEM , the GSS SHALL[425] generate statistics for the "Successful Loopbacks" and "Received Message" terminal statistics over 12-second frames aligned to JTOD using total messages received from the Host and total messages sent to the Host, respectively.

L. Ground Support System (Data Link Standards) (Total Capabilities: 15 | Total Requirements: 16)

THRESHOLD Capabilities for Ground Support System (Data Link Standards) (Total Threshold Capabilities: 1 | Total Threshold Requirements: 1)

L1. MIL-STD-6016F change 1 (or most current) / Link 16 (Threshold Capability Includes 1 Requirement)

SHALL[44] The GSS SHALL[44] conform to the message structures, constructs, and transactional processes defined in MIL-STD-6016Fch1 (most current).

Commented [EM82]: HM = ?

Commented [MCW83R82]: Host Mode.

Commented [EM84]: Do we need to define which type GPS receiver to supply?

Commented [MCW85R84]: No

Commented [EM86]: What is ‘immediately’? 1024 has 400ms….

Commented [MCW87R86]: Pulse vs data.

Commented [EM88]: Can you find a word other than fabricate? (invent or concoct (something), typically with deceitful intent)

Commented [MCW89R88]: MITRE has a fabrication shop and they build prototypes, not deceit.

OBJECTIVE Capabilities for Ground Support System (Data Link Standards) (Total Objective Capabilities: 6 | Total Objective Requirements: 7)

L2. MIL-STD-6016B / Link 16 (Objective Capability Includes 1 Requirement)

SHALL[610] The GSS SHALL[610] conform to the message structures, constructs, and transactional processes defined in MIL-STD-6016B.

L3. MIL-STD-6016C / Link 16 (Objective Capability Includes 1 Requirement)

SHALL[611] The GSS SHALL[611] conform to the message structures, constructs, and transactional processes defined in MIL-STD-6016C with Change 1.

L4. MIL-STD-6016D / Link 16 (Objective Capability Includes 1 Requirement)

SHALL[612] The GSS SHALL[612] conform to the message structures, constructs, and transactional processes defined in MIL-STD-6016D.

L5. STANAG 5516 Edition 2 / Link 16 (Objective Capability Includes 1 Requirement)

SHALL[614] The GSS SHALL[614] conform to the message structures, constructs, and transactional processes defined in STANAG 5516 Edition 2.

L6. STANAG 5516 Edition 3 / Link 16 (Objective Capability Includes 1 Requirement)

SHALL[615] The GSS SHALL[615] conform to the message structures, constructs, and transactional processes defined in STANAG 5516 Edition 3.

L7. MIL-STD-6020A / TDL Forwarding Rules (Objective Capability Includes 2 Requirements)

SHALL[690] The GSS SHALL[690] forward TADIL-J message data using the forwarding rules, message translation and data element conversion rules defined in MIL-STD-6020B, Appendix E. [Note: These rules apply independently from the encapsulation protocol used for transfer on a link.

NOT REQUIRED Capabilities for Ground Support System (Data Link Standards) (Total Not Required Capabilities: 8 | Total Not Required Requirements: 8)

L8. MIL-STD-6016A / Link16 (Not Required Capability Includes 1 Requirement)

SHALL[609] The GSS SHALL[609] conform to the message structures, constructs, and transactional processes defined in MIL-STD-6016A.

L9. STANAG 5516 Edition 1 / Link 16 (Not Required Capability Includes 1 Requirement)

SHALL[613] The GSS SHALL[613] conform to the message structures, constructs, and transactional processes defined in STANAG 5516 Edition 1.

L11. STANAG 5516 Edition 4+ / Link 16 (Not Required Capability Includes 1 Requirement)

Commented [MW90]: Why is shall 690 text duplicated?

Commented [EM91]: Get rid of them?

Commented [MCW92R91]: I’d leave them.

SHALL[616] The GSS SHALL[616] conform to the message structures, constructs, and transactional processes defined in STANAG 5516 Edition 4+.

L12. STANAG 5516 Edition 5 / Link 16 (Not Required Capability Includes 1 Requirement)

SHALL[617] The GSS SHALL[617] conform to the message structures, constructs, and transactional processes defined in STANAG 5516 Edition 5.

L13. STANAG 5516 Edition 6 / Link 16 (Not Required Capability Includes 1 Requirement)

SHALL[1045] The GSS SHALL[1045] conform to the message structures, constructs, and transactional processes defined in STANAG 5516 Edition 6.

L14. STANAG 5522 Edition 2 / Link 22 (Not Required Capability Includes 1 Requirement)

TBD

L16. MIL-STD-6013A / ATDL-1 (Not Required Capability Includes 1 Requirement)

TBD

L17. MIL-STD-6017C / VMF (Not Required Capability Includes 1 Requirement)

SHALL[751] The message baseline for the VMF implementation SHALL[751] be in accordance with MIL-STD-6017.

M. Ground Support System (Terminal Interfaces) (Total Capabilities: 2 | Total Requirements: 6)

THRESHOLD Capabilities for Ground Support System (Terminal Interfaces) (Total Threshold Capabilities: 1 | Total Threshold Requirements: 3)

M2. MIDS LVT-1 Platform D (Objective Capability Includes 3 Requirements)

SHALL[28] the GSS SHALL[28] interface within any combination depending on the configuration.

SHALL[29] The GGS SHALL[29] use Terminal: LVT-1 and Variants; Nomenclature: AN/USQ-140(V)1 (C) Plus Others

SHALL[120] SHALL[120] MIDS LVT 1 Platform Type D

O. Ground Support System (Message Generator - Scenario Generator - Object Emulator) (Total Capabilities: 14 | Total Requirements: 62)

THRESHOLD Capabilities for Ground Support System (Message Generator - Scenario Generator - Object Emulator) (Total Threshold Capabilities: 12 | Total Threshold Requirements: 60)

O1. Scripting Messages (Threshold Capability Includes 25 Requirements)

Commented [EM93]: What? What are these shalls saying (28, 29, 120)? What is the requirement.

Commented [MCW94R93]: Revised.

SHALL[437] The GSS Data Link Message Generator (DLMG) criteria SHALL[437] be message type, word structure, field, and unit value. Within the Link 16 (TADIL J) constructs this would be equivalent to the J Message Type, TADIL J Word structure, Data Field Identifier (DFI), Data Unit Identifier (DUI), and Data Item (DI).

SHALL[438] The GSS DLMG SHALL[438] allow any structures or coded values that fit within the fields regardless of whether the applicable standard provides for such structures or standards.

SHALL[439] The GSS DLMG SHALL[439] allow the messages to be sent on command, on a timer aligned to JTOD, or on a relative time offset from scenario start time.

SHALL[440] The GSS DLMG SHALL[440] allow the operator to specify a start time, end time, update rate, or total number of reports for any scripted message.

SHALL[441] The GSS DLMG SHALL[441] allow the operator to control all header fields.

SHALL[445] For Loopback ID (LBID) processing , the GSS SHALL[445] provide the operator an enable button that will set the LBID during run mode.

SHALL[446] This capability SHALL[446] override a hard-set value in the LBID field.

SHALL[447] For multi-word messages exceeding three TADIL J words , the GSS SHALL[447] allow the operator to specify sequences and recurrence rates for the sequences.

SHALL[448] The GSS DLMG SHALL[448] allow the operator to construct any defined Link 16 message through this scripting function with a point and click style interface.

SHALL[449] The GSS DLMG SHALL[449] allow the operator to construct any defined Link 11 (TADIL A/B) message through this scripting function with a point and click style interface.

SHALL[450] The GSS DLMG SHALL[450] allow the operator to construct any defined Link 1 message through this scripting function with a point and click style interface.

SHALL[451] The GSS SHALL[451] allow full duplex pseudo-track on both red and blue designated forces.

SHALL[452] The GSS DLMG SHALL[452] allow the operator to construct data link messages through hexadecimal word input.

SHALL[453] Where coded values are input, the GSS DLMG SHALL[453] allow operator input of data in decimal, octal or hexadecimal form.

SHALL[454] Where modal values are input , the GSS DLMG SHALL[454] allow operator input of data both the DI representation by the standard and a human readable meaning.

SHALL[455] The GSS DLMG SHALL[455] allow the operator to input position data in Lat/Lon, MGRS, or UTM coordinates.

SHALL[456] The default input form for position data SHALL[456] be Lat/Lon.

SHALL[457] The input for Lat/Lon SHALL[457] be configurable by the operator as fine format (Degrees:Minutes:Seconds:2DecimalPlaces) or coarse format (Degrees:Minutes.3Decimal Places) or decimal degrees (Degrees.Decimal Minutes and Seconds).

Commented [EM95]: What is DLMG?

Commented [MCW96R95]: Data Link Message Generator

Commented [EM97]: Even if Link 11 isn’t a requirement?

(same idea 450)

Commented [MCW98R97]: If you interconnect the GSS with other systems via JREAP-C, SIMPLE, etc, then this would be useful.

SHALL[458] The GSS SHALL[458] allow the operator to input data in a scripted message by mouse selection to a location on the map.

SHALL[459] The GSS DLMG SHALL[459] allow the operator to input speed in dm/hr, km/hr, nm/hr, or mph.

SHALL[460] The default input form for position data SHALL[460] be dm/hr.

SHALL[461] The GSS DLMG SHALL[461] provide special processing to sequence J3 tracks between specific type and platform activity.

SHALL[462] the alternating sequence SHALL[462] be selectable from the basic track template where the user has defined both Platform Activity and Specific Type.

SHALL[620] Subject to the conformance standard in the immediately preceding section, the GSS SHALL[620] construct and decode all messages as specified in the standard according to the defined TADIL-J word structures and encoding in accordance with the Data Field Identifiers (DFI), Data Unit Identifiers (DUI) and Data Items (DI).

O2. Script messages offline or online (Threshold Capability Includes 4 Requirements)

SHALL[463] The DLMG capabilities SHALL[463] be available in either online or offline operations. The offline operations comprise non-real-time scenario generation.

SHALL[467] The GSS DMLG SHALL[467] provide the operator a capability to modify scripted messages during on-line operations.

SHALL[468] The GSS DLMG SHALL[468] provide a duplicate message capability to allow the operator to quickly make similar messages

SHALL[469] SHALL[469] allow the operator to make changes to the duplicated message. For example, the operator may wish to script five different Air-to-Ground Air Support Operations J12.0 Mission Assignment messages addressed to the same unit against different targets. This capability will allow the operator to replicate the basic message five times and vary the Mission Assignment Discrete (MAD) value for each and perhaps a select other few fields.

O3. Provide offline storage and retrieval for up to 256 pre-scripted messages per file and load one or more files at a time. (Threshold Capability Includes 3 Requirements)

SHALL[464] The GSS DLMG SHALL[464] provide online access for up to 256 prescripted messages stored in a file.

SHALL[465] The DLMG SHALL[465] provide the capability to export selected prescripted messages to a named file

SHALL[466] SHALL[466] provide the capability to import one or more named files to any other scenario or in for immediate action in the on-line run mode.

O4. Set Playback filters for scenarios or recorded files to eliminate unwanted data during play. (Threshold Capability Includes 3 Requirements)

SHALL[566] The GSS SHALL[566] provide Scenario filters to limit data generated by the running scenario.

SHALL[567] The GSS SHALL[567] provide Playback filters to limit information conveyed during recording playback.

Commented [EM99]: What filters to what data?

Pass/reject? Of what?

Commented [MCW100R99]: The filters reduce the objects/messages being created during a running scenario.

SHALL[568] The GSS SHALL[568] provide two forms of filters, pass (accept) or reject (ignore).

O5. Scripting using point and click (Threshold Capability Includes 4 Requirements)

SHALL[448] The GSS DLMG SHALL[448] allow the operator to construct any defined Link 16 message through this scripting function with a point and click style interface.

SHALL[449] The GSS DLMG SHALL[449] allow the operator to construct any defined Link 11 (TADIL A/B) message through this scripting function with a point and click style interface.

SHALL[450] The GSS DLMG SHALL[450] allow the operator to construct any defined Link 1 message through this scripting function with a point and click style interface.

SHALL[451] The GSS SHALL[451] allow full duplex pseudo-track on both red and blue designated forces.

O6. Object Emulation (Threshold Capability Includes 3 Requirements)

SHALL[471] The GSS SHALL[471] provide a capability to create the following tactical objects: JTIDS Units (JU), tracks, points, targets, pointers, lines, and areas using platform/object templates.

SHALL[474] The GSS SHALL[474] allow objects to be created very specifically, e.g., F-15, or generically, e.g., ground C2 sensor.

SHALL[761] The GSS SHALL[761] present tactical objects on the TWS or RU that are emulations or representations of real-world tactical objects.

O7. Smooth kinematics (Threshold Capability Includes 2 Requirements)

SHALL[477] The GSS SHALL[477] [provides object performance parameter for] Gradual (smooth turns) for heading changes

SHALL[1016] The GSS SHALL[1016] [provides object performance parameter for] Gradual (smooth turns) for all defined orbits

O8. Messages at waypoints (Threshold Capability Includes 4 Requirements)

SHALL[472] As a product of object creation, the GSS SHALL[472] generate required messages characteristic of those objects (e.g., PPLIs for JUs, J3.2 for Air Tracks) and optional messages that the object may or may not generate (e.g., a JU sensor like AWACS would generate J3.2 air tracks as a optional message).

SHALL[489] The GSS SHALL[489] provide the capability to script a travel plan (e.g., flight plans or routes) with appropriate "change" points.

SHALL[770] At each created waypoint for a scenario object, the operator SHALL[770] be allowed to script up to 10 Data Link messages and populate the message contents as described in Section 3.2.2.7.

SHALL[771] Each scripted message SHALL[771] be configured by the operator to be prepared and sent either in advance or following the waypoint time by 12 (0-60,1) seconds.

O9. Inject SIM over LIVE (Threshold Capability Includes 1 Requirement)

Commented [EM101]: Link 11, 1 comments (required).

And… if we have these why not 22, VMF, ATDL-1?

Commented [MCW102R101]: Customer doesn’t have VMF /ATDL-1 if memory serves and are they cleared for L22?

Commented [EM103]: How is this different than 1016?

And wording is odd

Commented [MCW104R103]: One is head changes and one is orbit changes.

Commented [EM105]: Leaves a lot open to imagination.

What are the required msg characteristics?

Commented [MCW106R105]: Defined in MIL-STD 6016

SHALL[501] The GSS SHALL[501] allow the capability to script a travel plan off-line and run the script during on-line operations.

O10. Scenario Generator and Scenario Preparation (Threshold Capability Includes 7 Requirements)

SHALL[757] The GSS SHALL[757] provide an off-line scenario generator that can produce a complete time-ordered mission containing tactical objects and associated messages.

SHALL[758] Scenario start time SHALL[758] be configurable to start at time 00:00:00 or any user specified time.

SHALL[759] In on-line run mode, the primary GSS mission time SHALL[759] be configurable to use scenario time.

SHALL[760] (Note: A choice exists for the following requirements: SHALL[759]; SHALL[760]) the scenario SHALL[760] be configurable to align to the existing GSS primary mission time, e.g., JTOD or GPS.

SHALL[764] Tactical scenarios involving emulated objects created by the operator SHALL[764] be created off-line in scenario preparation mode or on-line during normal mission ops run mode.

SHALL[765] The scenarios SHALL[765] be based on time ordered events similar to the course of a sortie

SHALL[766] preplanned mission and SHALL[766] be changeable on-line by the operator on an object-by-object basis with appropriate changes to message contents generated or transactions performed.

SHALL[767] The scenario generated SHALL[767] be reviewable using time advance techniques such as skip to time, fast forward, pause, reverse n seconds, and replay.

O11. Create messages as a bi-product of object creation (Threshold Capability Includes 3 Requirements)

SHALL[620] The GSS SHALL[620] construct and decode all messages as specified in the standard according to the defined TADIL-J word structures and encoding in accordance with the Data Field Identifiers (DFI), Data Unit Identifiers (DUI) and Data Items (DI).

SHALL[762] When creating tactical objects for display, the data link messages SHALL[762] be created as a bi-product of the object creation.

SHALL[763] The GSS SHALL[763] allow messages with default and changeable fields to be associated with objects created.

O12. Object extrapolation (Threshold Capability Includes 1 Requirement)

SHALL[769] The GSS SHALL[769] provide the operator the capability to edit trajectory segments and waypoint events for any object without having to reconstruct the full event profile for the object.

OBJECTIVE Capabilities for Ground Support System (Message Generator - Scenario Generator - Object Emulator) (Total Objective Capabilities: 2 | Total Objective Requirements: 2)

O13. Provide extrapolation for scripted messages with velocity and other position data (Objective Capability Includes 1 Requirement)

Commented [EM107]: 463,…