Training Guide

Open-Platform Security Screening, AI-Assisted Monitoring, and Operational Accountability

Table of Contents 

1. Introduction to the Athena WDS AI Software Platform

2. System Components and Compatible Hardware

3. System Communication and Connection Status

4. Weapons Detection System Testing

5. Security Officer Check-In and Accountability

6. Detection Alerts and Secondary Screening

7. False Alerts and Confirmed Threats

8. Incident Response Reports (IRR)

9. Driver's License Scanning and Person of Interest Management

10. AI-Assisted Screening Oversight

11. Turn Around and Event Documentation

12. Alert Status and Reporting

13. Security Operations Best Practices

14. Support and Troubleshooting

1. Introduction to the Athena WDS OPEN AI Platform

The Athena Security Weapons Detection System (WDS) OPEN Platform is an AI-assisted, open-platform security solution designed to help organizations monitor screening operations, manage alerts, document incidents, and maintain consistent security procedures across multiple entrances and facilities.

Unlike systems limited to a single hardware manufacturer, the Athena Platform is designed to work with compatible weapons detection equipment from multiple manufacturers, enabling organizations to select hardware based on their unique operational and security requirements.

The platform supports Athena's Apollo 500 and Apollo 650 Weapons Detection Systems and integrations with select third-party systems, including models from CEIA, Garrett, Metrasens, and other manufacturers.

Detection and software responsibilities

The connected screening equipment performs the physical weapons detection. The Athena Platform provides an additional operational software layer that can include:

• Centralized screening alerts and monitoring

• AI-assisted screening bypass detection

• Security officer check-in and accountability

• Equipment testing workflows and documentation

• Secondary screening and incident reporting

• Confirmed and false alert documentation

• Security event images and reporting

• Multi-entrance and multi-location management

These capabilities help organizations implement consistent security procedures informed by applicable Department of Homeland Security (DHS) screening guidance and their own security policies.

Important: Available features, detection performance, object identification, and integration capabilities vary by the connected hardware, configuration, software version, and enabled Athena modules. No screening system can guarantee detection of every prohibited item.

2. System Components and Compatible Hardware

The Athena WDS Platform combines compatible screening hardware with software components configured for the facility's operational needs.

A. Weapons Detection Hardware

The physical screening device detects objects according to its technology, sensitivity settings, and manufacturer's specifications.

Examples of equipment supported through compatible Athena integrations include:

• Athena Apollo Weapons Detection Systems

• Select CEIA products including OPENGATE and other walk-through metal detector models

• Select Garrett PD 6500i and Paragon models

• Metrasens Ultra

• Other approved and supported equipment

Different manufacturers and models use different sensing technologies. Detection characteristics, sensitivity, threat localization, and screening capabilities are determined by the hardware and its configuration.

B. Controller Tablet

Where required by the deployment, the Controller Tablet serves as the local processing and communication component of the Athena Platform.

Depending on the installed configuration, it may support:

• Camera-based screening monitoring

• LiDAR or other available sensing capabilities

• AI-assisted analysis

• Communication with the Operator Tablet

• Screening events and alerts

• Additional operational monitoring

The Controller Tablet may be mounted on a wall, stand, ceiling, or other approved location.

Installation note: Placement, mounting distance, camera positioning, and supported functions depend on the site-specific installation plan. Follow the approved installation instructions rather than assuming one placement works for every hardware model.

C. Operator Tablet

The Operator Tablet provides the primary user interface for security personnel.

Depending on the system configuration, officers can use the tablet to:

• Review screening alerts

• Complete security officer check-ins

• Conduct and document WDS tests

• Classify and resolve alerts

• Create Incident Response Reports

• View previous incidents

• Access enabled identification and watchlist tools

• Contact Athena Support

The Operator Tablet should remain accessible to the assigned security officer during active screening operations.

D. System Connectivity

Athena supports several connection methods depending on the hardware and deployment, potentially including Ethernet (RJ45), Bluetooth, serial interfaces, Wi-Fi, and camera-based integration.

