RSInet Release Announcement Archive

Added “All ETAs Report” that will provide the most recent ETA data we collect and/or generate for a piece of Equipment. This ETA data is provided in separate fields based on the source of the ETA. The report also provides information on ETA Source and Type (predictive).

You can search for specific Equipment(s) using the Equipment filter or just run it to see results for all equipment for that Client. Notable Report field details below.

Masked ETA:

• The ETA applied by our system for the entire move
• This is hard set using CLM Mask Functionality in RSInet and overrides any other ETA we may have for the Equipment
• Usually applied when we are not getting accurate ETA from any other source
• Drops after shipment is placed

CLM Provider ETA:

• The ETA sent to us from the CLM provider (Carrier or Railinc)
• This data is usually from or passed through from the Carrier – exception is Railinc Predative ETA (below)

CLM Provider:

• Displays who provided (source of) the CLM and related ETA
• This is directly related to “CLM Provider ETA” output (above)

Is Railinc Predictive ETA:

• This indicates if Railinc has used their Prediction software to generate an ETA
• This usually occurs when Railinc has not received ETA data from the Carrier
• This is directly related to “CLM Provider ETA” and “CLM Provider” outputs (above)
• This will always show “No” for any non-Railinc CLM Provider (only Railinc sends Predictive ETAs)
• Accuracy is based on use of Historical transit data and is subject to the accuracy of that data

RSI Predictive ETA:

• The ETA that we generate based on Historical Transit (similar to Railinc’s Predictive ETA)
• This is usually applied when we don’t have any ETA data from other sources
• But there are multiple rules allowing the Predictive ETA to override the ETA values from other sources
• Accuracy is based on use of Historical transit data and is subject to the accuracy of that data

Calculated ETA:

• The ETA that we generate based on Est Transit stored in the Pattern in RSInet
• Our system adds the Est Transit Value to Ship Date of most recent shipment to get this value
• This is not based on historical data
• This may be inaccurate for movements without related shipment in RSInet, as it will reference the most recent shipment only

Original ETA:

• The first ETA that we collected after the movement started
• We collect the first ETA Date we get after the equipment is Released (W)
• This is not based on historical data

Notes:

• This report is limited to Equipment in the specific client
• This shows data for most recent sighting (CLM) only, similar to the Trace Report
• This does NOT indicate what is displaying in RSInet currently, just providing details of all possible ETAs

• Process was not properly relating the L/E status and Hazmat status of the shipment to the related Demurrage Rule settings (L/E & Hazmat, etc.)
• This ended up producing unwanted rows in reporting that were from rules not related to the shipment details (usually without any charges and other details)
• Users generally were manually removing duplicate rows before reporting could be manipulated.

Going forward demurrage reporting should only show charges for rules that specifically match the Shipment L/E status, Hazmat Status and any other related Demurrage Rule settings.

Added additional notation and links to the Preview BOL page ‘Duplicate Shipment Check’ Validation.

When you submit a shipment for Equipment that has already been shipped in RSInet in the last x days this “Duplicate Shipment Check” Validation will provide you notification of this conflict on the Preview BOL page.

If Equipment has been shipped within ‘x days’ value then the Preview BOL page will:

• Mark the Equipment and Weight in Red in body of BOL
• Add note near submit button (at bottom) that states “Note: Any equipment highlighted red has been shipped in RSInet within the last x days and has the potential to be a duplicate shipment”
• Provides a link with Equipment Number near note (at bottom) that will provide you the Most Recent Sightings and Shipments that can be used to investigate discrepancies
• Shipment can still be submitted – more of a Warning then Prevention

Note: “x days” is set on the New Shipment page. It defaults to 15 days, but can be adjusted before summitting.

Added entry fields and related outputs and filters to the Equipment pages to enhance reporting. 

New Data Entry Fields (New/Edit Equipment pages):

• Height Over Rail
• Auxiliary BOL
• Subleased To
• Subleased From

Optional Outputs & Filters (View Equipment page):

• Height Over Rail
• Auxiliary BOL
• Subleased To
• Subleased From.

Please reach out to your RSI contact for more details on each field usage.

Added multiple new features and logic related to ETAs:

ETA Source on Trace Report Pages:

• Added “ETA Source” output and filter to the Trace Report and Group Trace Report pages
• This provides the source of the ETA value shown in the “RR ETA” field on those pages
• This is to help provide additional clarity of ETA/CLM Source, since the RR ETA field can show ETA data from different sources depending on a multitude of rules and data
• Sources shown are:
  • CLM Provider:
    • When ETA value is from Railinc or the Carrier
    • Railinc can be passed through from the Carrier or will provide a Predictive ETA generated by Railing when they don’t get an ETA from the Carrier
    • You can use this along with CLM Source to determine which carrier is providing the ETA
  • RSI Predictive:
    • When ETA value is from our Predictive ETA Process that uses historical transit data to generate an ETA
    • This lets you know that RSI has generated the ETA, usually because we don’t have an ETA from other sources of the ETA is in the past (based on today). There are other rules as well.
  • RSI Mask:
    • When a user has set and ETA for this specific equipment for a entire trip
    • This is done using our CLM Mask tool in RSInet – field for Mask ETA
    • This is generated by RSI based on data entered by a user for that CLM Mask
    • Not based on historical data
    • Drops the Mask ETA when shipment is placed.

“Calculated ETA” for all EDI 417 (waybill) Generated shipments:

• We have updated our process to generate a “Calculated ETA” into related field on Trace Report pages when shipment does not have a related pattern in RSInet
• Normally the Calculated ETA is generated based on adding the Est Transit from the pattern in RSInet to the shipment
• But if shipment is not created from a pattern there is no Est Transit value to use in calculation
• Going forward, we are using a process similar to Predictive ETA where we will generate an Est Transit for the shipment based on historical transit
• This generated Est Transit will then be used in the Calculated ETA process to provide an accurate value in the “Calculated ETA” field in RSInet

RSI Predictive ETA when ETA Code blank:

• Added logic that will use the RSI Predictive ETA value in place of the CLM Provider ETA when we do not get a ETA Code on the CLM from CLM Provider
• The ETA Code determines what the ETA is to – either to Junction or to Destination
• Without this code it is unknown if the ETA provided to us is to Junction or Destination
• Under normal circumstances only ETA to Destination is wanted and shown
• Going forward to ensure we only provide ETA to Destination we will replace any ETA that does not have an ETA code with our Predictive ETA value – which is always to destination
• This should prevent showing ETAs that seems inaccurate and early – those usually to Junction

Added a couple features to the Maintenance section of RSInet

Update Car and Equipment Status when arrival at shop:

When equipment arrives at a shop, the system will recognize this and update the Car Status on the Maintenance Log and update the Equipment Status for the related Equipment

This will be done when all criteria below are met:

• There is an Active Maintenance Log on the equipment AND
• The current Car Status on Maintenance Log is set to “In Route” AND
• The most recent CLM received is a “Z” (Actual Placement)

When all that happens the system will:

• Update the Car status on related Maintenance Log to be “At Shop”
• Update the Equipment Status to be “Shop”
• This is intended to save time so users to not have to apply the update to Equipment or Car Status manually

Added “Edit Maintenance Detail” action to View Maintenance Detail page:

• This action will take you directly to the Edit Maintenance Log Detail page
• This is the same page accessed from View Maintenance Logs -> Edit Maintenance Log action -> Edit Maintenance Log Detail action
  • Intended to save a few steps to get to this data

Added Filters and Outputs to View Maintenance Details page:

• Outputs:
  • Fleet Path
  • Fleet
  • Lease
  • Lease Rider
• Filters:
  • Fleet Path
  • Fleet
  • Lease
  • Lease Rider
  • Notes

Fixed a bug that was preventing the Service Log Notes from showing in the View Service Logs page when the Service Log is Inactive.

Going forward we will show the Service Log notes on the View Service Log page when Service Log is Active or Inactive

• Date Modified
• Modifier (user)

Fixed a bug that was providing negative “Days Held” values on Demurrage reporting when dates used in calculation were null/blank.

This has been resolved to ensure negative day values will not show on Demurrage Reporting.

Also we have renamed this field to “Demurrage Days” to better represent the data shown. This value represents the days between the Demurrage Start Date and Demurrage End Date

Created Shipment/Delivery Window process to track the shipment inception and completion based on a window of days at the beginning and/or end of shipment.

Summary:

