RSInet Release Announcements

These are Release Notes related to the most recent RSInet Update. Past releases are in the “Announcement Archive”.
Enhancements and Bug Fixes for RSInet
Title RSInet Section(s) Description Go Live Date Release Version
ETA Date Logic Enhancements Trace Reports, Sightings

We have overhauled our ETA logic to provide more accurate and constant “RR ETAs” across RSInet. This is in addition to our current “RR ETA” logic that is already working to provide a single ETA from multiple data sources.

Below is a detailed list of the basic logic and what we are enhancing for the “RR ETA” logic. This only applies to the “RR ETA” field in RSInet – other ETA fields such as Calculated ETA are generated in a different process. Please reach out to your RSI Rep for more details if needed.

 

The logic for “RR ETA” output field is setup in a hierarchy based on the source of the ETA data. We have added some business rules that supersede this normal hierarchy (providing a more accurate ETA data that wouldn’t normally be seen due to the basic hierarchy applied). We have also added some business rules that apply to the “RR ETA” field globally across RSInet, applied after the hierarchy logic has selected an ETA to use.

 

Normal Hierarchy:

CLM Mask ETA:

  • This is an ETA manually applied to an Equipment via the “CLM Mask” tool in RSInet.
  • This is usually applied for a single trip on a single Equipment.
  • Reach out to your RSI Rep for more details on CLM Mask ETA.

CLM Provider ETA:

  • This is an ETA sent to us by a CLM Provider.
  • This could be directly from the Carrier (RR) OR from our 3rd party CLM provider – Railinc.
  • The Railinc ETAs could be passed along directly from data sent to them by the Carrier (RR) OR it can be a “Railinc Predictive ETA”
  • Predictive ETA uses historical data to generate an ETA when they don’t receive ETA data from the carrier directly.
  • Railinc only sends one of the two ETAs (Carrier or Predictive) so no sub-hierarchy needed.
  • Reach out to your RSI Rep for more details on Railinc Predictive ETA

RSI Predictive ETA:

  • This is an ETA that RSI generates from historical data RSI has on similar moves.
  • This is like the Railinc Predictive ETA but is generated from RSI’s data instead of Railinc’s.
  • There are times RSI Predictive ETA will not be generated due to lack of related historical data or outliers.
  • Reach out to your RSI Rep for more details on RSI Predictive ETA.

 

Business Rules that supersede the Hierarchy:

These rules will apply the RSI Predictive ETA in place of the CLM Provider ETA, where normally the CLM Provider ETA would be shown due to the hierarchy. The Predictive ETA needs to exist (be generated) and date needs to be in the future to show.

  • If the ETA date from CLM Provider is Blank/Null then we will show the Predictive ETA
  • If the ETA date from CLM Provider is in the past then we will show the Predictive ETA
  • If the ETA date from CLM Provider is 30+ days from the date we received the CLM then we will show the Predictive
  • If the ETA code is to Junction (J) then we will show the Predictive ETA.
    • ETA code defines where the ETA date is related to – Junction (J), Destination (D) or Placement (Z). ETA to Junction normally indicates when the car will be interchanged to another carrier (RR) and does not relate to when the car will arrive at a facility

 

Business Rules that apply across all RSInet:

These rules are applied across RSInet after the hierarchy logic has selected an ETA to use

  • If the ETA date is in the past then the ETA will appear blank across RSInet.
    • Previously this logic was only applied to the Trace Report and Grouped Trace Report, causing discrepancies between Trace data and the Sightings Between and Most Recent Sightings searches (that still showed an ETA in the past).
    • Going forward the ETA will be the same across RSInet.
  • If the Sighting Code (SC) on the related CLM is W,X,B,G,H,S,Y,Z,* or # then the ETA will appear blank across RSInet.
    • Exception to this is if we get a CLM with W or X from the “CLM Provider” – then we will show that ETA date.
    • These are left blank due to the nature of status related to those Sighting Code – most may see a car sit for an extended period of time causing any ETA we get to become more inaccurate as the car sits.

 

7/1/2020 20.4
View FB Action Enhancement Accounting

We have added Actions to the View Freight Bills page to allow quicker access to highly used tabs and sub-pages that normally take a few clicks to get to. These actions are available under the Actions link on each row (FB) in View Freight Bill pages if criteria below is met. Added actions are:

 

Shipment Pattern:

  • If FB has a related Shipment ID then the Related Shipment Pattern will show (normally access via the Shipment or Pattern pages)
  • If FB does NOT have a related Shipment ID then validation message will show (“No Shipment ID tied to FB ID [provide related FB ID]”)

 

Rates and Accrual:

  • If FB has a related Shipment ID then the Rates and Accrual tab data will show (normally access by opening the “Associated Bill Information” action and going to the “Shipment Info” tab and then to the “Rates and Accrual” tab).
  • If FB does NOT have a related Shipment ID then the “Rates and Accrual” action will not show.

 

Car History:

  • In either case, if FB has or doesn’t have a related Shipment ID then the Car History info will show (normally accessed by opening the “Associated Bill Information” action and going to the “Car History” tab).

 

Disputes:

  • If FB has a related Shipment ID then the Dispute Log info will show (normally accessed by opening the “Associated Bill Information” action and going to the “Dispute” tab).
    • Note that updates can be applied on this new action page the same way its done in the “Disputes” tab in the “Associated Bill Information” action.
  • If FB does NOT have a related Shipment ID then validation message will show (“The FB has No Dispute”)

 

7/1/2020 20.4
Grouping by STCC Enhancement Trace Reports

We have added “STCC” to the grouping options available on the Grouped Trace Report. This works similar to other existing grouping options.

Based on your selection in the “Summarize Data By” dropdown in Grouped Trace Report the results will be returned with data grouped by that option. In this case all results will have groups based on STCC tied to the most recent shipment in RSInet.

Note that movements without a related shipment will show a previous shipment’s STCC Code. This mostly happens with empty moves without a related empty shipment in RSInet – they will show the previous loaded shipment’s STCC.

 

7/1/2020 20.4