Attachment 5 OBAA Topic Solicitation No. 8 - Goverment Specified Equipment.pdf

Attachment 5

5.1

Attachment 5: Government Furnished and Specified Equipment

The Government is requesting that the Offerors incorporate options to integrate either Government Furnished Equipment (GFE) or Government Specified Equipment. The following sections cover the specified equipment. The information provided is copyrighted under the respective owner of the materials provided here for reference. These contacts and data sheets are provided to assist Offerors in preparing proposals and should not be considered to in anyway be a Government release copyright, or any other legal rights, held by the owners of these materials.

GFE or GSE Information Index Pg.

Chemical Warfare Agent Sensor

Chemical Detector Module (Smiths Detection) Vendor Contact Information 5.1

CHEM PUCK Housing-ACORNS (U.S. ARMY) Government Contact Information 5.2

Radiological Sensor Spectral Radiation Monitor Air (SPM-AIR)

Fact Sheet 5.2 Line Drawing 5.3 SRM Air Power and Data Options 5.4 SRM Air Multi-Purpose Cable Wiring Diagram 5.5 SRM Air Data Protocol 5.6

Basic Chemical Sensor MultiRAE Pro PGM-6248 (MCB3-A3C1REU-P2N)

Model Sensor Composition 5.8 Monitor Remote Control Functions for MultiRAE 5.12

ATAK

Android Team Awareness Kit

USBP Sensor System Cursor-on-Target Implementation Guide 5.17 Gas/Vapor Chemical Identification Sensor

MX 908 – Contact Information 5.2 Liquid/Solid Chemical Identification Sensor

Pendar 10x – Contact Information 5.2 Bio-Threat Sensor

FLIR IBAC-1 5.2

Contact Information Sensor Vendors:

Smiths Detection-Chemical Detector Module Technical Point of Contact:

Keith Parnell +441923658203 Keith.Parnell@smithsdetection.com Legal Point of Contact:

Erica Ramos 1-667-201-3311 mailto:Keith.Parnell@smithsdetection.com mailto:Keith.Parnell@smithsdetection.com

Attachment 5

5.2

1-667-201-3311 Erica.Ramos@smiths-detection.com

CHEM PUCK Housing-ACORNS (U.S. ARMY) Please contact Colin Graham C-SRIP, JPEO-CBRN/RPI through the technology transfer office.

https://www.cbc.ccdc.army.mil/work-with-us/ usarmy.apg.ccdc-cbc.mbx.technical-outreach@mail.mil

908 (MX 908)

Primary POC – Jim Kane, jim.kane@908devices.com NDA / Legal POC – Kerstin Barr, kbarr@908devices.com Technical POC – Matt Aernecke, maernecke@908devices.com

Pendar (Pendar x10)

FLIR (IBAC-1)

Phone: +1-877-692-2120

Fact Sheet Spectral Monitor Air

The SRM-Air is a platform agnostic gamma and neutron search and identification system built for use on unmanned vehicles. It has been demonstrated on various unmanned aerial, ground, and underwater platforms. The SRM-Air can operate independently of the platform with stand-alone power, communications, and GPS. For certain applications it has been integrated into the vehicle. The SRM-Air has additional ruggedization over handheld systems for field use and a real time ATAK user interface.

Information SRM-Air Dimensions (cm) 21.1 x 5.6 x 3.6 Weight 689 g (24.3 ox) Gamma Material CsI Dose Rate Range Bkgd to 50 R/hr Display TAK on Phone Battery Type External Power Consumption < 1.0 Watt Shock Mounts Internal Wireless Output Bluetooth External Hard Connection Mesh Network Radio Communication – Wireless xBee Communication – Radio MPU-5 Housing Material Carbon Fiber

Information provided by Naval Information Warfare Center Pacific

Romain Blanchard, blanchard@pendar.com

Korte, Kristin,Kristin.Korte@flir.com mailto:Erica.Ramos@smiths-detection.com mailto:Erica.Ramos@smiths-detection.com https://www.cbc.ccdc.army.mil/work-with-us/ https://www.cbc.ccdc.army.mil/work-with-us/ mailto:usarmy.apg.ccdc-cbc.mbx.technical-outreach@mail.mil mailto:usarmy.apg.ccdc-cbc.mbx.technical-outreach@mail.mil mailto:jim.kane@908devices.com mailto:jim.kane@908devices.com mailto:kbarr@908devices.com mailto:kbarr@908devices.com mailto:maernecke@908devices.com mailto:maernecke@908devices.com mailto:safety@pendar.com mailto:safety@pendar.com

FILE DATE: 2020/10/13 FILE NAME: 0249850_REV-_SRM-Air Dimensions.dft55910 D SIZE - ASME Y14.100, REV A, 2/2019

SHDWG. NO. 1

A

B

C

D

A

B

C

D

12345678

8 7 6 5 4 3 10249850

SHEET 1 OF 1

56760

DR-019644

COGNIZANT CODE125

55910

DO NOT SCALE THIS DRAWING

INTERPRET DRAWING IN

ACCORDANCE WITH ASME Y14.100

PREPARED

PROJECT NUMBER

APPROVED

APPROVED

CHECKED

APPROVED FOR

BY DIRECTIONRELEASED DATE

NEXT ASSY USED ON

APPLICATION

NAVAL INFORMATION WARFARE CENTER PACIFIC

SAN DIEGO, CA 92152-5001

DRAWING NUMBERCAGE CODESIZE

SCALE: 1/1

D

THIRD ANGLE PROJECTION

SRM-Air Dimensions

0249850

S. QIU 2020/10/13

- REV

12 SH REVISION

STATUS DESCRIPTION APPROVEDDATEREVZONE

REVISION HISTORY

THIS DRAWING HAS BEEN GENERATED AND IS MAINTAINED BY A CAD SYSTEM. CHANGES SHALL ONLY BE

INCORPORATED AS DIRECTED BY THE COGNIZANT DESIGN ACTIVITY.

UNLESS OTHERWISE SPECIFIED:

DIMENSIONS ARE IN INCHES

BREAK ALL EDGES .03 MAX

REMOVE ALL BURRS

TOLERANCES ARE:

.XX ±.03 .XXX ±.010

ANGLES ±2°

FILLETS .03 MAX

SURFACE ROUGHNESS

INITIAL DRAWING 2020/10/13-

2020/10/13.

DISTRIBUTION STATEMENT D. DISTRIBUTION AUTHORIZED TO DOD AND DOD

CONTRACTORS ONLY; CRITICAL TECHNOLOGY;

REFER OTHER REQUESTS TO COMMANDING OFFICIER, NAVAL INFORMATION

WARFARE CENTER PACIFIC, SAN DIEGO, CA 92152-5001

DESTRUCTION NOTICE - DESTROY BY ANY METHOD THAT WILL PREVENT

DISCLOSURE OF CONTENTS OR RECONSTRUCTION OF THE DOCUMENT.

WARNING - THIS DOCUMENT CONTAINS TECHNICAL DATA WHOSE EXPORT IS

