Attachment 0004 - AIE-3.4 SYSTEM DESCRIPTION AND ARCHITECTURE.pdf

Unclassified//For Official Use Only

DISTRIBUTION STATEMENT – Further dissemination only as directed by Contracting Officer, FPS-3 Contract or higher DoD authority.

DESTRUCTION NOTICE – For classified documents, follow the procedures in DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), Chapter 5, Section 7, or DoD 5200.1-R, Information Security Program Regulation, Chapter IX. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

System Description and Architecture

Unclassified//For Official Use Only

Product Manager, Force Protection Systems (PM FPS)

Automated Installation Entry (AIE)-3.4 System Description and Architecture

01 April 2022

System Description and Architecture iii April 2022

Unclassified//For Official Use Only

SYSTEM DESCRIPTION AND ARCHITECTURE

RECORD OF REVISION

Revision Number Date Description

Draft, Rev 0 17 October 2016 Initial Release for AIE-3

N/A 18 November 2016 Addressed comments by Government reviewers

N/A 22 November 2016 Additional details added regarding EntryPoint Datamodel (Appendix K) and Client-Server communication (Section 6.2)

Draft, Rev 1 31 January 2017 Added missing DODAF Views for: OV-6a, OV-6b, OV6c, SV-5b, SV-10a, SV-10b, SV-10c. Additionally, added Portable Registration System to SV-1 and SV-3.

Final 2 March 2017 Final submission

Final RCF 31 March 2017 Addressed comments by Government reviewers

Final, Rev 3 6 March 2020

Modifications to DODAF Views and Interfaces to account for Visitor Registration and RFID additions to the architecture. Depicts Pure Fleet design rather than AIE-3 baseline design.

Draft, Rev 4 14 February 2022

Modifications throughout to address AIE-3/4 capabilities and associated changes. Sections 3 and 8 have TBD’s identified in content. Appendices B, I, J, W, X, Y, Z, EE are TBD

Draft, Rev 4.1 28 February 2022

Modifications to Sections 3 and 8, and Appendices B, I, J, W, X, Y, Z, EE

Appendix J has TBDs for Event Trace: AutoRegistration, Event Trace: RFID Access Granted, and Event Trace:

Handheld Operations.

Final, Rev 4.2 1 April 2022 Addressed comments by Government reviewers

System Description and Architecture iv

Unclassified//For Official Use Only

TABLE OF CONTENTS

Section/Paragraph Title Page

1. Scope

1.1 Identification

1.2 System Overview

1.3 Document Overview

1.4 Component Definition

2. Reference Documents

2.1 Government Documents

2.1.1 DoD Documents (in alphabetical order)

2.1.2 Other Government Documents

2.1.3 Code of Federal Regulations (CFR)

2.1.4. AIE-3/4 Program Documents

2.2 Non-Government Documents

3. AIE-3/4 System-Wide Design Decisions

4. System Architectural Design

4.1 All Viewpoint 1 (AV-1): Overview and Summary Information

4.2 All Viewpoint 2 (AV-2): Integrated Dictionary

4.3 Operational Viewpoint 1 (OV-1): High Level Operational Concept Graphic

4.4 Operational Viewpoint 2 (OV-2): Operational Node Connectivity Description

4.5 Operational Viewpoint 3 (OV-3): Operational Information Exchange Matrix

4.6 Operational Viewpoint 4 (OV-4): Organizational Relationships Chart

4.7 Operational Viewpoint 5 (OV-5): Operational Activity Model

4.8 Operational Viewpoint 6a (OV-6a): Operational Rules Model

4.9 Operational Viewpoint 6b (OV-6b): Operational State Transition Description

4.10 Operational Viewpoint 6c (OV-6c): Operational Event Trace Description

4.11 Operational Viewpoint 7 (OV-7): Logical Data Model

4.12 Systems Viewpoint 1 (SV-1): Systems Interface Description

4.13 Systems Viewpoint 2 (SV-2): Systems Communications Description

4.14 Systems Viewpoint 3 (SV-3): Systems-Systems Matrix

4.15 Systems Viewpoint 4 (SV-4): Systems Functionality Description

4.16 Systems Viewpoint 4a (SV-4a): Systems Functionality Description

4.17 Systems Viewpoint 4b (SV-4b): Systems Functionality Description

4.18 Systems Viewpoint 5 (SV-5): Operational Activity to Systems Function

Traceability Matrix

4.19 Systems Viewpoint 5a (SV-5a): Operational Activity to Systems Function

Traceability Matrix

4.20 Systems Viewpoint 5b (SV-5b): Operational Activity to Systems Function

Traceability Matrix

4.21 Systems Viewpoint 5c (SV-5c): Operational Activity to Systems Function

Traceability Matrix

4.22 Systems Viewpoint 6 (SV-6): Systems Data Exchange Matrix

4.23 Systems Viewpoint 7 (SV-7): Systems Performance Parameters Matrix

4.24 Systems Viewpoint 8 (SV-8): Systems Evolution Description

4.25 Systems Viewpoint 9 (SV-9): Systems Technology Forecast

4.26 Systems Viewpoint 10a (SV-10a): Systems Rules Model

4.27 Systems Viewpoint 10b (SV-10b): Systems State Transition Description

4.28 Systems Viewpoint 10c (SV-10c): Systems Event-Trace Description

April 2022

System Description and Architecture v

Unclassified//For Official Use Only

4.29 Systems Viewpoint 11 (SV-11): Physical Schema

4.30 Technical Viewpoint 1 (TV-1): Technical Standards Profile

4.31 Technical Viewpoint 2 (TV-2): Technical Standards Forecast

5. Requirements Traceability Matrix

6. Software Design Description

6.1. COTS Software Component Identification

6.2. Registration

6.2.1 Portable Registration

6.2.2 Kiosk 66

6.2.3 Online Vetting and Registration

6.3. Installation-wide Data Store

6.4. Identity Management Middleware (IMM)

6.5. Removed

6.6. ACP Physical Access

6.6.1. Lane Control Client

6.6.2. IMM AutoReg

6.6.3. Handheld

6.6.4. Visual Verify

7. Interface Requirements Specification

7.1. Interface Identification

7.2. LE Vetting Interface Requirements

8. Interface Design Description

8.1. INT-001 IP network interface

8.2. INT-002 Wiegand

8.3 INT-003 RS-485

8.4 INT-004 Handheld