• This will show if a Shipment was “Early”, “On Time” or “Late”; in either being Shipped from Origin or being Delivered at Destination.
• Value will be based on the Days applied to the Shipment Window and/or Deliver Window Value – set globally at the client level.
• This is intended to enhance “On Time” reporting for shipments beyond an exact match between Expected and Actual dates or Shipment and Delivery.
• The Shipment and Delivery Window can be applied together or separately; with same Day or different Day values.
• Only the “Window” with a client level value will provide expected values for shipments.
• Values calculated are based on Dates only and do not reference any related Time
• Shipments without values in Expected Ship Date, Ship Date, Expected Received Date and/or Closed Date may not display Window Status values

Features:

• Fields:
  • Shipment Window Comment: Add any note related to the Shipment Window on the New/Edit Shipment pages for this specific shipment only
  • Delivery Window Comment: Add any note related to the Delivery Window on the New/Edit Shipment pages for this specific shipment only
• Outputs:
  • Shipment Window Comment: Displays value entered in related field when shipment created/edited
  • Delivery Window Comment: Displays value entered in related field when shipment created/edited
  • Shipment Window Status: Shows if shipment was shipped “Early”, “On Time” or “Late” based on Window value
  • Delivery Window Status: Shows if shipment was delivered “Early”, “On Time” or “Late” based on Window value
• Filters:
  • Shipment Window Comment: filters on related field data
  • Delivery Window Comment: filters on related field data
  • Shipment Window Status: filters on related field data, filter is dropdown containing options of “Early”, “On Time” or “Late”
  • Delivery Window Status: filters on related field data, filter is dropdown containing options of “Early”, “On Time” or “Late”

Process Overview:

• Shipment Window:
  • RSI will set a whole day value at the client level as defined by client
  • This value will be added to the Expected Ship Date value on specific shipments to create the Shipment Window for that shipment – spanning multiple days
  • A Shipment Window for a specific shipment is created by adding the Shipment Window Day value to both sides of the Expected Ship Date
  • The system will then compare the Ship Date to the Shipment Window and apply a value for that specific shipment based on where Ship Date falls in relationship to that Shipment Window:
    • Early: Ship Date Before Shipment Window
    • On Time: Ship Date within Shipment Window
    • Late: Ship Date after Shipment Window
  • Delivery Window:
    • RSI will set a whole day value at the client level as defined by client
    • This value will be added to the Expected Received Date value on specific shipments to create the Delivery Window for that shipment – spanning multiple days
    • A Delivery Window for a specific shipment is created by adding the Delivery Window Day value to both sides of the Expected Received Date
    • The system will then compare the Closed Date to the Delivery Window and apply a value for that specific shipment based on where Closed Date falls in relationship to that Delivery Window:
      • Early: Closed Date Before Delivery Window
      • On Time: Closed Date within Delivery Window
      • Late: Closed Date after Delivery Window

Examples:

• Shipment Window:
  • If you have a Shipment Window of 3 days and Expected Ship Date is 12/15/2020 then the Shipment Window will be 12/12/20 – 12/18/20.
  • If Shipment is created with a Ship Date that
    • Falls within that range then Shipment will be considered “On Time”;
    • If Ship Date is before Window then its “Early”;
    • If Ship Date is after Window then it is “Late”
• Delivery Window:
  • If you have a Delivery Window of 5 days and Expected Received Date is 1/15/2021 then the Delivery Window will be 1/10/21 – 1/20/21.
  • If Shipment generates a Closed Date that
    • Falls within that range then Delivery will be considered “On Time”;
    • If Closed Date is before Window then its “Early”;
    • If Closed Date is after Window then it is “Late”

Please reach out to your RSI Representative to enable this process or if you have further questions.

Fixed a bug where the “Hazmat Contact” field was not present for hazardous shipments on the Edit or View Shipment Actions (View Shipment page). The “Hazmat Contact” field was also not showing on New Shipment page when an error occurred while submitting a hazardous shipment.

Both bugs have been resolved and the “Hazmat Contact” field should appear on all New, Edit and View Shipment pages for hazardous shipments.

Note: This “Hazmat Contact” is the person certified to submit hazardous shipments to carriers (not related to the “Hazardous Materials Contact” in Products)

Added logic that will automatically close a “Load Shift” Service Log once the equipment begins to move again. “Load Shift” Service Logs will be inactivated when we get a Sighting Code that is NOT a “B” (Bad Order) or “G” (Bad Order Resolved) after the Log was created.

This is similar to the way we already automatically close “Bad Order” Service Logs.

Added a feature that will allow users to create multiple Maintenance Logs at once. This process is similar to the Add Multiple Equipment feature.

Process:

• After going to New Maintenance Log page users can select the “multiple” option at the top of the page.
• Then you can add/paste equipment into the text field that replaces the equipment dropdowns.
• From there you will fill out the Maintenance Log and Shop Detail as normal.

Notes:

• Equipment must already be in RSInet – please add any needed equipment prior to the process
• Page defaults to add “Single”
• All Maintenance Logs created will have same data applied
  • If you need Maintenance Logs with varying data they must be entered as singles.

Added the “File Name” output to the View Freight Bill page. This displays the name of the most recently added file to the Freight Bill in RSInet. There is a related filter for this output as well.

Fixed a variety of bugs related to ETAs:

Fixed a bug where the ETA Logic was preventing ETAs from showing that were up to 24 hours in the future. So if an ETA was for ‘today’ users did not see it. This has been corrected and ETAs with a date of ‘today’ will show going forward

Fixed a bug that was causing the same ETA date (from the most recent sighting received) to show as ETA for all sightings in sighting searches. This was limited to ETAs from CLM Providers. Going forward the sighting searches will show the correct ETA values for all sightings (most recent and historical)

Fixed a bug where the “Last Sightings” box (in Most Recent Sightings search results) was not applying the RSI Predictive ETA properly. This allowed for different ETA value to show here compared to other ETA values in RSInet. Going forward the “Last Sightings” box follows the same rules as all other ETA fields in RSInet and will show the RSI Predictive ETA when rules allow.

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.

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”)

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.

We are beginning to roll out our new Demurrage Reporting Process.

This release will contain the New Demurrage Reporting tools for all to use – Internally and Externally. While internally we will be ensuring user interfaces for the New Demurrage Rule, Edit Demurrage Rule and View Demurrage Rules pages are working entirely as expected prior to rolling out to all users in the near future.

Note: These new Demurrage Reporting tools work with an entirely different dataset then what is used for the current “Loaded Demurrage Report” and “Empty Demurrage Report” that many clients use (Reports tab of RSInet).

• If you are using the legacy Demurrage Reporting process and want to transition to the New Demurrage Process please reach out to your Client Representative at RSI for information.
• Some clients have custom reporting that is already tied to this new dataset. These clients can continue to use the current reporting options or transition to these reports created for this new process. Please discuss with your Client Representative for information on transitioning to this new process and what changes you may see from your current Demurrage Reporting options.

Main Features:

Carrier Demurrage Detail Report

• Will be available to ALL users upon release
• Shows the daily charge history for every Equipment that is accruing demurrage
• Contains related shipment and sighting information for the equipment
• Contains many filter options to narrow down data by Date, Fleet, Vendor, Contract, etc.

Carrier Demurrage Report Summary

• Will be available to ALL users upon release
• Shows the total charges for every equipment accruing demurrage
• Contains related shipment and sighting information for the equipment
• Contains many filter options to narrow down data by Date, Fleet, Vendor, Contract, Charge Status, etc.
  • “Charge Status” can show demurrage that is “Final” (car has moved out of Demurrage) or demurrage that is still “Accruing” (car still in Demurrage)

New Carrier Demurrage

• Will only be available for internal users upon release
• Will be rolled out to all once we internally ensure the page is working as intended
• Client Reps can add Demurrage Rules on your behalf in the mean time
• This page is where you would add New demurrage rules with details such as Daily Rate, Locations, Triggers, Vendors, Contract, etc.

View Demurrage Rules page

• Will only be available for internal users upon release
• Will be rolled out to all once we internally ensure the page is working as intended
• Client Reps can Edit Demurrage Rules on your behalf in the mean time and send you a report of All your demurrage rules if you need them
• This page is where you would view all your demurrage rules added to RSInet (active and inactive)
• This page also contains the Edit action to allow users to change any setting on a demurrage rule
• There are filters to allow users to dig down and find the demurrage rules needed.

Please reach out to your Client Representative for more details and transition information

Corrected issues with the “Return to Shipment” and the “Submit and Add New” buttons on the Preview BOL page.

Submit and Add New bug was preventing EDIs from being sent to carriers on any subsequent shipment when this button was used. It was also preventing edit capabilities within the Product fields on Subsequent shipments (New Shipment page). Both issues have been resolved.