RESTRICTED BY THE ARMS EXPORT CONTROL ACT (TITLE 22, U.S.C. SEC.

2751 ET SEQ.) OR EXPORT ADMINISTRATION ACT OF 1979 (TITLE 50, U.S.C.,

APP. 2401 ET SEQ.), AS AMENDED. VIOLATORS OF THESE EXPORT LAWS ARE

SUBJECT TO SEVERE CRIMINAL PENALTIES. DISSEMINATE IN ACCORDANCE

WITH PROVISIONS OF DOD DIRECTIVE 5230.25.

NOTES

1. DRAWING FOR EXTERIOR DIMENSION REFERENCE ONLY

8.2082.008

.512

2.750

1.7501.181

SRM Air Power and Data Options:

Powering the SRM Air:

The SRM Air can be powered by one of two power connections, either being acceptable and valid. The non-Xbee radio versions of the SRM Air have a power requirement of up to 2.5W, while the Xbee radio version has a power requirement of up to 7.5W. Check the power and voltage ratings of the supply to be used before application. The two connection options available are as follows:

Option 1 (Recommended): DC power with a voltage of between 4-16V DC. Wiring for this option is labeled as “Aux Power” in the cable wiring diagram on the following page.

Option 2: USB powering of the device. This can be a standard 5V USB connection, so long as needed current ratings are met. USB C Power Delivery supplies are also supported, utilizing supplies that support either 15V, 9V, or 5V USB C PD power.

Note: Connecting “Aux Power” and a USB connection simultaneously is allowed. This may be the case, for example, if USB is needed to use the data connection, while power is to be applied from the aux power connection. In this instance, the SRM Air will negotiate power from the highest rated voltage of the two connections.

Data Paths of the SRM Air:

Multiple options for data connectivity are available from the SRM Air. These options are given to provide support for most any integration to robotic platforms. If none of the wired options are suitable for integration to an expected platform, there is an integrated wireless radio version of the SRM Air.

This option uses a commercial radio protocol (Xbee) that operates on an unlicensed radio band (915 Mhz).

Option 1 (Recommended): 100 Base-T Ethernet. Standard RJ45 plug.

Option 2 (Recommended): RS-232 UART serial communications. 115200 baud, 8-N-1 messaging protocol. TTL (3.3V) signal levels.

Option 3: Integrated Xbee radio option. Recommended connectivity option if 1 or 2 isn’t available.

Option 4: USB 2.0 data. Available as an option, but USB integration isn’t generally well supported over long distance data links.

Cabling:

All data and power connection options come out of the SRM Air’s multi-purpose cable. Cables will be designed to length to match user’s exact integration needs. Standard connection termination options such as RJ-45 plugs, for example, would be available, as well as support for custom terminations options if needed.

Phoenix M12

Aux Power

RJ45 Plug

USB C

SRM Air Multi-Purpose Cable Wiring Diagram

Serial

Notes:

1. Cable lengths for both Phoenix and breakouts are determined by customer needs.

2. All posible breakouts are shown. Breakouts utilized for a particular cable are determined by particular customer needs.

3. Wiring colors for ethernet shown are using TIA-568B color scheme, if TIA-568A is needed, wire accordingly.

BRN

WHT

GRY/PNK

RED/BLU

ORG/WHTETH TX+

ETH TX-

ETH RX+

ETH RX-

ORG

GRN/WHT

6GRN

GRY

VLT

UART TX

UART RX

UART GND

AUX PWR V+

AUX PWR GND

USB GND

USB V+

USB CC

USB D+

USB D-YLW

GRN

BLK

RED

BLU

PNK RED

BLK

SHIELD/BRAID

RED

YLW OR BLU

GRN

WHT

EXAMPLE: Cable lengths and terminations are designed to customer specific needs.

SRM Air Data Protocol

Overview The SRM Air communicates over various potential data links. The data is a stream of messages, each of which is of variable length, as defined below.

A connection to the SRM Air can be established directly to the device utilizing ethernet, serial, or USB connection options. The SRM Air Base Station can establish a remote connection to the SRM Air through long distance data links utilizing available system data multiplexers while onboard that remote system. The data from the Base Station can be relayed to local command and control display devices utilizing Bluetooth, USB, or wired/wireless Ethernet connection options.

Message Overview The stream of data to and from the SRM Air is divided into discrete messages that are framed as described below in the Message Framing section. The data section of the messages is encoded using the Google protocol buffers format (protobufs).

Messages are sent asynchronously. In particular, the remote system should be able to receive SRM Air messages as soon as the connection is established. The remote system may also send commands to the SRM Air at will. Each command will be acknowledged by the SRM Air.

Message Framing

Field Name Synch Token Length Protobuf Data Checksum Size (in bytes) 4 4 Variable 2

Table 1: Message format.

Messages transmitted to, or from, the SRM Air will have the format listed in Table 1. Each section is described below.

Synchronization Token A synchronization token forms the first four bytes of a message. It is always fixed to the hexadecimal sequence 0xA5A5A5A5. The main purpose of this field is to make sure that the stream is synchronized.

Length The length is a four-byte, little-endian field that indicates the length of the data field. This is necessary since the data field’s length can vary.

Protocol Buffer (protobuf) Data This is encoded according to the .proto standard using Google Protocol Buffers. This data is further described within the proto file.

Checksum The checksum is a two-byte field that is calculated via the 8-bit Fletcher algorithm. The purpose of the checksum is to verify the integrity of the rest of the data in the message. The checksum is calculated by applying the following algorithm across the length field, and the protocol buffer data field.

Note: the synchronization token is NOT considered in the checksum calculation.

uint8_t CK_A = 0, CK_B = 0 For(I=0;I<N;I++) CK_A = CK_A + Buffer[I]

CK_B = CK_B + CK_A

Listing 1: Checksum algorithm

MultiRAE Pro wireless portable multi-threat monitors for radiation and advanced chemical detection

Monitor-Only Configuration Includes:

• MultiRAE Pro monitor with sensors, pump, battery and wireless options as specified, and protective rubber boot, swivel belt clip and filter installed

• Continuous datalogging (6 months for 5 sensors @ 1-minute intervals)

• Travel charger / PC communications adapter

• Desktop charging / PC communications cradle

• Desktop Charger / PC communication cable

• AC adapter

• Calibration adapter

• Alkaline battery adapter

• Toolkit with Hex tool and Phillips screwdriver

• PID sensor cap removal tool

• PID zeroing filter (P/N: 008-3024-000)

• 3 spare external filters Optional Accessories / Confined Space and Calibration Kits Add:

• 6'' flexi probe with inlet adapter • Remote Sample Draw Kit (P/N: 008-3015-200)

• Quick Start Guide - 10" (26 cm) aluminum sample probe with replaceable filters,

• ProRAE Studio II Instrument Configuration and Data Management Software - 3 hydrophobic barrier filters

• Calibration and test certificate - 10' (3 m) self-coiling Teflon® tubing with Luer-style quick-connect filters

• 10 charcoal VOC filters for CO sensor • 4-gas mix (34L; 50% LEL, 18% O₂, 10 ppm H₂S, 50 ppm CO, w/ regulator)

Instrument ships in a "Pelican" case with custom foam that can also accommodate OR accessories and up to 4 gas cylinders and 3 regulators • 10 ppm OR 100 ppm Isobutylene gas (34L) with regulator

