Cloud Readiness / Oracle Fusion Cloud Transportation Management
What's New
Expand All


  1. Update 23A
  1. Revision History
  2. Overview
  3. Update Tasks
  4. Feature Summary
  5. Transportation Management
    1. Transportation and Global Trade Platform
      1. Enhanced Workbench
        1. Improvements to the Enhanced Workbench
      2. User Interface
        1. Redwood UI Look and Feel Improvements
      3. Data Export API
        1. Data Export REST API
      4. Document Management
        1. Document Set Capabilities Added for Additional Objects
      5. Performance and Stability
        1. Online Help Centralized on docs.oracle.com
        2. Limit CSV Export File Size
        3. Raise Status Change Events in New Process
        4. Use Fallback Locale for Missing Translations
        5. Filter Agent Events Based on Data Query Type
        6. Property Validation
        7. Disable CSV Remote Host Support
        8. Enforce Content Security Policy
    2. Transportation Management (Base)
      1. Appointment Management
        1. Appointments - Support Shipment Stops Requiring Multiple Appointments
        2. Appointments - Location Appointment View Start Time - Hours and Minutes
        3. Appointments - Set Stop Appointment Times Based on Stop Type
        4. Appointments - Service Provider Cutoff Time by Location and Location Resource
        5. Appointments - Tolerance Values for Appointments
      2. Ocean Enhancement
        1. Voyage Schedules - Internal or External Schedule Sources
      3. Mobile
        1. Mobile Application Enhancements
      4. Document Management
        1. Documents for Shipment Stop
      5. Spot Bid Tender
        1. Spot Bid Enhancements
      6. Rate Maintenance
        1. Rate Maintenance UI Refresh
        2. Use Enhanced Rate Maintenance Links in Emails
      7. Shipment Group
        1. Enable Ship Group SC Rule Rule Type Validation
        2. Shipment Group UI Web Action - Recalculate Secondary Charge Shipment
        3. Secondary Charge Rule Shipment Group Criteria
      8. Rate Service and Activity Time
        1. Equipment Reference Unit Location Activity Time
        2. Day Duration Rate Service Supports Same Day Pickup and Delivery
      9. Asset Position and Status Report
        1. Fleet Asset Position Report and Fleet Asset Status Report
      10. Usability and Performance
        1. Add Tracking Event to Shipments
        2. Keep Existing Service Provider for Unassign
        3. Allow Order Unassign When Rating Is Infeasible
        4. Check Tender on Shipment Delete
      11. External Distance Engines - Address Validation
        1. Here Technologies - Address Validation - Quality Level
        2. PC*MILER Web Service - Address Validation - Quality Level
        3. Oracle Map Cloud Service - Address Validation - Quality Level
        4. Property to Turnoff Postal Point Lookup
      12. Here Technologies
        1. Generate Rush Hour Data Using HERE Technologies Large Scale Matrix Routing v8 API - Asynchronous Call
        2. HERE Technologies Map - Location Clustering
      13. Here Technologies v8 Mandatory Upgrade
        1. Mandatory HERE Routing API v8 Upgrade for Enhanced Workbench Mapping
    3. Transportation Operational Planning
        1. Logistics Guide Template - Equipment Reference Unit (ERU) for Planning Templates
        2. Network Routing with Location Calendar
        3. Use Consol Flag Added to Network Leg
      1. Work Assignments
        1. Convert Multi Segment Shipment to Single Petal Shipments
        2. Resource Scheduler Sequencing Option - Current Start Time Ascending
      2. Service Provider Assignment
        1. Service Provider Assignment - Shipment Preference Criteria - Consider Utilization Options
      3. 3D
        1. Gross Center of Gravity - Calculate and Persist on Shipment Equipment
      4. Transportation Sourcing
        1. Enhanced Build Lane Summary with Volume Target Action
    4. Freight Payment, Billing, and Claims
        1. Aggregated Shipment Cost Lines
        2. Inv Line Appr-Stop At First Passed Det and Rule
        3. Enable Improved Invoice Approval Logic
        4. Shipment Cost Associated to Order Release and Stop
    5. Transportation Intelligence
        1. Data Visualization - Transportation Operational Intelligence Subject Area
        2. Status Dimension Subject Area - Order Release, Shipment and Invoice
        3. Order Release Dimensions for Earliest Estimated Pickup Date, Latest Estimated Delivery Date
        4. Additional Shipment Dimension and Fact for Equipment Reference Units
    6. Logistics Network Modeling
        1. Extend Logistic Network Modeling to Include Work Assignment Optimization
        2. Logistic Network Modeling - LTL Rate Discount Data Rule Enhancement
    7. Logistic Digital Assistant
        1. Logistics Digital Assistant Available in Global Header

Update 23A

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Module Feature Notes
15 DEC 2023 Transportation Management and Global Trade Platform Raise Status Change Events in New Process Updated document. Revised feature information.
18 MAY 2023 Transportation Management (Base) Appointments - Set Stop Appointment Times Based on Stop Type Updated document.  Corrected feature information.
17 FEB 2023 Transportation And Global Trade Platform Redwood UI Look and Feel Improvements Updated document. Revised Tips and Considerations for Known Issue.
21 DEC 2022 Mobile Mobile Application Enhancements Updated document. Revised feature information.
21 DEC 2022 Asset Position and Status Report Fleet Asset Position Report and Fleet Asset Status Report Updated document. Revised feature information.
21 DEC 2022 Enhanced Workbench Improvements to the Enhanced Workbench Updated document. Revised feature information.
16 DEC 2022     Created initial document.

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Update Tasks

This section gives you information to help you plan, deploy, and validate your update. We make frequent additions to this document, so don’t forget to check back and get the latest information before your update starts.

Review the Release Notes.

  • The release notes include fixes, special instructions, and resolutions related to the Oracle Transportation and Global Trade Management Cloud.
  • Release Notes can be found here:
    • https://support.oracle.com/epmos/faces/DocumentDisplay?id=2898941.1

Use the following resources to prepare for and validate your Oracle Engagement Cloud update.

On My Oracle Support Read:

  • Doc ID 2095509.1
    • Oracle Cloud Applications - Transportation and Global Trade Management Cloud: Environment Refresh Policy
  • Doc ID 2095528.1
    • Oracle Cloud Applications - Transportation and Global Trade Management Cloud: Quarterly Update Planning
  • Doc ID 2096782.1
    • Oracle Cloud Applications - Transportation and Global Trade Management Cloud: Quarterly Update Planning FAQs
  • Doc ID 2195580.1
    • Oracle Cloud Applications - Transportation and Global Trade Management Cloud: Get Started with Your Implementation
  • Doc ID 2508854.1
    • Oracle Cloud Applications - Transportation and Global Trade Management Cloud: Quarterly Updates - Preparation and Testing Recommendations

Feature Summary

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Transportation Management

Transportation and Global Trade Platform

Enhanced Workbench

Improvements to the Enhanced Workbench

User Interface

Redwood UI Look and Feel Improvements

Data Export API

Data Export REST API

Document Management

Document Set Capabilities Added for Additional Objects

Performance and Stability

Online Help Centralized on docs.oracle.com

Limit CSV Export File Size

Raise Status Change Events in New Process

Use Fallback Locale for Missing Translations

Filter Agent Events Based on Data Query Type

Property Validation

Disable CSV Remote Host Support

Enforce Content Security Policy

Transportation Management (Base)

Appointment Management

Appointments - Support Shipment Stops Requiring Multiple Appointments

Appointments - Location Appointment View Start Time - Hours and Minutes

Appointments - Set Stop Appointment Times Based on Stop Type

Appointments - Service Provider Cutoff Time by Location and Location Resource

Appointments - Tolerance Values for Appointments

Ocean Enhancement

Voyage Schedules - Internal or External Schedule Sources

Mobile

Mobile Application Enhancements

Document Management

Documents for Shipment Stop

Spot Bid Tender

Spot Bid Enhancements

Rate Maintenance

Rate Maintenance UI Refresh

Use Enhanced Rate Maintenance Links in Emails

Shipment Group

Enable Ship Group SC Rule Rule Type Validation

Shipment Group UI Web Action - Recalculate Secondary Charge Shipment

Secondary Charge Rule Shipment Group Criteria

Rate Service and Activity Time

Equipment Reference Unit Location Activity Time

Day Duration Rate Service Supports Same Day Pickup and Delivery

Asset Position and Status Report

Fleet Asset Position Report and Fleet Asset Status Report

Usability and Performance

Add Tracking Event to Shipments

Keep Existing Service Provider for Unassign

Allow Order Unassign When Rating Is Infeasible

Check Tender on Shipment Delete

External Distance Engines - Address Validation

Here Technologies - Address Validation - Quality Level

PC*MILER Web Service - Address Validation - Quality Level

Oracle Map Cloud Service - Address Validation - Quality Level

Property to Turnoff Postal Point Lookup

Here Technologies

Generate Rush Hour Data Using HERE Technologies Large Scale Matrix Routing v8 API - Asynchronous Call

HERE Technologies Map - Location Clustering

Here Technologies v8 Mandatory Upgrade

Mandatory HERE Routing API v8 Upgrade for Enhanced Workbench Mapping

Transportation Operational Planning

Logistics Guide Template - Equipment Reference Unit (ERU) for Planning Templates

Network Routing with Location Calendar

Use Consol Flag Added to Network Leg

Work Assignments

Convert Multi Segment Shipment to Single Petal Shipments

Resource Scheduler Sequencing Option - Current Start Time Ascending

Service Provider Assignment

Service Provider Assignment - Shipment Preference Criteria - Consider Utilization Options

3D

Gross Center of Gravity - Calculate and Persist on Shipment Equipment

Transportation Sourcing

Enhanced Build Lane Summary with Volume Target Action

Freight Payment, Billing, and Claims

Aggregated Shipment Cost Lines

Inv Line Appr-Stop At First Passed Det and Rule

Enable Improved Invoice Approval Logic

Shipment Cost Associated to Order Release and Stop

Transportation Intelligence

Data Visualization - Transportation Operational Intelligence Subject Area

Status Dimension Subject Area - Order Release, Shipment and Invoice

Order Release Dimensions for Earliest Estimated Pickup Date, Latest Estimated Delivery Date

Additional Shipment Dimension and Fact for Equipment Reference Units

Logistics Network Modeling

Extend Logistic Network Modeling to Include Work Assignment Optimization

Logistic Network Modeling - LTL Rate Discount Data Rule Enhancement

Logistic Digital Assistant

Logistics Digital Assistant Available in Global Header

Transportation Management

Transportation and Global Trade Platform

Enhanced Workbench

Improvements to the Enhanced Workbench

This feature provides a set of new capabilities and features for the Enhanced Workbench. Enhancements have been provided in many areas, including:

  • Layout Display - Compact, Super Compact
  • Add New records  
  • Session based column rearrangement
  • Session based column show/hide
  • New Menu Location 
  • Map Filters
  • Inline Edit for Flex Fields
  • Action Checks for Inline Edit and Mass Update
  • Bill Line Item Table Added
  • Dock Scheduling Gantt Actions - Block Resource, Create Appointment

Layout Display  - Compact, Super Compact

This enhancement reintroduces the Compact and Super Compact Layout Display options for your Enhanced Workbench.  To change the Layout Display setting for your existing Enhanced Workbenches  - you can edit the display and change the Layout Display to the desired setting - Compact or Super Compact. You also have the option of changing the display within a session - without saving the changes to your Enhanced Workbench.

Layout Display

Layout Display Options - Default, Compact Super Compact

Side by side comparison of the different options.  The Super Compact option provides visibility to about twice the number of rows of data when compared to the Default layout.

Side by Side Comparison - Default, Compact and Super Compact

NOTE:  Images (all images - check boxes, favorites, indicators, etc.) that are included in your screen set will take up more space than text since the images include some "padding"  - you can squeeze in more information by configuring your screen sets so they avoid including images.

Add New

The Enhanced Workbench now supports the ability for you to create New records within your Workbench tables.  The create New option will be available for any screen set where the Show checkbox for the Control New option is selected.  The ability to create new records directly from within the Enhanced Workbench expands your usage of the Enhanced Workbenches to support use cases that involve creating new records. 

The create New option is initiated by selecting the plus icon on the table menu.

Create New Plus Sign Icon

Screen Set for Create New - Show checkbox for the Control New option is selected

In the example below, the Enhanced Workbench has been created to review each Buy Shipment's Shipment Costs,  and - when missing - allow the user to add a new Accessorial Shipment Cost for Insurance. To accomplish this, the Enhanced Workbench has been created with four panes.

  1. The upper left pane has the Buy Shipments 

 NOTE: The Buy Shipment screen set used does allows for create New.

  1. The lower left pane provides the Shipment Cost and is associated with the Buy Shipments. 

NOTE: The associated Shipment Cost pane does not provide the option to create New.

  1. The upper right pane shows the Shipment Stops and is associated with the Buy Shipments - again, note that the associated Shipment Stop table does not provide the option to create New.
  1. The lower right pane, once again, is related to the Shipment Cost table - but in this pane the table is not associated with the Buy Shipment and the option to create New is available.

Create New Enhanced Workbench Example

To add a new shipment cost to a shipment - you would select the New   icon from the lower right Shipment Cost table view, this will - in this case - bring up a specifically configured Manager Layout for this task to enter the shipment Cost.  The configure manager layout is configured specifically for the task to be accomplished - so any unnecessary fields have been removed (or defaulted) and only the minimum input required is shown.

For this use case - the purpose of the workbench is to review the shipment cost and - where necessary, add a Shipment Cost record for an INSURANCE accessorial. 

Shipment 05037does not have the Insurance Accessorial as a current Shipment Cost.

Shipment Without Required Shipment Cost

To add the New shipment cost to this shipment - you would select the New option from the lower right Shipment Cost table.  Selecting New, in this example, brings up the Shipment Cost manager layout which has been configured specifically for the task to be accomplished i.e., adding the Insurance Accessorial Cost. 

NOTE: Unnecessary fields have been removed (or defaulted) and only the minimum input required is shown.

Create New Shipment Cost

To enter the Insurance Shipment Cost for the shipment  05037 - you would enter the shipment ID, Shipment Cost and hit Finished.

Enter Shipment Cost Info to Create New Shipment Cost Record

Once the Shipment Cost has been created, the Enhanced Workbench is refreshed, and the New Insurance Shipment Cost record is now shown.

Shipment Cost Create New

Column Rearrangement

The Enhanced Workbench now supports session based modifications to the columns displayed and the order in which the columns are displayed.  In the example below, the Shipment ID column is moved from 2nd column to the 4th.  You can perform the move column action by clicking the column header with the left mouse button - once the column is selected/highlighted - you can simply drag and drop the column to the desired position.

 

Select the Column to Move

Use the left mouse button to select the column to move - the column will be highlighted as shown below.

Select Column to Move

Drag the column the desired location.  A blue line provides an indication where the column will be dropped.

Drag the Column to Desired Location

Complete the drag and drop operation.

Column Moved to New Location

You can drag and drop multiple columns at once by doing a Ctrl_Click with the left mouse button to select more columns.

Multiple Columns Selected

Session Based Column Show/Hide 

The Enhanced Workbench allows you to change the View to show/hide a selected set of the available columns.  Use the action View->Columns and then select or de-select the column to show/hide.  You can reset the view to show all columns by selecting the Select All option.

View Column

 In the example below, the unchecked columns (e.g., Shipment ID, Service Provider ID, Status, etc.) have been hidden 

Columns Hidden

To reset the set of columns displayed, the Select All options is used.

Select All

New Menu Location

To improve the amount of workable screen real estate available for you to use with the Enhanced Workbench, several improvements have been made to the Menu operation and the Select Layout drop down.  The Select Layout drop down is now a Menu option - previously the Select Layout drop down consumed a dedicated row of screen real estate - that dedicated row is now available to display information in your Workbenches.  The Menu previously was either fully visible or hidden - now the Menu can be expanded or collapsed - with each option providing Menu information and access - improving usability and screen management.

Below is the default starting setup for the Enhanced Workbench.  Select Layout is now a Menu Option, Menu is expanded by default when opened in Workbench Designer mode, the Menu is collapsed when an Enhanced Workbench is opened from a Menu Link.

Enhanced Workbench New Menu Operation

Enhanced Workbench Open Via Menu Link Menu Collapsed

Select Layout is now one of the Menu options, when the Select Layout options is chosen the Drop Down for the available Workbenches is provided.

Select Layout

  The selected layout is displayed at the top of the Menu above the Select Layout option.

Selected Layout

The Edit Layout option now toggles between initiating the edit and completing the edit of the layout - previously completed by selecting Done.

Edit Layout Select to Initiate Edit Layout - Done Editing to Complete

Once the edit is initiated, the Edit Layout toggles to Done Editing - which - when selected - will save the edits.

Edit Layout - Done Editing

Map Filters

You now have the option to apply filtering within the map view - across all the supported map vendor options - Oracle Map Cloud Services, HERE, and ALK.  You will find this feature very useful in controlling the information displayed on the map.

Map Filter

In the example below, the map view has been filtered to show TL Transport Mode for shipments with between 4 and 5 stops.

Applied Map Filter

Inline Edit for Flex Fields

Support for Inline Edit for Flex Fields (aka Attribute fields) has been added to the Enhanced Workbench.  In the example below, the Power Unit Screen Set has been configured with three Flex Fields with edit enabled.  Two of the fields are text fields and one is a calendar field. The configured screen set can be used for Inline Editing of the Flex Fields within the Enhanced Workbench.

Inline Edit for Flex Fields

Select Save and the Flex Field Edits Are Saved

Result

Action Checks for Inline Edit and Mass Update

This enhancement provides Action Checks on Inline editing and Mass update. The Inline editing and Mass update Action check capabilities are in addition to the already provided Enhanced Workbench Action Check capabilities provided for Drag and Drop. Actions Menu on the Table ,Gantt, Map and Manager Layouts.

In the example below- an Action Check has been configured and assigned for the Location.  When the Action Check fails - as shown below, you will receive a message on the screen and the error will also be logged in the Layout Messages.

Inline Edit Action Check Error

Below is the Action Check Error message captured in the Layout Messages list.

Inline Edit Action Check Error Message Layout Messages

Action Checks are also considered with Mass Updates.  In the example below, the Action Check error has been trigged during a Mass Update.  Like the Inline edit use case the error is provided on the screen and in the Layout Messages.

Mass Update Action Check Error Message

Bill Line Item Table Added

The Bill Line Item Table was added as an available table to include in your Enhanced Workbenches.

Bill Line Item Table Added

Bill Line Item Table

Dock Scheduling Gantt

This feature provides two new Power Actions for the Enhanced Workbench Dock Scheduling Gantt - Block Slot and Create Appointment.

New Resource Actions

In the example below, the Block Resource Power Action will be used to block a time range of slots.  Previously this action was invoked by clicking on the slot to block - one slot at a time - the new improved action supports blocking multiple slots with one run of the Block Resource action.

Select Block Resource Action

The Block Resource action takes  - as input - a slot time range start and end - as shown below - the result of the block is shown in the Gantt when the action is run - in this case the slot from 6:00 AM to 7:30 AM are blocked..

Block Resource Action Input

The Create Appointment action works as it has in previous versions with the legacy Manage Appointment UI and allows you to create an appointment for a shipment that was not planned/managed inside of OTM.

Create Appointment

Create Appointment Manager

This feature provides additional features and usability improvements for the Enhanced Workbench - giving you more options for implementing Enhanced Workbenches to support more use cases and users.  

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

NOTE: The Enhanced Workbench relies on REST calls to access data, due to the current security infrastructure, the following additional setup is required.

  • For users with any role other than ADMIN and DEFAULT the following Access Controls are necessary and can be added to the User Role or directly to the User:
    • REST – Workbench
    • Workbench – Create
      • This is required only for Add/Delete
      • Can also revoke the ability to Add/Delete