8.5 INT-005 Dry Contact

8.6 INT-006 Removed

8.7 INT-007 Vehicle Exiting Lane

8.8 INT-008 Gate Arm Up Command

8.9 INT-009 Gate Arm Down Command

8.10 INT-010 Gate Crash Alarm

8.11 INT-011 Red Light Control

8.12 INT-012 Green Light Control

8.13 INT-013 Rhino Reader Communications

8.14 INT-014 Traffic Light

8.15 INT-015 Rhino Reader Display

8.16 INT-016 Intercom Data

8.17 INT-017 Intercom Station

8.18 INT-018 Rhino Reader Credential Data

8.19 INT-019 Rhino Reader Fingerprint Capture

8.20 INT-020 Video

8.21 INT-021 Lane Control Client Operations

8.22 INT-022 Registration Operations

8.23 INT-023 Registration Data Collection

8.24 INT-024 Removed

8.25 INT-025 PIR Import

8.26 INT-026 Cache Box Synchronization

8.27 INT-027 Removed

8.28 INT-028 Registration Vetting

8.29 INT-029 In-Lane Auto Registration Vetting

April 2022

System Description and Architecture vi April 2022

Unclassified//For Official Use Only

8.30 INT-030 IoLS Vetting Request

8.31 INT-031 LE Vetting Request

8.32 INT-032 Qscan Reader Communications

8.33 INT-033 Qscan Reader Display

8.34 INT-034 Qscan Reader Credential Data

8.35 INT-035 Cache Box Updates

8.36 INT-036 App/DB Servers Updates

8.37 INT-037 Mobile Device Management

8.38 INT-038 Cellular Wireless

8.39 INT-039 Input Status

8.40 INT-040 Relay Control

8.41 INT-041 Contact Open/Close

9. Database Design Description

9.1. Database Overview

9.2. Removed

9.3. Symmetry Database Design

9.3.1. multiMAX

9.3.2. multiMAXExport

9.3.3. multiMAXImport

9.3.4. multiMAXTxn

9.3.5. multiMAXVideo

9.3.4. OPMG 88

9.4. Symmetry CompleteView Database Design

10. Notes

APPENDIX A

APPENDIX B

APPENDIX C

APPENDIX D

APPENDIX E

APPENDIX F

APPENDIX G

APPENDIX H

APPENDIX I

APPENDIX J

APPENDIX K

APPENDIX L

APPENDIX M

APPENDIX N

APPENDIX O

APPENDIX P

APPENDIX Q

APPENDIX R

APPENDIX S

APPENDIX T

APPENDIX U

APPENDIX V

APPENDIX W

APPENDIX X

APPENDIX Y

APPENDIX Z

APPENDIX AA

System Description and Architecture vii April 2022

Unclassified//For Official Use Only

APPENDIX BB

APPENDIX CC

APPENDIX DD

APPENDIX EE

System Description and Architecture viii April 2022

Unclassified//For Official Use Only

LIST OF FIGURES

Figure Title Page

Figure 1: System Component Definition Figure 2: Requirements Traceability Matrix Figure 3: Interface Identification Matrix Figure 4: Law Enforcement Vetting Interface Requirements Figure 5: Cellular Wireless Configuration Figure 6: DODAF Viewpoints Required by DI-MGMT-81644A Figure 7: AIE-3/4 Acronym Definitions Figure 8: OV-1, High Level Operational Concept Figure 9: OV-2, Operational Resource Flow Description Figure 10: OV-3, Operational Resource Flow Matrix Figure 11: OV-4, Organizational Relationships Chart Figure 12: OV-5a-1, Top Level Operational Activity Decomposition Figure 13: OV-5a-2, Decomposition of the Training Activity Figure 14: OV-5a-3, Decomposition of the Support Activity Figure 15: OV-5a-4, Decomposition of the Operate Activity Figure 16: OV-5a-5, Decomposition of the Use Activity Figure 17: OV-5b, Operational Activity Model Figure 18: OV-6a, Operational Rules Model Figure 19: OV-6b, State Transition - Overview Figure 20: OV-6c, Event Trace - Registration Figure 21: OV-6c, Event Trace – Visitor Self-Service Web Registration Figure 22: OV-6c, Event Trace – Online Vetting and Registration - Access Granted Figure 23: OV-6c, Event Trace - ACP Operations - Access Granted Figure 24: OV-6c, Event Trace - ACP Operations - Access Denied Figure 25: OV-6c, Event Trace - ACP Operations - Automatic Registration Figure 26: OV-6c, Event Trace - RFID Access Granted Figure 27: OV-6c, Event Trace - Handheld Operations - Tier 1 Access Granted/Auto

Registration Figure 28: OV-6c, Event Trace - Handheld Operations - Tier 1 Access Granted/In Lane

Registration Figure 29: OV-6c, Event Trace - Handheld Operations - Tier 2 Access Granted/Auto

Registration Figure 30: OV-6c, Event Trace - Handheld Operations - Tier 1 Access Granted/In Lane

Registration Figure 31: Identity Management Middleware Interface Definition Figure 32: NCITE Vetting Service Interface Definition Figure 33: Symmetry PIR Data Record Figure 34: AIE-3/4 OPMG Dashboard Reports Logical Data Model Figure 35: SV-1, AIE-3/4 & Pure Fleet Configurations with RFID Figure 36: SV-2a, AIE-3 System Resource Flow Figure 37: SV-2b, AIE-3 Pure Fleet System Resource Flow Figure 38: SV-2c, AIE-4 Pure Fleet System Resource Flow Figure 39: SV-2d, AIE-4 Pure Fleet System Resource Flow Figure 40: SV-2e, AIE-58 Large System Resource Flow Figure 41: SV-2f, AIE-58 Small System Resource Flow Figure 42: SV-3, System-System Matrix

System Description and Architecture ix April 2022

Unclassified//For Official Use Only