OR

• 4-gas mix (34L; 50% LEL, 18% O₂, 10 ppm H₂S, 50 ppm CO, w/ regulator)

• AND 10 ppm OR 100 ppm Isobutylene gas (34L) with regulator

Optional Guaranteed Cost of Ownership Program OR

• 4-year repair and replacement guarantee (available in North America only) • 4-gas mix (34L; 50% LEL, 18% O₂, 10 ppm H₂S, 50 ppm CO, w/ regulator)

• Annual maintenance service included • AND 10 ppm Isobutylene gas (34L) with regulator

• AND 100 ppm Isobutylene gas (34L) with regulator

Additional accessories, calibration systems, gas kits, individual gases and regulators are listed under Multi-Gas Accessories and

Multi-Gas Calibration sections of the Portable Pricing Guide

Pumped / 10.6 eV ppb PID / LEL / CO + H2S / O2 / Gamma / Li-ion / Non-Wireless

Unit only • • • •

Unit with Accessories / Confined Space and Calibration Kit (4-gas + 10 ppm Iso) • • • • • •

Unit with Access. / Conf. Space and Cal. Kit (4-gas + 10 ppm Iso + 100 ppm Iso) • • • • • •

Pumped / 10.6 eV ppb PID / LEL / CO + H2S / O2 / Gamma / Li-ion / Wireless

Unit only • • • • •

Unit with Accessories / Confined Space and Calibration Kit (4-gas + 10 ppm Iso) • • • • • • •

Unit with Access. / Conf. Space and Cal. Kit (4-gas + 10 ppm Iso + 100 ppm Iso) • • • • • • •

Pumped / 10.6 eV ppb PID / LEL / Cl2 / NH3 / O2 / Li-ion / Non-Wireless

Unit only • • •

Pumped / 10.6 eV ppb PID / LEL / Cl2 / NH3 / O2 / Li-ion / Wireless

Unit only • • • •

PART NUMBER List Price [USD $]

MCB3-A3C168E-020 5,937

PART NUMBER List Price [USD $]

MCB3-A3C168E-420 6,248

MCB3-A3C1REZ-420 6,993

MCB3-A3C1REZ-42M 7,862

MCB3-A3C1REZ-42N 8,111

MCB3-A3C1REZ-02M 7,551

MCB3-A3C1REZ-02N 7,800

PART NUMBER List Price [USD $]

PART NUMBER List Price [USD $]

MCB3-A3C1REZ-020 6,682

P

ID

S e n s o r

G a m m a S e n s o r

P u m p e d

W ir e le s s

L i-io n

R e c h a rg e a b le

A c c e s s o ri e s

K it

SERVICE PROGRAM OPTION PART NUMBER List Price [USD $] DESCRIPTION

4-Year Guaranteed Cost of Ownership SVC-PTC4-MC0 35% of instrument-only list price Extends warranty and covers replacement of all parts and sensors for 4 years from date of purchase

C a li b ra ti o n

K itListed below are some common configurations of the MultiRAE Pro monitors. For others, please use the Assemble-to-Order (ATO) Configuration Guide below.

Standard Sensor Configurations - MultiRAE Pro

MultiRAE Pro Monitors (Model PGM-6248)

Pricing subject to change without notice

Tel: 1.877.723.2878 | Fax: 1.408.952.8480

Email: raesales@raesystems.com | www.raesystems.com | Rev. 06/14 34

R

B CSA

M Model / Base Unit Price

3 MultiRAE Pro (PGM-6248) USD $ 3,774

AA

00 Empty Dummy sensor USD $ 0

PID Sensors

A1 PID, HR, 10.6 eV PID sensor (0.1 - 5,000 ppm; 0.1 ppm res.; 10.6 eV lamp) USD $ 642

A3 PID, ppb, 10.6 eV PID ppb sensor (10 ppb - 2,000 ppm; 10 ppb res.; 10.6 eV lamp) USD $ 859

Combustible NDIR Sensors

B4 CH4 NDIR, % LEL Combustible NDIR sensor (0-100% LEL CH4) USD $ 859

B5 CH4 NDIR, % Vol. Combustible NDIR sensor (0-100% Vol. CH4) USD $ 859

CO2 NDIR Sensors

B8 CO2 NDIR, HR Carbon dioxide (CO2) NDIR sensor (up to 50,000 ppm) USD $ 859

Electrochemical Sensors

01 H2S Hydrogen Sulfide (H2S) sensor (up to 100 ppm reading) USD $ 217

02 CO Carbon Monoxide (CO) sensor (up to 500 ppm reading) USD $ 217

03 SO2 Sulfur Dioxide (SO2) sensor USD $ 321

04 NO Nitric Oxide (NO) sensor USD $ 373

05 NO2 Nitrogen Dioxide (NO2) sensor USD $ 373

06 Cl2 Chlorine (Cl2) sensor USD $ 321

07 HCN Hydrogen Cyanide (HCN) sensor USD $ 435

08 NH3 Ammonia (NH3) sensor USD $ 435

09 PH3 Phosphine (PH3) sensor (up to 20 ppm reading) USD $ 435

0A ClO2 Chlorine Dioxide (ClO2) sensor USD $ 435

0D CO, HR Carbon Monoxide (CO) extended-range sensor (up to 2,000 ppm reading) USD $ 321

0E O2 Oxygen (O2) sensor USD $ 217

0F CO comp. H2 Carbon Monoxide (CO) sensor (H2-compensated) USD $ 373

0H CH3-SH Methyl Mercaptan (CH3-SH) sensor USD $ 538

0J EtO-A Ethylene Oxide (EtO-A) sensor (0 - 100 ppm; 1 ppm res.) USD $ 321

0K EtO-B Ethylene Oxide (EtO-B) sensor (0 - 10 ppm, 0.1 ppm res.) USD $ 321

0Q HCHO Formaldehyde (HCHO) sensor USD $ 745

0R CO+H2S Carbon Monoxide+Hydrogen Sulfide (CO+H2S) combo USD $ 435

0S Liquid O2 Liquid Oxygen sensor (0 o 30% Vol., 0.1% Vol. res.) USD $ 270

0U PH3-H Phosphine sensor (allows cross calibration) (0 to 20 ppm) USD $ 435

Select one option for Certification, Model, and one for each Feature Group (AA through H), to build a complete model number:

3 - D E - F

Sensor 4 Sensor 5 Wireless

MC B 3 - AA BB C D E - F G H

MultiRAE Pro Configuration Guide

MultiRAE Pro Monitors (Model PGM-6248) Certification of Intrinsic Safety

Battery Kits MultiRAE

Pro

Certification

(Always B)

Model

(Always 3) Sensor 1 Sensor 2 Sensor 3

High-Power Sensor (Options: Dummy / PID / Combust. NDIR / CO2 NDIR / Electrochemical Sensors Incl. CO+H2S Combo)

MC B AA BB C G H

* Note: If the instrument is ordered with fewer than five sensors, a dummy sensor must be installed in the empty sensor slot(s)

* Note: ClO2 and H2S sensors cannot be installed in the same instrument

