LTL System Requirement Matrix.pdf

UNCLASSIFIED

DOS Less-than-Lethal Defensive System Requirements Matrix

Req # Requirement Description

General System Requirements

G1

Shall comply with prohibitions on using hardware, software, and services from named countries and manufacturers. (Ref FAR 4.2 and

4.21).

G2

Shall be manufactured or substantially transformed in the United States or a Trade Agreements Act (TAA)-designated country. (Ref FAR

52.225-5).

G3 Shall be compatible with worldwide voltages (100 VAC - 250 VAC – 50

Hz/60 Hz) input power, VDC or PoE.

G4

Shall be electromagnetic compatibility (EMC)-compliant IAW CFR47, Part 15 Class A, (FCC requirements for radiated and conducted emissions) or equivalent U.S.-recognized international standard.

G5 Shall be UL-approved for electrical safety per IEC/UL 62368-1.

G6 Shall not be a cloud-based solution.

G7

Shall not require wireless communication (Wi-Fi, Bluetooth, NFC, etc.)

for operation. Any included wireless features must be user-configurable and capable of being fully disabled.

G8 Shall not require an internet connection for programming, operation or updates.

G9

Shall be commercial-off-the-shelf (COTS) (objective), modified COTS

(threshold), or custom using a majority of COTS components

(threshold).

G10

The system shall maintain uninterrupted functionality for 2 hours

(threshold)/8 hours (objective) under normal operating conditions without the need for refueling, recharging, or replacing consumables.

G11 The system shall be able to be configured and operated from a centralized control point within the building or compound.

G12 Shall be capable of performing a walk test of the system without dismantling or reconfiguring any edge devices.

UNCLASSIFIED

DOS Less-than-Lethal Defensive System Requirements Matrix

Req # Requirement Description

General System Requirements

G13

Shall not require the OEM to perform the installation, initialization, or commissioning of the system. System shall be configured in a manner that allows OEM trained DOS staff to perform all installation, initialization, and commissioning tasks.

G14

Shall not require the OEM to perform preventive or corrective maintenance of the system. Shall be able to be serviced and repaired by

DOS technicians, trained by the train-the-technician requirement (see

VS6).

Deterrent Component Requirements

DC1 Deterrent method shall be of a less-than-lethal design.

DC2

Shall be operational through a temperature range of -33 °C (threshold), -

40 °C (objective) to +60 °C at up to 95% humidity above freezing temperatures.

DC3

The deterrent components shall be able to be installed in both indoor and outdoor environments (objective) or be able to operate in sheltered but indirectly wet environments, e.g., under an outdoor building portico

(threshold).

DC4

The system shall be architecturally compatible and visually consistent with the design language of the diplomatic facility environment.

DC5

Shall be capable of being mounted to building or perimeter surfaces, not personnel-carried or vehicle-mounted.

DC6

Shall not use chloroacetophenone (CN), o-chlorobenzylidenemalononitrile (CS), or dibenzoxazepine (CR)

DC7 Shall not use bullets, canisters, or similar projectiles of any kind.

DC8 Shall not use an explosive charge to deploy irritants.

UNCLASSIFIED

Control Console Requirements

(If a control console is proposed)

[Note: some requirements only apply to a digitally controlled console]

CC1

Shall occupy a 19” wide rack panel with no more than 6 RU (10.5 in.) of rack height. The rear of the rack space may be used for components supporting the control console.

CC2

Shall be operational through a temperature range of 0 °C to +40 °C (32

°F to 104 °F) at up to 95% humidity at above freezing temperatures in an indoor environment.

CC3 Shall not be of a desktop or stand-alone rack design.

CC4

If the control console uses a digital display, it shall be a touchscreen

(objective) or a screen with pushbuttons (threshold) and be mountable within the rack. A pull-out, or tilt-up display is not permissible.

CC5

Shall include a system “Power On” indicator. Indicator may be a digital display that is energized and in stand-by mode.

CC6

Shall not require a keyboard or mouse for activation/deactivation. The use of a keyboard and mouse shall be limited to initial setup and local administrator level system configuration changes.

CC7

Shall have a mechanical (objective) or electronic (threshold) safeguard that prevents inadvertent activation of the system and that functions within the control console design. An electronic safeguard shall not employ any additional device such as a pass-card, physical key, electronic fob, phone verification, or similar.

CC8

Shall have a mechanical (objective) or electronic (threshold) emergency disable that will cease all system operations, that will return all prior operational selections to nominal and that functions within the control console design.

CC9 Shall have deterrent selection control labels that are user definable.

CC10

Shall have the capability to allow a one button selection/deselection of all zones.

CC11

Should allow for a hierarchy in which one control console acts as the primary over all other control consoles and any remaining control consoles that have different lower priorities in the hierarchical structure

(objective).

UNCLASSIFIED

Control Console Requirements

(If a control console is proposed)

[Note: some requirements only apply to a digitally controlled console]

CC12

Should allow for a higher priority control console to select and lock/unlock lower priority control consoles (objective).

CC13

Shall be capable of being installed remotely from the outlying deterrent components.

Incident Reporting Requirements

(If an Internet Protocol [IP]-based system is proposed)

IR1

Shall log the following events: activation, deactivation, zone enable, zone disable, system error, deterrent level, local console login, local console logout, and local console changes.

Security/Information Assurance Requirements

SIA1 Shall support Microsoft Active Directory authentication.

SIA2

Shall support role-based access that will allow the capability for customized roles.

SIA3

Shall operate on current operating systems, e.g., Windows 11, Windows Server, Red Hat Enterprise Linux (RHEL), Ubuntu Server, and Debian, etc.

System Operation Requirements

SO1

Shall provide a user interface that evidences ease-of-use and minimizes the potential for operator error.

Note: This requirement applies to both IP- and non-IP-based systems.

SO2

Shall, at a minimum, provide the capability to perform access audits to cover both remote and local access. The access audits will log detailed information for log on and log off actions.

UNCLASSIFIED

System Operation Requirements

(If an Internet Protocol [IP]-based system is proposed)

SO3

Shall use a secure communications protocol (HTTPS, Transport Layer

Security [TLS] 1.2 at a minimum, 1.3 preferred, Advanced Encryption

Standard [AES] encryption, etc.).

SO4

Shall, using the NTP protocol, synchronize its system date/time to the date/time provided by the NTP server.

SO5

Shall have a verification process to ensure that all commands received by the system components are received and properly executed.

SO6 Networked components shall support IPv4; IPv6 (objective).

Vendor Support Requirements

(General)

VS1

The warranty period shall be a minimum 1-year from the date of installation by DS/ST (objective) or the date of delivery to DS/ST

(threshold).

VS2

Shall provide replacement parts and labor for the duration of the product’s warranty.

VS3

Shall provide customer technical support during product’s warranty period, and for a minimum period of five years from the time of last manufacture.

VS4

Shall grant internal distribution rights for all necessary manuals and technical documentation.

VS5

Shall provide "train-the-trainer" support to allow Government instructors to develop instructional materials and training for the user community.

VS6

Shall provide "train-the-technician" support to allow Government technicians to become certified in servicing the equipment under warranty and once deployed worldwide.

UNCLASSIFIED

Vendor Support Requirements

(if an IP based system is proposed)

VS7

Shall provide backup copies of all software and firmware needed to restore the system, to include system interface and tools necessary for updates.

VS8

Shall provide Application Program Interface (API) documentation for all IP-based components.

VS9

Shall provide the capability for the DOS to remotely deploy software, and firmware updates to the management system/server as well as the edge devices.