DECT NR+ for Factory IoT in Thailand: Procurement and Radio Acceptance

Before adopting DECT NR+ for factory IoT, determine whether the exact product can be procured and operated in Thailand, then test whether battery sensors and moving equipment meet the needs of the real production process. On 15 September 2026, the DECT Forum described an expanding commercial ecosystem. That announcement does not establish regulatory clearance or radio performance for a particular Thai factory. This guide takes an OT team from the purchase decision through site acceptance.

The decision: clear regulatory and site-test gates

DECT NR+ (DECT-2020 NR) is a non-cellular radio technology developed in ETSI standards and included in the ITU-R IMT-2020 specifications. The DECT Forum describes point-to-point, star, and mesh topologies and power-saving features. These are technology capabilities, not guaranteed results in a factory. Steel structures, loads, antenna placement, neighboring transmitters, application traffic, and firmware versions can all change performance.

Use four gates. Define the production purpose and acceptable loss of communication. Verify current Thai band and use conditions, NBTC approval of the exact model, and import and operation requirements. Confirm that the exact hardware and firmware support the required topology and protocol. Finally, set acceptance limits before measuring in an operating plant. Trial duration and measurements in this article are planning examples; they are not standards-based guarantees. The plant must derive pass limits from its process and risk assessment.

Why consider DECT NR+ now?

The DECT Forum’s 15 September announcement says suppliers of silicon, software, gateways, and applications are moving toward commercial deployment. DECT World is scheduled for 2–4 November 2026 in Munich; its exhibits and conclusions have not happened yet. The Forum expects its certification programme, initially focused on building automation, to become available to manufacturers around mid-2027. A published radio standard therefore must not be confused with third-party interoperability certification for a purchased product.

STRATUM 9 announced an industrial gateway in May 2026. Its own product announcement describes mobile communication, Ethernet connection, transparent PROFINET/PROFISAFE transport, and handover. These are claims about that product, subject to the exact SKU, firmware, Thai availability, and field testing. Nordic Semiconductor publishes DECT NR+ firmware information for nRF91 parts; the feature set varies by release, and a listed MAC release explicitly supports star topology. Do not assume a mesh feature described for the technology exists in a candidate firmware build.

There are two distinct factory cases. A retrofit battery sensor prioritizes service life, measurement validity, and missing-data handling. A moving trolley or fixture prioritizes latency distribution, handover, and the machine’s behavior during a link failure. Approve each use case separately.

Retrofit battery sensors: start with the data purpose

A temperature or vibration sensor on a motor, pump, distribution board, or compressor may report periodically or trigger an urgent alarm. Write down whether its data supports maintenance trends, incident reconstruction, or an operator warning. Those uses demand different reporting intervals and rules for missing samples. For an alarm, define stale-value display, retransmission deadline, and sensor-fault behavior.

Do not copy a catalogue battery-life figure into a business case. Estimate sensing, transmission, retries, sleep, distance, ambient temperature, and the available maintenance window together. The DECT Forum explains a tradeoff between beacon intervals, sleep, and responsiveness. Request current measurements under traffic, battery, temperature, and firmware settings close to your use. In a plant, record retransmission and consumption rather than extrapolating from a pristine laboratory link.

Retrofitting also involves brackets, clearance for battery changes, calibration, vibration, and cleaning chemicals. A radio link has little value if the sensor itself cannot produce usable quality data. Define measurement points and the system of record before ordering hardware. Our factory IoT sensor selection guide discusses this wider selection process.

Moving equipment: inspect the difficult moments

Radio conditions change along a trolley, monorail, robot, or moving fixture route. Test near metal racks, doors, people, other vehicles, the rear of machines, and gateway boundaries. A vendor’s “low latency” or “seamless handover” phrase does not prove the control cycle. Measure the slow tail of the latency distribution, consecutive losses, recovery time, and machine behavior when reconnecting, rather than reporting only an average.

If a wireless path carries safety-related information, assess the entire machine safety function: risk assessment, protocol, safe state upon loss, and system validation. STRATUM 9’s PROFISAFE transport description is not automatic certification of a customer’s safety function. Bring the control designer and machine builder into the trial. Decide in advance whether a link loss must slow, stop, or hold the equipment.

