Can the same Android enterprise mobility strategy you use in safe areas be extended into Zone 2/22?
Yes, in many cases. Moving Android mobile workflows into a hazardous area changes the hardware and operating requirements, but it does not automatically mean creating a separate digital environment. With the right certified endpoint, organizations can retain familiar applications, device-management processes and lifecycle planning while introducing the additional controls required for hazardous area use.
Extend the digital estate rather than rebuild it
Enterprise mobility strategies are usually designed around consistency. Information Technology (IT) and Operational Technology (OT) teams want applications, security policies and device-management processes that can work across the organization rather than being recreated for each operating area.
The key difference in a hazardous area is the endpoint. Standard enterprise devices may not be suitable where explosive gas or dust atmospheres can occur, so the existing Android strategy needs appropriately certified hardware and operating procedures.
For example, our BARTEC ET60/65EX2 Android Tablet is co-engineered with Zebra Technologies and brings the Zebra Android platform into a device approved for ATEX and IECEx use in Zone 2/22 and Class I,II,III Division 2 areas. This means customers already using Zebra Android devices can extend familiar enterprise mobility principles into these areas without abandoning the wider platform they already know.
What can stay familiar?
Depending on the application and deployment, that continuity can include:
- Business applications: Existing Android applications may support the same inspection, maintenance, workflow, data-entry or information-access processes used elsewhere, subject to application validation.
- Data workflows: Information can continue into the same wider business systems instead of being isolated because the endpoint is used in a hazardous area.
- User experience: A familiar Android and Zebra environment can reduce the need to introduce a completely different device concept for Zone 2/22 users.
- Enterprise software: Zebra DNA™ on our enterprise mobility devices supports deployment, management, security and productivity requirements on compatible devices.
- Onboarding procedures: personnel can be onboarded to the Ex devices using the same software systems, further reducing cost and complication.
Not every application or configuration will transfer unchanged, so compatibility still needs to be checked against the intended deployment.
As the BARTEC ET60/65EX2 Android Tablet is built on the Zebra ET60/ET65 Android platform, existing enterprise concepts can remain consistent. We also confirm that Zebra documentation can be used for the setup and operation of the equivalent platform, with our hazardous area instructions taking priority where the two overlap.
Whichever device you are deploying for Ex environments, it is important to consider the manufacturers deployment documentation for specific information pertaining to use in Ex zones.
Plan device management before deployment
Device management should be considered at the selection stage rather than after devices reach the plant floor.
For organizations already managing Zebra Android devices, tools such as Zebra StageNow can support familiar staging and configuration processes. An existing Enterprise Mobility Management (EMM) platform may also remain part of the architecture, but compatibility should be verified against the selected Android version, applications and security policies.
Early collaboration between IT, OT and explosion-protection teams helps align the certified hardware with the way devices will be provisioned, secured, updated and supported across the wider mobile estate.
Android security and lifecycle still matter
Hazardous area certification addresses suitability for the defined operating conditions; it does not replace normal enterprise endpoint-security and lifecycle responsibilities. Guidance from the National Institute of Standards and Technology also emphasizes centralized management, endpoint protection and lifecycle controls as part of enterprise mobile-device security in its Guidelines for Managing the Security of Mobile Devices in the Enterprise.
For devices like the BARTEC ET60/65EX2 Android Tablet, we currently provide Android 14, with the hardware supporting Android versions through Android 16. Our operating-system support information explains how customers can obtain supported operating-system updates through Zebra or BARTEC service routes. This gives organizations a clearer upgrade path and helps them plan application and security support over the device lifecycle.
We also offer servicing and spare parts for the BARTEC ET60/65EX2 Android Tablet for up to four years after the product becomes end of life, subject to the applicable service terms and parts availability. This can reduce the risk of needing to replace recently deployed certified hardware prematurely and gives customers greater confidence when planning a longer-term mobile strategy.
What changes when the device enters a hazardous area?
Software continuity does not remove the hazardous area boundary. The certified configuration and operating instructions still determine how the device can be handled in the hazardous area.
For example, our BARTEC ET60/65EX2 Android Tablet Quick Start Guide for ATEX/IECEx Zone 2/22 states that inserting or replacing a Nano Subscriber Identity Module (SIM) card, inserting, changing or charging the battery, and attaching or removing accessories are only permitted outside the hazardous area. The battery lock screw and input/output (I/O) port cover lock screw must also be engaged when the device is used in a hazardous location.
These requirements from the device manufacturer need to be reflected in operating procedures, training and device-support processes. Ruggedness should also be considered separately from explosion protection: resistance to drops, dust or harsh industrial use does not replace the certification required for the hazardous area in which the device will operate.
Bringing Android and hazardous area requirements together
A practical deployment starts with the existing Android workflow and then identifies what must change for Zone 2/22. Before rollout, confirm:
- Applications and workflows: Which existing Android processes need to extend into the hazardous area and whether they have been validated on the selected device.
- Device management: How staging, enrolment, policy control and updates will be handled.
- Connectivity: How devices will reach the required enterprise or operational systems where they will be used.
- Lifecycle: How operating-system updates, application compatibility and long-term service support will be managed.
- Explosion protection: Whether the selected device configuration, operating procedures and accessories are appropriate for the intended Zone 2/22 Div. 2 application.
For organizations already invested in Zebra Android enterprise mobility, devices like the BARTEC ET60/65EX2 Android Tablet provide a route to extend that strategy into Zone 2/22 using a certified endpoint built around a familiar platform. Rather than creating a disconnected mobile environment, the objective is to preserve useful enterprise consistency while applying the additional controls required for hazardous area operation.
To explore the device in more detail, see the BARTEC ET60/65EX2 Android Tablet or talk to us about how it could fit into your Android enterprise mobility and hazardous area connectivity strategy.
Product Manager EM (Enterprise Mobility) Business Unit at BARTEC
“Certified Android devices can bring familiar apps and workflows into Zone 2/22, helping reduce training needs, simplify device management and maintain productivity across your operations.”