Return to Shipment bug was causing some selections made on the New Shipment page to revert to pattern defaults. This has been corrected and the fields below will retain selected/entered data when using the Return to Shipment button going forward:

• EDI Pattern checkbox
• Weigh In Route checkbox
• Product “Quantity” field
• Product “Code” dropdown
• Time Zone dropdown

• New Contact User page
• Edit Contact User action
• New Demurrage Contact page
• Edit Demurrage Contact action
• New Rate Contact page
• Edit Rate Contact action

• Updated the page so the Mass Update tool appears within the same page
  • Previously took you to a new page to select and apply updates.
  • This will help retain filters applied after performing a mass update
• Changed “Update” button to be called “Save” on the Mass Update tool
  • Name Change only, functionality the same
• Added the “Contacts” to options to the Mass Update tool
  • Works in the same way as editing a single Service Log to add Contacts
• Emails are blocked for Mass Updates to Service Logs at the time of the mass update
  • Any subsequent single updates or daily reports will still be emailed
  • This is to prevent email overload when performing mass updates

Fixed a bug that was preventing the Idle Days value from showing in the Last Sighting section of the Most Recent Sightings search. Going forward the Idle Days value will show in the Last Sighting section of the Most Recent Sightings search. This search is available on the Dashboard and also from an Actions on other pages in RSInet.

Updated the logic for the Is Potentially late field available for Trace Report and Report created from Trace Report pages. Going forward if the current Sighting Code (SC) is Actual Placement (Z) then the Is Potentially Late value will be “No”. This logic was added because when equipment is in Actual Placement (Z) status the trip is complete and cannot be “Potentially Late”.

Updates applied in a couple places to address the need to have Rule 11 Shipping Parties in order based on Routing and Party Billing information set in the Pattern. Some carriers are correcting on their end and had proposed possible future charges for performing this manual correction on their end going forward. This also prevents delays in waybill generation due to these corrections needed on the Carrier side.

Added Validation to the New and Edit Pattern pages that sets the Rule 11 Party order based on Parties selected in the Party Billing Section and also the order of the related Carriers in the Routing section.

• First carrier in route drives what the first Rule 11 party listed will be, also based on the connection in the Party Billing Information section.

Separately we updated the EDI Generator to order the Rule 11 parties per party list order set in the database.

• This is a secondary and backup operation to ensure the correct Rule 11 party order is sent to the carriers via EDI

Fixed a bug were multiple fields in the New and Edit Shipment page would drop data that had been applied after using the Return to Shipment button on the Preview BOL page to make corrections.

When on the Preview BOL page and the “Return to Shipment” button was selected, the New/Edit Shipment form would return without data in the fields below (reverting to a default or blank). Going forward these fields will retain data applied when using the “Return to Shipment” button from the Preview BOL page.

Fields that dropped data or reverted were:

• EDI Pattern Checkbox
• Weigh in Route Checkbox
• Quantity field in Product
• Code field in Product
• Time Zone dropdown

Fixed a bug that was preventing the Fuel Surcharge Value (FSC) showing in the View Fuel Surcharge page in the corporate website if that value was over $0.99. Going forward the FSC Table in the Corporate website will show values up to $10.00

Fixed a bug that was preventing the save of the Edit Shipment action page under certain conditions.

Conditions:

• Client Setting of “Auto Number Bill of Lading” is set to “Toggled” (the system allows the Auto-Generate BOL to be enabled or disabled at the Pattern level)
• The Pattern has this “Auto-Generate BOL” option enabled/checked (to Auto-Generate the BOL on shipments using this pattern)

This bug was incorrectly causing an error message and prevent saving when it should allowed the save. Going forward users will no longer hit this incorrect error when performing a save of an Edit Shipment action under the stated conditions above

Updated functionality to allow users to decide if they show Lease Rider data for Current, Future or Expire (Past) Riders – or any combination of the 3. The Report had previously been setup to only show current data.

Options:

• Current:
  • Enabled in report by default (automatically loads with this data)
  • Shows data if ‘today’s date FALLS WITHIN the Effective/Expiration date range for the related Lease Rider
• Expired:
  • Disabled by default (user will have to toggle on)
  • Shows data if ‘today’s date is BEFORE the Effective/Expiration date range for the related Lease Rider
• Future:
  • Disabled by default (user will have to toggle on)
  • Shows data if ‘today’s date is AFTER the Effective/Expiration date range for the related Lease Rider

• Works similar to the Product filter on Shipment Volume Report
• Contains all Equipment Ownership Type options available in Equipment pages in RSInet

Added the Equipment to the top of the “Shop Detail” pages. This change was made in order to streamline shop detail updates on popup windows and avoid system errors.

Added a “Ownership Type” Output and Filter to View Shipments page. Users can access the output/filter to enhance your reporting options for shipments.

• If no ETA date exists, we will use “Today” as the default ETA for calculation
• If we have no “Expected Received” date, then we will use the “Calculated ETA” as default Expected Received date for calculation
• We ensured that when the ETA is later than the “Expected Received” then the “Is Potentially Late” flag is properly applied
  • ETA > Expected Received

Added logic that will auto-populate the Maintenance Log fields based on data entered in the “Date Scheduled” field. This feature is only available when using the Maintenance Type “BRC – Running Repair”.

Date copied from Date Scheduled to other fields:

• Date sent to shop
• Date placed at shop
• Date complete
• Date released

Fixed a small bug preventing New Products from populating when Pattern is changed on the Ship Sales Orders page. Moving forward this dialogue should populate properly.

Added an optional “+4” extension to the postal code field. This is used when creating a new shipping party or editing an existing one. Should allow for greater shipping flexibility

Added ability to accrue separate rate values for different DOT Conditions (usually defined in the related Rate Contract set by the carrier). RSInet can now use the Equipment “DOT Tank Car Class” code and accrue only the related Rate Detail with the same DOT Code.

Notes:

• Both the Equipment and the Rates Detail used in the shipment must have DOT values applied for proper accrual matching
• If no matching DOT value between Equipment and Rates found then the highest valued Active Rate Detail will be applied
• The DOT Code on the rates only uses a truncated DOT code to allow for a single Rate Detail to match to Multiple Equipment “DOT Tank Car Class” codes
  • i.e. Rate has code of DOT 103A and would be applied to any equipment shipped that contains the DOT Codes of “DOT 103A” – like DOT 103AALW, DOT 103ANW and DOT 103AALW
• This accrual ability is in addition to the existing rate accrual features and using the DOT settings are not required
• Please contact your Logistics Rep for more details.

The CLM Masking functionality returns with better performance. Also addressed a few minor bugs related to the End Dates not getting set properly. Use of tool has not changed. If you need more info please see the write up in the Announcement Archive in Release 18.2 or contact your Logistics Rep.

We have restored the Days En Route functionality in RSInet. Performance Issues related to this feature have been resolved. There is no change in the way it works or data you should see. Changes were to how the data was stored.

Note: Days en Route calculates the days between the Ship/Release Date (* / W) and ‘Todays’ dates. Count stopped when cars are showing current sighting as Actually Placed (Z)

Added “Loaded CP Date” output column to the Transit Detail report. This provides the Loaded Constructive Placement Date of related Shipment

Updated “Placed Date” Output column in the Transit Detail report to be called “Loaded AP Date” to avoid confusion with the newly added Loaded CP Date field noted above. This contains the Loaded Actual Placement Date of related Shipment

Cleaned up some blank output columns and rows that contained no data in the Excel output file type

Added Filters for Origin State, Destination State, Origin Country, Destination Country, Product Group, Location Group, L/E, Pipeline Status & Display Type

Notes:

• Pipeline Status is related to the data shown in the Status output of the Pipeline Report
• Display Type provides users and option on how the Pipeline report displays data:
  • Detailed and Summary: Show all line items for each active shipment AND also a summary based on Pipeline Status and Total number of moves at the end of the report
  • Detail Only: Show only the line items for each active shipment
  • Summary Only: Shows only the summary based on Pipeline Status and Total number of moves

Updated the Currency field to be a dropdown on the New Freight Bill page and on the Edit/View Associated Bill Information action page. This contains the standard options of “USD” , CAD” and “MXN” to match to the associated country’s currency.

The Currency filter in View Freight Bill page was also updated to be a dropdown with the same options.

• Creator Name
• Created Date
• Modifier Name
• Modifier Date

Updated the logic that applies the “Close Date” for Empty Shipments to be more accurate. Previously the Closed Date on an Empty Shipment in RSInet was set by the Sighting Date of the First Loaded CLM Sighting (any sighting code). Going forward the Closed Date on an Empty Shipment in RSInet will be set by the First Empty Y or Z sighting code after the Ship Date.