Figure 43: SV-4-1, AIE-3/4 Major System Decomposition Figure 44: SV-4-2, Registration System Decomposition Figure 45: SV-4-3, IMM Interface System Decomposition Figure 46: SV-4-4, Intercom System Decomposition Figure 47: SV-4-5, Symmetry PACS Decomposition Figure 48: SV-4-6, Video System Decomposition Figure 49: SV-4-7, ACP Lane Control Decomposition Figure 50: SV-4-8, Visitor Registration Website Decomposition Figure 51: SV-4-9, Online Vetting and Registration Figure 52: SV-5a, Operational Activity to Systems Function Traceability Matrix Figure 53: SV-6, System Resource Flow Matrix Figure 54: SV-7, System Measures Matrix Figure 55: OV-10a, System Rules Model Figure 56: Identity Management Middleware Interface Physical Schema Figure 57: Dashboard Table Physical Schema Figure 58: DimSet Table Physical Schema Figure 59: Exceptions Table Physical Schema Figure 60: LaneHoursCount Table Physical Schema Figure 61:Site Table Physical Schema Figure 62:SiteACPID Table Physical Schema Figure 63: TransTimeData Table Physical Schema Figure 64: TransType Values Figure 65: TransSubType2 Type for Scans Values Figure 66: TransSubType2 for Continuous Denials Values Figure 67: TransSubType3 for Continuous Denials Values Figure 68: UserSite Table Physical Schema

System Description and Architecture 1 April 2022

Unclassified//For Official Use Only

1. Scope

The original scope of this document was limited to the Automated Installation Entry, increment 3 (AIE-3) programs as detailed in the AIE-3 Statement of Work, AIE-3

System Performance Specification, and AIE-3 Concept of Operations (CONOPS).

Revision 4 of this document incorporates the evolution of AIE-3 to provide both Pure

Fleet (PF) and AIE-4 functionality and capabilities and include:

➢ Includes fully internet protocol (IP) based lane operations through o the elimination of the Rhino Reader from the architecture replacement with an IP based Qscan reader device.

o elimination of the AMAG door controller and DBU in favor of direct IP communication between the QScan Card Reader.

o use of the Hawkeye Visual Verify software on the Guard Booth Workstation in support of RFID and Qscan processing; and o use of Hawkeye IMM software on the AIE Server or Cache Box

➢ In addition, the document details the integration of cellular wireless to provide alternate communications connectivity when warranted,

➢ replacement of existing handheld devices with upgraded Zebra handheld devices, upgrading to the enhanced visitor Kiosk 2.0,

➢ enhancements to the cloud enabled processing of the system, and

➢ enhancements to online vetting and registration.

1.1 Identification

This document describes the System Architecture (SA) for the AIE-3/4 program using the Department of Defense Architecture Framework (DoDAF) v2.02. This framework was developed to provide an accepted, consistent, integrated, and understandable means to express architectures of complex systems. In accordance with DoDAF v2.02 guidelines, the architecture will be depicted using prescribed diagrams and documents termed “viewpoints”. The format and content of the viewpoints are described in the

DoDAF v2.02 documentation titled, “DoD Architecture Framework v2.0 Volumes 1, 2, and 3”. The list of viewpoints to be provided in this document is defined in Data Item

Description (DID) DI-MGMT-81644A and is listed in Table 1 of the AIE-3 Systems

Engineering Management Plan (SEMP) and in Section A.2.1 of the All Viewpoint 1 (AV-

1) found at Appendix A.

System Description and Architecture 2 April 2022

Unclassified//For Official Use Only

1.2 System Overview

Homeland Security Presidential Directive - 12 (HSPD-12), signed by President George

W. Bush on 27 August 2004, mandated implementation of a government-wide standard for secure and reliable forms of identification issued by the Federal Government to its employees and contractors (including contractor employees). In November 2005, the

Access Control Working Group (ACWG), a standing sub-committee of The Department of the Army Physical Security Review Board, was convened to establish operational requirements for implementation of the AIE Program. As a direct result of this initial meeting, the Charter of the ACWG was changed to incorporate a reference to the Army

Standard for Access Control Points (ACP) and Standard Definitive Design and to add the AIE Program to the Army Transforming Access Control Initiative. A special focus group was designated by the Chairman of the ACWG, and an Integrated Process Team

(IPT) was established to examine specific functional requirements and technical solutions to satisfy the Army access control initiative.

The Joint Program Executive Office for Chemical and Biological Defense (JPEO-CBD) was designated by the Principal Deputy Assistant Secretary of the Army (Acquisition, Logistics and Technology) on 12 August 2008 as the Material Developer for the AIE

Program and has transitioned to Program Executive Office for Intelligence, Electronic

Warfare, and Sensors (PEO-IEWS). The AIE Program is being executed by the office of the Product Manager, Force Protection Systems (PM FPS), Fort Belvoir, Virginia.

The AIE System provides timely, effective, and efficient threat detection necessary for

Installation Commanders to assess and react in all threat environments. AIE automates access control processes for authorized and registered personnel entering an

Installation. AIE improves access/denial accuracy and enables near real-time changes of authentication requirements in response to changes in force protection conditions.

AIE enhances Installation security and improves both pedestrian and vehicle throughput at Access Control Points (ACPs).

System Description and Architecture 3 April 2022

Unclassified//For Official Use Only

The AIE System will be installed at Installations and provide automated access control for vehicular traffic and pedestrians that have been enrolled in the system and are authorized access in accordance with (IAW) the Department of Defense (DoD), Army and Installation Commander’s policies. The System will be modular and scalable to allow future extensions to other security, access control and force protection systems.

The System will be flexible and support future upgrades through incorporation of technical advancements. The AIE System will be used at US Military locations in the

Continental United States (CONUS) and Installations Outside the Continental United

States (OCONUS).

Two previous AIE Systems have been fielded. AIE-1 was fielded at three Installations.

AIE-1 was designed as an interim step to meet the AIE specifications and standards and achieved the Department of Defense (DoD) Information Assurance Certification and

Accreditation Process (DIACAP) as a stand-alone system.

AIE-2 enhanced AIE-1 capabilities. AIE-2 has enterprise capability and achieved

DIACAP accreditation. There are 32 AIE-2 Systems installed. A bridge contract issued to the AIE-2 contractor while waiting for the AIE-3 acquisition augmented the initial AIE-

2 capabilities to include law enforcement (LE) vetting of non-DoD credentials and an interface to Interoperability Layer Services (IoLS) as a replacement for the Defense

Enrollment Eligibility Reporting Service (DEERS) Interface Web Services (IWS). IoLS supports authoritative identity databases including DEERS as well as Continuous

Information Management Engine (CIME) to provide security alerts from enterprise sources including the National Crime Information Center (NCIC) Wanted Persons File.

The AIE-3 System provides a cost-effective system that enhances security of