** Note: NO and NH3 sensors cannot be installed in the same instrument

* Note: When ordering electrochemical sensors, please select the lower number first

* Note: NDIR % Vol.

combustible sensor must be accompanied by the catalytic % LEL sensor (installs in slot BB; see next page)

Pricing subject to change without notice

Email: raesales@raesystems.com | www.raesystems.com | Rev. 06/14 35

BB

00 Empty Dummy sensor USD $ 0

LEL Catalytic Bead Sensor

C1 LEL Combustible catalytic bead % LEL sensor USD $ 217

Electrochemical Sensors

01 H2S Hydrogen Sulfide (H2S) sensor (up to 100 ppm reading) USD $ 217

02 CO Carbon Monoxide (CO) sensor (up to 500 ppm reading) USD $ 217

03 SO2 Sulfur Dioxide (SO2) sensor USD $ 321

04 NO Nitric Oxide (NO) sensor USD $ 373

05 NO2 Nitrogen Dioxide (NO2) sensor USD $ 373

06 Cl2 Chlorine (Cl2) sensor USD $ 321

07 HCN Hydrogen Cyanide (HCN) sensor USD $ 435

08 NH3 Ammonia (NH3) sensor USD $ 435

09 PH3 Phosphine (PH3) sensor (up to 20 ppm reading) USD $ 435

0A ClO2 Chlorine Dioxide (ClO2) sensor USD $ 435

0D CO, HR Carbon Monoxide (CO) extended-range sensor (up to 2,000 ppm reading) USD $ 321

0E O2 Oxygen (O2) sensor USD $ 217

0F CO comp. H2 Carbon Monoxide (CO) sensor (H2-compensated) USD $ 373

0H CH3-SH Methyl Mercaptan (CH3-SH) sensor USD $ 538

0J EtO-A Ethylene Oxide (EtO-A) sensor (0 - 100 ppm; 1 ppm res.) USD $ 321

0K EtO-B Ethylene Oxide (EtO-B) sensor (0 - 10 ppm, 0.1 ppm res.) USD $ 321

0Q HCHO Formaldehyde (HCHO) sensor USD $ 745

0R CO+H2S Carbon Monoxide+Hydrogen Sulfide (CO+H2S) combo USD $ 435

0S Liquid O2 Liquid Oxygen sensor (0 o 30% Vol., 0.1% Vol. res.) USD $ 270

0U PH3-H Phosphine sensor (allows cross calibration) (0 to 20 ppm) USD $ 435

C

0 Empty Dummy sensor USD $ 0

Electrochemical Sensors

1 H2S Hydrogen Sulfide (H2S) sensor (up to 100 ppm reading) USD $ 217

2 CO Carbon Monoxide (CO) sensor (up to 500 ppm reading) USD $ 217

3 SO2 Sulfur Dioxide (SO2) sensor USD $ 321

4 NO Nitric Oxide (NO) sensor USD $ 373

5 NO2 Nitrogen Dioxide (NO2) sensor USD $ 373

6 Cl2 Chlorine (Cl2) sensor USD $ 321

7 HCN Hydrogen Cyanide (HCN) sensor USD $ 435

8 NH3 Ammonia (NH3) sensor USD $ 435

9 PH3 Phosphine (PH3) sensor (up to 20 ppm reading) USD $ 435

A ClO2 Chlorine Dioxide (ClO2) sensor USD $ 435

D CO, HR Carbon Monoxide (CO) extended-range sensor (up to 2,000 ppm reading) USD $ 321

E O2 Oxygen (O2) sensor USD $ 217

F CO comp. H2 Carbon Monoxide (CO) sensor (H2-compensated) USD $ 373

H CH3-SH Methyl Mercaptan (CH3-SH) sensor USD $ 538

J EtO-A Ethylene Oxide (EtO-A) sensor (0 - 100 ppm; 1 ppm res.) USD $ 321

K EtO-B Ethylene Oxide (EtO-B) sensor (0 - 10 ppm, 0.1 ppm res.) USD $ 321

Q HCHO Formaldehyde (HCHO) sensor USD $ 745

R CO+H2S Carbon Monoxide+Hydrogen Sulfide (CO+H2S) combo USD $ 435

S Liquid O2 Liquid Oxygen sensor (0 o 30% Vol., 0.1% Vol. res.) USD $ 270

U PH3-H Phosphine sensor (allows cross calibration) (0 to 20 ppm) USD $ 435

Select one option for Certification, Model, and one for each Feature Group (AA through H), to build a complete model number:

3 - D E - F

Sensor 4 Sensor 5 Wireless

Low-Power Sensor (Options: Dummy / Electrochemical Sensors Incl. CO+H2S Combo)

MC B 3 - AA BB C D E - F G H

MultiRAE Pro Configuration Guide

MC B AA BB C G H

MultiRAE

Pro

Certification

(Always B)

Model

(Always 3) Sensor 1 Sensor 2 Sensor 3 Battery Kits

High-Power Sensor (Options: Dummy / LEL / Electrochemical Sensors Incl. CO+H2S Combo)

* Note: ClO2 and H2S sensors cannot be installed in the same instrument

** Note: NO and NH3 sensors cannot be installed in the same instrument

* Note: When ordering electrochemical sensors, please select the lower number first

* Note: ClO2 and H2S sensors cannot be installed in the same instrument

** Note: NO and NH3 sensors cannot be installed in the same instrument

* Note: When ordering electrochemical sensors, please select the lower number first

Pricing subject to change without notice

Email: raesales@raesystems.com | www.raesystems.com | Rev. 06/14 36

D Low-Power Sensor (Options: Dummy / Electrochemical Sensors)

0 Empty Dummy sensor USD $ 0

Electrochemical Sensors

1 H2S Hydrogen Sulfide (H2S) sensor (up to 100 ppm reading) USD $ 217

2 CO Carbon Monoxide (CO) sensor (up to 500 ppm reading) USD $ 217

3 SO2 Sulfur Dioxide (SO2) sensor USD $ 321

4 NO Nitric Oxide (NO) sensor USD $ 373

5 NO2 Nitrogen Dioxide (NO2) sensor USD $ 373

6 Cl2 Chlorine (Cl2) sensor USD $ 321

7 HCN Hydrogen Cyanide (HCN) sensor USD $ 435

8 NH3 Ammonia (NH3) sensor USD $ 435

9 PH3 Phosphine (PH3) sensor (up to 20 ppm reading) USD $ 435

A ClO2 Chlorine Dioxide (ClO2) sensor USD $ 435

D CO, HR Carbon Monoxide (CO) extended-range sensor (up to 2,000 ppm reading) USD $ 321

E O2 Oxygen (O2) sensor USD $ 217

F CO comp. H2 Carbon Monoxide (CO) sensor (H2-compensated) USD $ 373

H CH3-SH Methyl Mercaptan (CH3-SH) sensor USD $ 538

J EtO-A Ethylene Oxide (EtO-A) sensor (0 - 100 ppm; 1 ppm res.) USD $ 321

K EtO-B Ethylene Oxide (EtO-B) sensor (0 - 10 ppm, 0.1 ppm res.) USD $ 321

Q HCHO Formaldehyde (HCHO) sensor USD $ 745