This aligns with the logic that applies the Close Date for Loaded Shipments: set by the First Loaded Y or Z sighting code after the Ship Date.

Fixed a bug in the View Pattern Rates page that was converting Net Ton rates to Per Car rates incorrectly. The process was using the wrong conversion value for Tons by dropping values after the decimal. This also caused the Total Rate + Fuel value to also be incorrect. Going Forward the Process will correctly use the entire conversion value to display Net Ton rates with a Per Car rate on View Pattern Rates page.

Example: Per Ton Rate has condition of 97.5 Tons minimum, but the system was only using 97 tons to convert to per car rate, so the value was off by a half ton.

Fixed a bug that was causing the same EW Date to be applied to different shipments for the same Equipment. The erroneous dates were outside of the Shipped and Placed dates range for the related trip and were not valid for that related trip. Going forward the EW Date output will be restricted to display only the first Empty Release (EW) sighting date within the Trip – between the Shipped and Placed sighting dates.

Added validation to the Manage Fleets page to prevent saving a fleet with a blank name. Going forward this validation will prevent saving a blank name to a fleet and force you to enter a valid name for the fleet prior to saving

Fixed a bug that was causing the “Group By” option to revert to the default of “Destination City” when editing a Saved Report created from the Group Trace Report page. Going forward the Group By option should store your selection when editing a Saved Report created from the Group Trace Report page.

• Product dropdown menu will now display the “Product Code” after the “Product Name”.
  • The Product code a value assigned to a product for internal RSInet use.

• Removed Carrier Contact fields from “Railroad Info” section:
  • Diversion Email Address
  • Diversion Fax Number
  • Contact Information Button
  • Do Not Send Checkbox

These are not needed on diversion entry form as the RSI team will determine the best contact means for each Diversion Request 

Links to Outage Table lookup tools at Equipment Owner websites have been updated in RSInet. We have addressed Missing and Broken links along with updated link names. These are found on the “View Outage Table” page and at the bottom of View/Edit pages for an individual railcar

Outage Tables are also known as Innage Tables, Strapping Charts or Gauge tables 

Fixed a bug on the Ship Sales Order page where the “Legend” data was hidden off-screen. Going forward all Sales Order “Legend” data should be visible.

We have addressed occasional ETA Discrepancies across RSInet. Logic has been unified on the pages/tools below. Under nearly all circumstances the ETA should match.

ETA should be the same on:

• “Sightings Between” search
• “Most Recent Sightings” search
• “Last Sightings” box
  • Appears at the top of the “Most Recent Sightings” page/popup and summarizes the most recent sighting info

Remaining ETA Discrepancies: 

• The Trace Report pages do NOT display ETAs in the past, while the pages/tools noted above will
  • So there will be times the Trace Report ETA will NOT match the Searches ETA
• Also the ETA Mask feature is NOT applied on all searches
  • So if an equipment has been masked with ETA data there may be discrepancies

Added “Freight Terms” dropdown to New, Edit and View Rate pages in RSInet. You are required to make a selection from the options of Rule 11, Prepaid, Collect and NR (non-revenue). This is a reporting field and currently does not drive any further logic in RSInet.

A Filter and optional Output for “Freight Terms” have been added to the View Rates page for reporting purposes. Filter contains same options in a dropdown menu.

Added multiple reporting features across multiple pages of RSInet:

• “Est Transit Days” Output and Filter added to View Pattern Rates page
  • Optional output displays the value applied to the Est Transit Days field on the related pattern.

• “Date Sent To Shop” Output and Filter added to View Maintenance Logs page
  • Optional output displays the value applied to the Date Sent To Shop field on related Shop Detail

• “Lease Rate” Output and Filter added to View Equipment page
  • Optional output displays the value applied to the Lease Rate field in Lease related to Equipment

• “Fleet Path” added as an option in Grouping dropdown (filters) in Grouped Trace Report
  • This will group equipment based on related Fleet Path

Note that “Est Transit Days” value is manually set on the pattern but can be automatically audited and updated based on historical transit data.

Enhanced Temp Car Drop Code feature allows more fine grain control over when your TEMP cars (Ownership Type = Customer) will be automatically dropped (inactivated) in RSInet and stop receiving CLM Sightings.

TEMP cars are sometimes used in RSInet when equipment that you do NOT own or lease is being used for a shipment you are monitoring. NOTE: This feature can only be set by RSI Employees so please contact your Rep or Manager for further details and suggested settings for your needs. Details provided below are informational and only provided to aid in planning your drop rules

There are separate Rule Settings based on L/E status of Current movement of Equipment

• “Loaded Temp/Customer Car Rules” are used for dropping equipment currently moving as a Load
• “Empty Temp/Customer Car Rules” are used for dropping equipment currently moving as an Empty
• Rule Settings are independent of each other and you can set just Loaded, just Empty, Both or Neither

Under each Rule Setting there are options for both the CLM L/E status and the Sightings (SC) you want to use to automatically Inactivate the TEMP Equipment

• Select CLM L/E Status used to Drop:
  • Select “Loaded” if you want a Loaded (L) CLM to Drop the TEMP Car
  • Select “Empty” if you want a Empty (E) CLM to Drop the TEMP Car
  • You can only select one L/E setting for each Rule
• Select Sighting (SC) used to Drop:
  • Select the checkbox(es) for the CLM Sighting Codes you want to Drop The TEMP Car
  • SC options are: *, A, D, J, P, R, S, W, X, Y, Z
  • You may select multiple SC options for each rule

Logic: The Drop Code logic combines the CLM L/E selection with the CLM Sighting selection(s) to create a rule that will automatically Drop TEMP equipment when a CLM is received for that equipment that matches the L/E and Sighting settings. This is done for both the Loaded and Empty Rule settings separately.

Example: if you want to Drop TEMP Loaded Cars after they have received an Empty Release (W) sighting or Empty Pull (X) sighting then

• Use the Loaded Temp/Customer Car Rules
  • Select Empty from the CLM L/E dropdown
  • Select the “W” and “X” checkboxes and save.

• User will need to select related checkbox for field for that data to be applied to related Equipment when using the tool.
• The Batch Update Equipment tool is available on the View Equipment page
  • Select checkboxes for equipment that needs updates and click the “Update” button to get to the tool.

Updated the underlying logic that drives the “Days en Route” values on the Trace Report & Grouped Trace Report pages in RSInet. We have included a rule that stops the “day count” when we get a “Z” Sighting Code (SC).

This will prevent the Days en Route count from continuing to accrue days while the car is Actually Placed (Z) for loading or unloading. This creates more accurate Days en Route values.

Updated the underlying logic that drives the “Predictive ETA” data that RSI Generates from historical movement data.

Very Basic Overview:

• Adding “Y” and “Z” sighting codes to the logic to increase sample size of historical movement data
• Adding a relationship between the Destination SPLC to the Shipment Destination SPLC to also increase sample size of historical movement data

Note that the Predictive ETA is shown in the “RR ETA” output column across RSInet ONLY when we do not have an ETA from a CLM Provider and/or there is no active CLM Mask applied to related equipment.

Added “Equipment Description” Filter and Optional Output to the Trace Report and Grouped Trace Report pages. This references data applied to the “Equipment Description” field on Equipment pages.

Added underlying logic that will remove an Inactive Contact from Contact Groups in RSInet. This is an additional layer to prevent correspondence from being sent from RSInet to Contacts that no longer want to receive correspondence (Inactive). Process runs daily, afterhours.

Updated the Insert Multiple Equipment tool on New Shipment page to contain entry fields for “Load Number” and “Volume” if the related features are enabled for the client. This tool is great for entering data for multicar shipments.

Added the “Origin Station” and “Destination Station” to BOLs generated by RSInet. These fields should appear in the section with Carrier and Date information near the top. These fields are driven by the Origin Station and Destination Station in RSInet Patterns/Shipments.

Notes:

• Addressed at all sources of BOL Creation.
• Origin Station and Destination Station dive the f9/d9 segments on EDIs
• BOLs can be accessed from:
  • RSInet
  • Sent via email/fax
  • Relayed to users via other data feed.

Added “Accrual Without Invoice” Report that will show Shipment Accrual data where we have NOT received a Freight Bill (invoice). This report is available under the Report menu section and access is based on user roles.

Note that report loads with Default Ship Date range of ‘Yesterday’ but this can be edited to a date range determined by user. Default added to avoid long load times as report is data heavy. 

