New SCRAMNET GPS Features

Ken SCRAM Ally, SCRAM GPS Device, SCRAMNET GPS

New SCRAMNET GPS Features

At 5:00 AM MDT on Thursday, April 3, 2025, SCRAM Systems is introducing two new features in SCRAMNET GPS. Enhancements include:

  1. Changes to the SCRAM Ally mobile app registration and login process
  2. Enhanced performance with HTTP/2 support
Information During the 15-minute deployment, you may not be able to access SCRAMNET GPS, but messages from the SCRAM GPS device will continue to be processed uninterrupted.

Changes to SCRAM Ally Registration & Login

Victim Notification: Background

The SCRAMNET GPS Victim Notification service, paired with its companion smartphone app, SCRAM Ally™, allows officers and case managers to automatically inform victims when an assigned GPS client is in close proximity to the victim’s smartphone, and possibly in violation of a restraining order.

Important! IMPORTANT: Activation of the Victim Notification service requires a contract amendment. If you are interested in the service, please contact your SCRAM Systems Account Manager or Sales Representative.

 

Changes That Impact Existing Victim Notification Customers

New victim-users of the SCRAM Ally mobile app must now select their home Country / Region* when registering the app:

Install Ally, allow services, and select your region.
Select the image above to open the SCRAM Ally App Victim Instructions help page
Important! IMPORTANT NOTES:
  • *If a new victim-user selects the wrong Region by mistake during registration, contact SCRAM Systems Customer Support for assistance immediately.
  • Existing users of the SCRAM Ally app will not need to take any action to continue using the app.

Enhanced Performance with HTTP/2 Support

SCRAMNET GPS now supports HTTP/2, a modern standard for allowing web browsers to communicate more efficiently with SCRAM Systems servers, which results in faster page-load times. You don’t need to do anything to take advantage of this feature. It is automatically enabled on your browser.

TipTip: For optimal performance we suggest clearing your browser’s cache and cookies following the April 3rd deployment of the feature.