912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
1 Introduction Information Only TPS-1
1.1 Scope Information Only TPS-5
1.1.0-1 This Performance Specification (PS) establishes the Information Only TPS-5043
functionality, performance, verification and acceptance
requirements for the Canadian Forces (CF) Integrated Soldier
System Suite (ISS-S) and the Canadian Forces (CF) System
Executive Planning Suite (SEP-Suite).
1.2 System Overview Information Only TPS-7
1.2.1 ISS-S Information Only TPS-5070
1.2.1.0-1 The ISS-S is the soldier-worn suite being purchased by the Information Only TPS-5363
ISSP.
1.2.1.0-2 All requirements that apply to the ISS-S have their "Applicable Information Only TPS-5368
Systems" attribute set to "ISS-S".
1.2.1.0-3 The following capabilities are to be part of the ISS-S: Information Only TPS-5071
• Communications Suite (Radio and Antenna);
• Audio Display;
• Wired Push-to-Talk (PTT) Switch;
• Bearing Indicator and GPS;
• SAASM GPS capability;
• Battle Management Software and Computer;
• External Data Storage;
• Tactical User Interface;
• System Management Software;
• Security Features;
• Power and Cabling; and
• Modular Load Carriage System.
1.2.1.0-4 Enhanced capabilities are requested to be part of the ISS-S: Information Only TPS-5362
• Growth Potential Enablers ;
• Wireless Push-To-Talk (PTT) Switch;
• Digital Imaging Capabilities; and
• Various Capability and Performance Enhancements.
1.2.2 SEP-Suite Information Only TPS-5074
1.2.2.0-1 The SEP-Suite is an items purchased by the ISSP that is not Information Only TPS-5075
part of the ISS-S but is required for the ISS-S to operate.
1.2.2.0-2 All requirements that apply to the SEP-Suite have their Information Only TPS-5369
"Applicable Systems" attribute set to "SEP-Suite".
1.2.2.0-3 The SEP-Suite includes the following capabilities: Information Only TPS-5364
• System Management Software; and
• Security Features.
1.2.3 Fitted For Information Only TPS-5076
1.2.3.0-1 Fitted For refers to Government Furbished Equipment (GFE). Information Only TPS-5077
This equipment is supplied to the contractor by DND and is to
interoperate with the ISS-S to enhance the system's capability.
Fitted For equipment includes:
• LCSS Radios; and
• CORAL-CR-C HHTI
1.2.3.0-2 Depending on how the contractor provides the SAASM GPS Information Only TPS-5365
capability, the ISS-S could interoperate with the in-service
DAGR.
2 Requirements Information Only TPS-3
2.1 System Level Requirements Information Only TPS-73
2.1.1 General Information Only TPS-2369
2.1.1.1 Languages Information Only TPS-4784
2.1.1.1.0-1 The ISS-S must fully support both official languages, French Mandatory ISS-S Description of Demo No TPS-4785
and English. Compliance
2.1.1.1.0-2 The SEP-Suite must fully support both official languages, Mandatory SEP-Suite Description of Demo No TPS-4977
French and English. Compliance
2.1.1.2 General Characteristics Information Only TPS-4786
2.1.1.2.0-1 The ISS-S audible noise emissions should be as low as Rated ISS-S MIL-STD-1474D Description of Test No TPS-4787
possible. Compliance
2.1.1.2.0-2 The ISS-S must have a way to prevent all devices part of the Mandatory ISS-S Description of Demo No TPS-2524
ISS-S from emitting visible light when stealth operations are Compliance
required.
2.1.1.2.0-3 Any and all sound generated by the ISS-S (excluding BMS Mandatory ISS-S Description of Contractor's Choice No TPS-5123
Software running on the CF-31 laptop) must be exclusively Compliance
presented to the user via the ISS-S Audio Display.
2.1.1.2.0-4 The exterior surfaces of all ISS-S electronic components and Mandatory ISS-S D-80-001-500/SF-001: CADPAT (TW) Description of Inspection No TPS-2884
cables must be of one or more of the following colours or Compliance
colour patterns:
• Non-reflecting flat green finish;
• Non-reflective flat black finish;
• Non-reflecting flat brown finish; or
• CADPATTM TW.
2.1.1.2.0-5 If any hardware is provided as part of the SEP-Suite, the Mandatory SEP-Suite D-80-001-500/SF-001: CADPAT (TW) Description of Inspection No TPS-4981
exterior surfaces of that hardware must be of one or more of Compliance
the following colours or colour patterns:
• Non-reflecting flat green finish;
• Non-reflective flat black finish;
• Non-reflecting flat brown finish; or
TM
• CADPAT TW.
2.1.1.2.0-6 The ISS-S must be fitted to the soldier without requiring to be Mandatory ISS-S GFE: CG634 CF Helmet, all 3 sizes + sizing Description of Contractor's Choice No TPS-5106
fixed to any head borne equipment and not affect the correct templates. Compliance
securing of the helmet.
Page 1 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.1.2.0-7 The ISS-S must not include storage devices with moving parts, Mandatory ISS-S Description of Analysis No TPS-5338
including but not limited to magnetic disks and optical drives. Compliance
2.1.1.2.0-8 The SEP-Suite must be used to configure the ISS-S nodes. Mandatory SEP-Suite Description of Contractor's Choice No TPS-5376
Compliance
2.1.1.2.0-9 Once the ISS-S nodes are configured, the SEP-Suite must not Mandatory ISS-S Description of Contractor's Choice No TPS-5378
be required to operate the ISS-S. Compliance
2.1.1.2.0-10 Once the ISS-S nodes are configured, the ISS-S nodes must Mandatory ISS-S Description of Contractor's Choice No TPS-5377
meet all TPS requirements without requiring any other device Compliance
or infrastructure.
2.1.1.3 Nameplates and Product Information Only TPS-2914
Marking
2.1.1.3.0-1 The ISS-S must include nameplates and product markings. Mandatory ISS-S MIL-HDBK-454 Description of Inspection No TPS-4983
D-02-002-001/SG-001 Compliance
DAOD 3010.0
DAOD 3010.1
2.1.1.3.0-2 The ISS-S nameplates and product markings must conform to Mandatory ISS-S MIL-HDBK-454 Description of Inspection No TPS-2915
the specifications of MIL-STD/HDBK-454, D-02-002-001/SG-001 Compliance
Requirement/Guideline 67 and D-02-002-001/SG-001. The DAOD 3010.0
NATO Stock Number (NSN), the Part Number (PN) and the DAOD 3010.1
DAODs 3010-0 and 3010.1 barcode must be inscribed on the
equipment to ensure proper identification. Details of which
version of MIL-STD/HDBK-454 and other details are to be
determined.
2.1.1.3.0-3 If any hardware is provided as part of the SEP-Suite, the Mandatory SEP-Suite MIL-HDBK-454 Description of Inspection No TPS-4984
hardware that is included as part of the SEP-Suite must D-02-002-001/SG-001 Compliance
include nameplates and product markings. DAOD 3010.0
DAOD 3010.1
2.1.1.3.0-4 If any hardware is provided as part of the SEP-Suite, the SEP- Mandatory SEP-Suite MIL-HDBK-454 Description of Inspection No TPS-4985
Suite nameplates and product markings must conform to the D-02-002-001/SG-001 Compliance
specifications of MIL-STD/HDBK-454, Requirement/Guideline DAOD 3010.0
67 and D-02-002-001/SG-001. The NATO Stock Number DAOD 3010.1
(NSN), the Part Number (PN) and the DAODs 3010-0 and
3010.1 barcode must be inscribed on the equipment to ensure
proper identification. Details of which version of MIL-
STD/HDBK-454 and other details are to be determined.
2.1.1.4 Weight and Volume Information Only TPS-3917
2.1.1.4.0-1 The ISS-S, including batteries to support a 24 hour mission as Rated ISS-S Test of Function Test No TPS-3919
per the ISS-S Mission Profile, should be as light as possible.
2.1.1.4.0-2 The ISS-S, including batteries to support a 24 hour mission as Rated ISS-S Test of Function Test No TPS-4776
per the ISS-S Mission Profile, should be as small as possible.
2.1.1.5 Human Systems Integration Information Only TPS-5332
2.1.1.5.0-1 The ISS-S of equipment as part of Fighting Order must Mandatory ISS-S - Tailored manequin Demonstration of Contractor's Choice No TPS-3436
accommodate ninety five (95) percent male/female of the - Reference Y Function
Land Force population as defined at Reference Y. - Baseline Combat Clothing and Equipment
(Annex B, sub section 2.5.2 - 2.5.4, To ISSP SOR
Cycles 1 and 2 Version: V1.1 08 Jul 10)
2.1.1.5.0-2 Control device(s) should be operable with one hand. Rated ISS-S Demonstration of Demo No TPS-3098
Function
2.1.2 Environment, Health & Information Only TPS-4045
Safety (EHS)
2.1.2.0-1 The Contractor must utilize a system safety process such as Mandatory ISS-S GFI: MIL-STD-882D Description of Analysis No TPS-5154
MIL-STD-882 or equivalent to identify potential hardware and Compliance
software hazards, assess mishap risk in terms of severity and
probability of occurrence, and provide mitigation methods.
2.1.2.0-2 The ISS-S must not present any environmental, health or Mandatory ISS-S GFI: MIL-STD-882D Description of Analysis No TPS-4048
system safety hazards of a Catastrophic or Critical mishap Compliance
severity, as determined through a systematic hazard analysis
approach such as MIL-STD-882D or equivalent.
2.1.2.0-3 The ISS-S must not be a toxicological, radiation, or ionizing Mandatory ISS-S GFI: ACGIH Description of Analysis No TPS-4049
radiation hazard to the operator or maintenance personnel and Compliance
not exceed maximum allowable limits for chemicals, vapours,
gases, particulate, or radiation as specified in the ACGIH
Threshold Limit Values and Biological Exposure Indices, or
equivalent.
2.1.2.0-4 The ISS-S must remain safe for the operator and surrounding Mandatory ISS-S Description of Analysis No TPS-4050
environment even when so damaged that it allows the ingress Compliance
of water or egress of internal substances.
2.1.2.0-5 The maximum allowable ISS-S surface contact temperatures Mandatory ISS-S GFI: MIL-STD-1472F Description of Test No TPS-4051
must be in accordance with MIL-STD-1472F section 5.13.4.6 Compliance
Thermal contact hazards for prolonged contact.
2.1.2.0-6 The ISS-S must meet the UL94 V-0 fire retardant rating, or Mandatory ISS-S Certificate of Test No TPS-4052
equivalent, for all plastic components and parts. Compliance or
Description of
Compliance
2.1.2.0-7 When rechargeable sealed batteries are used, they must Mandatory ISS-S GFI: MIL-PRF-32052(CR) Certificate of Test No TPS-4054
comply with the Cell Safety (para 3.5.3) and Battery Safety Compliance or
(para 3.16) requirements of MIL-PRF-32052(CR), or Description of
equivalent. Compliance
Page 2 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.2.0-8 The ISS-S must not discharge any connected laser due to any Mandatory ISS-S GFE: CORAL-CR-C Description of Analysis No TPS-4055
fault or failure. Compliance
2.1.2.0-9 Materials and parts containing mercury must not be used Mandatory ISS-S Description of Analysis No TPS-4201
unless use of mercury is specifically required and approved by Compliance
the procuring authority
2.1.2.0-10 Cadmium plating and devices using cadmium must not be Mandatory ISS-S Description of Analysis No TPS-4202
used unless specifically approved by the procuring authority. Compliance
2.1.2.0-11 Polychlorinated Biphenyls (PCBs), halocarbons and asbestos Mandatory ISS-S Description of Analysis No TPS-4057
must not be used by the contractor for the design, operation Compliance
and maintenance of the equipment.
2.1.3 Human Factors Information Only TPS-3073
2.1.3.0-1 It is recommended that the ISS-S complies to design criteria Information Only ISS-S FAA - Human Factors Design Standards (2003) No TPS-5210
standards as prescribed in FAA - Human Factors Design
Standards (2003) when applicable.
2.1.3.0-2 Any touch screen controls for displays used on the ISS-S Rated ISS-S MIL-STD-1472F Demonstration of Contractor's Choice No TPS-3110
should comply with the design criteria standards as prescribed Function
in MIL-STD-1472F, section 5.4.6.3 Positive indication.
2.1.3.0-3 The feedback provided by the ISS-S software should comply Rated ISS-S MIL-STD-1472F Demonstration of Contractor's Choice No TPS-3239
with the design criteria standards as prescribed in MIL-STD Function
1472F, section 5.14.5.2 Standby.
2.1.3.0-4 The feedback provided by the ISS-S software should comply Rated ISS-S MIL-STD-1472F Demonstration of Contractor's Choice No TPS-3240
with the design criteria standards as prescribed in MIL-STD Function
1472F, section 5.14.5.3 Process outcome.
2.1.3.0-5 The error management/data protection provided by the ISS-S Rated ISS-S MIL-STD-1472F Demonstration of Contractor's Choice No TPS-3261
software should comply with the design criteria standards as Function
prescribed in MIL-STD 1472F, section 5.14.8.1 Error
correction.
2.1.3.0-6 It is recommended that the ISS-S follows the HCI guidelines Information Only ISS-S MIL-HDBK-761A No TPS-5212
detailed in reference MIL-HDBK-761A when applicable.
2.1.4 Environmental Information Only TPS-78
2.1.4.1 Climatic / Natural Information Only TPS-291
Environments
2.1.4.1.0-1 The test methods and standards used throughout this section Information Only ISS-S GFI: MIL-STD-810G TPS-3961
refer to MIL-STD-810G, however alternate test standards will
be accepted provided equivalence is clearly demonstrated.
Equivalency will be determined by the Crown Technical
Authority.
2.1.4.1.1 Operation - High Information Only TPS-313
Temperature
2.1.4.1.1.0-1 The ISS-S must operate within normal performance limits at Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-317
temperatures up to 49°C tested according to MIL-STD-810G, Compliance or
Method 501.5, Procedure II (using cycling as for the A1 Description of
Climatic category) or equivalent. Compliance
2.1.4.1.1.0-2 If exposed to temperatures above 49°C and up to 60°C in an Rated ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-5155
operating (power-on) state, the ISS-S should continue to Compliance or
operate within normal performance limits or exhibit only a Description of
temporary loss or degradation of function that is self-recovered Compliance
upon returning to its rated temperature range. Tested
according to MIL-STD-810G, Method 501.5, Procedure II or
equivalent.
2.1.4.1.2 Storage - High Temperature Information Only TPS-315
2.1.4.1.2.0-1 The ISS-S must operate within normal performance limits Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-324
following storage at temperatures up to 71°C tested according Compliance or
to MIL-STD-810G, Method 501.5, Procedure I (using cycling Description of
as for the A1 Climatic category) or equivalent. Compliance
2.1.4.1.3 Operation - Low Information Only TPS-314
Temperature
2.1.4.1.3.0-1 The ISS-S must operate within normal performance limits at Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-323
temperatures down to -30°C tested according to MIL-STD- Compliance or
810G, Method 502.5, Procedure II or equivalent. Description of
Compliance
2.1.4.1.3.0-2 If exposed to temperatures below -30°C and down to -46°C in Rated ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-2189
an operating (power-on) state, the ISS-S should continue to Compliance or
operate within normal performance limits or exhibit only a Description of
temporary loss or degradation of function that is self-recovered Compliance
upon returning to its rated temperature range. Tested
according to MIL-STD-810G, Method 502.5, Procedure II or
equivalent.
2.1.4.1.4 Storage - Low Temperature Information Only TPS-316
2.1.4.1.4.0-1 The ISS-S must operate within normal performance limits Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-325
following storage at temperatures down to -30°C tested Compliance or
according to MIL-STD-810G, Method 502.5, Procedure I or Description of
equivalent. Compliance
2.1.4.1.4.0-2 The ISS-S should operate within normal performance limits Rated ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-2192
following storage at temperatures down to -46°C. Tested Compliance or
according to MIL-STD-810G, Method 502.5, Procedure I or Description of
equivalent. Compliance
2.1.4.1.5 Humidity Information Only TPS-299
2.1.4.1.5.0-1 The ISS-S must operate within normal performance limits at a Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-332
relative humidity of 95% and ambient temperature of 30°C Compliance or
tested according to MIL-STD-810G, Method 507.5 Procedure I Description of
or equivalent. Compliance
Page 3 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.4.1.6 Thermal Shock Information Only TPS-999
2.1.4.1.6.0-1 The ISS-S must operate within normal performance limits Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-1020
during sudden changes in temperature (thermal shock) due to Compliance or
transitioning through temperature changes from 24°C to 49°C Description of
and 21°C to -32°C tested according to MIL-STD-810G, Compliance
Method 503.5, Procedure I D (Multi-cycle shock) or equivalent.
2.1.4.1.7 Solar Radiation Information Only TPS-297
2.1.4.1.7.0-1 The ISS-S must operate within normal performance limits Mandatory ISS-S GFI: MIL-STD-810G Certificate of Contractor's Choice No TPS-329
during extended sunlight exposure with an intensity of 1120 Compliance or
W/m² and a temperature of 49°C tested according to MIL-STD- Description of
810G, Method 505.5 Procedure II or equivalent, or materials Compliance
analysis.
2.1.4.1.8 Blowing Rain Information Only TPS-298
2.1.4.1.8.0-1 The ISS-S must operate within normal performance limits Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-331
during rainfall exposure of a minimum 1.8 mm/min and a wind Compliance or
velocity of a minimum 18 m/s tested according to MIL-STD- Description of
810G, Method 506.5, Procedure I or equivalent. Compliance
2.1.4.1.9 Sand and Dust Information Only TPS-302
2.1.4.1.9.0-1 The ISS-S must operate within normal performance limits in a Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-2201
sand and dust environment as follows: Compliance or
Dust particles smaller than 150 µm at a wind speed of 8.9 Description of
m/s, and Compliance
Sand particles between 150 µm to 850 µm in size at wind
speeds up to 29 m/s.
Test according to MIL-STD-810G, Method 510.5 Procedure I
for Dust and Procedure II for Sand or equivalent, both at an
ambient temperature of 49°C.
2.1.4.1.10 Salt Fog Information Only TPS-301
2.1.4.1.10.0-1 The ISS-S must operate within normal performance limits Mandatory ISS-S GFI: MIL-STD-810G Certificate of Contractor's Choice No TPS-1010
under or following exposure to salt fog conditions tested Compliance or
according to MIL-STD-810G, Method 509.5 using four Description of
alternating 24-hour periods of salt fog exposure and drying Compliance
conditions, or equivalent, or materials analysis.
2.1.4.1.11 Fungus Information Only TPS-300
2.1.4.1.11.0-1 The ISS-S must not contain materials that support fungus Mandatory ISS-S GFI: MIL-STD-810G Certificate of Contractor's Choice No TPS-333
growth tested according to MIL-STD-810G, Method 508.6 or Compliance or
equivalent, or materials analysis. Description of
Compliance
2.1.4.2 Induced Environments Information Only TPS-2210
2.1.4.2.1 General Information Only TPS-5352
2.1.4.2.1.0-1 The test methods and standards used throughout this section Information Only ISS-S GFI: MIL-STD-810G TPS-3962
refer to MIL-STD-810G, however alternate test standards will
be accepted provided equivalence is clearly demonstrated.
Equivalency will be determined by the Crown Technical
Authority.
2.1.4.2.2 Shock Information Only TPS-305
2.1.4.2.2.0-1 The ISS-S must operate within normal performance limits Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-2218
following the shocks associated with dismounted soldier Compliance or
operations while in an operational mode tested according to Description of
MIL-STD-810G, Method 516.6 Procedure I or equivalent. Compliance
2.1.4.2.2.0-2 The ISS-S must operate within normal performance limits Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-2219
following a 1.22 m drop tested according to MIL-STD-810G, Compliance or
Method 516.6 Procedure IV or equivalent. Description of
Compliance
2.1.4.2.4 Transport Vibration Information Only TPS-2216
2.1.4.2.4.0-1 The ISS-S must operate within normal performance limits Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-2217
following exposure to the vibrations associated with transport GFI: Tracked Vehicle vibration exposure profile Compliance or
in Ground Vehicles while in a non-operating (power-off) state. Description of
Tested according to MIL-STD-810G, Method 514.6 Procedure Compliance
I using the Tracked Vehicle vibration exposure profile or
equivalent.
2.1.4.2.5 Immersion Information Only TPS-303
2.1.4.2.5.0-1 The ISS-S must operate within normal performance limits after Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-2205
immersion in fresh water, without preparation, for a period of Compliance or
30 minutes at a depth of 1 m tested according to MIL-STD- Description of
810G, Method 512.5 Procedure I (Immersion) or equivalent. Compliance
2.1.4.2.6 Reduced Pressure Information Only TPS-2206
2.1.4.2.6.0-1 The ISS-S must operate within normal performance limits at Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-2207
an atmospheric pressure of 57.2 kPa (corresponding to a Compliance or
standard altitude of 4,572m) tested according to MIL-STD- Description of
810G, Method 500.5 Procedure II (Operation) or equivalent. Compliance
2.1.4.2.6.0-2 The ISS-S must operate within normal performance limits Mandatory ISS-S GFI: MIL-STD-810G Certificate of Test No TPS-2208
following storage at an atmospheric pressure of 57.2 kPa Compliance or
(corresponding to a standard altitude of 4,572m) tested Description of
according to MIL-STD-810G, Method 500.5 Procedure I Compliance
(Storage) or equivalent.
2.1.4.2.7 Explosive Atmosphere Information Only TPS-2211
2.1.4.2.7.0-1 The ISS-S must not constitute a hazard in an explosive Mandatory ISS-S GFI: MIL-STD-810G Certificate of Contractor's Choice No TPS-2212
environment tested according to MIL-STD-810G, Method Compliance or
511.5 Procedure I or equivalent, or applicable analysis Description of
methods. Compliance
2.1.4.2.8 Contamination by Fluids Information Only TPS-2220
Page 4 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.4.2.8.0-1 The ISS-S must withstand, within normal performance limits, Mandatory ISS-S GFI: MIL-STD-810G Certificate of Contractor's Choice No TPS-2221
contamination by the following fluids: Compliance or
• Insect repellent with DEET; Description of
• Naphtha; Compliance
• Weapon cleaning solvents;
• Camouflage cream;
• Reactive Skin Decontaminant Lotion (RSDL);
• Salt water;
• Motor fuel (gasoline);
• Hydraulic fluids;
• Automotive and weapon grease;
• Molybdenum Disulphide grease;
• Icing inhibitor;
• Anti-freeze;
• Engine oil;
• Diesel fuel;
• Jet engine petroleum (JP-4);
• Sodium Hypochlorite (liquid bleach); and
• Dettol (COTS liquid antiseptic)
Tested according to MIL-STD-810G, Method 504.1 Procedure
II or equivalent, or applicable materials analysis.
2.1.4.3 Electromagnetic Information Only TPS-312
Environmental Effects (E3)
2.1.4.3.0-1 The ISS-S must demonstrate electromagnetic compatibility Mandatory ISS-S Certificate of Analysis - and - Test No TPS-666
with itself and its subsystems. Compliance or
Description of
Compliance
2.1.4.3.0-2 The ISS-S must demonstrate electromagnetic information Mandatory ISS-S Certificate of Analysis - and - Test No TPS-667
integrity to the level indicated. Compliance or
Description of
Compliance
2.1.4.3.0-3 The Electromagnetic Environmental Effects requirements Mandatory ISS-S GFI: MIL-STD-461F Description of Inspection No TPS-318
listed in this TPS are derived from MIL-STD-464A, MIL-STD- Compliance
461F, MIL-STD-1686C, and Health Canada Safety Code 6.
Vendors wishing to invoke compliance with other EMI/EMC
related specifications must obtain written approval from the
Crown before a compliance with the requirement can be
claimed.
2.1.4.3.0-4 The ISS-S must be compliant with system EMC requirements Mandatory ISS-S GFI: MIL-STD-464A Certificate of Analysis - and - Test No TPS-668
of MIL STD 464A. Compliance or
Description of
Compliance
2.1.4.3.1 EMI / EMC Information Only TPS-918
2.1.4.3.1.0-1 The ISS-S must meet all requirements from MIL-STD-461F for Mandatory ISS-S GFI: MIL-STD-461F Certificate of Test No TPS-344
CE102, Conducted Emission power leads, 10 kHz to 10 MHz. Compliance or
Description of
Compliance
2.1.4.3.1.0-2 The ISS-S radio must meet all requirements from MIL-STD- Mandatory ISS-S GFI: MIL-STD-461F Certificate of Test No TPS-345
461F for CE106, Conducted Emissions, antenna terminal 10 Compliance or
kHz to 40 GHz. Description of
Compliance
2.1.4.3.1.0-3 If equipment design characteristics preclude the use of Mandatory ISS-S GFI: MIL-STD-461F Certificate of Test No TPS-354
CE106, the ISS-S must meet all requirements from MIL-STD- Compliance or
461F for RE103, Radiated Emissions, antenna spurious and Description of
Harmonic outputs, 10 kHz to 40 GHz. Compliance
2.1.4.3.1.0-4 The ISS-S must meet all requirements from MIL-STD-461F for Mandatory ISS-S GFI: MIL-STD-461F Certificate of Test No TPS-346
CS101, Conducted Susceptibility, Power leads, 30 Hz to 150 Compliance or
kHz, figure CS101-1, Curve 2. Description of
Compliance
2.1.4.3.1.0-5 The ISS-S radio must meet all requirements from MIL-STD- Mandatory ISS-S GFI: MIL-STD-461F Certificate of Test No TPS-347
461F for CS103, Conducted Susceptibility, Antenna Port Compliance or
Intermodulation 15 kHz to 10 GHz. Description of
Compliance
2.1.4.3.1.0-6 The ISS-S must meet all requirements from MIL-STD-461F for Mandatory ISS-S GFI: MIL-STD-461F Certificate of Test No TPS-350
CS114, Conducted Susceptibility, Bulk Cable Injection, 10 kHz Compliance or
to 200 MHz for ground army applications. Description of
Compliance
2.1.4.3.1.0-7 The ISS-S must meet all requirements from MIL-STD-461F for Mandatory ISS-S GFI: MIL-STD-461F Certificate of Test No TPS-351
CS115, Conducted Susceptibility, Bulk Cable Injection, Compliance or
Impulse Excitation. Description of
Compliance
2.1.4.3.1.0-8 The ISS-S must meet all requirements from MIL-STD-461F for Mandatory ISS-S GFI: MIL-STD-461F Certificate of Test No TPS-352
CS116, Conducted Susceptibility, Damped Sinusoidal Compliance or
transients, cables and power leads, 10 kHz to 100 MHz, 10 A Description of
maximum. Compliance
2.1.4.3.1.0-9 The ISS-S must meet all requirements from MIL STD 461F for Mandatory ISS-S GFI: MIL-STD-461F Certificate of Test No TPS-353
RE102, Radiated Emissions, Electric Field, 10kHz to 18GHz, Compliance or
figure RE102-4, army curve. Description of
Compliance
2.1.4.3.1.0-10 The ISS-S must meet all requirements from MIL STD 461F for Mandatory ISS-S GFI: MIL-STD-461F Certificate of Test No TPS-356
RS103, Radiated Susceptibility, Electric Field, 2MHz to Compliance or
18GHz, limit of 50 V/m. Description of
Compliance
2.1.4.3.2 RADHAZ Information Only TPS-919
2.1.4.3.2.0-1 The ISS-S must meet the requirements of Health Canada Mandatory ISS-S GFI: CFTO C-55-040-001/TS-001 Certificate of Analysis - and - Test No TPS-920
Safety Code 6 and Canadian Forces Technical Order (CFTO) Compliance or
C-55-040-001/TS-001. Description of
Compliance
Page 5 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.4.3.2.0-2 Subject matter experts (SME) of the Crown will perform Crown ISS-S GFI: CFTO C-55-040-001/TS-001 TPS-922
RADHAZ Tests in accordance with the requirements of Health
Canada Safety Code 6 and CFTO C-55-040-001/TS-001.
2.1.4.3.2.0-3 For configurations that include provision for the support of Crown ISS-S Certificate of Analysis - and - Test No TPS-921
electrically initiated ordnance (EIO), special Hazard of Compliance or
Electromagnetic Radiation to Ordnance (HERO) requirements Description of
will be imposed. Compliance
2.1.4.3.3 Electrostatic Discharge Information Only TPS-925
2.1.4.3.3.0-1 All tests from MIL STD 1686C must be performed on a Mandatory ISS-S GFI: MIL-STD-1686C Certificate of Test No TPS-1036
minimum of eight points on each component of the ISS-S. Compliance or
Description of
Compliance
2.1.4.3.3.0-2 The ISS-S must meet all requirements from MIL STD 1686C, Mandatory ISS-S GFI: MIL-STD-1686C Certificate of Test No TPS-926
5.2.2.1, Direct Contact, Non-Operating Assembly, 2000V Compliance or
Body/Finger or Hand/Metal HBM test. Description of
Compliance
2.1.4.3.3.0-3 The ISS-S must meet all requirements from MIL STD 1686C, Mandatory ISS-S GFI: MIL-STD-1686C Certificate of Test No TPS-1031
5.2.2.2, Direct Contact, Operating Equipment, 4000V Compliance or
Hand/Metal HBM test. Description of
Compliance
2.1.4.3.4 Lightning Information Only TPS-311
2.1.4.3.4.0-1 The ISS-S must meet all requirements from MIL STD 461F, Mandatory ISS-S GFI: MIL-STD-461F Certificate of Analysis - and - Test No TPS-1030
RS105, Radiated Susceptibility, Transient Electromagnetic Compliance or
Field. Description of
Compliance
2.1.4.3.5 Grounding Information Only TPS-1032
2.1.4.3.5.0-1 The ISS-S should include, as part of its manufacturing Rated ISS-S Certificate of Demo No TPS-1033
process, a grounding and bonding test procedure to ensure Compliance or
proper bonding of conductive surfaces. Description of
Compliance
2.1.4.3.5.0-2 To maximise likelihood of compliance with Electromagnetic Rated ISS-S Certificate of Demo No TPS-1034
Environmental Effects requirements (TPS-312), the maximum Compliance or
impedance from component to component within the ISS-S Description of
should be 25 milli-ohms. Compliance
2.1.4.3.5.0-3 To maximise likelihood of compliance with Electromagnetic Rated ISS-S Certificate of Demo No TPS-1035
Environmental Effects requirements (TPS-312), the maximum Compliance or
impedance from component to cable within the ISS-S should Description of
be 2.5 milli-ohms. Compliance
2.1.5 Functional Security Information Only TPS-79
Requirements
2.1.5.0-1 Digital data consists in any of: Blue Force Tracking info, Information Only n/a TPS-927
reference documents and information, mission orders and
briefing materials, planning tools and materials, terrain
databases for an Area of Operations, photos, and information
about the local culture, hazards, and language, digital
information to enable the exchange of voice, imagery,
streaming video, traces, overlays, orders, pre formatted formal
text messages and informal free text messages and chat,
target list, electronic range card, application data, mission
information (routes, positions, messages), user's system
configurations and preferences, default system configurations,
OEM default settings, Communities of Interest (COIs) lists,
and digital voice.
2.1.5.1 Access Controls Information Only TPS-981
2.1.5.1.0-1 The ISS-S should provide an access control mechanism to Rated ISS-S NONE Description of Demo No TPS-1467
prevent unauthorised access. Compliance
2.1.5.1.0-2 The ISS-S access control should not require multiple logins. Rated ISS-S Description of Demo No TPS-5170
Compliance
2.1.5.1.0-3 Only authorized users should have access to digital data Rated ISS-S NONE Description of Demo No TPS-982
stored (either locally or in external ISS-S storage), transmitted, Compliance
received or processed by an ISS-S.
2.1.5.1.0-4 The ISS-S should provide role based access control, including Rated ISS-S NONE Description of Demo No TPS-983
System Administrator role and Basic User role. Compliance
2.1.5.1.0-5 The concept of a "User Profile" is defined as a logical grouping Information Only ISS-S TPS-5143
of user specific settings such as list of COI a given user may
access, rank and position of a user and other such items that
may pertain to an individual user and be used for individual
accountability.
2.1.5.1.0-6 The ISS-S access control should provide the ability to store Rated ISS-S NONE Description of Demo No TPS-5144
multiple "User Profile" while only allowing a single profile to be Compliance
active at any given time.
2.1.5.1.0-7 Activation of a specific ISS-S "User Profile" should be Rated ISS-S NONE Description of Demo No TPS-5171
performed using a single user identification/password Compliance
combination.
2.1.5.2 Identification and Information Only TPS-964
Authentication (I&A)
2.1.5.2.0-1 The ISS-S should provide an I&A capability to authenticate ISS- Rated ISS-S NONE Description of Demo No TPS-967
S System Administrators. Compliance
2.1.5.2.0-2 The ISS-S should provide an I&A capability to authenticate ISS- Rated ISS-S NONE Description of Demo No TPS-968
S Basic Users (as opposed to a System Administrators). Compliance
2.1.5.2.0-3 The ISS-S should provide I&A capability to authenticate a Rated ISS-S NONE Description of Demo No TPS-970
Wireless PTT that connects to it. Compliance
Page 6 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.5.2.0-4 The ISS-S I&A capability for Basic User and System Rated ISS-S NONE Description of Demo No TPS-973
Administrator authentication should implement a user Compliance
identification and password authentication technique (one
factor) to access the ISS-S, with the following characteristics:
• An authentication procedure is required to access the ISS-S
computer and data stored locally and externally; and
• An authentication procedure is not required to provide ISS-S
radio network voice and data services.
2.1.5.2.0-5 The ISS-S Basic User and System Administrator password Rated ISS-S NONE Description of Demo No TPS-978
based authentication capability should provide a settable Compliance
allowable number of consecutive unsuccessful entries.
2.1.5.2.0-6 The ISS-S Basic User and System Administrator password Rated ISS-S NONE Description of Demo No TPS-5145
based authentication capability should allow the number of Compliance
consecutive unsuccessful entries to be settable from a
minimum of 3 up to 15.
2.1.5.2.0-7 The ISS-S Basic User and System Administrator password Rated ISS-S NONE Description of Demo No TPS-980
based authentication capability should provide a settable "lock- Compliance
out time delay" once the set number of consecutive
unsuccessful entries is reached.
2.1.5.2.0-8 The ISS-S Basic User and System Administrator password Rated ISS-S NONE Description of Demo No TPS-5146
based authentication capability "lock-out time delay" should be Compliance
settable from 30 seconds to 10 minutes in increments of 30
seconds or less.
2.1.5.2.0-9 The ISS-S should provide an ISS-S Operating System settable Rated ISS-S NONE Description of Demo No TPS-4082
inactivity timer with the following characteristics: Compliance
• The ISS-S Operating System goes inactive after the inactivity
timer has elapsed;
• The ISS-S Operating System needs to be reactivated to
access its software functions; and
• The ISS-S voice and data capability is not affected in any
way by the ISS-S Operating System inactivity timer.
2.1.5.2.0-10 The ISS-S Operating System inactivity timer duration should Rated ISS-S NONE Description of Demo No TPS-4083
be settable by the ISS-S System Administrator and Basic Compliance
Users.
2.1.5.2.0-11 The ISS-S Operating System inactivity timer should be Rated ISS-S NONE Description of Demo No TPS-4084
settable in a range from 30 seconds to 10 hours in increments Compliance
of 30 seconds or less.
2.1.5.2.0-12 If the ISS-S provides an I&A capability defined in TPS-973, the Mandatory ISS-S Description of Demo No TPS-5147
ISS-S Basic User and System Administrator must be able to Compliance
disable the ISS-S Operating System inactivity timer.
2.1.5.2.0-13 The ISS-S Basic User and System Administrator minimum Rated ISS-S NONE Description of Demo No TPS-975
password size should be settable. Compliance
2.1.5.2.0-14 The ISS-S password size should be settable from a minimum Rated ISS-S NONE Description of Demo No TPS-976
of 4 characters and be capable of accepting passwords of up Compliance
to 16 characters or more.
2.1.5.3 Data At Rest (DAR) Information Only TPS-929
2.1.5.3.1 General Information Only TPS-5353
2.1.5.3.1.0-1 Stored digital data should be secured when stored in main Rated ISS-S Description of Demo No TPS-930
data storage as part of the ISS-S and when carried on external Compliance
data storage devices.
2.1.5.3.1.0-2 Stored digital data should be secured using both cryptographic Rated ISS-S Description of Demo No TPS-931
encryption and integrity protection. Compliance
2.1.5.3.1.0-3 The encryption mechanism should provide a minimum of 128 Rated ISS-S GFI: NIST SP 800-57 Description of Analysis - and - Demo No TPS-933
bits of security (see NIST SP 800-57 part 1, Table 2). Compliance
2.1.5.3.1.0-4 The encryption mechanism used to secure stored data should Rated ISS-S GFI: FIPS 197 Certificate of Test No TPS-934
be AES (FIPS 197). Compliance or
Description of
Compliance
2.1.5.3.1.0-5 The encryption mechanism should use one of the following Rated ISS-S GFI: NIST SP 800-38A, NIST SP 800-38C, NIST Certificate of Test No TPS-935
block cipher modes of operations: CBC (NIST SP-800-38A), SP 800-38D Compliance or
CTR (NIST SP-800-38A), CCM (NIST SP-800-38C) or GCM Description of
(NIST SP-800-38D). Compliance
2.1.5.3.1.0-6 The integrity mechanism used to protect stored data should Rated ISS-S Description of Test No TPS-936
provide an equivalent strength factor of at least 80 bits. Compliance
2.1.5.3.1.0-7 The integrity of stored data should be provided using one of Rated ISS-S GFI: NIST SP 800-38B, NIST SP 800-38C, NIST Certificate of Test No TPS-937
the following techniques: SP 800-38D, FIPS 197, FIPS 198-1, FIPS 180-3 Compliance or
a) AES 128 bits encryption (FIPS 197) in CMAC (NIST SP- Description of
800-38B), CCM (NIST SP-800-38C) or GCM (NIST SP-800- Compliance
38D) mode;
b) AES 256 bits encryption (FIPS 197) in CMAC (NIST SP-
800-38B), CCM (NIST SP-800-38C) or GCM (NIST SP-800-
38D) mode; or
c) Keyed-Hash Message Authentication Code (HMAC) as per
FIPS 198-1 using one of the NIST approved hash functions
(FIPS 180-3).
2.1.5.3.1.0-8 The encryption and integrity mechanisms implemented for Rated ISS-S GFI: FIPS 140-2 Certificate of Test No TPS-938
securing (confidentiality and integrity) stored data should be Compliance or
validated to a minimum of FIPS 140-2 Level 2 or equivalent. Description of
Compliance
2.1.5.3.2 Zeroizing Information Only TPS-129
2.1.5.3.2.0-1 The ISS-S must provide a means to zeroize all digital data Mandatory ISS-S NONE Description of Test Yes TPS-954
stored on a system. Compliance
Page 7 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.5.3.2.0-2 The means to zeroize the stored digital data may be provided Information Only ISS-S TPS-955
by securely deleting the storage key used for securing
encrypted and integrity protected digital data.
2.1.5.3.2.0-3 The digital data zeroization capability must require the Basic Mandatory ISS-S NONE Description of Demo Yes TPS-956
User to provide confirmation of the deletion request. Compliance
2.1.5.3.2.0-4 Upon zeroization of the digital data by the user, the ISS-S Rated ISS-S NONE Description of Demo Yes TPS-957
should send, on the Blue PA COI, a message indicating that Compliance
the user has performed a zeroize function as well as his last
position.
2.1.5.3.3 Over The Air Zeroizing Information Only TPS-958
(OTAZ)
2.1.5.3.3.0-1 The ISS-S should provide a secure means to remotely zeroize Rated ISS-S NONE Description of Test Yes TPS-959
the stored digital data on a remote ISS-S. Compliance
2.1.5.3.3.0-2 The ISS-S remote secure digital data zeroization capability Rated ISS-S NONE Description of Test Yes TPS-960
should require a minimum of 2 users to be effected. Compliance
2.1.5.3.3.0-3 The ISS-S remote secure digital data zeroization capability Rated ISS-S NONE Description of Demo Yes TPS-961
should be available to all Users. Compliance
2.1.5.3.3.0-4 The ISS-S remote secure digital data zeroization capability Rated ISS-S NONE Description of Demo Yes TPS-962
should require the Users performing it to provide confirmation Compliance
of the deletion request.
2.1.5.4 EMCON Information Only TPS-988
2.1.5.4.1 Normal and Electronic Information Only TPS-4989
Silence
2.1.5.4.1.0-1 The ISS-S must be capable of supporting the following Mandatory ISS-S GFI: CFTO B-GL-334-001/FP-001 Description of Demo No TPS-1481
emanation control (EMCON) conditions as defined by CFTO B- Compliance
GL-334-001/FP-001, Standing Operating Procedures for Land
Operations:
a. EMCON 1-electronic silence;
c. EMCON 4-no restrictions.
2.1.5.4.1.0-2 In support of EMCON 1 conditions, all powered devices that Mandatory ISS-S Description of Demo No TPS-4263
are part of the ISS-S must be capable of being powered-off. Compliance
2.1.5.4.2 Radio Silence Information Only TPS-4990
2.1.5.4.2.0-1 The ISS-S should be capable of supporting the following Rated ISS-S GFI: CFTO B-GL-334-001/FP-001, MIL-STD- Certificate of Test No TPS-4991
emanation control (EMCON) conditions as defined by CFTO B- 461F, MIL-STD-464A Compliance or
GL-334-001/FP-001, Standing Operating Procedures for Land Description of
Operations: Compliance
b. EMCON 2-radio silence;
2.1.5.4.2.0-2 In support of EMCON 2 conditions, the ISS-S should be Rated ISS-S GFI: CFTO B-GL-334-001/FP-001 Description of Demo No TPS-2677
capable of shutting down all radio transmissions including Compliance
Mobile Ad hoc Network (MANET) protocol transmissions and
any other wireless transmissions.
2.1.5.4.2.0-3 While EMCON 2 Conditions are imposed on the ISS-S, the Rated ISS-S Description of Demo No TPS-2678
following ISS-S functionality should remain active and Compliance
accessible:
a. Position generation and display functions (but not position
reporting functions);
b. Navigation capability; and
c. Non-networked Battle Management System functions; and
d. Non-networked System Management functions; and
e. Target Acquisition capabilities the CORAL-CR-C.
2.1.5.5 Data In Transit (DIT) Information Only TPS-939
2.1.5.5.0-1 When digital data is transmitted from one ISS-S to another it Mandatory ISS-S Description of Test No TPS-940
must be secured. Compliance
2.1.5.5.0-2 Transmitted data must be secured using cryptographic Mandatory ISS-S Description of Test No TPS-941
encryption and provide data integrity measures. Compliance
2.1.5.5.0-3 The encryption mechanism must provide a minimum of 128 Mandatory ISS-S GFI: NIST SP 800-57 Description of Test No TPS-944
bits of security (see NIST SP 800-57 part 1, Table 2). Compliance
2.1.5.5.0-4 The encryption mechanism used to secure transmitted data Mandatory ISS-S GFI: FIPS 197 Certificate of Test No TPS-945
must be AES (FIPS 197). Compliance or
Description of
Compliance
2.1.5.5.0-5 The encryption mechanism must use one of the following block Mandatory ISS-S GFI: NIST SP 800-38A, NIST SP 800-38C, NIST Certificate of Test No TPS-946
cipher modes of operations: OFB (NIST SP-800-38A), CFB SP 800-38D Compliance or
(NIST SP-800-38A), CTR (NIST SP-800-38A), CCM (NIST SP- Description of
800-38C) or GCM (NIST SP-800-38D). Compliance
2.1.5.5.0-6 The integrity mechanism used to protect transmitted data must Mandatory ISS-S Description of Test No TPS-947
provide an equivalent strength factor of at least 16 bits. Compliance
2.1.5.5.0-7 The integrity of transmitted data should be provided using one Rated ISS-S GFI: NIST SP 800-38B, NIST SP 800-38C, NIST Certificate of Test No TPS-948
of the following techniques: SP 800-38D, FIPS 197, FIPS 198-1, FIPS 180-3 Compliance or
a) AES 128 bits encryption (FIPS 197) in CMAC (NIST SP- Description of
800-38B), CCM (NIST SP-800-38C) or GCM (NIST SP-800- Compliance
38D) mode;
b) AES 256 bits encryption (FIPS 197) in CMAC (NIST SP-
800-38B), CCM (NIST SP-800-38C) or GCM (NIST SP-800-
38D) mode; or
c) Keyed-Hash Message Authentication Code (HMAC) as per
FIPS 198-1 using one of the NIST approved hash functions
(FIPS 180-3).
2.1.5.5.0-8 The encryption and integrity mechanisms implemented for Rated ISS-S GFI: FIPS 140-2 Certificate of Test No TPS-949
securing data in transit should be validated to a minimum of Compliance or
FIPS 140-2 Level 2 or equivalent. Description of
Compliance
2.1.5.6 TRANSEC Information Only TPS-4087
Page 8 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.5.6.0-1 As per CNSSI 4009, TRANSEC is defined as: "Component of Information Only ISS-S TPS-4089
COMSEC resulting from the application of measures designed
to protect transmissions from interception and exploitation by
means other than cryptanalysis."
2.1.5.6.0-2 The ISS-S should provide TRANSEC functionality using one of Rated ISS-S Description of Contractor's Choice No TPS-4088
the following techniques: Compliance
• Spread Spectrum;
• Frequency Hopping; or
• Spread Spectrum and Frequency Hopping
2.1.5.6.0-3 The TRANSEC functionality described in TPS-4088 should be Rated ISS-S Description of Contractor's Choice No TPS-5335
available on all the ISS-S provided frequency bands. Compliance
2.1.5.7 Key Management Information Only TPS-987
2.1.5.7.0-1 Key management is the ensemble of processes, techniques, Information Only TPS-5148
procedures, hardware and software used to manage the life
cycle of cryptographic keying material. Key management
includes "Key Ordering", "Key Generation", "Key Production",
"Key Storage/Archiving", "Key Distribution", "Key Usage", "Key
Destruction" and "Key Accounting". The key management
functionality has to be designed to provide the cryptographic
keying material "Confidentiality" and "Integrity" throughout its
life cycle.
2.1.5.7.0-2 At a minimum, the ISS-S security services will comprise the Information Only TPS-5149
mandatory Data In Transit (DIT) security service. Other likely
security services are: Data At Rest (DAR) and TRANSEC. All
of these security services will require cryptographic keying
material for their operations.
2.1.5.7.0-3 An ISS Key Management capability must be provided for Mandatory n/a Description of Analysis - and - Demo No TPS-5150
managing the keying material used by any of the ISS-S Compliance
security services.
2.1.5.7.0-4 The ISS Key Management capability must provide a minimum Mandatory n/a GFI: NIST SP 800-57 Description of Analysis - and - Test No TPS-1482
strength of 128 bits of security (see NIST SP 800-57 part 1, Compliance
Table 2) to protect the confidentiality of the cryptographic
keying material used by the ISS-S security services throughout
their life cycle (generation, production, storage, distribution,
usage and destruction).
2.1.5.7.0-5 The ISS Key Management capability must provide a minimum Mandatory n/a Description of Analysis - and - Test No TPS-5151
of 32 bits of integrity to protect cryptographic keying material Compliance
used by the ISS-S security services throughout their life cycle
(generation, production, storage, distribution, usage and
destruction).
2.1.5.7.0-6 The ISS Key Management capability must be integrated with Mandatory SEP-Suite Description of Demo No TPS-1497
the ISS System Executive and Planning Suite (SEP-Suite). Compliance
2.1.5.7.1 Key Generation & Information Only TPS-4992
Production
2.1.5.7.1.0-1 Key Generation is the process of randomly generating a key Information Only TPS-5152
with an appropriate number of bits. The random number
generation technique used to produce the key has to be
designed to provide at least as much entropy as the size of the
keying material it is required to produce. For example, to
produce a 128 bit key requires a random number generator
capable of producing at least 128 bits of entropy will be
needed.
Key Production is the process of transforming a random key
into a key that can be consumed by an end cryptographic
device. Typical steps in the production would be the addition of
attributes indicating the type of usage for the key (i.e. Traffic
Encryption Key -TEK- or Key Encryption Key - KEK - or
others), the level of security a key can be used to protect,
integrity checks on the key and possibly encrypting the key
(i.e. wrapping the key using another key - KEK) to secure its
transfer to another destination or for local storage.
2.1.5.7.1.0-2 The ISS Key Management capability must use a random Mandatory SEP-Suite Description of Analysis - and - Test No TPS-1492
number generation technique that provides a minimum of 128 Compliance
bits of entropy for the generation of ISS-S cryptographic
keying material.
2.1.5.7.1.0-3 The ISS key generation and production capability should be Rated n/a GFI: FIPS 140-2 Certificate of Test No TPS-4090
implemented with the help of a FIPS 140-2 Level 2 or Compliance or
equivalent validated cryptographic module providing a random Description of
number generator with a minimum of 128 bits of entropy and Compliance
the necessary cryptogaphic services to generate and produce
keying material with a minimum of 128 bits of confidentiality
and 32 bits of integrity.
2.1.5.7.2 Key Distribution Information Only TPS-4993
2.1.5.7.2.0-1 Key Distribution is the process of transporting a key that has Information Only TPS-5153
been securely generated and produced to its final destination
into an end cryptographic unit (ECU) for its usage and ultimate
destruction. The distribution process may involve the storage
of the key in external system during transport and might also
require transformation of the key (such as unwrapping it and
wrapping it again) before it reaches its final destination. The
confidentiality and the integrity of the key is be maintained at
all times during the key distribution process.
Page 9 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.5.7.2.0-2 The ISS Key Management capability must provide a means to Mandatory ISS-S, SEP- Description of Demo Yes TPS-4994
distribute cryptographic keying material from one working Suite Compliance
instance of an ISS Key Management node to a final
destination ECU for usage.
2.1.5.7.2.0-3 The ISS Key Management capability should provide a means Rated SEP-Suite Description of Demo No TPS-4995
to distribute cryptographic keying material from one working Compliance
instance of an ISS Key Management node to another.
2.1.5.7.2.0-4 The ISS Key Management capability should provide an Over- Rated ISS-S, SEP- Description of Demo Yes TPS-1488
The-Air-Rekey (OTAR) capability. Suite Compliance
2.1.5.7.2.0-5 If the ISS Key Distribution capability require the usage of a Rated n/a GFI: FIPS 140-2 Certificate of Test No TPS-4093
special key distribution device (e.g. a fill device of sort), then Compliance or
that device should be implemented with the help of a FIPS 140- Description of
2 Level 2 or equivalent, validated cryptographic module Compliance
providing the necessary cryptographic services to distribute
keying material with a minimum of 128 bits of confidentiality
and 32 bits of integrity.
2.1.5.8 EMSEC Information Only TPS-4266
2.1.5.8.0-1 The ISS-S Audio Display, when connected to both the ISS-S Mandatory ISS-S GFE: PRC-148, PRC-152 and PRC-117F Certificate of Test No TPS-4267
radio and an LCSS GFE radio, must provide at least 40dB of Compliance or
isolation between the two signal paths. Description of
Compliance
2.1.5.8.0-2 The ISS-S Audio Display, when connected to both the ISS-S Rated ISS-S GFE: PRC-148, PRC-152 and PRC-117F Certificate of Test No TPS-5172
radio and an LCSS GFE radio, should provide at least 60dB of Compliance or
isolation between the two signal paths. Description of
Compliance
2.1.5.8.0-3 The ISS-S Audio Display, when connected to both the ISS-S Rated ISS-S GFE: PRC-148, PRC-152 and PRC-117F Description of Analysis - and - Test No TPS-4268
radio and an LCSS GFE radio, should not enable a direct Compliance
conductive path between the LCSS GFE radio and the ISS-S.
2.1.6 Reliability, Availability and Information Only TPS-80
Maintainability
2.1.6.0-1 The ISS-S and all its subsystems are to be capable of Information Only ISS-S TPS-2036
operation without loss of function throughout its expected
service life across the full spectrum of environments and
operating conditions specified above and defined in the
Mission Profile and Operational Mode Summary of Annex YY.
2.1.6.0-2 The Reliability and Maintainability performance specifications Information Only ISS-S TPS-2037
listed below are to be measured across the full spectrum of
environments and operating conditions as defined in the
Mission Profile and Operational Mode Summary of Annex YY.
2.1.6.0-3 An integrated Reliability and Maintainability Program for Mandatory ISS-S GFI: NATO ARMP 1 (Edition 4) Description of Analysis No TPS-2038
designing, manufacturing and sustaining the ISS-S, based on GFI: NATO ARMP 7 (Edition 2) Compliance
best practices and standards, must be developed,
incorporated and refined to ensure the economical
achievement of the RAM requirements listed below.
2.1.6.0-4 The Contractor must develop and deliver a Reliability and Mandatory ISS-S Description of Analysis No TPS-2581
Maintainability Program Plan as specified at Annex CA, Compliance
Paragraph xx.
2.1.6.1 Reliability Information Only TPS-2039
2.1.6.1.1 Mission Reliability Information Only TPS-2043
2.1.6.1.1.0-1 The ISS-S must have a Mean Time Between Critical Failures Mandatory ISS-S Description of Contractor's Choice No TPS-2044
(MTBCF) of at least 750 hours (minimum acceptable value), Compliance
under all expected environmental and operating conditions. A
critical failure is an event that results in the loss or degradation
below normal performance limits of a Critical Function, as
defined in the Failure Definition and Scoring Criteria of Annex
XX.
2.1.6.1.2 Basic Reliability Information Only TPS-2048
2.1.6.1.2.0-1 The ISS-S must have a Mean Time Between Failure (MTBF) Mandatory ISS-S Description of Contractor's Choice No TPS-2049
of at least 500 hours (minimum acceptable value), under all Compliance
expected environmental and operating conditions. A failure is
defined as the inability of the ISS-S to perform within
previously specified limits or an intended function. In the
determination of the MTBF it includes Critical Failures,
Essential Function Failures and Non-Essential Function
Failures as defined in the Failure Definition and Scoring
Criteria of Annex XX.
2.1.6.1.3 Durability Information Only TPS-2052
2.1.6.1.3.0-1 The ISS-S must be capable of completing 180 consecutive Mandatory ISS-S Description of Contractor's Choice No TPS-2053
Battlefield Days as per the Mission Profile and Operational Compliance
Mode Summary of Annex YY.
2.1.6.2 Maintainability Information Only TPS-2055
2.1.6.2.1 Maintenance Concept Information Only TPS-2056
2.1.6.2.1.0-1 To maximise the Operational Availability of the ISS-S, repairs Information Only ISS-S TPS-2057
are to be conducted as far forward as possible. To achieve
this, the maintenance concept is to be based on self-test
monitoring, and the replacement of subsystems and modules
(LRUs - Line Replaceable Units) rather than repair. Refer to
Annex ZZ for details on the overall Support Concept.
2.1.6.2.1.0-2 The ISS-S must be designed so that the operator can detect, Mandatory ISS-S Description of Demo No TPS-2058
isolate and remove a faulty LRU and replace, configure and Compliance
check-out the new LRU.
2.1.6.2.2 Maintainability General Information Only TPS-2059
Requirements
Page 10 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.6.2.2.0-1 The in-service Land Force multi-tool should be the only tool Rated ISS-S GFE: Land Force multi-tool Description of Demo No TPS-2062
required by the ISS-S User to make emergency repairs or Compliance
remove and replace an LRU.
2.1.6.2.2.0-2 If special tools or test equipment for the operator are provided, Mandatory ISS-S Description of Demo No TPS-4199
there must only be one single ISS-S multifunction tool to Compliance
service all subsystems.
2.1.6.2.2.0-3 The failure of any ISS-S LRU must not induce or cause Mandatory ISS-S Description of Analysis - and - Demo No TPS-2066
damage in another ISS-S LRU. Compliance
2.1.6.2.3 Operator Maintenance Information Only TPS-2069
2.1.6.2.3.0-1 Operator maintenance must not exceed a mean time of 15 Mandatory ISS-S Description of Test No TPS-2070
minutes per Battlefield Day. Compliance
2.1.6.2.3.0-2 Operator maintenance must be limited to system checks, Mandatory ISS-S Description of Analysis No TPS-2071
inspections, cleaning and replacement of faulty LRUs. Compliance
2.1.6.2.3.0-3 The ISS-S must not need to be dismantled to conduct daily Mandatory ISS-S Demonstration of Demo No TPS-2072
checks and inspection. Function
2.1.6.2.3.0-4 The ISS-S must withstand normal daily cleaning with mild Mandatory ISS-S Description of Analysis - and - Test No TPS-2073
detergent and water without any degradation in operation or Compliance
reliability.
2.1.6.2.3.0-5 When contaminated with POL, the ISS-S must be capable of Mandatory ISS-S Description of Analysis - and - Test No TPS-2074
being cleaned with mild detergent and water to remove a Compliance
significant amount of the POL in order to render any residue
non-hazardous to combustion.
2.1.6.2.4 Mission Service Restoration Information Only TPS-2076
2.1.6.2.4.0-1 The Maximum Mission Time to Restore System Mandatory ISS-S Description of Test No TPS-2077
(MaxMTTRSys) by the operator following a system Critical Compliance
Failure must not be greater than 15 mins at the 90th percentile
(based on a log-normal distribution). This includes fault
detection and isolation, replacement of the faulty LRU, and
confirming repair.
2.1.6.2.4.0-2 The Maximum Mission Time to Restore Service Mandatory ISS-S Description of Test No TPS-2078
(MaxMTTRSvc) following a system Critical Failure must not be Compliance
greater than 30 mins at the 90th percentile (based on a log-
normal distribution). This includes fault detection and isolation,
replacement and reconfiguration of the faulty LRU,
adjustment, calibration, and checks. Service is considered
restored when the ISS-S node is fully operational and has full
data and voice access to the ISS-S network.
2.1.6.2.5 Time to Repair Information Only TPS-2079
2.1.6.2.5.0-1 The ISS-S must have a Mean Time To Repair (MTTR) of an Mandatory ISS-S Description of Test No TPS-2080
LRU at the first line of maintenance of no more than 30 Compliance
minutes and at the second line of maintenance of no more
than 1 hour.
2.1.6.2.6 Preventive Maintenance Information Only TPS-2082
2.1.6.2.6.0-1 The ISS-S should not require any preventive maintenance Rated ISS-S Description of Analysis No TPS-2083
beyond the daily operator checks, inspection and cleaning. Compliance
2.1.6.2.6.0-2 The ISS-S must not exceed a mean time of 1.5 hours of Mandatory ISS-S Description of Test No TPS-2084
preventive maintenance per 168 operating hours (weekly) Compliance
beyond daily operator checks, inspection and cleaning.
2.1.6.3 Built In Test (BIT) and Fault Information Only TPS-2085
Detection
2.1.6.3.0-1 The ISS-S should incorporate embedded Built In Test (BIT) Rated ISS-S Demonstration of Contractor's Choice No TPS-2087
functionality to detect, diagnose and isolate system faults and Function
failures.
2.1.6.3.0-2 The ISS-S BIT design should incorporate Continuous or Rated ISS-S Description of Contractor's Choice No TPS-2089
Periodic Built In Test (BIT) so as not to disrupt normal Compliance
operation.
2.1.6.3.0-3 Normal ISS-S operation should take precedence over BIT Rated ISS-S Description of Contractor's Choice No TPS-2090
functions. Compliance
2.1.6.3.0-4 The operator should be able to manually initiate the available Rated ISS-S Description of Demo No TPS-2375
diagnostic and self-test routines. Compliance
2.1.6.3.0-5 Any interruptive system test or check should be operator Rated ISS-S Description of Analysis No TPS-2091
initiated and not autonomously run. Compliance
2.1.6.3.0-6 The operator should be able to terminate any interruptive Rated ISS-S Description of Demo No TPS-2092
system test or check once started, and return to normal ISS-S Compliance
operation within 5 seconds.
2.1.6.3.0-7 The ISS-S should include start-up BIT that provides a Rated ISS-S Description of Demo No TPS-2093
complete functional test of the system. Compliance
2.1.6.3.0-8 The ISS-S should be able to display a list of all contractor Rated ISS-S Description of Demo No TPS-2574
integrated devices that are part of the ISS-S. Compliance
2.1.6.3.0-9 The list of devices should indicate whether the devices are Rated ISS-S Description of Demo No TPS-2575
connected or not connected to the ISS-S. Compliance
2.1.6.3.0-10 The ISS-S should produce an alarm if a connected device Rated ISS-S Description of Demo No TPS-2576
becomes unconnected. Compliance
2.1.6.3.0-11 The ISS-S should produce an alarm when a device is Rated ISS-S Description of Demo No TPS-2577
connected to the system. Compliance
2.1.6.3.1 Fault Detection Information Only TPS-2095
2.1.6.3.1.0-1 The operator should detect all system Critical Failures by BIT Rated ISS-S Description of Contractor's Choice No TPS-2096
or obvious malfunction, as defined in the Failure Definition and Compliance
Scoring Criteria of Annex XX.
2.1.6.3.1.0-2 The ISS-S BIT should have a Fraction of Faults Detected Rated ISS-S Description of Contractor's Choice No TPS-2097
(FFD), as defined in the Failure Definition and Scoring Criteria Compliance
of Annex XX, of at least 95% of all known faults.
2.1.6.3.2 Fault Isolation Information Only TPS-2098
Page 11 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.1.6.3.2.0-1 For all Critical Failures, the ISS-S BIT should have a Fraction Rated ISS-S Description of Contractor's Choice No TPS-2099
of Faults Isolated (FFI), as defined in the Failure Definition and Compliance
Scoring Criteria of Annex XX, of 95% isolation to a single
LRU.
2.1.6.3.2.0-2 For all detected faults, the ISS-S BIT should have a Fraction of Rated ISS-S Description of Contractor's Choice No TPS-2100
Faults Isolated (FFI), as defined in the Failure Definition and Compliance
Scoring Criteria of Annex XX, of 90% isolation to a single
LRU.
2.1.6.3.3 Fault Reporting Information Only TPS-2101
2.1.6.3.3.0-1 The ISS-S should report any detected ISS-S malfunction or Rated ISS-S Description of Demo No TPS-2102
the loss of functionality to the operator, with fault isolation Compliance
information.
2.1.6.3.3.0-2 The ISS-S should present the results of any manually initiated Rated ISS-S Description of Demo No TPS-2376
diagnostic or self-test routines. Compliance
2.1.6.3.3.0-3 The ISS-S should allow the operator to suppress repetitive Rated ISS-S Description of Demo No TPS-2105
fault reports. Compliance
2.1.6.3.3.0-4 The ISS-S should terminate fault reports automatically when Rated ISS-S Description of Demo No TPS-2106
the fault has been corrected. Compliance
2.1.6.3.4 False Alarms Information Only TPS-2107
2.1.6.3.4.0-1 The ISS-S BIT should have a False Alarm Rate, as defined in Rated ISS-S Description of Contractor's Choice No TPS-2108
the Failure Definition and Scoring Criteria of Annex XX, of less Compliance
than 1%.
2.1.6.3.5 BIT Failure Information Only TPS-2109
2.1.6.3.5.0-1 Failure of the BIT should not cause a system Critical Failure. Rated ISS-S Description of Analysis No TPS-2110
Compliance
2.1.6.3.6 Fault Logging Information Only TPS-2111
2.1.6.3.6.0-1 The ISS-S should record all fault information from the BIT. Rated ISS-S Description of Demo No TPS-2112
Compliance
2.1.6.3.6.0-2 The ISS-S BIT fault information should be retained for at least Rated ISS-S Description of Demo No TPS-2113
30 Battlefield Days. Compliance
2.1.6.3.6.0-3 The ISS-S should allow the System Administrator role to Rated ISS-S Description of Demo No TPS-2114
extract the BIT fault information for further analysis. Compliance
2.1.6.4 Software Fault Recovery Information Only TPS-2377
2.1.6.4.0-1 The ISS-S should monitor software application operations for Rated ISS-S Description of Analysis No TPS-2378
faults and failures. Compliance
2.1.6.4.0-2 The ISS-S should allow the user to reset/restart applications. Rated ISS-S Demonstration of Demo No TPS-2380
Function
2.1.6.5 Service Life Information Only TPS-2117
2.1.6.5.0-1 The reliability and maintainability of the ISS-S, excluding Mandatory ISS-S Description of Contractor's Choice No TPS-2119
batteries, must not be degraded as a result of being Compliance
transported by land, sea or air, or by storage for up to 8 years
under the Basic climatic conditions defined in the Mission
Profile and Operational Mode Summary of Annex YY.
2.2 Subsystem Functional Information Only TPS-74
Requirements
2.2.1 Modular Load Carriage Information Only TPS-5341
System
2.2.1.0-1 Based on the allocated real-estate for the ISS-S in the Mandatory ISS-S CCMFR pouches identified in Annex ZZ. Description of Analysis No TPS-5350
conceptual load configurations that are described in Annex ZZ, Placebo equipment to put in the pouches as per Compliance
the ISS-S physical devices must be affixed on a medium sized Annex ZZ.
Modular Load Carriage System.
2.2.1.0-2 Based on the allocated real-estate for the ISS-S in the Mandatory ISS-S CCMFR pouches identified in Annex ZZ. Description of Analysis No TPS-5370
conceptual load configurations that are described in Annex ZZ, Placebo equipment to put in the pouches as per Compliance
the ISS-S physical devices must be affixed on a large sized Annex ZZ.
Modular Load Carriage System.
2.2.1.0-3 All requirements within this specification must be met while the Mandatory ISS-S CCMFR pouches identified in Annex ZZ. Description of Analysis No TPS-5366
ISS-S physical devices are affixed on a medium size and a Placebo equipment to put in the pouches as per Compliance
large size Modular Load Carriage System in all configurations Annex ZZ.
that are stated in TPS-5350 and TPS-5370.
2.2.1.1 MLCS Carrier Information Only TPS-5343
2.2.1.1.0-1 The MLCS Carrier is expected to be delivered as part of the Information Only No TPS-5373
ISS-S. Detailed requirements TBD.
2.2.1.1.0-2 The MLCS Carrier must be included with the ISS-S. Mandatory ISS-S Description of Contractor's Choice No TPS-5380
Compliance
2.2.1.2 MLCS Combat Pouches Information Only TPS-5344
2.2.1.2.0-1 The MLCS Combat Pouches are to be provided by the Crown. Information Only No TPS-5372
2.2.1.3 MLCS ISS-S Pouches Information Only TPS-3471
2.2.1.3.0-1 The ISS-S equipment is expected to be provided with pouches Information Only No TPS-5371
or attachments to affix to the MLCS. Detailed requirements
TBD.
2.2.1.3.0-2 The MLCS ISS-S Pouches must be included with the ISS-S. Mandatory ISS-S Description of Contractor's Choice No TPS-5381
Compliance
2.2.2 Battle Management System Information Only TPS-87
2.2.2.0-1 The Battle Management System Performance Specifications Information Only TPS-4792
include all the hardware specifications related to the data
storage, processing unit and displays included in the ISS-S.
They also include all the software functions accessible through
the displays.
2.2.2.1 Tactical User Interface Information Only TPS-2478
2.2.2.1.1 General Information Only TPS-5354
2.2.2.1.1.0-1 The ISS-S must include a Tactical User Interface. Mandatory ISS-S Visual Inspection Inspection No TPS-2483
2.2.2.1.1.0-2 The Tactical User Interface must not be head or helmet Mandatory ISS-S Visual Inspection Inspection No TPS-2482
mounted.
2.2.2.1.1.0-3 The Tactical User Interface must have a control to turn off the Mandatory ISS-S Description of Demo No TPS-2507
screen. Compliance
Page 12 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.1.1.0-4 The Tactical User Interface must allow the control and display Mandatory ISS-S Description of Contractor's Choice No TPS-5218
of all supported Battle Management Software functions Compliance
described in TPS-5125.
2.2.2.1.2 Resolution Information Only TPS-2480
2.2.2.1.2.0-1 The Tactical User Interface screen must support a minimum Mandatory ISS-S Description of Contractor's Choice No TPS-2488
resolution of 100 pixels per inch (PPI), both horizontally and Compliance
vertically.
2.2.2.1.2.0-2 The Tactical User Interface screen should support a resolution Rated ISS-S Description of Contractor's Choice No TPS-2489
of more than 100 pixels per inch (PPI), both horizontally and Compliance
vertically.
2.2.2.1.3 Luminance Information Only TPS-465
2.2.2.1.3.0-1 The Tactical User Interface screen luminance must be Mandatory ISS-S Description of Demo No TPS-517
adjustable by the User using a variable control. Compliance
2.2.2.1.3.0-2 The display luminance adjustability (highest to lowest) range Mandatory ISS-S Description of Demo No TPS-5347
must be at least 50:1. Compliance
2.2.2.1.3.0-3 The Tactical User Interface should provide a low-luminance Rated ISS-S Description of Demo No TPS-5348
display setting control that is continuously variable by the user Compliance
across the following range of luminance [0.35 cd/m2 to the full
off position].
2.2.2.1.3.0-4 The Tactical User Interface screen luminance should Rated ISS-S Description of Demo No TPS-5219
automatically adjust to ambient lighting conditions, which is to Compliance
be overridable by the manual variable control as described in
TPS-517.
2.2.2.1.4 Text Entry Capability Information Only TPS-2545
2.2.2.1.4.0-1 A hard keyboard or a soft keyboard are both acceptable Information Only ISS-S TPS-5252
solutions for the Text Entry Capability.
2.2.2.1.4.0-2 The Tactical User Interface must include a Text Entry Mandatory ISS-S Demonstration of Demo No TPS-2546
capability. Function
2.2.2.1.4.0-3 If a hard keyboard solution is provided for the Text Entry Mandatory ISS-S Visual Inspection Inspection No TPS-4099
capability, it must be integrated in the same casing as the
display.
2.2.2.1.4.0-4 The Text Entry capability must allow text input to the Battle Mandatory ISS-S Description of Demo No TPS-2551
Management Software. Compliance
2.2.2.1.4.0-5 The Tactical User Interface Text Entry capability should Rated ISS-S GFI: Ask HF input Description of Inspection No TPS-2547
respect the QWERTY layout. Compliance
2.2.2.1.4.0-6 The Tactical User Interface Text Entry capability should include Rated ISS-S Description of Demo No TPS-2548
all 94 ASCII printable characters, where all lowercase Compliance
alphanumeric characters are accessible using a single
keystroke.
2.2.2.1.4.0-7 The Tactical User Interface Text Entry capability should Rated ISS-S Description of Demo No TPS-4104
provide feedback to the user each time a character is Compliance
selected.
2.2.2.1.5 Touchscreen Interface Information Only TPS-471
2.2.2.1.5.0-1 The Tactical User Interface must include a Touchscreen Mandatory ISS-S Description of Demo No TPS-3930
interface. Compliance
2.2.2.1.5.0-2 The Touchscreen must permit the User to interact with the Mandatory ISS-S Description of Demo No TPS-565
Battle Management Software. Compliance
2.2.2.1.5.0-3 The Touchscreen must permit the User to select and interact Mandatory ISS-S Description of Demo No TPS-2393
with entities, menu items and locations on the map by pointing Compliance
and selecting them.
2.2.2.1.5.0-4 When displaying the map, the Touchscreen must permit the Mandatory ISS-S Description of Demo No TPS-1462
user to select a point on the ground and generate a Military Compliance
Grid Reference System (MGRS) 10 figure grid reference with
UTM map reference sheet for this point.
2.2.2.1.5.0-5 The Touchscreen must be used for any software function that Mandatory ISS-S Description of Demo No TPS-1919
requires the user to provide input or create entities on the Compliance
map.
2.2.2.1.5.0-6 The Tactical User Interface should include a secondary Rated ISS-S Description of Demo No TPS-4098
Pointing and Selection mechanism that does not rely on the Compliance
touchscreen capability.
2.2.2.1.5.0-7 If the Tactical User Interface is accessible using a stylus pen, it Mandatory ISS-S Description of Demo No TPS-2542
must also be useable without the provided stylus. Compliance
2.2.2.2 Main Processing Unit Information Only TPS-448
2.2.2.2.0-1 With a specified set of ISS-S functions executed, CPU Mandatory ISS-S Description of Test No TPS-752
histograms of utilization averaged over a 3 minute period must Compliance
not exceed 75% of the total possible utilization.
2.2.2.2.0-2 With a specified set of ISS-S functions executed, memory Mandatory ISS-S Description of Test No TPS-5221
histograms of utilization averaged over a 3 minute period must Compliance
not exceed 75% of the total possible utilization.
2.2.2.2.0-3 With a specified set of ISS-S functions executed, CPU Rated ISS-S Description of Test No TPS-4804
histograms of utilization averaged over a 3 minute period Compliance
should use as little CPU resources as possible.
2.2.2.2.0-4 With a specified set of ISS-S functions executed, memory Rated ISS-S Description of Test No TPS-5222
histograms of utilization averaged over a 3 minute period Compliance
should use as little memory resources as possible.
2.2.2.2.0-5 The ISS-S must go from a completely turned off state to a Mandatory ISS-S Description of Test No TPS-2523
normal operational state (cold start) in less than 30 seconds, Compliance
excluding the time required by the User to enter his log-in
information.
2.2.2.3 Main data storage Information Only TPS-454
2.2.2.3.0-1 The ISS-S must have a Main data storage where data and Mandatory ISS-S Description of Contractor's Choice No TPS-1466
applications are saved while they are being used by the Compliance
system.
2.2.2.3.0-3 The ISS-S Main data storage must have enough data storage Mandatory ISS-S Description of Contractor's Choice No TPS-2511
to retain 8 GB of data, storage used for applications excluded. Compliance
Page 13 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.3.0-4 The ISS-S Main data storage should have enough data Rated ISS-S Description of Contractor's Choice No TPS-2512
storage to retain more than 8 GB of data, storage used for Compliance
applications excluded.
2.2.2.3.0-6 Any unstructured data must be saved in separate files that the Mandatory ISS-S Description of Demo No TPS-2691
ISS-S User can select, open, delete and exchange. Compliance
2.2.2.3.0-7 The quantity of information, files and entities that can be saved Mandatory ISS-S Description of Contractor's Choice No TPS-675
on the ISS-S must only be limited by the amount of storage Compliance
space on the Main data storage.
2.2.2.4 External Data Storage Information Only TPS-453
2.2.2.4.0-1 The ISS-S should have an External data storage device that Rated ISS-S Description of Demo No TPS-1351
can be removed from the ISS-S and connected to other ISS- Compliance
S.
2.2.2.4.0-2 The ISS-S should have an External data storage device that Rated ISS-S GFE: CF-31 laptop Description of Demo No TPS-5223
can be removed from the ISS-S and connected to a CF-31 Compliance
laptop.
2.2.2.4.0-3 The ISS-S must have the capability of transferring data Mandatory ISS-S Demonstration of Demo No TPS-574
between the Main and External data storage devices. Function
2.2.2.4.0-4 The ISS-S should have the capability of transferring Maps Rated ISS-S Description of Demo No TPS-2672
between the Main and External data storage devices. Compliance
2.2.2.4.0-5 The SEP should have the capability of transferring Maps Rated ISS-S Description of Demo No TPS-4935
between the SEP suite and External data storage devices. Compliance
2.2.2.4.0-6 The ISS-S should have the capability of transferring Routes Rated ISS-S Description of Demo No TPS-2515
between the Main and External data storage devices. Compliance
2.2.2.4.0-7 The ISS-S should have the capability of transferring Hand Rated ISS-S Description of Demo No TPS-2611
drawings between the Main and External data storage devices. Compliance
2.2.2.4.0-8 If the additional functionality presented in TPS-2395, Time Rated ISS-S Description of Demo No TPS-3960
Appreciation tool, is provided, then the ISS-S should have the Compliance
capability of transferring Time Appreciation tables and
templates between the Main and External data storage
devices.
2.2.2.4.0-9 If the additional functionality presented in TPS-2396, Staff Rated ISS-S Description of Demo No TPS-2953
Planning tool, is provided, then the ISS-S should have the Compliance
capability of transferring Planning Tables between the Main
and External data storage devices.
2.2.2.4.0-10 If the additional functionality presented in TPS-2397, Combat Rated ISS-S Description of Demo No TPS-2958
Estimate tool, is provided, then the ISS-S should have the Compliance
capability of transferring Combat Estimates and Estimates
templates between the Main and External data storage
devices.
2.2.2.4.0-11 If the additional functionality presented in TPS-417, Imagery, is Rated ISS-S Description of Demo No TPS-2676
provided, then the ISS-S should have the capability of Compliance
transferring Images between the Main and External data
storage devices.
2.2.2.4.0-12 If the additional functionality presented in TPS-416, Videos, is Rated ISS-S Description of Demo No TPS-2681
provided, then the ISS-S should have the capability of Compliance
transferring videos between the Main and External data
storage devices.
2.2.2.4.0-13 If the additional functionality presented in TPS-376, Graphical Rated ISS-S Description of Demo No TPS-2615
Plans, is provided, then the ISS-S should have the capability of Compliance
transferring Graphical Plans between the Main and External
data storage devices.
2.2.2.4.0-14 If the additional functionality presented in TPS-377, Range Rated ISS-S Description of Demo No TPS-2674
Cards, is provided, then the ISS-S should have the capability Compliance
of transferring Range Cards between the Main and External
data storage devices.
2.2.2.4.0-15 If the additional functionality presented in TPS-2657, Text Rated ISS-S Description of Demo No TPS-4944
Documents, is provided, then the ISS-S should have the Compliance
capability of transferring Text Documents between the Main
and External data storage devices.
2.2.2.4.0-16 The External data storage device must be commercially Mandatory ISS-S Description of Contractor's Choice No TPS-2504
available. Compliance
2.2.2.4.0-17 The ISS-S should provide a place on the ISS-S for the External Rated ISS-S Visual Inspection Contractor's Choice No TPS-757
data storage device to be securely stored while carried by the
user.
2.2.2.4.0-18 The External data storage device must have enough data Mandatory ISS-S Description of Contractor's Choice No TPS-758
storage to retain 4 GB of information. Compliance
2.2.2.4.0-19 The External data storage device should have enough data Rated ISS-S Description of Contractor's Choice No TPS-760
storage to retain more than 4 GB of information. Compliance
2.2.2.4.0-20 The ISS-S should display download percentage completion Rated ISS-S Description of Demo No TPS-1353
status. Compliance
2.2.2.4.0-21 The External data storage device must be a different device Mandatory ISS-S Description of Contractor's Choice No TPS-2503
than the Main data storage. Compliance
2.2.2.5 Battle Management Information Only TPS-5125
Software
2.2.2.5.1 General Information Only TPS-5355
2.2.2.5.1.0-1 The Battle Management Software needs to run on any Information Only ISS-S No TPS-5129
desktop or portable standard personal computer. This
functionality can be used for training purposes, and for
commander planning while in the field.
2.2.2.5.1.0-2 The Battle Management Software must run on an Operating Mandatory ISS-S Description of Contractor's Choice No TPS-1350
System that is commercially available. Compliance
2.2.2.5.1.0-3 The ISS-S Battle Management Software must function on a Mandatory ISS-S GFE: CF-31 Laptop Description of Demo No TPS-5126
CF-31 laptop. GFI: CF-31 typical OS, CPU, Memory (RAM and Compliance
Disk), IOs, etc ...
Page 14 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.1.0-4 It is recognized that some functions of the BMS Software are Information Only TPS-5224
not going to be available as per the nature of CF-31 laptops
(e.g. Comms, Navigation, touchscreen, CORAL-CR-C
interfaces, etc...).
2.2.2.5.1.0-5 The ISS-S must support information exchange of any ISS-S Mandatory ISS-S GFE: CF-31 Laptop Description of Demo No TPS-5127
supported file between a CF-31 laptop and an ISS-S GFI: CF-31 typical OS, CPU, Memory (RAM and Compliance
computer. Disk), IOs, etc ...
2.2.2.5.2 Maps Information Only TPS-427
2.2.2.5.2.1 General Information Only TPS-5356
2.2.2.5.2.1.0-1 The ISS-S must have a Map display capability. Mandatory ISS-S Demonstration of Demo No TPS-2440
Function
2.2.2.5.2.1.0-2 The ISS-S must support map geo-referencing. Mandatory ISS-S Demonstration of Demo No TPS-3936
Function
2.2.2.5.2.1.0-3 The Map display capability must support the display of grid Mandatory ISS-S Demonstration of Demo No TPS-4109
lines. Function
2.2.2.5.2.1.0-4 The ISS-S must have the capability of saving Maps on the Mandatory ISS-S Demonstration of Demo No TPS-2671
Main data storage. Function
2.2.2.5.2.1.0-5 The ISS-S must offer an option to display an indicator showing Mandatory ISS-S Demonstration of Demo No TPS-1343
the true north whenever the map is displayed. Function
2.2.2.5.2.2 Formats Information Only TPS-1921
2.2.2.5.2.2.0-1 The Map display capability must support and display the Mandatory ISS-S Description of Demo No TPS-731
following raster map formats: Compliance
1) ARC Digitised Raster Graphics (ADRG);
2) Compressed ARC Digitised Raster Graphics (CADRG);
3) Controlled Image Base (CIB);
2.2.2.5.2.2.0-2 The Map display capability should support and display Rated ISS-S Description of Demo No TPS-4812
GeoTIFF raster map formats: Compliance
2.2.2.5.2.2.0-3 The Map display capability should support and display National Rated ISS-S GFI:MIL-STD-2500B Description of Demo No TPS-4813
Imagery Transmission Format (NITF, MIL-STD-2500B) raster Compliance
map formats.
2.2.2.5.2.2.0-4 The Map display capability should support and display NATO Rated ISS-S GFI: STANAG 4545 Description of Demo No TPS-4814
Secondary Image Format (NSIF, STANAG 4545) raster map Compliance
formats.
2.2.2.5.2.2.0-5 The Map display capability should support and display Rated ISS-S Description of Demo No TPS-4815
GeoPDF raster map formats. Compliance
2.2.2.5.2.2.0-6 The Map display capability must support and display all the Mandatory ISS-S Description of Demo No TPS-732
following vector map formats: Compliance
1) ESRI Shapefiles;
2) Vector Product Format (VPF).
2.2.2.5.2.2.0-7 The Map display capability must support the Digital Terrain Mandatory ISS-S Description of Demo No TPS-733
Elevation Data (DTED) level 0, 1 and 2 model for terrain Compliance
elevation.
2.2.2.5.2.2.0-8 The Map display capability should support the Digital Terrain Rated ISS-S Description of Demo No TPS-2931
Elevation Data (DTED) level 3 model for terrain elevation. Compliance
2.2.2.5.2.3 Maps functions Information Only TPS-432
2.2.2.5.2.3.1 Zoom Information Only TPS-433
2.2.2.5.2.3.1.0-1 The Map display capability must allow zooming in and out on Mandatory ISS-S Demonstration of Demo No TPS-1713
the map. Function
2.2.2.5.2.3.1.0-2 The zooming functionality must provide sufficient zooming such Mandatory ISS-S Demonstration of Demo No TPS-553
that an area of 2500 square meters makes maximum use of Function
the map display.
2.2.2.5.2.3.1.0-3 The zooming functionality must allow an ISS-S User to clearly Mandatory ISS-S Demonstration of Demo No TPS-4794
distinguish at a minimum of eight (8) entities distributed within Function
a square area of 2500 square metres.
2.2.2.5.2.3.1.0-4 The zooming functionality must provide sufficient zooming out Mandatory ISS-S Demonstration of Demo No TPS-2692
so that it is possible to display a map area of at least 225 Function
square kilometres.
2.2.2.5.2.3.1.0-5 The Map display functionality must display a graphic scale (line Mandatory ISS-S Description of Demo No TPS-1714
marked with distance on the ground which the map user can Compliance
use to determine scale) on the screen to indicate to the user
the dimension of the terrain on the map.
2.2.2.5.2.3.1.0-6 The graphic scale must adjust itself based on the level of Mandatory ISS-S Demonstration of Demo No TPS-4816
zoom. Function
2.2.2.5.2.3.1.0-7 The zooming functionality should be operable by a single Rated ISS-S Demonstration of Demo No TPS-4111
action. Function
2.2.2.5.2.3.1.0-8 When zooming in and out, the Map display functionality should Rated ISS-S Description of Demo No TPS-747
switch automatically between maps of different resolutions, if Compliance
they are available, according to the zoom being displayed.
2.2.2.5.2.3.2 Map orientation Information Only TPS-434
2.2.2.5.2.3.2.0-1 By default, the Map display functionality must display maps Mandatory ISS-S Demonstration of Demo No TPS-1463
oriented with the North facing up on the screen. Function
2.2.2.5.2.3.2.0-2 By default, the map display functionality must have a user Mandatory ISS-S Description of Demo No TPS-748
tracking functionality that moves the map so that it remains Compliance
centred on the user, with an option to override the tracking
functionality and not move the map as the user moves.
2.2.2.5.2.3.2.0-3 The Map display functionality should include a user selected Rated ISS-S Description of Demo No TPS-1464
option to have the map oriented in any direction selected by Compliance
the User.
Page 15 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.2.3.2.0-4 The Map display functionality should include a user selected Rated ISS-S Description of Contractor's Choice No TPS-608
option to have the map orientation continuously adjusts itself to Compliance
have the bearing of the user facing up on the display, with the
following characteristics:
• The rotation of the map made by steps of 10 degrees or
less;
• The bearing is calculated using the direction of travel of the
User when he is travelling;
• The bearing is calculated using the facing direction of the
User when he is not travelling.
2.2.2.5.2.3.3 Pan Information Only TPS-435
2.2.2.5.2.3.3.0-1 The map display functionality must have a Pan capability. Mandatory ISS-S Description of Demo No TPS-750
Compliance
2.2.2.5.3 Navigation Information Only TPS-365
2.2.2.5.3.1 Coordinate References Information Only TPS-2947
Systems
2.2.2.5.3.1.0-1 The ISS-S must have the capability of displaying the MGRS 10 Mandatory ISS-S Demonstration of Demo No TPS-2948
figure grid reference with UTM map reference of any waypoint, Function
entity or point on the map that the User selects.
2.2.2.5.3.1.0-2 The ISS-S should have an option to display positional Rated ISS-S Description of Demo No TPS-4788
information using MGRS 10 figure grid reference with UTM Compliance
map reference or latitude/longitude, in degrees, minutes and
seconds map reference system.
2.2.2.5.3.2 Bearing Information Only TPS-401
2.2.2.5.3.2.0-1 The ISS-S must have the capability to calculate the bearing Mandatory ISS-S Description of Demo No TPS-1338
between two points on the map. Compliance
2.2.2.5.3.2.0-2 The ISS-S must have the capability to display the bearing of Mandatory ISS-S Description of Demo No TPS-2364
the direction faced by the User while travelling and standing Compliance
still.
2.2.2.5.3.2.0-3 The ISS-S must have a user selectable option to display, on Mandatory ISS-S Description of Demo No TPS-1339
the map: Compliance
1) The bearing between two points selected by the user;
2) The bearing currently faced by the user;
3) When the user is moving along a predefined route, the
bearing from the user to the next waypoint;
4) When the user is moving along a predefined route, the
bearing to any waypoint the user selects.
2.2.2.5.3.2.0-4 The ISS-S must be able to display bearing information either in Mandatory ISS-S Demonstration of Demo No TPS-1340
degrees or mils. Function
2.2.2.5.3.2.0-5 The ISS-S should have an option to display bearing Rated ISS-S Demonstration of Demo No TPS-5110
information either in degrees or mils. Function
2.2.2.5.3.3 On-screen Compass Information Only TPS-1342
2.2.2.5.3.3.0-1 The ISS-S must include an integrated electronic compass. Mandatory ISS-S Demonstration of Demo No TPS-5379
Function
2.2.2.5.3.4 Distance Measurement Information Only TPS-402
2.2.2.5.3.4.0-1 The ISS-S must include a Distance Measurement function. Mandatory ISS-S Description of Demo No TPS-715
Compliance
2.2.2.5.3.4.0-2 The Distance Measurement function must have the capacity to Mandatory ISS-S Description of Demo No TPS-716
measure and display the distance along a straight line: Compliance
1) between two points selected on the map,
2) between the User's location and a selected point on the
map,
3) between the User's location and a selected entity.
2.2.2.5.3.4.0-3 The Distance Measurement function must be available to the Mandatory ISS-S Description of Demo No TPS-717
User whenever the map is displayed. Compliance
2.2.2.5.3.4.0-4 The Distance Measurement function should have the capacity Rated ISS-S Description of Demo No TPS-718
to measure automatically and display automatically the Compliance
following information:
• The distance of a route inputted by the user;
• the distance remaining to the final waypoint of a route; and
• the distance travelled along the route.
2.2.2.5.3.4.0-5 The ISS-S must be able to display distance information using Mandatory ISS-S Description of Demo No TPS-719
the metric system. Compliance
2.2.2.5.3.4.0-6 The ISS-S should have an option to display distance Rated ISS-S Description of Demo No TPS-5111
information using either the metric or imperial system. Compliance
2.2.2.5.4 GUI Information Only TPS-421
2.2.2.5.4.1 General Information Only TPS-5357
2.2.2.5.4.1.0-1 The ISS-S must have the capability to maintain concurrently at Mandatory ISS-S Description of Contractor's Choice No TPS-708
least 2000 active entities in memory. Compliance
2.2.2.5.4.2 Colours Information Only TPS-2360
2.2.2.5.4.2.0-1 The ISS-S GUI must be capable of presenting a minimum of Mandatory ISS-S Description of Contractor's Choice No TPS-1744
256 colours graphics. Compliance
2.2.2.5.4.2.0-2 The ISS-S GUI should be capable of presenting more than Rated ISS-S Description of Contractor's Choice No TPS-1745
256 colours graphics. Compliance
2.2.2.5.5 Graphical Data Types Information Only TPS-4818
2.2.2.5.5.1 Blue PA Information Only TPS-2539
2.2.2.5.5.1.0-1 The ISS-S must support Blue PA Graphical data types. Mandatory ISS-S Description of Demo No TPS-2697
Compliance
2.2.2.5.5.1.0-2 The ISS-S must have a Blue PA generation functionality. Mandatory ISS-S Description of Demo No TPS-2585
Compliance
2.2.2.5.5.1.0-3 The Blue PA generation functionality must have the capability Mandatory ISS-S Description of Demo No TPS-2586
to generate a MGRS 10 figure grid reference with UTM map Compliance
reference indicating the ISS-S own position.
Page 16 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.5.1.0-4 The ISS-S own position must be based on the information Mandatory ISS-S Description of Contractor's Choice No TPS-2596
generated by the navigation and positioning functions specified Compliance
in TPS-96.
2.2.2.5.5.1.0-5 The Blue PA generation functionality must automatically Mandatory ISS-S Description of Test No TPS-2587
generate a Blue PA message after a configured time interval Compliance
has passed since the last Blue PA message.
2.2.2.5.5.1.0-6 In addition to the Blue PA messages generated as part of TPS- Rated ISS-S Description of Test No TPS-4820
2587, the Blue PA generation functionality should automatically Compliance
generate a Blue PA message after the user has travelled a
configured distance since the last Blue PA message.
2.2.2.5.5.1.0-7 Blue PA messages must be exchanged over-the-air using the Mandatory ISS-S Description of Demo No TPS-4836
Blue PA rule described in TPS-4182 Compliance
2.2.2.5.5.1.0-8 The ISS-S must indicate to the User when Blue PA information Mandatory ISS-S Description of Contractor's Choice Yes TPS-4100
is unreliable. Information is treated as unreliable if any of the Compliance
following conditions are met:
a) no Blue PA message was received for a predetermined
period of time,
b) the Blue PA message has been marked as unreliable by
the originating node,
c) an indication of GPS spoofing or jamming is received.
2.2.2.5.5.1.0-9 ISS-S nodes for which Blue PA is unreliable, as defined by Mandatory ISS-S Description of Demo No TPS-2721
TPS-4100, must be distinguishable from other nodes. Compliance
2.2.2.5.5.1.0-10 When the ISS-S detects GPS spoofing or jamming, as defined Rated ISS-S Description of Contractor's Choice No TPS-4101
in TPS-96 in the Navigation section, an indication should be Compliance
sent to all nodes on the Blue PA COI.
2.2.2.5.5.1.0-12 By default, the ISS-S must display all ISS-S nodes within the Mandatory ISS-S Description of Demo Yes TPS-2717
ISS-S Network (Blue PA COI). Compliance
2.2.2.5.5.1.0-13 The symbol indicating the User's own position must be Mandatory ISS-S Description of Demo No TPS-3045
different than all other nodes. Compliance
2.2.2.5.5.1.0-14 The ISS-S should provide a bread crumbs feature, that can be Rated ISS-S Description of Demo No TPS-5112
toggle on/off, displaying the real path travelled by the ISS-S Compliance
node.
2.2.2.5.5.1.0-15 The symbol indicating the User's own position should also Rated ISS-S Description of Demo No TPS-3046
indicate the direction of travel when the user is travelling and Compliance
indicate the facing direction when the user is standing still.
2.2.2.5.5.1.0-16 The ISS-S should offer an automatic aggregation mode which Rated ISS-S Description of Demo No TPS-4122
automatically displays either Commanders or centre of mass Compliance
of section / platoon / company depending on the level of zoom.
2.2.2.5.5.1.0-17 The ISS-S should offer the option to view only the Blue PA Rated ISS-S Description of Demo No TPS-2019
from ISS-S nodes registered to selected COIs Compliance
2.2.2.5.5.1.0-18 The ISS-S should have the capability to display different COIs Rated ISS-S Description of Demo No TPS-2023
according to one of three positional information display modes: Compliance
centered on the Commander, centre of mass (aggregated), or
individual soldier positions.
2.2.2.5.5.2 Routes Information Only TPS-399
2.2.2.5.5.2.0-1 The ISS-S must support Routes Graphical data types. Mandatory ISS-S Description of Demo No TPS-2707
Compliance
2.2.2.5.5.2.0-2 In the following subsection, a route refers to a series of Information Only n/a TPS-704
waypoints linked together, indicating to the user a path he is to
follow.
2.2.2.5.5.2.0-3 Users must have the capacity to generate waypoints on the Mandatory ISS-S Description of Demo No TPS-641
map. Compliance
2.2.2.5.5.2.0-4 Users must have the capacity to select waypoints on the map. Mandatory ISS-S Description of Demo No TPS-709
Compliance
2.2.2.5.5.2.0-5 The ISS-S must include a Route Planning function. Mandatory ISS-S Description of Demo No TPS-1691
Compliance
2.2.2.5.5.2.0-6 The Route Planning function must have the capability to create Mandatory ISS-S Description of Demo No TPS-705
routes by inputting and linking waypoints together. Compliance
2.2.2.5.5.2.0-7 The Route Planning function must support Routes of at least Mandatory ISS-S Description of Demo No TPS-5091
200 waypoints Compliance
2.2.2.5.5.2.0-8 The ISS-S Route Planning function must have the capacity to Mandatory ISS-S Description of Demo No TPS-707
modify routes by deleting or adding waypoints at the end of the Compliance
route.
2.2.2.5.5.2.0-9 The ISS-S Route Planning function should have the capacity to Rated ISS-S Description of Demo No TPS-1973
modify routes by selecting, modifying, deleting or adding Compliance
waypoints anywhere in the route, whether it is at the beginning,
the end or between two waypoints.
2.2.2.5.5.2.0-10 The ISS-S must have the capability of saving multiple Routes Mandatory ISS-S Description of Demo No TPS-1692
on the Main data storage. Compliance
2.2.2.5.5.2.0-11 For quick access to alternate routes, the Route Planning Rated ISS-S Description of Demo No TPS-706
function should have the capacity to save multiple routes in Compliance
memory and switch between them on the display.
2.2.2.5.5.2.0-12 When the User wishes to display Routes, he must be able to Mandatory ISS-S Description of Demo No TPS-4154
select which Routes he wants to display from the ones saved Compliance
in his/her system.
2.2.2.5.5.2.0-13 The ISS-S must be capable of displaying multiple Routes at Mandatory ISS-S Description of Demo No TPS-4155
the same time. Compliance
2.2.2.5.5.2.0-14 When the ISS-S displays multiple routes, they must be visually Mandatory ISS-S Description of Demo No TPS-5113
distinguishable. Compliance
2.2.2.5.5.2.0-15 Routes must be exchanged over-the-air using the Manual rule Mandatory ISS-S Description of Demo No TPS-4837
described in TPS-2565 Compliance
2.2.2.5.5.2.0-16 When a Route is exchanged between two ISS-S, the receiving Rated ISS-S Description of Demo No TPS-4838
ISS-S should allow the User to make modifications to the Compliance
received Route.
Page 17 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.5.2.0-17 When a Route is exchanged between two ISS-S, the receiving Rated ISS-S Description of Demo No TPS-4842
ISS-S should allow the User to make copies of the received Compliance
Route.
2.2.2.5.5.2.0-18 The User should have the capability to filter routes. Rated ISS-S Description of Demo No TPS-4877
Compliance
2.2.2.5.5.2.0-19 The Route Planning Function should offer the option to select Rated ISS-S Description of Demo No TPS-1907
an active route. Compliance
2.2.2.5.5.2.0-20 When a user is navigating along an active route, the ISS-S Rated ISS-S Description of Demo No TPS-2949
should be capable of displaying the Estimated Time of Arrival Compliance
to the last waypoint.
2.2.2.5.5.2.0-21 When a user is navigating along an active route, the ISS-S Rated ISS-S Description of Demo No TPS-4913
should be capable of displaying the distance travelled along Compliance
the route.
2.2.2.5.5.3 Hand Drawing Information Only TPS-1721
2.2.2.5.5.3.0-1 The ISS-S must support Hand Drawing Graphical data types. Mandatory ISS-S Description of Demo No TPS-2708
Compliance
2.2.2.5.5.3.0-2 The ISS-S must have a Hand drawing capability when Mandatory ISS-S Demonstration of Demo No TPS-1722
displaying the map. Function
2.2.2.5.5.3.0-3 The Hand drawing capability must allow users to draft quick Mandatory ISS-S Description of Demo No TPS-1725
plans on their map. Compliance
2.2.2.5.5.3.0-4 The Hand drawing capability should support multiple colours. Rated ISS-S Description of Demo No TPS-5114
Compliance
2.2.2.5.5.3.0-5 The Hand drawings must be geo-referenced and associated to Mandatory ISS-S Description of Demo No TPS-1726
the map on which they were drawn. Compliance
2.2.2.5.5.3.0-6 The ISS-S must have the capability of saving multiple Hand Mandatory ISS-S Description of Demo No TPS-2610
drawings on the Main data storage. Compliance
2.2.2.5.5.3.0-7 When the User wishes to display Hand drawings, he/she must Mandatory ISS-S Description of Demo No TPS-4160
be able to select which Hand drawings he/she wants to display Compliance
from the ones saved in his/her system.
2.2.2.5.5.3.0-8 The ISS-S must be capable of displaying multiple Hand Mandatory ISS-S Description of Demo No TPS-4161
drawings at the same time. Compliance
2.2.2.5.5.3.0-9 Hand Drawings must be exchanged over-the-air using the Mandatory ISS-S Description of Demo No TPS-4843
Manual rule described in TPS-2565 Compliance
2.2.2.5.5.3.0-10 When a Hand Drawing is exchanged between two ISS-S, the Rated ISS-S Description of Demo No TPS-4844
receiving ISS-S should allow the User to make modifications to Compliance
the received Hand Drawing.
2.2.2.5.5.3.0-11 When a Hand Drawing is exchanged between two ISS-S, the Rated ISS-S Description of Demo No TPS-4845
receiving ISS-S should allow the User to make copies of the Compliance
received Hand Drawing.
2.2.2.5.5.3.0-12 The User should have the capability to filter Hand Drawings. Rated ISS-S Description of Demo No TPS-4878
Compliance
2.2.2.5.5.4 Quick Symbols Information Only TPS-4819
2.2.2.5.5.4.0-1 The ISS-S must support Quick Symbols Graphical data types Mandatory ISS-S Description of Demo No TPS-4822
Compliance
2.2.2.5.5.4.0-2 The ISS-S must have the capability to generate, display and Mandatory ISS-S Demonstration of Demo No TPS-2598
manage the following Quick Symbols: Function
• Yellow Circle;
• Green Square;
• Red Diamond;
• Black Triangle.
• Blue Rectangle
2.2.2.5.5.4.0-3 Quick Symbols must be exchanged over-the-air using the Mandatory ISS-S Description of Demo No TPS-4847
Automatic rule described in TPS-2562. Compliance
2.2.2.5.5.5 Enemy, Non-Emitting Information Only TPS-1990
Friendly, Unknown, Neutral
entities
2.2.2.5.5.5.0-1 The ISS-S should support Enemy, Non-Emitting Friendly, Rated ISS-S Description of Demo No TPS-4905
Unknown and Neutral entities data types. Compliance
2.2.2.5.5.5.0-2 When displaying the map, the ISS-S should have the capability Rated ISS-S GFI: B-GL-334-001/FP-001 Description of Demo No TPS-1991
to create, display and manage the following entities described Compliance
in B-GL-334-001/FP-001:
• TAM 105.03 UNIT ICONS, section 2 (Unit Icons)
• TAM 105.04 EQUIPMENT ICONS, section 2 (Equipment
Icons), and
• TAM 105.06 IRREGULAR WARFARE
2.2.2.5.5.5.0-3 For presentation purpose, when displaying the entities Rated ISS-S GFI: B-GL-334-001/FP-001 Description of Demo No TPS-4113
specified in TPS-1991, except TAM 105.06 IRREGULAR Compliance
WARFARE, the ISS-S should use the Friend, Hostile,
Unknown and Neutral affiliation symbols used for Land Units,
Land Equipment and Land Installations, presented in B-GL-
334-001/FP-001TAM 105.02, Figure 2.
2.2.2.5.5.5.0-4 The following fields indicated in B-GL-334-001/FP-001 TAM Rated ISS-S GFI: B-GL-334-001/FP-001 Description of Demo No TPS-2003
105.02, Table 1 "Symbol Modifier Fields" should be accessible Compliance
and modifiable by selecting the entity on the display using an
ISS-S:
1) A - Symbol Indicator
2) B - Size Indicator
3) D - Task Force Indicator
4) F - Reinforced or Detached
5) M - Higher Formation
6) S - HQ Indicator / Location Offset Indicator
7) T - Unique Designation
2.2.2.5.5.5.0-5 Entities should include a free text field accessible and Rated ISS-S Description of Demo No TPS-4866
modifiable in the same way as the fields specified in TPS-2003 Compliance
Page 18 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.5.5.0-6 When a User modifies a field indicated in TPS-2003, the ISS-S Rated ISS-S GFI: B-GL-334-001/FP-001 Description of Demo No TPS-4867
should modify the graphical representation of the icon Compliance
according to the placement of modifiers indicated in B-GL-334-
001/FP-001 TAM 105.02, Figure 4 "Unit Size Indicators" and
Figure 5 "Symbol Modifier Field Positions for Units,
Installations and Equipment"
2.2.2.5.5.5.0-7 The User should be able to query symbols/map entities for Rated ISS-S Description of Demo No TPS-4110
more information by placing the cursor on the entity and Compliance
selecting to bring up an information box next to the symbol.
2.2.2.5.5.5.0-8 The ISS-S should allow linking pictures, images, videos or Rated ISS-S Description of Demo No TPS-1993
other files to any enemy, non-emitting friendly, neutral and Compliance
unknown entity on the map.
2.2.2.5.5.5.0-9 The ISS-S should be able to change an enemy, non-emitting Rated ISS-S Description of Demo No TPS-1994
friendly, neutral and unknown entity into another entity Compliance
amongst those four categories by selecting it and making
modifications to its parameters.
2.2.2.5.5.5.0-10 All enemy, non-emitting friendly, neutral and unknown entity Rated ISS-S Description of Demo No TPS-3904
should include the time the entity was created and time of Compliance
modifications.
2.2.2.5.5.5.0-11 The ISS-S should be capable of exchanging enemy, non- Rated ISS-S Description of Demo No TPS-4875
emitting friendly, neutral and unknown entities over-the-air Compliance
using the Automatic rule described in TPS-2562
2.2.2.5.5.5.0-12 When the User adds an enemy, non-emitting friendly, neutral Rated ISS-S Description of Demo No TPS-1998
or unknown entity on the map, the ISS-S should present a list Compliance
of all entities that the User can select.
2.2.2.5.5.5.0-13 Entities should be grouped by categories in the list of Rated ISS-S Description of Demo No TPS-2572
selectable entities to ease user selection. Compliance
2.2.2.5.5.6 Tactical Graphics Information Only TPS-2012
2.2.2.5.5.6.0-1 The ISS-S should support Tactical Graphics data types. Rated ISS-S Demonstration of Demo No TPS-4906
Function
2.2.2.5.5.6.0-2 When displaying the map, the ISS-S should have the capability Rated ISS-S GFI: B-GL-334-001/FP-001 Description of Demo No TPS-2600
to create, display and manage the following Tactical Graphics Compliance
described in B-GL-334-001/FP-001:
• All orders symbols presented in page TAM 102-2 to 102-9
• Friendly Ground Axis of Supporting attack (page TAM 105-
29)
• Friendly Ground Axis of Main Attack (page TAM 105-29)
• Enemy Confirmed (page TAM 105-29)
• General or Unspecified Command and Control Point (page
TAM 105-21)
• Coordination point (page TAM 105-21)
• All boundaries specified in page TAM 105-22
• Point/Single Target (page TAM-37)
• Observation post (OP) / Outpost (page TAM 105-26)
• OP, Recce (page TAM 105-26)
• Obstacle Line (page TAM 105-30)
• Anti-tank ditch (page TAM 105-30)
• Abatis (page TAM 105-30)
• AT minefield (page TAM 105-31)
• AP minefield (page TAM 105-31)
• Trip wire (page TAM 105-32)
• Bridge or gap (page TAM 105-33)
• Double apron fence (page TAM 105-34)
• Low wire fence (page TAM 105-34)
• High wire fence (page TAM 105-34)
• Single concertina (page TAM 105-34)
• Double strand concertina (page TAM 105-34)
• Triple strand concertina (page TAM 105-34)
2.2.2.5.5.6.0-3 When displaying the map, the ISS-S should have the capability Rated ISS-S GFI: B-GL-334-001/FP-001 Description of Demo No TPS-4869
to create, display and manage all the Tactical Graphics Compliance
described in B-GL-334-001/FP-001 section TAM 105.05
"Tactical Graphics". The Hand Drawing capability can be used
in any icon described as a "zone","area","line", or "route".
2.2.2.5.5.6.0-4 When displaying the map, the ISS-S should allow the User to Rated ISS-S Description of Demo No TPS-1944
add text annotation to a point on a map. Compliance
2.2.2.5.5.6.0-5 The ISS-S should be capable of exchanging Tactical Graphics Rated ISS-S Description of Demo No TPS-4942
and text annotation over-the-air using the Automatic rule Compliance
described in TPS-2562
2.2.2.5.5.7 Range Cards Information Only TPS-377
2.2.2.5.5.7.0-1 The ISS-S should support Range Cards data types as Rated ISS-S GFI: B-GL-332-008/FP-001, TAM 807.12 Description of Demo No TPS-4907
described in B-GL-332-008/FP-001, TAM 807.12. Compliance
2.2.2.5.5.7.0-2 When displaying the map, the ISS-S should include a Range Rated ISS-S Demonstration of Demo No TPS-1598
Card function. Function
2.2.2.5.5.7.0-3 The Range Card function should enable ISS-S Users to Rated ISS-S Demonstration of Demo No TPS-635
graphically generate, display and manage range cards for all Function
weapons specified in section TPS-1288.
2.2.2.5.5.7.0-4 If TPS-4907 is provided, Range Cards must be geo- Mandatory ISS-S Description of Demo No TPS-3938
referenced. Compliance
2.2.2.5.5.7.0-5 Range Cards should include the date and time they were Rated ISS-S Description of Demo No TPS-3939
created. Compliance
2.2.2.5.5.7.0-6 The Range Card function should make use of the GIS services Rated ISS-S Description of Demo No TPS-636
and terrain visualisation tools provided by the ISS-S. Compliance
Page 19 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.5.7.0-7 When an ISS-S User initially loads a Range Card, the Range Rated ISS-S Description of Demo No TPS-638
Card function should automatically adjust the zoom and Compliance
resolution such that the full Range Card is displayed, excluding
the Danger Area.
2.2.2.5.5.7.0-8 The ISS-S should be capable of exchanging Range Cards Rated ISS-S Description of Demo No TPS-4873
over-the-air using the Manual rule described in TPS-2565 Compliance
2.2.2.5.5.7.0-9 When a Range Card is exchanged between two ISS-S, the Rated ISS-S Description of Demo No TPS-5295
receiving ISS-S should allow the User to make modifications to Compliance
the received Range Card.
2.2.2.5.5.7.0-10 When a Range Card is exchanged between two ISS-S, the Rated ISS-S Description of Demo No TPS-5296
receiving ISS-S should allow the User to make copies of the Compliance
received Range Card.
2.2.2.5.5.7.1 Range Card Drawing Information Only TPS-1246
2.2.2.5.5.7.1.1 Range Card Content Information Only TPS-1247
2.2.2.5.5.7.1.1.0-1 All range card developed by the Range Card function should Rated ISS-S Description of Demo No TPS-1248
include: Compliance
• A Target Area;
• The weapon the range card was designed for;
• Danger Area;
• A Default weapon direction (if inputted by the user);
• Pre designated targets (if inputted by the user);
• Marked features (if inputted by the user).
2.2.2.5.5.7.1.1.0-2 ISS-S Users should have the capability of inputting multiple Rated ISS-S Description of Demo No TPS-2604
weapons on a single Range Card. Compliance
2.2.2.5.5.7.1.1.0-3 ISS-S Users should have the capability of modifying any Rated ISS-S Description of Demo No TPS-1717
parameter that were inputted while creating the Range Card, Compliance
both while creating the range card and after saving it.
2.2.2.5.5.7.1.1.1 Target Area Information Only TPS-1600
2.2.2.5.5.7.1.1.1.0-1 When drawing a range card, the Range Card function should Rated ISS-S Description of Demo No TPS-1258
require the User to select, for each weapon inputted, a left arc Compliance
of fire, right arc of fire, firing point and type of weapon.
2.2.2.5.5.7.1.1.1.0-2 For the 84mm Carl Gustav and LAVIII 25mm cannon, the Rated ISS-S Description of Demo No TPS-1718
Range Card function should require the User to select the type Compliance
of ammunition.
2.2.2.5.5.7.1.1.1.0-3 The Target area should be the area included within the left arc Rated ISS-S Description of Demo No TPS-1252
of fire, right arc of fire and arc of circle centred on the Compliance
weapon's location, contained within the left and right arc of fire
and representing the maximal weapon effective range.
2.2.2.5.5.7.1.1.1.0-4 The maximal weapon range should be automatically Rated ISS-S Description of Demo No TPS-1254
determined by the Range Card function depending on the Compliance
weapon and ammunition inputted by the user as specified in
section TPS-1288.
2.2.2.5.5.7.1.1.2 Dead Ground Information Only TPS-1599
2.2.2.5.5.7.1.1.2.0-1 If DTED elevation is provided for the area of observation, the Rated ISS-S Description of Demo No TPS-1249
ISS-S should have the capability to generate and display the Compliance
Dead ground, calculated by considering the line of sight from
the weapon's location and altitude, as if the weapon is at
ground level. The Dead ground is the area located within the
Target Area that cannot be reached by the weapon's direct fire
due to obstacles or elevation.
2.2.2.5.5.7.1.1.2.0-2 The Range Card function should offer the option to the ISS-S Rated ISS-S Description of Demo No TPS-1251
User to input a weapon height from the ground and calculate Compliance
the Dead Ground by considering the line of sight from this
altitude.
2.2.2.5.5.7.1.1.3 Danger Area Information Only TPS-1601
2.2.2.5.5.7.1.1.3.0-1 All Danger Areas should be built as described in B-GL-381- Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-2170
001/TS-000, chap 2, para 25, "Danger Area for Single Compliance
Weapon and Multiple Targets", by rotating the danger area
template between the left and right of arc of fire.
2.2.2.5.5.7.1.1.3.0-2 When creating a range card for a C6, C7, C8 or C9, the User Rated ISS-S Description of Demo No TPS-4868
should be able to select the appropriate Danger Area Compliance
Template associated to the weapon selected.
2.2.2.5.5.7.1.1.4 Default Weapon Direction Information Only TPS-1602
2.2.2.5.5.7.1.1.4.0-1 The Range Card function should allow the ISS-S User to Rated ISS-S Description of Demo No TPS-1260
select a direction which is the default line of fire of the weapon. Compliance
2.2.2.5.5.7.1.1.5 Pre Designated Targets and Information Only TPS-1603
Important Features
2.2.2.5.5.7.1.1.5.0-1 When drawing a range card, the Range Card function should Rated ISS-S Description of Demo No TPS-1261
give the ISS-S User the option to identify important features by Compliance
selecting points on the map and adding annotation to the
selected points on the map.
2.2.2.5.5.7.1.1.5.0-2 When drawing a range card, the Range Card function should Rated ISS-S Description of Demo No TPS-1262
give the ISS-S User the option to identify pre-designated Compliance
targets by selecting points on the map and adding annotation
to the selected points on the map.
2.2.2.5.5.7.1.1.5.0-3 The Range Card function should add the MGRS 10 figure grid Rated ISS-S Description of Demo No TPS-1263
reference with UTM grid reference to the annotation of all Compliance
important features and pre-designated targets.
2.2.2.5.5.7.1.2 Primary and Secondary Arcs Information Only TPS-1275
of Fire
2.2.2.5.5.7.1.2.0-1 The Range Card function should allow ISS-S Users to prepare Rated ISS-S Description of Demo No TPS-1276
primary and secondary arcs of fire for a single firing position. Compliance
2.2.2.5.5.7.1.3 Aggregation Information Only TPS-1264
Page 20 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.5.7.1.3.0-1 The ISS-S User should have the option to aggregate the range Rated ISS-S Description of Demo No TPS-1267
cards received from the members of his COI into a single Compliance
Collective Range Card including all the received range cards.
2.2.2.5.5.7.1.3.0-2 The Collective Range Card should include all individual range Rated ISS-S Description of Demo No TPS-1268
cards Danger Area overlays and all individual areas of Compliance
observation.
2.2.2.5.5.7.1.3.0-3 If the ISS-S can calculate Dead Ground, then the Collective Rated ISS-S Description of Demo No TPS-1269
Range Card should include a Collective dead ground which is Compliance
the area that cannot be reached by any weapon within the
Collective range card.
2.2.2.5.5.7.1.3.0-4 When displaying a Collective Range Card, the Range Card Rated ISS-S Description of Demo No TPS-1272
function should have the option to draw only the contour of the Compliance
area of observations as well as the contour of the danger area
overlays received from the members of his COI.
2.2.2.5.5.7.2 Range Cards Display Information Only TPS-1281
2.2.2.5.5.7.2.0-1 When displaying an Individual Range card, the Range Card Rated ISS-S Description of Demo No TPS-1282
display function should offer to turn on or off the following Compliance
options:
• View all range cards received from all members of the COI,
• Display the Danger Area of his weapon,
• Display the aggregated range card of the whole COI,
• Display the pre designated targets,
• Display the marked features,
• Display the default weapon direction,
• Display the Individual or Collective Dead Ground (If provided
by the ISS-S).
2.2.2.5.5.7.2.0-2 When displaying the Range Cards of all members of the Rated ISS-S Description of Demo No TPS-1285
User's COI or the Collective Range Card, the ISS-S User Compliance
should have the option to display the Danger Area of all range
cards or Collective range card.
2.2.2.5.5.7.2.0-3 Pre designated targets should be represented using a different Rated ISS-S Description of Demo No TPS-1287
colour or shape than the important features. Compliance
2.2.2.5.5.7.2.0-4 When displaying an Individual Range Card, the Range Card Rated ISS-S Description of Demo No TPS-1280
function should display the contour of the Target Area. Compliance
2.2.2.5.5.7.2.0-5 The ISS-S should be capable of displaying multiple Range Rated ISS-S Description of Demo No TPS-4149
Cards at the same time. Compliance
2.2.2.5.5.7.3 Supported Weapons Information Only TPS-1288
2.2.2.5.5.7.3.1 C7 Information Only TPS-1289
2.2.2.5.5.7.3.1.0-1 The choices of Danger Area template for a C7 weapon should Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-1436
be the following templates presented in B-GL-381-001/TS- Compliance
000:
• ANNEX B DANGER AREA TEMPLATE CLASSIFICATION
RANGE 5.56 mm QE 89 mils OR LESS
• ANNEX C DANGER AREA TEMPLATE 5.56 mm RIFLE,
LAR OR MG FIELD FIRING QE 200 mils OR LESS, page 2C-
1.
• ANNEX D DANGER AREA TEMPLATE 5.56 mm RIFLE
LAR OR MG ANTI-AIRCRAFT FIRE QE 1200 mils OR LESS
2.2.2.5.5.7.3.1.0-2 When drawing a range card for a C7, the maximum effective Rated ISS-S Description of Demo No TPS-1437
range should be 300m. Compliance
2.2.2.5.5.7.3.2 C8 Information Only TPS-1290
2.2.2.5.5.7.3.2.0-1 The choices of Danger Area template for a C8 weapon should Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-1438
be the following templates presented in B-GL-381-001/TS- Compliance
000:
• ANNEX B DANGER AREA TEMPLATE CLASSIFICATION
RANGE 5.56 mm QE 89 mils OR LESS
• ANNEX C DANGER AREA TEMPLATE 5.56 mm RIFLE,
LAR OR MG FIELD FIRING QE 200 mils OR LESS, page 2C-
1.
• ANNEX D DANGER AREA TEMPLATE 5.56 mm RIFLE
LAR OR MG ANTI-AIRCRAFT FIRE QE 1200 mils OR LESS
2.2.2.5.5.7.3.2.0-2 When drawing a range card for a C8, the maximum effective Rated ISS-S Description of Demo No TPS-1439
range should be 200m. Compliance
2.2.2.5.5.7.3.3 C9 Information Only TPS-1291
2.2.2.5.5.7.3.3.0-1 The choices of Danger Area template for a C9 weapon should Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-1440
be the following templates presented in B-GL-381-001/TS- Compliance
000:
• ANNEX B DANGER AREA TEMPLATE CLASSIFICATION
RANGE 5.56 mm QE 89 mils OR LESS
• ANNEX C DANGER AREA TEMPLATE 5.56 mm RIFLE,
LAR OR MG FIELD FIRING QE 200 mils OR LESS, page 2C-
1.
• ANNEX D DANGER AREA TEMPLATE 5.56 mm RIFLE
LAR OR MG ANTI-AIRCRAFT FIRE QE 1200 mils OR LESS
2.2.2.5.5.7.3.3.0-2 When drawing a range card for a C9, the maximum effective Rated ISS-S Description of Demo No TPS-1441
range should be 600m. Compliance
2.2.2.5.5.7.3.4 C6 Information Only TPS-1292
Page 21 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.5.7.3.4.0-1 The choices of Danger Area template for a C6 weapon should Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-1442
be the following templates presented in B-GL-381-001/TS- Compliance
000:
• ANNEX E DANGER AREA TEMPLATE CLASSIFICATION
RANGE 7.62 mm QE 89 mils OR LESS
• ANNEX F DANGER AREA TEMPLATE 7.62 mm RIFLE,
LAR OR MG FIELD FIRING QE 200 mils OR LESS
• ANNEX G DANGER AREA TEMPLATE 7.62 mm, RIFLE OR
MG ANTI-AIRCRAFT FIRE QE 1200 mils OR LESS
2.2.2.5.5.7.3.4.0-2 When drawing a range card for a C6, the maximum effective Rated ISS-S Description of Demo No TPS-1443
range should be 1200m. Compliance
2.2.2.5.5.7.3.5 M203 Information Only TPS-1293
2.2.2.5.5.7.3.5.0-1 The Danger Area template for a M203 weapon should be the Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-1444
template presented in B-GL-381-001/TS-000, ANNEX W Compliance
DANGER AREA TEMPLATE 40 mm GRENADE C149 AND
C158 LOW VELOCITY PRACTISE COLOUR MARKING
FIRED FROM LAUNCHER M203, page 2W-1.
2.2.2.5.5.7.3.5.0-2 When drawing a range card for a M203, the maximum Rated ISS-S Description of Demo No TPS-1445
effective range should be 400m. Compliance
2.2.2.5.5.7.3.6 84mm Carl Gustav Information Only TPS-1294
2.2.2.5.5.7.3.6.0-1 The Danger Area template for an 84mm Carl Gustav weapon Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-1447
using HEAT RAP FFV551 and FFV552 ammo should be the Compliance
template presented in B-GL-381-001/TS-000, ANNEX AG
DANGER AREA TEMPLATE 84 mm RECOILLESS CARL
GUSTAV M2-M3 CARTRIDGE 84 mm HEAT, RAP FFV551
AND TP RAP FFV 552, page 2AG-1.
2.2.2.5.5.7.3.6.0-2 The Danger Area template for an 84mm Carl Gustav weapon Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-1939
using HEDP FFV502 ammo should be the template presented Compliance
in B-GL-381-001/TS-000, ANNEX AF DANGER AREA
TEMPLATE 84 mm RECOILLESS CARL GUSTAV M2-M3
CARTRIDGE 84 mm HEAT FFV 502.
2.2.2.5.5.7.3.6.0-3 The Danger Area template for an 84mm Carl Gustav weapon Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-1940
using FFV533 ammo should be the template presented in B- Compliance
GL-381-001/TS-000, ANNEX AI DANGER AREA TEMPLATE
84 mm RECOILESS CARL GUSTAV M2-M3 FFV533 QE 200
mils OR LESS.
2.2.2.5.5.7.3.6.0-4 When drawing a range card for an 84mm Carl Gustav using Rated ISS-S Description of Demo No TPS-1446
HEAT RAP FFV551 and FFV552 ammo, the maximum Compliance
effective range should be 700m.
2.2.2.5.5.7.3.6.0-5 When drawing a range card for an 84mm Carl Gustav using Rated ISS-S Description of Demo No TPS-1720
HEDP FFV502 ammo, the maximum effective range should Compliance
be 1000m.
2.2.2.5.5.7.3.6.0-6 When drawing a range card for an 84mm Carl Gustav using Rated ISS-S Description of Demo No TPS-1941
FFV533 ammo, the maximum effective range should be Compliance
1000m.
2.2.2.5.5.7.3.7 LAV III 25mm cannon Information Only TPS-1299
2.2.2.5.5.7.3.7.0-1 The Danger Area template for a LAV III 25mm cannon weapon Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-1452
using C137 ammo should be the template presented in B-GL- Compliance
381-001/TS-000, ANNEX P DANGER AREA TEMPLATE
CARTRIDGE 25 mm C137 APFSDS-T FROM M242 CANON
QUADRANT ELEVATION 178 mils OR LESS, page 2P-1.
2.2.2.5.5.7.3.7.0-2 The Danger Area template for a LAV III 25mm cannon weapon Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-1942
using C138 ammo should be the template presented in B-GL- Compliance
381-001/TS-000, ANNEX Q DANGER AREA TEMPLATE
CARTRIDGE 25 mm FAPDS-T C138 QUADRANT
ELEVATION 178 mils OR LESS.
2.2.2.5.5.7.3.7.0-3 When drawing a range card for a LAV III 25mm cannon for Rated ISS-S Description of Demo No TPS-1453
C137 or C138 ammo, the maximum effective range should be Compliance
2000m.
2.2.2.5.5.7.3.8 M72 Information Only TPS-4915
2.2.2.5.5.7.3.8.0-1 The Danger Area template for a M72 weapon should be the Rated ISS-S GFI: B-GL-381-001/TS-000 Description of Demo No TPS-4916
template presented in B-GL-381-001/TS-000, ANNEX AD Compliance
DANGER AREA TEMPLATE 66 MM LIGHT ATK WEAPON
SYSTEM M72 A5, E5 SERIES STATIONARY ANDMOVING
TARGETS
2.2.2.5.5.7.3.8.0-2 The maximal range for a M72 should be 350m. Rated ISS-S Description of Demo No TPS-4917
Compliance
2.2.2.5.5.8 Graphical Plans Information Only TPS-376
2.2.2.5.5.8.0-1 The ISS-S should support Graphical Plans. Rated ISS-S Description of Demo No TPS-4908
Compliance
2.2.2.5.5.8.0-2 The ISS-S should have a functionality to create Graphical Rated ISS-S Demonstration of Demo No TPS-1983
Plans using all the graphical entities specified in: Function
• TPS-399 (Routes)
• TPS-1721 (Hand Drawings)
• TPS-4819 (Quick Symbols)
• If provided, TPS 1990 (Enemy, Non-emitting friendly,
Unknown, Neutral entities)
• If provided, TPS-2012 (Tactical Graphics)
• If provided, TPS-377 (Range Cards)
2.2.2.5.5.8.0-3 Any entity generated as part of a Graphical Plan should be Rated ISS-S Description of Demo No TPS-2616
associated to this Graphical Plan when saved. Compliance
2.2.2.5.5.8.0-4 Graphical plans should be geo-referenced. Rated ISS-S Description of Demo No TPS-4870
Compliance
Page 22 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.5.8.0-5 When creating a plan, the ISS-S should allow creating Rated ISS-S Description of Demo No TPS-1984
anticipated troops position using the dashed line specified in B- Compliance
GL-334-001/FP-001, TAM 105.02, Figure 3 (Status),
"anticipated or planned position" line.
2.2.2.5.5.8.0-6 The ISS-S should have the capability of saving multiple Rated ISS-S Description of Demo No TPS-2614
Graphical Plans on the Main data storage. Compliance
2.2.2.5.5.8.0-7 The ISS-S should not impose that the User enters a minimal Rated ISS-S Description of Demo No TPS-1986
set of information prior to saving a Graphical Plans. Compliance
2.2.2.5.5.8.0-8 When the User wishes to display Graphical Plans, he/she Mandatory ISS-S Description of Demo No TPS-4165
must be able to select which Graphical Plans he wants to Compliance
display from the ones saved in his/her system.
2.2.2.5.5.8.0-9 The ISS-S should be capable of displaying multiple Graphical Rated ISS-S Description of Demo No TPS-4166
Plans at the same time. Compliance
2.2.2.5.5.8.0-10 The ISS-S User should be able to distinguish entities that are Rated ISS-S Description of Demo No TPS-4168
part of a Plan from other similar entities that are not part of a Compliance
Plan, when both are displayed at the same time. The Battle
Management Software can present entities associated to a
Plan using a slightly different colour, size, contour,
transparency or any other display parameter in order to meet
this requirement.
2.2.2.5.5.8.0-11 The ISS-S should be capable of displaying only a Graphical Rated ISS-S Description of Demo No TPS-4871
Plan on the map, without displaying any other entity. Compliance
2.2.2.5.5.8.0-12 The ISS-S should be capable of exchanging Graphical Plans Rated ISS-S Description of Demo No TPS-4872
over-the-air using the Manual rule described in TPS-2565 Compliance
2.2.2.5.5.8.0-13 When a Graphical Plan is exchanged between two ISS-S, the Rated ISS-S Description of Demo No TPS-5297
receiving ISS-S should allow the User to make modifications to Compliance
the received Graphical Plan.
2.2.2.5.5.8.0-14 When a Graphical Plan is exchanged between two ISS-S, the Rated ISS-S Description of Demo No TPS-5298
receiving ISS-S should allow the User to make copies of the Compliance
received Graphical Plan.
2.2.2.5.6 Intervisibility Information Only TPS-366
2.2.2.5.6.0-1 In this subsection, the term Intervisibility refers to the capacity Information Only n/a TPS-720
to determine and display a full 360 degrees Line Of Sight
assessment from a selected point or series of points on a
map.
2.2.2.5.6.0-2 When displaying the map, the ISS-S should include an Rated ISS-S Description of Demo No TPS-721
Intervisibility function. Compliance
2.2.2.5.6.0-3 The Intervisibility function should use DTED level 2 elevation Rated ISS-S Description of Demo No TPS-723
when calculating Line Of Sight. Compliance
2.2.2.5.6.0-4 The Intervisibility function should allow the User to select a Rated ISS-S Demonstration of Demo No TPS-722
point on the map and have the Intervisibility displayed on the Function
map for this point.
2.2.2.5.6.0-5 The Intervisibility function should allow the User to select Rated ISS-S Description of Demo No TPS-724
multiple points on the map and have the Intervisibility Compliance
simultaneously displayed on the map for all points.
2.2.2.5.7 Power Monitoring Information Only TPS-367
2.2.2.5.7.0-1 By default, the Tactical User Interface should display the ISS-S Rated ISS-S Description of Demo No TPS-1732
main power source charge level whenever the display is turned Compliance
on.
2.2.2.5.8 Request for Medic Information Only TPS-1858
2.2.2.5.8.0-1 The ISS-S should provide a means to generate a Request for Rated ISS-S Description of Demo No TPS-1859
Medic Message. Compliance
2.2.2.5.8.0-2 The Request for Medic function should broadcast a Message Rated ISS-S Description of Demo No TPS-1861
on the Blue PA COI indicating the position of the User that sent Compliance
the Request for Medic.
2.2.2.5.8.0-3 The Request for Medic function should include a way to cancel Rated ISS-S Description of Demo No TPS-4851
the Request for Medic after the Message has been sent on the Compliance
Blue PA COI
2.2.2.5.8.0-4 The Request for Medic function should have safeguards to Rated ISS-S Description of Demo No TPS-3959
avoid accidental activation. Compliance
2.2.2.5.8.0-5 The symbols for individual ISS-S nodes should be different for Rated ISS-S Description of Demo No TPS-2720
nodes that sent a Request for Medic message. Compliance
2.2.2.5.9 Time, clock, daily alarms Information Only TPS-3946
2.2.2.5.9.0-1 The ISS-S should have the capability of displaying the time Rated ISS-S Description of Demo No TPS-3947
from multiple time zones. Compliance
2.2.2.5.9.0-2 The ISS-S should have the capability of setting the local time, Rated ISS-S Description of Demo No TPS-3949
date and time zone. Compliance
2.2.2.5.9.0-3 The ISS-S should have the capability of a stop watch, count Rated ISS-S Description of Demo No TPS-3950
down timer and daily alarms. Compliance
2.2.2.5.10 Mission Planning Tools Information Only TPS-2528
2.2.2.5.10.1 Time Appreciation tool Information Only TPS-2395
2.2.2.5.10.1.0-1 The ISS-S should include a Time Appreciation tool. Rated ISS-S Description of Demo No TPS-2398
Compliance
2.2.2.5.10.1.0-2 The Time Appreciation tool should allow the User to create, Rated ISS-S Description of Demo No TPS-2951
save, load, delete and modify Time Appreciation tables. Compliance
2.2.2.5.10.1.0-3 The Time Appreciation tables should be based on the format Rated ISS-S GFI: B-GL-332-008-FP-001 Description of Demo No TPS-2399
presented in B-GL-332-008-FP-001, section 807.01, Figure 8- Compliance
1 "Example of a time estimate for a platoon attack".
2.2.2.5.10.1.0-4 The Time Appreciation tables should include columns for Rated ISS-S Description of Demo No TPS-2400
activity names, time required for the activity and end time for Compliance
the activity.
2.2.2.5.10.1.0-5 The Time Appreciation tables should present the User with the Rated ISS-S Description of Demo No TPS-2401
current time. Compliance
Page 23 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.10.1.0-6 The Time Appreciation tables should allow the User to Rated ISS-S Description of Demo No TPS-2402
automatically calculate the end time for the activities based on Compliance
the time required or the time allocated based on the end time
for the activities.
2.2.2.5.10.1.0-7 The Time Appreciation tool should allow the User to save Time Rated ISS-S Description of Demo No TPS-2404
Appreciation tables in a printable text format. Compliance
2.2.2.5.10.2 Staff Planning Tool Information Only TPS-2396
2.2.2.5.10.2.0-1 The ISS-S should include a Staff Planning tool. Rated ISS-S Description of Demo No TPS-2406
Compliance
2.2.2.5.10.2.0-2 The Staff Planning tool should allow the User to create, save, Rated ISS-S Description of Demo No TPS-2405
load, delete and modify Planning tables. Compliance
2.2.2.5.10.2.0-3 The Planning tables should be built using a spreadsheet Rated ISS-S Description of Demo No TPS-2408
approach. Compliance
2.2.2.5.10.2.0-4 Planning Tables should be able to include text or numbers. Rated ISS-S Description of Demo No TPS-2409
Compliance
2.2.2.5.10.2.0-5 The User should be able to configure the number of columns Rated ISS-S Description of Demo No TPS-2410
and rows in the Planning tables. Compliance
2.2.2.5.10.2.0-6 Using the Staff Planning tool, the User should be able to start Rated ISS-S GFI: B-GL-334-001-FP-001 Description of Demo No TPS-2411
with a blank Planning Table and reproduce the following tables Compliance
located in B-GL-334-001-FP-001:
• SOP 105, Figure 4: States of Readiness;
• TAM 302.02 - Weapons Data.
2.2.2.5.10.3 Combat Estimate Tool Information Only TPS-2397
2.2.2.5.10.3.0-1 The ISS-S should include a Combat Estimate tool. Rated ISS-S Description of Demo No TPS-2412
Compliance
2.2.2.5.10.3.0-2 Using the Combat Estimate tool, The User should be able to Rated ISS-S GFI: B-GL-300-003/FP-000 Description of Demo No TPS-2955
start with a blank table and reproduce the Estimate presented Compliance
in B-GL-300-003/FP-000, Annex A of Chapter 6, Table 6A.2.
2.2.2.5.10.3.0-3 The Combat Estimate tool should have the capability to switch Rated ISS-S Description of Demo No TPS-2432
back and forth between the Combat Estimate tool and the Compliance
following tools to help the user prepare his combat estimate:
• Map display functionality;
• Plans as defined in TPS-376;
• Distance measurement function as defined in TPS-402;
• Planning tables as defined in TPS-2392;
• Imagery as defined in TPS-417;
• Orders as defined in TPS-386.
2.2.2.5.10.3.0-4 The Combat estimate tool should allow the User to create Rated ISS-S Description of Demo No TPS-2433
tentative Courses of Action, presented in the form of a Compliance
Graphical Plan and Text Document.
2.2.2.5.10.3.0-5 The Combat Estimate tool should allow the User to save Rated ISS-S Description of Demo No TPS-2434
developed Graphical Plans and Text Documents for Compliance
distribution.
2.2.2.5.10.3.0-6 The ISS-S should have the capability of saving, delete and Rated ISS-S Description of Demo No TPS-2957
modify Combat Estimates on the Main data storage. Compliance
2.2.2.5.11 Reports & Returns Information Only TPS-379
2.2.2.5.11.0-1 Reports & Returns should be exchanged over-the-air using the Rated ISS-S Description of Demo No TPS-4858
Manual rule described in TPS-2565. Compliance
2.2.2.5.11.1 Supported Reports & Information Only TPS-2554
Returns
2.2.2.5.11.1.0-1 The ISS-S should have the capacity to receive, generate, Rated ISS-S GFI: B-GL-334-001/FP-001 Description of Demo No TPS-1305
display and manage the pre-formatted, structured Reports & Compliance
Returns listed in Appendix A in accordance with B-GL-334-
001/FP-001.
2.2.2.5.11.1.0-3 The ISS-S should automatically populate all known information Rated ISS-S Description of Demo No TPS-1306
to the appropriate field of the Report & Return being Compliance
generated.
2.2.2.5.11.1.1 Fire Mission Information Only TPS-387
2.2.2.5.11.1.1.0-1 The Fire Mission Report & Return should include all fields Rated ISS-S GFI: B-GL-334-001/FP-001 Description of Demo No TPS-1325
specified in B-GL-334-001/FP-001 SOP 704.08 plus an Compliance
"Adjustments" and "Altitude" field.
2.2.2.5.11.1.1.0-2 When a Fire Mission is sent over the air, the ISS-S should Rated ISS-S Description of Demo No TPS-1326
provide a way to send updates to the "Adjustments" field to the Compliance
Fire Mission over the air.
2.2.2.5.11.1.1.0-3 The Battle Management System should be able to use the Rated ISS-S Description of Demo No TPS-1327
information provided by the CORAL-CR-C to complete the Compliance
Fire Mission Report and Return fields.
2.2.2.5.11.1.1.0-4 If a CORAL-CR-C is not used to fill a Fire Mission Report, the Rated ISS-S Description of Demo No TPS-1328
User should be able to fill the "Direction" and "Target Location" Compliance
fields automatically by selecting a point or an entity on the
map.
2.2.2.5.11.1.1.0-5 If the Map display has DTED elevation data for the target Rated ISS-S Description of Demo No TPS-1329
location, the User should be able to fill the "Altitude" field Compliance
automatically by selecting a point or an entity on the map.
2.2.2.5.11.1.2 ADREP Information Only TPS-388
2.2.2.5.11.1.2.0-1 The ISS-S should have the capacity to receive, generate, and Rated ISS-S Description of Demo No TPS-2662
manage ADREP Reports & Returns. Compliance
2.2.2.5.11.1.2.0-2 The ADREP report should include the following: Rated ISS-S Description of Demo No TPS-1330
1) Title (ADREP); Compliance
2) Time of delivery;
3) Pickup location;
4) Ammo;
5) POL;
6) Rations;
7) Water;
8) Misc.
Page 24 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.11.1.3 Report consolidation Information Only TPS-2663
2.2.2.5.11.1.3.0-1 When an ISS-S user receives multiple ADREPs or SITREPs, Rated ISS-S Description of Demo No TPS-1331
the ISS-S should be able to automatically consolidate specified Compliance
structured reports and produce a consolidated Report &
Return suitable for onward transmission to another ISS-S.
2.2.2.5.11.1.3.0-2 Consolidation of ADREPs or SITREPs should not remove or Rated ISS-S Description of Demo No TPS-1332
modify the received ADREPS or SITREPS or their structured Compliance
data including its persistence in the User's Main data storage.
2.2.2.5.11.2 Input to Reports & Returns Information Only TPS-2555
2.2.2.5.11.2.0-1 The ISS-S User should have the option to change the Rated ISS-S Description of Demo No TPS-1309
information entered into a structured data field by using the Compliance
following means:
1) cut/copy/paste;
2) direct entry from the Text Entry Capability if available;
3) selecting an object or location on the map display (where
applicable);
4) Laser Range Finder if available (where applicable).
2.2.2.5.11.2.0-2 The ISS-S should be capable of generating a Contact Report Rated ISS-S Description of Demo No TPS-2664
when the User adds an enemy, Non-Emitting friendly, Compliance
unknown or neutral entity on his screen.
2.2.2.5.11.2.0-3 The ISS-S should display and save the appropriate enemy, Rated ISS-S Description of Demo No TPS-2665
Non-Emitting friendly, unknown or neutral entity when receiving Compliance
a Contact Report, based on the content of this Contact
Report.
2.2.2.5.12 Imagery Information Only TPS-417
2.2.2.5.12.0-1 The ISS-S should be capable of displaying images with a Rated ISS-S Description of Demo No TPS-483
resolution of 3968x2976 and lower, encoded in the JPEG Compliance
format.
2.2.2.5.12.0-2 The ISS-S should be capable of importing images from Rated ISS-S Description of Demo No TPS-5092
external commercial cameras. Compliance
2.2.2.5.12.0-3 The ISS-S should be capable of converting JPEG pictures into Rated ISS-S GFI: STANAG 4545 Description of Demo No TPS-4123
a STANAG 4545 compliant format by adding, at a minimum, Compliance
geo-referencing and time.
2.2.2.5.12.0-4 The ISS-S should be capable of importing and displaying Rated ISS-S GFI: STANAG 4545 Description of Demo No TPS-4124
images encoded in a STANAG 4545 compliant format. Compliance
2.2.2.5.12.0-5 The ISS-S should have the capability to zoom in and out on a Rated ISS-S Description of Demo No TPS-3942
displayed image. Compliance
2.2.2.5.12.0-6 The ISS-S should have the capability to pan on a displayed Rated ISS-S Description of Demo No TPS-3944
image. Compliance
2.2.2.5.12.0-7 The ISS-S should be capable of scaling images so that it can Rated ISS-S Description of Demo No TPS-3943
be displayed entirely on the display without the User having to Compliance
pan to see the full picture.
2.2.2.5.12.0-8 The ISS-S should have the capability of saving images on the Rated ISS-S Description of Demo No TPS-2675
Main data storage. Compliance
2.2.2.5.12.0-9 The ISS-S should have the capability to annotate pictures and Rated ISS-S Description of Demo No TPS-486
save the annotated pictures. Compliance
2.2.2.5.12.0-10 The ISS-S should be capable of exchanging Images over-the- Rated ISS-S Description of Demo No TPS-4859
air using the Manual rule described in TPS-2565 Compliance
2.2.2.5.12.0-11 If TPS-4795 is provided, the ISS-S should have the ability to Rated ISS-S Description of Demo No TPS-5306
display and save the still imagery and the motion imagery from Compliance
the digital camera(s).
2.2.2.5.13 Videos Information Only TPS-416
2.2.2.5.13.0-1 The ISS-S should be capable of importing, displaying and Rated ISS-S GFI: STANAG 4609 Description of Demo No TPS-4119
saving videos encoded in the standard ITU-T H.264, as Compliance
defined in STANAG 4609 (edition 3).
2.2.2.5.13.0-2 The ISS-S should be capable of importing, displaying and Rated ISS-S GFI: STANAG 4609 Description of Demo No TPS-4120
saving videos encoded in the standard ISO/IEC 13818 (MPEG- Compliance
2), standard definition, as defined in STANAG 4609 (edition 3).
2.2.2.5.13.0-3 The ISS-S should have the capability of saving videos on the Rated ISS-S Description of Demo No TPS-2680
Main data storage. Compliance
2.2.2.5.13.0-4 The ISS-S should be capable of exchanging Videos over-the- Rated ISS-S Description of Demo No TPS-3945
air using the Manual rule described in TPS-2565 Compliance
2.2.2.5.14 Text Messaging Information Only TPS-406
2.2.2.5.14.0-1 The ISS-S should have a Text messaging capability. Rated ISS-S Description of Demo No TPS-1518
Compliance
2.2.2.5.14.0-2 The Text Messaging capability should allow the ISS-S Users to Rated ISS-S Description of Demo No TPS-2420
type free text messages and send them to one or more other Compliance
Users.
2.2.2.5.14.0-3 The ISS-S should have the capability to receive and display Rated ISS-S Description of Demo No TPS-2422
Text messages. Compliance
2.2.2.5.14.0-4 All Text Messages sent or received by the ISS-S should be Rated ISS-S Description of Demo No TPS-2683
saved on the Main data storage. Compliance
2.2.2.5.14.0-5 The ISS-S should have the capability to delete the sent and Rated ISS-S Description of Demo No TPS-2427
received Text messages. Compliance
2.2.2.5.14.0-6 The ISS-S Text Messaging capability should allow the User to Rated ISS-S Description of Demo No TPS-5339
attach files to text messages, and to detach files from Compliance
messages and store them in the Main data storage.
2.2.2.5.14.0-7 The ISS-S should be capable of exchanging Text Messages Rated ISS-S Description of Demo No TPS-4862
over-the-air using the Manual rule described in TPS-2565 Compliance
2.2.2.5.15 Text documents Information Only TPS-2657
Page 25 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.15.0-1 The ISS-S should be capable of reading Text documents Rated ISS-S Description of Demo No TPS-2684
written in the following formats: Compliance
a) Plain Text,
b) RTF (Rich Text Format),
c) Portable Document Format (PDF).
2.2.2.5.15.0-2 The ISS-S should be capable of generating Text documents in Rated ISS-S Description of Demo No TPS-2685
RTF. Compliance
2.2.2.5.15.0-3 The ISS-S User should be capable of writing Orders, Warning Rated ISS-S Description of Demo No TPS-2689
Orders, and Frag Orders using Text documents. Compliance
2.2.2.5.15.0-4 The ISS-S User should be capable of creating, modifying and Rated ISS-S Description of Demo No TPS-2688
reusing templates when writing Orders, Warning Orders, and Compliance
Frag Orders.
2.2.2.5.15.0-5 The ISS-S should have the capability of saving Text Rated ISS-S Description of Demo No TPS-4863
documents on the Main data storage. Compliance
2.2.2.5.15.0-6 The ISS-S should be capable of exchanging Text documents Rated ISS-S Description of Demo No TPS-4864
over-the-air using the Manual rule described in TPS-2565 Compliance
2.2.2.5.16 Overlays Information Only TPS-2530
2.2.2.5.16.0-1 The ISS-S should allow the user to filter all the Graphical Data Rated ISS-S Description of Demo No TPS-613
types defined in TPS-4818 displayed on the map. Compliance
2.2.2.5.16.0-2 Filtered information should be presented on the display in the Rated ISS-S Description of Demo No TPS-736
form of Overlays, with different Data types presented in Compliance
different overlays.
2.2.2.5.16.0-3 The ISS-S should be capable of presenting and supporting Rated ISS-S Description of Demo No TPS-2715
Enemy, Non-Emitting Friendly, Unknown and Neutral entities Compliance
using the following Overlay separation:
• Enemy
• Non-Emitting Friendly
• Neutral and Unknown
2.2.2.5.16.0-4 ISS-S Users should have the capability of turning on or off any Rated ISS-S Description of Demo No TPS-2695
Overlay. Compliance
2.2.2.5.16.0-5 When an overlay is turned on by the User, the ISS-S should Rated ISS-S Description of Demo No TPS-4040
display all data entities associated to the Overlay. Compliance
2.2.2.5.16.0-6 When an overlay is turned off by the User, the ISS-S should Rated ISS-S Description of Demo No TPS-4041
not display any data entity associated to the Overlay. Compliance
2.2.2.5.16.0-7 The ISS-S should be capable of presenting all available Rated ISS-S Description of Demo No TPS-2696
Overlays at the same time. Compliance
2.2.2.5.16.0-8 Different Hand Drawings, Routes, Range Cards and Graphical Rated ISS-S Description of Demo No TPS-4879
Plans should be presented as different Overlays. Compliance
2.2.2.5.17 Alarms and Alerts Information Only TPS-361
2.2.2.5.17.0-1 Definitions: Information Only ISS-S TPS-4918
Caution - A signal that indicates the existence of a condition
requiring attention but not immediate action.
Warning - A signal that indicates the existence of a hazardous
condition requiring immediate action to prevent loss of life,
equipment damage, or a service interruption.
Advisory - A signal that indicates a safe or normal
configuration, condition of performance, or operation of
essential equipment or attracts attention and imparts
information for routine action purposes.
2.2.2.5.17.0-2 It is recommended that alarms and alerts Information Only ISS-S TPS-5116
a. alert the user to the fact that a problem exists,
b. inform the user of the priority and nature of the problem,
c. guide the user's initial responses, and
d. confirm in a timely manner whether the user's response
corrected the problem
2.2.2.5.17.0-3 For each Warning and Caution signal specified in this Rated ISS-S Description of Demo No TPS-1729
document, the ISS-S should produce a visual alert and an Compliance
audio alarm.
2.2.2.5.17.0-4 The User should not be capable of configuring the visual alerts Rated ISS-S Description of Demo No TPS-4824
and audio alarms associated to Warning signals. Compliance
2.2.2.5.17.0-5 The User should be capable of configuring the visual alerts Rated ISS-S Description of Demo No TPS-4826
and audio alarms associated to Caution signals. Compliance
2.2.2.5.17.0-6 Caution signals should be readily distinguishable from warning Rated ISS-S Description of Demo No TPS-4922
signals. Compliance
2.2.2.5.17.0-7 For each Advisory signal specified in this document, the ISS-S Rated ISS-S Description of Demo No TPS-4825
should produce a visual alert. Compliance
2.2.2.5.17.0-8 Audio alarms should provide an auditory cue in the audio Rated ISS-S Description of Demo No TPS-2461
display. Compliance
2.2.2.5.17.0-9 All nonverbal audio signals should be accompanied by a visual Rated ISS-S Description of Demo No TPS-4923
signal that defines the condition. Compliance
2.2.2.5.17.0-10 Visual alerts should provide a visual cue on the Tactical User Rated ISS-S Description of Demo No TPS-2462
Interface. Compliance
2.2.2.5.17.0-11 A message priority system should be established so that more Rated ISS-S Description of Analysis No TPS-4921
critical alarms and alerts override the presentation of any Compliance
alarms and alerts having a lower priority.
2.2.2.5.17.0-12 The user should have the ability to control the volume of all Rated ISS-S Description of Demo No TPS-5117
audio signals generated by the ISS-S BMS functions. Compliance
2.2.2.5.17.0-13 The user should have the ability to turn off the volume of all Rated ISS-S Description of Demo No TPS-5118
audio signals generated by the ISS-S BMS functions. Compliance
2.2.2.5.17.0-14 When the ISS-S BMS functions' audio signals have been Rated ISS-S Description of Demo No TPS-5119
turned off, a visual indication that the audio signals has been Compliance
turned off should be provided to the user.
2.2.2.5.17.0-15 The ISS-S must not present more than seven different non- Mandatory ISS-S Description of Demo No TPS-3145
verbal audible warning signals to the user. Compliance
Page 26 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.17.0-16 In addition to MIL-STD 1472F, it is recommended that any Information Only ISS-S TPS-4834
alarms, audio and voice employed on the ISS-S comply with
the applicable design criteria standards as prescribed in FAA -
Human Factors Design Standards (2003), section 7: Alarms,
Audio, and Voice.
2.2.2.5.17.1 Supported Alarms and Alerts Information Only TPS-4827
2.2.2.5.17.1.0-1 If a user is navigating along an active route, then the ISS-S Rated ISS-S, SEP- Description of Demo No TPS-1909
should provide a Caution to the User when he deviates more Suite Compliance
than a determined distance from the route.
2.2.2.5.17.1.0-2 If the additional functionality presented in TPS-1858, Request Rated ISS-S Description of Demo No TPS-1862
for Medic, is provided, then the ISS-S should produce a Compliance
Warning when receiving a Request for Medic.
2.2.2.5.17.1.0-3 If the additional functionality presented in TPS-406, Text Rated ISS-S Description of Demo No TPS-1520
Messaging, is provided, then Users should be notified when Compliance
they receive a new message.
2.2.2.5.17.1.0-4 If the additional functionality presented in TPS-367, Power Rated ISS-S Description of Demo No TPS-2374
monitoring, is provided, the ISS-S should indicate by means of Compliance
a Warning signal that the main power source contains less
than 20% (+/- 5%) of its charge.
2.2.2.5.17.1.0-5 If the additional functionality presented in TPS-3966, Rated ISS-S Description of Demo No TPS-4829
Emergency Alerts, is provided, then the ISS-S should produce Compliance
a Warning signal when receiving an Emergency Alert
message.
2.2.2.5.17.1.0-6 If the additional functionality presented in TPS-2431, Rated ISS-S Description of Demo No TPS-3956
Precedence level, is provided, then the ISS-S should produce Compliance
a caution whenever a Priority or Immediate message is
received.
2.2.2.5.17.1.0-7 If the additional functionality presented in TPS-2431, Rated ISS-S Description of Demo No TPS-4876
Precedence level, is provided, then the ISS-S should produce Compliance
a Warning whenever a Flash message is received.
2.2.2.5.17.1.0-8 If the additional functionality presented in TPS-2977 is Rated ISS-S Description of Demo No TPS-2979
provided, then the ISS-S should produce an Advisory listing Compliance
the devices that have been configured whenever the Basic
User reconfigures his ISS-S using a Configuration file.
2.2.2.5.17.2 Emergency Alerts Information Only TPS-3966
2.2.2.5.17.2.0-1 The ISS-S should have an Emergency Alert capability. Rated ISS-S Description of Demo No TPS-3967
Compliance
2.2.2.5.17.2.1 Supported Emergency Alerts Information Only TPS-3976
2.2.2.5.17.2.1.0-1 The Emergency Alert capability should allow the ISS-S User to Rated ISS-S Description of Demo No TPS-3968
generate the following Emergency Alerts: Compliance
• Imminent Air Attack,
• Biological or Chemical attack,
• Friendly nuclear strike,
• All Clear.
2.2.2.5.17.2.1.0-2 When generating a Friendly nuclear strike Alert, the ISS-S Rated ISS-S GFI: STANAG 2104 Description of Demo No TPS-3969
User should have the option of inputting graphically: Compliance
• Location of the strike,
• Date-time of the strike,
• A circle centred on the entity indicating the Minimum safe
distance One, as defined in STANAG 2104,
• A circle centred on the entity indicating the Minimum safe
distance Two, as defined in STANAG 2104.
2.2.2.5.17.2.1.0-3 When generating a Friendly nuclear strike Alert, the ISS-S Rated ISS-S Description of Demo No TPS-3973
User should have the option of attaching a free text message Compliance
to the Alert.
2.2.2.5.17.2.1.0-4 When generating a Biological or Chemical attack Alert, the ISS- Rated ISS-S Description of Demo No TPS-3971
S User should have the option of inputting graphically: Compliance
• The location of the entity,
• Date-Time of the attack,
• The contour of an area indicating the contaminated zone,
• The downwind direction.
2.2.2.5.17.2.1.0-5 When generating a Biological or Chemical attack Alert, the ISS- Rated ISS-S Description of Demo No TPS-3974
S User should have the option of attaching a free text Compliance
message to the Alert.
2.2.2.5.17.2.1.0-6 The Imminent Air Attack Alert should consist of a structured Rated ISS-S Description of Demo No TPS-3970
message with the following fields: Compliance
• Date-time of enemy sighting,
• Location of observer,
• Direction of the enemy,
• Free text.
2.2.2.5.17.2.1.0-7 When the ISS-S User generates an Imminent Air Attack Alert, Rated ISS-S Description of Demo No TPS-3975
the Date-time of enemy sighting and location of observer fields Compliance
should be automatically generated by the ISS-S.
2.2.2.5.17.2.2 Generation of Emergency Information Only TPS-3977
Alerts
2.2.2.5.17.2.2.0-1 The ISS-S should automatically generate an Alert Message Rated ISS-S Description of Demo No TPS-3978
upon creation of any Emergency Alert listed in TPS-3976. Compliance
2.2.2.5.17.2.2.0-2 All Emergency Alert Messages should be broadcasted Rated ISS-S Description of Demo No TPS-3980
automatically to all nodes on the ISS-S Network. Compliance
2.2.2.5.17.2.3 Reception of Emergency Information Only TPS-3982
Alerts
Page 27 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.17.2.3.0-1 When receiving an Emergency Alert Message, the ISS-S Rated ISS-S Description of Demo No TPS-3983
should generate a dedicated audio Alarm and visual Alert. Compliance
2.2.2.5.17.2.3.0-2 The ISS-S should not allow the User to disable the audio alarm Rated ISS-S Description of Demo No TPS-3984
and visual alert associated with an Emergency Alert Message. Compliance
2.2.2.5.17.2.3.0-3 Reception of an All clear Emergency Alert should remove all Rated ISS-S Description of Demo No TPS-3987
Visual Alerts and clear Audio Alarms. Compliance
2.2.2.5.18 Data Exchange Capabilities Information Only TPS-4835
2.2.2.5.18.0-1 The ISS-S must have the capability to send any information Mandatory ISS-S Description of Demo No TPS-4180
associated to the Automatic rule using the Manual rule instead Compliance
if the User decides to resend the information.
2.2.2.5.18.0-2 The ISS-S should time-stamp every message being Rated ISS-S Description of Demo No TPS-4117
exchanged. Compliance
2.2.2.5.18.0-3 The ISS-S should have the capability to display the message Rated ISS-S Description of Demo No TPS-4118
time-stamp. Compliance
2.2.2.5.18.1 Rules Information Only TPS-2561
2.2.2.5.18.1.0-1 The ISS-S must support the following Rules: Mandatory ISS-S Description of Demo No TPS-2726
• Automatic; Compliance
• Blue PA;
• Manual.
2.2.2.5.18.1.1 Automatic Information Only TPS-2562
2.2.2.5.18.1.1.0-1 When an ISS-S User sends information based on the Mandatory ISS-S Description of Demo No TPS-2727
"Automatic" Rule, the information must be sent to the Compliance
configured COI(s) as soon as the information entry is
completed and confirmed.
2.2.2.5.18.1.2 Blue PA Information Only TPS-4182
2.2.2.5.18.1.2.0-1 Blue PA must be sent automatically to the Blue PA COI. Mandatory ISS-S Description of Demo No TPS-4181
Compliance
2.2.2.5.18.1.3 Manual Information Only TPS-2565
2.2.2.5.18.1.3.0-1 When an ISS-S User sends information based on the Mandatory ISS-S Description of Demo No TPS-1685
"Manual" Rule, the system must present to him the possible Compliance
COIs and recipients list so that the User can select one or
more recipients from the lists.
2.2.2.5.18.1.3.0-2 The information must be sent to all Users selected recipients Mandatory ISS-S Description of Demo No TPS-2736
list. Compliance
2.2.2.5.18.2 Precedence Level Information Only TPS-2431
2.2.2.5.18.2.0-1 All over-the-air Messages and information exchange should be Rated ISS-S Description of Demo No TPS-1687
associated with a precedence level. Compliance
2.2.2.5.18.2.0-2 ISS-S Users should be able to select the precedence level of Rated ISS-S Description of Demo No TPS-1688
their messages before sending them. Compliance
2.2.2.5.18.2.0-3 Default message settings should be provided to the User. Rated ISS-S Description of Demo No TPS-2929
Compliance
2.2.2.5.18.2.0-4 The precedence levels should be: Rated ISS-S Description of Demo No TPS-1689
• Routine; Compliance
• Priority;
• Immediate;
• Flash.
2.2.2.5.18.2.0-5 In the event of an overloaded network, access to the network Rated ISS-S Description of Test No TPS-1690
resources should be given to messages with the highest Compliance
priority (flash being the highest level, routine being the lowest).
2.2.2.5.18.2.0-6 All Emergency Alert messages listed in TPS-3976 should have Rated ISS-S Description of Demo No TPS-3988
FLASH precedence. Compliance
2.2.2.5.18.3 Address Lists Information Only TPS-1890
2.2.2.5.18.3.0-1 The ISS-S should have an Address List functionality that Rated ISS-S Description of Demo No TPS-1891
provides a list of all Users based on the ORBAT as defined in Compliance
TPS-2938.
2.2.2.5.18.3.0-2 The Address List should include only the Nodes detected by Rated ISS-S Description of Demo No TPS-1893
the Presence service specified in TPS-2939. Compliance
2.2.2.5.18.3.0-3 The Address list should present the ORBAT Position of the Rated ISS-S Description of Demo No TPS-2943
detected nodes. Compliance
2.2.2.5.18.3.0-4 The Address list should group ORBAT positions by platoon, Rated ISS-S Description of Demo No TPS-2944
section and detachments. Compliance
2.2.2.5.18.3.0-5 When the ISS-S User sends a message, file or information Rated ISS-S Description of Demo No TPS-1894
other than friendly positional awareness information, the Compliance
Address List functionality should allow him to select the
individual Users or group of Users to whom the message is to
be sent.
2.2.2.5.18.3.0-6 The ISS-S User should be capable of selecting multiple groups Rated ISS-S Description of Demo No TPS-1895
or multiple Users in the Address List when sending his Compliance
messages.
2.2.2.5.18.3.1 ORBAT Positions Information Only TPS-2938
2.2.2.5.18.3.1.0-1 Upon log-in, the ISS-S User should have the capability to Rated ISS-S Demonstration of Demo No TPS-2933
select their ORBAT position based on a predefined list of Function
positions.
2.2.2.5.18.3.1.0-2 During normal operations, the ISS-S User should have the Rated ISS-S Description of Demo No TPS-4183
capability to modify their ORBAT position based on a Compliance
predefined list of positions without rebooting the system.
2.2.2.5.18.3.2 Presence service Information Only TPS-2939
2.2.2.5.18.3.2.0-1 The Presence Service gives the opportunity to the ISS-S User Information Only TPS-5142
to determine, when required, if a certain node has joined the
network or not for a particular COI. This service tells the ISS-
User which node can receive information or not at a given
time.
2.2.2.5.18.3.2.0-2 The ISS-S should have a Presence Service that detects which Rated ISS-S Description of Demo No TPS-2940
nodes are reachable through the ISS-S network. Compliance
Page 28 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.2.5.18.3.2.0-3 The Presence service should automatically update the list of Rated ISS-S Description of Test Yes TPS-2941
connected nodes every two (2) minutes or faster. Compliance
2.2.2.5.18.4 Interoperability Information Only TPS-1544
2.2.2.5.18.4.1 LCSS Information Only TPS-1545
2.2.2.5.18.4.1.0-1 The ISS-S should be capable of exchanging certain types of Rated ISS-S GFE/GFI: LCSS Data terminal, ICD Description of Demo No TPS-4184
information (e.g. Blue PA, Reports & Returns such as Call for Compliance
fire, SitRep and Contact Report) with the LCSS through a
wired network connections.
Specific types of information exchanged and ICD will be
provided in final specification.
2.2.2.5.19 Integrated Help Information Only TPS-4956
2.2.2.5.19.0-1 The ISS-S must include an Integrated Help function. Mandatory ISS-S Description of Demo No TPS-4957
Compliance
2.2.2.5.19.0-2 The ISS-S Integrated Help function must be accessible from Mandatory ISS-S Description of Demo No TPS-5183
the Tactical User Interface and from the CF-31 Laptop. Compliance
2.2.2.5.19.0-3 The ISS-S Integrated Help function must provide help Mandatory ISS-S Description of Demo No TPS-4958
information for every User function of the ISS-S. Compliance
2.2.2.5.19.0-4 When using the ISS-S Integrated Help function on the CF-31 Mandatory ISS-S Description of Demo No TPS-5180
Laptop, the User must have the ability to save and print the Compliance
help information.
2.2.3 Audio Display Information Only TPS-94
2.2.3.0-1 The ISS-S Audio Display function supports the restitution of Information Only ISS-S TPS-4271
sound from the ISS-S and the functionality to be used by
soldiers in dismounted combat to minimise the risk of
permanent or temporary hearing loss, to enhance the
operator's ability to receive and comprehend information and,
to reduce noise-induced fatigue.
2.2.3.0-2 The ISS-S Audio Display headset includes the following Information Only ISS-S TPS-4275
features:
• the ability to listen to up to two radios concurrently;
• using Push-to-Talks, the ability to transmit on one of possibly
two attached radios.
2.2.3.0-3 The ISS-S Audio Display consists of the following components: Information Only ISS-S TPS-4278
Headset, Control Box and Push-To-Talk; and associated
subcomponents:
2.2.3.0-4 Headset: the part of the ISS-S Audio Display that includes Information Only ISS-S TPS-5136
cabling going to the Earshells and the Earshells themselves.
2.2.3.0-5 Cables: The Cables that connect the control box to the Information Only ISS-S TPS-4285
Headset.
2.2.3.0-6 Earshells: The part of the Headset that provides the hearing Information Only ISS-S TPS-4280
protection, delivers the voice signal from the radio to the user
and from the user to the radio and conveys the ambient
sounds to the user. The Earshell consists of two parts: first a
hard shell that contains the speakers, microphones and any
required circuitry and second a replaceable earplug that fits
into the wearer's ear canal.
2.2.3.0-7 Control Box: A case that holds the circuit boards and other Information Only ISS-S TPS-4282
components needed to operate the Audio Display. The Control
Box is where audio signals from the LCSS SECRET radios
and from the ISS-S Unclassified Communications suite
connect to the Headset. The EMSEC requirements specified
in TPS-4266 apply to the Control Box. For EMSEC
considerations, the Control Box may not be integrated with
another device except for the Wired Push-To-Talk if desired.
2.2.3.0-8 Wired Push-To-Talk (PTT): The Wired Push-To-Talk (PTT) Information Only ISS-S TPS-4283
switches are located on a component worn on the soldier's
body and is easily accessible by the soldier. The Wired PTT
could be integrated in the Control Box.
2.2.3.0-9 Wireless Push-To-Talk (PTT): The Wireless Push-To-Talk Information Only ISS-S TPS-4284
(PTT) switches would be typically located on the soldier's
weapon.
2.2.3.0-10 Noise Reduction System: Passive attenuation, active Information Only ISS-S TPS-4288
attenuation or a combination of both active and passive
attenuation that provides hearing protection.
2.2.3.1 General Description Information Only TPS-4270
2.2.3.1.1 General Information Only TPS-5358
2.2.3.1.1.0-1 An Audio Display must be provided as a core function of the Mandatory ISS-S Visual Inspection Inspection No TPS-4272
ISS-S.
2.2.3.1.1.0-2 The ISS-S Audio Display must include: Mandatory ISS-S Description of Contractor's Choice No TPS-4299
• a Headset that includes two earphones that display the audio Compliance
signal from within the ear canal, microphone(s) that collect the
voice signal from within the ear canal and microphones to
collect the sound from the environment;
• a Noise Reduction System (NRS);
• a Talk Through Circuit (TTC) to convey safe levels of
environmental noise;
• a Control Box that contains the circuitry to connect the audio
signals between the radios and the Headset;
• a Wired Push-To-Talk (PTT) to enable transmission of voice
communications on two voice networks (on one or two radios)
sequentially;
2.2.3.1.1.0-3 The ISS-S Audio Display should include: Rated ISS-S Description of Contractor's Choice No TPS-4276
• a Wireless Push-To-Talk (PTT) to enable transmission of Compliance
voice communications on two voice networks (on one or two
radios) sequentially;
Page 29 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.3.1.1.0-4 The ISS-S Audio Display must be provided to both ears. Mandatory ISS-S Description of Contractor's Choice No TPS-3170
Compliance
2.2.3.1.1.0-5 Using the ISS-S Audio Display, the ISS-S user must be able to Mandatory ISS-S Description of Demo No TPS-3171
perform voice transmissions on one of possibly two Compliance
simultaneously used radios.
2.2.3.1.1.0-6 Using the ISS-S Audio Display, the ISS-S user must be able to Mandatory ISS-S Description of Demo No TPS-5137
perform sequential voice transmissions to two voice networks Compliance
on one radio.
2.2.3.1.1.0-7 Using the ISS-S Audio Display and one radio, the ISS-S user Mandatory ISS-S Description of Demo No TPS-3173
must be able to listen to two voice nets simultaneously, with Compliance
one net to each ear.
2.2.3.1.1.0-8 Using the ISS-S Audio Display and two radios, the ISS-S user Mandatory ISS-S Description of Demo No TPS-5374
must be able to listen to two voice nets simultaneously, one Compliance
voice net per radio, with one net to each ear.
2.2.3.1.1.0-9 The ISS-S Audio Display should be capable of displaying the Rated ISS-S Description of Demo No TPS-3174
same or different information to the right and left ear based on Compliance
User preference.
2.2.3.1.2 Interface Requirements Information Only TPS-4291
2.2.3.1.2.0-1 The ISS-S Audio Display must be worn, used and operated Mandatory ISS-S GFE: Description of Demo No TPS-4292
with the following list of radios: AN/PRC 148 MBITR Compliance
a) ISS-S radio; AN/PRC 152
b) LCSS GFE radio for dismounted forces, as identified below: AN/PRC 117F
i) AN/PRC-148 MBITR; GFI: Interface specifications for the GFE radios
ii) AN/PRC-152;
iii) AN/PRC-117F.
2.2.3.1.2.0-2 The ISS-S Audio Display must operate with and meet the Mandatory ISS-S GFE: Description of Contractor's Choice No TPS-4293
interface specifications of the LCSS GFE Radios. AN/PRC 148 MBITR Compliance
AN/PRC 152
AN/PRC 117F
GFI: Interface specifications for the GFE radios
2.2.3.1.3 Headset and Earshells Information Only TPS-4413
2.2.3.1.3.0-1 All cables connecting to the ISS-S Audio Display headset must Mandatory ISS-S Visual Inspection Contractor's Choice No TPS-4415
be protected by strain relief.
2.2.3.1.3.0-2 Headbands and neckbands must not be part of the ISS-S Mandatory ISS-S Visual Inspection Contractor's Choice No TPS-4307
Audio Display.
2.2.3.1.3.0-3 The replaceable earplug part of the earshell must be available Mandatory ISS-S Description of Contractor's Choice No TPS-5169
in the following two variations: Compliance
1) As foam inserts; and
2) As moulded pieces customized to fit the Users' ears.
2.2.3.1.4 Noise Reduction System Information Only TPS-4310
2.2.3.1.4.0-1 The maximum audio level of the electronic communications Mandatory ISS-S Description of Test No TPS-4342
presented in the ear by the ISS-S Audio Display must be no Compliance
higher than 87dBA.
2.2.3.1.4.0-2 In the 125Hz to 1kHz frequency range, the ISS-S Audio Mandatory ISS-S Description of Test No TPS-4998
Display must provide at least 20dB of attenuation at the ear Compliance
when the external environmental noise is at a level above
107dBA.
2.2.3.1.4.0-3 In the 125Hz to 1kHz frequency range, the ISS-S Audio Rated ISS-S Description of Test No TPS-4999
Display should be able to provide more than 20dB of Compliance
attenuation at the ear when the external environmental noise is
at a level above 107dBA.
2.2.3.1.4.0-4 In the 125Hz to 1kHz frequency range, the ISS-S Audio Mandatory ISS-S Description of Test No TPS-5000
Display must keep the noise level at the ear below 87dBA Compliance
when the environmental noise level is between 87dBA and
107dBA.
2.2.3.1.4.0-5 In the 1kHz to 4kHz frequency range, the ISS-S Audio Display Mandatory ISS-S Description of Test No TPS-5001
must provide at least 30dB of attenuation at the ear when the Compliance
external environmental noise is at a level above 117dBA.
2.2.3.1.4.0-6 In the 1kHz to 4kHz frequency range, the ISS-S Audio Display Rated ISS-S Description of Test No TPS-5002
should be able to provide more than 30dB of attenuation at the Compliance
ear when the external environmental noise is at a level above
117dBA.
2.2.3.1.4.0-7 In the 1kHz to 4kHz frequency range, the ISS-S Audio Display Mandatory ISS-S Description of Test No TPS-5003
must keep the noise level at the ear below 87dBA when the Compliance
environmental noise level is between 87dBA and 117dBA.
2.2.3.1.4.0-8 While the TTC is ON, the ISS-S Audio Display must not Mandatory ISS-S Description of Test No TPS-5004
provide any attenuation when the external environmental noise Compliance
is at a level less than 80dBA.
2.2.3.1.4.0-9 The ISS-S Audio Display must provide protection from impulse Mandatory ISS-S Description of Test No TPS-3161
noise above 140dBA. Compliance
2.2.3.1.4.0-10 If ISS-S Audio Display makes use of Active Noise Cancellation Mandatory ISS-S Description of Demo No TPS-5204
techniques, the User must have the ability to disable that ISS- Compliance
S Audio Display's Active Noise Cancellation function.
2.2.3.1.5 Talk-Through Circuit (TTC) Information Only TPS-4340
2.2.3.1.5.0-1 The TTC must allow the ambient sound to be transmitted to Mandatory ISS-S Demonstration of Demo No TPS-4341
the wearer's ear when the ISS-S Audio Display mode selector Function
switch is set to the Talk-Through Circuit mode.
2.2.3.1.5.0-2 The ISS-S Audio Display TTC should provide the user with the Rated ISS-S Description of Test No TPS-3163
ability to selectively enhance hearing by 3 dB. Compliance
2.2.3.1.5.0-3 The ISS-S Audio Display TTC must have a switch that can be Mandatory ISS-S Demonstration of Demo No TPS-4343
turned ON or OFF. Function
2.2.3.1.6 Voice Microphone Information Only TPS-4345
Page 30 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.3.1.6.0-1 The ISS-S Audio Display must not make use of throat Mandatory ISS-S Description of Contractor's Choice No TPS-4347
microphones. Compliance
2.2.3.2 Human Systems Integration Information Only TPS-5333
2.2.3.2.0-1 The end-to-end over-the-air speech intelligibility of the ISS-S Mandatory ISS-S - Wave file with MRT test on it to bidders Certificate of Test No TPS-3156
must meet a minimum Modified Rhyme Test score of 91%. - PD Staff to provide PRR and headsets to HSI Compliance or
Description of
Compliance
2.2.3.2.0-2 The ISS-S external microphone, amplifier and speaker must Rated ISS-S - Sound files (WAV). Sound files will be Certificate of Test No TPS-3157
not distort sounds from the environment such that a sample of operationally relevant. Specific sounds TBD Compliance or
test subjects can achieve a minimum of x% correct detections Description of
and y% correct identifications as tested in accordance with the Compliance
test plan in Appendix XX.
2.2.3.2.0-3 The mean error of sound localisation should not exceed plus or Rated ISS-S - Sound files (WAV). Sound files will be Certificate of Test No TPS-3158
minus 45 degrees in the horizontal plane as tested in operationally relevant. Specific sounds TBD Compliance or
accordance with the test plan in Appendix XX. Description of
Compliance
2.2.3.3 Audio Display Control Box Information Only TPS-5165
2.2.3.3.0-1 The ISS-S Audio Display Control Box must provide EMSEC Mandatory ISS-S Description of Contractor's Choice No TPS-5167
separation, as specified in TPS-4266, between security Compliance
domains for voice communications.
2.2.3.3.0-2 Because of EMSEC consideration, the ISS-S Audio Display Mandatory ISS-S Description of Contractor's Choice No TPS-5168
Control Box must not be integrated with any other device Compliance
except for the Wired Push-To-Talk if desired.
2.2.3.4 Wired Push-To-Talk (PTT) Information Only TPS-4400
Switch
2.2.3.4.0-1 The ISS-S Wired PTT Switch must have a separate PTT Mandatory ISS-S Demonstration of Contractor's Choice No TPS-4401
switch for each radio voice communication network. Function
2.2.3.4.0-2 The ISS-S Wired PTT Switch must support a single radio Mandatory ISS-S Demonstration of Contractor's Choice No TPS-4403
operating two (2) independent channels on a voice radio Function
communication network allowing sequential voice
transmissions to two (2) voice Communities Of Interest.
2.2.3.4.0-3 The ISS-S Wired PTT Switch must support two (2) radios Mandatory ISS-S Description of Contractor's Choice No TPS-4404
operating each a single channel on a voice radio Compliance
communication network of different security domains, allowing
sequential voice transmissions to two (2) voice Communities
Of Interest.
2.2.3.4.0-4 It is recommended that the Wired PTT Switch be designed Information Only ISS-S TPS-4412
such that the user will be unlikely to unintentionally push the
incorrect PTT switch.
2.2.3.5 Wireless Push-To-Talk (PTT) Information Only TPS-5027
Switch
2.2.3.5.0-1 The ISS-S Wireless PTT Switch should consist of a wireless Rated ISS-S Visual Inspection Contractor's Choice No TPS-5028
PTT switch with a mounting system that allows it to be
attached to the weapon.
2.2.3.5.0-2 The ISS-S Wireless PTT Switch should have a separate PTT Rated ISS-S Demonstration of Contractor's Choice No TPS-5029
switch for each radio voice communication network. Function
2.2.3.5.0-3 The ISS-S Wireless PTT Switch should support a single radio Rated ISS-S Demonstration of Contractor's Choice No TPS-5030
operating two (2) independent channels on a voice radio Function
communication network allowing sequential voice
transmissions to two (2) voice Communities Of Interest.
2.2.3.5.0-4 The ISS-S Wireless PTT Switch should support two (2) radios Rated ISS-S Description of Contractor's Choice No TPS-5031
operating each a single channel on a voice radio Compliance
communication network of different security domain, allowing
sequential voice transmissions to two (2) voice Communities
Of Interest.
2.2.3.5.0-5 It is recommended that the Wireless PTT Switch be designed Information Only ISS-S TPS-5035
such that the user will be unlikely to unintentionally push the
incorrect PTT switch.
2.2.4 Position Generation and Information Only TPS-96
Navigation
2.2.4.0-1 It is expected that dismounted soldiers use GPS for reporting Information Only ISS-S N/A TPS-4203
the location of individuals, sections, platoons, and company
elements. This reporting may be reported verbally using
manual GPS queries or using automated position reporting
systems based on GPS inputs. When GPS signal is degraded
the commander is expected to continue to be able to
determine his position and his team's position. Navigation
sensor may also provide help for fire support missions.
2.2.4.0-2 The ISS-S must be fitted with an integrated Global Positioning Mandatory ISS-S N/A Description of Contractor's Choice No TPS-4204
System receiver. Compliance
2.2.4.0-3 It is expected that ISS-S will be able to calculate and estimate Information Only ISS-S N/A TPS-4219
degradation from the GPS that will trigger warning.
Degradation calculation will be based on:
• GPS receiver's fix is invalid or estimated;
• GPS receiver has access to less then 4 satellites;
• GPS receiver has an average SNR lower than a minimum
threshold.
2.2.4.0-4 The ISS-S must provide the soldier with a warning indication Mandatory ISS-S N/A Description of Test No TPS-4207
that he operates in a GPS-degraded or GPS-denied Compliance
environment.
2.2.4.0-5 The ISS-S GPS must provide position information for 10 digit Mandatory ISS-S N/A Description of Demo No TPS-4208
UTM grid reference. Compliance
2.2.4.0-6 The ISS-S must have the capability to calculate the bearing of Mandatory ISS-S Description of Test No TPS-582
the direction faced by the User in relation with the True North, Compliance
while travelling and while standing still, with an accuracy of at
least 5 degrees.
Page 31 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.4.0-7 The ISS-S should have the capability to calculate the bearing Rated ISS-S Description of Test No TPS-2436
of the direction faced by the User in relation with the True Compliance
North, while travelling and while standing still, with an accuracy
of better than 5 degrees.
2.2.4.0-8 The ISS-S must provide the calculated bearing to the Battle Mandatory ISS-S N/A Description of Demo No TPS-4209
Management System. Compliance
2.2.4.1 GPS Receiver Performance Information Only TPS-4210
2.2.4.1.0-1 The ISS-S integrated GPS receiver must have a minimum Mandatory ISS-S N/A Description of Test No TPS-4212
position accuracy of 13m horizontal with a Circular Error Compliance
Probable (CEP) of 95%, in unobstructed terrain.
2.2.4.1.0-2 The ISS-S integrated GPS receiver should have a minimum Rated ISS-S N/A Description of Test No TPS-4213
position accuracy of 22m vertical with 95% vertical error in Compliance
unobstructed terrain.
2.2.4.1.0-3 Cold Start is usually the slowest TTFF. GPS receiver has Information Only N/A TPS-4215
some knowledge of Almanac data but no Ephemeris data. The
receiver has to download a full set of Ephemeris data from
satellites which are retransmitted every 30 seconds.
2.2.4.1.0-4 Hot Start is usually the quickest TTFF. GPS receiver has Information Only N/A TPS-4216
knowledge of Almanac data most Ephemeris data. The
missing ephemeris information is not sufficient for the GPS
receiver to go through a full Ephemeris transmission cycle.
2.2.4.1.0-5 The ISS-S integrated GPS receiver must not exceed the Mandatory ISS-S N/A Description of Test No TPS-4217
following Time To First Fix in unobstructed terrain: Compliance
1. 60 seconds for a Cold Start;
2. 5 second for a Hot Start.
2.2.4.2 Military GPS Information Only TPS-4223
2.2.4.2.0-1 Military GPS device: A GPS Capable of tracking and decoding Information Only ISS-S N/A TPS-4224
the encrypted P(Y) code.
2.2.4.2.0-2 Military GPS capability is to be provided by either: Information Only ISS-S N/A TPS-4225
1. Providing and proving an interface to the CF in-service
DAGR; or
2. Integrating a Military Grade GPS in the ISS-S
Note: If the DAGR interface concept is chosen, the ISS-S is to
be fitted with a GPS receiver (commercial based).
2.2.4.2.0-3 The ISS-S must be capable of operating in military GPS Mandatory ISS-S N/A Description of Demo No TPS-5214
mode. Compliance
2.2.4.2.0-4 To operate in military GPS mode, the ISS-S should have an Rated ISS-S N/A Description of Demo No TPS-5215
integrated military grade GPS receiver capability based on a Compliance
Selective Availability / Anti-Spoofing Module (SAASM). with the
following characteristics:
2.2.4.2.0-5 To operate in military GPS mode, the ISS-S should have an Rated ISS-S GFE/GFI: DAGR Description of Demo No TPS-5216
interface to interoperate with a DAGR. ICD: User Manual and ICD-GPS-154 Compliance
2.2.4.2.0-6 The Military grade GPS performance must be the same or Mandatory ISS-S N/A Description of Test No TPS-4226
better than the GPS performance specified in the "GPS Compliance
Receiver Performance" section (TPS-4210).
2.2.4.2.0-7 The ISS-S must support IS-GPS-153D messages generated Mandatory ISS-S Description of Test No TPS-4229
by the Military GPS. The minimum message set must be: Compliance
1. 4 (24-Channel Time Mark Data);
2. 5040 (Current Status);
3. 5044 (Warnings).
2.2.4.2.0-8 When operating in military GPS mode, the ISS-S should Rated ISS-S GPS KeyMat Description of Contractor's Choice No TPS-4230
provide the Estimated Position Error (EPE) to the BMS. Compliance
2.2.4.2.0-9 When operating in military GPS mode, the ISS-S must provide Mandatory ISS-S GPS KeyMat Description of Demo No TPS-4231
the soldier with a warning indication when the ISS-S Military Compliance
GPS receiver has identified possible jammer or spoofer as per
message 5044 of IS-GPS-153D.
2.2.4.2.0-10 When operating in military GPS mode, the ISS-S must Mandatory ISS-S GPS KeyMat Description of Contractor's Choice No TPS-4232
process the Military grade GPS information in priority over any Compliance
other GPS device within the ISS-S.
2.2.4.2.0-11 The ISS-S must allow the User to load Military GPS Mandatory ISS-S GPS KeyMat Description of Contractor's Choice No TPS-4233
cryptographic keys and confirm keyed state. Compliance
2.2.4.2.0-12 When operating in military GPS mode, the ISS-S Military GPS Mandatory ISS-S GPS KeyMat Description of Contractor's Choice No TPS-5217
receiver must perform Signal Authentication when Compliance
cryptographic keys are loaded.
2.2.4.2.0-13 When operating in military GPS mode, the ISS-S Military GPS Mandatory ISS-S GPS KeyMat Description of Contractor's Choice No TPS-4234
receiver must perform direct Y-Code Acquisition for quicker Compliance
acquisition.
2.2.4.2.0-14 When operating in military GPS mode, the ISS-S Military GPS Rated ISS-S GPS KeyMat Description of Contractor's Choice No TPS-4236
receiver should simultaneously process L1/L2 dual frequency Compliance
GPS signal reception.
2.2.5 Communication Information Only TPS-97
2.2.5.0-1 The ISS-CS includes all the communications functions that are Information Only ISS-S N/A No TPS-1616
required to enable the soldier to use voice and data services to
fulfil their mission as set out in Section 1 of the TPS.
Communications functions will reside on ISS-S functional
entities, including radios and computer operating systems (i.e.
communications networking functions). The ISS-S will use an
audio display permitting soldiers to talk and listen through the
radio provided by the ISS-CS. The ISS-CS is distinct and
separate from the LCSS and LCSS communications devices.
Page 32 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.5.0-2 Communications functions for dismounted commanders Information Only ISS-S N/A No TPS-1668
include the use of 2 radios. The first radio will be the ISS-S
radio procured by the ISS-S and will provide voice and data
communications with dismounted soldiers. A second SECRET
LCSS radio will be provided as GFE for voice communications
with LCSS-equipped vehicles and other dismounted
commanders. Dismounted commanders will have a visual
display for interaction and control of some ISS-S radio
functions from the Battle Management System.
2.2.5.0-3 Communications functions for dismounted soldiers include Information Only ISS-S N/A No TPS-1669
voice and data communications. The ISS-S will have a visual
display for interaction and control of some radio functions from
the Battle Management System.
2.2.5.0-4 definition: Integrated Soldier System Communications Suite Information Only N/A No TPS-2619
(ISS-CS)
The Integrated Soldier System Communications Suite is a
dismounted soldier communications kit based on a wearable
soldier radio for tactical unclassified voice and data
communications.
2.2.5.0-5 definition ISS-S communications network Information Only N/A No TPS-4080
ISS-S communications network is a dynamic self-forming radio
network established by two or more ISS-CSs to permit the
exchange of information between soldiers. Radios within the
ISS-S communications network are initialised with common
operating parameters (e.g. frequencies, timeslots, encryption
keys, etc.) from a communications plan.
2.2.5.0-6 definition: Land Command Support System (LCSS) Information Only N/A No TPS-2652
The Land Command Support System is the C4ISR system
used by the Canadian Forces to provide Army
communications in a theatre of operations. The LCSS is a
system of systems and includes communications networks for
vehicles, mobile headquarters, static headquarters, and
soldiers. Additionally, the LCSS provides applications and
services to support Army operations. The LCSS operates as a
SECRET System High network for Canadian national
operations.
2.2.5.0-7 definition: Dismounted Peer Network Information Only N/A No TPS-2621
In a system-of-system context with LCSS, the ISS-S
communications network forms a Dismounted Peer Network
consisting of all voice and data COIs for dismounted soldiers.
2.2.5.1 General Information Only TPS-795
2.2.5.1.0-1 The ISS-CS must provide a communications device or set of Mandatory ISS-S Not required Description of Demo Yes TPS-796
devices to all Users with the capability to send and receive Compliance
digital voice and data concurrently within any allocated COI.
2.2.5.1.0-3 The ISS-CS must provide an operational communication Mandatory ISS-S Bid Eval: Trg area, frequency requests Description of Demo Yes TPS-800
system for voice and data communications between Qual: Trg area, frequency requests Compliance
dismounted soldiers at section and platoon for company level Above GFE and GFI for all Comms requirements.
operations as described in scenarios at Annex TBD - SAT.
2.2.5.1.0-4 The ISS-S must provide concurrent communication services Mandatory ISS-S Not required Description of Analysis - and - Demo Yes TPS-4254
for a 60 soldier organisation (i.e., platoon with company Compliance
assets), operationally dispersed over one (1) square kilometre,
including:
4 concurrent section voice exchanges,
1 concurrent platoon, with company assets, voice exchange,
1 concurrent platoon-wide Blue PA exchange,
1 concurrent platoon-wide data exchange (for up to 5 COIs).
2.2.5.1.0-5 The ISS-S must provide concurrent communication services Mandatory ISS-S Not required Description of Analysis - and - Demo Yes TPS-5157
for a 60 soldier organisation (i.e., platoon with company Compliance
assets), operationally dispersed over one (1) square kilometre,
including 4 concurrent section voice exchanges where 3 voice
COIs utilize separate ISS-CS nodes as relaying stations.
2.2.5.1.0-6 The ISS-S should provide concurrent communication services Rated ISS-S Not required Description of Analysis - and - Demo Yes TPS-5158
for a 60 soldier organisation (i.e., platoon with company Compliance
assets), operationally dispersed over one (1) square kilometre,
including 4 concurrent section voice exchanges where 3 voice
COIs automatically utilize any separate dynamically allocated
ISS-CS node as a relaying station.
2.2.5.1.0-7 The ISS-S must provide concurrent communication services Mandatory ISS-S Not required Description of Analysis - and - Demo Yes TPS-5159
for a 60 soldier organisation (i.e., platoon with company Compliance
assets), operationally dispersed over one (1) square kilometre,
for Blue PA exchanges between all stations within 10 seconds
where a minimum of three (3) ISS-CS nodes as dynamically
allocated relaying stations are utilized.
Page 33 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.5.1.0-8 The ISS-S must provide concurrent communication services Mandatory ISS-S Not required Description of Analysis - and - Demo Yes TPS-5160
for a 60 soldier organisation (i.e., platoon with company Compliance
assets), operationally dispersed over one (1) square kilometre,
for data distribution of a 20 kilobyte message from a sender to
all stations within 30 seconds where a minimum of three (3)
ISS-CS nodes as dynamically allocated relaying stations are
utilized.
2.2.5.1.1 Capacity Information Only TPS-244
2.2.5.1.1.0-1 User Services (TPS-246) traffic requirements specifically Mandatory ISS-S Not required Description of Analysis - and - Test Yes TPS-822
identified must be verified using system scenarios provided at Compliance
Annex TBD - SAT.
2.2.5.1.1.0-2 Each ISS-CS must provide communications capacity for Mandatory ISS-S Not required Demonstration of Test Yes TPS-2633
concurrent reception of two independent voice networks and Function
for transmission on either voice network when selected.
2.2.5.1.1.0-3 Each ISS-CS must provide communications capacity for Mandatory ISS-S Not required Demonstration of Test Yes TPS-2634
concurrent transmission and reception of two voice Networks Function
and a data Network where data channel(s) will provide for the
exchange of User Services (TPS-246). NOTE: only one voice
network is selected for outbound transmission at any point in
time.
2.2.5.1.1.0-4 The ISS-S communications network must support a minimum Mandatory ISS-S Trg area, frequency requests, trg keys Description of Test Yes TPS-1622
of 5 concurrent, non-overlapping voice networks located within Compliance
one square kilometre for dismounted close combat
operations. (This requirement to be verified as part of a
system level scenario / use case).
2.2.5.1.1.0-5 The ISS-CS must perform network synchronisation and meet Mandatory ISS-S Description of Test No TPS-4261
the functional and performance requirements defined in this Compliance
specification in a GPS-denied environment.
2.2.5.1.2 Mobility and Movement Information Only TPS-245
2.2.5.1.2.0-1 Once set up with its initial data fill, the ISS-S communications Mandatory ISS-S Bid Eval: Nil Description of Analysis - and - Test Yes TPS-833
network must automatically adapt (i.e. no manual interaction Qual: Could GFE/GFI the layout of attenuator Compliance
for data services) to support connectivity changes due to tree, but also need to verify. Contractor could also
mobility, topology, or attrition while maintaining reachability provide the attenuator tree.
between ISS-S nodes.
2.2.5.1.2.0-2 When groups of ISS-S nodes move within radio range of one Mandatory ISS-S Trg area, frequency requests, trg keys Description of Test No TPS-1623
or more other ISS-S nodes, the ISS-CS must provide voice Compliance
service with no perceived voice service interruptions when
there is no change in voice relays while data is being
exchanged on the network.
2.2.5.1.2.0-3 When groups of ISS-S nodes move within radio range of one Mandatory ISS-S Trg area, frequency requests, trg keys Description of Analysis Yes TPS-2635
or more other ISS-S nodes, the ISS-CS must provide PA Compliance
service with the loss of no more than 2 sequential PA
messages per minute per user.
2.2.5.1.3 Operational Modes Information Only TPS-242
2.2.5.1.3.0-1 Any group of ISS-CS, once loaded with an initial configuration Rated ISS-S Not required Description of Demo Yes TPS-804
fill, should be able to automatically establish a dismounted Compliance
peer network without operator intervention as the standard
operating mode.
2.2.5.1.3.0-2 Once a dismounted peer network has been established, the Rated ISS-S Not required Description of Demo Yes TPS-803
ISS-CS, loaded with its persistent configuration fill, should Compliance
provide voice and data services without operator intervention
other than applying power to the device.
2.2.5.1.3.0-3 Once a dismounted peer network has been established Mandatory ISS-S Not required Description of Test No TPS-2622
between several ISS-S nodes, any new ISS-S node must allow Compliance
soldiers to exchange voice messages within 60 seconds of
applying power to the ISS-CS.
2.2.5.1.3.0-4 Once a dismounted peer network has been established, the Mandatory ISS-S Not required Description of Test No TPS-2623
ISS-S must transmit positional awareness messages within 90 Compliance
seconds of applying power to the ISS-CS.
2.2.5.2 User Services Information Only TPS-246
2.2.5.2.1 Voice Information Only TPS-247
2.2.5.2.1.1 General Information Only TPS-5359
2.2.5.2.1.1.0-1 A voice COI is a named virtual radio channel associated with a Information Only n/a N/A No TPS-2132
set of system users, providing a means of establishing two-
way communication among those users with a single speaker
(User) at any point in time.
2.2.5.2.1.1.0-2 A selectable voice COI is a voice COI that has been allocated Information Only n/a N/A No TPS-1632
to the user by the System Manager and is available for use as
either an active voice COI or inactive voice COI (not available)
through a user selection function.
2.2.5.2.1.1.0-3 A selected primary voice COI has been chosen by the user as Information Only n/a N/A No TPS-1633
a voice group to be directed to the audio display. The user can
hear audio from this primary voice COI in an assigned ear.
When the user activates the voice transmission switch -
primary voice COI control, the user's voice is transmitted over
the air on the active primary voice COI.
2.2.5.2.1.1.0-4 A selected secondary voice COI has been chosen by the user Information Only n/a N/A No TPS-1634
as a voice group to be directed to the audio display. The user
can hear audio from this voice group in an assigned ear,
opposite from the primary voice group. When the user
activates the voice transmission switch - secondary voice COI
control, the user's voice is transmitted over the air on the
active secondary voice COI.
2.2.5.2.1.1.0-5 Voice speech inputs and outputs for soldiers must be provided Mandatory ISS-S Not required Description of Demo No TPS-836
through the ISS-S Audio Display connected to the ISS-CS. The Compliance
ISS-S Audio Display is defined in TPS-94.
Page 34 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.5.2.1.1.0-6 The ISS-CS must provide individual, user-selectable voice Mandatory ISS-S Not required Description of Demo No TPS-2638
COIs for voice exchanges (i.e. listen/speak) between COI Compliance
members.
2.2.5.2.1.2 Voice Service Information Only TPS-249
2.2.5.2.1.2.0-1 The ISS-S voice service will enable an all-informed voice Information Only ISS-S N/A No TPS-2124
network with a single person speaking and multiple listeners.
2.2.5.2.1.2.0-2 The ISS-CS must provide voice service to enable the individual Mandatory ISS-S Description of Demo No TPS-837
soldier to communicate vocally through the ISS-CS radio in the Compliance
following configurations:
1) ISS-CS and ISS-S Audio Display only; and
2) ISS-S (all components)
2.2.5.2.1.2.0-3 The ISS-CS voice service must be activated by a soldier Mandatory ISS-S Not required Description of Demo No TPS-840
pressing the ISS-S Audio Display's PTT switch, as defined in Compliance
TPS-94.
2.2.5.2.1.3 Voice Communities of Information Only TPS-250
Interest
2.2.5.2.1.3.0-1 The ISS-CS must present and make available 5 or more voice Mandatory ISS-S Not required Description of Demo No TPS-847
COIs which can be selected and assigned to available PTT Compliance
switches or controls.
2.2.5.2.1.3.0-3 The voice service should time out a speaker when a voice Rated ISS-S Not required Description of Test No TPS-2641
transmission switch remains in the active position for longer Compliance
than 90 seconds on any voice COI or provide other
mechanisms to allow remaining members of a voice COI to
continue using the voice COI.
2.2.5.2.1.4 Voice Encoding Information Only TPS-253
2.2.5.2.1.4.0-2 If other voice codecs other than STANAG 4591 are proposed, Rated ISS-S Not required Description of Contractor's Choice No TPS-2133
the base data stream should be less than or equal to 16 kbps Compliance
for each voice channel.
2.2.5.2.2 Data Information Only TPS-255
2.2.5.2.2.1 Data Exchange Information Only TPS-256
2.2.5.2.2.1.0-1 The ISS-S communications network must provide end-to-end Mandatory ISS-S Not required; assume contractor provides all BMS Description of Contractor's Choice Yes TPS-859
data distribution between instances of the Battle Management information required Compliance
System. We are not stipulating data types, or information
types, quantities, etc.
2.2.5.2.2.2 Data Types Information Only TPS-257
2.2.5.2.2.2.0-1 The ISS-S communications network must support the Mandatory ISS-S Not required; assume contractor provides all data Demonstration of Demo Yes TPS-860
transmission of multiple data types as defined in this types as test information Function
specification.
2.2.5.2.2.3 Delivery to Communities of Information Only TPS-258
Interest
2.2.5.2.2.3.0-1 The ISS-S communications network must distribute data and Mandatory ISS-S Not required; assume contractor provides all data Description of Contractor's Choice Yes TPS-861
voice to all network-reachable ISS-S nodes subscribed to a types as test information Compliance
defined COI.
2.2.5.2.2.3.0-2 Data exchanges sent from an ISS-S to a Community of Mandatory ISS-S Not required; assume contractor provides all data Description of Contractor's Choice Yes TPS-862
Interest must be distributed to all Community of Interest types as test information Compliance
instances (one to many transfer).
2.2.5.2.2.3.0-3 The ISS-S must permit users to select Communities of Interest Mandatory ISS-S Not required; assume contractor provides all data Description of Contractor's Choice Yes TPS-864
for data exchange. types as test information Compliance
2.2.5.2.2.4 Data Transfer Modes Information Only TPS-259
2.2.5.2.2.4.0-1 The ISS-CS must exchange Internet Protocol packets with Mandatory ISS-S Description of Contractor's Choice No TPS-865
external devices. Compliance
2.2.5.2.2.5 Data Applications Information Only TPS-1738
2.2.5.2.2.5.1 Video Information Only TPS-260
2.2.5.2.2.5.1.0-1 The ISS-CS should stream video, defined as Level 1 Low- Rated ISS-S Crown provides motion imagery data. To be Description of Test Yes TPS-869
Bandwidth Motion Imagery (Motion Imagery System Matrix gathered from ISTAR project. Yves Compliance
levels - L1.0H and L1.1H) as per STANAG 4609 Edition 3 Simoneau/Leon Anderson to verify the data is
(2009) and Allied Publication AEDP-08, Edition 2 (2007), obtainable.
between ISS-S CS instances, including one (1) relaying node.
2.2.5.2.2.6 Grade of Service Information Only TPS-263
2.2.5.2.2.6.1 General Information Only TPS-5360
2.2.5.2.2.6.1.0-1 The ISS-CS must provide resource reservation or prioritization Mandatory ISS-S N/A Description of Analysis - and - Test No TPS-876
mechanisms within the ISS communications network for low Compliance
latency services (e.g., voice, positional awareness data).
2.2.5.2.2.6.2 Voice Information Only TPS-2138
2.2.5.2.2.6.2.0-1 The ISS-S voice service must provide end-to-end voice service Mandatory ISS-S N/A Description of Test No TPS-2139
between two ISS-CS nodes, with one (1) intervening ISS-CS Compliance
relay nodes, having a maximum end-to-end one-way voice
delay of less than 400 milliseconds.
2.2.5.2.2.6.2.0-2 The ISS-S voice service should provide end-to-end voice Rated ISS-S N/A Description of Test No TPS-4068
service between two ISS-CS nodes, with one (1) intervening Compliance
ISS-CS relay nodes, having a maximum end-to-end one-way
voice delay of less than 200 milliseconds.
2.2.5.2.2.6.3 Positional Awareness Information Only TPS-2142
2.2.5.2.2.6.3.0-1 The Positional Awareness service must have a maximum end- Mandatory ISS-S N/A Description of Analysis - and - Test No TPS-2143
to-end one-way delay of less than four (4) seconds between Compliance
ten (10) ISS-S nodes in the same COI and operating within
250 metres in open and complex terrain under a network
loading consistent with scenario in Annex TBD.
(A position transmitted by any node will be received by the
other 9 nodes within 4 seconds).
Page 35 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.5.2.2.6.3.0-2 The Positional Awareness service must have a maximum end- Mandatory ISS-S N/A Description of Analysis - and - Test No TPS-2642
to-end one-way delay of less than ten (10) seconds between Compliance
thirty (30) ISS-S nodes operating within a circle of 1000 metres
diameter in open terrain under a network loading consistent
with scenario in Annex TBD.
(A position transmitted by any node will be received by the
other 29 nodes within 10 seconds).
2.2.5.2.2.6.3.0-3 The Positional Awareness service should have a maximum Rated ISS-S N/A Description of Analysis No TPS-2643
end-to-end one-way delay of less than fifteen (15) seconds Compliance
between 60 ISS-S nodes operating within a circle of 2000
metres diameter in open terrain under a network loading
consistent with scenario in Annex TBD.
(A position transmitted by any node will be received by the
other 59 nodes within 15 seconds).
2.2.5.3 Communications Coverage Information Only TPS-243
2.2.5.3.0-1 The ISS-CS is expected to provide voice and data services to Information Only n/a N/A No TPS-808
dismounted soldiers, sections, platoons, and company in
suburban, urban, forested, jungle, caves, sewers, and desert
environments.
2.2.5.3.1 Relay Information Only TPS-812
2.2.5.3.1.0-1 Definition: relaying: The concept of relaying user data and Information Only ISS-S TPS-5189
possibly control information between ISS-CS mobile devices
through one or more relay stations using allocated spectrum.
The purpose of enabling relay is to enhance coverage, range,
throughput, and capacity of the ISS-S communications
network. Relaying is considered to be distinct from routing.
2.2.5.3.1.0-2 Definition: relay link: An ISS-CS mobile device radio link Information Only ISS-S TPS-5190
between a pair of ISS-CS devices.
Relayed traffic can be sent in either direction between devices.
2.2.5.3.1.0-3 Definition: relay path: Concatenation of k consecutive relay Information Only ISS-S TPS-5191
links (k >= 1) between ISS-CS mobile devices.
2.2.5.3.1.0-4 Definition: relay traffic: Traffic traveling over a relay link. Information Only ISS-S TPS-5192
2.2.5.3.1.0-5 Definition: relaying device: An ISS-CS mobile device that Information Only ISS-S TPS-5193
conforms to this specification and whose functions are 1) to
relay user data and possibly control information between other
stations, and 2) to execute processes that indirectly support
mobile multihop relay.
2.2.5.3.1.0-6 Definition: Mobile adhoc network: A MANET consists of mobile Information Only ISS-S TPS-5194
platforms, referred to as nodes, which are free to move about
arbitrarily. A MANET is an autonomous system of mobile
nodes.
MANET nodes are equipped with wireless transmitters and
receivers using antennas. At a given point in time, depending
on the nodes' positions and their transmitter and receiver
coverage patterns, transmission power levels and co-channel
interference levels, a wireless connectivity in the form of a
random, multihop graph or "ad hoc" network exists between
the nodes. This ad hoc topology may change with time as the
nodes move or adjust their transmission and reception
parameters. [adapted from IETF RFC 2501]
2.2.5.3.1.0-7 The ISS-S communications network must provide mobile Mandatory ISS-S N/A Description of Contractor's Choice Yes TPS-3907
adhoc networking. Compliance
2.2.5.3.1.0-8 A cluster of ISS-CSs forming an ISS-S communications Mandatory ISS-S N/A Description of Contractor's Choice Yes TPS-3908
network must have no single point of failure. Compliance
2.2.5.3.1.0-9 The ISS-CS must provide automatic reconfiguration of relays Mandatory ISS-S N/A Description of Contractor's Choice Yes TPS-5161
for data services. Compliance
2.2.5.3.1.0-10 The ISS-CS should provide automatic reconfiguration of relays Rated ISS-S N/A Description of Analysis - and - Demo Yes TPS-4079
for voice services. Compliance
2.2.5.3.1.0-11 When configured, each ISS-CS must be capable of acting as Mandatory ISS-S N/A Description of Demo Yes TPS-3909
voice and data relays for other ISS-CSs in the network. Compliance
2.2.5.3.1.0-12 The ISS-S communications network must provide single hop Mandatory ISS-S N/A Description of Analysis - and - Test Yes TPS-4253
(i.e. direct path) or multi-hop (i.e. relay path) capability for data Compliance
distribution to extend the network range to at least two (2)
thousand metres in open terrain.
2.2.5.3.1.0-13 The ISS-S communications network should provide single hop Rated ISS-S N/A Description of Analysis - and - Test Yes TPS-3910
(i.e. direct path) or multi-hop (i.e. relay path) capability for data Compliance
distribution to extend the network range to at least six (6)
thousand metres in open terrain.
2.2.5.3.1.0-14 The ISS-S communications network must be able to relay Mandatory ISS-S N/A Description of Test Yes TPS-1620
voice communications a minimum of 2 radio hops for Voice Compliance
COI extension.
2.2.5.3.1.0-15 The ISS-S communications network should be able to relay Rated ISS-S N/A Description of Test Yes TPS-2438
voice communications a minimum of 4 radio hops. Compliance
2.2.5.3.1.0-16 The relay of any single service must not consume all available Mandatory ISS-S N/A Description of Analysis - and - Test No TPS-1621
bandwidth in the relaying ISS-CS. Compliance
2.2.5.3.1.0-17 The ISS-S communications network must be able to Mandatory ISS-S N/A Description of Analysis - and - Test No TPS-2120
automatically switch between known relay points in less than 4 Compliance
seconds as described in scenarios at Annex TBD - SAT (to
be based on WISELAB - relay transfer configuration 4).
Page 36 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.5.3.1.0-18 The ISS-S communications network should be able to Rated ISS-S N/A Description of Analysis - and - Test No TPS-4255
automatically switch between known relay points in less than 2 Compliance
seconds as described in scenarios at Annex TBD - SAT (to
be based on WISELAB - relay transfer configuration 4).
2.2.5.3.1.0-19 The ISS-S communications network should be able to Rated ISS-S N/A Description of Analysis - and - Test No TPS-816
automatically configure relay points for data services within 15 Compliance
seconds of beaconing from a new, previously unknown, node.
2.2.5.3.1.0-20 A minimum group of sixty (60) ISS-CS must be capable of Mandatory ISS-S N/A Description of Analysis No TPS-880
operating as a single ISS-S communications network for voice Compliance
and data where all nodes are within 1 radio hop (i.e. no relay).
2.2.5.3.1.0-21 A minimum group of thirty (30) ISS-CS must be capable of Mandatory ISS-S N/A Description of Test Yes TPS-1650
operating as a single ISS-S communications network for voice Compliance
and data where 66% of nodes are separated by 2 radio hops
(e.g., 3 sections separated by distance or terrain with relaying
between sections).
2.2.5.3.1.0-22 The ISS-S communications network must operate in open Mandatory ISS-S N/A Demonstration of Test No TPS-1658
terrain at a range of 2000 metres between two ground-based Function
ISS-CS devices using an intermediating ground-based ISS-CS
relaying node.
2.2.5.3.1.0-23 An ISS-S communications network of 10 ISS-CSs must Mandatory ISS-S N/A Description of Analysis - and - Test Yes TPS-3911
communicate voice and data with each other where suites are Compliance
separated in open terrain as a randomly distributed cluster two
thousand (2000) m in diameter and no suite is more than one
thousand (1000) metres from another suite.
2.2.5.3.1.0-24 An ISS-S communications network of 10 ISS-CSs should Rated ISS-S N/A Description of Analysis - and - Test Yes TPS-3913
communicate voice and data with each other where suites are Compliance
separated in open terrain as a randomly distributed cluster six
thousand (6000) m in diameter and no suite is more than two
thousand (2000) m from another suite.
2.2.5.3.1.0-25 An ISS-S communications network of 10 ISS-CSs must Mandatory ISS-S N/A Description of Analysis - and - Test Yes TPS-3914
communicate voice and data with each other in urban terrain Compliance
where suites are deployed in a randomly distributed cluster five
hundred (500) metres in diameter.
2.2.5.3.1.0-26 An ISS-S communications network of 10 ISS-CSs should Rated ISS-S N/A Description of Analysis - and - Test Yes TPS-3915
communicate voice and data with each other in urban space Compliance
where suites are deployed in a randomly distributed cluster
two thousand (2000) metres in diameter.
2.2.5.3.2 Range Extension Information Only TPS-817
2.2.5.3.2.1 Integral Soldier Range Information Only TPS-2627
Extension
2.2.5.3.2.1.0-1 It is expected that the ISS-CS support range extension through Information Only N/A TPS-4250
installation in an elevated platform.
2.2.5.3.2.1.0-2 It is expected that the ISS-CS have the capability to extend Information Only N/A TPS-4251
range with an antenna range extension kit.
2.2.5.3.2.2 Additional Range Extension Information Only TPS-2632
2.2.5.3.2.2.0-3 The ISS-S communications, when placed in an aerial platform, Mandatory ISS-S Options: Description of Contractor's Choice No TPS-820
must provide a communications relay range of 40 kilometres 1) use a fixed tower if vendor has access to a Compliance
or more between two (2) ground-based nodes. suitable location or if a government agency has
access to one (e.g. CRC)
2) use an aerostat in cooperation with DLCSPM
2.2.5.4 Network Information Only TPS-265
2.2.5.4.1 Data Network Convergence Information Only TPS-881
2.2.5.4.1.0-1 A peer network of quantity ten (10) ISS-S Communications Mandatory ISS-S N/A Description of Analysis - and - Test No TPS-882
devices must permit data to be transmitted between all Compliance
devices, including relays, within 60 seconds from power on of
all devices.
2.2.5.4.1.0-2 The ISS-CS must be capable of choosing an alternate data Mandatory ISS-S N/A Description of Test No TPS-883
network path within ten (10) seconds of an established path Compliance
being broken.
2.2.5.4.2 System Access Time Information Only TPS-269
2.2.5.4.2.0-1 The ISS-CS must provide voice service within 250 milliseconds Mandatory ISS-S N/A Description of Test No TPS-884
following a push-to-talk action by the soldier. Compliance
2.2.5.4.3 Addressing Information Only TPS-270
2.2.5.4.3.0-1 The ISS-CS must integrate with Internet Protocol version 4 Mandatory ISS-S N/A Certificate of Contractor's Choice No TPS-826
addressing (IETF RFC 794, 1519). Compliance or
Description of
Compliance
2.2.5.4.3.0-2 The ISS-S must provide mechanisms to prevent assignment Mandatory ISS-S N/A Description of Contractor's Choice No TPS-2150
of duplicate Internet Protocol addresses. Compliance
2.2.5.4.3.0-3 The ISS-CS should detect duplicate Internet Protocol Rated ISS-S N/A Description of Contractor's Choice No TPS-2151
addresses and automatically reconfigure a new non-duplicate Compliance
Internet Protocol address to any conflicting nodes.
2.2.5.4.3.0-4 The ISS-S must provide unique addresses for a fleet of 10,000 Mandatory ISS-S N/A Description of Analysis No TPS-825
ISS-S kits, including all devices in the ISS-S. Compliance
2.2.5.4.4 Routing Information Only TPS-885
2.2.5.4.4.0-1 The ISS-CS should support dynamic inter-domain routing with Rated ISS-S Crown would need to provide reference platforms Description of Contractor's Choice No TPS-2156
other networks, including supporting vehicles integral to the for inter-operation Compliance
section, platoon and company.
2.2.5.4.5 Transport Enhancement Information Only TPS-886
Page 37 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.5.4.5.0-1 Data sent over lossy radio channels is subject to throttling and Information Only n/a N/A No TPS-2157
failure effects caused by errors and variations in the channel.
The use of transport enhancement can improve user
throughput.
2.2.5.5 Radio Information Only TPS-271
2.2.5.5.1 Transmitted Power Information Only TPS-3896
2.2.5.5.1.0-1 The ISS-CS primary power mode must be used to support all Mandatory ISS-S NA Description of Contractor's Choice Yes TPS-5163
of the TPS functional requirements. Compliance
2.2.5.5.1.0-2 The ISS-CS should provide selectable or adaptive radio output Rated ISS-S N/A Description of Test No TPS-4069
power levels. Compliance
2.2.5.5.1.0-3 The ISS-CS should provide a lower power mode to reduce Rated ISS-S N/A Description of Test No TPS-4070
power by 6 dB or more. Compliance
2.2.5.5.1.0-4 A quantity of ten (10) ISS-CS must operate concurrently, while Mandatory ISS-S N/A Description of Contractor's Choice Yes TPS-5195
using voice and data services, in a three (3) metre by three (3) Compliance
metre space without damaging any of the ISS-CS devices.
2.2.5.5.2 Transmission range Information Only TPS-272
2.2.5.5.2.0-1 The ISS-CS must operate at a range of 500 metres between Mandatory ISS-S Should Crown define / provide the urban test Description of Analysis - and - Test Yes TPS-890
two ISS-CS devices in an urban environment as described in environment? Compliance
scenarios at Annex TBD - SAT. I believe we absolutely have to define and
"provide" the urban test environment. Making
any open RF range test repeatable is challlenging.
Doing it in an urban environment will be even
more so.
2.2.5.5.2.0-2 The ISS-CS must provide point-to-point communications Mandatory ISS-S N/A Description of Test No TPS-1652
between two unobstructed (open space, line of sight) Compliance
dismounted soldiers separated by a distance of 1000 metres
while sustaining both voice and data at 160 kilobits per second
of internet protocol (IP) data throughput after error correction.
2.2.5.5.2.0-3 The ISS-CS should provide point-to-point communications Rated ISS-S Can vendor find a suitable piece of terrain? Description of Test No TPS-1653
between two unobstructed (open space, line of sight) Should Suffield test range be made available? Compliance
dismounted soldiers separated by a distance of 2000 metres
while sustaining voice and data at 80 kbps kilobits per second
of internet protocol (IP) data throughput after error correction.
2.2.5.5.2.0-4 The ISS-CS must have positive link margin of 30 dB to sustain Mandatory ISS-S N/A Description of Analysis - and - Test No TPS-1655
transmission through an obstacle producing an attenuation of Compliance
xx at a range of 300m.
2.2.5.5.2.0-5 The ISS-CS must have positive link margin of 30 dB to sustain Mandatory ISS-S N/A Description of Analysis - and - Test No TPS-4256
transmission through 2 obstacles producing an attenuation of Compliance
xx where the 2 obstacles are separated by 5 m and the ISS-
CSS devices are separated by 5.5 m.
2.2.5.5.2.0-6 The ISS-CS must meet all range requirements (i.e. no Mandatory ISS-S NA Description of Contractor's Choice No TPS-1657
reduced range performance) when worn by a standing soldier Compliance
in full combat load.
2.2.5.5.3 Frequencies / Frequency Information Only TPS-275
Planning
2.2.5.5.3.0-1 The ISS-CS is expected to operate in a single operating Information Only TPS-5196
frequency band at any point in time.
2.2.5.5.3.0-2 The ISS-CS must meet all TPS performance requirements Mandatory ISS-S Description of Contractor's Choice No TPS-5162
within the mandatory 225-450 MHz UHF band (i.e. Primary Compliance
Operating Band) using common frequency channels having a
fixed channel size.
2.2.5.5.3.0-3 The ISS-CS must provide a minimum of 20 orthogonal Mandatory ISS-S Operating licenses for this band to support any Description of Test No TPS-893
frequency channels (meeting the user service performance testing Compliance
requirements outlined in this specification) within the 225 - 450
MHz band.
2.2.5.5.3.0-4 The ISS-CS should provide a minimum of 40 orthogonal Rated ISS-S Operating licenses for this band to support any Description of Test No TPS-4071
frequency channels (meeting the user service performance testing Compliance
requirements outlined in this specification) within the 225 - 450
MHz band.
2.2.5.5.3.0-5 In addition to the 225 - 450 MHz band, the ISS-CS should also Rated ISS-S Operating licenses for these bands to support any Description of Test No TPS-894
operate in at least one of the following frequency bands, testing Compliance
providing a minimum of 10 orthogonal frequency channels:
• 902-928 MHz;
• 1210-1415 MHz;
• 2360-2473 MHz.
2.2.5.5.3.0-10 If the ISS-CS operates in the 2360 to 2473 MHz frequency Mandatory ISS-S N/A Description of Test No TPS-5200
band, the ISS-CS must: Compliance
• provide communications capacity for concurrent reception of
two independent voice networks and for transmission on either
voice network when selected; and
• operate within RADHAZ limits defined in this specification.
Page 38 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.5.5.3.0-11 If the ISS-CS operates in the 2360 to 2473 MHz frequency Mandatory ISS-S N/A Description of Test No TPS-5201
band, the ISS-CS communications network must: Compliance
• support a minimum of 5 concurrent, non-overlapping voice
networks located within one square kilometre for dismounted
close combat operations.
• distribute data and voice to all network-reachable ISS-S
nodes subscribed to a defined COI.
• provide single hop (i.e. direct path) or multi-hop (i.e. relay
path) capability for data distribution to extend the network
range to at least two (2) thousand metres in open terrain with
data throughput equivalent or greater than data throughput
measured in the Primary Operating Band.
• using a network of 10 ISS-CS, communicate voice and data
with each other where suites are separated in open terrain as
a randomly distributed cluster two thousand (2000) m in
diameter and no suite is more than one thousand (1000)
metres from another suite.
• using a network of 10 ISS-CS, communicate voice and data
with each other in urban terrain where suites are deployed in a
randomly distributed cluster five hundred (500) metres in
diameter.
2.2.5.5.4 Spectrum Access Flexibility Information Only TPS-3923
2.2.5.5.4.0-1 Where spectrum availability is limited within a frequency band, Rated ISS-S N/A Description of Analysis No TPS-3924
the ISS-CS should have the capability to be programmed to Compliance
operate with a reduced occupied bandwidth while providing a
reduced level of service for 5 or more voice channels, blue PA
data, and 10 kilobits per second (point-to-point).
2.2.5.5.4.1 Spectrum Efficiency Information Only TPS-4072
2.2.5.5.4.2 Normal occupied bandwidth Information Only TPS-4073
2.2.5.5.4.2.0-1 The maximum occupied bandwidth in the 225 - 450 MHz Mandatory ISS-S Experimentation license for use of spectrum Description of Test No TPS-4075
frequency band must be no more than 5 MHz. Compliance
2.2.5.5.4.2.0-2 The maximum occupied bandwidth in the 225 - 450 MHz Rated ISS-S Experimentation license for use of spectrum Description of Test No TPS-4252
frequency band should be less than 5 MHz. Compliance
2.2.5.5.4.2.0-3 The maximum occupied bandwidth in the 902 - 928 MHz Rated ISS-S Experimentation license for use of spectrum Description of Test No TPS-3926
frequency band should be no more than 1.8 MHz. Compliance
2.2.5.5.4.2.0-4 The maximum occupied bandwidth in the 1210-1415 MHz Rated ISS-S Experimentation license for use of spectrum Description of Test No TPS-3927
frequency band should be no more than 2.5 MHz. Compliance
2.2.5.5.4.2.0-5 The maximum occupied bandwidth in the 2360-2473 MHz Rated ISS-S Experimentation license for use of spectrum Description of Test No TPS-3928
frequency band should be no more than 5 MHz. Compliance
2.2.5.5.5 Configuration Persistence Information Only TPS-278
2.2.5.5.5.0-1 The ISS-CS must store its radio and network configuration so Mandatory ISS-S N/A Description of Demo No TPS-879
that its devices can be powered off and restarted without Compliance
requiring a new configuration.
2.2.5.5.5.0-2 The ISS-CS must retain its radio and network configuration for Mandatory ISS-S N/A Description of Test No TPS-1649
a period of not less than 5 minutes upon removal of ISS-S Compliance
batteries.
2.2.5.5.6 User Configurable Functions Information Only TPS-280
2.2.5.5.6.0-1 The ISS-CS parameters should be controlled using the Battle Rated ISS-S N/A Description of Demo No TPS-897
Management Software. Compliance
2.2.5.5.6.0-2 The ISS-CS must provide a user control to change voice COI. Mandatory ISS-S N/A Description of Demo No TPS-4257
Compliance
2.2.5.5.6.0-3 The ISS-CS must provide a volume control for adjusting audio Mandatory ISS-S N/A Description of Demo No TPS-4258
output levels. Compliance
2.2.5.5.7 Radio Device Interfaces Information Only TPS-281
2.2.5.5.7.0-1 The ISS-CS must be compatible with one or more of the Mandatory ISS-S N/A Certificate of Contractor's Choice No TPS-4259
following interfaces: Compliance or
• IEEE 802.3 - Ethernet; Description of
• Universal Serial Bus version 2.0 - serial communications. Compliance
2.2.5.5.7.0-2 The ISS-CS must provide an interface to make voice inputs Mandatory ISS-S N/A Description of Inspection No TPS-2646
and outputs available to the ISS-S Audio Display. The ISS-S Compliance
Audio Display is defined in TPS-94.
2.2.5.5.8 Radio Antennas Information Only TPS-282
2.2.5.5.8.0-1 The ISS-CS must include an antenna. Mandatory ISS-S N/A Visual Inspection Inspection No TPS-903
2.2.5.5.8.0-2 The ISS-CS radio antenna must be interchangeable without Mandatory ISS-S N/A Description of Demo No TPS-2167
requiring special tools. Compliance
2.2.5.5.9 Software-Defined Radio Information Only TPS-906
2.2.5.5.9.0-1 The ISS-CS is expected to operate using a single radio Information Only ISS-S N/A TPS-5202
waveform at run-time.
2.2.5.5.9.0-2 The ISS-CS must use a software-defined radio that permits Mandatory ISS-S N/A Description of Analysis No TPS-907
functional upgrades and technology insertion without modifying Compliance
hardware or interfaces to the radio.
2.2.5.5.9.0-3 The ISS-CS must permit replacement, in whole or part, of the Mandatory ISS-S N/A Description of Contractor's Choice No TPS-832
entire physical layer software, including layer elements, for Compliance
enhanced performance without changing the physical device
and associated interfaces.
2.2.5.5.9.0-4 The ISS-CS must permit replacement, in whole or part, of the Mandatory ISS-S N/A Description of Contractor's Choice No TPS-4260
entire media access layer software, including layer elements, Compliance
for enhanced performance without changing the physical
device and associated interfaces.
2.2.5.5.9.0-5 The ISS-CS should provide a configurable function for Rated ISS-S N/A Description of Contractor's Choice No TPS-5203
modifying digital filters (e.g. spectral masks) of transmitted and Compliance
received radio frequency signals.
2.2.5.5.10 Codec Information Only TPS-277
Page 39 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.5.5.10.0-1 The ISS-CS should permit the replacement of radio voice Rated ISS-S N/A Description of Contractor's Choice No TPS-896
codec without changing radio hardware and interfaces to the Compliance
radio.
2.2.5.6 LCSS Compatibility Information Only TPS-2650
2.2.5.6.1 LCSS Radio Information Only TPS-2651
2.2.5.6.1.0-1 The ISS-S is expected to interface to the AN/PRC-152, Crown ISS-S Provide reference radios at a Crown facility with a TPS-1617
AN/PRC-148, and AN/PRC-117 as LCSS radios to COMSEC account
dismounted commanders for communications with the Land Provide reference radios to winning contractor if
Command Support System. that company has a COMSEC account that is
suitable
NOTE: would require 2xeach reference radio for
compatability/interoperability testing for the vendor
to complete development and tests.
May need to GFE CNR(P) and/or connector
spec/ICD.
2.2.5.6.1.0-2 It is expected that the LCSS GFE radio be EMC/EMI Information Only ISS-S same as TPS-1617 TPS-1618
compatible with the ISS-S as defined in the EMC/EMI section
of this TPS.
2.2.5.6.1.0-3 It is expected that the LCSS GFE radio be integrated with the Information Only ISS-S same as TPS-1618 TPS-2653
ISS-S audio display as defined in the audio display section of
this TPS.
2.2.5.6.2 Grade of Service Information Only TPS-3929
2.2.5.6.2.0-1 The ISS-S (i.e. computer network function) should support Rated ISS-S N/A Description of Demo No TPS-878
Differentiated Services in accordance with IETF RFC 2474 for Compliance
integration with the Land Command Support System (LCSS).
2.2.6 Power and Data Information Only TPS-98
Infrastructure
2.2.6.1 General Information Only TPS-4446
2.2.6.1.0-1 The ISS-S must be able to complete eight (8) hours of Mandatory ISS-S Description of Test No TPS-4509
continuous operation without recharge or replacement of its Compliance
power source(s) where the eight (8) hours of operation are as
per Table 2 - ISS-S Battlefield Day Usage Profile (dividing all
time for each task by three (3)) of the ISS-S Mission Profile &
Operational Mode Summary Annex.
2.2.6.1.0-2 The ISS-S should be able to complete twenty-four (24) hours Rated ISS-S Description of Test No TPS-4510
of continuous operation without recharge or replacement of its Compliance
power source(s), where the twenty-four (24) hours of operation
is as per Table 2 - ISS-S Battlefield Day Usage Profile of the
ISS-S Mission Profile & Operational Mode Summary Annex.
2.2.6.2 Power Sources Information Only TPS-4500
2.2.6.2.0-1 The ISS-S must be able to operate using rechargeable Mandatory ISS-S Description of Contractor's Choice No TPS-4449
batteries and non-rechargeable batteries. Compliance
2.2.6.2.0-2 The ISS-S rechargeable batteries must be manufactured and Mandatory ISS-S Description of Contractor's Choice No TPS-5036
available from at least two different vendors. Compliance
2.2.6.2.0-3 The ISS-S non-rechargeable batteries must be manufactured Mandatory ISS-S Description of Contractor's Choice No TPS-5208
and available from at least two different vendors. Compliance
2.2.6.2.0-4 The ISS-S should require as few battery types as possible. Rated ISS-S Description of Contractor's Choice No TPS-5173
Compliance
2.2.6.2.0-5 The ISS-S User must not require any tools to replace ISS-S Mandatory ISS-S Description of Demo No TPS-5209
batteries. Compliance
2.2.6.2.0-6 The ISS-S User must be capable of changing batteries without Mandatory ISS-S Description of Demo No TPS-5179
the system shutting-down or rebooting, and without the loss of Compliance
data.
2.2.6.2.0-7 After 200 charge/discharge cycles, the ISS-S rechargeable Mandatory ISS-S Description of Contractor's Choice No TPS-4511
power sources must be able to store a charge of 80% of their Compliance
rated capacity in amp-Hr.
2.2.6.3 Connectors and Cables Information Only TPS-4748
2.2.6.3.0-1 One common set of ISS cables must support all the ISS-S Mandatory ISS-S Description of Contractor's Choice No TPS-5337
conceptual loads as defined in Annex ZZ while meeting all ISS- Compliance
S requirements.
2.2.6.3.0-2 The ISS-S User must not require any tools to mate and Mandatory ISS-S Description of Demo No TPS-5176
unmate ISS-S connectors. Compliance
2.2.6.3.0-3 The ISS-S connectors must be cleanable without specialised Mandatory ISS-S Description of Demo No TPS-4752
tooling. Compliance
2.2.6.3.0-4 The ISS-S connectors must have a lifetime of 2 000 mating Mandatory ISS-S Description of Analysis No TPS-4754
cycles or more without requiring any maintenance. Compliance
2.2.6.3.0-5 The ISS-S connectors should have a lifetime of more than 2 Rated ISS-S Description of Analysis No TPS-4755
000 mating cycles without requiring maintenance. Compliance
2.2.6.3.0-6 The connector at the Audio Display Control Box connecting to Mandatory ISS-S Description of Test No TPS-5336
the Audio Display Headset must include a breakaway. Compliance
breakaway force To Be Determined.
2.2.6.3.0-7 Connecting a cable to the wrong device must not cause any Mandatory ISS-S Description of Contractor's Choice No TPS-5177
physical damage to the ISS-S. Compliance
2.2.6.3.0-8 The ISS-S computer must continue to operate normally when Mandatory ISS-S Description of Demo No TPS-5178
a physical device (excluding batteries) is being connected to it Compliance
or being disconnected from it.
2.2.6.3.0-9 The ISS-S must include a removable protective cover for every Mandatory ISS-S Description of Inspection No TPS-5382
connector that is located on an ISS-S physical device. Compliance
2.2.6.4 External interfaces Information Only TPS-4801
2.2.6.4.0-1 The ISS-S should have a USB interface. Rated ISS-S USB spec Description of Contractor's Choice No TPS-4909
Compliance
2.2.6.4.0-2 The ISS-S should have an Ethernet interface. Rated ISS-S IEEE 802.3 Description of Contractor's Choice No TPS-4911
Compliance
Page 40 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.6.4.0-3 The ISS-S must be able to physically connect the AN/PAS-503 Mandatory ISS-S GFE and ICD: Description of Demo No TPS-4486
CORAL-CR-C HHTI GFE to the ISS-S. AN/PAS-503 CORAL-CR-C HHTI Compliance
2.2.7 Sensor Information Only TPS-99
2.2.7.1 Digital Camera Information Only TPS-4970
2.2.7.1.0-1 The ISS-S should be able to import pictures to the ISS-S Rated ISS-S Description of Demo No TPS-4795
computer in one of two ways: Compliance
• Interface with commercial digital camera; or
• Include an integrated digital camera within the ISS-S.
2.2.7.1.0-2 If TPS-4795 is met by interfacing with a commercial digital Rated ISS-S Description of Demo No TPS-5323
camera, the ISS-S should be able to import still imagery and Compliance
motion imagery from at least three (3) commercially available
cameras from different manufacturers.
2.2.7.1.0-3 If TPS-4795 is met by integrating a digital camera within the Rated ISS-S Description of Demo No TPS-5324
ISS-S, the integrated digital camera should have the following Compliance
characteristics:
• Digital zoom of at least x4;
• Still imagery resolution of at least 640 pixels by 480 pixels;
• Motion imagery resolution of at least 320 pixels by 240 pixels;
• Capture Audio while recording motion imagery;
• Frame rate of at least 15 frames per second at a resolution
of 320 pixels by 240 pixels;
• A built-in flash;
• The ability to enable and disable the flash;
• An automatic picture taking mode (point and shoot);
• The ability to disable all light emissions;
• The ability to disable all emitted sounds; and
• An auto off (i.e. shutdown) function
2.2.7.2 CORAL-CR-C Information Only TPS-4976
2.2.7.2.0-1 An entity generated on the map by the ISS-S when using the Mandatory ISS-S Description of Demo Yes TPS-5325
CORAL-CR-C must be accurately geo-referenced. Compliance
2.2.7.2.0-2 The ISS-S must be capable of displaying the MGRS 10 grid Mandatory ISS-S Description of Demo Yes TPS-5327
reference with UTM map coordinates of an entity lased by the Compliance
CORAL-CR-C.
2.2.8 System Management Information Only TPS-104
2.2.8.0-1 System Management (SM) includes all the network Information Only TPS-1037
administration background functions that are required to
enable the main BMS and communication functions to work,
including network management and configuration, individual
ISS-S software and devices configuration, etc.
2.2.8.0-2 Every ISS-S user is to be given a role, with associated Information Only TPS-4762
administration privileges.
ISS-S identifies three different roles:
• Basic User;
• System Administrator;
• System Executive and Planning (SEP).
The Basic User role is to be granted to all ISS-S users. The
System Administrator is going to be either a Platoon level
asset (infantryman with signals training), a Company Asset
(Signaller Master Corporal) or a first or second line maintainer.
The System Administrator is also using an ISS-S kit. The SEP
is typically the Battalion Signal Officer, typically at the rank of
Lt or Capt, or any person that needs network planning
capabilities.
2.2.8.0-3 The Basic User system management capabilities are limited to Information Only TPS-1038
monitoring the ISS-S and the network and installing
configurations using a USB device.
System Administrator functions include the distribution of
configuration parameters, debugging and network health
monitoring. SEP functions include configuration parameters
preparation, network planning, range card template
preparation, BMS settings configuration, etc.
The SEP is expected to perform his planning on a specialised
planning software, accessible through a CF-31 or Standalone
PC. The software is identified here as the SEP suite.
2.2.8.0-4 Using the SEP Suite, the SEP is responsible to create an ISS Information Only TPS-1039
Network Plan for a given operation. It is expected that the ISS
Network Plan will take the form of Configuration Files such that
System Administrators or other qualified personnel can load
them on the ISS-S of their respective Basic Users.
Considering that the SEP is a Bn/Battle Group asset, he/she is
to create an ISS Network Plan for four Coys within this
Bn/Battle Group. That translates into more than 600 ISS-S. It
is important that the concept of Configuration Files offers
flexibility and simplicity for the SEP, the Basic User and the
System Admin. Also, it is expected that the ISS Network Plan
be available in human readable format. As part of the ISS
Network Plan, the SEP will create COIs to which services
(Voice, Data or Blue PA) will be assigned and network
resources (frequencies, channels, time slots, etc...) will be
allocated. It is expected that every ISS-S will be initially
configured from a blank state with the possibility to reconfigure
once deployed. It is expected that a Basic User is to have the
flexibility to join and leave any available COIs.
2.2.8.1 System Executive and Information Only TPS-2962
Planning (SEP) Suite
Page 41 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.8.1.0-1 The SEP Suite must be accessible only to Users with SEP Mandatory SEP-Suite Description of Demo No TPS-3018
access privileges. Compliance
2.2.8.1.0-2 The SEP Suite must be installable and executable on a CF-31 Mandatory SEP-Suite CF-31 Description of Demo No TPS-3043
laptop, which is its only expected mode of operation. Compliance
2.2.8.1.1 Communication Network Information Only TPS-2966
Planning
2.2.8.1.1.1 General Information Only TPS-5361
2.2.8.1.1.1.0-1 A Communications Electronics Operating Instruction (CEOI) Information Only TPS-5367
describes in human language the various configuration
parameters used in the communication plan.
2.2.8.1.1.1.0-2 The SEP Suite must include a Communication Network Mandatory SEP-Suite Description of Demo No TPS-4112
Planning (CNP) tool. Compliance
2.2.8.1.1.1.0-3 The CNP must provide the capability to configure all Mandatory SEP-Suite Description of Demo Yes TPS-3014
parameter settings required for proper configuration of the ISS- Compliance
S nodes.
2.2.8.1.1.1.0-4 The CNP must permit the SEP to plan and distribute an ISS Mandatory SEP-Suite Description of Demo Yes TPS-1816
Network Plan with all ISS-S devices starting from a blank state Compliance
(no IP address or User name) and achieving a fully operational
network where all ISS-S are capable of exchanging voice and
data over-the-air.
2.2.8.1.1.1.0-5 The CNP should have the capability to create a CEOI in Rated SEP-Suite CEOI Annex Format Description of Demo No TPS-1157
human readable format that captures all the configuration Compliance
parameters included in the ISS-S network plan.
2.2.8.1.1.1.0-6 The CNP should have the capability to extract CEOI Rated SEP-Suite Description of Demo No TPS-1968
information for selected sub-units. Compliance
2.2.8.1.1.1.0-7 The CNP should be capable of saving the CEOI and any sub- Rated SEP-Suite Description of Demo No TPS-4097
unit extracts. Compliance
2.2.8.1.1.1.0-8 The CNP should allow a previous communication plan to be Rated SEP-Suite Description of Demo No TPS-3041
modified and saved as a new communication plan. Compliance
2.2.8.1.1.2 Prepare ISS network plan Information Only TPS-2992
2.2.8.1.1.2.0-1 The CNP must identify which service among the following is Mandatory SEP-Suite Description of Demo Yes TPS-2998
associated to which COI: Compliance
• Blue PA;
• Data;
• Voice.
2.2.8.1.1.2.0-2 The CNP must allow the SEP to enter Frequencies and IP Mandatory SEP-Suite Description of Demo Yes TPS-1135
addresses and other required parameters based on imposed Compliance
constraints.
2.2.8.1.1.2.0-3 The CNP must allow the SEP to allocate network resources to Mandatory SEP-Suite Description of Demo Yes TPS-3002
COIs. Compliance
2.2.8.1.1.2.0-4 The CNP must allow the SEP to create and give unique Mandatory SEP-Suite Description of Demo No TPS-1139
names to all COIs in the ISS Network plan Compliance
2.2.8.1.1.2.0-5 The CNP must allow configuration of spare COIs. Mandatory SEP-Suite Description of Demo Yes TPS-3003
Compliance
2.2.8.1.1.2.0-6 If the communications network requires configurating relays, Mandatory SEP-Suite Description of Demo Yes TPS-2999
the CNP must allow for planning of relays. Compliance
2.2.8.1.1.2.0-7 The CNP must allow the SEP to assign network addresses to Mandatory SEP-Suite Description of Demo Yes TPS-3008
the communication devices. Compliance
2.2.8.1.1.2.0-8 The CNP must allow distribution of the ISS network plan to the Mandatory SEP-Suite Description of Demo Yes TPS-4930
individual ISS-S. Compliance
2.2.8.1.2 Map Distribution Information Only TPS-2969
2.2.8.1.2.0-1 The SEP suite must have the capability to import the maps Mandatory SEP-Suite Description of Demo Yes TPS-1818
defined in TPS-1921and distribute them to individual ISS-S. Compliance
2.2.8.1.3 Validation Plan Information Only TPS-2994
2.2.8.1.3.0-1 The CNP should identify network resource conflicts that are Rated SEP-Suite Description of Demo Yes TPS-3009
known to prevent the ISS Network to function. Compliance
2.2.8.1.4 ORBAT Information Only TPS-2996
2.2.8.1.4.0-1 The CNP should have the ability to create an ISS ORBAT Rated SEP-Suite Description of Demo Yes TPS-1162
based on a predefined list of positions that can include the Compliance
following groups:
• Platoon;
• Section;
• Detachment.
2.2.8.1.4.0-2 The ORBAT should be presented in a hierarchical format. Rated SEP-Suite GFI: Example of an ORBAT Description of Demo No TPS-2997
Compliance
2.2.8.1.4.0-3 The CNP should allow assignment of COIs based on the Rated SEP-Suite Description of Demo No TPS-3005
ORBAT. Compliance
2.2.8.1.4.0-4 The CNP should provide a way to ensure that all ORBAT Rated SEP-Suite Description of Demo No TPS-1140
entities are included in the ISS-S network plan. Compliance
2.2.8.1.4.0-5 The predefined list of positions should be capable of including Rated SEP-Suite Description of Demo No TPS-2936
at least 300 positions. Compliance
2.2.8.1.5 Alternate ISS Network Plan Information Only TPS-4929
2.2.8.1.5.0-1 The CNP should provide the capability of developing an Rated SEP-Suite Description of Demo No TPS-3004
alternate ISS Network Plan using a different part of the Compliance
frequency spectrum.
2.2.8.1.5.0-2 The CNP should have the capability to distribute the alternate Rated SEP-Suite Description of Demo No TPS-4936
ISS Network Plan using the same mean as for the main ISS Compliance
Network Plan.
2.2.8.1.5.0-3 The ISS-S User should have the ability to select an alternate Rated ISS-S Description of Demo No TPS-1064
communication plan saved on his system without having to Compliance
restart the system.
2.2.8.1.6 Battle Management Information Only TPS-2968
Software Configuration
2.2.8.1.6.1 Blue PA messages reporting Information Only TPS-1792
parameters
Page 42 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.8.1.6.1.0-1 The SEP Suite should provide the capability to configure the Rated SEP-Suite Description of Demo Yes TPS-3024
two functionality of Blue PA reporting specified in TPS-2587 Compliance
and TPS-4820.
2.2.8.1.6.1.0-2 The following Blue PA messages settings should be provided: Rated SEP-Suite Description of Demo Yes TPS-1793
• Time-Based Automation - ON/OFF; Compliance
• Time Interval;
• Distance-Based Automation - ON/OFF;
• Distance Interval.
2.2.8.1.6.1.1 Time-Based Automation Information Only TPS-1798
2.2.8.1.6.1.1.0-1 The Blue PA messages settings should allow the SEP Suite to Rated SEP-Suite Description of Demo No TPS-1799
configure whether or not Blue PA messages are sent after a Compliance
certain Time Interval has passed since the last Blue PA
message.
2.2.8.1.6.1.1.0-2 The default Time-Based Automation setting should be that Rated SEP-Suite Description of Demo No TPS-1800
Blue PA messages are sent after the Time interval has Compliance
passed.
2.2.8.1.6.1.2 Time interval Information Only TPS-1801
2.2.8.1.6.1.2.0-1 The SEP suite should allow for the configuration of the time Rated SEP-Suite Description of Demo No TPS-1802
interval in increments of 5 sec. starting at 5 sec. and up to at Compliance
least 1 min.
2.2.8.1.6.1.2.0-2 The Blue PA messages settings should provide a default value Rated SEP-Suite Description of Demo No TPS-1803
for the Time interval. Compliance
2.2.8.1.6.1.3 Distance-Based Automation Information Only TPS-1804
2.2.8.1.6.1.3.0-1 The Blue PA messages settings should allow the SEP Suite to Rated SEP-Suite Description of Demo No TPS-1805
configure whether or not Blue PA messages are sent after the Compliance
user has travelled a certain distance since the last Blue PA
message.
2.2.8.1.6.1.3.0-2 The default Distance-Based Automation setting should be that Rated SEP-Suite Description of Demo No TPS-1806
Blue PA messages are sent after the user has travelled Compliance
passed the Distance interval.
2.2.8.1.6.1.4 Distance Interval Information Only TPS-1807
2.2.8.1.6.1.4.0-1 The SEP suite should allow for the configuration of the Rated SEP-Suite Description of Demo No TPS-1808
distance interval in increments of 5 m starting at 5 m and up to Compliance
at least 50 m.
2.2.8.1.6.1.4.0-2 The Blue PA messages settings should provide a default value Rated SEP-Suite Description of Demo No TPS-1809
for the Distance interval. Compliance
2.2.8.2 SEP role Information Only TPS-2964
2.2.8.2.0-1 The SEP's access privileges must allow him access to the Mandatory SEP-Suite Description of Demo No TPS-1129
System Executive Planning (SEP) Suite. Compliance
2.2.8.2.0-2 The SEP must be able to create and save an ISS Network Mandatory SEP-Suite Description of Demo No TPS-1132
plan using the ISS Communication Network Planning (CNP) Compliance
tool.
2.2.8.3 System Administrator Role Information Only TPS-2965
2.2.8.3.0-1 The ISS-S should provide a System Administrator role. Rated ISS-S Description of Demo No TPS-4937
Compliance
2.2.8.3.0-2 System Administrator access privileges should be given to a Rated ISS-S Description of Demo No TPS-2982
User before he can access any System Administrator specific Compliance
function on an ISS-S.
2.2.8.3.0-3 In addition to specific System Administrator functions, the Rated ISS-S Description of Demo No TPS-1091
System Administrator should be able to perform all the Compliance
functions listed for the Basic User.
2.2.8.3.0-4 The System Administrator should be able to perform an Rated ISS-S Description of Demo No TPS-1109
automated network connectivity test on any COI. Compliance
2.2.8.3.0-5 The Automated network connectivity test should verify that Rated ISS-S Description of Demo No TPS-4938
data can be sent and received to and from all ISS-S registered Compliance
on the COI.
2.2.8.3.0-6 The System Administrator's Access privileges should include Rated ISS-S Description of Demo No TPS-1094
the ability to log into any ISS-S. Compliance
2.2.8.3.0-7 The System Administrator's Access privileges should give him Rated ISS-S Description of Demo No TPS-1098
permission to change all configuration parameters on any ISS- Compliance
S.
2.2.8.3.0-8 The System Administrator's Access privileges should give him Rated ISS-S Description of Demo No TPS-4796
permission to change the authentication information of the ISS- Compliance
S Basic User.
2.2.8.4 Basic User Role Information Only TPS-2963
2.2.8.4.0-1 The ISS-S User must have the capability to view a list of all Mandatory ISS-S Description of Demo No TPS-1055
COIs he can select. Compliance
2.2.8.4.0-2 The list of COIs must indicate their associated service types Mandatory ISS-S Description of Demo No TPS-2972
(Voice, Data or Blue PA). Compliance
2.2.8.4.0-3 The ISS-S User must have the ability to join and leave any COI Mandatory ISS-S Description of Demo Yes TPS-1058
from the list of COIs. Compliance
2.2.8.4.0-4 The ISS-S User must be able to view to which COIs he is a Mandatory ISS-S Description of Demo No TPS-1060
member. Compliance
2.2.8.4.0-5 The Basic User should have the capability to monitor data Rated ISS-S Description of Demo No TPS-1066
transfer progress. Compliance
2.2.8.5 Configuration Files Information Only TPS-4926
2.2.8.5.0-1 All parameters configured using the SEP suite should be Rated SEP-Suite Description of Demo Yes TPS-3015
distributed using Configuration files. Compliance
2.2.8.5.0-2 The CNP should allow distribution of the ISS network plan to Rated SEP-Suite Description of Demo No TPS-4931
the individual ISS-S by saving it in a Configuration File. Compliance
2.2.8.5.0-3 The SEP Suite should have the capability to transfer Rated SEP-Suite Description of Demo No TPS-4933
Configuration files to an external storage device. Compliance
2.2.8.5.0-4 The ISS-S should have the capability of transferring Rated ISS-S Description of Demo No TPS-1083
Configuration Files between the Main and External data Compliance
storage devices.
Page 43 of 44 Printed Thursday, 7, October, 2010
912309e0-0c0a-4859-b8e1-7178a7a149e1.xls
Applicable
Object Number Object Heading Object Text Requirement Type Systems GFE-GFI Evaluation Method Evaluation Criteria Verification Method SAT Verification Criteria ID
2.2.8.5.0-5 The Basic User should have the ability to configure his ISS-S Rated ISS-S Description of Demo No TPS-2977
using configuration files saved on his Main data storage. Compliance
2.2.8.5.0-6 The Basic User should be able to view the current Rated ISS-S Description of Demo No TPS-1081
Configuration file identifier and time-stamp. Compliance
2.2.8.5.0-7 SEP Suite and ISS-S should have the capability to distribute Rated ISS-S, SEP- Description of Demo No TPS-3033
Configuration files over-the-air. Suite Compliance
2.2.8.5.0-8 The ISS-S User should be able to review the configuration Rated ISS-S, SEP- Description of Demo No TPS-1103
settings included in Configuration Files, in human readable Suite Compliance
form, to verify completeness.
2.2.8.6 Application Management Information Only TPS-223
2.2.8.6.0-1 It should be possible to install new software or software Rated ISS-S Description of Demo No TPS-1199
versions on any ISS-S without having to send any device to a Compliance
contractor.
2.2.8.6.0-2 The SEP suite should provide a way to measure and analyse Rated SEP-Suite Description of Demo No TPS-1833
the total message traffic within COIs and provide traffic Compliance
analysis that can be reviewed at a static location to determine
operational status and isolate operational irregularities.
2.2.8.6.0-3 The ISS-S should allow the System Administrator to measure Rated ISS-S Description of Demo No TPS-4034
and analyse the total message traffic within COIs and provide Compliance
traffic analysis to determine operational status and isolate
operational irregularities.
2.2.8.7 Integrated Help Information Only TPS-5186
2.2.8.7.0-1 The SEP-Suite must include an Integrated Help function. Mandatory SEP-Suite Description of Demo No TPS-5205
Compliance
2.2.8.7.0-2 The SEP-Suite Integrated Help function must provide help Mandatory SEP-Suite Description of Demo No TPS-5181
information for every User function of the SEP-Suite. Compliance
2.2.8.7.0-3 When using the SEP-Suite Integrated Help function, the User Mandatory SEP-Suite Description of Demo No TPS-5187
must have the ability to save and print the help information. Compliance
Page 44 of 44 Printed Thursday, 7, October, 2010