OEMConfig for proprietary device features

Scenario

Supported platforms: Android

Manufacturing organizations deploy rugged devices from multiple OEMs for frontline workers across multiple shifts. For example, a manufacturing company allows factory employees to use wearable Android devices to capture manufacturing defects. The company runs 3 shifts every day of the week and uses shared devices where employees pick any device at the beginning of their shift, log in, and start by using it.

Each OEM provides proprietary device capabilities through their own Application Protocol Interfaces (APIs) instead of standard Android APIs. These vendor-specific features include advanced scanning configurations, custom button mappings, battery optimization settings, and specialized hardware controls that are critical for manufacturing operations but not accessible through standard Android management.

What IBM MaaS360 does

• Standardized configuration:
  • Access OEM-specific features through a unified management console.
  • Deploy OEMConfig applications from Google Play to managed devices.
  • Configure proprietary settings by using OEM-maintained schemas.
  • Eliminate the need for custom Enterprise Mobility Management (EMM) integrations.
  • Support hundreds of OEM configuration policy attributes directly from device manufacturers.
• Device-specific capabilities:
  • Configure advanced bar code scanner settings.
  • Optimize battery performance with OEM-specific power profiles.
  • Control specialized hardware features such as industrial sensors.
  • Manage device-specific security features and encryption.
  • Enable only required modules such as Bluetooth and Wi-Fi per user.
• Policy management:
  • Create device-specific configuration profiles.
  • Deploy different policies and configurations for different device groups based on restrictions and compliance requirements.
  • Update configurations remotely without device interaction.
  • Maintain consistent settings across the device lifecycle.
  • Apply day-zero device settings for immediate productivity.
• Shared device support:
  • Enable proper partitioning for each user with data privacy and device security.
  • Apply policies and applications immediately when a shared-device user logs in.
  • Support bulk device deployment by using Apple Device Enrollment Program (DEP), Google Zero Touch, Samsung Knox, and QR code-based enrollments

Implementation steps

1. Verify OEMConfig support:
   • Confirm that your OEM provides an OEMConfig application.
   • Check device compatibility with OEMConfig requirements. For more information, see Supported devices in MaaS360 based on operating system.
   • Ensure that devices are enrolled in Device Owner (DO) mode.
   • Verify support for your deployment method such as Google Zero Touch, Samsung Knox, or QR code enrollment.
2. Deploy OEMConfig application:
   • Add the OEM-specific OEMConfig app from Google Play to your app catalog.
   • Configure application security settings to restrict app removal.
   • Assign the OEMConfig app to the appropriate device groups.
   • Distribute the application to enrolled devices. For more information, see Distributing Primary Enterprise apps to devices and Distributing Secondary Enterprise apps to devices.
3. Configure OEM-specific settings:
   • Access the OEMConfig policy editor in the IBM MaaS360 console.
   • Select the OEM-specific configuration schema.
   • Define settings for scanner behavior, buttons, battery, and hardware.
   • Configure wifi and VPN settings for seamless device setup.
   • Set security controls such as restrictions and compliance requirements.
   • Save the configuration profile.
4. Deploy and monitor:
   • Assign configuration profiles to device groups.
   • Monitor deployment status in the console.
   • Verify that settings are applied correctly on devices.
   • Track device battery health remotely.
   • Update configurations as operational requirements change.

   For more information, see Devices, Assigning MDM policy to device groups , and Managing device groups in the IBM MaaS360 Portal.

For more information on portal administration functions, device management, software distributions, policy self-service, and device compliance functions, see IBM MaaS360 Portal.

Expected outcomes