Updated the Empty Disposition logic to prevent access to the Origin Switch and Destination Switch fields on Empty Disposition Route tool. Empty Disposition uses a flat route without Switch indicators. Using Origin Switch and Destination Switch fields – when they were available – was causing errors in the billing submitted to carriers. These fields will be shown but not accessible for Empty Disposition

Added a way to indicate a “Shop Party” in RSInet is a “RR Shop Party” (a shop run by a rail carrier/RR). When the “Shop Party” role is selected in New/Edit Shipping Party pages a new section will be inserted at the bottom of the page/form called “RR Shop Party?”. Selecting that checkbox will indicate this Shop Party is a “RR Shop Party” throughout RSInet.

There are filters and outputs for “RR Shop Party” on View Shipping Parties, View Maintenance Invoices, View Maintenance Details, View Maintenance Logs pages. This is used for reporting purposes only and does not drive any functionality.

• Added an Idler option to the Equipment section of New/Edit Rates pages.
  • This is just for reporting purposes and does drive any functionality
• Added an Idler option to the Rate Conditions available in Rate Details section of New/Edit Rates pages.
  • This must be set for the rate to be considered “Idler” Rate throughout RSInet and for the Freight to be Accrued properly
  • Note that Equipment on Shipment must also be marked as “Idler” for the Idler Rate to be accrued properly for the Idler car(s) 

Basic Process Overview:

• Create an Idler Rate; must have Idler Rate Condition
• Add Idler rate to Pattern
• Create New Shipment from pattern; Ensure to mark the Idler checkbox in the Equipment that will be Idler, then “Submit” Shipment
• The system will then:
  • Apply Idler Rates to Cars indicated as Idler in the shipment
  • Apply the other (non-Idler rates) to the Equipment NOT indicated as Idler in the shipment.
  • This creates a Total Accrual that has both the Idler and Non-Idler rate values and should match up to Freight Bill received under normal circumstances.

Note that Idler Rates will NOT be displayed in or part of the totals in View Pattern Rate page. Please contact your RSI Customer Service Rep or Manager to have this feature enabled.

Fixed a bug where the generic “Restrictions” field and related data was missing from auto-generated emails when a New Rate Request is saved in RSInet. This field was present on all other automated Rate Request correspondence. Going forward the generic “Restrictions” field and related data should always appear on all auto-generated Rate Request correspondence

Fixed a bug where the Volume Output in View Shipment, Trace Reports and on BOLs was showing value of “0” when the related field was left blank when shipment was created. Going forward the Volume Output in RSInet and on BOLs will appear blank when the related field on a New Shipment is left blank.

Fixed a bug where the Excel output from the “CLM” tab on View/Edit Shipment action was NOT matching the data displayed in the tab itself. Going forward the Excel output will match the data shown in the CLM Tab (UI). This tab is accessed from View Shipments page -> View/Edit Shipment action – CLM Tab.

Added an “Equipment” Output and Filter to the View Maintenance Detail page to help with Filtering and Reporting of Shop Details. This is a standard output and will load as the first output on the page (unless you have Default Filters applied). This is also the standard Equipment filter used across RSInet.

Updated the “DOT Tank Car Class” feature in the Equipment section of RSInet to be dropdown with preset DOT Tank Car Class Codes. This change was due to inaccurate data being populated in the original free form text field and a need to store and send correct data in a proper format.

“DOT Tank Car Class” field on New and Edit Equipment pages:

• Is a dropdown containing the DOT Car Class Codes.
• Codes provided by Railinc (page 98/99)

“DOT Tank Car Class” Filter on View Equipment page:

• Uses a dropdown containing the DOT Car Class Codes.
• Contains the same list from Railinc (page 98/99)

“DOT Tank Car Class” Output on View Equipment page:

• Basically unchanged, besides that it displays data in correct format

Note:

• Existing “DOT Tank Car Class” data that match exactly or was determined to be a match to the Codes provided by Railinc (page 98/99) where updated to the dropdown value
• In some cases the data provided was actually AAR Code data, and that was added to the new AAR Code Feature (more info in these release notes).
• Anything that was not clearly a DOT or AAR Code was moved to the Comments field for the related Equipment.

Added an “AAR Car Type Code” feature to the Equipment section of RSInet comprised of Entry field, along with an Output and Filter for reporting.

“AAR Car Type Code” entry field:

• On New/Edit/View Equipment pages
• Free Form field
• 4 Character limit
• Codes are usually 1 Alpha and 3 Numbers (“C113”)

“AAR Car Type Code” Output/Filter:

• On View Shipment Page
• Output is Optional
• Filter has standard “Equal”, “Contains” and other options.

More info on AAR Car Type Codes 

Added ability to apply “Load Number(s)” to shipments created in RSInet.

If Feature enabled for your client:

• A “Load Number” field will appear for each equipment added to the New Shipment page
  • Can apply different value to each equipment
  • Not Required
  • 30 Character Limit

“Load Number” Output and Filter

• Added to View Shipments, Trace Report and Group Trace Report pages
• Optional, Sortable Output
• Filter has “Contains”/”Not Contains”

Notes:

• Process for data feeds (where shipment data is sent to RSI) varies, but essentially the Load Number data will populate the related field on the shipment
  • Can be edited
  • Feed must be properly formatted
• Load Number is NOT sent on EDI
• Load Number WILL show on BOL
• Please contact your Account Manager or Rep for more details and to have this feature enabled for your client.

Added ability to apply “Volume” (value) and “Volume Unit” (qualifier) to shipments created in RSInet.

If feature enabled for your client:

• A “Volume” field will appear for each equipment added to the New Shipment page
  • Can apply different value to each equipment
  • Not Required
  • 8 Character Limit
• A Volume Unit dropdown field will be on the New Shipment page in Shipment Options section
  • Can set to a value of Gallons, Liters, Cubic Feed or Cubic Meters
  • Default can be set at Client Level
  • If Default not set a client level, page will load with Gallons

“Volume” and “Volume Unit” Outputs and Filters

• Added to View Shipments, Trace Report and Grouped Trace Reports
• Optional Sortable Outputs
• Filter for Volume has Greater Than / Less Than options
• Filter for Volume Unit has dropdown option (Gallons, Liters, Cubit Feed, Cubic Meters)

Notes:

• Process for data feeds (where shipment data is sent to RSI) varies, but essentially the Volume and Volume Unit data will populate the related fields on the shipment
  • Can be edited
  • Feed must be properly formatted
• Volume and Volume Unit WILL be sent on EDI
• Load Number WILL show on BOL
• Please contact your Account Manager or Rep for more details and to have this feature enabled for your client.

Added “Covered Hopper PD” and “Covered Gravity Hopper” options to the “Equipment Type” dropdown field in New and Edit Equipment pages. These options were added to the Filter (dropdown) and Output to the View Equipment page as well. These are in addition to the existing generic “Hopper Car” currently available as Equipment Type

Fixed a bug where the RSInet User Guide Videos (Help section) were not showing when connected to RSInet via HTTPS protocol. These videos should now run on both HTTP and HTTPS for RSInet.

• Removed logic sorting Equipment by Fleet
• Added logic to sort Equipment by Equipment Marks.
  • This will sort on the alphas first then on numerals.

• These fields are near the bottom of the “Loading Information” section in Equipment pages.
• Filters and optional Outputs were also added to the View Equipment page for “Hatch Type” and “Gate Type”.
• Outputs can be added to the page using the filters tool (output tab)

Added new functionality that will create a CLM in RSInet to represent a Diversion after one is submitted in RSInet. A CLM with a Sighting Code (SC) of “#” will be inserted into CLM/Sighting Search Results and Trace Reports. It will also have a Sighting Date matching the Date/Time the Diversion was created in RSInet. Other details below.

Some of the Diversion CLM Sighting Data is pulled from the Diversion itself:

