Overview of Mobile Computing

You can use an APM mobile app on mobile devices running iOS or Android to collect data (indicator readings or inventory counts) and then upload the data into APM. In the process, you will assign activities to specific devices in APM, download activities, upload the collected data, and process uploaded activities.
This topic explains concepts related to mobile computing.

Mobile Computer Record in APM

When an employee installs an APM mobile app on a device and logs on for the first time, a mobile computer record is automatically created in the APM database. The computer name is set to the employee number and name, for example, “93 - Jane Smith”. The device type is automatically set to “iOS or Android Device”. Any activities assigned to the employee’s maintenance group or warehouse are downloaded to the device.
A mobile device record in APM provides a container into which computing activities (checksheets or count sheets) can be placed while they wait to be downloaded to the device. They also provide a place to view the history of past activities that were performed using the device.

Inventory Versus Maintenance Functions

A mobile device can be used for either maintenance or inventory functions but not both. The device’s intended functional area is controlled by a setting on its record in APM. If the device is intended to be used by maintenance, the computer must be assigned to a specific maintenance group. If it is to be used for inventory functions, it must be assigned to a specific warehouse. In either case, you can also optionally assign it to one of the employees who works in the maintenance group or the warehouse to which the computer is assigned.

Mobile Computing Activities

A mobile activity is a task that has been assigned to a mobile device to be carried out. There are two types of mobile computing activities:
Checksheet activities can be created from work order tasks, standard jobs, and standard tasks. Count sheet activities can be created from prepared count sheets. You can view mobile activities created from all sources at the site level.
Mobile computing activities contain the following information:
Title of the checksheet or the count sheet
Reference to a checksheet or a count sheet

Life-cycle of a Mobile Computing Activity

A mobile computing activity’s life-cycle in APM has five stages: creation, assignment, downloading, uploading, and processing. When viewing activities in the site’s Mobile Computing view, you will notice that each activity’s status indicates its stage in the life-cycle.

Creation

When an activity is created, it is given the status “New”. The activity remains in this status until it is assigned to a mobile device.

Assignment

An activity is next assigned to a specific mobile device. The activity’s status becomes “Assigned” in preparation for being downloaded to the device.

Downloading

The downloading stage involves transferring the activity (checksheet or count sheet) from the desktop to the mobile device. After this occurs, the activity’s status becomes “Downloaded”. In the case of a count-sheet activity, this stage signifies that the count has begun, which “freezes” the items being counted and prevents any transactions from being entered for them.

Uploading

The uploading stage involves transferring the completed activities from the mobile device to the APM database. Once this occurs, the status of uploaded activities becomes “Uploaded”.

Processing

In the final stage, the uploaded data is incorporated into the APM database. This step can be performed automatically by the Upload Transaction Broker or manually from the site’s Mobile Computing view. Once an activity has been processed, the activity’s status becomes “Closed”. Closed activities are saved for historical and audit purposes.

One-time and Repetitive Activities

Checksheet activities that originate from a standard task or standard job can be designated as repetitive. Repetitive activities are different from normal one-time activities in that they remain on the mobile device after the upload process has completed so that they can be reused again without having to be downloaded.
When a repetitive checksheet is uploaded, a new one-time activity is created in APM. This new activity references the repetitive activity on which it is based. The newly created activity is processed and closed in the normal way, while the repetitive one remains open with a status of downloaded.