DECT NR+ for Factory IoT in Thailand: Procurement and Radio Acceptance - figure 1

*Figure 1. Retrofit sensors and moving machines expose different failure modes.*

Thailand: verify band, use case, and exact NBTC approval

A common mistake is to transfer a European “license-exempt DECT band” statement directly to Thailand. Nordic’s product page uses license-exempt 1.9 GHz as a general product benefit. It cannot settle Thailand’s allowed use, power, model, import, installation, or operation conditions. Do not state that all DECT NR+ devices may operate without a licence in Thai factories.

In 2025 NBTC publicly described adding 1880–1900 MHz for DECT, in a discussion centered on event and concert equipment. NBTC consultation material also mentions DECT-2020 NR in a draft technical standard. Neither item by itself establishes blanket approval for every industrial NR+ deployment. At purchase time, compare the final effective Thai notices, scope, and current operating conditions with the device’s actual emissions, band, power, antenna, and regional configuration.

Search NBTC’s type-approval database for the exact brand and model. A gateway, battery terminal, and mobile terminal can be separate models. Ask the local supplier for hardware revision, RF module, antenna, channel band, maximum emitted power, regional settings, firmware, approval number, and import or sales documents. If a listing is absent, do not immediately call the device prohibited; ask NBTC or a qualified local testing adviser about the valid route. Equally, do not transmit a trial signal until the applicable authorization is clear.

An approved module does not automatically establish approval of every finished product built around it. Enclosure, antenna, power setting, label, and use may matter. Procurement, legal/import, and engineering staff should reconcile the same SKU list against sample units and paperwork.

Questions to send suppliers before a purchase order

Topic	Evidence requested
Thai SKU	Exact model, hardware revision, antenna, firmware
Radio	Band and channels, maximum power, regional configuration and lock
NBTC	Approval certificate/number, scope, import, sale, and use conditions
Features	Version-specific star/mesh, power saving, handover, capacity
OT interface	Ethernet, protocols, timing, data format, missing-data behavior
Support	Updates, vulnerability response, spares, Thai service, life cycle
Trial	Same SKU for field testing and a credible production supply path

This checklist is a procurement aid. Regulatory conclusions require current NBTC documents and the exact product details.

Compare the industrial network options by application

DECT NR+ need not replace an existing factory WLAN or private 5G installation. If Wi-Fi operations, identity management, and monitoring are mature, improving coverage and roaming may be the sensible first trial. See our factory wireless LAN design article. Private 5G brings its own spectrum, device, core-network, operator, and cost questions; see our Thai private 5G and NBTC guide.

“Non-cellular 5G” is a classification, not a claim that DECT NR+ uses the same equipment, SIMs, or regulatory route as 3GPP private 5G. ITU-R’s inclusion of ETSI DECT 5G-SRIT in IMT-2020 does not itself certify a factory system. Compare exact-SKU legality, observed battery life, losses in shielded areas, handover breaks, protocol compatibility, OT segmentation, local spares, and whole-life cost. Give each candidate the same traffic and route. Score fixed sensors and moving machinery separately.

Map the path from machine to application

Put the radio segment on a full architecture diagram. A vibration reading may pass through a terminal, gateway, OT collector, historian, and maintenance display. At each boundary retain timestamp, unit, asset ID, and quality flag. Never fill a missing reading with zero; that could appear to show a stopped vibration when the data was merely lost.

A gateway attached to the OT LAN needs a management route, credentials, logs, update procedure, and remote-access policy. The DECT Forum describes IPv6 as a technology feature; verify the needed IP, security, and higher-layer protocols in the purchased implementation. For cloud-bound data, plan buffering, replay, and duplicate handling after an outage.

Distinguish a wireless Ethernet bridge for moving control equipment from telemetry moving toward an application. The former raises cycle, ordering, and latency questions; the latter raises completeness and event questions. One supplier’s transparent industrial-protocol feature does not automatically extend to every NR+ implementation. Specify the actual data path and failure response in the request for proposal.

DECT NR+ for Factory IoT in Thailand: Procurement and Radio Acceptance - figure 2

*Figure 2. Test every boundary from terminal to OT collector and application.*

Run an acceptance test in the operating plant

Agree on pass criteria first

