Recommended  requirements for mobile devices

*NOTE: IBM recommends against using devices with operating systems not supported by the operating system vendor (ex.  Apple, Google, Microsoft).  IBM does not support running IBM software on these operating systems.  The support state for these operating systems is dynamic, so this statement overrides any statements specific to operating system versions below.
 

Android 4, 5, 6, 7, or 8 operating systems

    Android 7 and 8:  Supported if you installed the latest interim fix for Maximo Anywhere and you applied the Mobile First interim fix, 7.1.0.0-MFPF-IF201709131648.  

    Android CPU:  CPU score of 900 or above recommended 

    Recommended Memory: Minimum 1 GB of RAM

*Notes on Android 9 Support

  - Android 9 is supported as "runs on".  This means Anywhere 7.6.3.x will run on Android 9 as long as it is built  using API 26 or lower. 

  - If you are deploying to an Enterprise store and need to build on API 28, follow the information here

iOS 8, 9, 10 and 11 operating systems

   iOS 11:  Supported if you installed the latest interim fix for Maximo Anywhere 
       iOS apps built  using Xcode 8.3.2 using 64-bit architecture are supported by iOS 11.

       iOS apps built by using Xcode 9 are not supported by iOS 11.

   iOS CPU: Dual core processor at least iPhone 5 and above recommended

                 CPU devices with a benchmark score above 700

   Recommended Memory: Minimum 1 GB of RAM

   Note:  If deploying Maximo Anywhere to iOS devices (iPad and iPhone) a MacBook notebook, iMac, Mac Pro or Mac mini desktop running OS X 10 or later is required to build the applications.

*Note:  IoS 13 is supported as "Runs On"
In addition, it has been built and tested using using xcode version 10.x
It is not tested and supported on the latest XCode versions for IoS 13.

Windows 8.1 or 10 Tablets

   Disk space: 300 MB per application minimum; 1 GB or higher per application is recommended for maps and attachment files

    Recommended Memory: Minimum 1 GB of RAM 

    32 and 64-bit systems with Windows 8.1 or Windows 10

     Multicore CPU and 64 bit

  Note:  if building the apps for Windows 8.1 or 10 Tablets, then Windows 8, Windows 10, or Windows 2012 Server R2 is required.

Other notes:

    Medium, large, and extra large size screens are supported.
    Medium, high, and extra high densities are supported.
    An environment that supports HTTP protocol, such as LAN TCP/IP, WiFi, cellular, or satellite communications, is required.

Software requirements

Required third-party software

The following software is used with Maximo Anywhere:

• Android SDK, API 14 or later is required to build Maximo Anywhere mobile apps. Building by using the android-23 platform and running on Android 6 and 7 is also supported. Ensure that you start your Android SDK Manager and download the Android 23 platform before you rebuild the android apps. For push notification, Android 28 SDK is the minimum supported version for Android apps.
• Google Chrome is required to view the deployed applications in the MobileFirst Console.
• The Oracle Java Development Kit (JDK) is a prerequisite for Android development and its subcomponent, the Java Runtime Environment (JRE), is required to run MobileFirst Studio.The following versions are supported:
  • For building with Android using the latest build tools, Oracle Java 1.7 is required
  • Oracle Java SDK/JRE/JDK 7.0
  • Oracle Java SDK/JRE/JDK 6.0 Update 45
• Other Java SDKs are also supported for some components:
  • IBM Java SDK/JRE 7.0 for the IBM MobileFirst Server
  • IBM Java SDK 6.0 for the IBM MobileFirst Server
  • Oracle Java 1.7 is now supported for the IBM MobileFirst Server

Other software information:

• For middleware software requirements, such as databases, refer to Software Product Compatibility Reports

  For hardware requirements only, select Create report under the Hardware requirements section. Fill in the product name and the version that you are interested in. You can either print or download the report as a PDF.

  For a more detailed list of requirements, select Detailed system requirements.