Enhanced Workbench - Access Control Setup = Provide Access - Revoke Add/Delete

  • Additional Note:  User Interface - View is needed
    • This is included in COMMON
    • By default, all user roles typically have this COMMON Access Control

The legacy Workbench Designer has been hidden from the PUBLIC menus.  A first step toward the deprecation and removal of this older technology.

User Interface

Redwood UI Look and Feel Improvements

This feature provides you with a set of UI style improvements designed to align the system's look and feel with Oracle's Redwood UI look and feel.  You will find the consistent look and feel to be more comforting as you navigate between all of your Oracle Cloud applications.

To highlight the improvements, the images below provide a side by side comparison of the 22C UIs (on the left) and their improved Redwood altered versions provided in 23A (on the right).  The differences are nuanced, but will be appreciated by all users who spend many hours of their day working across multiple Oracle Cloud applications.

The Shipment Finder image below captures many of the changes, which include:

  1. Shading of the "white space" on the UI, which allows the input fields on the UI to standout
  2. Changing the tab label colors from blue to black
  3. A more reserved use of bold fonts for heading, field labels etc.
  4. A slightly smaller more pleasing font size, 

22C Shipment Finder Versus the 23A Redwood Shipment Finder

The 22C Shipment Finder Results versus the 23A Shipment Finder results, below, highlights the changes made around column shading.  The Redwood UI (on the right), has removed the shading in the column headings, providing you with a cleaner more modern look.

22C Shipment Finder Result Versus 23A Redwood Shipment Finder Result

Similar to the Finder - the Manager in the Edit view below highlights many of the same improvements noted for the Finder.

  1. Shading of the "white space" on the UI, allows the input fields on the UI to standout
  2. Change in tabs label colors from blue to black
  3. A more reserved use of bold fonts for heading, field labels etc.
  4. A slightly smaller more pleasing font size, 

22C Shipment Manager Edit v 23A Shipment Manager Edit

To complete the set - below is a comparison of the Shipment Manager View - 22C versus 23A.

Again - the View highlights the changes mentioned above. 

  1. Shading on the column headings for the Grids is now white - which provides a cleaner look.
  2. A more reserved use of bold fonts for heading, field labels etc.
  3. A slightly smaller more pleasing font size, 

22C Shipment Manager View Versus 23A Redwood Shipment Manager View

Finally - to complete the tour, below is an RIQ request with results.

22C RIQ Request Versus 23A RIQ Request

22C RIQ Results Versus 23A RIQ Results

Provides a consistent look and feel across Oracle Cloud applications.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

NOTE: There is a known issue where the Redwood Look and Feel does not get applied with custom themes.  While we work to remedy this issue, follow the steps below to correct the issue:

  1. Create a New Theme - DBA Access required - Configuration and Administration > Branding > Theme Management.

  2. On the Select Theme UI, enter a name for the your new theme in the Create Theme field and then select OK.

Create A New Theme

  1. In the Create Theme UI, select Save to save the new Theme, once you receive confirmation that the new theme has been created cancel out of the Create Theme UI.

Save the New Theme

  1. On the Select Theme UI, under Update Theme - select the newly created theme from the drop down and then select OK.

Update the New Theme

  1. Update/make changes to your newly created theme - you can change a setting and/or select Set as Global and then select Save.
  • It’s the Save during the Update step that will bring in the Redwood Look and Feel changes into the new theme.

Update/Change Theme and Save

  1. Once the Update Is Confirmed the Redwood look and feel should be available/applied to the new theme.

Update Confirmed

Data Export API

Data Export REST API

This feature provides you with the second set of features for the evolving Data Export REST API.  The Data Export REST API is designed to support the replication / export / extraction of table-oriented data from the system's database tables to external data repositories for the purposes of feeding analytical tools. This is a read-only service and all underlying tables will remain unchanged after the process. The export will happen in real time and the expectation is that the data to be exported should be reasonably static e.g., completed orders or shipments.

Provides another option for extracting data from the system to feed external data repositories. 

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Note that this version of the Data Replication Service - REST Data API does not handle the processing of deletes or updates for replicated data.

Key Resources

For complete coverage of the available capabilities and recommended usage of the current version of the REST Data API the API documentation listed below, on docs.oracle.com, is the best source of information:

  • Transportation and Global Trade Management Data Export Rest API Documentation
  • Transportation and Global Trade Management Business Object Resource Rest API Documentation

Document Management

Document Set Capabilities Added for Additional Objects

This feature extends the availability of the Document Sets functionality to the objects listed below.  All objects listed have been extended to include the availability of the Assign and View Document Set web actions.  The Send Document Sets agent actions has been added for the  Order Releases, Shipment Stop, Shipment Groups, Invoices and  Bills - as noted below.

  •  Order Releases
    • Assign and View Document Set web actions added
    • Send Document Sets agent action added
  • Shipment Stop
    • Assign and View Document Set web actions added
    • Send Document Sets agent action added
  • Shipment Groups
    • Assign and View Document Set web actions added
    • Send Document Sets agent action added
  • Invoices
    • Assign and View Document Set web actions added
    • Send Document Sets agent action added
  • Bills
    • Assign and View Document Set web actions added
    • Send Document Sets agent action added
  • Items 
    • Assign and View Document Set web actions added
  • Item Qualification 
    • Assign and View Document Set web actions added
  • Campaigns
    • Assign and View Document Set web actions added
  • Campaign Lines
    • Assign and View Document Set web actions added

Order Releases

Order Release - Assign and View Document Sets Actions

Order Release - Send Document Sets Agent Action

Shipment Stop

Assign Document Sets and View Document Sets was added to the Shipment Stop as part of the larger feature to add and manage documents at the Shipment Stop level.

Shipment Stop - Assign and View Document Sets Actions

Shipment Stop - Send Document Sets Agent Actions

Shipment Groups

Shipment Group - Assign and View Document Sets Actions

Shipment Group- Send Document Sets Agent Actions

Invoices

Invoices - Assign and View Document Sets Actions

Invoice - Send Document Sets Agent Actions

Bills

Bill- Assign and View Document Sets Actions

Bill - Send Document Sets Agent Actions

Items 

Item - Assign and View Document Sets Actions

Item Qualification 

Item Qualification - Assign and View Document Sets Actions

Campaigns

Campaigns - Assign and View Document Sets Actions

Campaign Lines 

Campaign Lines - Assign and View Document Sets Actions

The addition of the Assign and View Document Set actions to additional objects simplifies the process of assigning and viewing sets of documents related to these objects.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The Send Documents - Send Documents/Document Sets action/functionality was not included in the set of actions added for the six objects included in this feature. 

Performance and Stability

Online Help Centralized on docs.oracle.com

This feature provides you with a new centralized location (docs.oracle.com) for the system's online Help.  In previous versions, online Help was distributed with each installation - now, by default, all instances will access a single centralized online Help version.  The switch to the new centralized online Help should be transparent to you and your users.

With this feature - Help can be updated universally for all clients on a given release, the Help is searchable on the Oracle Help Center, and Oracle can  now collect metrics on what is read in online Help to identify and improve high traffic areas.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

If for some reason there is a need to revert back to the local vs centralized online Help, the property - glog.webserver.onlinehelp.enabled - can be set to false (the property by default is set to true) - when this property is set to false the help links will open using the local files that were installed along with the application.

Limit CSV Export File Size

This Optional  Feature, when enabled, enforces a 512 MB CSV export file size limit.  The 512 MB limit is being provided to avoid single file CSV file exports that could lead to a system failure by filling up available disk space.  If you are running the export on the browser, and the file size exceeds the 512 MB limit, the error message will be raised on the screen, the export will complete with the amount of exported data being roughly equivalent to the export file size limit.  If the export is not run in the browser, you will find limit error in the exception log.

This feature is designed to avoid system failures related to the filling of available disk space with an excessively large single CSV file export. 

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

NOTE: If you need to do a CSV file export larger than 512 MB: 

  • Until this Optional Feature is promoted - you can OPT Out of the feature and still export larger files than 512 MB.

  • After this feature is promoted - you can raise a CR to request to increase the export limit. 

Raise Status Change Events in New Process

This Optional Feature will raise status change events independently from the process triggering them, this change will help avoid contention issues with synchronous user actions and will improve performance.

NOTE: In 24A this Optional Feature was removed and replaced with the Optional Feature - PROPAGATE LOCKS TO TASK LISTS.  Your OPT IN setting for the replaced Optional Feature RAISE STATUS CHANGE EVENTS IN NEW PROCESS were migrated to the new Optional Feature - PROPAGATE LOCKS TO TASK LISTS.

This feature provides the opportunity for improved performance by raising the status change event independently from the process triggering them.

Steps to Enable

You don't need to do anything to enable this feature.

Use Fallback Locale for Missing Translations

This Optional Feature, when enabled, uses a predefined fallback for translation bundles when a language is provided that has no default translations but requires a country specification, e.g., Portuguese.

This feature improves system resiliency.

Steps to Enable

You don't need to do anything to enable this feature.

Filter Agent Events Based on Data Query Type

This Optional Feature, when enabled, will filter agent events based on the data query type. When the Optional Feature is disabled, it will display agent events up to 1000 events.

Limits agents events based on the data query type - reducing the agents events listed.

Steps to Enable

You don't need to do anything to enable this feature.

Property Validation

This Optional Feature - when enabled -  validates property entry.  Based on strongly-typed property metadata, property values are checked for Boolean, numeric, list or other constraints.

This feature improves the usability and reliability of the system by validating property values.

Steps to Enable

You don't need to do anything to enable this feature.

Disable CSV Remote Host Support

This Optional Feature removes support for the import and export of CSV data to remote hosts. Support for the import and export of CSV data directly to remote host URLs is no longer available.

This feature simplifies the usage of the system by removing features that are no longer available.

Steps to Enable

You don't need to do anything to enable this feature.

Enforce Content Security Policy

This Optional Feature, when enabled, will stop a page from rendering whenever something in the page content violates a rule. When the feature is Opted Out, instead of the page not rendering, a message will be written to the browser’s console log.

This feature improves the security and resilience of the system.

Steps to Enable

You don't need to do anything to enable this feature.

Transportation Management (Base)

Appointment Management

Appointments - Support Shipment Stops Requiring Multiple Appointments

This feature enhances the Dock Scheduling functionality providing you with a new action - Schedule Partial Stop Appointment.  The Schedule Partial Stop Appointment action supports the scheduling of partial/multiple appointments at a shipment stop  where the appointments being scheduled are to accommodate the loading or unloading of multiple shipment equipments, or to schedule the loading/unloading of multiple commodities - for example, the loading/unloading of refrigerated and frozen commodities that require appointments be arranged for different doors.

The Schedule Partial Stop Appointment action is available as both a Shipment Action and a Shipment Stop Action. 

  • Shipment Management > Shipment Management > Buy Shipments > Actions > Operational Planning > Dock Scheduling > Schedule Partial Stop Appointment
  • Shipment Management > Shipment Management > Sell Shipments > Actions > Operational Planning > Dock Scheduling > Schedule Partial Stop Appointment
  • Shipment Management > Shipment Management > Shipment Stops > Actions > Operational Planning > Dock Scheduling > Schedule Partial Stop Appointment

The examples below will demonstrate the usage of the Schedule Partial Appointment action for a shipment equipment (s_equipment) centric stop appointment making use case and a commodity partial stop appointment use case.  In both examples, the Schedule Partial Stop Appointment is being run as a Buy Shipment action.

Schedule Partial Stop Appointment - Multiple Shipment Equipment

In the example below, the shipment  has three shipment equipments assigned.  The Schedule Partial Stop Appointment action will be used to assign pickup appointments for each of shipment equipments on the shipment and picking at the Atlanta DC.

To initiate the process, select the shipment and run the action Schedule Partial Stop Appointment.

Schedule Partial Stop Appointment - Buy Shipment Action

When the Schedule Partial Stop Appointment action is run, the schedule appointment input screen is displayed.  Note, in addition to Stop Location selection, the action input screen (below) also supports selecting and creating appointments for either the shipment equipment level or commodity level.

Schedule Partial Stop Appointment Action Input Screen

For this example, the goal is to create appointments for the three shipment equipments on the shipment.  There are two options for scheduling the appointments - Schedule - which allows the system to automatically find the appointment slot or Show Options - which shows and allows you to select the appointment slot.

Collapsed View Shipment Equipment

Show Options for the First Shipment Equipment

When Show Options is run, the application provides the available appointment slots to select from.  In this example, the 10:00 AM to 11:00 AM slot is selected, and the selection is Saved.  

Show Options - Option Selected

Once the selected option is saved, a confirmation screen is provided. The confirmation screen provides the option to view the schedule board to review the appointment.

Confirmation Screen

Selecting the Go to Schedule Board option brings up the classic Schedule Board below, the partial appointment for the first shipment equipment is highlighted on the board - 10:00 AM to 11:00 AM slot Door 3.

Schedule Board - Slot Assigned

Running the Schedule Partial Stop Appointment Action a second time, to schedule the appointment for the second shipment equipment, provides the Input Screen below, note that the first shipment equipments appointment is now scheduled and the details of the appointment are provided.

Schedule Partial Stop Appointment Action Input Screen - Subsequent Run

For scheduling the appointment for the second shipment equipment, the Schedule option will be used to schedule the appointment.

Schedule for the Second Shipment Equipment

The Schedule option will bring up the classic Schedule Board with the appointment scheduled. In this case, the second appointment for the second shipment equipment is scheduled for the 9:00 AM to 10:00 AM slot Door 4.

Schedule Board - Slot Assigned

As shown below, two of the three shipment equipments have scheduled appointments.

Two Partial Shipment Equipment Appointments Created

Running the Schedule Partial Stop Appointment Action on the third shipment equipment completes the partial stop appointment process for this stop.  The final set of schedule appointments are below.

Partial Appointments Complete

The same three partial appointments from above, shown on the classic Schedule Board below.

Three Partial Appointments Complete

Schedule Partial Stop Appointment - Multiple Commodities

In the shipment below, there are 9 Commodity Groups to be scheduled.  The partial appointment setting process for commodities is similar to the shipment equipment example above. 

In the example below, the Schedule Partial Stop Appointment has been run against the shipment.  The first Commodity ID (70.0) - is selected and the Schedule option is run for scheduling the partial appointment.

First Commodity ID Selected - Schedule Selected

As was the case before, when the Schedule option is run, the result is shown in the classic Schedule Board.  In this example, the Commodity ID (70.0) is assigned to the 9:00 AM to 10:00 AM Door 2 slot.

Schedule Board Slot Assigned

On the subsequent run of the Schedule Partial Stop Appointment to schedule the appointment for the next Commodity ID, the first scheduled appointment for the first commodity scheduled is show.

Schedule Partial Stop Appointment Action Input Screen - Subsequent Run

For the second Commodity ID (92.5), Show Options is selected for assigning the appointment. 

Schedule Partial Stop Appointment - Show Options

For the Commodity ID 92.5, the option below 10:00 AM to 11:00 AM is selected and saved.

Show Options Selection

In this example, the Commodity ID 92.5 is assigned to the 9:00 AM to 10:00 AM Door 2 slot.  

Schedule Board Slot Assigned

Below is the result after all the Partial Stop Appointments have been arranged for all nine of the Commodity IDs on the shipment.

Schedule Board Slots Assigned

Schedule Partial Stop Appointment - Slots Assigned

Shipment Action - Manage Appointments

The new Shipment Action  - Manage Appointments - Buy Shipment> Actions > Dock Scheduling > Manage Appointments - will open the PUBLIC Dock Scheduling enhanced workbench layout for the shipments selected. From within Dock Scheduling Enhanced Workbench you can manually adjust the appointments.

Shipment Action - Manage Appointments

This feature greatly expands the system's Dock Scheduling capabilities to support use cases where a single stop (pickup or delivery) requires that multiple appointments be arranged to accommodate the loading or unloading activities for different commodities (e.g., frozen and refrigerated) or to handle the loading unloading of multiple pieces of equipment.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Note that the activity time at the stop represents the calculated activity time based on the fixed and variable activity time setups - with partial appointments it is now possible to have the Appointment Stop Duration time exceed the time calculated as the stop Activity Time.

Stop Activity Time, Appointment Stop Duration 

NOTE: Only one equipment or commodity can be selected when running this action. Multiple commodities, even if belonging to same commodity group, cannot be scheduled together.

Selected Multiple

If a partial appointment exists for a stop, you can not run the action Schedule Appointment, the existing partial appointment must be removed before running this action.

Stop Appointment Already Assigned

If you have already run the Schedule Appointment action for a stop, you cannot assign appointments using the Schedule Partial Stop Appointment action for the same stop.

Schedule Appointment Already Run

Actions and default Appointment Gantt used.  As we migrate from the classic Scheduling Gantt to the new Enhanced Workbench and Dock Gantt. you will notice that some actions link to the classic displays.

Appointments - Location Appointment View Start Time - Hours and Minutes

This feature allows you to set your Location Appointment View Start Time to both Hours and Minutes.  Previously the Location Appointment View Start Time could only be set in one hour increments.

In the example below the Location Appointment View Start Time has been set to start at 7:15 AM.

Location Appointment Start Time Set to 7:15

Dock Scheduling Grid Appointment View Start Time 7:15

This feature provides improved usability and configurability for setting your Appointment Start Time View.

Steps to Enable

You don't need to do anything to enable this feature.

Appointments - Set Stop Appointment Times Based on Stop Type

The Optional Feature - Set Stop Appointment Times Based On Stop Type - when enabled - will assign your shipment stop appointment times to the proper Appointment Time fields based on the Stop Type (Pickup or Delivery) for the appointment being scheduled. 

The Optional Feature Set Stop Appointment Times Based On Stop Type works in conjunction with the previously available property - glog.appointment.shipmentstop.updateAppointmentTime (which is on/true by default) to properly populate your Appointment Stop Time values on your Shipment Stops.

When you enable the Set Stop Appointment Times Based On Stop Type optional feature and with the property - glog.appointment.shipmentstop.updateAppointmentTime set to true - the following fields will be populated on your stops when setting appointments.

For a pickup appointment, the Pick Appointment field will be populated.

Pickup Appointment Example

For a delivery appointment, the Delivery Appointment field will be populated. 

Delivery Appointment Example

This feature provides a more intuitive mapping of the assigned appointment times to the shipment stop appointment fields.

Steps to Enable

To take advantage of this feature, you will want to enable (Opt In) to the Optional Feature Set Stop Appointment Times Based On Stop Type

The Optional Features UI is accessed via Configuration and Administration > Property Management > Optional Features - Note: Only the DBA.ADMIN user can access and use the Optional Features page.  To Opt In to this feature, select the feature and then run the action Opt In.

The Optional Feature Set Stop Appointment Times Based On Stop Type requires that the property glog.appointment.shipmentstop.updateAppointmentTime to be set to true - which is the default value. 

Tips And Considerations

An example of the previous appointment field mapping, the mapping that will be seen when this feature is not enabled - is provided below.

For a Pickup Appointment, the Pick Appointment and Delivery Appointment fields were used to capture the Appointment Start and End times.

Previous Behavior Pickup Appointment

Similarly, for a Delivery Appointment, the Pick Appointment and Delivery Appointment fields where used to capture the Delivery Appointment Start and End times.

Previous Behavior Delivery Appointment

Appointments - Service Provider Cutoff Time by Location and Location Resource

This feature provides you with the ability to setup your Service Provider dock scheduling appointment cutoff requirements at the location and location resource group level.  This new capability is in addition to the previously available option which allowed you to set the Service Provider cutoff values at the system level using a set of properties.

To configure the Service Provider cutoff at the location level, three new fields have been added to the location to allow for this configuration.  Note that you must configure all three fields to properly setup the feature.

