This is an old revision of the document!
Table of Contents
TrackTools is a fill in name until Marketing can think up a product name. It's main purpose is to give an easy way for job site workers an easy way to assign the DCS (or other) trackers to a project and a machine. A side benefit will be an additional mode where tracks and trackers can be moved, reassigned, renamed, deleted? or otherwise edited in a single interface. Machines edited and made not active as well.
I could easily see a web version of this interface as an office supplement and this will probably end up on the Apple and Android Play stores.
First Screen - Log in and Tracker Assignment
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.
Login
Assign Trackers Main Screen
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.
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.
Changing settings
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.
Typical New Tracker story
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).
Typical Tracker edit story
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 does a Move to Project from the menu. The program prompts him for the new project and he selects it. 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.
Tracker info
Tracker/Tracks/Machine Edits