R CO+H2S Carbon Monoxide+Hydrogen Sulfide (CO+H2S) combo USD $ 435

S Liquid O2 Liquid Oxygen sensor (0 o 30% Vol., 0.1% Vol. res.) USD $ 270

U PH3-H Phosphine sensor (allows cross calibration) (0 to 20 ppm) USD $ 435

E

0 Empty Dummy sensor USD $ 0

Gamma Radiation Sensor

Z Gamma Gamma radiation sensor USD $ 1066

Electrochemical Sensors

1 H2S Hydrogen Sulfide (H2S) sensor (up to 100 ppm) USD $ 217

2 CO Carbon Monoxide (CO) sensor (up to 500 ppm) USD $ 217

3 SO2 Sulfur Dioxide (SO2) sensor USD $ 321

4 NO Nitric Oxide (NO) sensor USD $ 373

5 NO2 Nitrogen Dioxide (NO2) sensor USD $ 373

6 Cl2 Chlorine (Cl2) sensor USD $ 321

7 HCN Hydrogen Cyanide (HCN) sensor USD $ 435

8 NH3 Ammonia (NH3) sensor USD $ 435

9 PH3 Phosphine (PH3) sensor (up to 20 ppm reading) USD $ 435

A ClO2 Chlorine Dioxide (ClO2) sensor USD $ 435

D CO, HR Carbon Monoxide (CO) sensor (up to 2,000 ppm) USD $ 321

E O2 Oxygen (O2) sensor USD $ 217

F CO comp. H2 Carbon Monoxide (CO) sensor (H2-compensated) USD $ 373

H CH3-SH Methyl Mercaptan (CH3-SH) sensor USD $ 538

J EtO-A Ethylene Oxide (EtO-A) sensor (0 - 100 ppm; 1 ppm res.) USD $ 321

K EtO-B Ethylene Oxide (EtO-B) sensor (0 - 10 ppm, 0.1 ppm res.) USD $ 321

Q HCHO Formaldehyde (HCHO) sensor USD $ 745

R CO+H2S Carbon Monoxide+Hydrogen Sulfide (CO+H2S) combo USD $ 435

S Liquid O2 Liquid Oxygen sensor (0 o 30% Vol., 0.1% Vol. res.) USD $ 270

U PH3-H Phosphine sensor (allows cross calibration) (0 to 20 ppm) USD $ 435

F

0 Empty Non-wireless USD $ 0

4 W-900 Wireless, 900 MHz (built-in wireless modem) USD $ 311

B BLE Bluetooth Low Energy USD $ 200

W Wi-Fi Wi-Fi modem (built-in wireless modem) USD $ 300

P P2P P2P Communication capability USD $ 1,758

G Battery Options

1 Extended-duration (Li-ion) battery with alkaline adapter USD $ 166

2 Rechargeable (Li-ion) battery with alkaline adapter USD $ 114

3 Alkaline battery pack USD $ 0

H

0 Monitor only USD $ 0

2 Accessories / Conf. Space + 10 ppm Isobutylene Cal. Kit (with 1 regulator) USD $ 362

3 Accessories / Conf. Space + 100 ppm Isobutylene Cal. Kit (with 1 regulator) USD $ 362

9 Accessories / Conf. Space + 4-gas (LEL/O2/CO/H2S) Cal. Kit (with 1 regulator) USD $ 621

