ATTACHMENT_1_-_SALIENT_CHARACTERISTICS.pdf

Hand Held Portable UHF Radio – Designed to be carried in a radio holder on person. Radios must be shipped with all required equipment including antennas, two batteries per radio, removable belt clips and programming. Also, required programming software, OEM hardware, and cables.

• All features of the devices must be tested with verification for use on the Navy ELMR ASTRO 7.17.3 system prior to this solicitation. This includes all management capabilities such as OTAR and OTAP.

MANAGEMENT CAPABILITIES OF RADIOS OVER ELMR NETWORK:

o All radios must use Over the Air Programming (OTAP) through the ELMR network. o All radios are managed by existing OTAP programming software, OTAP client, and ELMR OTAP servers / infrastructure.

It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAP. This would invalidate the current ATO and incur additional cost.

All radios must leverage the existing OTAP infrastructure capabilities such as presence notification which provides batch programming capability as well as dynamic management of radio IP addresses. In addition, OTAP will prioritize voice over data and resume stopped sessions that are interrupted -preserves OTAP and network efficiency. Radios must utilize OTAP partial codeplug rewrite – capability ensures radios are able to efficiently receive updates while not impacting radio operation and preserves ELMR network resources.

All radios must utilize automated OTAR and Bulk OTAR for rekey via the key loss function.

All radios must be manageable by the existing Key Management Facility (KMF) to allow for both Clear and Secure Hello packets and radio Kill functions. It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAR. This would invalidate the current ATO and incur additional cost.

All radios must have P25 Link Layer Authentication via in place infrastructure server, preserving network security and to ensure no cloning of radios and ID’s can take place. Radio authentication must pass the APCO P25 Compliance Acceptance Program (CAP) testing process on a Motorola ASTRO 7.17.3 Trunk Infrastructure.

All radios must utilize Multi-key Encryption meaning the ability to have multiple encryption keys on the same radio with different keys assigned to different Talk Groups on a per Channel basis, and a separate data key.

Radios must use integrated voice and data (IV&D). Includes capability for group messaging, text messaging to enable interoperability as well as OTAP and OTAR.

All voice must be given priority over data for radios on the LMR network.

Radio must have capability for ASTRO Enhanced Data and transmit of GPS on PTT features for location services such as dynamic GPS polling.

All radios include integrated GPS without additional hardware on the subscriber.

All radios must be optimized for radio user roaming on Motorola infrastructure. This includes optimization for data session roaming. This allows for continuous site preference, assignment updating and seamless roaming during data transfers.

All radios must have capability for User Alias Update through the ASTRO 7.17 infrastructure.

All radios must have DoD JF-12.

All radios must have a minimum of fifteen channels per zone. Removable rechargeable batteries. Meet IP68 dust and waterproof standard. Microphone and speaker attachment. Include a duress button capable of notifying the regional dispatch center.

Motorola Battery charger APX insert adapter for XTS

• All features of the devices must be tested with verification for use on the Navy ELMR ASTRO 7.17.3 system prior to this solicitation. This includes all management capabilities such as OTAR and OTAP.

MANAGEMENT CAPABILITIES OF RADIOS OVER ELMR NETWORK:

o All radios must use Over the Air Programming (OTAP) through the ELMR network. o All radios are managed by existing OTAP programming software, OTAP client, and ELMR OTAP servers / infrastructure.

It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAP. This would invalidate the current ATO and incur additional cost.

All radios must leverage the existing OTAP infrastructure capabilities such as presence notification which provides batch programming capability as well as dynamic management of radio IP addresses. In addition, OTAP will prioritize voice over data and resume stopped sessions that are interrupted -preserves OTAP and network efficiency. Radios must utilize OTAP partial codeplug rewrite – capability ensures radios are able to efficiently receive updates while not impacting radio operation and preserves ELMR network resources.

All radios must utilize automated OTAR and Bulk OTAR for rekey via the key loss function.

All radios must be manageable by the existing Key Management Facility (KMF) to allow for both Clear and Secure Hello packets and radio Kill functions. It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAR. This would invalidate the current ATO and incur additional cost.

