The pre-existing (pre-2017) web app was written as a proof of concept and to provide basic capabilities to administer users and licenses. This tool was written around a forms based framework, which is now dated and doesn't follow modern conventions. A new web app is proposed to provide modern look and feel, and add expanded capabilities.

NOTE: This page has been superceeded by the the newest revision of WebApp stories (after 2018-07-24)

The new web app (AccessWeb2) will provide the following areas of functionality:

• AccessClient file access
• Project centric management
• Vehicle and tracker management
• User administration (customer level)
• License administration (customer level)
• User profile management

The web file app is functionally complete and we're working on visual refinement. This is a pass on visual changes to the actual page.

Revisions in Red (L=leftalign, R=rightalign, FR=Float:Right, C=Center

I tried to do a very light touch on the css. If for some reason you need it for reference it's available here:External Link

The web based access client is to replace the current desktop (Java) program (which is actually a semi-productized prototype). The web application has the advantage of “zero” deploy, and available to all platforms (even mobile).

The following image show a the overview of the access client. There is a list of important things to notice after the image.

Notice the following details:

• The left pane shows folders, but sorted by category: Projects, Archived Projects, Files (non project based)
• Projects are sorted by:
• Archived projects show files inside of archived projects. If they are proper archives, list proper project name
• The right hand pane shows contents (subfolders or files)
• Selecting right hand folder expands the folders
• Buttons on right hand pane allow deleting, downloading, or creating new folders.
• TBD: Mechanism for archiving and restoring projects.
• TBD: Right click context menu

This image shows what happens when expanding a folder in the left hand pane.

This image shows selecting a folder in left pane, showing the contents, in this case, some files.

• TBD: public link operations
• TBD: Drag and drop

Project management is the synthesis of several project aspects of project related data contained in the Access server:

• “Machine Tracks” (auto tracking via vehicles)
• Photos
• “User tracks”
• Measure areas
• Notes
• Cost Codes and coded data

A project also has associated with it a Project Journal, which is time stamped. The journal will contain references to the previously mentioned data items, and the journal may be displayed as part of the project summary. Items to note are listed after this image:

• Projects overview has 3 different sorting bands: Today, Yesterday, Other days
• Each project is shown with a summary card
• Summary cards are composed of the Project tite, map button, configuration button; latest update time, time range for theday; summry details
• Card buttons allow access to project configuration and mapping of the day
• Summary details could be the Journal, Day timeline, tracking statistics, tracking progress.
  • Journal is the time sorted list of journal events maintained by the server
  • Day timeline is the track timeline the same as SmartTrack (TrackManager)
  • Tracking statistics is the same as SmartTrack (TrackManager)
  • Tracking progress is a barchart showing progress against expected totals (to date).
• Nav buttons on the left side provide sub-navigation within Projects
  • “+” allows creation of new projects
  • “Dozer” allows access to machines page
  • “Table” allows access to cost code page
  • “Map” allows access to TBD
• Configuration of which of the four sub-modules are displayed in the project
  • Journal (Journal File Storage)
  • Timeline TBD:
  • Progress TBD:
  • Machine statistics TBD:
• TBD: Show project map for latest day, integrate with Google maps.

Clicking on the project opens the day detail for that day. This image shows an example day detail view: (NB: The four buttons on the left are a story board artifact and not in the actual implementation)

• Each track for the day is listed with it's time line view, the vehicle name, the actual time range, and operations.
• The time range graphic respects the project working hours, as defined in the project settings.
• Operations on the track include:
  • Mapping the track
  • Downloading the track (GPX/LLA)
  • Deleting the track.
• Below the tracks are:
  • The day's journal, in it's own pane
  • Statistics box, with drop downs to select vehicle classes.

Creating a new project is done from the project overview page, using the “+” button.

• A “create project” summary card is inserted into the display.
• User can specify the project name and description (text fields), timezone, and code list.
• This should have the configuration checkboxes here for the four project sub-cards.

Pressing the CostCodeList button allows the user to edit cost codes:

All known cost code lists are listed in the upper portion of the left hand pane. Below the pane are buttons for creating a new CostList, editing, and deleting the cost list.

• Edit boxes at top are for adding new items. Use a “+” button to left and it should appear like the “new machine” does.
• Left hand pencil, “Edit” allows user to edit the list name.

The web app provides the ability to create new vehicle descriptions and assign them to trackers and projects. Vehicles provide a descriptive capability to the actual work done in the project. When combined with cost codes and amounts allow the system to make predictions about future performance, allowing users to compare the current activity to planned activity.

The user arrives here by selecting the “Dozer” button from the project over view.

• All machine colors shall be round (unlike rows 3 onward in this image)
• Pressing the map icon will locate the vehicle (tracker actually) by invoking a google maps link.
• The batter icon will show the current amount of charge on the tracker, but clicking it will show a graph.
• Configure icon will allow the user to edit details such as name, color, etc. Same as “new”.
• TBD: Delete is really making a vehicle inactive.

• Details on the machine are to be edited similar to “edit” of the machine.
  • The name must be assigned.
  • Trackers may be assigned.
  • A project may be assigned.
  • The quantity may be changed.
• Machines are sorted by project
• TBD: Menu option: Other sorting option (ST support sort by type).
• TBD: Menu option: Show inactive…

Customer admins will retain the ability to create, update, or delete users. The may also assign users to licenses.

Customer admins will retain the ability the assign users to licenses, or change the maximum amount of checkout time on a license. (stretch goal: provide license event log to customers? - mja)

Users will be able to to edit various information of their user profile, like email address and password.

The current Access page has a Logout button in the upper right of the page header. This will change to a button titled with the userid of the logged-in user, with a glyph of a user. Clicking on this button will show a menu with two options: 'USER PROFILE' and 'LOG OUT'. Clicking on LOG OUT will do the same as the current Logout button.

Clicking on USER PROFILE will post a new page which has the controls to view and edit profile information.

There are two main sections to this page: User Profile and Assigned Keys.

In the User Profile section there will be a series of labeled edit fields for the pieces of information in the user profile. In this version all but the 'Login' field will be editable, 'Login' will remain readonly. Following the series of edit fields will be buttons labeled 'Save' and 'Cancel'. Clicking on Save will validate the fields for completion and correctness, and then dismiss the page, going back to the page the user was last on. Pressing 'Cancel' will just dismiss the page and return user to the last page. A number of the labels of the edit fields are marked with an asterisk indicating these are required fields. If a user attempts to Save with one of those edit fields empty (containing only white space characters), the save operation will not complete and the user will be prompted via a message as to what needs to be done. Similarly, if the email field does not have text in valid email format, user will be prompted to correct. If the value of the Confirm Password field does not match the value of the Password field, the user will be prompted to correct.

The Assigned Keys section will consist of a read-only dashboard of zero or more entries of keys that the user can access. Each entry will consist of the key value and the list of applications for that key.