Fix the assets, route, production modes, load, and period before the proof of concept. Record whether the line is running or stopped, trolley load, door position, and metal stock layout. Choose pass limits based on the application’s deadline and hazard analysis; this article does not invent a universal packet or delay threshold. Pre-agreement prevents selection of only the favorable trial hours.

At minimum, log terminal and gateway IDs, location, timestamps, firmware, RF settings, application cycle, trolley position, power status, and error details. Measure end-to-end delay distribution, consecutive gaps, retry count, recovery time, and battery trend, not only radio reception. Correlate radio and application logs to separate RF delay from gateway or server delay.

Build the difficult cases

For fixed sensors, include metal enclosures, nearby motors, high or under-floor positions, and far locations, both while equipment is running and stopped. For moving systems, pass rack corners, building boundaries, shutters, vehicle crossing points, and gateway handover areas. Drawings cannot capture every reflection or obstruction; test the actual work and material layout. Repeat representative production cycles and include shift, cleaning, and delivery periods where conditions change. “Not tested” must remain a separate result from “passed.”

Inject faults safely

Under an approved trial procedure, power-cycle a terminal or gateway, interrupt the backhaul or collector, and stop a moving unit near a boundary. Verify the missing samples are visible, restored samples are not duplicated, alarms remain actionable, and the machine behaves safely. Any test touching a safety function requires the machine builder and safety lead’s procedure.

Report pass, conditional pass, failure, or not tested by use case, with a corrective owner and retest scope. A good average delay does not excuse a dangerous consecutive gap. If the candidate misses a requirement, compare placement changes, traffic changes, or another radio technology before expanding.

DECT NR+ for Factory IoT in Thailand: Procurement and Radio Acceptance - figure 3

*Figure 3. Drive through obstructions and gateway boundaries while logging interruption and recovery.*

A practical order for purchasing and rollout

First, make a desktop feasibility sheet with process need, candidate SKU, NBTC evidence, and realistic delivery. If legality or supply is unresolved, do not pay for a large installation trial. Check whether the existing network can meet the need. Second, run a small site test with the actual terminal and gateway at representative fixed locations and difficult moving-route points. If trial and production SKUs differ, document the difference and require production-model retesting.

Third, operate in a limited area with an agreed fallback: existing wired path, dual alarm, or manual data collection where appropriate. Put maintenance, IT, OT, machine builder, and supplier on one version and incident-contact list. Count battery replacement and software-update labor in whole-life cost. Fourth, compare the results with the preapproved use-case criteria, recheck paperwork against deployed hardware, and monitor performance after rollout. A changed antenna or power configuration may require a renewed compliance check. Recheck radio quality after a line move or rack extension.

Write testable conditions into the procurement specification

“DECT NR+ gateway set” is too vague for comparable bids. Specify terminal and gateway roles, mounting points, regional settings, antenna and cable, upper-network interface, protocol, power, and support. The same radio chip can be packaged with different firmware, enclosure, antenna, and service terms. Compare trial equipment with the production bill of materials.

Separate quotations for hardware, site survey, regulatory and import checks, loan units, installation, OT configuration, logs, acceptance, training, and incident support. Agree who performs first-line troubleshooting if a link issue stops a line. Document where logs are kept and who contacts whom before a failure occurs.

Check supply continuity. A discontinued trial model or a changed RF implementation may invalidate a rollout assumption. Specify replacement-model compatibility, firmware support life, regional lock, and security update process. “Same standard” does not prove multi-vendor interoperation for the versions you will buy; order combination tests if this matters. Track the DECT Forum certification programme without extrapolating its current scope.

For acceptance, replace “stable communication” with a table. For fixed sensors list locations, reporting cycle, missing-data marking, alarm deadline, and battery plan. For mobile equipment list route, speed, load, boundary, safe behavior, and restart. Assign plant-approved limits, trial duration, and operating conditions. Record any untested state and a date for retest before wider deployment.

Calculate battery and network tradeoffs as operating cost

A battery sensor can save cabling but create a large replacement workload. Include access equipment, downtime, disposal, and post-replacement calibration. Measure consumption at the relevant temperatures, sensing and reporting rates, retransmission conditions, and alarm frequency. Check low-voltage warnings as well as new-battery performance.