All radios must have P25 Link Layer Authentication via in place infrastructure server, preserving network security and to ensure no cloning of radios and ID’s can take place. Radio authentication must pass the APCO P25 Compliance Acceptance Program (CAP) testing process on a Motorola ASTRO 7.17.3 Trunk Infrastructure.

All radios must utilize Multi-key Encryption meaning the ability to have multiple encryption keys on the same radio with different keys assigned to different Talk Groups on a per Channel basis, and a separate data key.

Radios must use integrated voice and data (IV&D). Includes capability for group messaging, text messaging to enable interoperability as well as OTAP and OTAR.

All voice must be given priority over data for radios on the LMR network.

Radio must have capability for ASTRO Enhanced Data and transmit of GPS on PTT features for location optimization for data session roaming. This allows for continuous site preference, assignment updating and seamless roaming during data transfers.

All radios must have capability for User Alias Update through the ASTRO 7.17 infrastructure.

All radios must have DoD JF-12.

All radios must have a minimum of fifteen channels per zone. Removable rechargeable batteries. Meet

Multi Unit OEM Bank Charger capable of charging six Hand Held Portable UHF Radios or batteries simultaneously in a single piece of hardware.

Single Unit OEM Charger capable of charging one Hand Held Portable UHF Radios or battery.

• All features of the devices must be tested with verification for use on the Navy ELMR ASTRO 7.17.3 system prior to this solicitation. This includes all management capabilities such as OTAR and OTAP.

MANAGEMENT CAPABILITIES OF RADIOS OVER ELMR NETWORK:

o All radios must use Over the Air Programming (OTAP) through the ELMR network. o All radios are managed by existing OTAP programming software, OTAP client, and ELMR OTAP servers / infrastructure.

It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAP. This would invalidate the current ATO and incur additional cost.

All radios must leverage the existing OTAP infrastructure capabilities such as presence notification which provides batch programming capability as well as dynamic management of radio IP addresses. In addition, OTAP will prioritize voice over data and resume stopped sessions that are interrupted -preserves OTAP and network efficiency. Radios must utilize OTAP partial codeplug rewrite – capability ensures radios are able to efficiently receive updates while not impacting radio operation and preserves ELMR network resources.

All radios must utilize automated OTAR and Bulk OTAR for rekey via the key loss function.

All radios must be manageable by the existing Key Management Facility (KMF) to allow for both Clear and Secure Hello packets and radio Kill functions. It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAR. This would invalidate the current ATO and incur additional cost.

All radios must have P25 Link Layer Authentication via in place infrastructure server, preserving network security and to ensure no cloning of radios and ID’s can take place. Radio authentication must pass the APCO P25 Compliance Acceptance Program (CAP) testing process on a Motorola ASTRO 7.17.3 Trunk Infrastructure.

All radios must utilize Multi-key Encryption meaning the ability to have multiple encryption keys on the same radio with different keys assigned to different Talk Groups on a per Channel basis, and a separate data key.

Radios must use integrated voice and data (IV&D). Includes capability for group messaging, text messaging to enable interoperability as well as OTAP and OTAR.

All voice must be given priority over data for radios on the LMR network.

Radio must have capability for ASTRO Enhanced Data and transmit of GPS on PTT features for location optimization for data session roaming. This allows for continuous site preference, assignment updating and seamless roaming during data transfers.

All radios must have capability for User Alias Update through the ASTRO 7.17 infrastructure.

All radios must have DoD JF-12.

All radios must have a minimum of fifteen channels per zone. Removable rechargeable batteries. Meet

OEM Rechargeable Batteries for the Hand Held Portable UHF Radios meeting below requirements.

• All features of the devices must be tested with verification for use on the Navy ELMR ASTRO 7.17.3 system prior to this solicitation. This includes all management capabilities such as OTAR and OTAP.

MANAGEMENT CAPABILITIES OF RADIOS OVER ELMR NETWORK:

o All radios must use Over the Air Programming (OTAP) through the ELMR network. o All radios are managed by existing OTAP programming software, OTAP client, and ELMR OTAP servers / infrastructure.

