This is a revamp of the Engineering tracking website to be more track friendly. The goal is to not invest too much time on this version but update the look and feel as well as optimize the tracking organization to be more useful.

The paint has been applied although it needs a little touchup here and there.

I'd like to reorganize the Menu order and defaults. If the user has Track & Enterprise the menu order should look this:

There's no interface on our ecosystem at this time to backup, restore or delete projects. I'm thinking this functionality is probably on the next to-do list.

There's currently no method of reporting the segments, segment notes and cost codes reported in SmartTrack as any kind of output. Writing them out as a Kml/KMZ would create a method (even if it's not optimal) to get the data out and into Earthwork 4D (it has kmz import). The output could also be displayed as part of the Access, tracks webpage whether we capture the statistics at creation on the view or whether we calculate them on demand from the web.

• Projects - The initial view and dashboard for field activity.

• Access -

• Admin -

The Project Dashboard is the heart of the Web field system

Project Dashboard Example

• Left Controls
  • Add new Project (on same page)
  • Machine Page - Go to Machine List
  • Cost Code Page - Go to Cost Code Page
  • Map - Create a KMZ map of all projects - We may actually want to create an on screen version as well
  • Space
  • View Inactive - Allowing me to see old projects I may have made inactive. The same concept as inactive machines?

• Today's Projects Container
  • Individual Project overview/Widget. One for each project active that day
    • Project Name
    • Configure Project
    • Map Project - Show daily activity on map/kmz
    • Last Activity
    • Activity Range
    • Any involved Machines (summarized by type. Can be expanded to show just a type with more detail on this page.
    • Modular Info based upon user desires, stage of job, notes
      • Potential Modules
        • Motion timeline - Starts and stops
        • Job Docs. Timeline notes, Notes, Tracks, Pictures, Measure Areas (may limit to those with notes or key codes for this view)
        • Progress graphs assuming we have some input method
        • View Statistics - Defining of default views, view triggering events
        • Select Statistics - For example TNT just wanted to know average move time per cycle. Or Moving hours, yards per hour. Lots of options here that will be part of Project/user configuration. The Project configuration currently sets stuff line Timezone, code lists, background files, etc. There's also a view element that could be default by project but is ultimately dependent on the user. A foreman for example might want a different view than a boss or not even care about some projects that aren't his.

• Yesterday's Projects Container
• Jobs don't necessarily run everyday but we still need a way to see them. I'm putting them in a different container later on the page. Otherwise the content is the same as Today's.
• Earlier Projects Container
• Jobs don't necessarily run everyday but we still need a way to see them. This is for stuff older than two days. We may change the granularity of these containers with experience but the idea is to separate them from the active data coming in.

These are for general interface and functionality. Actual look and feel will depend somewhat on the framework chosen. Development is ongoing.

Machine List Example

Sorted by Project by default

List controls on the left

New machines and edit takes place on the same page with interface. The goal is to have fewer sub-pages.