Installation Access Control Points (ACPs), automates identity authentication and verification of authorized registered personnel entering the Installation, minimizes guard force requirement, maintains, or increases pedestrian and vehicle throughput with enhanced security, and allows for adaptation of increased authentication requirements at high threat levels.

System Description and Architecture 4 April 2022

Unclassified//For Official Use Only

AIE-3 consists of Fixed-Full and wireless Handheld-only configurations. The Fixed-Full configuration includes the wireless handheld capability, but the handheld-only configuration provides AIE-3 capabilities to Installations that do not require the vehicle lane equipment. AIE-3 was also implemented at previously installed AIE-2 locations under the Pure Fleet fielding effort. This solution leverages existing AIE-2 lane equipment where possible to provide previously fielded AIE Installation with full AIE-3 capability.

AIE-4 related functionality and capabilities include elimination of the Rhino Reader from the architecture by replacement with an IP based Qscan reader device; elimination of the AMAG door controller and DBU in favor of direct IP communication between the

QScan Card Reader; use of the Hawkeye Visual Verify software on the Guard Booth

Workstation in support of RFID and Qscan processing; use of Hawkeye IMM software on the AIE Server or Cache Box. AIE-4 is also being implemented at previously installed

AIE-2/3 locations under the Pure Fleet fielding effort. This solution leverages existing

AIE-2/3 lane equipment where possible to provide previously fielded AIE Installation with full AIE-4 capability. AIE-4 also includes the integration of cellular wireless capabilities to provide alternate communications connectivity when warranted;

replacement of existing handheld devices with upgraded Zebra handheld devices;

upgrading to the enhanced visitor Kiosk 2.0; and enhancements to the cloud enabled processing of the system.

1.3 Document Overview

In accordance with DID DI-IPSC-81432A, the AIE-3/4 System-wide Design and

Architecture Description is described in this document. The architecture is described through DID DI-MGMT-81644A designated DoDAF architecture views, and the document is further enhanced with DID DI-IPSC-81434A (Interface Requirements

Specification), DID DI-IPSC-81435A (Software Design Description), DID DI-IPSC-

81436A (Interface Design Description), and DID DI-IPSC-81437A (Database Design

Description).

System Description and Architecture 5 April 2022

Unclassified//For Official Use Only

1.4 Component Definition

The following table identifies the components (with identifier prefix, CMP-) of the AIE-3/4

System.

System Description and Architecture 6 April 2022

Unclassified//For Official Use Only

Component ID Component Name Component Description Component Type Associations

CMP-001 Site Server Set Runs applications at Installation level (Registration Server, Symmetry Server-Site, Identity Management Middleware (IMM) Client, and SQL Server). Supports database for PIR records, and Identity vetting.

Hardware CMP-004, CMP-009, CMP-011, CMP-022, CMP-026, CMP-030

CMP-002 Removed CMP-003 Removed CMP-004 Symmetry Server-Site/Cloud Services to support integration with Registration Server, SQL database, and manage PIR data.

Software CMP-001, CMP-011

CMP-005 Removed CMP-006 Removed CMP-007 Registration Client Application to collect PIR data, print temporary and permanent passes.

Software CMP-009, CMP-022, CMP-026, CMP-039

CMP-008 Symmetry Client Application to support various functions at Guard Booth, Gatehouse, and Central remote monitoring location.

Software CMP-023, CMP-024, CMP-025

CMP-009 IMM Client Identity Management Middleware to interface with vetting services (IoLS and LE Vetting service).

Software CMP-001, CMP-007, CMP-015, CMP-016, CMP-017, CMP-022, CMP-026, CMP-032

CMP-010 Removed CMP-011 SQL Server-Site/Cloud Database management at the Site/App/DB Servers Software CMP-001, CMP-004, CMP-030

CMP-012 Removed

System Description and Architecture 7 April 2022

Unclassified//For Official Use Only

Component ID Component Name Component Description Component Type Associations

CMP-013 Symmetry Gate Controller Access control, input and output interface and intelligence to control automated and manual operations at vehicle and pedestrian lanes. NOTE:

comprised of the DCU and

DBU.

Hardware CMP-035

CMP-13a Symmetry Door Control Unit (DCU) Provides a conduit for barcode data exchanged between the Rhino Reader and DBU.

Hardware CMP-013, CMP-042

CMP-13b Symmetry Database Unit (DBU) Provides a local database of trusted travelers for an installation.

Hardware CMP-001, CMP-013, CMP-041, CMP

CMP-014 Lane Intercom Station Intercom station that allows vehicle driver or pedestrian to initiate call to Guard for assistance.

Hardware CMP-014, CMP-027, CMP-028, CMP-029

CMP-015 IoLS Interoperability Layer Services is a government-managed cloud service that supports identity vetting through multiple authoritative sources and continuous information management engine (NCIC, TSDB, etc.)

External CMP-009

CMP-016 LE Vetting Service Law Enforcement vetting and adjudication service provides a response to an LE vetting request initiated by a CJIS trained operator

External CMP-009

CMP-017 Hawkeye Mobile Software solution that runs on the handheld for registration and validation at the ACP.

Software CMP-009, CMP-018

CMP-018 Removed CMP-018(ALT1) CrossMatch Verifier Sentry Handheld for use at vehicle and pedestrian lanes.

Hardware CMP-017

CMP-018(ALT2) Zebra TC72 Handheld for use at vehicle and pedestrian lanes.

Hardware CMP-017

System Description and Architecture 8 April 2022

Unclassified//For Official Use Only

Component ID Component Name Component Description Component Type Associations

CMP-019 Removed CMP-020 Removed CMP-021 Video Cameras Cameras to capture front of vehicle, rear of vehicle (for vehicle lane), and person’s face (vehicle and pedestrian gates).

Hardware CMP-034

CMP-022 Registration Workstation Workstation for use by the Registrar to register suitable personnel into the AIE-3 system. NOTE: aka Registration Workstation.

(RGWS).

Hardware CMP-001, CMP-007, CMP-009, CMP-039

CMP-023 Lane Control Workstation Touch-enhanced workstation for use by Guard to monitor and control devices at the lane or multiple lanes.

NOTE: aka Guard Booth Workstation. (GBWS).

Hardware CMP-008

CMP-024 ACP Monitoring Workstation Touch-enhanced workstation for use by Guard to monitor and control devices at one or more lanes. NOTE: aka Gatehouse Workstation

(GHWS).