It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAP. This would invalidate the current ATO and incur additional cost.

All radios must leverage the existing OTAP infrastructure capabilities such as presence notification which provides batch programming capability as well as dynamic management of radio IP addresses. In addition, OTAP will prioritize voice over data and resume stopped sessions that are interrupted -preserves OTAP and network efficiency. Radios must utilize OTAP partial codeplug rewrite – capability ensures radios are able to efficiently receive updates while not impacting radio operation and preserves ELMR network resources.

All radios must utilize automated OTAR and Bulk OTAR for rekey via the key loss function.

All radios must be manageable by the existing Key Management Facility (KMF) to allow for both Clear and Secure Hello packets and radio Kill functions. It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAR. This would invalidate the current ATO and incur additional cost.

All radios must have P25 Link Layer Authentication via in place infrastructure server, preserving network security and to ensure no cloning of radios and ID’s can take place. Radio authentication must pass the APCO P25 Compliance Acceptance Program (CAP) testing process on a Motorola ASTRO 7.17.3 Trunk Infrastructure.

All radios must utilize Multi-key Encryption meaning the ability to have multiple encryption keys on the same radio with different keys assigned to different Talk Groups on a per Channel basis, and a separate data key.

Radios must use integrated voice and data (IV&D). Includes capability for group messaging, text messaging to enable interoperability as well as OTAP and OTAR.

All voice must be given priority over data for radios on the LMR network.

Radio must have capability for ASTRO Enhanced Data and transmit of GPS on PTT features for location optimization for data session roaming. This allows for continuous site preference, assignment updating and seamless roaming during data transfers.

All radios must have capability for User Alias Update through the ASTRO 7.17 infrastructure.

All radios must have DoD JF-12.

All radios must have a minimum of fifteen channels per zone. Removable rechargeable batteries. Meet

Mobile UHF Radio – Designed to be installed in a vehicle. Radios must be shipped with all required equipment including antennas with magnetic mounts, wiring harnesses, and programming. Also, required programming software, associated OEM programming hardware, and cables.

• All features of the devices must be tested with verification for use on the Navy ELMR ASTRO 7.17.3 system prior to this solicitation. This includes all management capabilities such as OTAR and OTAP.

MANAGEMENT CAPABILITIES OF RADIOS OVER ELMR NETWORK:

o All radios must use Over the Air Programming (OTAP) through the ELMR network. o All radios are managed by existing OTAP programming software, OTAP client, and ELMR OTAP servers / infrastructure.

It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAP. This would invalidate the current ATO and incur additional cost.

All radios must leverage the existing OTAP infrastructure capabilities such as presence notification which provides batch programming capability as well as dynamic management of radio IP addresses. In addition, OTAP will prioritize voice over data and resume stopped sessions that are interrupted -preserves OTAP and network efficiency. Radios must utilize OTAP partial codeplug rewrite – capability ensures radios are able to efficiently receive updates while not impacting radio operation and preserves ELMR network resources.

All radios must utilize automated OTAR and Bulk OTAR for rekey via the key loss function.

All radios must be manageable by the existing Key Management Facility (KMF) to allow for both Clear and Secure Hello packets and radio Kill functions. It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAR. This would invalidate the current ATO and incur additional cost.

All radios must have P25 Link Layer Authentication via in place infrastructure server, preserving network security and to ensure no cloning of radios and ID’s can take place. Radio authentication must pass the APCO P25 Compliance Acceptance Program (CAP) testing process on a Motorola ASTRO 7.17.3 Trunk Infrastructure.

All radios must utilize Multi-key Encryption meaning the ability to have multiple encryption keys on the same radio with different keys assigned to different Talk Groups on a per Channel basis, and a separate data key.

Radios must use integrated voice and data (IV&D). Includes capability for group messaging, text messaging to enable interoperability as well as OTAP and OTAR.

All voice must be given priority over data for radios on the LMR network.

Radio must have capability for ASTRO Enhanced Data and transmit of GPS on PTT features for location optimization for data session roaming. This allows for continuous site preference, assignment updating and seamless roaming during data transfers.

