Optimiz Resolved Issues May 9, 2012

(1)

Optimiz

(2)

Landing Page

Updated Landing Page

Rather than opening to a blank page, Optimiz now opens to the Load Management page.

Entities

Updating an Entity’s Postal Code when Adding a New Entity

Changing an entity’s postal code during entity creation automatically updates the City and State fields to display the correct city and state for the new zip code.

Entity Search Results

When you conduct an entity search the results appear in alphabetical order by first letter of Entity name, rather than in numerical order by Display ID.

Entity Suggestions

Entity suggestions that appear when adding a new entity through the Entity Search section of Optimiz have been updated to contain the following additional details:

(5)

Load Entry

Updates to the Equipment Type field in the Primary and Secondary Carrier Tabs

(6)

Load Management

Load Details

The Details section of the Load Management screen now includes the Carrier Name, Route Name, and Carrier contact for the selected load.

(7)

Updated Cancel Tender Dialog Box

When users click the Cancel Tender button on the Load Management page, the cancel tender dialog box that opens now reads “Do you want to cancel the tender?”

Load Management Error Messages

Users who click the exception column on the Load Management page will no longer receive a server error message.

Optimiz will no longer return an error message when shipments or stops are removed from a load plan and the load is re-tendered.

Load Management Searches

Load Management searches will no longer carry over to the Load history page, and vice-versa.

Re-Tendering Loads

When a load is re-tendered for a reason other than an auto-generated tender sent to the Secondary carrier due to time expiring for the tender to the Primary carrier, the “Added By” column of event log entry displays the username of the user who re-tendered the load.

(8)

Load Tendered to Secondary Carrier

If a primary carrier rejects a tender and the load is tendered to the secondary carrier, the load event log records the tender event and then the load details and grid update to show the secondary carrier’s name in the Carrier field.

Cancelled Tender Email

(9)

Duplicate Entries in the Event Log

Duplicate entries for the same event, including load creation, will no longer appear in the Event Log. For example: when a tender is accepted, currently a ‘tender accepted’ event and a

‘scheduled’ event appear in the event log. Moving forward, the only the ‘scheduled’ event will be created.

In addition, Optimiz will no longer add an ‘accepted’ event to the event log when tenders are accepted. Instead, these details will be associated with the ‘scheduled’ event.

Event Types

(10)

Load Editing

When action is taken on a load instance or load plan (Edit Load page), the Edit Load page will no longer automatically close once the Save Load button is clicked. It will remain open on the screen until the user navigates away from the page.

Check Call Reporting Updates

Check Call Exceptions

The check call exception icon was changed. It is no longer a green box with a “C” inside it, it is now a blue box with a phone and a green arrow.

Loads with check call exceptions now display in the search results when the exceptions search option is selected in the Load History or Load Management search panel.

Incorrect check call exceptions for in-transit interval and stop departure check calls will no longer be generated by the system.

Missed Check Call Reporting

(11)

Check Call Update Service

Optimiz runs an update service every 15 minutes looking for stop arrival, stop departure, or in-transit check calls. If any are detected, load records are updated accordingly.

Stop arrival check calls are expected to have been made between the stop appointment times entered during load entry. Interval check calls are expected to be made “every ‘x’ number” of minutes from the appointment end time of stop 1. The interval check calls are also afforded a 15 minute grace period before and after the expected time to give carriers more flexibility in

entering check calls (e.g. if interval check call was expected at 12:00; the system would consider a check call “good” if it was made between 11:45 and 12:15).

Stop Departure Check Calls

Stop departure check calls will no longer trigger an exception if missed. While they are

(12)

Load Instance

Pro Numbers

Pro Numbers now appear in the load details section of the Load Instance page.

Editing Load Instances: Updates to the Equipment Type field in the Carrier Tab

(13)

Load History

Declined Loads

Loads declined on the Planning Management page will now appear on the Load History page in “Declined” status.

Cancelled Loads

The status column for all cancelled loads displays “Cancelled” regardless of where in the load planning process the load was cancelled. In addition, Loads in “Cancelled” status on the Load History page will no longer display a tender exception in the Exceptions column.

Updates to the Load History Grid

(14)

Load Details Section

The Details section of the Load History page now includes the Carrier Name, Route Name, and Carrier contact for the selected load.

Load Search

Recurrence Column

(15)

Planning Management

Updates to the Planning Management Grid

The Status column has been removed from the Planning Management grid and replaced with a new column, “Route.” It appears as at the far left of the grid and displays the custom route name assigned to the route.

Updates to the Load Details Section

(16)

Carrier Portal

Missed Check Call Notifications

Missed check calls will show in the carrier portal event log.

Entering Check Calls on Cancelled Loads

Carriers can no longer enter check calls on cancelled loads.

Load Details on the Carrier Portal Tender Page