Hardware CMP-008

CMP-025 Remote Monitoring Workstation Touch-enhanced workstation for use by Guard to monitor and control devices at one or more lanes. NOTE: aka Central Monitoring Workstation (CMWS) or (Enhanced Monitoring Workstation) when configured with registration software to be used for dual purpose.

Hardware CMP-008

System Description and Architecture 9 April 2022

Unclassified//For Official Use Only

Component ID Component Name Component Description Component Type Associations

CMP-026 Portable Registration System Transportable system for use by the Registrar (or designee) to register suitable personnel into the AIE-3/4 system outside of the Visitor Center.

Hardware CMP-001, CMP-007, CMP-009, CMP-039

CMP-027 Guard Booth Intercom Station Intercom station that allows Guard to answer and initiate calls from/to the vehicle and pedestrian lanes.

Hardware CMP-014, CMP-027, CMP-028, CMP-029

CMP-028 ACP Intercom Station Intercom station that allows Guard to answer and initiate calls from/to the vehicle and pedestrian lanes.

Hardware CMP-014, CMP-027, CMP-028, CMP-029

CMP-029 Remote Monitoring Intercom Station Intercom station that allows Guard to answer and initiate calls from/to the vehicle and pedestrian lanes.

Hardware CMP-014, CMP-027, CMP-028, CMP-029

CMP-030 Hawkeye Sync Services Service that prepares PIR data at App/DB Servers for synchronization to Cache Box servers.

Software CMP-001, CMP-011, CMP-038, CMP-51

CMP-031 Removed CMP-032 IMM-AutoReg Service that manages the automatic registration process at the vehicle and pedestrian lanes.

Software CMP-009, CMP-033

CMP-033 Rhino Reader Multi-credential reader with display, biometric verification, and PIN pad.

NOTE: Rhino Reader is being eliminated and replaced with Qscan device.

Hardware CMP-032, CMP-013

CMP-034 Symmetry CompleteView Video management subsystem

Software CMP-021

System Description and Architecture 10 April 2022

Unclassified//For Official Use Only

Component ID Component Name Component Description Component Type Associations

CMP-035 RFID Reader Antenna and reader to interact with Ultra-High Frequency (UHF) tags issued to trusted travelers for expedited passage through ACP. NOTE:

operates with Symmetry Gate Controller or Adam Module.

Hardware CMP-013, CMP-032

CMP-036 VCC Kiosk Kiosk system accessible to visitors to the VCC for self-service registration.

Hardware CMP-037

CMP-036 (ALT1) VCC Kiosk 2.0 Iberon Kiosk system accessible to visitors to the VCC for self-service registration.

Hardware CMP-037

CMP-037 AIE Visitor Registration Web Server Hosted web site for visitor self-service input of registration information.

Software CMP-036, CMP-039, CMP-040

CMP-038 SQL Server Enterprise Enterprise cloud host of the SQL Database that houses PIR data store and Installation configuration DB

Software CMP-030, CMP-039

CMP-039 Symmetry Server Enterprise Enterprise cloud host of the Symmetry services that handle database management and the IMM Services that handle vetting and Web input.

Software CMP-007, CMP-022, CMP-026, CMP-037, CMP-038

CMP-040 Visitor Home PC or another browser device Visitor self-service portal (PC, tablet, or phone).

Hardware CMP-037

CMP-041 Adam Module IP enabled input/output device used to provide a method to monitor device status, provide status to Hawkeye IMM, receive commands from Hawkeye IMM, and control devices based on those commands.

Hardware CMP-035, CMP-043, CMP-045

System Description and Architecture 11 April 2022

Unclassified//For Official Use Only

Component ID Component Name Component Description Component Type Associations

CMP-042 Exit Ground Loop with Loop Detector Detects vehicles passing or arriving at a certain point and provides a response signal for processing.

Hardware CMP-013

CMP-043 Gate Arm Mechanical barrier used at the ACP to secure traffic.

Hardware CMP-013, CMP-042

CMP-044 Traffic Light Set of automatically operated lights for controlling traffic at the ACP.

Hardware CMP-CMP057

CMP-045 Barcode Reader Card credential reader that reads 1D and 2D barcodes.

NOTE: Rhino Reader is being eliminated and replaced with Qscan barcode reader display device at installations.

Hardware CMP-032, CMP-013

CMP-046 Mobile Device Management (MDM) Server Enterprise cloud host of the SOTIMobiControl services that handle mobile device management of the handheld devices.

Hardware CMP-018(ALT1), CMP-018(ALT2)

CMP-047 SOTIMobiControl Enterprise cloud host for the SOTIMobiControl services that handle mobile device management of the handheld devices.

Software CMP-018(ALT1), CMP-018(ALT2), CMP-048

CMP-048 SOTIMobiControl Client Client for handheld devices to be managed by Enterprise cloud host SoTIMobiControl services.

Software CMP-018(ALT1), CMP-018(ALT2), CMP-047

CMP-049 Cache Box Runs applications and provides storage for local installation population as a backup to the App/DB Servers.

Hardware CMP-050

System Description and Architecture 12 April 2022

Unclassified//For Official Use Only

Component ID Component Name Component Description Component Type Associations

CMP-050 Cloud Servers Runs applications at Installation level from AIE Enterprise Data Center in the cloud (Registration Server, Symmetry Server- Site, Identity Management Middleware (IMM) Client, and SQL Server). Supports database for PIR records and Identity vetting.

Virtual Machine CMP-004, CMP-009, CMP-011, CMP-022, CMP-026, CMP-030, CMP-38, CMP-39

CMP-051 Hawkeye Visual Verify Application to support various functions at Guard Booth, Gatehouse, and Central remote monitoring location.

Software CMP-23, CMP-24, CMP-25

CMP-052 Iberon Kiosk Software Application to support the operations of the VCC Kiosk 2.0.

Software CMP-036 (ALT1)

CMP-053 Cellular Wireless (Cradlepoint) Provides a cellular wireless link into a connected device.

Also used to provide a cellular point to multi-point link to provide IP connectivity without hard-wired infrastructure.

Hardware CMP-001

CMP-054 Network Video Recorder Records and stores video files from in lane cameras used to perform forensic analysis

Hardware CMP-021, CMP-034

CMP-055 Cloud Server Runs applications at Installation level (Registration Server, Symmetry Server-Site, Identity Management Middleware (IMM) Client, and SQL Server). Supports database for PIR records, and Identity vetting.