All radios must have capability for User Alias Update through the ASTRO 7.17 infrastructure.

All radios must have DoD JF-12.

All radios must have a minimum of fifteen channels per zone. Removable rechargeable batteries. Meet

Motorola XTS5000 OEM Rechargeable Batteries for the Hand Held Portable UHF Radios. 1700 MAH Batteries for the Motorola XTS5000.

• All features of the devices must be tested with verification for use on the Navy ELMR ASTRO 7.17.3 system prior to this solicitation. This includes all management capabilities such as OTAR and OTAP.

MANAGEMENT CAPABILITIES OF RADIOS OVER ELMR NETWORK:

o All radios must use Over the Air Programming (OTAP) through the ELMR network. o All radios are managed by existing OTAP programming software, OTAP client, and ELMR OTAP servers / infrastructure.

It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAP. This would invalidate the current ATO and incur additional cost.

All radios must leverage the existing OTAP infrastructure capabilities such as presence notification which provides batch programming capability as well as dynamic management of radio IP addresses. In addition, OTAP will prioritize voice over data and resume stopped sessions that are interrupted -preserves OTAP and network efficiency. Radios must utilize OTAP partial codeplug rewrite – capability ensures radios are able to efficiently receive updates while not impacting radio operation and preserves ELMR network resources.

All radios must utilize automated OTAR and Bulk OTAR for rekey via the key loss function.

All radios must be manageable by the existing Key Management Facility (KMF) to allow for both Clear and Secure Hello packets and radio Kill functions. It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAR. This would invalidate the current ATO and incur additional cost.

All radios must have P25 Link Layer Authentication via in place infrastructure server, preserving network security and to ensure no cloning of radios and ID’s can take place. Radio authentication must pass the APCO P25 Compliance Acceptance Program (CAP) testing process on a Motorola ASTRO 7.17.3 Trunk Infrastructure.

All radios must utilize Multi-key Encryption meaning the ability to have multiple encryption keys on the same radio with different keys assigned to different Talk Groups on a per Channel basis, and a separate data key.

Radios must use integrated voice and data (IV&D). Includes capability for group messaging, text messaging to enable interoperability as well as OTAP and OTAR.

All voice must be given priority over data for radios on the LMR network.

Radio must have capability for ASTRO Enhanced Data and transmit of GPS on PTT features for location optimization for data session roaming. This allows for continuous site preference, assignment updating and seamless roaming during data transfers.

All radios must have capability for User Alias Update through the ASTRO 7.17 infrastructure.

All radios must have DoD JF-12.

All radios must have a minimum of fifteen channels per zone. Removable rechargeable batteries. Meet

LOW and High Noise Kit – capable of enhancing comprehensibility in low noise environment or transmitting in a high noise environment.

• All features of the devices must be tested with verification for use on the Navy ELMR ASTRO 7.17.3 system prior to this solicitation. This includes all management capabilities such as OTAR and OTAP.

MANAGEMENT CAPABILITIES OF RADIOS OVER ELMR NETWORK:

o All radios must use Over the Air Programming (OTAP) through the ELMR network. o All radios are managed by existing OTAP programming software, OTAP client, and ELMR OTAP servers / infrastructure.

It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAP. This would invalidate the current ATO and incur additional cost.

All radios must leverage the existing OTAP infrastructure capabilities such as presence notification which provides batch programming capability as well as dynamic management of radio IP addresses. In addition, OTAP will prioritize voice over data and resume stopped sessions that are interrupted -preserves OTAP and network efficiency. Radios must utilize OTAP partial codeplug rewrite – capability ensures radios are able to efficiently receive updates while not impacting radio operation and preserves ELMR network resources.

All radios must utilize automated OTAR and Bulk OTAR for rekey via the key loss function.

All radios must be manageable by the existing Key Management Facility (KMF) to allow for both Clear and Secure Hello packets and radio Kill functions. It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAR. This would invalidate the current ATO and incur additional cost.

