---
alias: meddev-feature-mobilecockpit
render_macros: false
---

# Mobile Cockpit

## Overview

Shop floor operators currently need to navigate the full MES interface to perform the most frequent and time-critical operations at a resource: checking in, dispatching, tracking in, and tracking out materials. On the shop floor, operators work with handheld Zebra devices that have a built-in scanner but a small screen, making the standard MES interface impractical to use efficiently.

### Concept

The feature provides a lightweight, scan-driven Operator Cockpit tailored for the Zebra device enables operators to perform these core operations quickly, accurately, and without relying on a desktop terminal, reducing wait times, minimizing navigation steps, and keeping operators focused on the physical work at hand.

---

## Assumptions

To use Mobile Cockpit function, the following conditions should be followed:

- The lookup table `MedDevMaterialStateForMobileCockpit` has data.

![MedDevMaterialStateForMobileCockpit](features.images/mobilecockpit-lookuptable.png)

- The Resource attributes `MedDevMobileCockpitDefaultDispatchAndTrackIn` and `MedDevMobileCockpitDefaultTrackoutAndMoveNext` set as true.

![Resource Attribute](features.images/mobilecockpit-resource-attributes.png)

## Example Scenario

This section briefly introduces how to use Mobile Cockpit feature.

### Entry

![Entry01](features.images/mobilecockpit-entry01.png)
![Entry01](features.images/mobilecockpit-entry02.png)
![Entry01](features.images/mobilecockpit-entry03.png)

### Scan Resource and Check In

Scan a Resource that you want to operate, if the Resource need to Check In, then you need to Check In first.

![CheckIn](features.images/mobilecockpit-checkin.png)

### Search

After scanned a resource, the page will display all the materials with the material system state of Queued on this resource.

![Default List](features.images/mobilecockpit-defaultlist.png)

You can search according material system state and material name.

![Search](features.images/mobilecockpit-search01.png)
![Search](features.images/mobilecockpit-search02.png)

### Scan Material

If you want to select a material, you can scan it or select it manually.

If you want to cancel a material, you can scan it again or cancel it manually.

### Insert Barcode

Relevant information can be manually entered vio the `Insert Barcode` button in the menu bar.

![Insert Barcode](features.images/mobilecockpit-insertbarcode01.png)
![Insert Barcode](features.images/mobilecockpit-insertbarcode02.png)

### Dispatch and Track-In

You can select the materials these you want to Dispatch and Track In.

![Dispatch and Track-In](features.images/mobilecockpit-dispatchandtrackin01.png)
![Dispatch and Track-In](features.images/mobilecockpit-dispatchandtrackin02.png)
![Dispatch and Track-In](features.images/mobilecockpit-dispatchandtrackin03.png)

### TrackOut and Move Next

You can select the materials these you want to TrackOut and Move Next.

![TrackOut and Move Next](features.images/mobilecockpit-trackoutandmovenext01.png)
![TrackOut and Move Next](features.images/mobilecockpit-trackoutandmovenext02.png)
![TrackOut and Move Next](features.images/mobilecockpit-trackoutandmovenext03.png)

# Mobile Cockpit Known Issue – Lookup Table Not Found

## Issue

When opening the **Mobile Cockpit**, the following error may be displayed:

> **The data for the LookupTable with Name= was not found in the system.**

This is a known product issue and is expected to be fixed in a future product patch.

![LookupTable not found](features.images/mobilecockpit-knownissue01.png)

---

# Temporary Workaround

Follow the steps below to resolve the issue until the product fix is available.

## 1. Create a New UI Version

Create a new version of the **Mobile Cockpit** UI with the desired Change Set selected, or create a new Change Set.
![Create or select Change Set](features.images/mobilecockpit-knownissue00.png)
![Create new version](features.images/mobilecockpit-knownissue02.png)

---

## 2. Enable the Tabs Widget Header

1. Edit the UI Page.
2. Open the **Tabs Widget** settings by clicking the widget menu.

![Edit Mobile Cockpit UI](features.images/mobilecockpit-knownissue03.png)

3. Enable **Show Header**.
4. Click **Save and Close**.

> **Note:** This temporarily exposes the widget title, allowing you to identify the correct widget.

![Enable Show Header](features.images/mobilecockpit-knownissue04.png)

---

## 3. Open the Resource Materials Widget

1. Click the menu of the **Resource Materials** widget.

![Open Resource Materials Widget Setting](features.images/mobilecockpit-knownissue05.png)

2. Verify that the widget **Name** is:

```text
Resource Materials
```

![Resource Materials Widget Setting](features.images/mobilecockpit-knownissue06.png)

---

## 4. Refresh the Lookup Table Reference

Navigate to the **Custom Filters** tab.

For the **SystemState** filter:

1. Select **SystemState** from the filter list.
2. Copy the **Reference Type Name** value: **MedDevMaterialStateForMobileCockpit**.
3. Click the **X** button to clear the field.
4. Paste the copied value into the lookup search box.
5. Select the same lookup table from the search results.
6. Click **Save and Close**.

![Custom Filters](features.images/mobilecockpit-knownissue07.png)

---

## 5. Disable the Tabs Widget Header

1. Open the **Tabs Widget** settings again.
2. Disable **Show Header**.
3. Click **Save and Close**.

![Disable Show Header](features.images/mobilecockpit-knownissue08.png)

---

## 6. Verify the Result

Open the **Mobile Cockpit** again.

The Lookup Table error should no longer appear.

![Mobile Cockpit resolved](features.images/mobilecockpit-knownissue09.png)

---

## 7. Save the UI Page

Finally:

1. Save the UI Page.
2. Click **Request Approval**.

---

# Summary

This workaround refreshes the **Reference Type Name** used by the **SystemState** custom filter.

1. Create a new UI version.
2. Enable the **Tabs Widget** header.
3. Open the **Resource Materials** widget.
4. Re-select the **Reference Type Name** for the **SystemState** filter.
5. Disable the **Tabs Widget** header.
6. Save the UI Page and submit it for approval.

> **Note:** This workaround is only required until the official product fix becomes available.