Tive Security Seal [Beta Access Only]

Why Use the Tive Seal?

The Tive Seal offers a powerful new way to detect shipment tampering and improve shipment security. Designed for customers who need real-time visibility into potential theft or unauthorized access, the Tive Seal solution helps ensure the integrity of high-value or sensitive shipments. By combining Bluetooth beacon technology with intelligent alerting, the Tive Seal helps ensure secure transit from origin to destination.

How It Works

Seals

The Tive Seal is a single-use Bluetooth beacon designed to detect potential cargo theft and report tampering events. It remains inactive until sealed, at which point it starts intermittently transmitting via Bluetooth to nearby Solo devices. These Solos then relay the signal to the Tive platform, which reflects the seal’s integrity status.

How do seals operate?

• Activation occurs when the cable is inserted and locked.
• Transmits to any Solo device within ~30 meters (range may vary with physical obstructions).
• Seals cannot send data to the platform directly, they depend on nearby Solos.
• Once cut, a seal will continue to broadcast its “cut” status to nearby devices until it dies. 
• Once cut, the seal can not be restored and reused.

In the platform:

• Seals appear on the “Trackers” page under “Device Type: BEACON.”
• Seals can be assigned to a shipment via the “Trackers” field when creating a shipment.
• If no Solo is present, a warning appears, and the seal will not function effectively.
• While basic data like battery and signal strength are visible, cut vs. intact status is only communicated via alerts (not directly shown on the tracker page).

Seal Tampered Alerts 

Seal Tampered Alerts notify users when a seal has been cut or broken. 

• The alert can be applied to an individual seal or to an entire shipment.
• The alert works at any phase - at origin, in transit, or at destination.

Important behavior:

• If not assigned to a shipment, Solo devices must have Bluetooth manually enabled. This is automatic if a seal is added to a shipment.
• The alert only triggers when a Solo device picks up the signal of a tampered seal. If a seal is cut outside Bluetooth range, no alert is triggered until it's brought back into range.

Beacon Separation Alerts

This alert type detects when a beacon, whether a seal or a temperature beacon, stops communicating with its associated Solo device. It helps prevent tampering by identifying when a beacon is removed, shielded, or destroyed. Separation alerts:

• Must be used in the context of a shipment (cannot apply to standalone beacons).
• Are configurable at any point in the shipment journey (at origin, in transit, at destination).

• Trigger when any Solo device on the shipment sends a transmission that is missing data from one or more expected beacons.
• Automatically close when the beacon is re-detected, and re-open if the issue recurs.
• Include details about which specific beacons have gone missing.

Important behavior:

• If multiple Solos and beacons are used, all Solos must remain within range of all assigned beacons to avoid triggering the alert.
• This alert is not limited to seals, it can also detect the removal of temperature beacons.

Key Points to Know

• The Tive Seal is one-time use; once cut, it cannot be reused.
• Requires proximity to Solo devices with Bluetooth enabled.
• Seal status (cut/intact) is not directly visible on the platform UI, alerts must be used to monitor tampering.
• Beacon Separation alerts require a shipment to function correctly.
• The seal continues broadcasting after being cut, which allows delayed alerting if Solo re-establishes connectivity with the seal.

Best Practices

• Use both alert types together: Use “Seal Tampered” alerts to detect if the seal was broken and “Beacon Separation” alerts to detect if someone tries to move or block the beacon before cutting it.
• Use the Lost Connectivity alert: Use this alert for the Solo to ensure you are informed when the seal or the Solo has lost connection. It is especially useful in situations where consistent connectivity is crucial for shipment visibility.
• Always include a Solo device in your shipment: Seals do not work independently and rely on Solo devices for communication.
• Assign beacons properly: Add Seals during shipment creation using the “Trackers” field.
• Monitor RSSI data to check beacon health throughout the shipment. Battery monitoring for Seals is generally not necessary, as they only begin drawing power once the cable is inserted and sealed, and their battery life typically exceeds one year.
• Validate alert triggers in test shipments before deploying at scale.

If you have any additional questions, you can contact support@tive.com for help!