How to prepare device policy and MDM for field teams using

For security managers in Singapore, the shift from traditional two-way radios to 5G push-to-talk (PTT) over mission-critical services (MCX) requires careful device policy and Mobile Device Management (MDM) preparation. Without a structured approach, field teams risk inconsistent connectivity, security gaps, and operational delays. The answer lies in a phased MDM rollout that enforces device compliance, application configuration, and network access controls before the first PTT call is made. This ensures that every officer's device is ready for reliable, secure communication across all operational sites.

Anonymous project scenario: A Singapore security firm modernises field communication

Singapore-based AV and IPTV integrator Prestige Solutions was engaged by a security firm operating across 12 commercial sites in Singapore. The firm managed over 150 security officers using outdated UHF walkie talkies with limited range and no data capability. The goal was to transition to a unified 5G PTT Singapore platform using MCX standards, enabling group calls, emergency alerts, and location sharing. The security manager needed to ensure that the Android ruggedised devices issued to officers were properly configured, secured, and managed remotely. As of 2026, the firm faced increasing pressure to improve response times and audit trails, making device policy and MDM readiness a critical first step.

Operational challenge: Fragmented device management and security risks

The existing device fleet consisted of mixed Android devices from different vendors, some running outdated operating systems. There was no central policy for app whitelisting, VPN configuration, or remote wipe. Officers occasionally sideloaded unauthorised apps, creating malware risks. The security manager reported that during a simulated emergency, one team could not join the PTT group because their device had an incompatible PTT client version. This highlighted the need for a robust MDM strategy. Additional challenges included inconsistent charging habits leading to battery drain during shifts, and devices being used for personal tasks which blurred the line between work and leisure. The security manager realised that without standardised device policies, the transition to 5G PTT would introduce more complexity than it solved.

Key pain points identified

• No standardised device provisioning process for new officers
• Inconsistent PTT application settings across devices
• Lack of remote lock/wipe capability for lost or stolen devices
• No compliance reporting to verify device health
• Devices running Android versions below 12, missing critical security patches
• Officers using devices for personal apps, increasing attack surface

Planning approach: MDM readiness assessment and policy design

The first step was to assess the existing device estate. Prestige Solutions conducted an audit covering device models, OS versions, and installed applications. As of 2026, the recommended baseline for Android devices is Android 12 or later with at least 4 GB RAM to handle MCX applications smoothly. The security manager adopted a zero-trust device policy: only devices enrolled in MDM could access the corporate network and PTT service. The assessment revealed that 30% of the devices were running Android 10 or earlier, requiring replacement. A phased replacement plan was created, prioritising devices used by officers in high-traffic sites. The policy also mandated that all devices be equipped with a ruggedised case and screen protector to withstand daily wear and tear.

Device policy framework

The policy included mandatory encryption, screen lock with 6-digit PIN, and prohibition of rooted devices. Applications were whitelisted to only the approved PTT client, a browser, and essential productivity tools. The MDM enforced automatic updates for the PTT app and OS security patches within 72 hours of release. Additionally, the policy required that location services be enabled during shifts to support emergency location sharing. For privacy, location could be disabled after shift end via a policy-based rule. The framework also included a 'lost device' protocol: after 10 failed PIN attempts, the device would automatically wipe all corporate data and disable the PTT client.

Configuration considerations: MDM profiles and PTT settings

MDM profiles were created for three user roles: security officer, supervisor, and control room operator. Each role had different PTT group memberships and feature permissions. For example, supervisors could initiate emergency group calls while officers could only respond. The PTT application was configured with a dedicated APN for low-latency voice traffic, ensuring quality of service on Singapore's 5G networks. Network slicing was considered for critical communications, but the public 5G network with QoS markers proved sufficient for the pilot. The MDM also enforced VPN connectivity for any data transmission outside the PTT app, protecting sensitive location and user data.

Table: MDM configuration by role

Handover and support: Training and ongoing management

Prestige Solutions provided a two-day training program for the security manager and IT support staff on MDM console operations, including enrolling devices, pushing policy updates, and generating compliance reports. A standard operating procedure (SOP) was documented for device onboarding: 1) Enrol device in MDM, 2) Install PTT client from managed Play Store, 3) Assign user role, 4) Test PTT connectivity. The support team was given a troubleshooting guide for common issues such as PTT registration failures and GPS drift. Additionally, a monthly compliance review was scheduled to ensure devices remained compliant with the latest security policies. The security manager also set up a dedicated support hotline for officers to report device issues during shifts.

Handover checklist

• MDM console administrator accounts created
• Device enrollment links distributed
• PTT application configuration profiles deployed
• Compliance policies activated
• Emergency contact escalation list provided
• Training completed for IT support staff
• Monthly compliance review schedule established

Recommended next step: Pilot deployment and iterative refinement

The security manager planned a pilot with 20 officers across two sites for two weeks. During this period, MDM logs were reviewed daily to identify devices failing compliance checks. The PTT application was updated twice to fix group call latency issues. After the pilot, the policy was refined to allow supervisors to temporarily disable location sharing for privacy during off-duty hours. The full rollout to 150 devices was completed within one month with zero security incidents. Post-deployment, the security manager reported a 40% reduction in response times to incidents, and the compliance rate of devices remained above 98% over the first quarter. The success of this project led to discussions about expanding the solution to other departments within the firm.

FAQ

What is the minimum Android version required for MCX PTT?

As of 2026, Android 12 or later is recommended to support the latest MCX standards and security features. Older versions may lack necessary APIs for group management and emergency services. Devices running Android 10 or earlier should be replaced to ensure compatibility and security.

Can existing walkie talkie frequencies be reused with 5G PTT?

No, 5G PTT operates over cellular networks using data connections, not dedicated radio frequencies. However, the transition can be phased, and some organisations keep legacy radios as backup for specific sites where cellular coverage is weak. Planning for dual-mode operation during the transition period is advisable.

How does MDM help if a device is lost or stolen?

MDM enables remote lock and wipe of the device to prevent unauthorised access to PTT communications and sensitive data. The policy can also trigger automatic wipe after repeated failed login attempts. In the scenario described, the automatic wipe after 10 failed attempts ensured data protection without manual intervention.

Is a private 5G network required for MCX PTT?

Not necessarily. MCX PTT can operate over public 5G networks with appropriate QoS settings. Private 5G may be considered for sites with high security requirements or poor public coverage. For most Singapore commercial sites, public 5G with dedicated APN provides sufficient reliability and low latency.

What support does Prestige Solutions provide after deployment?

Prestige Solutions offers ongoing MDM administration training, policy review, and troubleshooting assistance. They can also help with scaling the solution to additional sites or users. Their support includes regular compliance audits and updates to device policies as new threats emerge.

Ready to prepare your field teams for 5G PTT? Contact Prestige Solutions for a device policy and MDM readiness assessment tailored to your security operations. Visit our home page to learn more about our communication solutions.