Part 2 of a 3-part series on integrating two-way radios with industrial alarm management.
In the first post in this series, we covered why integrating SCADA alarms directly into Motorola MOTOTRBO two-way radios is one of the highest-leverage moves a plant can make for response time and operator awareness.
SeQent is the only alarm management platform that integrates natively with Motorola MOTOTRBO two-way radios. That native integration is why we can offer three different MOTOTRBO alarm integration paths instead of a single forced fit, and you can see the full overview on our Motorola integrations page.
This post is about the next question. Once you know you want SCADA alarms reaching the radios on your floor, how do you know which path fits your environment? The good news: choosing comes down to three practical questions, and the deployment itself splits cleanly across three parties. Answer the questions below, and you will know which path is yours before your first call with our team.
Question 1: Do you need text, voice, or both?
The first decision is what your operators need to see or hear when an alarm fires.
A text message on the radio screen is the most common choice. It puts a clear, structured alarm description in front of the operator with timestamp, source, and any acknowledgement codes you choose to include. The operator can read it, acknowledge it, and act without losing context.
A voice announcement is the right choice when operators are wearing PPE, working in environments where reading a screen is not practical, or when you need an alarm to carry across an entire talk group at the same moment. Voice is also useful for emergency mass notification scenarios where every radio on a channel needs to hear the same instruction at once.
If text fits, you have two integration paths to choose between based on your radio system. If voice fits, the path is the same regardless of system type. Many plants run both paths together: often starting with text for routine alarms, adding voice for high-priority and emergency events later.
Question 2 (Text path): What is your MOTOTRBO system architecture?
This is the key qualifying question for text messaging. SeQent supports two paths because Motorola supports two fundamentally different system architectures.
FirstPAGE Link for MNIS (FPLNKMNIS) is the right path if your plant runs MOTOTRBO Conventional, Capacity Plus, or Linked Capacity Plus. These are the most common architectures in single-site and multi-site industrial plants. FPLNKMNIS works directly with the MOTOTRBO repeaters in your radio rack, using Motorola Solutions’ MNIS (MOTOTRBO Network Interface Service) and DDMS (Device Discovery and Mobility Service). All repeaters need an active NAI Data licence applied through Motorola Solutions’ Radio Management software, handled by your radio dealer.
FirstPAGE Link for Capacity Max (FPLNKCMAX) is the right path if your plant runs MOTOTRBO Capacity Max, Motorola Solutions’ a trunked digital system designed for larger fleets and multi-site coverage. Instead of talking to repeaters directly, FPLNKCMAX talks to the Capacity Max System Server (CMSS), which routes messages to the right radios. In a Capacity Max system, the MNIS license is applied within Radio Management on the CMSS side.
If you are not sure which architecture you have, your Motorola radio dealer can confirm in a single phone call.
Question 3 (Voice path): How many talk groups need alarm notifications?
For voice announcements, FirstPAGE Link for TTS (FPLNKTTS) uses text-to-speech to convert alarm messages into audio and broadcast them over a MOTOTRBO talk group. The integration uses a JPS Interoperability Solutions device (NXU-2B for a single talk group, RSP-Z2 for two talk groups, or a combination of devices for more) connected to a MOTOTRBO mobile radio configured as a control station.
What you will need on each side
Regardless of which path you choose, the deployment splits the same three ways.
SeQent provides the FirstPAGE Alarm Manager platform, the appropriate FirstPAGE Link software, licence keys, and remote installation, testing, and ongoing support through our Customer Care site.
You provide a Windows host to run the software (Windows Server 2019 or 2022, or Windows 10 or 11, with 8 GB of RAM and 100 GB of disk as a minimum, and a static IP recommended), IP addresses for any JPS or Motorola equipment that needs them, network connectivity from the host to your Motorola infrastructure, and firewall rules that allow the required SNPP, TCP, and UDP traffic. SeQent provides the exact port specifications during deployment.
Your Motorola Solutions radio dealer provides the radio hardware and programming, JPS hardware and interface cables for voice deployments, and the MOTOTRBO licences your architecture requires. That means the NAI Data licence on each repeater for Conventional, Capacity Plus, or Linked Capacity Plus, or the MNIS configuration in Radio Management for Capacity Max.
A short qualifying checklist
Before your first scoping call with SeQent, having the following information ready will speed up the design and quote:
- Do you need text, voice, or both?
- What MOTOTRBO architecture do you run: Conventional, Capacity Plus, Linked Capacity Plus, or Capacity Max?
- How many talk groups will receive notifications?
- What SCADA, HMI, MES, or PLC platform is the alarm source? FPAM connects natively to AVEVA System Platform and InTouch, AVEVA PI System, GE Vernova iFIX and CIMPLICITY, Rockwell FactoryTalk View SE, OPC Classic and OPC UA, ODBC, and PTC ThingWorx.
- Do you have a Motorola radio dealer engaged already, or do you need a referral?
- Will the SeQent software run on a virtual machine or a dedicated Windows PC?
Ready to see MOTOTRBO alarm integration live?
If you can answer most of the questions above, you are ready for a 30-minute scoping conversation with our team. We will confirm the right integration path, walk through what is needed from your radio dealer, and outline a deployment timeline.
Book a demo and see SCADA alarms delivered to MOTOTRBO radios live, in an environment that mirrors yours.
In the final post of this series, we will walk through what a typical FirstPAGE Link deployment looks like end-to-end, from kickoff to first production alarm.