Not every connection method or platform feature is supported by every device. Refer to Athena's approved compatibility documentation for the specific installation.

3. System Communication and Connection Status

The Operator Tablet displays communication status in the upper-right portion of the screen.

Green Connection Indicator

A green indicator means the configured Operator and Controller components are communicating as expected.

Red Connection Indicator

A red indicator means the expected communication connection is unavailable.

If the connection indicator is red:

1. Check that the required tablets and connected equipment are powered on.

2. Verify that the configured network or local connection is available.

3. Check for disconnected cables or other visible connection issues.

4. Follow the facility's established procedure for an unavailable screening system.

5. Contact Athena Support if the connection cannot be restored.

Important: A green connection indicator does not, by itself, confirm that the detection hardware is functioning correctly or has passed its required operational test.

4. Weapons Detection System Testing

Routine testing helps verify that screening equipment operates according to its configured detection requirements and the facility's security policies.

The Athena Platform provides testing workflows and electronic records for supported configurations.

Starting a WDS Test

1. On the Operator Tablet, select Start WDS Test.

2. Follow the instructions displayed on the screen.

3. The system may enter a dedicated test mode for approximately 10 minutes, depending on its configuration.

4. Where supported, the Controller Tablet will display or announce that the system is in WDS Test Mode.

5. Perform the prescribed test for the installed detection hardware.

WDS Testing Procedure

The testing process must be appropriate for the connected manufacturer's equipment, approved test objects, configured sensitivity, and applicable screening requirements.

For configurations using Athena's nine-position test:

1. Use the approved test object, such as the supplied AM7 test piece where specified.

2. Follow the nine-position testing template displayed on the Controller Tablet.

3. Walk through the detection area as instructed.

4. Verify that each required test produces the expected system response.

5. Complete all required positions.

6. Record the results in the Athena Platform.

Clean Tester Requirements

Personnel performing tests should remove unnecessary metallic objects, personal electronics, watches, and other items that could affect the test, as required by the approved protocol.

A clean tester helps reduce interference and supports more consistent testing.

Equipment-Specific Testing

Not all compatible devices use the same test object, test positions, or procedures.

Always follow the approved testing protocol for the installed equipment.

For example, a nine-position AM7 test procedure should not automatically be applied to another detection technology unless Athena and the applicable equipment documentation specify that procedure.

Testing Records and Accountability

After completing the test, the operator should enter the requested information, including:

• Testing officer identification

• Date and time

• Equipment or screening location

• Test results

• Any failed or incomplete steps

• Additional comments, where necessary

These records help supervisors review testing activity and identify possible operational problems.

If a system fails its required test, notify the appropriate supervisor, follow the facility's out-of-service or alternative-screening procedure, and arrange corrective action before returning the equipment to normal use.

Testing Frequency

Testing frequency should follow the equipment manufacturer's instructions, applicable requirements, and the facility's approved security policy.

Athena recommends establishing a documented routine, including checks before operational use where appropriate and after relevant equipment changes, relocation, or service.

5. Security Officer Check-In and Accountability

The Athena Platform supports security officer accountability by documenting which personnel are assigned to operate supported screening stations.

Adding a Security Officer

1. On the Operator Tablet, select Add Security Officer Check-In.

2. Follow the displayed instructions.

3. If camera-based verification is enabled, position your face within the indicated area.

4. When prompted, enter your name or assigned user identification.

5. Select Save to complete the check-in.

The officer is now associated with the screening position according to the system's configured check-in workflow.

Periodic Officer Check-Ins

Management may configure periodic check-in intervals, such as every 15 or 30 minutes.

When prompted:

1. Follow the check-in notification.

2. Complete the required verification.

3. Confirm that the Operator Tablet displays Check-In Complete.

This process helps supervisors maintain records of officer presence and screening post accountability.

Periodic check-ins supplement, but do not replace, active supervision and required staffing.

6. Detection Alerts and Secondary Screening

When compatible screening hardware generates a detection event, the Athena Platform can display the event on the Operator Tablet.

The available information may include:

• Detection notification

