Tracker App - Production

Overview

BOS Enterprise has a Tracker app that is designed for staff to record data as they produce or deliver goods. It can also be used for Field Service. It is integrated with Production Planning, Timekeeping, Deliveries and Field Service.

The Tracker app can be run in:

  • Dual Mode (Connected and Offline): The application runs on a Local Database which is populated from and then replicated to the Live Database when an internet connection exists. The Local Database is a metadata backup of the Live Database.
  • Connected Mode: Connects directly to the Live Database without an offline option.
Note

Only the Field Service and Deliveries modules support Dual Mode.

Tracker.exe can be downloaded from Tools or the Shared Drive\Downloads\... folder. For Dual Mode, a Data folder needs to be created and contain a metadata backup of the BOS Enterprise Database which must be made from the Live Database after it is upgraded.

This document focuses on Production Timekeeping.

Login Screen

  • Keypad: You can use it to type in your password (code).
  • Login (button): A colour-coded button that is green when connected, and red when offline. You can tap it to log in once the correct code is entered on the keypad.
  • Settings (button bottom right-hand corner): Opens the Setup Database Connection screen.

Setup Database Connection

  • Radio buttons to select a Mode:
    • Connected:
      • Will always work online and update the server in real time.
      • The app is unavailable if not connected.
    • Dual – Connected and Offline: 
      • You need to connect to the server to download user and transaction data and to upload your data.
      • If the device is used while connected to the internet, the server is updated in real time.
      • If the device is not connected, the data is saved on the device and uploaded once the device is connected to the internet/server.
      • Only available for Field Service and Deliveries.
  • Live Database:
    • Server: 
      • Enter the name of the Server for the TRACKER.INI file.
      • Dual – Connected and Offline: [SERVERDB] path = server:localDBpath and [LOCALDB] path = server:localDBpath.
      • Connected Mode: [SERVERDB] is not required. [LOCALDB] path = Live DB (e.g. 34.243.32.223:C:\QuickEasy\Data\QUICKEASY.FDB).
    • Database: Enter the name of the Database for the TRACKER.INI file.
    • Create TRACKER.INI file (button): Creates the TRACKER.INI file for the database connections.
  • Back (button): Returns to the login screen.

Main Screen

  • Refresh: Updates the data.
  • Logout: Logs the user out and returns to the login screen.
  • Deliveries per activated Transaction Type (e.g. DN Deliveries): Transfers users to the Deliveries interface.
  • Field Service per activated Transaction Type (e.g. WO Field Service): Transfers users to the Field Service interface.
  • Timekeeping: Transfers users to the Timekeeping interface.

Timekeeping

Buttons Explained

Button Description
LogoutLogs the user out and returns to the login screen.
StartStarts the selected task.
Start DowntimeStart downtime.
Show NotesDisplays the notes.
RefreshUpdates the data, including the durations of the Active Jobs.
BackReturns to the main screen.

Left-Hand Side Interface Explained

  • Active Jobs – Username: A clickable banner that refreshes the times of the Active tasks below it.
  • Active Jobs – Username (below): Lists the current active jobs.

Right-Hand Side Interface Explained

  • Name of Stage: A clickable banner for you to select a different Stage.
  • Production Stage Name (below): Lists the Work Order Number and the details of the task that must be performed for the selected Stage.

Active Tasks Interface

  • Lists the available Workstations for you to select one.
    • Default Tab: Lists the Workstations for the Stage that is currently selected.
    • Tabs with alphabet letters: Lists the other Stages alphabetically, for you to select a different stage.
  • Logout (button): Logs the user out and returns to the login screen.
  • Next (button): Continues to the next screen.
  • Cancel (button): Cancels the task and returns to the task selection screen.

Select an NCR (if applicable)

Buttons Explained

Button Description
LogoutLogs the user out and returns to the login screen.
Start
  • Starts the job based on the NCR selection.
  • Returns the user to the list of tasks.
    • The active task shows Run on the left user list and appears in green on the right under the Stage list.
CancelCancels the task and returns to the task selection screen.
BackReturns to the previous screen.

Fields Explained

Field Description
Not linked to NCRButton for a normal task that is within the constraints.
NCR PendingButton to complete a task that is outside the constraints (that is, it does not conform to the specifications).
NCR numberIf an NCR already exists, it is listed there for selection.

Stopping a Task

  • You can click the red block on the task that shows Run to stop it.
  • If confirmed, they are transferred to an interface where they can select either Part-Complete or Complete.
  • The job appears with three coloured blocks representing the statuses as follows:
    • 🟨Yellow: Set the status to Pending.
    • 🟦Blue: Set the status to Active.
    • 🟩Green: Set the status to Complete.
  • Clicking the red stop button finally stops the job.
  • Logout (button): Logs the user out and returns to the login screen.
  • Next (button): Continues to the next screen: Select a Status.
  • Cancel (button): Cancels the last action and returns to the screen from which the last action was initiated.

Select a Status

  • You can select the following:
    • Complete: To indicate that the job is complete.
    • Part Complete: To indicate the job is partially complete.
  • Logout (button): Logs the user out and returns to the login screen.
  • Stop (button):
    • Stops the task.
    • Returns to the task selection screen.
    • Removes the task if it was marked complete.
  • Cancel (button): Cancels the last action and returns to the screen from which the last action was initiated.
  • Back (button): Returns to the previous screen.

Open Records

On exiting BOS Enterprise, you are asked to confirm your exit if one of these two conditions exist on the Tracker app or in BOS Enterprise:

  • One or more records are not uploaded to the Server.
  • There are open Timekeeping records.

Report an issue with this page

For more useful feedback, select the text on the page you're reporting about, then click Feedback again — or continue without selecting anything.