M Access. / Conf. Space + 4-gas (LEL/O2/CO/H2S) + 10 ppm Iso Cal. Kit (with 2 reg's) USD $ 869

B Access. / Conf. Space + 4-gas (LEL/O2/CO/H2S) + 100 ppm Iso Cal. Kit (with 2 reg's) USD $ 869

N Acc. / Conf. Sp. + 4-gas (LEL/O2/CO/H2S) + 10 ppm Iso + 100 ppm Iso Cal. Kit (3 reg's) USD $ 1,118

Select one option for Certification, Model, and one for each Feature Group (AA through H), to build a complete model number:

3 - D E - F

Sensor 4 Sensor 5 Wireless Battery Kits MultiRAE

Pro

Certification

(Always B)

Model

(Always 3) Sensor 1 Sensor 2 Sensor 3

MultiRAE Pro Configuration Guide

MC B AA BB C G H

Wireless Options

Kits and Accessories

MC B 3 - AA BB C D E - F G H

Low-Power Sensor (Options: Dummy / Gamma / Electrochemical Sensors)

* Note: ClO2 and H2S sensors cannot be installed in the same instrument

** Note: NO and NH3 sensors cannot be installed in the same instrument

* Note: When ordering electrochemical sensors, please select the lower number first

* Note: ClO2 and H2S sensors cannot be installed in the same instrument

** Note: NO and NH3 sensors cannot be installed in the same instrument

* Note: When ordering electrochemical sensors, please select the lower number first

* Note: Please contact Inside Sales department for P2P option

Pricing subject to change without notice

Email: raesales@raesystems.com | www.raesystems.com | Rev. 06/14 37

Technical Note TN-190 10/14

RAE Systems by Honeywell 877-723-2878 raesystems.com 1

MONITOR REMOTE CONTROL FUNCTIONS

FOR MULTIRAE

This technical note explains how instrument data can be transferred, and remote control functions implemented in real time, between a RAE Systems MultiRAE-family monitor and a personal computer via a HyperTerminal emulation (Point-To-Point, or P2P, protocol).

This P2P protocol is different from the wireless protocol used in the RAE Systems wireless networks. P2P and wireless capabilities are mutually exclusive and cannot be combined in one instrument.

What You’ll need In order to set up the P2P connection?

You’ll need the following:

• Hard wire or existing cable that shipped with the MultiRAE

• A TelNet client (communications software) in order to establish communication and to give the MultiRAE commands and display its readings and settings on the PC.

In order to operate when hardwired to a computer, the MultiRAE must be running Application Firmware v.1.14 and Sensor Firmware

1.04 or higher and configured for Point-To-Point communications.

This icon should appear at the top left of the MultiRAE’s display when it is running:

HyperTerminal to control serial devices isn’t included in some versions of Windows http://windows.microsoft.com/en-us/ windows/what-happened-hyperterminal#1TC=windows-7 In this case a version of HyperTerminal can be found on the Internet and can be downloaded for personal use.

• If you are using Windows 7, for example, you can copy the following two programs from a Window XP computer to run HyperTerminal:

1. hypertrm.dll

2. hypertrm.exe

Important! Both of these files must be in the same folder. Start the program by double-clicking hyprtrm.exe. Also note that this approach does not allow capturing a log of the session.

• You can also use one of many TelNet clients available online, including PuTTY, which is free (available at http://www.chiark.greenend.org.uk/~sgtatham/putty/).

CONNECTING THE MULTIRAE TO THE PC AND

IDENTIFYING A COM PORT

• Connect the MultiRAE to the computer using the special RS232 Travel Charger and its mini-USB to DB9 cable (the standard MultiRAE Travel Charger and mini-USB-to-USB PC communications cable will not support P2P). If your computer does not have a DB9/RS232 serial port, use the USB-to-Serial Adapter (p/n 410-0210-000) to connect the mini-USB to DB9 cable to a PC’s USB port.

• Supply power to the RS232 Travel Charger. Either attach the AC adapter to the RS232 Travel Charger, or plug its USB-A plug into an active USB port on the computer for power. The RS232 Travel Charger will not operate without a power source.

Note: Do not plug in both the USB and the AC adapter at the same time, as this may cause errors.

Follow one of the three diagrams below for power and data connection options.

RAE Systems by Honeywell 877-723-2878 raesystems.com 2

• Turn on the MultiRAE.

• Determine the COM (communications) port that you must use.

Right-click on “Computer” Icon on your desktop and follow the path Properties >> Device Manager >> Ports (COM & LPT).

• Find the number of the COM port to which the MultiRAE is connected. The MultiRAE port is the one that reads “Silicon Labs CP210x USB to UART Bridge (COM[Port Number]).”

• Close the Device Manager window.

• Start your TelNet client.

TelNet Clients

Here are setup procedures for two typical, easy-to-use TelNet clients, HyperTerminal and PuTTY. If you are familiar with others, they may be used as well.

HyperTerminal

• Start HyperTerminal.

a. Enter a name for the connection and click “OK.”

b. At the “Connect To” screen’s “Connect Using” option, select the port number.

c. Click “OK.”

d. In the Properties window for your COM port, select these settings:

• Bits per second (or Baud): 9600

• Data bits: 8

• Parity: None

• Stop bits: 1

• Flow control: None

e. Click “Apply.”

f. Click “OK.”

The HyperTerminal window appears and the connection is active.

Test the connection by typing “S.” You should see the Serial Number of your MultiRAE.

PuTTY

• Double-click the PuTTY icon to start it.

• Click “Run.”

• At the PuTTY Configuration window, click the “Serial” button.

• In the box labeled “Serial line,” input your COM (communications) port number.

• Set the “Speed” to 9600.

• Give your session a name by typing a name into “Saved Sessions” and click “Save.” (This shortcut can be used for subsequent sessions.)

• Click “Open.”

The PuTTY window with your port’s name should appear.

Type “S.” You should see the serial number of your MultiRAE.

Operation

The keyboard shortcuts in Table 1 display the unit’s remote control readout in the terminal window.

Sensor Error/Alarm Limit Bits

A byte, comprising eight bits, is used to record the alarm limits and errors for each sensor. All of the sensors in the MultiRAE are checked remotely, and then the results are displayed when you type a shortcut.

Type “N.” The names of the sensors appear.

Type “E.” If everything is operating correctly, “0 0 0 0 0” appears.

Note: the number of zeroes corresponds to the number of sensors.

Therefore, if there are four sensors, you see four zeroes, etc.

RAE Systems by Honeywell 877-723-2878 raesystems.com 3

Typing “?” tells the instrument to list all supported shortcut commands. For normal operation mode, the menu structure is:

MultiRAE2 P2P Menu C: Calculated Reading E: Sensor Error F: Firmware Version I*: Monitor Status L: Alarm Limits M: Model Number N: Sensor Name P: Go To Sleep R: Instant Reading S: Serial Number T: Interval Set U: Unit ?: Display This Menu Ready…

When instrument already in “Sleep” mode, then the menu structure is:

MultiRAE2 P2P Menu P: Wake up ?: Display This Menu Ready...

Table 1: Commands And Query Functions

Command Function Display (Sample)

C Calculated Reading

CO 49 0 5 3

VOC 300 0 45 35

H2S 15 0 3 3

LEL 3 0

O2 20.9 19.5

E Sensor Alarm/Error 0 0 144 8 0

F Firmware version V1.14

I* Monitor Status 17

L Alarm Limits

CO 100 35 25 25

VOC 500 100 100 50

H2S 50 20 15 15

LEL 50 35

O2 23.5 19.5

M Model Number PGM-6248

N Sensor Name CO VOC H2S LEL O2

P Go To Sleep/Wake Up

R Instant Reading 4 6 0 0 21.4

S Serial Number 090*******

RAE Systems by Honeywell 877-723-2878 raesystems.com 4

Table 1: Commands And Query Functions

Command Function Display (Sample)

T Interval Set (update rate to the display, in seconds) Type “T” followed by a number from 1 to 3600

0 20.9 0 0.0 0 0 0 0 0 0 0 20.9 0 0.0 0 0 0 0 0 0 0 20.9 0 0.0 0 0 0 0 0 0 0 20.9 0 0.0 0 0 0 0 0 0

U Unit (of measure) ppm ppm ppm %LEL %

? Display Menu

MultiRAE2 P2P Menu

C: Calculated Reading E: Sensor Error F: Firmware Version I*: Monitor Status L: Alarm Limits M: Model Number N: Sensor Name P: Go To Sleep R: Instant Reading S: Serial Number T: Interval Set U: Unit ?: Display this menu

Ready…

* Command “I” appears with Firmware V1.18 and Sensor Firmware

1.08 or higher.

Command “P” appears with Firmware V1.31 and Sensor Firmware V1.08 or higher.

Keyboard Shortcuts And Query Functions

The following table shows the keys you type to query the MultiRAE, as well as the function name and a sample of what is then shown on the display.

Notes:

• Commands are not case-sensitive.

• Tab(0x09) is used to separate readings or Alarm/Error code.

• The interval between two commands will be longer than 100ms.

• For a quick view of the sensors’ status (installed sensors, units of measure, and readings), type these three letters:

N U R

Here is a sample of the display:

LEL OXY CO H2S VOC

%LEL % ppm ppm ppb 0 20.9 0 0.0 0

(N) The first line is the names of the sensors.

(U) The second line is their units of measure.

(R) The third line shows their readings.

To view the Calculated Reading, type “C.” Here as an example of the output:

LEL 0 0

OXY 20.9 20.9

CO 0 0 0 0

H2S 0.0 0.0 0.0 0.0

VOC 170 0 0 0

To view the Alarm Limits, type “L.”

Here is a sample of the Alarm Limits display:

LEL 20 10

OXY 23.5 19.5

CO 200 35 100 35

H2S 20.0 10.0 15.0 10.0

VOC 100000 50000 25000 10000

The information is arranged to show the sensor name, High, Low, STEL (where appropriate) and TWA (where appropriate).

RAE Systems by Honeywell 877-723-2878 raesystems.com 5

Sensor Error/Alarm Limit Bits A byte, comprising eight bits, is used to record the alarm limits and errors of each sensor. When you type the command “E,” all of the sensors in the unit are checked remotely and then the results are displayed.

Table 2: Alarm/Error Codes

Alarm/Error Code Explanation

Over Range 1 (Bit 0) Sensor over range error

Max 2 (Bit 1) Sensor max (hardware saturated)

Fail 4 (Bit 2) A failure has occurred

• If the sensor is a PID, the lamp has failed

• If the sensor is an LEL: the LEL sensor is off

High 8 (Bit 3) High alarm limit has been reached

Low 16 (Bit 4) Low alarm limit has been reached

STEL 32 (Bit 5) STEL has been reached

TWA 64 (Bit 6) TWA has been reached

Drift 128 (Bit 7) A negative drift has occurred

Table 3*: Unit status information, a byte, comprising 8 bits

Status Code Explanation

Power 1 Power – 1 = Normal, 0 = Abnormal

Battery 2 Battery – 1 = Low alarm , 0 = Normal

Pump 4 Pump – 1 = Stall, 0 = Normal or Not installed

Memory 8 Datalog Memory - 1 = Full, 0 = Normal or Not installed

Sensor alarm 16 Sensor alarm, any of the sensor alarm the bit will be set, includes latched alarms.

Unit Failure 32 Unit Failure–1=Failure, 0=Normal (Not used in MRII, always return 0)

Reserve 64 Reserve as 0

Alarm Mode 128 The current setting of alarm mode. 1 - Latch 0 - Auto Reset

Examples Of How To Interpret MultiRAE Alarm/Error Codes If the High alarm has been exceeded on sensor number one (LEL), this illustrates a reply when you type “E”:

8 0 0 0 0 This tells you that the High alarm limit has been reached on the first sensor (LEL).

If the High alarm and the STEL alarm limit are reached for the second sensor (H2S), this is the information you would see:

0 40 0 0 0 (40 = 8 + 32)

If two events occur simultaneously, the display looks like this:

8 40 0 0 0

The quickest way to identify the nature of the alarm or error is to subtract the largest numbers first.

40 - 32 = 8 32 = Bit 5 = STEL alarm 8 = Bit 3 = High alarm

DISTRIBUTION STATEMENT A. Approved for public release: distribution unlimited.

DEPARTMENT OF HOMELAND SECURITY

SCIENCE AND TECHNOLOGY DIRECTORATE

Land Automated Scene Understanding Program

U.S. Border Patrol Sensor System Cursor‐on‐Target (CoT)

Implementation Guide

April 22, 2020

Version 10a ii | P a g e

DISTRIBUTION STATEMENT A. Approved for public release: distribution unlimited

Table of Contents

Section 1: Introduction

1.1 Purpose

1.2 Ownership

1.3 Background

1.4 Terminology

Section 2: Export Interface

2.1 Protocols Used

2.2 User Interface

2.3 Domain Name Resolution

2.4 Ancillary Equipment

Section 3: Radar Track Message

3.1 CoT Message Format (Radar Track Message)

3.2 Message Rate (Radar Track Message)

3.3 User Interface & Data Generation (Radar Track Message)

Section 4: Platform Position Message

4.1 CoT Message Format (Platform Position Message)

4.2 Message Rate (Platform Position Message)

4.3 User Interface & Data Generation (Platform Position Message)

Section 5: Field of View (FOV) Cone Message

5.1 CoT Message Format (FOV Cone Message)

5.2 Message Rate (FOV Cone Message)

5.3 User Interface & Data Generation (FOV Cone Message)

Section 6: Sensor Point of Interest (SPI) Message

6.1 CoT Message Format (SPI Message)

6.2 Message Rate (SPI Message)

6.3 User Interface & Data Generation (SPI Message)

Section 7: Unattended Ground Sensor (UGS) Alarm Message

7.1 CoT Message Format (UGS Alarm Message)

7.2 Message Rate (UGS Alarm Message)

7.3 User Interface & Data Generation (UGS Alarm Message)

Section 8: Situational Awareness (SA) Message iii | P a g e

8.1 CoT Message Format (SA Message)

8.2 Message Rate (SA Message)

8.3 User Interface & Data Generation (SA Message)

Section 9: Small UAS (SUAS) Surveillance Message

9.1 CoT Message Format (SUAS Surveillance Message)

9.2 Message Rate (SUAS Surveillance Message)

9.3 User Interface & Data Generation (SUAS Surveillance Message)

Section 10: Circle Shape Message

10.1 CoT Message Format (Circle Shape Message)

10.2 Message Rate (Circle Shape Message)

10.3 User Interface & Data Generation (Circle Shape Message)

Section 11: Polyline Shape Message

11.1 CoT Message Format (Polyline Shape Message)

11.2 Message Rate (Polyline Shape Message)

11.3 User Interface & Data Generation (Polyline Shape Message)

Appendix A: Field Value Conventions

Appendix B: Example CoT Messages

Appendix C: Video Link Tag

Change Tracker Version Date Change Description

1 04/05/2018 Initial version 2 04/12/2018 Corrected initial version date; updated Section 1 3 04/27/2018 Modified 3.3 b) and c) 4 05/03/2018 Modified UID and callsign in all messages 5 05/04/2018 Minor formatting changes 6 05/08/2018 Fixed version number and typos in Appendix A 7 05/18/2018 Updated slope description and SA message rate guidance 8 05/02/2019 Changed “SPOI” to “SPI”; Changed “Ownship” to “Platform”; Changed

“Blue Force Tracking” (message) to “Situational Awareness (SA)” (message); consolidated examples of messages into (new) Appendix B;

inserted Appendix A w/ matrix of systems implementing CoT and system type implementation guidance; updated uid guidance & reflected guidance in CoT message examples; added Polyline Shape & Circle Shape Message

9 02/11/2020 Added Appendix C for Video Link Tags 10a 04/22/2020 Minor edits to allow Distro A (Public Release) designation; moved system matrix to Addendum A of the document iv | P a g e

Tables Table 1: CoT Radar Track Message Table 2: CoT Platform Position Message Table 3: CoT FOV Cone Message Table 4: CoT SPI Message Table 5: CoT UGS Alarm Message Table 6: CoT SA Message Table 7: CoT SUAS Surveillance Message Table 8: CoT Circle Shape Message Table 9: CoT Polyline Shape Message Table 10: Values for Messages Incorporating the how (Event) Field Table 11: Values for Messages Incorporating the type (Event) Field Table 12: Values for Messages Incorporating the uid (Event) Field Table 13: Values for Messages Incorporating the callsign (Contact) Field Table 14: Values for Messages Incorporating the relationship (Link) Field Table 15: Values for Messages Incorporating the type (Link) Field Table 16: Values for Messages Incorporating the uid (Link) Field Table 17: Radar Track Message Example (from Mobile Radar System) Table 18: Platform Position Message Example (from Mobile Radar System) Table 19: FOV Cone Message Example (from Mobile Radar System) Table 20: SPI Message Example (from Mobile Radar System) Table 21: UGS Alarm Message Example (from Seismic Sensor) Table 22: SA Message Example (from ATAK) Table 23: SUAS Surveillance Message Example (from SUAS) Table 24: Circle Shape Message Example Table 25: Polyline Shape Message Example (for a Line) Table 26: Video Link Tag Message Examples

1 | P a g e

Section 1: Introduction Specification for requirements along with best practices recommendations to be implemented as applicable to specific sensor systems.

1.1 Purpose

This document is intended to serve as a reference for current and future U.S. Border Patrol (USBP) sensor systems to consult when evaluating what, if any, CoT interface they should implement.

The intent of the document is to enable current and future USBP sensor systems to identify the type of the data which could be exported and samples to provide to contractors to enable them to provide a rough estimate to satisfy any requirements USBP may put in their contract to export data via CoT.

The document owner (currently S&T) would then work with the respective USBP sensor system owner to create a system‐specific implementation profile (see appendices) to be written as contractual requirements for their developer.

1.2 Ownership

This document is currently owned and will be updated by S&T prior to its transition to USBP, after which time USBP will obtain ownership and responsibility for updating the document.

S&T may use the document to develop similar CoT implementation guides for other CBP or DHS components which would then transition to their respective offices for ownership and responsibility.

The version number is appended with an “a” to indicate this version has been edited to enable it to be marked as Distribution A for unlimited release to the public.

1.3 Background

USBP has historically operated in many areas which are sparsely populated and which have limited communications bandwidth and resulted in voice‐only communications via land mobile radios to be the primary means of communication.

For this reason many of the USBP sensor systems providing tactical surveillance did not have a requirement to export data to other systems as the cost for the functionality would not be justified by the limited use of it.

As mobile technology matured and became more ubiquitous there is now a greater opportunity to leverage technology to enable data exchanges with mobile tactical technologies. The result is greater shared tactical situational awareness while reducing congestion on voice channels.

One of those mobile technologies is the Android Team Awareness Kit (ATAK) family of solutions which was developed by AFRL for the DoD for Special Operations Units conducting missions in a variety of environments many of which resemble those of USBP.

The ATAK family of solutions use the Cursor on Target (CoT) format used by many DoD systems for exchanging data. CoT is a mature standard which is an XML based message format that is event based and has time, location and type for each message along with any additional descriptor tags which may be added depending on the type of event.

2 | P a g e

As the ATAK family of solutions has emerged as the possible cornerstone of the overall shared tactical situational awareness capability across USBP an effort is underway to enable other tactical situational awareness technologies to interface and exchange data via CoT.

S&T has partnered with USBP on evaluation and implementation of the ATAK family of solutions and subsequent implementation of CoT by other USBP sensor systems and will continue the partnership thru transition and potentially beyond.

1.4 Terminology

The meaning and implications of several terms within the context of this document are described below to alleviate any concern with their general or other usage.

“Should” indicates general guideline which should be evaluated for any special circumstances prior to adding the requirement and should be changed to “shall” when it is inserted into requirements document.

“Generated” implies created and sent when referring to a message type being generated.

3 | P a g e

Section 2: Export Interface The system exporting CoT should provide an interface to enable transmitting the data from the system to include identified protocols, user interface for configuration, domain name resolution, and network connection point.

2.1 Protocols Used

a) The system exporting CoT should support the multi‐cast protocol to a specified multi‐cast group and port.

b) The system exporting CoT should support the TCP/IP sent to a specific IP address and port.