All radios must have P25 Link Layer Authentication via in place infrastructure server, preserving network security and to ensure no cloning of radios and ID’s can take place. Radio authentication must pass the APCO P25 Compliance Acceptance Program (CAP) testing process on a Motorola ASTRO 7.17.3 Trunk Infrastructure.

All radios must utilize Multi-key Encryption meaning the ability to have multiple encryption keys on the same radio with different keys assigned to different Talk Groups on a per Channel basis, and a separate data key.

Radios must use integrated voice and data (IV&D). Includes capability for group messaging, text messaging to enable interoperability as well as OTAP and OTAR.

All voice must be given priority over data for radios on the LMR network.

Radio must have capability for ASTRO Enhanced Data and transmit of GPS on PTT features for location optimization for data session roaming. This allows for continuous site preference, assignment updating and seamless roaming during data transfers.

All radios must have capability for User Alias Update through the ASTRO 7.17 infrastructure.

All radios must have DoD JF-12.

All radios must have a minimum of fifteen channels per zone. Removable rechargeable batteries. Meet

Hand Held Portable UHF Radio Holder – Leather over the shoulder strap portable radio holders with anti-sway strap. Designed for the radios procured.

• All features of the devices must be tested with verification for use on the Navy ELMR ASTRO 7.17.3 system prior to this solicitation. This includes all management capabilities such as OTAR and OTAP.

MANAGEMENT CAPABILITIES OF RADIOS OVER ELMR NETWORK:

o All radios must use Over the Air Programming (OTAP) through the ELMR network. o All radios are managed by existing OTAP programming software, OTAP client, and ELMR OTAP servers / infrastructure.

It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAP. This would invalidate the current ATO and incur additional cost.

All radios must leverage the existing OTAP infrastructure capabilities such as presence notification which provides batch programming capability as well as dynamic management of radio IP addresses. In addition, OTAP will prioritize voice over data and resume stopped sessions that are interrupted -preserves OTAP and network efficiency. Radios must utilize OTAP partial codeplug rewrite – capability ensures radios are able to efficiently receive updates while not impacting radio operation and preserves ELMR network resources.

All radios must utilize automated OTAR and Bulk OTAR for rekey via the key loss function.

All radios must be manageable by the existing Key Management Facility (KMF) to allow for both Clear and Secure Hello packets and radio Kill functions. It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAR. This would invalidate the current ATO and incur additional cost.

All radios must have P25 Link Layer Authentication via in place infrastructure server, preserving network security and to ensure no cloning of radios and ID’s can take place. Radio authentication must pass the APCO P25 Compliance Acceptance Program (CAP) testing process on a Motorola ASTRO 7.17.3 Trunk Infrastructure.

All radios must utilize Multi-key Encryption meaning the ability to have multiple encryption keys on the same radio with different keys assigned to different Talk Groups on a per Channel basis, and a separate data key.

Radios must use integrated voice and data (IV&D). Includes capability for group messaging, text messaging to enable interoperability as well as OTAP and OTAR.

All voice must be given priority over data for radios on the LMR network.

Radio must have capability for ASTRO Enhanced Data and transmit of GPS on PTT features for location optimization for data session roaming. This allows for continuous site preference, assignment updating and seamless roaming during data transfers.

All radios must have capability for User Alias Update through the ASTRO 7.17 infrastructure.

All radios must have DoD JF-12.

All radios must have a minimum of fifteen channels per zone. Removable rechargeable batteries. Meet

Hand Held Portable UHF Radio OEM – Ear piece kits with coil cable. Replacement ear seals for ear piece kits.

• All features of the devices must be tested with verification for use on the Navy ELMR ASTRO 7.17.3 system prior to this solicitation. This includes all management capabilities such as OTAR and OTAP.

MANAGEMENT CAPABILITIES OF RADIOS OVER ELMR NETWORK:

o All radios must use Over the Air Programming (OTAP) through the ELMR network. o All radios are managed by existing OTAP programming software, OTAP client, and ELMR OTAP servers / infrastructure.

It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAP. This would invalidate the current ATO and incur additional cost.