• If you are installing Maximo Anywhere 7.6.3 into an environment that contains other industry solution's mobile apps (ex.Maximo for Nuclear Power Operator Round), include the following:
  • MobileFirst Platform version compatibility based on the version on which the mobile apps are run

  • Java/JDK version compatibility

  • Maximo Anywhere 7.6.3 has a new skin that might affect app usability if there are unique controls that are not part of the Maximo Anywhere mobile apps

  • With the Android platform, Maximo Anywhere 7.6.3 uses the Gradle build instead of the ant build.

                  *Note: Gradle build process download jars from the internet and due to this, Internet access is required 

• Multitenancy environments are not supported.
• A Windows device that has a low camera resolution might result in poor performance of the camera bar code scanner. A device's camera has low resolution if you point the camera to a bar code and you cannot make out the difference between the lines because of blurriness. Such devices need an enlarged bar code picture. You can tell that it is enlarged enough when you can see the difference between two lines in a bar code from the device's camera.

  Useful link: https://www.microsoft.com/surface/en-us/support/hardware-and-drivers/troubleshoot-photo-and-video-quality

• If your virtual keyboard is not working on Windows 10, follow these instructions
• For the ability to enable push notifications, Maximo Asset Management 7.6.0.4 or greater is required.

Other information

Bar code types

Bar codes are supported with Blue-tooth enabled external scanner and device camera.  If the device has an in-built bar code scanner - then it is not supported.

    Note:  For bar code scanning, a 5 mega pixel camera that has autofocus is required.

Supported bar code types by device type:

For Android devices, the QR bar code type works for simple scans with only one value, such as the asset number.

RFID

• Only Bluetooth RFID scanners are supported with Android, iOS, and Windows.
• RFID scanners must be in human interface device (HID) profile. Refer to your device's owner's manual to determine whether your device can use the HID profile.
• All frequencies, ultra high frequency (UHF), high frequency (HF), and low frequency (LF), are supported if the RFID scanner is Bluetooth-enabled and in HID profile.

Map information

Maximo Anywhere Version 7.6.3 supports IBM Maximo Spatial Asset Management 7.5.0.1 to provide positioning information that determines the location of a work order on a map. If your enterprise system includes Maximo Spatial Asset Management, positioning information is obtained from work order objects that are linked to a map feature.

If Maximo Spatial Asset Management is not in your environment, positioning information is obtained by using non-linked objects.

ESRI offline tile packages (TPK) can be processed to display basemap tiles on Windows systems. Unlike iOS and Android systems, the map control uses JavaScript to consume offline TPK files on Windows systems. This capability supports TPK packages that are built by using only web mercator projection with spatial reference WKID 102100 (EPSG 3857). For more information about this projection, see the Spatial Reference.

This restriction is for basemap tile projection on Windows systems only. Android and iOS offline maps work with other ESRI-supported projections. Coordinates for Maximo work orders are maintained by using the Maximo Spatial Asset Management configuration. Spatially enabled work orders are transformed to web mercator at the time of the projection in the map control.

For geographical information system (GIS) data that is maintained in other coordinates, such as NAD83 or New York East State Plane Coordinates, ESRI software can reproject the data in web mercator. This projection can occur at the time of the TPK package creation.

For Maximo Spatial Asset Management maps that are newly supported by this release of Maximo Anywhere, Maximo Spatial Asset Management 7.6.0.2 or later is required.

Push Notifications

In 2019, push notification support has been migrated  from Google Cloud Message (GCM) to Firebase Cloud Messaging (FCM).  If your organization has a firewall that restricts the traffic to or from the Internet, you must complete the following steps:

1. Configure the firewall to allow connectivity with FCM in order for your FCM client apps to receive messages. The ports to open are 5228, 5229, and 5230. FCM typically uses only 5228, but it sometimes uses 5229 and 5230. FCM does not provide specific IP, so you must allow your firewall to accept outgoing connections to all IP addresses contained in the IP blocks listed in Google’s ASN of 15169.
2. Ensure that your firewall accepts outgoing connections from MobileFirst Server to fcm.googleapis.com on port 443.