• Sight Date: Diversion Created Date
• L/E: L/E selected in Diversion
• RR: Carrier Selected in Diversion
• Destination City: from Consignee in Diversion
• Destination State: from Consignee in Diversion
• SC: “#”
• SC2: “DV (Diversion (#))”
• All other data comes from Previous CLM if available (or otherwise blank)

Added more grouping option to the “Summarize Data By” dropdown in Grouped Trace Report. Dropdown located in the filters tool. The Grouped Trace Report will apply grouping based on selection made. Data is exportable with grouping (PDF/Excel).

“Summarize Data By” Options Added:

• Ship Dest City
• Ship Dest St
• Origin City
• Product
• Product Code
• Product Group
• Fleet
• Equipment Initials
• Load/Empty

Links under the Data Visualization section have been updated to display in Alphabetical Order to assist in locating Reports

The character limit for the “Gaskets & O-Rings” field on New/Edit Equipment pages has been extended to 250 characters. Was previously set to a limit of 50 characters.

Added validation to the New/Edit/Clone Pattern pages to ensure important required data is provided and that conditional data is applied and relevant based on other selections. Detailed Validation Messages should display at the top of the page describing the situation.

Added Validation:

• Prevent the same Rule 11 party from being applied to the same pattern more then once.
• Prevent a “Party to Receive Freight Bill” from being applied to a pattern where Freight Terms are “Rule 11”.
  • If Freight Terms are Rule 11 then only Rule 11 parties must be used to indicate who will get freight charges
• Ensure that if Rule 11 is selected in “Route Type” field then Rule 11 must be selected in “Freight Terms” – and vice-versa.
• Ensure that if more then one Rule 11 party is applied to pattern then the “Party Billing Information” section becomes required.
  • This area defines what Rule 11 party will pay for what portion of the move.
• Ensure that if Freight Terms are set to “NR” then the Revenue field must also be “Non” – and vice-versa
• Ensure that the Carrier selected in “Send BOL to Carrier” matches the Carrier selected in the first “RR” in the Routing section – non-switch area of route.
• Ensure that there is a “Customs Broker” applied to a pattern where the Origin and Destination Countries do not match – crossing border.
  • This can be any Broker Type – US, Canadian, Mexican or [generic] Customs Broker.
• Ensure that a selection is set in the main “Route Type” and a “RR” dropdowns in the Routing section
• Ensure that Junctions (Junct/R260) are present between Carriers (RRs) in the Routing section.
• Ensure the required fields have data/selection made in the Party Billing Information section of Pattern pages.

Fixed a bug where the system was preventing a New CLM Mask for Equipment that has a Previously Existing CLM Mask in RSInet for that same Equipment. Now users should be able to add New CLM mask for Equipment that has previous CLM Mask(s) applied in RSInet – depending on Status and End Date of previous CLM Mask(s).

Updated Logic:

• If an existing ACTIVE mask DOES NOT have and End Date then RSInet will PREVENT another mask from being saved
• If an existing ACTIVE mask DOES have and End Date then RSInet will ALLOW another mask to be saved
• If an existing INACTIVE mask DOES NOT have and End Date then RSInet will ALLOW another mask to be saved
• If an existing INACTIVE mask DOES have and End Date then RSInet ALLOW another mask to be saved
• If there is NO Existing/Previous mask then RSInet ALLOW another mask to be saved.

Fixed a bug where the Product “Quantity” and Product “Code” data were being removed from the shipment if the Product was changed in the Edit Shipment Pattern action page. Going forward the “Quantity” and “Code” related to the product should be retained if a product is changed on Edit Shipment Pattern.

Added feature that indicates an Equipment is an “Idler” when submitting a New Shipment or Sales Order. This is a Client level feature available based on Shipment Regulations or Client Requirements – contact your Rep as needed.

If Enabled for your Client:

• An “Idler” checkbox will appear at the end of each Equipment box in the New Shipment Page
• If you select checkbox Equipment will be marked as “idler” for this shipment ONLY

Once shipment is submitted, the Idler indicator will be on:

• All BOLs for this shipment
• View/Edit Shipment Action for this shipment
• The EDIs sent to Carriers for this shipment
  • This will help the carriers properly indicate the “Idler” car in the shipment and apply proper pricing and services.

• Validation will prevent a shipment from being “submitted” with a Non-Standard character in any free-form data fields
• Validation Message should indicate where the Non-Standard Character is located in the New Shipment Form
• This was implemented because Non-Standard Characters can cause issues on EDI 404, and shipments may be rejected by carriers.

Exception:

• Non-Standard Characters will be allowed in the Comments Field since that is not transmitted on the EDI 404

Notes:

• Characters that are ALLOWED are “Code” 32 – 127 at http://www.htmlhelp.com/reference/charset/
• EDI 404 is the electronic version of a BOL (also called Shipment Information)

Added “Idle Days” to the Last Sighting box that is located at the top of the “Most Recent Sightings” search (available from Dashboard Search or Trace Report Actions). Reports how long the car has been Idle at current location per CLMs received.

Added the Attachment (“Add File“) feature to the View and Edit Product actions (View Product page). You can now save files to a specific product in RSInet (i.e. SDS).

NOTE: This is not available on New Product page because a Product needs to be created prior to attaching a file. 

Fixed a bug where the Time was missing from the Date/Time displayed in the “Date First Available” field on Loaded and Empty Diversion reports

Updated the Logic for the View Pattern Rates page to ONLY show Pattern Rate data if ALL Rates tied to a Pattern are both Active and Current. This will prevent displaying misleading Pattern Rate Values ($) due to missing/outdated Rate Details.

NOTE:

• Active is the standard “Status” toggle on many features of RSInet.
• Current is when the Rates’ Effective and Expiration dates encompass today’s date. 

Filters and optional Outputs have been added to the Trace Report and Grouped Trace Report pages:

Product Code:

• Displays the Product Code applied to the related Product.
• All Product Codes can seen on View Product page and can be set at New/Edit Product pages.
• Product Code is a user/client defined reference field

Days En Route:

• Displays the number of days the equipment has been moving on current trip.
• This is based on the Most Recent Shipped or Released Date compared to today’s date.

Added New “Rate Contact” feature to Contacts section to help manage the specific Contacts that provide/work Rail Rates:

View Rate Contacts page

• Provides an index view of Rate Contact details including all the options from the basic “Contact” feature.
• Rate Contact has added options for Carrier, Commodity, Type of Contact and Comments

New Rate Contacts page

• Allows for creation of New Rate Contacts
• Includes the new options for Carrier, Commodity, Type of Contact and Comments.

NOTE:

• Carrier is the list of ALL Rail Carriers stored in RSInet
• Commodity is a list of all products stored in RSInet for the specific client
• Type of Contact can be either “Account Manager” or “Pricing Manager”
• Comment is just a free form text field

Added Fields, Filters and (optional) Outputs to assist with OT-5 Management to the Equipment pages in RSInet. The New Equipment page and View/Edit Equipment Actions have a new “Loading Authority OT-5” section that contains the new entry fields for OT-5 Management. The View Equipment page has new Filters and (optional) Outputs for the related OT-5 entry fields noted below.

New Fields/Outputs/Filters are:

• OT-5 Application ID
• OT-5 Application Status
• OT-5 Application Effective Date
• OT-5 Application Expiration Date
• OT-5 Application Comments

Added Max Gross Weight Validation feature to New Shipment page. The validation – occurring after clicking the Submit button – will display a Warning Message on Preview BOL page if a shipment may be in excess of the Allowable Max Gross Weight at the Origin and/or Destination. You will have the option to go back and edit the shipment information if needed or submit with warning anyway.

Shipping Party Feature Details:

• New “Max Gross Weight” input field added to Edit/New Shipping Party pages
  • This is where you store the Max Gross Weight for this specific location (6 digit max).
• New Outputs and Filters for Max Gross Weight are on the View Shipping Parties page as well and displays the value saved to the specific Shipping Party

Pattern Feature Details:

• New Outputs and Filters for Max Gross Weight are on the View Patterns page –
  • This will show the smallest Max Gross Weight  value associated with all (Rail Serviced) Shipping Parties tied to the pattern 
  • Rail Serviced Party is Shipper, Party at Pick Up Location, Consignee and In Care of Party

Validation Feature Details:

• Validation on New Shipment page uses the smallest Max Gross Weight value associated with all (Rail Serviced) Shipping Parties tied to the pattern 
  • Same Logic for Max Gross Weight values displayed on View Patterns page as well
• Warning will appear on top of Preview BOL page if Weight entered in New Shipment + Tare Weight on related Equipment is Greater then the smallest Max Gross Weight for the pattern – otherwise you will see no warning

NOTES:

• This validation feature requires Max Gross Weight values to be set on the related Shipping Parties in RSInet to perform proper checks on a New Shipment
  • No Max Gross Weight values set in related shipping parties will ignore this check.
• This validation feature also requires a Tare Weight applied to the related Equipment used in the Shipment
  • No Tare Weight value set on related equipment then Tare Weight used equals zero (“0”)
• If Shipping Party is serviced by multiple carriers then we suggest entering the smallest value of Max Gross Weight from all carriers that service the location
• RSInet should perform proper conversions based on the U/M used in Shipment
• This is only a Warning and you have the ability to submit a New Shipment even with this warning displayed
• The Carriers (RRs) dictate the Max Gross Weight, RSI has no control over this and values should be obtained from Carriers.
• Please contact your Rep or Manager for more details or with questions

Added the “Include Round Trip” option on the Transit Report. If you run the Transit Report with Include Round Trip set to “True” it will require the data to include both the Loaded trip and the Empty return data (good for those who own or lease their cars). If you run with Include Round Trip set to “False” it will only require the Loaded trip data (good for those that use RR system cars or collect shipment data via EDI417)

Added Outputs to show the Original CLM Data that is being hidden by a CLM Mask: “Orig. Dest City”, “Orig. Dest State”, “Orig ETA Date”.

We have also updated the previously existing Outputs for “Dest City”, “Dest State” and “RR ETA”. Now named “Masked Dest City”, “Masked Dest State” and “Masked RR ETA” to differentiate from the “Original” outputs that were added.

To view this data go to the “View CLM Mask” page (“Customer SVC” section), then open the “Edit CLM Mask” action for the CLM mask you want to View or Edit.

Added a link to the “RSInet Update Announcements” in the Help section of RSInet. This links to the same Announcement page emailed when RSInet is update with New Features and Bug fixes. (i.e. this page)

Added and updated the logic on some weight related field in Trace Report, Grouped Trace Report and View Shipments pages. All of these Outputs reference the original shipment weight to display the weight in another unit of measure (U/M) or different total weight (gross/net).

New Outputs Added:

• “Weight in Kg”
• “Weight in MT”

Existing Outputs Fixed:

• “Gross Weight” – Updated logic to reference U/M when calculating Gross Weight
• “Weight in NT” – Updated logic to reference U/M when calculating Weight in NT (was previously named just “Weight in Tons”).

Filters and optional Outputs have been added to the Trace Report and Grouped Trace Report.

Fleet Path:

• This output will display the Top Level Fleet, along with all Sub-fleets that each equipment is assigned. All Fleet “layers” are displayed. Fleets and Sub-fleets can be managed in the Fleets tab.

Insulated:

• This output will display “Yes” or “No” based on selection made in the “Insulated” dropdown on the New/Edit Equipment page. This usually indicates if a Tank Car is Insulated or Not. Output will be blank in Trace pages if not selected in Equipment page.

Fixed a bug that was preventing the scheduling of saved Grouped Trace Reports for automated distribution. Users are now able to schedule Saved Reports created from the Grouped Trace Report page to be sent to contacts stored in RSInet. Accessed via the Edit Subscription Info action on the Saved Reports page.

The “Weight” field on Shipment pages has been limited to 8 characters. NOTE: If you get an error message about length of Weight field being too long please remove any non-numeric characters as needed and round to closest whole number.

Fixed a bug where emailed Loaded Demurrage reports in Excel format were NOT showing a “Total” row in each grouping. This has been corrected to show the Total Row – users may have to click the “enable editing” button in excel file after opening

The system will attempt to block ETAs with dates prior to ‘todays’ date from displaying in the Trace Report and Grouped Trace Report pages, along with any Saved Reports created from those pages. If this “block” occurs, our system will attempt to generate a Predictive ETA based on historical data collected. These “blocked” ETAs will still appear in other CLM sighting searches such as Sightings Between and Most Recent Sightings

NOTE: Predictive ETA process requires a minimum sample size and other CLM data to generate – so blank ETAs are possible if certain criteria is not met. 

The “Restrictions” field has been added to New/Edit Rate Request pages. This free-form comment type field is used to indicate any known Weight, Length, Height or Other Restrictions that need to be considered as the Rate is being constructed. This information will be displayed as an Output field in the View Rate Request page and will be Filterable. The Rate Request Response emails will also contain the Restriction data.

We have added a “Shipment Creator” option for auto-filling the Name for the Hazmat Certification Contact field when creating a New Shipment in RSInet (Hazardous Shipments only). The “Shipment Creator” option will automatically use the First and Last Name of the User submitting the Shipment to auto-fill in the Hazmat Certification Contact field on the New Shipment page. This option is in addition to the current options of “Manually Entered” (name must be manually entered every shipment) and “Global Contact” (one name used for ALL shipments).

If you would like to update your Hazmat Certification Contact setting please contact your RSI Customer Service Manager or Representative. 

Report designed to provide Actual Placement (AP) dates, Constructive Placement (CP) dates and other related data in detail. This will be the report used to view AP/CP dates on a mulicar shipment 

The “Trace Report Summary” is a snapshot of basic CLM Sighting data that provides a Count of Equipment headed to a Destination, broken down by the Current Location of the equipment.

Sample:

We have updated the look for RSInet. The layout and functionality will remain the same.

Added optional Filters and Outputs for “Lease Equipment Type” and “GL Code” to the View Lease Rider page.

Added optional input fields for “Lease Equipment Type” and “GL Code” to the New and Edit Lease Rider pages.

• “Lease Equipment Type” is a dropdown containing the same Equipment Types listed for individual Equipment.
• “GL Code” is a free-form field.

• Users are asked to review the Origin/Destination Station Information within these Patterns to ensure that the City, St/Prov or Country of the Station does not need related updates.
• The list will be accessible via a link in the Edit Party Confirmation note in RSInet (for quick review) and will also send an emailed list to the address provided for the user making the Edit (for later review).
• This process will occur for Shipping parties with the qualifiers of: Shipper, Party at Pick-up Location, Consignee & In Care Of Party – as they drive the station information in patterns.
• NOTE: Rail Station data (City, St/Prov or Country) does NOT always match the Physical Address data for the an Origin/Destination Party, therefore changes to the City, St/Prov or Country on these parties need to be reviewed to see if they should be applied to the Rail Station as well.
  • These determinations need to be done on a pattern by pattern basis.

• Users with the CLM Admin role will be able to change how the Destination City, Destination State and/or RR ETA are shown in RSInet for a specific Equipment.
• The Mask will be applied to ALL CLM Sightings for the Equipment during the date range specified (Start/End Date).
• The real, non-masked, CLM data will be displayed outside of the date range window.
• You can only have 1 Mask per Equipment.
• ATTENTION: This “Mask” data will display for ALL RSInet users at your company and also display on ALL correspondence sent from RSInet (i.e. Reports).

There are 2 ways to Start a “CLM Mask”:

• The “New CLM Mask” page itself OR via the “Create CLM Mask” action on the Trace Report.
• Selecting the “Create CLM Mask” action related to specific equipment on the Trace Report will populate the New CLM Mask page with the most recent CLM data for that equipment
• Selecting the “New CLM Mask” page link itself will provide a blank form.

Filling in New CLM Mask form:

• Equipment Number must be entered and that will then populate the Start Date and  “Original” Dest City/St/ETA fields from the most recent CLM data on file for that equipment.
• Then you can manually set the “Masked” Dest City/St/ETA fields to what you want to display for the remainder of the trip.
• The End Date will be set by the next Shipment Creation (‘*’), Release (‘W’), or Pull (‘X’) CLM received and will prevent the mask from displaying for future sightings.
• You MUST enter data in at least 1 “Masked” field, and City/St are to be used together.

Editing a Mask:

• The Edit action is available for each mask on the View CLM Masks page.
• Selecting this will allow you to change the Start Date and “Masked” Dest City/St/ETA fields.
• Once changes are saved the masks will be applied across RSInet.
• The Edit page also provides a list of CLM Sightings that are being masked.

Closing out a Mask:

• The CLM masks will automatically “End” when the next Shipment Creation (‘*’), Release (‘W’), or Pull (‘X’) CLM is received
  • This will keep the masked data for the date range but not apply mask to new sightings.
• You also have the option of Inactivating the Mask
  • This will revert to the original CLM data for the date range (un-masked).

Added Output and Filter for “Load Limit” to the View Shipments page. This shows the maximum weight of commodity that can be added to the equipment. Data pulled from the Load Limit field on View Equipment pages.

Added Output and Filtering options to the View Pattern Rates page for each Rate’s “Created” & “Modified” Dates – Created Date 1, Created Date 2, Created Date 3, Modified Date 1, Modified Date 2, Modified Date 3.  These are optional and can be added via the Filters tool (output tab). This supplies data on the Initial Created Date and most recent Modified Date.

Fixed a bug where inactive contacts were being sent correspondence (Emails, Faxes) from RSInet for data such as BOLs and Reports.

Fixed a bug where the “Output Type” of Saved Reports were being marked with an type of “Undefined” which prevented the report from being Run, Edited and Distributed when set with that “Output Type”.

 Updated Filtering for Equipment #s, BOL #s and/or FB #s on select pages in RSInet. This enhancement will allow you to filter for multiple items without the need for a separator (like a “;”). This feature was already in place for Equipment # searches (“Equals” only) on View Shipments page, but has been expanded:

Enhanced View Freight Bills page filters added:

• FB # [Equals & Contains]
• Equipment [Contains]
• BOL # [Equals & Contains]

Enhanced View Shipments page filters added:

• Equipment [Contains]
• BOL # [Equals & Contains]

Added rules that will automatically close/inactivate Service Logs based on CLM data:

“Common Delay” Service Logs will now Auto-Close when we get any sighting after the CLM that triggered the Common Delay log to open – [At that point the car is considered beyond the “delay” that caused log to open].

“Car in Interchange” Service Logs will now Auto-Close when we get any sighting after the CLM that triggered the Car in Interchange log to open AND as long as the Sight Code (SC) is not an Interchange Code (“R” or “J”) – [At that point the car is considered to be beyond the interchange point; if we received non-interchange Sight Codes]

New feature that allows users to set a Time Zone to a Pattern or when submitting a New Shipment. RSInet data is set to Eastern Time by default.

Pattern Level: Users can Create New or Edit Patterns to set a Time Zone in the Routing Information section of pattern pages. Any new shipments entered using that pattern going forward will be created with that Time Zone (unless changed on New Shipment page when creating the shipment). The “Ship Date” field will be adjusted to the current time for the time zone selected – based on when the New Shipment page was access.

New Shipment Level: Users can change the Time Zone on the New Shipment page in the Shipment Options section prior to submitting the Shipment. By default, the Time Zone in New Shipment page is set to the Time Zone set on the Pattern (see “Pattern Level”)  or it will be set to Eastern if not set on Pattern. When a Time Zone is changed on the New Shipment page, the  “Ship Date” field will be adjusted to the current time for the time zone selected – based on when the New Shipment page was access.

There are also related outputs and filters on the View Shipments and View Patterns pages

New Feature to track and calculate Demurrage on Empty Cars. While the outcome is similar to the Loaded Demurrage Reporting tools, the process to track and collect data is much different: Empty is using SPLC (location) data directly to trigger demurrage (shipment not needed). Loaded is using Shipments and related Shipping Parties created within RSInet to trigger demurrage.

The Manage Empty Demurrage page is under the Customer SVC section of the RSInet menu. This page will list all Active Demurrage Settings and allow you to Edit, View and Delete them using the actions next to each setting. Also on this page is a “Create” button, click that and it will take you to a page to create the Empty Demurrage Settings and Rules.

To Create a New Setting, Select the Days that the location is serviced in “Switch Schedule”; Enter a “Station State” (will populate the Station City dropdown); select the “Station City” from dropdown. At this point RSInet will provide the SLPC for that location – you can only create one Empty Demurrage Setting for a SPLC. Now enter the “Initial Sight Code(s)” that will trigger the start of the demurrage clock (starts when a CLM matching the Initial Sight Code and the SPLC above is received); then select a “Release Sight Code” from dropdown to stop demurrage clock (stops when we get a CLM matching the Release Sight Code and is after the Initial Sight Code that started the clock).

Now you can add Demurrage Rules via the “Add Empty Demurrage Rule” button – you can add as many Rule “Tiers” as you want, but days must be continuous between the tiers (no overlap or gaps in days). First select the “Equipment Types” you want to collect demurrage data for. Next select the “Start Days” – this is the range of days to apply this rule tier (if “3 to 8” then demurrage clock starts on day 3 and ends on day 8). Also, if using multiple Rules this is where you need to ensure continuous days. You can enter an optional “Placed Cut Off Time” that will indicate the time of day the Carrier no longer services the location. You can then enter the “Charge Amount” – this is the amount per day, per car that will be accrued. Finally you can enter a Credit Amount (first tier only) – this will allow you to give credits for a car released prior to the Start Days in tier 1.

You can now add any additional Rule Tiers following the same instructions above – using continuous days. Save once complete.

The Empty Demurrage Report can be found under the Reports tab in the RSInet menu. You can adjust the “Demurrage Report Dates” to your needs for reporting – Demurrage is generally calculated on the 2nd of each month, for the previous month so “Last Month” is the default option. Then you can run in your browser by using the Submit button or use Download to Excel to export directly. You can also adjust the Output options or save a Demurrage Report using the related tabs in the filter tool. The Report output is Grouped by location (SPLC) and provides the total charges and credits for a single equipment, along with other supplemental data.

If you have further questions please reach out to your RSI Logistics Representative

Fixed a bug where Auto-Open Customer Service Logs were not properly applying the “Car In Interchange” Service Log Type when the corresponding logic was met.

• “Date Placed at Shop” Field added to Shop Details. This can store the date the car was delivered to the shop.
• “Save and Create Shipment” button added to View/Edit Maintenance Log page. Takes the user to the New Shipment page while saving the Maintenance Log. Also Equipment from the Log is loaded in the New Shipment page by default (removable)

Automation:

• Update ‘Car Status’ Dropdown automatically to “Complete” when the ‘Date Released’ field is filled with a valid date
• Update ‘Car Status’ Dropdown automatically to “At Shop” when the ‘Date Placed at Shop’ field is filled with a valid date
• Update the “Date Placed at Shop” field with the date of the first placement CLM when Placement (“Y” or “Z” sight code) is after the date stored in “Date Sent to Shop”, AND current Car Status is “In Route”
• Update the “Date Released” field with the date of the first Release CLM when Release (”W” sight code) is after a Placement CLM “Y” or “Z”, AND current Car Status is “In Route”, “At Shop” or “Completed”

Notes:

• Maintenance Logs must be “Active” for this process to update them.
• This procedure will override any existing dates if new data triggers an update.
• This automated data is updated periodically throughout the day, therefore will not show immediately after adding data that would trigger the updates.

New feature that allows users to update Customer Service Logs in batches. Especially usefully if multiple cars are moving together and require the same updates to the related Service Logs.

For users with access:

The “View Service Logs” page will have check-boxes next to each CS Log (row) and an “Update” button at the top of the page. Select the logs you want to edit by marking the associated check-boxes and click the “Update” button. You will be sent to a new “Edit Multiple Service Logs” page that shows the related Equipment and Log IDs you will be updating. There will also be multiple CS Log options to update en masse. Select the option(s) you want to update by marking check-boxes, then make a selection or enter data in related field. Click the “Update” button on the bottom of the page and that will save the logs with selected data and will put you back into the View Service Logs page once completed.

Notes:

• The Filters tool (funnel button) will allow you to find groups of logs based on criteria searched (i.e. all cars with open logs on BNSF in Chicago, IL)
• Feature is limited to those users with the “Customer Service Admin” role (i.e. those who can currently Edit a CS Log)
• Options in the Edit Multiple Service Logs must have associated check-box selected in order to save edit/changes entered

We have added enhancements to the Demurrage Reporting features in RSInet to allow for “Tiered” pricing. This will allow you to set different demurrage charge amounts ($) for different date ranges in the Demurrage Settings on a Shipping Party. Prior to this there was only 1 charge amount per Shipping  Party. Minor updates to the Demurrage Report itself were applied – mostly to capture correct calculations/dates, and update the notes to include the rules for each tier. Example based on screen shot below: If a car sat for 23 days you would see a demurrage charge of $825 on the Demurrage Report. Tier 1 starts on day 7 so they get 6 free days. Then 7 days of charges in Tier 1 ($175). Then 7 Days of charges in Tier 2 ($350) and 3 Days of charges in Tier 3 ($300).

The transition from using the Shipping Party Qualifier of “Ship From” (SF) to the use of the Qualifier “Party at Pick-Up Location” (PU) in RSInet will be finalized. Containment Actions took place March 2016 to ensure EDIs and Waybills from RSI met the BNSF’s Waybill Requirements.

The transition to “Party at Pick-Up Location” as a system wide change is due to EDI Standards for Rail. These standards list “Party at Pick-Up Location” as the proper Qualifier on Carload Shipments to indicate the ‘Location that physically handles the shipment at origin if the “Shipper” is not physically at origin’. While very similar, the Qualifier of “Ship From” should be used for Intermodal Shipments.

This final step includes (1) ensuring there is a PU party for every SF party in all RSInet patterns, (2) removal of all SF parties from all RSInet patterns and (3) removal of any process to add SF party back to RSInet. Historical Shipments will keep the “Ship From” qualifier (if present) to match the associated waybill on file with the carrier(s). Ship From will continue to be reportable from RSInet, a requirement for Historical Shipment data. This final step has been in trials using actual shipment data.

New Filters and Outputs have been added to the View Patterns page. These are features you access by using the filter image funnel link, or when you edit a saved report in RSInet. Please refer to the image below for a list of all new Filters & Outputs.