Location Service Provider Cutoff Time Setup

  • Service Provider Cutoff Hours - The selected option from the drop-down list indicates the appointment cutoff time allowed for the service providers at the location.
  • Service Provider Appointment Days Before Cutoff - provides the duration allowed before the appointment cutoff time for the service providers.
  • Service Provider Appointment Days After Cutoff - provides the duration allowed after appointment cutoff time for the service providers.

To manage the Cutoff at the location resource group level, the Service Provider Cutoff fields available at the location level are now also available on the Appointment Rule Set.  Once configured, the Appointment Rule Set assigned to the Location Resources Group will be used as the Service Provider Cutoff for the Location Resource Group.

Appointment Rule Set

This feature provides more control for setting your Service Provider cutoff requirements at a location level to support situations where a global one-size-fits-all property setup cannot support your variety of location specific cut off requirements.

Steps to Enable

To take advantage of managing the Service Provider Cutoff values at the location or location or location resource level the newly added fields must be configured.

Tips And Considerations

The Cutoff values set on the location level, if present, will override the property values. Values set on the resource level via Appointment Rule Set takes precedence over Location, Location takes precedence over the property.

The existing properties and defaults:

  • glog.appointment.enforceServprovRule=false
  • glog.appointment.servprovRule.cutOffHour=16
  • glog.appointment.servprovRule.numberOfDaysBeforeCutOffHour=1
  • glog.appointment.servprovRule.numberOfDaysAfterCutOffHour=2

Appointments - Tolerance Values for Appointments

This feature provides you with a new property - glog.appointment.showOptions.applyToleranceLimit - that allows you to define a tolerance value (in minutes) that will extend the list of feasible Appointment Options available.   With the property configured, the list of feasible Appointment Options will include Appointment Options that start before (based on the tolerance value) the shipment stop's arrival time.

In the example below, the shipment pickup stop for the Miami location has an pickup arrival time of 10:10 America/New_York.  Without the new tolerance property defined, the first available Appointment Option is the 11:00 America/New_York option.  With the new property - glog.appointment.showOptions.applyToleranceLimit - configured with a value of 15 minutes, the list of Appointment Options is extended to include the 10:00 America/New_York Appointment Option.

Shipment Stop Arrival Time

With the Stop Arrival Time of 10:10  - and without the appointment tolerance property value set, the available Appointment Options starts with the 11:00 option as shown below.

Run Schedule Appointment from Dock Scheduling Workbench

Without any tolerance set, the first Appointment Option is for the 11:00 slot.

Appointment Options Without Tolerance Property Set

With the property set, the Appointment Option includes the 10:00 American/New_York slot.

Property Set with Tolerance of 15 Minutes

Appointment Options provide with property setup as defined above.

Appointment Options with Tolerance Property Set to 15 Minutes

This feature will help eliminate missed appointment slots that were available, but not considered based on strict consideration of the shipment stop estimated arrival time.

Steps to Enable

To take advantage of this feature you will need to set a tolerance value (in minutes) for the property - glog.appointment.showOptions.applyToleranceLimit. Navigate to Configuration and Administration > Property Management > Property Sets.

NOTE: Only the DBA.ADMIN user can access and use the Property Sets page.

Ocean Enhancement

Voyage Schedules - Internal or External Schedule Sources

This feature provides the first set of capabilities for the integration of OTM with external voyage schedule providers. 

For this release, the following capabilities have been provided:

  • The option to license and use external voyage schedules with OTM.  For 23A, the ability to connect to project44's Container Sailing Schedules has been provided. (see Steps To Enable for more info)
  • A new Ask Oracle Voyage Schedules option, which provides an improved look and feel and filtering capabilities has been provided.  The new Ask Oracle Voyage Schedules can be configured for external or internal voyage schedule queries. 
    A new Order Release action - Assign Voyage Schedules - which allows you to lookup and assign external voyage schedules from external sources (project44) or this new action can be used to assign voyage information to the order release for voyage schedules loaded into OTM

Ask Oracle Voyage Schedules

The new Ask Oracle About Voyage Schedules is available via Ask Oracle > Voyage Schedules (shown below), you can also follow the navigation path of Operational Planning > Ask Oracle > Voyage Schedules.

Ask Oracle About Voyage Schedules

You will notice (below) that the Ask Voyage Schedules UIs have a slightly different look and feel.  Specifically, the icons provided for Search, View, Calendar etc. have been improved, and the Required fields are now indicated as required with the word Required below the field versus the legacy asterisk "*".

Ask Oracle About Voyage Schedules

The request input screen operates much like the other screens/other Ask Oracle screens.  The one slightly different component on the UI is the Arrive/Departure Date field.  This Date and Time component handles the setting of the date and time differently from other Date fields you are familiar with.  By default, the new date/time component sets the time to a default time of 12:00 AM.  In the scenario where you are looking to just select the date, the new component will, by default, set the time to the component default time versus the current time which is standard behavior in other areas of the application.  If you wish to set the time along with selecting the date, then you can do that by either setting the time using the control provided (example below) or by selecting the date with the default time and then updating the time after the date has been set.

For example, to select the Arrive/Departure Date of November 29th - the current day/date in this case - the calendar highlights the current date and you select Done to assign 11/29 as the date.  The time is set by default to 12:00 AM as the Arrive/Departure Date time value.

Input Date with Default Time

Below is the result of selecting the date and not specifying a time.

Date with Default Time

If you wish to change/set the time and date, you can change the time set by selecting the time icon (highlighted below) and then using the dial control to set a new time.

Set Time

The dial control below allows you to easily set a different/new time.  Once you have the time you want, select done and the date and time will be set.

Set New Time

Below is the result when specifying the date and a time.

Set Date and Time

Voyage Schedule Request

Given the query above, The new Ask Voyage Schedules results UI (below) provides a number of improvements.  The Number of Schedules is provided (in this example 288), you can filter the results by Connections (Direct or Transshipment) and by Service Provider, and you can sort the response data directly in the column header(s).  The results shown below are provided via an external voyage source - in this case project44. 

Ask Oracle About Voyage Schedules Results

In the example below, the results have been filtered to only showing Transshipment voyage schedules.

Filter by Connection - Transshipment

In the example below the results have been filtered by Connections - Direct and by two Service Providers - HLCU and APLU.

Multiple Filters

Order Release action - Assign Voyage Schedules

This feature also includes the addition of a new Order Release action - Assign Voyage Schedules which allows you to lookup and assign voyages to your Order Release.  Based on your setup, the action can be used to assign either external vessel schedules or internal vessel schedules - see the Steps to Enable section for more info.

In the example below, the Order Release is has the Port of Load of INNAS and the Port of Discharge as USNYC. 

Order Release Assign Voyage Schedules - POL/POD

When the Assign Voyage Schedules action is run for the order above, the Voyage Schedules options below are provided.  Again, these are from the external voyage source  - project44.

 

Assign Voyage Schedules Options

In this example, you want to select only Direct Connections for the Service Provider MSCU (Mediterranean Shipping Company), to do this you filter for those options.  In this example, the November 30th voyage is selected. 

Filter and Select Direct and MSCU Voyage Option

With the selection above, when you select Finish, the assignment to the Order Release is made.

Assignment of Selected Voyage

Below is the Order Release with the Assigned Voyage.  As part of the Voyage Assignment processing, the direct port to port section of the related voyage rotation for this voyage will be saved to OTM Voyage Schedule table - so the port of load and port of discharge portion of the external voyage schedule will be persisted in OTM which will allow for the assigned voyage schedule to be use in planning.

Order Release with Assigned Voyage Schedule

Below is the information stored in the Voyage table for the Voyage ID assigned to the Order Release above - MSCU_IV247A. 

Voyage Information Persisted As Part of Order Release Voyage Assignment from External Voyage Source

Assign Voyage Schedule - Internal Voyage Schedules

In the example below, the Assign Voyage Schedule is run using internally stored voyage schedules versus externally provided voyage schedules.  The functionality is the same - but the setup is different/simpler.

Assign Voyage Schedule - Internally Stored Voyage Data