Virtual Machine CMP-004, CMP-009, CMP-011, CMP-022, CMP-026, CMP-030

System Description and Architecture 13 April 2022

Unclassified//For Official Use Only

Component ID Component Name Component Description Component Type Associations

CMP-056 OPMG Enterprise Server Provides repository to collect installation scan, registration, and denial data for generating OPMG Dashboard Reports.

Virtual Machine CMP-052

CMP-057 24VDC Relay Controls Traffic Light mechanical operations.

Hardware CMP-041, CMP-044

Figure 1: System Component Definition

System Description and Architecture 14 April 2022

Unclassified//For Official Use Only

2. Reference Documents

2.1 Government Documents

The following documents contribute to this architecture to the extent that they reflect topics and content which relate to the AIE-3/4 requirements and architecture. Unless otherwise specified, the latest revision of the referenced document is in effect.

Documents not specifically identified in the body of this architecture are for reference only.

2.1.1 DoD Documents (in alphabetical order)

a. Army Regulation (AR) 25-1, Army Information Technology, 15 July 2019.

b. AR 25-2, Army Cybersecurity,4 April 2019.

c. AR 70-1, Army Acquisition Policy, 10 August 2018.

d. AR 190-13, Army Physical Security Program, 27 June 2019.

e. AR 700-127, Integrated Logistics Support, 22 October 2018

f. Army Access Control Points Standard Definitive Design, 13 April 2019.

g. Chairman of the Joint Chief of Staff Instruction (CJCSI) 3170.01I Joint

Capabilities Integration and Development System (JCIDS), 23 January

2015.

h. CJCSI 5123.01G, Charter of the Joint Requirements Oversight Council, 30

October 2021

i. Department of the Army (DoA), Office of the Chief Information Officer, Army Information Architecture (AIA) v4.1, 5 June 2013.

j. DoD Architecture Framework (DoDAF) v2.02, Change 1, Volumes I, II, III, & IV, January 2015.

k. DoD Direction (DoDD) 5101.07, DoD Executive Agent for Information

Technology Standards, 21 May 2004.

l. DoD, Office of the Chief Information Officer, DoD Information Enterprise

Architecture (IEA) v2.0, Volume I, August 2012.

System Description and Architecture 15 April 2022

Unclassified//For Official Use Only

m. DoD, Office of the Chief Information Officer, DoD Information Enterprise

Architecture (IEA) v2.0, Volume II, August 2012.

n. DoD Information Technology Standards Repository (DISR), (See DoDD

5101.07, May 2004).

o. DoDI 5200.08, Security of DoD Installations and Resources and the DoD

Physical Security Review Board (PSRB), May 19, 2010, Incorporating

Change 3, Effective: 20 November 2015.

p. DoD 5200.08R, Physical Security Program, April 9, 2007, Incorporating

Change 2, 19 October 2020.

q. DoDI 8500.01, Cybersecurity, 14 March 2014, Incorporating Change 1, Effective: 7 October 2019.

r. DoDI 8510.01, Risk Management Framework for DoD Information

Technology, 29 December 2020.

s. DoDI 8580.1, Information Assurance (IA) in the Defense Acquisition

System, 9 July 2004.

t. Military Standard (MIL-STD) 810, Environmental Engineering

Considerations and Laboratory Tests, latest revision (G or later). 810G with Change 1, Effective 15 April 2014

u. Security Equipment Integration Working Group (SEIWG) Interface Control

Document (ICD) 0101B, Force Protection Systems Sensor Information

Interchange Information Interchange using XML, June 2011.

v. Unified Capabilities Requirements (UCR) 2013, Unified Capabilities

Requirements 2013, January 2013, Change 2, Effective 2 September

2017.

2.1.2 Other Government Documents

a. Criminal Justice Information Services, Electronic Fingerprint Transmission

Specification (EFTS), July 2013.

b. Criminal Justice Information Services, Electronic Biometric Transmission

Specification (EBTS), 14 December 2012.

System Description and Architecture 16 April 2022

Unclassified//For Official Use Only

c. Criminal Justice Information Services 6510.01F Information Assurance

(IA) and Computer Network Defense (CND) 9 June 2015.

d. Department of Labor (DOL), Americans with Disabilities Act: Accessibility

Guidelines for Buildings and Facilities (ADAAG), Latest Revision/Update.

e. Federal Highway Administration (FHWA), Installation of Traffic Control

Devices, FHWA-SA-89-006, March 1988.

f. FIPS 140-3: Security Requirements for Cryptographic Modules. National

Institute for Standards and Technology (NIST) Computer Security

Resource Center (CSRC). 22 March 2019

g. FIPS 201-3: Personal Identity Verification (PIV) of Federal Employees and

Contractors. NIST CSRC. January 2022

2.1.3 Code of Federal Regulations (CFR)

a. 36 CFR Part 1194, Electronic and Information Technology Accessibility

Standards.

2.1.4. AIE-3/4 Program Documents

a. AIE Standards and Specifications November 19, 2007.

b. System Performance Specification for AIE-3, 22 October 2014.

c. AIE-3 Concept of Operations (CONOPS), 8 September 2014.

d. AIE-3 Statement of Work (SOW) 6 November 2014.

e. Additional clarifying requirements.

• Rhino Elimination, July 2021

• Kiosk 2.0, March 2020

• Dashboard, March 2022

• Network, January 2022

2.2 Non-Government Documents

a. American National Standards Institute/National Institute of Standards and

Technology- ITL 1-2011, updated 2015

System Description and Architecture 17 April 2022

Unclassified//For Official Use Only

b. American National Standards Institute/National Institute of Standards and

Technology- ITL 1-2011, updated 2013.

c. National Fire Protection Association (NFPA) 72, National Fire Alarm

Code®, 2022 (or latest revision).

2.3 Order of Precedence: The contractor applies precedence in accordance with the post-award clarification, SOW, the System Architecture (this document), the System

Performance Specification and the Concept of Operations, respectively. The various

Specification documents detail the technical requirements of the system and/or component. However, nothing in this document supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. AIE-3/4 System-Wide Design Decisions

The AIE-3/4 System is an incremental improvement of the Army’s fielded and operational AIE-2 system solution. Previous AIE increments were designed around a combination of COTS products and proprietary, non-COTS hardware and software.