• Time and screening location

• Hardware-provided detection details

• Available object location or classification information

• Camera imagery or additional event context, if enabled

• Operator response options

Object detection information varies by hardware. Some equipment provides general alarm information, while other models can provide more detailed location or classification information.

Responding to a Detection Alert

When an alert appears:

1. Review the alert on the Operator Tablet.

2. Follow the facility's established security response procedure.

3. Conduct any necessary secondary screening using approved methods.

4. Identify the item or cause of the alert when possible.

5. Select the appropriate event classification.

6. Document the screening result.

Security personnel must not assume that an alarm automatically confirms the presence of a weapon.

7. False Alerts and Confirmed Threats

The Athena Platform supports documentation of screening outcomes to help maintain accountability and create records for later operational review.

False Alerts

If secondary screening establishes that the alert was not associated with a prohibited threat, the officer may select False.

1. Select False on the alert.

2. Choose or enter the reason for the classification.

3. Save the response.

The event will be classified and recorded according to the site's retention and reporting configuration.

If an officer later determines that the alert was incorrectly classified, authorized users may review and update it through the Status feature.

Confirmed Threats

If screening verifies a prohibited item or other reportable threat, the officer should select Confirm.

1. Select Confirm on the alert.

2. Identify the item or incident category.

3. Follow the facility's response and escalation procedures.

4. Complete the required incident documentation.

Depending on the configuration, confirmed events may remain available for management review, reporting, and investigation.

Important: Officers should classify alerts using verified observations rather than assumptions. An unidentified alarm should not automatically be recorded as a confirmed weapon or a false alert.

8. Incident Response Reports (IRR)

The Incident Response Report feature allows security personnel to document events occurring during screening operations.

An IRR may be created following a confirmed detection alert or independently when an incident requires documentation.

Completing an Incident Response Report

After confirming an alert, the officer may be prompted to create an Incident Response Report.

The report can include:

• Incident date and time

• Screening location

• Officer identification

• Type of prohibited item or incident

• Description of events

• Action taken

• Additional observations

• Photographs of relevant items, if authorized and enabled

The IRR helps create a documented record of what occurred and how security personnel responded.

Creating an IRR Without an Alert

To create a report independently:

1. Select IRR at the bottom of the Operator Tablet.

2. Enter the required incident information.

3. Attach any authorized supporting documentation.

4. Review the report for accuracy.

5. Submit the report.

Viewing Incident Reports

Select Show Incidents on the Operator Tablet.

Authorized personnel can review available Incident Response Reports and use the applicable date filters to locate records.

Record availability depends on user permissions, retention settings, and system configuration.

9. Driver's License Scanning and Person of Interest Management

The Athena Platform offers optional identification and Person of Interest (POI) management features for organizations that enable these capabilities.

These functions are not required for normal weapons detection screening and may be disabled by default.

Driver's License Scanning

Where enabled and authorized:

1. Select Scan Driver's License on the Operator Tablet.

2. Scan the barcode on the supported identification document.

3. Review the information displayed by the system.

4. Follow the facility's approved procedures for using or retaining that information.

Available fields depend on the identification document, supported barcode format, and customer configuration.

Person of Interest (POI) Management

Authorized users may be permitted to create or update POI records in accordance with the facility's policies.

If the feature is enabled:

1. Review the available identification information.

2. Confirm that adding a POI is authorized and appropriate.

3. Complete any required supervisor approval or officer PIN verification.

4. Enter the required information and permitted notes.

5. Save the record.

Access to POI information should be restricted according to the customer's configured permissions.

Privacy Notice

Identification collection, POI management, photographs, and related records should only be used when authorized and consistent with applicable laws, contractual obligations, and the organization's privacy policies.

Customer settings determine which information is collected, retained, restricted, or deleted.

10. AI-Assisted Screening Oversight

Athena's AI-assisted software can provide additional monitoring of screening operations when the applicable features and required cameras or sensors are installed.

Screening Bypass Detection

Where enabled, Athena's Screening Bypass Detection capability analyzes supported camera views to identify potential attempts to move around or avoid the designated screening area.