Longer sleep or beacon intervals may save energy but can delay notice of a change. A qualified current profile is more useful than a generic “years of battery life” claim. In the field, shielded locations may cause retries that a bench estimate misses. Name the person and available work window for replacement, and confirm the device reconnects to the correct asset.

Always put a measurement time and freshness state on the application data. A last good value must not appear as a new measurement after the radio stops. Monitor battery and link quality separately from the sensed variable.

Diagnose failures and retest after changes

Do not label every missing sample “weak radio.” Check the sensor acquisition, transmission queue, over-the-air retries, gateway, OT network, and application in order. A full gateway buffer can delay data despite good signal; a slow screen can mislead even when the air link works. Synchronize clocks and agree on log formats before the trial.

Classify faults by location and time. A rack-specific problem points to placement or path. A shift-change pattern may reflect people or vehicle movement. Simultaneous terminal losses suggest a shared gateway, power, or backhaul fault. A post-update problem calls for firmware and setting comparison. Preserve logs before changing settings, and give each change a separate trial case.

After adding a gateway or moving an antenna, retest adjacent cells and relevant routes as well as the original failure point. Such a change can improve one spot while altering handover or battery drain elsewhere. Keep before/after settings, photos, logs, and results as the baseline for future layout changes.

An acceptance record that others can reproduce

Record site, building, asset, date, owner, and witnesses. Freeze terminal and gateway models, serial numbers, antenna, installation height, power, firmware, and region. Mark locations and routes on a plan and photograph stock and nearby operating equipment. For each case state the stimulus, measurement, approved pass criterion, and equipment protection on failure.

For a fixed sensor, trigger both ordinary readings and a simulated threshold event. For a mobile unit, include travel, stops, restart, and crossing a gateway boundary in both directions. Preserve application and radio logs with one event identifier. On a failure, archive the original configuration before making a change. If several settings change together, the cause of any improvement becomes unclear. A plant process owner should approve both data usefulness and outage handling, rather than leaving signoff solely to radio engineers.

Security and service are part of acceptance

A small sensor may remain an OT network entry point for years. Verify device enrollment, separated administrative rights, replacement of default credentials, encryption settings, key renewal, and revocation after theft. Confirm these features in the exact product and firmware, not only in a technology overview.

Restrict gateway management to a defined OT path and logging destination. For remote support set access windows, named operators, records, and stop procedure. Because an update can change timing or RF behavior, rerun representative radio and application cases after firmware upgrades. Maintain configuration backups and spares so security fixes can be applied without improvisation.

During battery replacement, match machine plate, terminal label, asset register, and application ID; otherwise good measurements can be assigned to the wrong asset. On mobile machines, a changed antenna orientation can affect the link. Keep installation photos and inspection points in routine maintenance.

FAQ

Is DECT NR+ the same as private 5G for a factory?

No. It is non-cellular DECT-2020 NR included in IMT-2020, while a 3GPP private 5G design uses a different equipment and operating model. Compare the purchased implementation and local requirements rather than the shared “5G” label.

Is 1.9 GHz DECT NR+ automatically licence-exempt in Thailand?

Do not assume that from European marketing. NBTC has described 1880–1900 MHz support for DECT, but check the final Thai rules, industrial use, emissions, exact device approval, and import/operation conditions at purchase time.

Will retrofit sensors always have a long battery life?

No. Reporting interval, alarms, retries, temperature, cell capacity, and firmware determine consumption. Use conditional measurement data and field observations to plan replacement.

Can mobile equipment use PROFINET and PROFISAFE over NR+?

STRATUM 9 describes those functions for its gateway. They are not properties of every NR+ product. Confirm SKU and firmware, test with the machine builder, and assess the whole safety function.

What should radio acceptance measure?

End-to-end delay distribution, consecutive gaps, recovery, handover, and battery trend, each tied to production conditions and exact device versions. Approve limits before the test and mark unobserved states as untested.

Summary

DECT NR+ merits consideration for retrofit battery sensors and moving machines. Commercial announcements in autumn 2026 and the upcoming November DECT World make supplier evaluation timely. Procurement still depends on Thailand-specific band and type-approval checks for exact devices, version-specific features, and acceptance tests in the running plant.

TOMAS TECH can help map retrofit sensors, OT collection paths, and site-test criteria. If you are still comparing radio options, share your equipment and data goal through our contact page.