This posed significant challenges for transferring support and sustainment to the government beyond the contractor support period. The design of AIE-3/4 addresses this issue by being composed entirely of widely supportable, field-tested, and proven

COTS hardware and software components. These design choices result in a significantly lower total cost of ownership (TCO) to the Government.

The AIE-3/4 System is designed to meet or exceed all required performance capabilities, including all key capabilities. Subsystems and components of the AIE-3/4

System have been selected for integrated system performance; relevant DoD physical security systems program experience; industry best practices; and long-term availability, supportability, and upgradability.

In addition, because the AIE-3/4 System is composed entirely of COTS products, the systems and equipment are constantly evolving to deliver new features, better performance, and supported integrations at no direct cost to the Government. The

System Description and Architecture 18 April 2022

Unclassified//For Official Use Only primary AMAG Symmetry Access Control System (ACS), IoLS and LE Vetting Services include published application programming interfaces (APIs) and software development kits (SDKs) to facilitate integrations.

The AIE-3/4 System takes advantage of open architecture and cloud computing concepts to provide an on-premises and hybrid enterprise cloud solution. Cloud capabilities are procured and managed under the Infrastructure as a Service (IaaS) model, where all the environment is ‘rented’, and the program retains full control over the environment with respect to VM creation, network/firewall configuration, in addition to control over the Operating Systems and application on the VM servers. This approach allows Installation to share support Infrastructure, allowing for cost reduction and greater visibility into the Enterprise.

The AIE-3/4 network architecture leverages the existing Army network infrastructure backbone, in accordance with NETCOM guidance. Local networking is provided by the

Installation over existing Non-secure Internet Protocol Router Network (NIPRnet) circuits, or by dedicated Fiber connecting AIE endpoints. External connections to both the cloud environment, and supporting external services is provided through the

Installations connection to the Joint Regional Security Stack (JRSS) housed within the

Network Enterprise Center (NEC). The IPSEC based site to site VPN connections are utilized between the cloud and the individual Installations, providing for continuous secure links, which enhances the capabilities provided by the IaaS cloud component.

4. System Architectural Design

In accordance with DID DI-MGMT-81644A, the AIE-3/4 architecture is described through DoDAF viewpoints (diagrams and documents) in the format prescribed by

DoDAF v2.02. The following DoDAF artifacts are provided to describe the Systems description and architecture.

System Description and Architecture 19 April 2022

Unclassified//For Official Use Only

4.1 All Viewpoint 1 (AV-1): Overview and Summary Information

The AIE-3/4 AV-1 Overview and Summary document outlines the content, justification, and point of reference of the targeted architecture and encompasses the entire architecture. It lists the elements to be contained in the architecture, the organizational, programmatic and system documentation which provide the justification for creating the architecture and the enterprise points of reference which provide an anchor point for the development of the architecture artifacts. The AIE-3/4 AV-1 is provided as Appendix A.

4.2 All Viewpoint 2 (AV-2): Integrated Dictionary

The AIE-3/4 AV-2 Integrated Dictionary includes terms, abbreviations and acronyms that are system or topic unique found in the architecture. The AIE-3/4 AV-2 is provided as Appendix B.

4.3 Operational Viewpoint 1 (OV-1): High Level Operational Concept Graphic

The AIE-3/4 OV-1 provides a high-level graphical view of the system activities, elements, organizations, and external entities. The view includes system elements as well as external elements with which the AIE-3/4 will interface and support or which will provide support to AIE-3/4. The AIE-3 OV-1 is provided as Appendix C.

4.4 Operational Viewpoint 2 (OV-2): Operational Node Connectivity Description

The AIE-3/4 OV-2 provides a view depicting operational resource flows between the

AIE-3/4 activities. The direction of resource flow and type of resource is identified. The

AIE-3/4 OV-2 is provided as Appendix D.

4.5 Operational Viewpoint 3 (OV-3): Operational Information Exchange Matrix

The AIE-3/4 OV-3 is a matrix with the operational activities arrayed across the axes and the resource exchanges identified between the activities. The AIE-3/4 OV-3 is provided as Appendix E.

System Description and Architecture 20 April 2022

Unclassified//For Official Use Only

4.6 Operational Viewpoint 4 (OV-4): Organizational Relationships Chart

The AIE-3/4 OV-4 depicts the relationship between the various organizations which perform the activities depicted in the other operational views. It details the context, roles, and other relationships among the organizations. The AIE-3/4 OV-4 is provided as Appendix F.

4.7 Operational Viewpoint 5 (OV-5): Operational Activity Model

The AIE-3/4 OV-5 depicts the Capabilities, operational activities, relationships among activities, inputs, and outputs; overlays can show cost, performing nodes, or other pertinent information organized hierarchically to provide a context for understanding their relationships. The AIE-3/4 OV-5 is provided as Appendix G.

4.8 Operational Viewpoint 6a (OV-6a): Operational Rules Model

The AIE-3/4 OV-6a depicts the operational rules that govern the activities and the organizations performing the activities. These are the “business” rules which constrain operations. The AIE-3/4 OV-6a is provided as Appendix H.

4.9 Operational Viewpoint 6b (OV-6b): Operational State Transition Description

The AIE-3/4 OV-6b depicts how the activities react to events and how they change or adjust their course as the operational flow of events unfolds. The AIE-3/4 OV-6b is provided as Appendix I.

4.10 Operational Viewpoint 6c (OV-6c): Operational Event Trace Description

The AIE-3/4 OV-6c depicts the sequential flow of events and how they may alter their course (branches) due to operational conditions. The AIE-3/4 OV-6c is provided as

Appendix J.

4.11 Operational Viewpoint 7 (OV-7): Logical Data Model

The AIE-3/4 OV-7 depicts the system data requirements and structural business process rules of the Operational View. The AIE-3/4 OV-7 is provided as Appendix K.

System Description and Architecture 21 April 2022

Unclassified//For Official Use Only

4.12 Systems Viewpoint 1 (SV-1): Systems Interface Description

The AIE-3/4 SV-1 depicts the systems, system components and elements and their interconnections. The AIE-3/4 SV-1 is provided as Appendix L.

4.13 Systems Viewpoint 2 (SV-2): Systems Communications Description

The AIE-3/4 SV-2 depicts the systems, system components and their elements, and the system resource flows between the systems. The AIE-3/4 SV-2 is provided as

Appendix M.