c) The system exporting CoT should support the UDP sent to a specific IP address and port.

2.2 User Interface

a) The system exporting CoT should support operator configuration of the multi‐cast group and port.

b) The system exporting CoT should support operator configuration of the IP address and port.

c) The system exporting CoT should support operator configuration of the IP address and port.

2.3 Domain Name Resolution

The system exporting CoT should support domain name resolution of a DNS address (e.g.

www.takserver.com) entered into an IP address fields.

2.4 Ancillary Equipment

a) The system exporting CoT should use the existing network connection point if one exists.

b) The system exporting CoT should provide a port, power, and space to install and operate any necessary communications equipment if none exists.

4 | P a g e

Section 3: Radar Track Message The Radar Track Message is being implemented by USBP for terrestrial sensor systems with radars which are able to identify a target and generate a track of its movements.

3.1 CoT Message Format (Radar Track Message)

The format for a CoT‐compliant Radar Track Message is described in the figure below that provides the fields, field descriptions, and example schema. System specific Radar Track Message examples are contained in the appendices.

Field Field Description Message Format how method for determining track/target <?xml version=”1.0” standalone=”y”?>

<event how=” – “ stale=” “ start=” “ time=” “ type=” - - “ uid=” “ version=”2.0”>

<point ce=” “ hae=” “ lat=” “ le=” “ lon=” “/>