Provides access to the most current voyage data from an external voyage source (project44's Container Sailing Schedules) and avoids the need to load voyage data into OTM.

Steps to Enable

The new functionality can be used for both internally stored and externally stored voyage schedules. 

To use the new functionality with and external voyage schedule provider - currently limited to project44, the following configurations are required.

You will need to subscribe to the project44 Container Sailing Schedules service.

To get the voyage schedule from the project44, you need to create an external system in the External System screen. To create an external system and connect to the project44,  define an external system with the following details:

  1. Content Type: Provide the content type as "application/vnd.oracle.resource+json; type=otm"
  2. URL: In the For HTTP/HTTPS section, provide the URL as "https://capi2.ocean-insights.com/sailingschedules/v2/"
  3. HTTP Header Profile ID: You need to define the Parameter Name and Parameter Value. Contact a customer service representative to get them.
  4. HTTP Method: Provide the HTTP method as Post.

External System Setup Example

Setup the required Rate Service for the Rate Service Type of External Voyage Schedule.  For this Rate Service  - you will select the Rate Service Type of EXTERNALVOYAGESCHEDULE, then select P44 from the External Voyage Engine Type - P44 (project44) is the only option supported currently. You will also want to link this Rate Service to the External System configured above to call out to P44 (project44). The Rate Service defined here ties together the external system configured above, the Voyage Parameter to enable using the External Voyage Schedule provider - explained below - and the Service Type(s) which link to the Service Provider and the various Rates provided for different Service Types.

 

External Voyage Schedule P44 Rate Service Setup Example

Service Type for Rate Service

Once the External System and Rate Service have been configured - the last step is to assign the external voyage Rate Service configured above to the new Voyage Schedule Parameter - DEFAULT VOYAGE RATE SERVICE ID DEFAULT, as shown below.  The Voyage Schedule section is a new Parameter section added for this feature.   By default the Assigned rate service supports looking up voyages for internal voyages.  The example below shows the setup for using the configuration above for looking up voyages from an external source. 

Set Voyage Planning Parameter

There is more information available in help regarding the additional parameters provided - for completeness a brief description of each parameter is provided below.

  • VOYAGE BEFORE ARRIVAL OR AFTER DEPARTURE
    • This parameter is used to decide whether to search the voyage schedules before arrival or after departure from a specific date.
  • VOYAGE EXTERNAL ALL ROUTES
    • This parameter indicates whether all or only the best voyages should be requested. By default, the parameter value is set to false and the application will fetch the best voyages. If you set the parameter value to true, the application will fetch all voyages.
  • VOYAGE LOOKUP NUM OF WEEKS
    • In the case of the parameter "VOYAGE BEFORE ARRIVAL OR AFTER DEPARTURE" is "After departure", this parameter is used to define how many weeks to look ahead from the mentioned date, when it is "Before Arrival" how many weeks to look backward from the mentioned date.

Once all of the above has been configure, the last step is to make sure that the Parameter Set configured above is set as your Domain Default parameter set. 

Domain Default

Internally Stored Voyage Schedules Setup

If you wish to use both the new Ask Oracle Voyage Schedules option and the new Order Release action - Assign Voyage Schedules - with internally stored voyage schedules - the only changes you will need to make is to provide the following access control additions for the user(s) who wish to take advantage of the new functionality.

  • REST - Location - View
  • REST - Order - Update
  • REST - Order - View
  • REST - Service Provider - View
  • REST - Voyage Configuration - Update
  • REST - Voyage Configuration - View
  • REST - Voyage - Update
  • REST - Voyage - View

Tips And Considerations

The new functionality provided with this feature does not provide the option for OTM's planning logic to call out to an external voyage schedule source directly.  For now, planning with external voyage schedules requires that the schedules be assigned to the Order Releases using the Assign Voyage Schedule action first before being planned.

NOTE: If the proper access control permissions are not provided for the user attempting to use the Order Release Assign Voyage Schedule action for internally stored voyage data, the action will return the error below.

Error Assign Voyage Schedule

Mobile

Mobile Application Enhancements

This feature provides a long list of new features and improvements to the Mobile App.  The highlights include the following enhancements:

  • Service Provider Flow - Shipment Tender (Accept/Decline), Spot Bid Tender (Enter bid amount) and Tracking Event entry
  • Mobile Help
  • New Offline indicator
  • Support for Image Compression
  • Update Received Quantity
  • Shipment Filter 
  • Ability to View Shipment Documents on Mobile App
  • Show Shipment Contact Information

Service Provider Mobile Layout and Flow

The Service Provider Mobile Layout - supports your Service Provider Mobile use cases for Ordinary Shipment Tender (Accept/Decline), Spot Bid Tender (Bid entry) and Tracking Event entry - including prompted event entry for stop arrival/departure events.

As with the Driver Flow - released previously, the Service Provider Layout and Flow is defined by the Mobile Layout assigned to the Service Provider's User Preference.  The example below uses the default Service Provider Mobile Layout (SERVPROV_MOBILE_LAYOUT) to demonstrate the new capabilities.  You have the option to configure your own Mobile Layout and assign that configured Mobile Layout to your Service Provider's User Preference to support modifications like changing colors, adding/removing information displayed (for example, remove cost information) or to change the options provided to the user - like removing the option to review Spot Bid Tenders.

After logging into the Mobile Application, the Service Provide will see the multiple panel screen below.  The Service Provider Mobile Layout screen supports both the Ordinary Tender process and Spot Bid Tender process.  

Service Provider Mobile Layout

 For the Ordinary Tender flow, the Service Provider will start the process by reviewing and accepting or declining the shipment(s) shown in the Tendered Shipment box.  In this example, there are 6 tendered shipments for this Service Provider.  In the series of sides below the Service Provider  - selects the Tender Shipments box - then for the list of tendered shipments shown the Service Provider can drill in for more detail or they can just select Accept or Decline for the shipments in the list.  The Accepted shipments will then move to the Accepted Shipments box.

Tendered Shipments Accept

After the shipment(s) have been accepted, the next step to complete, is for the Service Provider to select and "Start" the accepted shipment(s).

Start Accepted Shipment

Once the Service provider has started the shipment(s), the shipments are then moved into the Active Shipments box.  The Active Shipments are the shipments that the Service Provider will provide tracking events for - including prompted events for stop arrival/departure, including additional details like document uploads, signatures, and an update for received quantities.  In the series below, the Service Provider Mobile User is entering the prompted stop arrival event.  Note that the list of twenty five active shipments was filtered down to one shipment (01028) using the filter.

Active Shipments - Filter and Add Stop Arrived Tracking Event

After entering the arrival event, the next logical event - Departed - (departing from the stop) -  is highlighted to prompt the Service Provider to enter this event when ready.

Arrived Entered - Promoting for Departed

Below is the Add Event screen configured with Capture Received Quantity Enabled.

Capture Received Quantity

Highlighted below are the steps to Add Documents or Add Signature.  

Add Signature and Upload Documents

The Spot Bid Tender process is supported by the Open Spot Bids and Submitted Bids boxes.  Your Service Providers will review Spot Bid Tenders in the Open Spot Bid box and either Bid or Decline. 

Spot Bid - Bid or Decline

If the Service Provide decides to Bid, then the Bid Entry screen below is provided.  The screen shows the Last Bid, and allows for the Service Provider to Submit a New Bid - which is validated against the allowed threshold range which is shown below the New Bid entry field.

Open Spot Bids - Enter New Bid

The Submitted Bids box allows the the Service Provider to quickly check on the status of the Shipments they have Submitted Bids against.

Submitted Bids - Bid Status

Mobile Documentation

This release provides you with complete Help documentation for the Mobile Application, topics cover both the usage and configuration options available with the Mobile App.

Mobile App Help Available

Offline Indicator Improvements

Additional visibility is now provided to you when the Mobile App is running in offline mode.  Now, when the Mobile App is offline - an offline Icon is displayed in the header and a banner message is also displayed.  The banner message can be closed by hitting the "X" the offline Icon will be displayed until the Mobile App is back online.

Offline Banner and Icon

 Allow Image Compression

The Mobile Layout now supports configuration options for image compression.  To configure image compression in the Mobile Layout:

  • Set allowImageCompression: true -  When set to true this will invoke the logic to evaluate your uploaded images and consider them for compression, when set to false your images will not be considered for compression.
  • Set minimumImageSizeForCompression: When allowImageCompress is set to true, then the minimumImageSizeForCompression value (in MegaBytes) is used as both the threshold to consider for compression and it is also used as the compression target.
    • For example - the setting "minimumImageSizeForCompression": 1, will set a compression threshold of 1MB and, if an image is uploaded greater than 1MB, the compression ratio will be set so that 1MB is used as the target for compressing the file. The minimumImageSizeForCompression does support decimals so "1" and "1.5" are both supported values. 

Allow Image Compression

Add Event  - Capture Received Quantity 

The Mobile Layout now supports the configuration option to include capturing Received Quantities as part of the Add Event process.  To configure the Received Quantities:

  • Set captureReceivedQuantityEnabled: true -  When set to true, the Mobile App will support the entry of one or more of the Ship Unit Received Quantities depending on what quantity options you select - Count, Weight, Volume.
  • Set captureReceivedShipUnit: true -  When set to true, the Mobile App will support the entry of the tracking event ship unit count.
  • Set captureReceivedWeight: true -  When set to true, the Mobile App will support the entry of the tracking event ship unit weight.
  • Set captureReceivedVolume: true -  When set to true, the Mobile App will support the entry of the tracking event ship unit volume.
  • Set sShipUnitRefnumQualGid: to select a Shipment Reference Number Qualifier to identify the Ship Unit versus the default Ship Unit ID.  In the example below, the Shipment Ship Unit Reference Number Qualifier is set to "OOTB.AAA" .

Shipment Ship Unit Reference Number Qualifier GID Set

The default Mobile Layout assumes the Shipment Ship Unit ID as the reference id - in the example below, the Reference Number Qualifier setup will be used.

Shipment Ship Unit ID vs Reference Number Qualifier GID

Below is the Add Event screen configured with Capture Received Quantity Enabled set to true.

Capture Received Quantity Enabled

The Ship Unit Received Quantities input screen is below.  Shipment Ship Unit Count, Weight and Volume are configured for input in this example.

Capture Received Quantity Input

Below is the information provided after the Received Quantity information has been entered and saved.

Received Quantity Information

The event entry above, once submitted, will map into the Tracking Event as shown below.

Ship Unit Received Quantity Tracking Event

Shipment Filter

A Shipment Filter has been provided allowing you to easily filter the list of shipments shown on the screen based on the filter value entered.  The value entered will filter the shipments based on matching the Filter value entered to the fields shown for the shipment.  In the example below, the value "01028" is used to filter the list of shipments shown to just one shipment.

          

Shipment Filter                                                                                        Filtered View

Ability to View Shipment Documents on Mobile App

From within the Mobile App, you can now view the documents attached to a shipment.  

Shipment Documents OTM Shipment Manager View

Shipment Documents - Mobile View

Show Shipment Contact Information

The Mobile Layout supports the ability to display a selected Shipment Contact.  The selection of the qualifier to use as the Shipment Contact is handled in the Mobile Layout.  By default it is set to LOGISTICS as shown below..

Mobile Layout Shipment Contact Setup

This feature extends the flows supported by the application to include the third party carrier use case - as well as providing many usability improvements that will benefit all users of the application.

Steps to Enable

You don't need to do anything to enable this feature.

Document Management

Documents for Shipment Stop

This feature extends OTM's Document Management capabilities to the Shipment Stop level.  Document Management web actions supported for the Shipment Stop include Add Document, Assign Document Sets, Upload Document and View Document Sets.  In addition, to automate Shipment Stop document processing - Agent Actions for Add Document To, Add Document From and Send Document Sets have been added.

Document Actions Supported on Shipment Stop

In the example below, the Add>New Document action was used to upload a shipment stop specific document to delivery stop.

Add > New Document Shipment Stop

You also have the option to view documents for a shipment stop via the SmartLink as shown below.

Shipment Stop Document SmartLink

In this example, the pickup stop/first stop has two documents.

Stop Document SmartLink View

Agent Actions provided for Shipment Stop include the following:

  • Add Document From - Allows you to link/copy a document to a business object from another business object. For example, you link proof of delivery to a shipment stop from a tracking event.
  • Add Document To - Allows you to link/copy a document from a specific business object to another business object. See Utility Agent Actions for details on limits imposed upon this agent action to prevent performance issues.

Shipment Stop Document Agent Actions - Add Document From and Add Document To

  • Send Document Sets - Allows you to send the selected document sets.

Shipment Stop Document Agent Actions - Send Document Sets

Provides you with the ability to manage your Shipment Stop related documents at the Shipment Stop level directly versus managing all Shipment Stop documents at the Shipment level.

Steps to Enable

You don't need to do anything to enable this feature.

Spot Bid Tender

Spot Bid Enhancements

This feature extends the Spot Bid Tender functionality to include a long list of configuration, usability and information availability improvements.  These enhancements will improve the usability of this functionality for your existing implementation(s) and also allow you to extend your usage of the Spot Bid Tender functionality to additional modes, regions and users.

Specific Enhancements include the following:

Enhanced View All Bid Options

This feature provides you with a richer and more complete View All Bid Options UI that allows for a comparison of all the Shipment Cost/Bid Options provided and the ability to award the bid directly from within the enhanced View All Bid Options UI.

In the example below - you can view the different costs and bid options offered by the service providers in one easy to understand view.  In this example, there are three service providers who have provided bids for the shipment. With the enhanced View All Bid Options UI, you can quickly see each service provider and the different options proposed and the total Shipment Cost/Bid Options for each option along with comments related to the options offered.

In this example, the three service providers have provided four different Bid Options:

  • Carrier05 - 1,200.00 USD - This Bid Option requires a change to the Pickup Time.
  • Carrier04 - 700.00 USD - Will take the shipment as tendered.
  • Carrier03 - 400.00 USD - This Bid Option requires a change to Pickup Time.
  • Carrier03 - 1,394.64 USD - Will take the shipment as tendered.

Spot Bid View All Bid Options

Additional Fields

The additional fields (highlighted below) have been added to the Spot Bid Finder, Finder Results, and Spot Bid Tender Results UI.

The Public Spot Bid Tender Finder screen has the additional fields below added to help you quickly find the shipments you are looking for.  

Public Spot Bid Tender Finder

The Public Finder Results has also been enhanced to include the following additional fields.

Public Spot Bid Tender Finder Results

The Public Spot Bid Tender Response manager (edit and view) have both been enhanced to include the additional fields by default.

Spot Bid Tender Response Edit

Public Spot Bid Tender Results Manager- View

The table below provides a complete list of the additions.

Field Public Finder Public Finder Results Manager - Edit Manager - View

Respond by (Expected Response)

X X X X

Origin Location Id

X X X X

Origin Location Name

    X X

Origin Providence Code

    X X

Origin Postal Code

    X X

Destination Location Id

X X X X

Destination Location Name

    X X

Destination Providence Code

    X X

Destination Postal Code

    X X

Shipment Cost (Planned Cost)

X   X X

Shipment Time

X X X X

Offer Pickup Time (Original Pickup Time)

X X X X

Offer Delivery Time (Delivery Time)

X X X X

View All Bid Options Improvements

Bid Options Comments

The service provider can now enter comments at the Bid Option level.  This allows the service provider to better clarify the different bid options provided.  The entered comments are available to review by the planner in the View All Bid Options screen.

Bid Option Comments Entered on Bid Response Screen

The comments enter are available for review on the View All Spot Bids screen as shown below.

View All Spot Bids - Comments

Optional Tag fields

You have the option to customize the Spot Tender Response and View manager layout to include three tag fields within the bid options grid.  In the example below the RefNum1, Refnum2, Refnum3 columns were added to capture additional information as part of the spot bid response and review of all the bid options provided.

Spot Bid Response Enter Tag Fields

Tag Fields on Bid Options

The optional columns, as noted are managed as tag fields - there are three tag fields. In the example below - for the tender response screen set the Refnum1 tag field is configured.

Manager Layout

The tag fields are added to the Bid Options Grid Section.

Details Configure Bid Options Grid

Select and Add Tag Field

To have the configured tag fields added to the shipment - on award - as Shipment reference numbers the property 'log.tender.spotBid.updateShipmentRefNumberQualBasedonTagField should be set  - the property contains comma separated values for the mapping of the Shipment Qualifiers to map to the three tag fields -  such as QUALGID1,QUALGID2,QUALGID3. QUALGID1 is mapped to TENDER_SERVPROV_BID.TAG1, QUALGID2 is mapped to TENDER_SERVPROV_BID.TAG2 and QUALGID3 is mapped to TENDER_SERVPROV_BID.TAG3.

Award Bid Action Converted to Manager Layout Action

You can now configure the information displayed when the Award Bid action is run. To configure the Award Bid action input screen, make a copy of the AWARD_BID Action Manager Layout, configure as desired and then assign to the screen set.

 

Award Bid Action Manager Layout Configuration

Award Bid Action Manager Layout Configuration Detail

New Lower and Upper Bound Threshold Properties for Bid Amount

This feature provides you with the option of defining separate Lower and Upper Bid Amount thresholds.  Previously, a Single Property was used to define both the Lower and Upper Bid Amount thresholds - with the Single Property the upper and lower ranges were the same.  Now, with the two properties, you can define the upper and lower ranges independently.  Note that the new properties do not replace the original property, but they do take precedence.  If both the Single Property and just one of the Upper/Lower value properties are set, the the set Upper/Lower Property values will take precedence, and the Single Property value will be used as the value for for the unspecified Lower/Upper independent property value.. 

Newly added properties:

  • Upper Bound Property - glog.webserver.tender.spotBid.upperBidThreshold
  • Lower Bound  Property - glog.webserver.tender.spotBid.lowerBidThreshold

Original property:

  • Single  Property - glog.webserver.tender.spotBid.bidThreshold

Force Award Reason Code When Lowest Bid Not Selected

This feature allows you to configure the Spot Bid Tender process to require the entry of an Award Reason Code in the situation where the lowest cost bid option is not selected.

To enable this feature the property - glog.tender.spotBid.enableValidationForLowestBid - must be set to true, the Default value is false.

When the property glog.tender.spotBid.enableValidationForLowestBid is set to true, in the scenario below, the user will be required to provide an Award Reason Code when awarding the bid to any service provider other than the service provider with the lowest bid.

The lowest bid in the list of bid available is for Roadway at 1,100.00 USD.  

Spot Bid Options

The user selects Red Star to Award the bid to, Red Star's last bid is higher than the lowest bid, since this is not the lowest bid, the user must enter in an Award Reason Code to provide a reason for their award decision.

Award Reason Code Required

Award Reason Code

The entered Award Reason Code is stored in the TENDER_COLLAB_SERVPROV.DECLINE_REASON_CODE_GID column.

This feature provides a long list of usability and functional improvements to the Spot Bid Tender feature.  These changes will simplify the usage of the Spot Bid Tender process and allow you to be extend the usage of this functionality to new regions and modes.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Note that you have the option to configure the screens (manager view and edit) and the finder finder results to included/exclude the information you would like to see.

Rate Maintenance

Rate Maintenance UI Refresh

This feature updates the Rate Maintenance UI from the legacy ADF UI infrastructure to OTM's standard UI infrastructure, providing you with improvements in the overall user experience and usability of the Rate Maintenance functionality. 

Rate Maintenance steps that previously required the usage of non-standard search screens or involved multiple screens or multiple tabs have been redesigned so that the Rate Maintenance process is more streamlined and consistent with the rest of the application. 

The View Approval Details process has been completely redone and is now managed within a single Enhanced Workbench, providing you with a more intuitive way to manage the approval process at the Rate Load Group level, Rate Offering level and Rate Record level.

To demonstrate the new UI changes, a simple end-to-end Rate Maintenance scenario is provided below. While the UIs for Rate Maintenance are new, the Menu, Springboard and Menu links for the Rate Maintenance functionality have not changed.

For the Rate Maintenance process, the first step involves defining your Rate Load Definition - this is accomplished via the Manage Rate Load Definition menu option.

Rate Maintenance Springboard Options

After selecting the Manage Rate Load Definition option, you will notice that the Rate Load Definition screen has been redone and is now a standard Finder screen.

Manage Rate Load Definition Finder Screen

The Rate Load Definition New UI (below) has been redone so that it mimics the legacy UI. In this case, the UI's look and functionality are similar to the legacy UI, but the UI has been re-written using the new UI infrastructure.

Rate Load Definition New Screen

For this demonstration, a new Rate Load Definition will be created as shown below.

Rate Load Definition New Screen - New RLD

Now, when you select the next step in the process - Save and Continue - the Rate Load Definitions UI (below) is provided.  Again, this UI is similar to the legacy UI - with a couple of improvements.   The Involved Parties grid is now a standard Involved Parties grid and the icons displayed have been revised to follow the new Redwood UI standards. 

Rate Load Definition Header

Rate Load Definition Header with Involved Party

Moving from the Rate Load Definition Header tab to the Rate Load Definition Rate Offering Structure Tab, you will notice that the new UI is very similar to the legacy UI and provides the same functional capabilities - you can include or exclude columns, make columns read only and reorder columns.

Rate Load Definition Rate Offering Structure Tab

Like the Rate Load Definition Rate Offering Structure Tab, the new Rate Record Structure tabs are very similar to the legacy UI and provide the same functional capabilities  - you can include or exclude columns, make columns read only and reorder columns.

In the example below - the Rate Record Structure 1 supports a per Shipment cost as shown under the Rate Costs section.

Rate Record Structure 1 Tab

For this example, Rate Record Structure 2 supports a per Shipment Total Distance (Including Depot Stops) rate structure.

Rate Record Structure 2 - Per Mile

Once the Rate Load Definition is configured, the next step involves downloading the Rate Load Definition.  You have the option to Download without Rates or to download with rates - the download with rates option - Multiple Structure Rate Download - allows you to pick and choose which Rate Structures to download for one or multi-structures - assuming multiple rate structures are available.  In this example, multiple rate structures are associated with the Template Rate Offering - one structure supporting a Shipment Total Distance RBI and the other supporting a per Shipment cost.   

Download Rate Load Definition Actions

For the Multiple Structure Rate Download action (which actually supports single and multiple rate structures) - the UI has been improved so that the selection of the structures to include is managed using a Rate Record Saved Query.  To demonstrate, in the example below, if both the per Shipment Structure and the per Shipment Total Distance structure were to be included, that is accomplished by having a saved queries for the Rate Records that provides the desired Rate Record Structure for each of the Rate Structures that will be used/downloaded.  In this case, the Saved Query RLDSTRUCT_ST2ST_PERSHIP provides the structure for the per Shipment rate and the Saved Query RLDSTRUCT_ST2ST_PerMI provides the rate record for the Per Shipment Total Distance rate.

Rate Record Structure 1 - Select Related Rate Record Saved Query

The process for adding the Rate Record Structure(s) is to select the Rate Record Structure and the corresponding Rate Record Saved Query and then Add the selection to the list.  In the example below - the Add step for Rate Record Structure 1 and Rate Record Saved Query is shown.

Add Rate Record Structure 1 and Rate Record Saved Query to Download List

Once you have added a Rate Record Structure and Rate Record Saved Query to the list, the actions for Selected Rates and Download Rates are available, so for a multiple structure rate you could run the Download Rates action for one structure and then add the additional structure(s) and re-run the Download Rates action.

Added Rate Record Structure and Rate Record Saved Query

For this example, both Rate Record Structures and Rate Record Saved Queries will be added and then the Selected Rates option will be used to finalize the list for running the Download Rates action.

Selected Rates- Multiple Rate Structures and Rate Record Saved Queries Added 

When the Selected Rates action is run, the selected Rate Record Structure(s) and Rate Record Saved Quer(ies) are ready for Download - as shown below.  At this point, you have the option to remove any of the selected Structures or download all selected..

Ready to Download

When the Download Rates process is initiated, an informational message is provided to keep you informed of the system's activity and what to expect.

Download Message

As noted in the message, when the Download process is complete - an email, with attachments, will be provided as shown below.

Download Email

The downloaded rate spreadsheet can then be updated with the information required to either create a new version of an old rate offering or it can be used as a template for creating new rates covering different geography.  Note - no changes have been made in this release to the functionality related to the generation and management of the provided spreadsheets.  For completeness, what was downloaded in this example is shown below.

Structure 1 State to State Per Shipment Rate

Structure 1 State to State Per Shipment Total Distance Rate

After making the required changes to the downloaded spreadsheet - the next step in the process is to upload the spreadsheets. For this example, the spread sheets are being used to create 48 rates that are using the per mile rate structure and then two additional rates will be created for the per shipment rate - for lanes going from California to Hawaii and California to Alaska.

Upload Rates

Selection Upload Rates brings you to the UI below, where you specify the file/spreadsheet to upload.

Upload Rates

To upload your rates, select the file to upload, enter a Rate Load Group ID and select Upload.

Upload Rates

Upload Rates Message

Like the download process, an email will be provided with information about the Upload.  In this case, all of the rates were uploaded successfully.

Upload Rate Status Email

Once the rates have been uploaded, the remaining steps focus on review and approval - with the final step making the new rates operational.  The final steps are all accomplished using by navigating to the Approval Summary menu option.

Approval Summary

Selecting Approval Summary brings you to the Rate Load Summary Finder UI - again - redone as a standard Finder and Finder Result.

Rate Load Finder

In the Rate Load Summary results, for the upload that was completed - the Rate Load Summary results provides Upload Status (SUCCESSFUL), an indication if there were an issues Warning Indicator (check/none), the number of records uploaded (50), the user uploading the records (OOTB.TB) and a view to the Approval Status - in this case no approvals have been done, the upload is NEW,

Rate Load Summary Result

At this point, you have the option to perform a number of Actions related to approval for all the rates associated with the uploaded Rate Load Group - you can Approve All, or Approve Only New.

Rate Load Group Actions

You also have the option of approving at a more detailed level using the View Approval Details enhanced workbench.  The View Approval Details navigation to the View Approval Details is done via a SmartLink as shown below.

View Approval Details SmartLink

Selecting the View Approval Details SmartLink will bring up the enhanced workbench below.  The View Approvals Details workbench allows you to run actions at different levels, you can run actions at the Rate Load Group level - and all Rate Offerings and Rate Records will be impacted or you can run Actions at the Rate Offering level, or you can run actions at the Rate Record level.

View Approval Details Enhanced Workbench

Actions for Rate Load Group Level

Actions for Rate Offering Level

Actions for Rate Record Level

To complete the process, the newly added rates will be approved at the Rate Load Level and then Finalized after being approved.

Approval All Rate Load Group Level

Approval All Message

Below is the view after the Approval As completed.  Note that the Rate Offering and Rate Records are Approved, the Approval Status for the Rate Load Group is now In Process with the final step being Finalize All.

View Approval Details After Approve All

To finalize the process and make the rates operational, you will run the Finalize All action.

Finalize All

Below is the message received when you run the Finalize All action. In this case the Finalize All action ran successfully - one Rate Offering was created with 50 Rate Records.

Finalize All Action Message

After the Rate Offering and Rate Records are Finalized the information will be removed from the View Approval Details workbench - since they are beyond the Approval step.  The rate load definition provides a view to the final status for this Rate Maintenance loading exercise.

Approval Status Final

Below is the newly added Rate Offering and the newly added Rate Records.

Rate Offering and Rate Records

This feature improves the usability of the Rate Maintenance feature - eliminating unnecessary steps and consolidating information into single UIs.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

  1. Your menu links will need to be reverted back to the Legacy Rate Maintenance Screen Sets
  2. You will need to Opt Out of the Optional Feature USE ENHANCED RATE MAINTENANCE LINKS IN EMAILS.  This step requires DBA access.

More complete steps on how to revert back have been provided in Help.

Use Enhanced Rate Maintenance Links in Emails

This Optional Feature is provided in the unlikely case that you need to revert back to the legacy Rate Maintenance UIs from the new Uis.  This feature, when enabled, provides emails links to the new Rate Maintenance UIs.  In the unlikely event that you need to revert to the legacy UIs, Opting Out of this feature will switch the Rate Maintenance emails links to the legacy UIs.

Provides you with the option - if necessary - to revert to the old legacy Rate Maintenance UIs.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Reverting back to the legacy Rate Maintenance UIs requires several steps.

  • You will need update your Menu to point to the legacy Finders and Finder Results.
  • You will need to Opt Out of this Optional Feature so that Rate Maintenance email provide links to the legacy UIs.

Shipment Group

Enable Ship Group SC Rule Rule Type Validation

This Optional Feature - Enable Ship Group SC Rule Rule Type Validation - when opted in - provides the following validation - only secondary charge rule of type shipment group can be added to the shipment group rule and only secondary charge rule of type shipment group will be used to build secondary charge shipments.

This feature - when enabled - validates the proper assignment of secondary charge rules defined for shipment groups and the assignment of those rules for building secondary charge shipments for shipment groups. 

Steps to Enable

You don't need to do anything to enable this feature.

Shipment Group UI Web Action - Recalculate Secondary Charge Shipment

This feature provides you with a new Shipment Group UI web action -  Recalculate Secondary Charge Shipment - which will recalculate the cost of your shipment group secondary charge shipment.

Recalculate Secondary Charge Shipment

Recalculate Secondary Charge Shipment - Result

This feature provides you with the option to manually recalculate your shipment group secondary charge shipment.  

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The Shipment Group UI Web Action - Recalculate Secondary Charge Shipment - provides you with a manual action for recalculating the secondary charge shipment related to a shipment group.  The Shipment Group agent action equivalent - Shipment Group Recalc Secondary Charge - was made available in a previous release.

Secondary Charge Rule Shipment Group Criteria

This feature provides you with Secondary Charge Rule Criteria that is used to limit the shipment groups the defined Secondary Charge Rule will apply to.

The Secondary Charge Rule Criteria for shipment groups is provided for the Rule Type of Shipment Group.

The screen shot below shows the Secondary Charge Rule Criteria that is available for the Secondary Charge Rule of Shipment Group.  

The new Secondary Charge Rule Criteria added for Shipment Group includes:

  • Lane ID
  • Port of Load
  • Port of Discharge
  • Involved Party Qualifier
  • Contact Profile ID
  • Service Provider ID

Secondary Charge Rule - Shipment Group Rule Type

This feature allows you to defined Secondary Charge Rules with Criteria that is specifically related to the generation of Secondary Charges for Shipment Groups.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

You should consider enabling the Optional Feature - Enable Ship Group SC Rule Rule Type Validation - which - when opted in - provides the following validation - only Secondary Charge Rules of type Shipment Group can be added to the Shipment Group Rule and only Secondary Charge Rules of type Shipment Group will be used to build Secondary Charge Shipments.  

Rate Service and Activity Time

Equipment Reference Unit Location Activity Time

This feature provides you the option of defining your Location Activity Time Definition by Equipment Reference Units (ERUs).  You will find this option beneficial in any scenario where your location's stop activity times are determined by the number and type of Equipment Reference Units being loaded or unloaded.

In the example below, the location's Location Activity Time Definition is defined for two different Equipment Reference Units (ERUs).  The Activity Time Definition for ERU SMALL BOXES related to the Equipment Reference Unit SM_BOX - is defined with a 30 Minute Fixed Stop Time and a 10 minute variable loading time for every 10 SM_BOX ERU units.  The second Activity Time Definition  - ERU BIG BOX - is defined with an hour of Fixed Stop Time and a variable activity time of 20 minutes for every 5 BIG_BOX ERU units.   

ERU Activity Time Setup

Given the Order Release Lines below -  one with 50 SM_BOX ERUs and another  with 25 BIG_BOX ERUs. 

Order Release Line 1 50 SM_Box units

Order Release Line 2 25 BIG_BOX ERU Units

Based on the Location Activity Time Definition above - the Location Activity time - for this order with these two lines will be the calculated as the sum of the Fixed Stop Times for these two ERUs (30 minutes plus 1hour) plus the maximum value for the calculated variable activity time for the two Activity Time Definitions.  In this case - for the SM_BOX - (50 SM_BOX ERUs/10) * 10 Minutes = 50 Minutes versus BIG_BOX (25 BIG_BOX/5) * 20 Minutes = 1 hour 40 minutes which provides a total Activity Time at the stop of  1 hour 30 minutes of Fixed Time plus 1 hour 40 minutes of variable time for a total Activity Time of 3 hours and 10 minutes. 

Total Stop Activity Time and Ship Unit Variable Activity Time 

Provides implementations using ERUs as their primary unit of measure with the option to define activity time at their location's based on ERU count.

Steps to Enable

To take advantage of this feature - you will need to create a new Location Activity Time Definition where the Fixed and Variable Time Activity Time Definition is based on an Equipment Reference Unit ID and an Equipment Reference Unit Count. 

Equipment Reference Unit Activity Time Definition 

Day Duration Rate Service Supports Same Day Pickup and Delivery

This feature enhances the DAYDURATION Rate Service so that both Pickup and Receive activities can be scheduled on the same day.

Previously, the DAYDURATION Rate Service with a zero-day Service Days value for a lane would (by default) add a day to the service time calculation and treat a zero-day Service Days setup as a one-day duration.  Now, with this enhancement, a zero-day Service Days value will be treated as a same-day delivery transit time opportunity.

In the example below, the DAYDURATION Rate Service has been configured to support same day service on a lane from location DC1 to the state of CA.  The Calendar  (SAMEDAY) assigned to the Rate Service defines the same day time for the service with a Pickup window from 8AM to 9AM and a Receive window of 5PM to 8PM.  To simplify the demonstration the location calendars involved here do not impact the times shown - but remember that location calendars are considered in the logic. 

Example Same Day DayDuration Setup - Header

For this setup - the calendar SAMEDAY - is defined as a 5 day a week Pick and Receive calendar.

Example Same Day Setup - Calendar

Below is the lane level setup - in this example, service from the DC1 location to any location in State/Provide Code of CA will be same day  - configured with Service Days = 0.00.

Example Same Day Rate Service - Detail

When this rate service is used - the shipment stop times, by default, are as follows... the pickup departs at 9:00 AM (latest Pickup time) and delivers at 17:00/5:00 PM - the earliest Receive time.

Example - Same Day Dayduration Rate Service - Shipment Stop Times

The calculated Transit Time in this example - from 9:00 AM to 5:00 PM is 8 hours as highlighted below.

Transit Time

Previously - the same setup would have provided the result below, where the pickup occurs on October 3rd at 9:00 AM and the delivery occurs 1 day later on October 4th at 17:00/5:00 PM.  Now, to achieve this same result, the Service Days value will need to be set to 1.0. A Service Days values of zero will now be interpreted as same day.

Previous Result - Same Setup

This feature allows you to model the increasingly more common same day pickup and delivery option using the OTM DayDuration Rate Service. 

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

NOTE: The new behavior/interpretation of zero days is on by default, and is not controlled by a parameter, property or an Optional Feature.  If, for some reason, your Day Duration was setup with zero days specified for the Service Days value (taking advantage of the one day transit interpretation) then, for these zero day setups, the calculated transit time will be changed by this feature.  If, again, you have DAYDURATION Service Days values set to 0.0/zero assuming OTM will default to a one day transit  - you will want to update the 0.0 value entries for Service Days to 1.0 to provide the desired result of a one day transit time.

Only Handle One Pickup/Delivery

  • OTM will not handle the case where the same same-day rate service specifies different pickup/delivery times.  For example, there is a legitimate business case where the same-day service is something like "pick at 9am, deliver at 5pm / pick at 12:30pm, delivery at 8pm".  However, we will not handle this case.

The parameter BY DAY RATE SERVICES USE EARLY PICKUP TIME by default is set to FALSE - if you would like to use the latest pickup time instead  = you can accomplish that by setting the parameter to TRUE.

Asset Position and Status Report

Fleet Asset Position Report and Fleet Asset Status Report

This feature provides you with two operational reports that you can use to understand and share the current status and position of your fleet.  The reports are designed to serve the needs of specific users within your operation. 

The Fleet Asset Position Report provides visibility to your customers for all the loaded enroute assets heading to their location (s) - information available includes product, asset ID, ETA and latest position.  The Fleet Asset Position Report also provides your planners with visibility to empty assets that can be scheduled for loading - information includes asset ID, ETA and current position etc. 

The Fleet Asset Status report provides your asset manager with a comprehensive view to the current status for all of the assets they manage.

Both reports are dependent on the availability of equipment static data (ID, etc.), tracking event data, and the configuration of several agents.  Once all of the configurations and data feeds are provided, you will find the Fleet Asset Position and Status Reports extremely helpful in understanding the current status and position of your equipment.

Both reports - Fleet Asset Position Report and Fleet Asset Status Report are available in the Report Manager (Business Process Automation > Reporting > Report Manager) under the Asset Management Reports heading.

Fleet Asset Position and Fleet Asset Status Reports

Below is an example of the Fleet Asset Position Report for one Division and Customer Fleet. The report is grouped by Division Name, Customer Fleet and then for each Equipment in the Division and Customer Fleet the details are reported for each Status Value in the newly added Status Type of SERVICE_TRACKING.

The Fleet Asset Position Report can be used to provide visibility to your customers for all the loaded enroute assets heading to their location (s).  In the example below, the Fleet Asset Position Report is run to provide the Southern Fuels receiving department at the Jackson Mississippi plant visibility into the enroute equipment, product and current ETA.

Fleet Asset Position Report Example - Parameters - Receivers - Enroute Loaded

The report below provides the receiving department at Jackson MS with usable information regarding enroute equipment (5 cars), the product loaded on the equipment (Biodiesel) and the ETA of each asset/car/equipment.

Enroute to Southern Fuels Jackson MS Destination

The same report can be run to provide the Midwest Biodiesel planner with visibility to inbound empty cars.  In the example below, the report is run to provide the planner at the El Paso location visibility into incoming empties.

Fleet Asset Position Report Example - Parameters - Planners - Inbound Empty

Inbound Empty Equipment for El Paso

Equipment Status and Equipment State

For the Fleet Asset Position Report the two report parameters Equipment Status and Equipment State are actually mapped as follows.  The Equipment Status is mapped to the Status Type of SERVICE_TRACKING.  The Equipment State is mapped the Status Values supported by the Status Type of SERVICE_TRACKING. 

Status Type and Status Values reported in the Fleet Asset Position Report

  • SERVICE_TRACKING_LOAD - UNASSIGNED
  • SERVICE_TRACKING_LOAD – PLANT
  • SERVICE_TRACKING_EMPTY – HOLD
  • SERVICE_TRACKING_LOAD – CUSTOMER
  • SERVICE_TRACKING_EMPTY – CUSTOMER
  • SERVICE_TRACKING_EMPTY – PLANT
  • SERVICE_TRACKING_EMPTY – ENROUTE
  • SERVICE_TRACKING_LOAD - ENROUTE

Mapping and Report Prerequisites

 Most all of the data provided in the Fleet Position Report is managed on/through the Equipment Record. For example, 17 of the 19 fields provided on the report are provided on or through the Equipment object.  The only fields not managed on/through the Equipment record are the IN TRANS DAYs (In Transit Days) and the DWELL DAYS which are provided by the report itself.

 

Fleet Asset Position Report for Equipment ADMX130

Below is the Equipment Record with the fields that are mapped into the report above.  

Equipment Record

Fleet Asset Position Report - Mapping and Processing

Fleet Asset Status Report

The Fleet Asset Status Report provides your Asset Managers with a summary/count of the Fleet Status by Division and then by Fleet along with a summary count for Loaded v Empty and Load %.

To see the status of all the fleets across all divisions the report would be run without specifying any specific Division or Fleet.

Fleet Asset Status Report - All Divisions and All Fleets

Fleet  Asset Status Report All Divisions All Fleets

Entering information about your Division and/or Fleet, for example Division =  Midwest Biodiesel and Fleet = Eve-Cheyenne - will narrow the information down to the specific Division and/or Fleet you are interested in.

Fleet Asset Status Division  = Midwest BioDiesel and Fleet = Eve Cheyenne

Fleet Asset Status Report Division = Midwest Biodiesel Fleet = Eve Cheyenne

  

This feature pulls together all the various pieces of information required to provide information about the current status and position of your Fleet/Equipment Assets.

Steps to Enable

To take advantage of the provided Fleet Asset Position Report and Fleet Asset Status Report you will need to setup the necessary static data, provide the required tracking event information and create or configure Automation Agents to process the incoming information to support the operational nature of the reports.

Usability and Performance

Add Tracking Event to Shipments

This feature provides you with a new Shipment web UI action - Add Tracking Event to Shipments - that allows you to add the same Tracking Event information to more than one shipment. This new capability is designed to support the manual input of a standard set of tracking events against a set of shipments. 

In the example below, the15 shipments completed by Carrier04 on October 26th - need to have a pickup and delivery Tracking Event added for each shipment.  Previously, for the same set of shipments, the Tracking Events for the pickup and delivery would need to be added for each shipment one at a time - so 30 individual entries..

Shipments Requiring Pickup and Delivery Tracking Events

In this example, all 15 shipments start at the same location - DC1, using the new action Add Tracking Event to Shipments, you will now be able to add the Pickup Tracking event for all 15 shipments running the new action just one time.

Shipments Requiring Pickup and Delivery Tracking Events

Add the Pickup Tracking Event to all 15 shipments. Select all 15 shipments and run the Add Tracking Event to Shipments action.

Add Tracking Event to Shipments

Add Tracking Event to Shipments Input

To enter the Tracking Event for the completed pickup, all that is required is a Quick Code - which provides the Status, Status Code, Reason and Reason Code for the pickup tracking event.  the Date and the Shipment Stop.  The Add Tracking Event to Shipments action evaluates the set of shipments selected and will provide the list of Shipment Stops shared by all of the selected shipments - in this case the only common stop is the pickup stop. 

Add Tracking Event to Shipments Pickup at DC1 Input

Tracking Events Added Confirmation

To add the delivery tracking events - the shipments were delivered to two different locations - Diamond Bar and Coachella.  Selecting all the shipments that delivered to Diamond Bar and running the action Add Tracking Event to Shipments action will allow you to add all the delivery tracking events for for all the shipments that delivered to the Diamond Bar location.

Select the Shipments Delivering to the Same Location

Add Tracking Event to Shipments Delivery at Diamond Bar Input

Note that in this example, the Shipment Stops available in the drop down will include both the pickup stop and the delivery stop, since both are shared by all of the selected shipments.

Both Pickup Stop and Delivery Stop Shared

The above steps can be repeated for the second set of shipments that require a delivery Tracking Event for the deliveries at Coachella.

Add Tracking Event to Shipments Delivery at Coachella Input

Below are the results for a few of the shipments, running the Add Tracking Event to Shipments three times - added all 30 of the required Tracking Events in this example.

Tracking Events Added

Tracking Events Added

This feature provides an easy way to enter the same Tracking Event information -  Quick Event, Date, Shipment Stop - to many shipments.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

You may consider creating Quick Codes that map to the Tracking Events you wish to add to multiple shipments using the Add Tracking Event to Shipments action.

Keep Existing Service Provider for Unassign

This feature provides you with the option of retaining the currently assigned Service Provider for your shipments in the scenario where an order (or order movement) is unassigned from a shipment and the desired behavior is for OTM to re-drive/re-rate the shipment, but retain the current Service Provider even when a less expensive alternative Service Provider and rate could be assigned.  With the previous (on by default ) logic, the logic includes the option to change the Service Provider as part of the order unassignment process if changing the Service Provider provides a lower cost solution.  With this new feature - for all your unassign order/order movement scenarios, you have the option to retain the existing Service Provider.

In the example below - an order is unassigned with the new Shipment Planning Parameter KEEP EXISTING SERVICE PROVIDER FOR UNASSIGN set to the default value = FALSE - which, in this case - using the current logic - results in the Service Provider being changed from Red Star to Werner.  Then, in the second example, the same scenario is run, but in this case the Shipment Planning Parameter KEEP EXISTING SERVICE PROVIDER FOR UNASSIGN is set to TRUE and the original Service Provider is retained.

Orders for this example are from the same source and destination.

Sample Orders

The shipment created - two stops from origin Tulsa to destination Houston.  Red Star is the Service Provider Assigned and the cost is 593.80 USD.

Shipment Created

Now unassigning one of the orders on the shipment using the Unassign Action results - using the default behavior - with the Service Provider being changed to Werner from Red Star.  The change to Werner reduces the cost for the shipment from 593.80 USD to 360.00 USD .

Unassign Order

When the action is run - with the current logic/default logic, the system will change the assigned Service Provider if a lower cost feasible option is available which is the case in this scenario - changing to Werner does reduce the cost to 360.00 USD.

Default Unassign Order Behavior

Below is the same Unassign action, but in this case the parameter Shipment Planning Parameter KEEP EXISTING SERVICE PROVIDER FOR UNASSIGN is set to TRUE.  With this parameter setting Red Star is retained as the Service Provider- even though a less expensive alternate exists - Werner. 

Keep Existing Service Provider for Unassign = TRUE

This feature provides you with more control over the impact order release (order movement) unassignment scenarios have with your planned shipments.

Steps to Enable

To take advantage of the new behavior, you will need to set the parameter KEEP EXISTING SERVICE PROVIDER FOR UNASSIGN in your parameter set to TRUE - the default value is FALSE - which retains the current behavior. 

Shipment Management > Power Data > General > Parameter Sets  - Group = Shipment Planning

Keep Existing Service Provider for Unassign

Below is an example of a Domain level Parameter Set setup. 

Domain Level Planning Parameter Setup

Tips And Considerations

  • When the Unassign Order action runs the Parameter Set is set on the action (whether in the UI or on the agent action), OTM use that Parameter Set instead of the Domain’s default PPS.
  • The UNASSIGN ORDER agent action honors the new parameter (KEEP EXISTING SERVICE PROVIDER FOR UNASSIGN)
  • The ORDER RELEASE – DELETE agent action honors the new parameter
  • The ORDER RELEASE – MOD – FULL IMPACT agent action honors the new parameter
  • Use the existing property glog.business.orderActions.unassign.redriveShipmentWithOptimalStartTime to redrive your shipment after the unassignment process if you want the shipment to reflect the time windows of the orders that remain on the shipment after the unassign is complete.  The property provides the following behavior:
    • When unassigning an order release, OTM redrives the partial shipment with original shipment's start time that is being unassigned (default is false, existing default behavior). When set to true, OTM will redrive the shipments using the optimal start time in the unassign process.

      For example, you have three orders releases with early pickup dates of the 19th, 20th and 21st. When planning these, the shipment is planned with a start time on the 21st. If you unassign the last one (early pickup date of the 21st). The resulting shipment is still planned with a start time on the 21st. When true, the shipment will be updated from the original start time (the 21st) to the next latest early pickup date on the remaining order releases (the 20th).

Allow Order Unassign When Rating Is Infeasible

This feature allows you to un-assign your orders or order movements from shipments even in situations where the un-assignment will lead to the shipment being Rate Infeasible.

In previous versions, OTM's logic would not allow you to unassign an order or order movement if that unassign action would result in a Rate Infeasible shipment.  With this enhancement, you can un-assign your orders or order movements even if the impact of the un-assignment is for the shipment to be infeasible from a rating perspective.

In the example below, two orders - when routed together, meet the rate condition on the available rate record -  in this case the rate applies for shipments greater than 25000 pounds. In this example if either order is unassigned, the assigned rate will no longer be feasible/valid for the resulting shipment.  

The rate record for this scenario is below, the rate is valid for shipments that have a shipment total weight that is greater than 25,000 pounds.

Rate Record

The two orders planned in this example - have a total weight > 25000 pounds - 26000 pounds.  Un-assigning either order will result in the rate record assigned to the shipment to be infeasible.

Order Planned

With the existing behavior/default behavior, un-assigning the order for 4000 pounds results in an error message, and the order is not unassigned.

Unassign Order

When the order is unassigned - without the new parameter configured to allow for the unassign, the error message below is displayed, and the order is not removed.

Error Message  -- Order Is Not Unassigned

Now - using the Shipment Planning planning parameter ALLOW UNASSIGN WHEN RATING INFEASIBLE is set to TRUE  - the order can be unassigned.

In the example below - the same order as above is being unassigned - but in this case the Shipment Planning planning parameter ALLOW UNASSIGN WHEN RATING INFEASIBLE is set to TRUE.  With the parameter set to TRUE the un-assignment now works.

Rate Infeasible Un-assign Success

The impacted shipment  - shipment 24191 - is now Rate Infeasible once the order is unassigned.

Rate Infeasible Shipment After Un-assign

This feature provides a straightforward way to unassign orders from shipments even in situations where unassigning the order invalidates the rate used on the impacted shipment.

Steps to Enable

You will need to set the Shipment Planning parameter ALLOW UNASSIGN WHEN RATING INFEASIBLE to True.  The related Planning Parameter Set should be provided as the Domain Default planning parameter set.

Tips And Considerations

A related parameter for time infeasible scenarios (ALLOW UNASSIGN WHEN TIME INFEASIBLE) was provided in the 22C Update. With the 23A update, the original parameter shipped with 22C (ALLOW TIME INFEASIBLE FOR UNASSIGN) has been renamed to ALLOW UNASSIGN WHEN TIME INFEASIBLE and regrouped (moved from SERVICE TIME to SHIPMENT PLANNING)  so it is co-located with the ALLOW UNASSIGN WHEN RATING INFEASIBLE parameter.

Two Allow Unassign Parameters

Check Tender on Shipment Delete

This Optional Feature, Check Tender On Shipment Delete, when enabled, will improve the processing done to check the tender status of a shipment as part of a shipment deletion to verify that the shipment can be deleted.  

This feature, when enabled, will provide performance improvements as part of the shipment deletion process by improving the tender status check done as part of the shipment delete process.

Steps to Enable

You don't need to do anything to enable this feature.

External Distance Engines - Address Validation

Here Technologies - Address Validation - Quality Level

This feature extends the Address Validation process to include the Quality Level match value provided by Here Technologies.  You can use the Quality Level match value to configure the system to eliminate (poor) matches that do not meet your desired Quality Level threshold value.  In addition, the Validate Address action provides the Quality Level match value for all matches that meet or exceed you Match Threshold.

This enhancement also extends the Address Validation information that is saved to your locations.

Quality Level

For the HERE Geocoding & Search API (v7) the Quality Level values (scoring values) provided fall between 0 and 1.  A value of 1 indicates that all of the address tokens matched (e.g., house number; prefix direction, prefix type, street name; street type, city, province code, postal code), while a value of 0 indicates that none of the address tokens matched.

In the examples below (where the correct address is: 191 Park Dr Boston MA 02215), it's clear that the Quality Level score provided by Here Technologies Geocoding & Search API (v7) is dependent on the presence and the correctness of the various address tokens provided. Depending on the quality of the information provided for an address, the Quality Level value returned can be an excellent guide for selecting the correct match, while in other situations, where there is missing or incorrect address information, the Quality Level value maybe a less useful guide.

In the example below - the Quality Level value is 1.0 - meaning that all the address tokens match - a perfect match, and there is just one match provided.  In this case, the Quality Level value is an excellent indicator for the quality of the match.

Correct Address Perfect Match Quality Level - 1

In the example below, the address has been altered a bit, the Street Type has been incorrectly entered as AVE vs the correct value of DR.  In this case, there is still only one match (to the correct address), but the Quality Level match value is now just .83 vs 1.0 for an exact match.  The match is good - but not an exact match.

Wrong Street Type Match Quality Level Now - .83

In the third example below, the address has been altered so that the Street Type has been removed altogether.  In this case, there are now Multiple Matches (six) and the Quality Level value provided is the same for each of the matches (.99) - in this case the Quality Level value provides limited/no real guidance for selecting the best match.  The point here is that the Quality Level value provided by Here Technologies can be useful guide in some situations, but in situations with Multiple Matches, the Quality Level provided by Here Technologies is not a fool proof guide for selecting the best/right match.  

No Street Type - Multiple Matches - All Same Quality Level - .99

Location Address Validation Fields Added

As part of this feature, the Address Validation information stored on a location has been extended to include the following details:

  • The External Engine used for Validation
  • The Quality Level value of the match provided by the engine used
  • A Multiple Matches indicator to indicate if the match was a single match or if there where multiple match options identified for the address provided.

Additional Address Validation Information on Location

Turn Off Postal Code Latitude/Longitude Lookup

This feature also provides you with the option of turning off the usage of the Postal Code Latitude/Longitude power data table (the GEO_POSTAL_POINT table) for geocoding your locations - turning this logic off will allow you to configure your Address Validation and Geocoding process to use the Here Technologies Geocoding & Search API as the source for your location address validation and latitude/longitude values.

To turn off the Postal Point lookup - you will set need to set the property - glog.ExternalDistanceEngine.Geocode.UseGeoPostalPointData - to false - the default value is true/to use the Postal Point lookup.

NOTE: Only the DBA.ADMIN user can access and use the Property Sets page.

Property

Set Quality Level Threshold

To set the Quality Level value, navigate to Shipment Management > Power Data > Geography > External Distance Engine and select the current External Distance Engine setup for Here Technologies - or create a new one. In the example below, the Quality Level threshold value has been set to .95 - which means that matches with Quality Levels that fall below .95 will not be considered.

Quality Level Threshold Value

The addition of the geocoding quality factor, for those implementations that depend on accurate street level geocoding, will ensure that locations will only be updated with latitude/longitude values that satisfy the required level of match accuracy.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Note the Here Technologies Geocoder API (v6) is now in Maintenance mode and is no longer actively supported by Here Technologies.

Key Resources

For more information about the Quality Level information provided by HERE Geocoding & Search API v7:

  • https://developer.here.com/documentation/geocoding-search-api/api-reference-swagger.html

PC*MILER Web Service - Address Validation - Quality Level

This feature extends the Address Validation process to include the Quality Level match value (Confidence Level) provided by PC*MILER Web Service.  You can use the Quality Level match value to configure the system to eliminate (poor) matches that do not meet your desired Quality Level threshold value. When the Validate Address action is run, all the matches above the Quality Level match value will be available for you to review

This enhancement also extends the Address Validation information that is saved to your locations - information related to the Address Validation Quality Level and the presence of Multiple Matches during the Address Validation process are now saved to the location.

Quality Level

For the PC*MILER Web Service the Quality Level values (Confidence Level values) available are: Exact, Good, Uncertain, and Failed - explanation below. 

The Quality Level (Confidence Level), indicate for each result provided how good the result matches to the original query. 

  • Exact – An exact match was made. For street addresses, trust is 95% or greater.
  • Good – Inexact match but unique result (i.e. there is only one match). For street addresses, trust is 85% or greater.
  • Uncertain – Inexact match and there is more than one match in the database. For street addresses, trust is 50% or greater.
  • Failed – Match not found. Trust is below 50% for street addresses. Trust is below 50% for street addresses.

In the example below - the Quality Level value is Exact - there is just one match.  In this case, the Quality Level value is an excellent indicator for the quality of the match.

Correct Address Exact Match

Location Address Validation Fields Added

As part of this feature, the Address Validation information stored on a location has been extended to include the following details:

  • The External Engine used for Validation
  • The Quality Level value of the match provided by the engine used
  • A Multiple Matches indicator to indicate if the match was a single match or if there where multiple match options identified for the address provided.

Additional Address Validation Information on Location

Turn Off Postal Code Latitude/Longitude Lookup

This feature also provides you with the option of turning off the usage of the Postal Code Latitude/Longitude power data table (the GEO_POSTAL_POINT table) for geocoding your locations - turning this logic off will allow you to configure your Address Validation and Geocoding process to use PC*MILER Web Service as the source for your location's address validation and latitude/longitude values.

To turn off the Postal Point lookup - you will set need to set the property - glog.ExternalDistanceEngine.Geocode.UseGeoPostalPointData - to false - the default value is true/to use the Postal Point lookup.

NOTE: Only the DBA.ADMIN user can access and use the Property Sets page.

Property

Set Quality Level Threshold

To set the Quality Level threshold value, navigate to Shipment Management > Power Data > Geography > External Distance Engine and select the current External Distance Engine setup for PC*MILER Web Service  - or create a new one. You can select any of the available PC*MILER provided Confidence Values as your desired threshold value.

Quality Level Threshold Value

The addition of the geocoding quality factor, for implementations that depend on accurate street level geocoding, will ensure that locations will only be updated with latitude/longitude values that satisfy the required level of match accuracy and precision.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

The link below provides more information about the PC*MILER Web Service Address Validation and geocoding api: 

  • https://developer.trimblemaps.com/restful-apis/location/geocoding-api/geocoding/

Oracle Map Cloud Service - Address Validation - Quality Level

This feature extends the Address Validation process to include the Quality Level match value provided by Oracle Map Cloud Service (aka Oracle Spatial).  You can use the Quality Level match value to configure the system to filter out (poor) matches that do not meet your desired Quality Level threshold value. When the Validate Address action is run, all the matches above the Quality Level match value that you configure will be available for you to review

This enhancement also extends the Address Validation information that is saved to your locations - information related to the Address Validation Quality Level and the presence of Multiple Matches during the Address Validation process are now saved to the location.

Quality Level

The Oracle Map Cloud Service Quality Level values (match codes) available are : 0, 1, 2, 3, 4, 10 , 11, 12 - explanation below. The value of 4 (default) indicates that only the input fields postal code and city name are matched. Higher Quality Level values indicate lesser accuracy, except 0, which indicates no match, whereas 1 indicates an exact match.

The Oracle Map Cloud Service Quality Level values (match codes) indicate, for each result provided, how good the result matches to the original query. 

  • 12 - The region is matched, but the postal code and city name are not matched.
  • 11 - The postal code is matched, but the city name is not matched.
  • 10 - The city name is matched, but the postal code is not matched.
  • 4 - The postal code and city name are matched, but the street address is not matched.
  • 3 - The city name, postal code and street base name are matched, but the house number is not matched.
  • 2 - The city name, postal code, street base name and house number are matched, but the street type, suffix or prefix is not matched.
  • 1 - An exact match: city name, postal code, street base name, street type/suffix/prefix and house number are matched.
  • 0 - If there was no match.

In the examples below (where the correct address is: 191 Park Dr Boston MA 02215), it's clear that the Quality Level score provided by Oracle Map Cloud Service is dependent on the presence and the correctness of the various address tokens (e.g., house number; prefix direction, prefix type, street name; street type, city, province code, postal code) provided. Depending on the quality of the information provided for an address, the Quality Level value can be an excellent guide for selecting the correct match, while in other situations, where there is missing or incorrect address information, the Quality Level value can be a less useful guide.

In the example below - the Quality Level value is 1- meaning that all the address tokens match - a perfect match, and in this example there is just one match.  For this case, the Quality Level value is an excellent indicator for the quality of the match.

Correct Address Perfect Match Quality Level - 1

In the example below, the address has been altered a bit, the Street Type has been removed altogether.  In this case, there are now Multiple Matches and the Quality Level value provided is the same for each of the matches (2) - in this case the Quality Level value provides limited/no real guidance for selecting the best match.  The point here is that the Quality Level can be useful as a guide, but in situations with Multiple Matches, the Quality Level is not a fool proof approach for selecting the best/right match.  

No Street Type - Multiple Matches - All Same Quality Level - 2

Location Address Validation Fields Added

As part of this feature, the Address Validation information stored on a location has been extended to include the following details:

  • The External Engine used for Validation
  • The Quality Level value of the match provided by the engine used
  • A Multiple Matches indicator to indicate if the match was a single match or if there where multiple match options identified for the address provided.

Additional Address Validation Information on Location

Turn Off Postal Code Latitude/Longitude Lookup

This feature also provides you with the option of turning off the usage of the Postal Code Latitude/Longitude power data table (the GEO_POSTAL_POINT table) for geocoding your locations - turning this logic off will allow you to configure your Address Validation and Geocoding process to use  Oracle Map Cloud Service as the source for your location's address validation and latitude/longitude values.

To turn off the Postal Point lookup - you will set need to set the property - glog.ExternalDistanceEngine.Geocode.UseGeoPostalPointData - to false - the default value is true/to use the Postal Point lookup.

NOTE: Only the DBA.ADMIN user can access and use the Property Sets page.

Property

Set Quality Level Threshold

To set the Quality Level/Matchcode Threshold value, navigate to Shipment Management > Power Data > Geography > External Distance Engine and select the current External Distance Engine setup for Oracle Map Cloud Service - or create a new one. In the example below, the Quality Level/Matchcode Threshold value has been set to 3 - the city name, postal code and street base name are matched, but the house number is not matched..

Quality Level Threshold Value

The addition of the geocoding quality factor, for implementations that depend on accurate street level geocoding, will ensure that locations will only be updated with latitude/longitude values that satisfy the required level of match accuracy and precision.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

When using Oracle Map Cloud Service to validate a location, OTM uses both the match_code and match_vector attributes that are returned with the match to determine if the response is a valid response or not.  The evaluation of both the match_code and match_vector can lead to situations where there are matches provided by Oracle Map Cloud Service that do not pass OTM's match_vector validation and when this happens, no matches are displayed, and the fields 'Valid Address' and 'Multiple Matches' are set to 'N'. 

The evaluation of the match_vector is handled in the following manner.

 Each position in the match_vector string represents an address field, and the numeric value to which these positions are set can vary from 0–4 (see table below). This value indicates what the Oracle Map Cloud Service did with that address field.  Inside OTM the match_vector values returned are validated  - values <= 1 mean that the input value for the address field matches with the returned value.

For example - given a returned match_vector response of  "???12101010??004?" and based on the type of address validation used, OTM checks the value returned at certain specific positions in the match_vector. In this case, the numeric value at position 5 (House number) is 2, so these matches are not considered valid as they fail the check (values <= 1) and are discarded.  When this happens, there is a chance for no valid matches to be found, so no matches are displayed, and the fields 'Valid Address' and 'Multiple Matches' are set to 'N'.

Value

Description

0

The input attribute is not null and is matched with a non-null value.

1

The input attribute is null and is matched with a null value.

2

The input attribute is not null and is replaced by a different non-null value.

3

The input attribute is not null and is replaced by a null value.

4

The input attribute is null and is replaced by a non-null value.

Key Resources

For more information about the Oracle Map Cloud Service and geocoding use the links below: 

  • http://maps.oracle.com/geocoder/ 

Property to Turnoff Postal Point Lookup

This feature provides you with the option of turning off the usage of the Postal Code Latitude/Longitude power data table (the GEO_POSTAL_POINT table) for geocoding your locations. Turning this logic off will allow you to configure your Address Validation and Geocoding process to use other sources (e.g., External Distance Engines) for your location's address validation and latitude/longitude values.

To turn off the Postal Point lookup - you will set need to set the property - glog.ExternalDistanceEngine.Geocode.UseGeoPostalPointData - to false - the default value is true/to use the Postal Point lookup.

NOTE: Only the DBA.ADMIN user can access and use the Property Sets page.

Property

This feature allows you to change your Address Validation and geocoding process to use latitude/longitude lookup sources that provide more accurate latitude/longitude than the centroid values provided by the Postal Point Lookup process.

Steps to Enable

You don't need to do anything to enable this feature.

Here Technologies

Generate Rush Hour Data Using HERE Technologies Large Scale Matrix Routing v8 API - Asynchronous Call

This feature switches the processing for the HERE Technologies v8 Large Scale Matrix Routing API for Generate Rush Hour Data to an Asynchronous process. In previous versions, this call was done Synchronously.

The Asynchronous approach is the correct approach for generating the (typically) thousands of Rush Hour records that are created when the Generate Rush Hour Data process is run. In the example below, the Rush Hour Generation is being run for a five day period - Monday to Friday covering the time from 7:00 AM to 10:00 AM every day (defined in the Calendar M-F 7AM-10A) for the Source and Destination Location Profiles (NW-CO, VIT-PAX)  - with only two (2) locations per profile  Even with this very simple setup, the Generate Rush Hour Data process will generate 240 Rush Hour records. That breaks out as follows.  The rush hour generation process will cover three hours per day - which represents twelve (12) fifteen (15) minute time increments (15 minutes is the offset used in the Generate Rush Hour Data process) that will need to be generated for each of the pairwise location combinations  - in this case that is only four combinations for profiles defined.   The process will generate 48 rush hour records per day for 5 days = 240 records.

The process actually generates those 240 records by generating all the records without rush hour being considered and then the process generates the records with rush hour calculated and then the rush hour delay is saved  for each lane with its related calendar.

Example Setup

 Below is an example of one of the generated records for Monday 9:00 AM to 9:15 AM the Rush Hour Delay for the lane assigned between 9:00 AM and 9:15 AM is 17 Minutes.

Same Rush Hour Record

The Asynchronous option for calling the Here Technologies v8 API provides performance improvements.

Steps to Enable

To take advantage of the new Asynchronous option - you will need to set the property glog.business.HereRoutingBatch.isAsyncMatrixCall  to true.

If you have not already - you will need to reconfigure your Generate Rush Hour Data process to use the new v8 API and the new required OAuth 2.0 authentication and authorization approach.  This change will involve setting up a new External System for your HERE External Distance Engine to use the proper end point and to setup the OAuth 2.0 authorization.  A sample External System Setup - HERE_ROUTING_MATRIX_SAMPLE_ES -  has been provided to guide your configuration.  See Below.

Sample External System

  You will need to contact your existing HERE Technologies account team for your required OAuth 2.0 credentials. 

Tips And Considerations

  • HERE Technologies requests that all customers on older versions of their Location Services move to the newer versions as soon as possible to take advantage of their new API framework and their supported authentication methods - in this case OAuth 2.0.  If you have any questions or concerns about this move - please contact your existing HERE Technologies account team.
  • The option to run this process Synchronously - available in previous releases - will be deprecated in a future release.   The Generate Rush Hour Data process should be run Asynchronous.

Key Resources

Please refer to On-line Help "Integrating with HERE Engine" for information on

  • Setting up your External System
  • Setting up your External Engine(s)
  • Authentication
  • Obtaining API Key or OAuth 2.0 Credentials

Contact your existing HERE account team for information regarding your required credentials.

HERE Technologies Map - Location Clustering

This feature - provide you (those using HERE Technologies as the Enhanced Workbench Map vendor) with the option of mapping locations on the HERE map in a clustering view vs mapping locations individually based on the location's latitude longitude coordinates..  You will find this option particularly helpful in uncluttering your map display when you map many locations on your map.  You may also find the clustering helpful in identifying locations that - based on HERE Technologies clustering algorithm, are close together.

In the example below, Enable Cluster has been used to show a clustered view for all the airport locations globally.  There are two primary controls for the Clustering - Maximum Radius - which allows you to control the clustering radius for gathering locations into a cluster and Minimum Points - which sets the minimum number of locations to be considered a cluster.

HERE Technologies Location Clustering

HERE Technologies Enable Clustering Map View

The Maximum Radius allows you to adjust the size of the clustering radius.  In the example below, the Maximum Radius has been doubled to 64 - yielding a less cluttered display with fewer clusters with each cluster containing more locations.

Maximum Radius Increased

As you zoom into the map, the clusters disperse until the Minimum Points (set to 2 in this case) are no longer satisfied and the individual locations are plotted.

Zoom 1

Zoom 2

At the zoom level below, the Minimum Points setting starts to come into play - note that many of the clusters are at the minimum.

Zoom 3

Provides you with a clustering view to your locations.  This clustering could help guide your region settings for planning purposes.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The Enable Clustering mapping feature is currently only available for HERE Technologies maps.

Here Technologies v8 Mandatory Upgrade

Mandatory HERE Routing API v8 Upgrade for Enhanced Workbench Mapping

This feature provides you with the ability to configure your usage of the Enhanced Workbench for mapping (using HERE) to HERE's required/mandatory HERE Routing API v8. The migration to the required/mandatory HERE Routing API v8 should be done to cover all of your Enhanced Workbench mapping usage - including the mapping of Shipments, Order Releases, Order Movements and Network.

Shipment Mapping

For your Shipment mapping - the mapping configuration is based on the External Distance Engine configured for the Rate Offering Rate Distance used to plan the shipment.  The ability to setup and use HERE Routing API v8 was provided previously in the 21A release.  If you have already upgraded your External Distance Engine to use the required HERE Routing API v8, then your Shipment mapping with the Enhanced Workbench will use the updated v8 configuration.  You will want to confirm that your Rate Distance External Distance Engine(s) are configure with he External Engine Type of HERE_ROUTING.

If you have not changed your HERE External Distance Engine configuration to use the required HERE Routing API v8 - then you should follow the detailed instructions provided under the Integrating with HERE Engine to ensure that both your Authentication setup and version setup (under HERE Routing) are meeting HERE Technologies' mandatory requirements.

Order Releases, Order Movements and Network

For all other Enhanced Workbench mapping usage  - Order Releases, Order Movements and Network  - when street level mapping is used - you will want to set the property here.useLatestApi= true to use the required HERE Routing API v8 in 23A.

  

This feature provides you with the ability to insure (and configure - if necessary) your mapping usage of the Enhanced Workbench with the latest/required HERE Routing API v8.  

Steps to Enable

If you have not changed your HERE External Distance Engine configuration to use the required HERE Routing API v8 - then you should follow the detailed instructions provided under the Integrating with HERE Engine to ensure that both your Authentication setup and version setup (under HERE Routing) are meeting HERE Technologies' mandatory requirements.

Tips And Considerations

HERE Technologies requests that all customers using older versions move to the HERE Routing API v8 as soon as possible.  HERE Technologies plans for the current Routing v7 API are to maintain this version 1 April 2023, all existing partners and customers are encouraged to upgrade no later than 31 March 2023.

If you have any questions or concerns - please contact your existing HERE Technologies account team.

Transportation Operational Planning

Logistics Guide Template - Equipment Reference Unit (ERU) for Planning Templates

This feature extends the Logistics Guide Template metrics supported to include Equipment Reference Unit (ERU).  The new Equipment Reference Unit metric is available where your Template Type = Planning.  With this addition, you now have the option of configuring your Logistics Guide Template for Planning using either Weight or Volume or a Number of Equipment Reference Units (ERUS).  You will find the ERU metric particularly useful in areas where equipment capacity and transportation pricing are based on ERUs - for example - equipment capacity and pricing that are based on pallet spaces.

Logistics Guide Template - Equipment Reference Units

In the example below - the routing decision changes based on the number of Large Pallets/ERUs that need to be routed.  In this example/setup - scenarios that involve <= 30 Large Pallets will be routed via the cross dock - with a total cost <= 2,000 USD.  Scenarios involving more the 30 Large Pallets/ERUs will go direct at a cost of 2,000 USD. 

Scenario Example

The Logistic Template for this example is below.  The Logistics Template in this case provides calculations for 1 to 33 Large Pallet Equipment Reference Units.

Logistics Guide Template - Equipment Reference Units

The Rate Unit Break setup is below - 20 USD per additional Large Pallet.

Rate Unit Break

This feature allows Network Routing to consider routing decisions considering Equipment Reference Unit metrics and costing.  You will find this feature particularly beneficial in network routing decisions where there is an opportunity to go direct or to go via a cross dock and the costing for the two routing options is based on pallet spaces (modelled as ERUs) for both the capacity of the equipment and the rates that apply..

Steps to Enable

To take advantage of this new feature you will need to modify and/or create a new Logistics Guide Template that includes the correct setup for modeling routing decisions based on Equipment Reference Units.

You can get to your Logistics Guide Template navigating to Contract and Rate Management > Logistics Guide > Logistics Guide Template.

  • Select Planning from the Template Type list box. The Planning will generate cost information that will be used to guide planning.
  • Enter the Equipment Reference Unit ID field in the page header.

  • Enter  Number of Equipment Reference Units (ERU) in the corresponding field.
    • The planning parameter CHECK EQUIPMENT CAPACITY IN REFERENCE UNITS should be set to true, when ERUs are used as a quantity break to generate cost options for particular lanes.

Network Routing with Location Calendar

This feature enhances the Routing logic used in Network Routing to consider location calendars when evaluating the different routing options to consider within a defined network. 

In the example below, given an order that has a late pickup date/day of Monday and a late delivery date/day of Thursday.  The least expensive option, DC1->Xdock A->Dest 2 would be the best option from a cost perspective and would be feasible if location calendars were not considered, however, when Xdock A's location calendar is considered, this option - while the cheapest at 900 USD, is not feasible. The best routing option, considering the involved location calendars, is DC1->Xdock B-> Dest 2 for 1,150 USD.  This option will feasibly deliver the order by Thursday given the 3 day transit involved and considering the location calendars. 

Location Calendars Considered In Network Routing

This feature improves the routing solutions provided by OTM's Network Routing planning in networks that involve locations with tight/restrictive activity calendars.

Steps to Enable

To take advantage of this new planning feature you need to set the Network Routing Logic Configuration parameter CONSIDER LOCATION CALENDARS IN ROUTE SELECTION to TRUE. 

This parameter is used to enable the new logic that considers location calendars in network routing. When this is set to true, feasible routes are found for an order by taking into account the calendars defined at all locations along the route. By default the parameter is set to false.

CONSIDER LOCATION CALENDARS IN ROUTE SELECTION

Tips And Considerations

Note: In the example below - without considering the location calendars in the routing decisions made by Network Routing, OTM would generate order movements choosing the least expensive feasible (not considering location calendars) path of DC1->Xdock A->Dest 2.  Then - in the next step within Network Routing  - where the order movements are planned onto shipments - the solution would be found to be infeasible due to the location calendar at Xdock A - which is closed on Tuesday, the result would be that the order and order movements would be left unscheduled.

Without Location Calendars Considered

Use Consol Flag Added to Network Leg

This feature adds the Use Consol check box to the Network Leg.  The Use Consol check box allows you to indicate the network leg(s) that can be used as a candidates for building a consol shipments. The Use Consol check box has been added to both the edit and view managers for the Network Leg.  The Use Consol check box is considered in two actions - Bulk Plan - Buy and Show Network Routing Options - the flag is not considered in any other actions.

Use Consol  Check Box - Network Leg - Edit

Use Consol - Network Leg View

You will find this feature extremely beneficial in situations where you need to control which network legs are and are not candidates for building consol shipments.

Steps to Enable

You don't need to do anything to enable this feature.

Work Assignments

Convert Multi Segment Shipment to Single Petal Shipments

This feature extends the Convert Multi-segment to Multiple Shipments logic provided previously, to allow you to split your multi-segment shipments by shipment petal - where a petal segment starts at a location, goes empty, and then returns to the starting location - a round trip segment.  This new capability extends the opportunities to combine the robust multi-stop multi-segment planning capabilities of OTM with the resource scheduling capabilities provided with the Work Assignment planning logic. 

When configured, the new logic allows the multi-stop logic to create groups of single-segment shipments that can fit nicely together in work assignments. The Convert Multi-segment logic extends the capabilities of the algorithms used to create multi-segment shipment by breaking each of the generated multi-segment shipments into its individual segments, each of which are then  persisted as a single-segment shipment. As part of the processing, each of the single-segment shipments created from the same multi-segment shipment is marked with the same Projected Tour Name, with a Projected Tour Sequence Number based upon its position in the original multi-segment shipment. You can use the Work Assignment logic to put the single-segment shipments into the same work assignment - you will need to turn on the  Resource Scheduler logic parameter RS USE PROJECTED TOUR to honor the specified Projected Tour information.

As illustrated below, this new capability allows you to take advantage of the multi-stop/multi-segment planning capabilities provided by bulk planning to develop good single candidate shipments (in this case, petal shaped shipments) for Work Assignment planning to string together to create a full day of work for a resource.

Multi-Stop Multi-Segment and Work Assignment Flow

To use this new functionality, you will need to set the MULTISTOP Logic Configuration parameter CONVERT MULTI SEGMENT TO MULTI SHIPMENT to Convert to Single Petal Shipments.  You will also need to set the MULTISTOP SEQUENCING parameter MULTISTOP MAXIMUM SEGMENTS PER SHIPMENT to a value greater than 1 to generate multi-segment shipments. 

New Multistop Logic Configuration Parameter - Convert Multi Segment to Multi Shipments

With the parameter CONVERT MULTI SEGMENT TO MULTI SHIPMENT set to Convert to Single Petal Shipments, the multi-stop logic will now look to convert the petal segments contained in your multi-segment shipments into individual petal shipments.  In the example below, the multi-stop multi-segment shipment consists of two petal shaped segments.  The first petal from stop 0 to stop 5 - the starting and ending location is MX-14109 NY 14109 which in this example is both the pickup location and the domicile.  Highlighted below (in orange) the first segment starts with a pickup at MX-14109 NY 14109 and then makes four deliveries and then returns empty back to MX-14109 NY 14109.  The second segments starts with another pickup at MX-14109 NY 14109 then makes five additional deliveries and then returns (empty) back to MX-14109 NY 14109.

Multi-Stop Multi-Segment Shipment - Two Petal Segments

With the parameter CONVERT MULTI SEGMENT TO MULTI SHIPMENT set to Convert to Single Petal Shipments, the twelve stop multi-segment multi-stop shipment will be converted into two individual petal shipments.

Converted Multi-segment Shipment Petal 1

Converted Multi-Segment Shipment Petal 2

As was the case with the he individual segment shipments, the petal shaped shipments are also updated with a Projected Tour Name and Projected Tour Sequence Number - this information will be used by the Work Assignment Logic to keep this set of shipments together (if possible) within a single Resource Schedule Instance.  The Projected Tour Sequence Number will be used to guide the sequencing of the shipment within the Work Assignment.

To have the Work Assignment logic consider the assigned Project Tour Name and Project Tour Sequence Number you need to set the Work Assignment parameter RS USE PROJECTED TOUR  to true to consider the projected tours.  When the RS USE PROJECTED TOUR parameter is set to true, the work assignment building process will start by stringing together any shipment which has a common projected tour name into one string. The initial sequence of these shipments in the string will be determined by the projected tour sequence number associated with each shipment. The parameter is found in the Resource Scheduler Logic Configuration - in the Resource Scheduler Consolidation section.

Projected Tour Name and Sequence

User Project Tour and Sequence Parameter

In the example above, the (single) home location MX-14109 NY 14109 was considered as the source for a petal.  The new logic also supports the definition of a location profile for defining a set of possible home locations (defined as a Location Profile) to consider for your petals. Each of these locations in the Location Profile act as potential home locations while creating the petal shipments. You will find this additional feature beneficial in situations where you have multiple "home" facilities delivering to a set of customers in a small city, in this case you may want to consider the shipment petals that start at any of your "home" locations as candidates for defining a petal.

In the example below - Location A, Location B and Location C all represent opportunities for being a petal shipment's home/source.  To support this option, a Location Profile is defined and assigned to the parameter PETAL SOURCE LOCATION PROFILE, as shown below. In this example - the petal logic will consider all three locations as potential source/home locations - for the multi-segment, multi-stop shipment below will be split into two petal shipments - Location  A to Location B (petal 1) and Location B to Location C (petal 2).

Scenario - Location A, Location B, Location C - All Valid Petal Sources

Location ABC profile definition is below.

Location Profile LOCATIONABC

Petal Source Location Profile assigned to PETAL SOURCE LOCATION PROFILE parameter.

Location Profile LOCATIONABC Assigned to Parameter

This feature extends OTM's available multi-stop and tour building planning capabilities, when applied to the right use case and scenario, the new capabilities will provide you with improved solution quality and additional cost savings.

Steps to Enable

To take advantage of this feature you must be planning with multi-segments, the Convert to Single Petal Shipments parameter must be on/converting and you should be using Resource Schedules and Work Assignment planning logic. 

Tips And Considerations

The sequence of stops in the petal shipment will be maintained to ensure that the petal shipments are more meaningful.

Note that for a specified Projected Tour Name  - the Work Assignment logic requires an all or nothing solution i.e., either all the shipments for the same Projected Tour Name are assigned or none will be assigned. 

Each of the individual segment shipments will be re-driven after they are split - start times, rates, equipment etc. could change as part of this process.

If you are using Capacity Limits - each of the individual segments shipments may require capacity - so the single multi-stop multi-segment shipment could have only consumed one available resource - if the multi-segment shipment is split into three shipments - each of those shipments could now require capacity.  

Note that for the single petal shipments created with the new logic:

  • each corresponds to a segment from what was originally a multi-segment shipment
  • each has a corresponding Projected Tour ID and Projected Tour Sequence Number
  • each has its own depot stops (if applicable)
  • each is driven without regard to the others  (they are not driven as they would have been as part of multi-segment shipment)

The Projected Tour Name and Projected Tour Sequence Number is an editable field on the Shipment. You can enter a Projected Tour Name and a Projected Tour Sequence Number to a set of shipments, manually, if you already know the set of shipments you would like to see in a Work Assignment and the sequence of those shipments.  Again - the set of shipments and the sequence specified must not overload the Resource Schedule Instance.

Shipments that would have been single-segment shipments to begin with are not affected.

Resource Scheduler Sequencing Option - Current Start Time Ascending

This feature provides you with a new Resource Scheduler Sequencing Option - Current Start time Ascending - which will consider your shipment's current start time when setting up the process for assigning shipments to available resource schedule instances.  You will find this feature beneficial in any scenario where your assignment of shipments to available resource schedules should consider the current start time of the shipment which includes consideration for location calendars and other timing related requirements.

New Resource Scheduler Sequence Option - Current Start Time Ascending

In addition to the new option - Current start time ascending - this feature also renamed the previously available sort option - Start time ascending-  to the new name - Earliest start time ascending.  This change was done to help clarify the usage of the two parameter values - Current start time ascending and Earliest start time ascending. Earliest start time ascending" will choose the shipment with the earliest possible start time,  not their current start time as the shipment around which to build a work assignment.

Renamed Resource Scheduler Sequence Option - Earliest Start Time Ascending

In the example below.  The Shipment Current start time (Start Time) is November 24th at 9:00 AM - this time considers location calendars etc. The Earliest Start Time - is based on the Early Pickup Time of the order release(s) on the shipment  - in this case November 24th at 8:00 AM.

Current Start Time (Start Time) v Earliest Start Time

This feature will improve solution quality the assignment of shipments to available resource schedule instances in situations where the currently schedule timing for the shipment is an important assignment element. 

Steps to Enable

To take advantage of this feature - you will need to set the Resource Scheduler Sequencing option to the new option - Current start time ascending.

Tips And Considerations

The RS SEQUENTIAL SAVINGS SORT METHOD parameter allows you to choose which method to use in determining the first shipment from which to build your work assignment. You can guide the algorithm to build work assignments that are more likely to contain the types of shipments desired by the resources associated with the work assignments. The valid values are:

"0. None" is the default. With this option, the first shipment to merge is chosen based on an internally generated ID, essentially random.

"1. Earliest start time ascending" will choose the shipment with the earliest possible start time,  not their current start time as the shipment around which to build a work assignment. 

"2. Weight descending" will choose the shipment with the heaviest weight as the shipment around which to build a work assignment. 

"3. Duration descending" will choose the shipment with the longest duration as the shipment around which to build a work assignment.

"4. Cost descending" will choose the shipment with the highest cost as the shipment around which to build a work assignment.

"5. Savings descending" will choose the shipment pair which offers the most savings as the shipments around which to build a work assignment.

"6. Current start time ascending" will sort shipments by their start times to determine which shipment to first consider for merges with other shipments, and assignment to resource schedules.

Service Provider Assignment

Service Provider Assignment - Shipment Preference Criteria - Consider Utilization Options

This feature provides you with some additional criteria for guiding how the Service Provider Assignment logic handles the assignment of shipments to service providers in scenarios where Capacity Limits come into play.  By default the Service Provider Assignment logic attempts to minimize cost in the Service Provider Assignment decision - with this feature you can select one of the following criteria to guide the Service Provider Assignment decision  - either Shipment Priority (available previously) or Shipment Utilization criteria measured by Weight or Volume or ERUs. 

Service Provider Assignment - Shipment Preference Criteria Parameter

The available options for the Shipment Preference Criteria parameter are:

0. None: No preference criteria is used for shipments.

1. Priority: A shipment with a higher priority will be preferred over a shipment with lower priority.

Previously you would consider priority in Service Provider Assignment by setting USE PRIORITY IN SPA = true.  With the new Shipment Preference Criteria parameter, one of the preferences below is selected - weight/volume/ERU - the Service Provider Assignment logic will use that criteria effectively ignoring/overriding the USER PRIORITY IN SPA = true setup.

2. Total weight: A shipment with a higher total weight will be preferred over a shipment with lower total weight.

3. Total volume: A shipment with a higher total volume will be preferred over a shipment with lower total volume.

4. Total ERU: A shipment with a higher total ERU count will be preferred over a shipment with lower total ERU count.

This feature extends the Service Provider Assignment logic to include the option to consider equipment utilization (measured by weight, volume or ERUs) when determining which shipment is the more important shipment to be assigned to a limited set of available equipment resources.

Steps to Enable

To take advantage of this new capability and behavior related to the consideration of utilization in the assignment logic, the Service Provider Assignment Shipment Preference Criteria parameter should be configured to one of the  options listed below:

  • Total weight: A shipment with a higher total weight will be preferred over a shipment with lower total weight.
  • Total volume: A shipment with a higher total volume will be preferred over a shipment with lower total volume.
  • Total ERU: A shipment with a higher total ERU count will be preferred over a shipment with lower total ERU count.

Tips And Considerations

This parameter provides an option for the user to select a rule by which one shipment will be preferred over another in the Service Provider Assignment Optimization logic, when there are limited resources (i.e. due to Capacity Limits). These new rules apply only when the parameter PLAN SHIPMENTS WITH CARRIER COMMITMENT is turned on.

The default option is set to None. When SHIPMENT PREFERENCE CRITERIA is "0. None", and USE PRIORITY IN SPA is set to true, SHIPMENT PREFERENCE CRITERIA will be internally forced to "1. Priority". In all other cases, the parameter setting for SHIPMENT PREFERENCE CRITERIA takes precedence over USE PRIORITY IN SPA.

3D

Gross Center of Gravity - Calculate and Persist on Shipment Equipment

This feature provides you will visibility to your Shipment Equipment Empty Center of Gravity (CoG), Freight Center of Gravity and Gross Center of Gravity.

Below is the Edit Load Config UI showing the Center of Gravity fields that are now populated within the bulk plan automatically

Center of Gravity

The Shipment Equipment fields (shown below) are populated as follows:

  • The logic populates the Empty CoG Floor Height and Tare Weight from the equipment group - if they exists.
  • The Freight and Gross CoG values are automatically calculated and persisted to the S_Equipment if 3D based load config is used.
  • Gross CoG values are populated only if the Empty CoG Values exist on the equipment group.  If the Gross CoG values do not exist on the equipment group then the Gross CoG values calculation will be skipped.
  • If Tare Weight is not defined on the equipment group, then the value is considered to be 0 and the values for the Freight CoG and Gross CoG will be equal.

Shipment Equipment Center of Gravity Fields

This feature provides you with more insight into the Center of Gravity value calculations done as part of a Bulk Plan.

Steps to Enable

You don't need to do anything to enable this feature.

Transportation Sourcing

Enhanced Build Lane Summary with Volume Target Action

This Transportation Sourcing feature provides you with enhanced logic for the Build Lane Summary With Volume Target action.  The Build Lane Summary With Volume Target action will now evaluate each the lanes in the assigned Geo Hierarchy Profile, for each lane, where the volume of shipments meets the specified Volume Target, a new lane will be generated. 

In the example below, each of the Geo Hierarchy lanes defined in the DVML Geo Hierarchy Profile ID will be evaluated - a new lane will be created when the number of shipments evaluated meets the entered Volume Target of 13.

Build Lane Summary With Volume Target

Given the shipment data below - lanes and counts.  The Build Lane Summary With Volume Target action will generate nine lanes. 

Input Shipment Data

The results are below - nine Lanes are created based on the Build Lane Summary With Volume Target action criteria defined above.

Lane Summary Results

With the same data, but with the Volume Target set to 20 versus 13 running the Build Lane Summary With Volume Target against the same set of data yields six (6) lanes.  In this case, the City to City Geo Hierarchy does not get used since no City to City combinations satisfy the entered Volume Target of 20.

Build Lane Summary With Volume Target 20

Volume Target = 20 Lanes Generated

For the same set of data- running the Build Lane Summary action results in only two lanes being generated.

Build Lane Summary Action

Build Lane Summary Results

Automates the generation of lane summary data at the more detailed level lane level geography, allowing for the sourcing bid to be generated and communicated to the Service Providers at the most detailed level where there is sufficient volume of shipment activity.

Steps to Enable

You don't need to do anything to enable this feature.

Freight Payment, Billing, and Claims

Aggregated Shipment Cost Lines

This feature is designed to handle the case where a single invoice line needs to match and tolerate to multiple shipment cost lines. For example, this feature handles the situation where there is one accessorial code and charge for a handling fee provided on the invoice and that one handling charge is represented in OTM as three separate shipment cost lines, this feature provides the ability to aggregate, match and tolerate the three shipment cost lines to the one invoice line.

To demonstrate this new capability - the autopay/create invoice scenario below will be used.  In this example, the shipment cost lines have been aggregated on the generated Invoice based on the Line Aggregation Constraint Set linked to the Invoice/Bill Rule that was used to create the invoice.  In this example, the three Base shipment cost (100.00 USD, 4.00 USD, 100.00 USD) have been aggregated into one invoice line cost of 204.00 USD and the two accessorial costs for INS (10.00 USD and 40.00 USD) have been aggregated into a single invoice line for 50.00 USD. 

Shipment Cost

The generated invoice/invoice lines are below. The aggregated Base cost (204.00 USD) and the aggregated Accessorial (INS) cost (50.00 USD) are highlighted.  This invoice has also been processed by the new action - Approve Invoice Preprocess - as indicated by the Preprocess Status (MATCHED_IN_TOLERANCE). 

Aggregated Invoice Line

The Line Aggregation Constraint Set linked to the Invoice/Bill Rule used to drive the aggregation is below.  In this example, the aggregation is done by Cost Type  - Base and then by Accessorial for the INS Accessorial Code. 

Constraint Set

In the example below, the aggregation is done for a Shipment Group. In this case the Shipment Group contains two shipments and one secondary charge shipment - the total cost is 2,959.00 USD.

Shipment Group Two Shipments One Secondary Charge Shipment

The sixteen Shipment Cost records for the three shipments in the Shipment Group are listed below.

Shipment Cost

Below are the aggregated invoice lines for the sixteen Shipment Costs in the Shipment Group based. In this example, the Base costs (100.00 USD, 4.00 USD, 100.00 USD ,100.00 USD ,225.00 USD, 2,000 USD) have been aggregated into one Base cost of 2529.00 USD, and the three Accessorial INS costs (40.00 USD, 10.00 USD, 90.00 USD) have been aggregated into one INS Accessorial cost of 140.00 USD, and the three THC Accessorial costs (40.00 USD, 10.00 USD, 90.00 USD) have been aggregated into one THC Accessorial cost of 140.00 USD.

Invoice Lines Aggregated

Below, for comparison - are the original sixteen Shipment Costs for the Shipment Group (three shipments) grouped by the Cost Type and Accessorial Codes.

Shipment Cost Aggregated

The Line Aggregation Constraint Set linked to the Invoice/Bill Rule used to drive the aggregation is below.  The aggregation is done by Cost Type  - Base and then by Accessorial for the INS and THC Accessorial Codes.

Line Aggregation Constraint Set

Invoice Action  - Approve Invoice Preprocess

The new Invoice action - Approve Invoice Preprocess  - when run against an autopay generated invoice will redo the existing invoice lines to shipment cost mapping and aggregation and then will check the tolerance based on the line approval tolerance rule. The matched shipment cost details will be stored, and the tolerance deviation details and the Preprocess Status field on the invoice line will be updated.

In the example below, an invoice will be created for a shipment with the shipment cost as shown.  In this example, the shipment cost include four Base costs and three Accessorial cost for INS Accessorial Code.  The same Line Aggregation Constraint Set and same Invoice/Bill Rule used in the above examples will be used in this example - so the aggregation will be for the Base cost and the Accessorial Code of INS. 

Shipment Cost Lines

The first step in the process is to run the Create Invoice action against the shipment.

Create Invoice

As noted, the same Aggregate Lines Bill Rule and Line Aggregation Constraint Set will be used in this example.

Bill Rule Used

The created invoice is below. As expected the Base cost and the Accessorial INS Cost are aggregated. After running Create Invoice, the Preprocess Status is Matched - meaning that the shipment cost lines (aggregated), and the invoice lines have been matched.

Created Invoice

 Running the action Approve Invoice Preprocess against the invoice will redo the matching, the aggregation and also check the line approval tolerance rule.  

Approve Invoice Preprocess

After running the Approve Invoice Preprocess the Process Status is now set to MATCH_IN_TOLERANCE for all of the aggregated invoice lines.

Approve Invoice Preprocess action - Updated Preprocess Status

The Approve Invoice Preprocess action operates similarly for both created invoices as well match and pay/externally provided invoices.  In both cases the Approve Invoice Preprocess action will:

  • map the invoice lines to shipment costs,
  • check the tolerance based on the line approval tolerance rule,
  • store the matched shipment cost details,
  • store the tolerance deviation details,
  • update the Preprocess Status field on the invoice line.

This feature simplifies the settlement process of matching and tolerating invoice line entries and shipment costs when those costs are provided at different levels of aggregation. 

Steps to Enable

To take advantage of the new aggregation capabilities you will need to create and/or modify an existing Invoice/Bill Rule to include Line Aggregation Constraint Set details.

Tips And Considerations

The Optional Feature, ENABLE IMPROVED INVOICE APPROVAL LOGIC, should be Opted In to use this feature.

Inv Line Appr-Stop At First Passed Det and Rule

This Optional Feature, when enabled, will provide the following processing -  the invoice line approval will look up the line tolerance rule detail from specific to general order. The tolerance check will stop after the first pass.

This feature improves the look up tolerance logic.

Steps to Enable

You don't need to do anything to enable this feature.

Enable Improved Invoice Approval Logic

This Optional Feature, when enabled, will use the improved invoice approval logic for your invoice approvals.  The improved invoice approval logic allows invoices to be approved based on the invoice line status. In addition, the improved approval logic provides invoice approvals based on aggregation definition and shipment cost reference.

This feature provides enhanced invoice approval features and usability.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

This Optional Feature is dependent on another Optional Feature - Feature ID INVOICE PAYMENT - SAVE SHIPMENT COST AS REFERENCE

Shipment Cost Associated to Order Release and Stop

This feature allows you to, when manually entering a Shipment Cost, to associate the entered cost to either a specific Shipment Stop, an Order Release, or an Order Release Line - available previously.

The association of the Shipment Cost is managed within the Shipment Cost Reference section of the Shipment Cost Screen  - Shipment Management > Shipment Manager > Buy Shipments select the Financials tab. 

As shown below, the available Shipment Cost Qualifiers now support, in addition to Order Release Line, Order Release and Shipment Stop.

Shipment Cost Reference Section

Below are some  examples for how to associate your entered Shipment Cost to an Order Release Line, Order Release and Shipment Stop.

Order Release Line Cost Reference

Order Release Cost Reference

Shipment Stop Cost Reference

This feature provides an easy way for you to associate your Shipment Cost to a specific Order Release Line, Order Release or Shipment Stop.

Steps to Enable

You don't need to do anything to enable this feature.

Transportation Intelligence

Data Visualization - Transportation Operational Intelligence Subject Area

This feature provides you with a new Data Visualization (DV) subject area - Transportation Operational Intelligence.  The Transportation Operational Intelligence subject area contains three new subject area folders: 

  1. Shipment Operational Analysis,
  2. Order Release Operational Analysis,
  3. Invoice Operational Analysis. 

The Transportation Operational Intelligence subject area provides you with the opportunity to use data visualization reporting tools against your operational data. 

Transportation Operational Intelligence Subject Area

Transportation Operational Intelligence Subject Area Folders

With the Data Visualization - Transportation Operational Intelligence Subject Area - you can use the provided subject area folders to quickly generate graphical reports with you operational data. For example, in the report below, the monthly transportation spend by service provider is provided.

Shipment Planned Cost By Mode  - Shipment Operational Analysis

.

Order Release By Location - Order Release Operational Analysis

Net Due by Month - Invoice Operational Analysis

Business Spotlights

When you combine the ability to develop insightful graphical reports using your operational data with the ability to embed these graphical reports into an Enhanced Workbench and then set that workbench as your Home page - the new insights available provide you with data visualizations that can be used to develop reports that provide a complete view across the business.  The steps required to implement the Business Spotlight as your Home page are available in Help under - Transportation Operational Intelligence Data Visualization/Business Spotlight.

As an example - for 23A, the Business Spotlight DV workbook (below) is available for you to embed in an Enhanced Workbench.

Business Spotlight

In the example below, an Enhanced Workbench has been created with the Transportation Operational Intelligence Business Spotlight as the Component Type and Project Path.  Then, for this user, the Business Spotlight Enhanced Workbench has been assigned to their User Preference as their Home Workbench Layout ID.  The Business Spotlight provides you with a graphical view into the Status Types and their Status Values for Status Types: Shipment – Enroute, Shipment – Secure Resources, Invoice – Approval and Order Release – Planning.

Business Spotlight

This feature provides you with the ability to generate Data Visualization reports generated from your operational data.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

As with any reporting that operates against your operational data, there is the possibility for the reporting (queries used in the reporting) to impact performance.  To avoid surprises, performance testing should be a part of your testing plans for any reports developed using the Transportation Operational Intelligence subject area.

Key Resources

You will find additional information on setting up the Business Spotlight as your Home Workbench in On-line Help in the Business Spotlight section under the Transportation Intelligence Data Visualization section.

Status Dimension Subject Area - Order Release, Shipment and Invoice

This feature extends the Subject Areas provided for the Order Release, Shipment and Invoice - to include a Status Dimensions Subject Area for the Order Release Status, Shipment Status and Invoice Status.

Order Release Status Dimensions Subject Area

Shipment Status Dimensions Subject Area

Invoice Status Dimensions Subject Area

This feature provides you with new Status Dimensions folder for the Order Release, Shipment and Invoice. The new Status Dimensions Subject Area provides both Status Type and Status Value.

Provides additional dimensions for business intelligence reporting and analysis.

Steps to Enable

You don't need to do anything to enable this feature.

Order Release Dimensions for Earliest Estimated Pickup Date, Latest Estimated Delivery Date

This feature extends the Order Release Dimensions to include the Order Release Earliest Estimated Pickup Date and Latest Estimated Delivery Date.

The Earliest Estimated Pickup Date captures the earliest departure time for all of the first leg shipments that an order release is on, the Latest Estimated Delivery Date captures the latest delivery date from the last leg shipment that order was delivered on.   

Order Release Dimensions Estimated Pickup and Delivery

  

The addition Order Release Earliest Estimated Pickup Date, Latest Estimated Delivery Date will be extremely useful in gaining insight into the typical/expected lead time required to delivery an order release.

Steps to Enable

You don't need to do anything to enable this feature.

Additional Shipment Dimension and Fact for Equipment Reference Units

This feature extends the Shipment Facts and Dimensions provided to include additional Equipment Reference Unit insight.  The Shipment Dimensions now includes the Equipment Reference Unit GID and Shipment Facts now includes the Total Number of Reference Units fact.

Shipment Dimensions - Equipment Reference Unit GID and Shipment Facts Total Number of Reference Units

Below is a report showing the Total Number of Reference Units by Equipment Reference Unit GID.

Sample Report - Total Number of Reference Units by Equipment Reference Unit GID

Again - the same report in DV form.

DV Report - Total Number of Reference Units by Equipment Reference Unit GID

The additional Shipment related Equipment Reference Unit Fact and Dimension provides you with additional insight into your Equipment Reference Unit utilization.  

Steps to Enable

You don't need to do anything to enable this feature.

Logistics Network Modeling

Extend Logistic Network Modeling to Include Work Assignment Optimization

This feature extends the Logistics Network Modeling capabilities to include Work Assignment Project and Scenario modeling simulations.  This additional modeling capability will allow you to easily evaluate the impact/benefit of different resource schedule settings (e.g., count, duration) using as input.  You can generate Work Assignment related Modeling Projects and Modeling Scenarios using either your operational OTM shipments as input or you can generate Modeling Work Assignments as part of your LNM Bulk Plan simulation runs.

The Modeling Project and Modeling Scenario setup for a Work Assignment simulation using OTM Operational shipments is demonstrated below.    

To create a Modeling Project and related Modeling Scenarios for a Work Assignment simulation using OTM shipments as input - you will start by creating a Modeling Project with a Modeling Project Type of Work Assignment.  The Modeling Project UI, by default (below), shows the Modeling Project Type of Shipment Planning - where the input to that setup is Order Releases.

Modeling Project UI - Modeling Type = Shipment Planning - Default

When you switch from the default Shipment Planning Modeling Project Type to the Work Assignment Modeling Project Type the UI changes to reflect the inputs and constraints that are appropriate for the Work Assignment Modeling Project Type.  Specifically, the query is now for OTM shipments v Order Releases and the constraints related to planning orders into shipments, like Itinerary and Itinerary Profile, are no longer available.

Work Assignment Modeling Project Type

For this example, the Modeling Project will have three Modeling Scenarios.  Each Modeling Scenario will have a Data Rule Instance with a different Resource Count.  For this example - Modeling Scenario 1 will have a Resource Count of 5, Scenario 2 will have a Resource Count of 10 and Scenario 3 will have a Resource Count of 15.  To accomplish this - the Data Rule and the Data Rule Instances will need to be created as shown below.

For any Work Assignment Modeling Type simulation - the Resource Schedule is a key modeling object.  To support Work Assignment simulations, the Resource Schedule has been added to the Data Rules.  The columns available for Data Rule/Data Rule Instance configuration are provided below.

Resource Schedule Data Rule Columns

For this example, the Data Rule Definition and Data Rule Parameter will be Count based - as shown below.  The Data Rule Instance for each Modeling Scenario will then have a different Count value set for each of the Modeling Scenarios.

Data Rule Definition

  Below are the three Data Rule Instances that will be used in the three Modeling Scenarios.

Data Rule Instance Resource Count = 5

Data Rule Instance Resource Count = 10

Data Rule Instance Resource Count = 15

The Data Rule Instances will then be assigned to each of the Modeling Scenarios for this Modeling Project.  See below.  For each Modeling Scenario, the assigned Data Rule Instance will set the Resource Count on the Resource Schedule Instances selected by the Saved Query Filter - DAILYRESOURCEINSTANCE.

Modeling Scenario 1 - Modeling Resource Count = 5

Modeling Scenario 2 - Modeling Resource Count = 10

Modeling Scenario 3 - Modeling Resource Count = 15

Once all the Modeling Scenarios are defined - the Modeling Project is complete for this simulation. For this Work Assignment Modeling Project, there are three Modeling Scenarios with varying Resource Counts.  Each scenario will all be run using the OTM operational shipments returned by the Shipment Saved Query TODAYS SHIPMENTS - the goal is to generate Work Assignments for the shipments considering the different Resource Counts. 

Modeling Project

To run the Work Assignment simulation at the Modeling Project level - select the action Scenario Work Assignment Optimization.

Scenario Work Assignment Optimization

When the Scenario Work Assignment Optimization is run at the Modeling Project level - you have the option to deselect some of the Scenarios from the optimization run. In this case all three scenarios are selected.

Option to Choose Scenarios to Include

.While the simulations are running, you have visibility to the Modeling Scenarios and the current Scenario Work Assignment Optimization state.

Running State - Submitted

Running State - Completed

Once the Work Assignment Optimization is complete - you have various tools to compare results, specifically, both the Aggregate Scenario Results and Compare Modeling Scenario Plan Results provide good summary level information. 

Analysis Options

Result Analysis - Aggregate Scenario Results

Compare Modeling Scenario Plan Result

In addition to the Aggregate Scenario Results and Compare Modeling Scenario Plan Results, you also have the option of incorporating the Modeling Work Assignments into your Logistics Network Modeling Workbench.  In the Workbench below, the Modeling Work Assignment table has been added to the Workbench and linked to the Modeling Scenario for the Modeling Project.  Using the Workbench it's easy to evaluate the Modeling Scenarios, the Work Assignments generated, and the Modeling Shipments included in each of the Modeling Work Assignments.

Work Assignment Table Added to Workbench

This feature extends the simulations provided by Logistics Network Modeling to include modeling different resource availability and resource schedules defined using Work Assignment planning logic.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Logistics Network Modeling  - Modeling Work Assignment generation.  The example above shows the approach for generating Work Assignments with Modeling Project Type = Work Assignments.  As a reminder, there are two ways to generate Modeling Work Assignments with Logistics Network Modeling.

  1. You can generate Modeling Work Assignments using the approach where the Modeling Project Type = Shipment Planning - in this setup your Bulk Plan configuration will include the typical Bulk Plan Work Assignment setup:
  • FLEET AWARE BULK PLAN parameter set to True
  • RESOURCE SCHEDULER CONFIG -  setup with
    • CREATE WORK ASSIGNMENTs to TRUE
    • GENERATE RESOURCE SCHEDULE INSTANCES set to TRUE
    • RESOURCE SCHEDULE PROFILE defined and assigned
  1. You can also create Modeling Work Assignments using OTM Shipments as input using the Scenario Work Assignment Optimization with Modeling Project Type = Work Assignment.  From a parameter configuration setup the configuration is similar to the above setup:
  • FLEET AWARE BULK PLAN  -  not considered in this approach.
  • RESOURCE SCHEDULER CONFIG -  setup with
    • CREATE WORK ASSIGNMENTs to TRUE
    • GENERATE RESOURCE SCHEDULE INSTANCES set to TRUE
    • RESOURCE SCHEDULE PROFILE defined and assigned

Logistic Network Modeling - LTL Rate Discount Data Rule Enhancement

This feature extends the Logistics Network Modeling Data Rule Definition to include the option to change the discount percentage (increase or decrease) for your LTL Rates.  Specifically, for the RATE_GEO table, the RATE_GEO_COST.CHARGE_MULTIPLIER_SCALAR column has been added so that you can now create Data Rule Definitions and Date Rule Instances that will allow you to increase or decrease the discount percentage applied to your LTL Rates.

In the example below, the Data Rule Definition is configured to allow for you to input, on a Data Rule Instance, the desire LTL Discount. 

RATE_GEO_COST.CHARGE_MULTIPLIER_SCALAR Column Added for RATE_GEO Table

Data Rule Saved

In the example below- the Date Rule will be used to create a Data Rule Instance that will increase the discount by 20%. 

Select the LTL Discount Date Rule Definition

The Data Rule Parameter input for the Data Rule Instance provides five options for the Operand - SET, INCREASE, DECREASE, INCREASE BY PERCENT, and DECREASE BY PERCENT.

Data Rule Parameter Input

In this example the setup will be to INCREASE the Discount by 20%.

Parameter Setup

Data Rule Instance Defined

When the LTL DISCOUNT INCREASE Data Rule Instance is applied, the discount on the rate will be increased by 20%.  Assuming an undiscounted cost of  300 USD and an existing 20% Discount already specified on the rate, when LTL DISCOUNT INCREASE Data Rule Instance is applied, the effective discount applied will now be 40%  - the original 20% discount increased by an additional 20% based on the rule resulting in a 40% discount against the 300 USD amount for a discounted cost of 180 USD.

The table below provides some examples for how the different Operands would be applied.

This feature simplifies the modeling steps required to vary your LTL rate discounts in your Logistic Modeling Scenarios. 

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The data rule will be applied to all possible discounts that are available on the rate records you can not specify a different discount for say the Minimum or by Weight Break.

Logistic Digital Assistant

Logistics Digital Assistant Available in Global Header

This feature provides you with the option to include access to the Logistic Digital Assistant directly from the system's Global Header.  Providing access from the Global Header allows you to take advantage of the Logistic Digital Assistant's use of artificial intelligence which provides a more conversational and human interactions between you and the system. 

The Logistics Digital Assistant (LDA) is enabled through the use of Oracle's digital assistant platform, Oracle Digital Assistant (ODA), which provides the tools and capabilities you need to build AI-powered assistants with task-specific skills, like the OTM Order/Shipment Status skill.

Once configured, you can bring up the Logistics Digital Assistant by selecting the Logistics Digital Assistant icon from the Global Header - as shown below.

Global Header Access for Logistic Digital Assistant

Once selected, the dialog box for the Logistics Digital Assistant will be provided.  To minimize the dialog box simply select the minimize icon  - highlighted below.

Logistic Digital Assistant Dialog Box

The minimized Logistics Digital Assistant appears on your Springboard with the icon below. 

Minimized Logistics Digital Assistant

The Logistics Digital Assistant dialog panel provided in the Springboard operates in the same fashion as the dialog box on a mobile device.  You enter normal language questions and the bot interprets the questions and finds the desired information.

Logistics Digital Assistant Conversation - Question

The Logistics Digital Assistant interprets and responds in a conversational way to your inquiries.

  

Logistics Digital Assistant Conversation 

Logistics Digital Assistant Conversation Response

Once the Logistics Digital Assistant has provided you with all your answers, you can hit the X to end and clear the conversation.

End the Conversation

For Logistics Digital Assistant users, this feature provides access to the Logistics Digital Assistant tool directly from the Global Header. With this feature, Logistic Digital Assistant users can now gain access to the LDA capabilities either via a mobile device or directly from within the system. 

Steps to Enable

The Getting Starting Guide for LDA covers - in great detail - all of the required enabling steps including: ODA setup/configuration, ODA licensing, identity management setup, user setup, and OTM setup.

To enable this specific feature - you will need to set the property glog.webserver.digitalAssistant.embedInHeader to 'true'.  By default, the property is 'false'. 

NOTE: If there is a problem with the setup - the error message below - with a link to Logistics Digital Assistant Help will be displayed.

Logistics Digital Assistant Configuration Error

Key Resources

For more information on configuring the Logistics Digital Assistant, see the Logistics Digital Assistant Getting Started Guide on the Oracle Help Center.