4.14 Systems Viewpoint 3 (SV-3): Systems-Systems Matrix

The AIE-3/4 SV-3 provides a tabular summary of the system interactions depicted in

SV-1 & SV-2. The AIE-3/4 SV-3 is provided as Appendix N.

4.15 Systems Viewpoint 4 (SV-4): Systems Functionality Description

The AIE-3/4 SV-4 depicts the functions performed by the various parts of the system, their relationships, and the data/resources shared between the functions. The AIE-3/4

SV-4 is provided as Appendix O.

4.16 Systems Viewpoint 4a (SV-4a): Systems Functionality Description

The AIE-3/4 SV-4a depicts the system functional hierarchies and system functions, and the system data flows between them. The AIE-3/4 SV-4a is provided as Appendix P.

4.17 Systems Viewpoint 4b (SV-4b): Systems Functionality Description

The AIE-3/4 SV-4b depicts the service functionality that is exposed to the Net-Centric

Environment, their respective grouping into service families, and their service specifications. The AIE-3/4 SV-4b is provided as Appendix Q.

4.18 Systems Viewpoint 5 (SV-5): Operational Activity to Systems Function

Traceability Matrix

The AIE-3/4 SV-5 depicts the mapping of systems back to capabilities or of system functions back to operational activities. The AIE-3/4 SV-5 is provided as Appendix R.

System Description and Architecture 22 April 2022

Unclassified//For Official Use Only

4.19 Systems Viewpoint 5a (SV-5a): Operational Activity to Systems Function

Traceability Matrix

The AIE-3/4 SV-5a depicts the mapping of operational activities to system functions and thus identifies the transformation of an operational need into a purposeful action performed by a system. The AIE-3/4 SV-5a is provided as Appendix S.

4.20 Systems Viewpoint 5b (SV-5b): Operational Activity to Systems Function

Traceability Matrix

The AIE-3/4 SV-5b extends the SV-5a and depicts the mapping of capabilities to operational activities, operational activities to system functions, system functions to systems, and thus relates the capabilities to the systems that support them. The AIE-

3/4 SV-5b is provided as Appendix T.

4.21 Systems Viewpoint 5c (SV-5c): Operational Activity to Systems Function

Traceability Matrix

The AIE-3/4 SV-5c depicts the traceability and mapping of services to operational activities to assist in understanding which services support operational activities. The

AIE-3/4 SV-5c is provided as Appendix U.

4.22 Systems Viewpoint 6 (SV-6): Systems Data Exchange Matrix

The AIE-3/4 SV-6 provides details of system data elements being exchanged between systems and the attributes of that exchange. The AIE-3/4 SV-6 is provided as Appendix

V.

4.23 Systems Viewpoint 7 (SV-7): Systems Performance Parameters Matrix

The AIE-3/4 SV-7 provides performance characteristics of Systems View elements for the appropriate time frame(s). The AIE-3/4 SV-7 is provided as Appendix W.

4.24 Systems Viewpoint 8 (SV-8): Systems Evolution Description

The AIE-3/4 SV-8 provides planned incremental steps toward evolving the older AIE-1 and AIE-2 systems to the AIE-3/4 implementation. The AIE-3/4 SV-8 is provided as

Appendix X.

System Description and Architecture 23 April 2022

Unclassified//For Official Use Only

4.25 Systems Viewpoint 9 (SV-9): Systems Technology Forecast

The AIE-3/4 SV-9 provides details of emerging technologies and software/hardware products that are expected to be available in each set of time frames and that will affect future development of the architecture. The AIE-3/4 SV-9 is provided as Appendix Y.

4.26 Systems Viewpoint 10a (SV-10a): Systems Rules Model

The AIE-3/4 SV-10a identifies constraints that are imposed on systems functionality due to some aspect of systems design or implementation. The AIE-3/4 SV-10a is provided as Appendix Z.

4.27 Systems Viewpoint 10b (SV-10b): Systems State Transition Description

The AIE-3/4 SV-10b identifies responses of a system to events. The AIE-3/4 SV-10b is provided as Appendix AA.

4.28 Systems Viewpoint 10c (SV-10c): Systems Event-Trace Description

The AIE-3/4 SV-10c identifies system-specific refinements of critical sequences of events described in the Operational View. The AIE-3/4 SV-10c is provided as Appendix

BB.

4.29 Systems Viewpoint 11 (SV-11): Physical Schema

The AIE-3/4 SV-11 describes the physical implementation of the Logical Data Model entities, e.g., message formats, file structures, physical schema. The AIE-3/4 SV-11 is provided as Appendix CC.

4.30 Technical Viewpoint 1 (TV-1): Technical Standards Profile

The AIE-3/4 TV-1 provides a listing of standards that apply to Systems View elements in the given architecture. The AIE-3/4 TV-1 is provided as Appendix DD.

System Description and Architecture 24 April 2022

Unclassified//For Official Use Only

4.31 Technical Viewpoint 2 (TV-2): Technical Standards Forecast

The AIE-3/4 TV-2 provides a description of emerging standards and potential impact on current Systems View elements, within a set of time frames. The AIE-3/4 TV-2 is provided as Appendix EE.

System Description and Architecture 25 April 2022

Unclassified//For Official Use Only

5. Requirements Traceability Matrix

RTM ID Requirement ID Requirement Description Source Document Operational

Area AIE-3/4 Design Component Comment

1 SS_100 The System shall perform verification of the user’s (user is defined as personnel presenting credentials to gain access onto an Installation) credentials when the user presents a valid credential during registration.

AIE-3 System Performance Specification

Registration Registration Client

2 SS_101 The System shall vet credentials with authoritative databases through IoLS and populate registration fields without the operator having to re-key information. The System will connect to IoLS for access to DEERS, the local database, NCIC and out to the Federal Bridge. (Modification) The government waives this portion of the requirement: The System will connect to DEERS, independently of IoLS and be available in the event IoLS is unavailable.

AIE-3 System Performance Specification

Registration [Multiple Requirements are delineated below]

The System shall vet credentials with authoritative databases through IoLS.

SS_101 Registration IMM Client

The System shall populate registration fields without the operator having to re-key information.

SS_101 Registration Registration Client

The System will connect to IoLS for access to DEERS.

SS_101 Registration IMM Client

The System will connect to the local database.

SS_101 Registration Registration Server

System Description and Architecture 26 April 2022

Unclassified//For Official Use Only

The System will…