The main function here is assigning trackers. There's no copy protection on this program but there does need to be a login to allow a customer to see trackers assigned to their company.

We use are standard login screen from most apps to log into the server and see just what trackers are assigned to that company.

Changing logins can be done by going to Settings (gear on action bar)

The main screen allows the user to pick a tracker, see its current settings (project, machine, last track), reassign the project or machine and set those values for subsequent tracks. By nature (server does it?) when a machine is changed it breaks the tracks at that moment. The History button (name might change) will show all the tracks for that tracker, allow editing (project, machine) and perhaps might allow joining of tracks on the same day if moved and reassigned machines.

Add a battery indicator to current settings.

Trackers are picked from the list by number (later scan bar code and/or NFC). Only trackers assigned to that customer display. As soon as a tracker is picked, the current settings display below.

The user can change the tracker machine or more likely the project and press Set to change all future tracks from that moment. Once Set, the current settings below should change to reflect that and reinforce that they did go through.

Joe Foreman starts the app, logs in if it's the first time and gets the number (pick or scan). He sets the project and the machine and has it put on the machine (may hand off to mechanic or even do the machine later).

Joe Foreman goes to look at SmartTrack and wonders where the heck is the machine track. He remembers he forgot to move it from the old project to the new. He picks that tracker, sees the current settings are to the old tracker and does a Set after changing the project. All new points are going to now show up.

If he was really slow to catch the mistake he has tracks from previous days going to the wrong project. He presses history and he sees previous days of tracks. He taps the checkbox to select any number of days and presses the move button and the bottom of the screen. The program prompts him to select the new project and he selects it and presses Ok. The server does this and then refreshes the history to show the tracks have moved. Partial tracks moved to a project should be combined with any other tracks for that machine/tracker that were on that day. The likely scenario is he figures out the project mistake halfway through the day so he wants them combined.

This example screen shows a likely scenario where user has forgotten to move the tracker on 5:30. Setting the tracker to the new project has broken days track but not moved previous data for 5/30. The expectation would be that the user would pick the 5/30 checkbox and press the Move button and choose the new project. That days data would merge together.