<detail> <contact callsign=” “/>

<track course=” “ speed=” “ slope=” “/> </detail> </event> stale time data ceases to be valid (for event) start time data will become valid (for event) time time data was generated (for event) type type of message/event uid unique identifier for the event target version version of CoT schema ce cylinder radius of point (meters) hae height above ellipsoid point (meters, WGS84) lat latitude of point (decimal degrees, WGS84) le cylinder half-height of point (meters) lon longitude of point (decimal degrees, WGS84) course course track/target heading (decimal degrees) speed speed of the track/target (meters per second) slope vertical component of track vector (degrees) callsign callsign for the originator (i.e. system)

Table 1: CoT Radar Track Message

3.2 Message Rate (Radar Track Message)

a) Start: A Radar Track Message should be generated upon the selection of a target for export (in CoT format).

b) End: A Radar Track Message should cease to be generated upon the de‐selection of a target for export and when a target is no longer being detected by the radar. In both cases, the stale time from the last Radar Track Message for the target detection will signal the end of the track.

c) Update: Subsequent Radar Track Messages (with updates on the target) should be generated at the sensor system refresh rate for the radar.

3.3 User Interface & Data Generation (Radar Track Message)

a) The user interface should allow an operator to select a track (of a detected target) created by the system to start exporting the data (in CoT format).

b) The user interface should allow an operator to designate track type (i.e. unknown, hostile, neutral, friendly).

c) The method for defining the name for the track shall be specified in sensor profiles and impact either the user interface (i.e. provide ability for user to enter value) or system automation requirements.

5 | P a g e

d) The default value for track type should be “unknown” unless another value is selected via the user interface.

e) The track type (i.e. unknown, hostile, neutral, friendly) selected should be implemented using the

MIL2525 symbology.

f) The user interface should allow an operator to de‐select a track (of a detected target) created by the system to cease exporting the data (in CoT format).

h) The uid should automatically be generated for the track based upon system data (specified in system profiles).

h) The user interface should provide the ability to enter/edit the callsign of the track.

i) The user interface should display the callsign of the track (not the uid).

6 | P a g e

Section 4: Platform Position Message The Platform Position Message is being implemented by USBP for terrestrial mobile/relocatable sensor systems which do not have a permanent/fixed location (geo‐referenced in existing systems).

4.1 CoT Message Format (Platform Position Message)

The format for a CoT‐compliant Platform Position Message is described in the figure below that provides the fields, field descriptions, and example schema. System specific Platform Position Message examples are contained in the appendices.

Field Field Description Message Format how method for determining system position <?xml version=”1.0” standalone=”y”?>

<event how=” – “ stale=” “ start=” “ time=” “ type=” - - - - - - “ uid=” “ version=”2.0”>

<point ce=” “ hae=” “ lat=” “ le=” “ lon=” “/>

<detail> <contact callsign=” “/>

stale time data ceases to be valid (for event) start time data will become valid (for event) time time data was generated (for event) type type of message/event uid unique identifier for the system version version of CoT schema ce cylinder radius of point (meters) hae height above ellipsoid point (meters, WGS84) lat latitude of point (decimal degrees, WGS84) le cylinder half-height of point (meters) lon longitude of point (decimal degrees, WGS84) course course track/system heading (decimal degrees) speed speed of the track/system (meters per second) callsign callsign for the originator (i.e.…