When a potential bypass is identified, the platform can notify designated security personnel for review.

This capability can help officers identify events that require attention beyond ordinary hardware detection alarms.

Important: Bypass monitoring is a software-based operational feature. It is separate from the connected equipment's physical weapons detection capabilities. Performance depends on camera coverage, placement, environmental conditions, and configuration.

Consistent Screening Workflows

Athena helps organizations implement standardized operational procedures across supported screening locations, including:

• Officer check-ins

• Equipment testing documentation

• Alarm classification

• Secondary screening documentation

• Incident reporting

• Review of recorded events

This can provide a common operational framework when an organization uses multiple compatible detection systems.

11. Turn Around and Event Documentation

The Turn Around feature allows authorized officers to capture an image associated with a screening-related event where the capability is enabled.

The feature may be used to document a person turning away from a screening checkpoint or another event requiring review.

Using Turn Around

1. Select Turn Around on the Operator Tablet.

2. Follow the on-screen instructions.

3. Review the captured event information where available.

4. Complete any required incident report or follow-up.

This feature should be used only for legitimate security purposes, consistent with approved operating procedures and privacy requirements.

A person turning away from screening does not, by itself, establish that the person was carrying a prohibited item or attempting a crime.

12. Alert Status and Reporting

The Status feature allows officers to review and filter available screening events.

Depending on the configured workflow, filters may include:

• Action Required

• False Alerts

• Confirmed Threats

• Other available event classifications

Reviewing Alert Status

1. Select Status in the upper-right corner of the Operator Tablet.

2. Choose the appropriate filter.

3. Review the available events.

4. Update an event classification when authorized and necessary.

On applicable software versions, the Operator Tablet returns automatically to the Action Required filter after approximately 10 minutes.

Centralized Reporting

Where enabled, the Athena Platform supports centralized review of available operational information across multiple screening stations or sites.

This may include equipment tests, operator activity, recorded detection events, incident reports, and relevant screening workflows.

Reporting availability depends on supported integrations, customer settings, network connectivity, and data retention policies.

13. Security Operations Best Practices

Athena's software helps organizations carry out and document security procedures informed by applicable DHS guidance, equipment manufacturer instructions, and facility policies.

Officers should:

• Verify screening equipment is operational before use.

• Perform required equipment testing.

• Complete assigned check-ins.

• Monitor and respond to screening alerts.

• Conduct secondary screening according to approved procedures.

• Accurately distinguish confirmed findings from false alerts.

• Document reportable incidents.

• Follow facility escalation procedures.

• Notify supervisors when equipment or communication issues occur.

• Protect personal information and incident records.

The Athena Platform supports operational consistency and documentation. It does not replace officer judgment, required training, manufacturer instructions, or applicable regulatory obligations.

14. Support and Troubleshooting

Athena Security provides 24/7 technical support for its software platform and supported integrations.

To contact Support:

1. Select Support in the upper-right corner of the Operator Tablet.

2. Choose the available support or ticket option.

3. Describe the issue and provide the affected screening location or equipment details.

4. Follow the instructions provided by the support team.

Athena Support Phone: +1-833-928-4362

Support Website: https://support.athena-security.com

For hardware-specific failures, repairs, or maintenance, follow the applicable manufacturer's support requirements and Athena's agreed support responsibilities.

Independent Platform and Third-Party Compatibility Notice

Athena Security is an independent, open-platform security AI technology provider. Its software may integrate with compatible third-party screening equipment without requiring a current commercial partnership with the equipment manufacturer.

Athena Security is not currently affiliated with, endorsed by, sponsored by, or partnered with CEIA. References to CEIA, OPENGATE, Garrett, Metrasens, and other third-party equipment are provided solely to identify supported products and describe applicable compatibility.

All third-party trademarks belong to their respective owners.

Hardware compatibility, detection capabilities, integration methods, and available software features may vary by model, firmware, configuration, and deployment.

Athena Security — One Platform. Multiple Hardware Options. Consistent Security Operations.