• Implement the ability to interact with multiple Accounts

• Implement Signal-r to deal with multi users accessing the same data

        - There will be multi users attempting to use and edit the same data throughout Event

        - This process will track users and provide each user with visibility on which other users are in                 the same product on the same day filters (i.e. maybe date window, but if includes same date)

        - This process will prevent a user from being able to edit / action a Route currently being viewed               by another.

        - We must not allow overwriting, duplication for deletion.

• Update Connect process in VITALS

        - Include ability for superuser to connect with another account and to connect with an edit                       profile. Allowing the Account to view and edit the connecting accounts data.

        - Include ability for superuser to update current connection from 'view only' to 'edit'.

        - This will include an edit by product. So a user can request to connect and edit ROUTE, VITALS,                 DOCK

• Implement additional notifications to deal with issues where moves in route are not possible due to location Account specific to not confuse user. 

• Use connection process as explained in Multi Account Visibility, through invite function.

• Once connection is confirmed we will immediately update user profile with connecting data.

        - including configs, searches, filters, 

        - Route data, Vitals data

• User will be able to view connected Accounts individually

• User will be able to view selected connected accounts in same view together

• User will be able to view all routes / stops through grids as current

• User will be able to set the Route Control screen to show just the data they want to see.

            - This will include additional new fields for Stops on the route

            - Blades will be updated to allow user to set there position and width even on refresh

• User will be able to view all Routes / Stops on new interactive map interface

• User will get ability to configure Route to setup blades as preferred.

• User will be able to interact with map and view Order detail in Order Control as required.

• User will be able to move Stops between routes on mapping

• User will be able to see mapping by Route filters, only single day in phase 1

• User will be able to open map up to full view in blade

        - Close the view route blade header, Event bottom section and Event header section to create                   largest screen open

        - Provide a UI button for this to close all above and open all above.

• User will be able to move Stops between Routes for different Accounts

• User will see Stops showing which Account easily

• User will get warnings if they are moving Stops between Accounts (configurable )

• User will get KPI view to see how change affects overall Plan KPI

        - Includes plan cost, plan distance, plan greenhouse gas, % empty fill...

• User will get overlays in map to view

        - Stop summary address

        - Stop % load fill

        - Stop equipment

        - Stop date, time

        - Stop Account owner

        - Distance, time, delays to next stop / between Stops

        - Total route distance, time, delays

• Ability to select a route to view possible return routes

        - User can select a route, we will use AMI to identify the delivery time, empty run to offer best                     return load based on return loads delivery times.

        - Store all options and those selected by user for AMI

        - Enable a user to link the routes 

• Show backload options, link backloads

• Use AMI to suggest backloads

• Ability to discount backloads (through tariff for manually)

• Auto reoffer route on rejection by carrier

• Auto hide carrier rejection for lane for that day. Where carrier rejects, do not show in Carrier Control.

• vv