All radios must leverage the existing OTAP infrastructure capabilities such as presence notification which provides batch programming capability as well as dynamic management of radio IP addresses. In addition, OTAP will prioritize voice over data and resume stopped sessions that are interrupted -preserves OTAP and network efficiency. Radios must utilize OTAP partial codeplug rewrite – capability ensures radios are able to efficiently receive updates while not impacting radio operation and preserves ELMR network resources.

All radios must utilize automated OTAR and Bulk OTAR for rekey via the key loss function.

All radios must be manageable by the existing Key Management Facility (KMF) to allow for both Clear and Secure Hello packets and radio Kill functions. It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAR. This would invalidate the current ATO and incur additional cost.

All radios must have P25 Link Layer Authentication via in place infrastructure server, preserving network security and to ensure no cloning of radios and ID’s can take place. Radio authentication must pass the APCO P25 Compliance Acceptance Program (CAP) testing process on a Motorola ASTRO 7.17.3 Trunk Infrastructure.

All radios must utilize Multi-key Encryption meaning the ability to have multiple encryption keys on the same radio with different keys assigned to different Talk Groups on a per Channel basis, and a separate data key.

Radios must use integrated voice and data (IV&D). Includes capability for group messaging, text messaging to enable interoperability as well as OTAP and OTAR.

All voice must be given priority over data for radios on the LMR network.

Radio must have capability for ASTRO Enhanced Data and transmit of GPS on PTT features for location optimization for data session roaming. This allows for continuous site preference, assignment updating and seamless roaming during data transfers.

All radios must have capability for User Alias Update through the ASTRO 7.17 infrastructure.

All radios must have DoD JF-12.

All radios must have a minimum of fifteen channels per zone. Removable rechargeable batteries. Meet

Hand Held Portable UHF Radio OEM Hand Microphone/Speaker – designed to attach to the portable radio and have a lapel clip.

• All features of the devices must be tested with verification for use on the Navy ELMR ASTRO 7.17.3 system prior to this solicitation. This includes all management capabilities such as OTAR and OTAP.

MANAGEMENT CAPABILITIES OF RADIOS OVER ELMR NETWORK:

o All radios must use Over the Air Programming (OTAP) through the ELMR network. o All radios are managed by existing OTAP programming software, OTAP client, and ELMR OTAP servers / infrastructure.

It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAP. This would invalidate the current ATO and incur additional cost.

All radios must leverage the existing OTAP infrastructure capabilities such as presence notification which provides batch programming capability as well as dynamic management of radio IP addresses. In addition, OTAP will prioritize voice over data and resume stopped sessions that are interrupted -preserves OTAP and network efficiency. Radios must utilize OTAP partial codeplug rewrite – capability ensures radios are able to efficiently receive updates while not impacting radio operation and preserves ELMR network resources.

All radios must utilize automated OTAR and Bulk OTAR for rekey via the key loss function.

All radios must be manageable by the existing Key Management Facility (KMF) to allow for both Clear and Secure Hello packets and radio Kill functions. It is not acceptable to require additional hardware/infrastructure added to the Navy ELMR network for successful operation of OTAR. This would invalidate the current ATO and incur additional cost.

All radios must have P25 Link Layer Authentication via in place infrastructure server, preserving network security and to ensure no cloning of radios and ID’s can take place. Radio authentication must pass the APCO P25 Compliance Acceptance Program (CAP) testing process on a Motorola ASTRO 7.17.3 Trunk Infrastructure.

All radios must utilize Multi-key Encryption meaning the ability to have multiple encryption keys on the same radio with different keys assigned to different Talk Groups on a per Channel basis, and a separate data key.

Radios must use integrated voice and data (IV&D). Includes capability for group messaging, text messaging to enable interoperability as well as OTAP and OTAR.

All voice must be given priority over data for radios on the LMR network.

Radio must have capability for ASTRO Enhanced Data and transmit of GPS on PTT features for location optimization for data session roaming. This allows for continuous site preference, assignment updating and seamless roaming during data transfers.

All radios must have capability for User Alias Update through the ASTRO 7.17 infrastructure.

All radios must have DoD JF-12.

All radios must have a minimum of fifteen channels per zone. Removable rechargeable batteries. Meet