RSInet Release Announcement Archive

These are Release Notes related to past releases. The most recent release is located in the “RSI Release Announcement page”.
Previous Enhancements and Bug Fixes for RSInet
Title RSInet Section(s) Description Go Live Date Release Version
Days en Route Functionality Restored Reports

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)

 

10/15/2019 19.7
Transit Detail Enhancements Reports

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

 

10/15/2019 19.7
Pipeline Report Enhancements Reports

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

 

10/15/2019 19.7
Currency Dropdown Enhancement Accounting

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.

 

10/15/2019 19.7
Rate Contact Enhancement Contacts Added Filters and optional Outputs to the View Rate Contacts page related to Creating and Modifying related contacts. Fields and Outputs added:

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

 

10/15/2019 19.7
Updated Closed Date Logic Shipments

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.

 

10/15/2019 19.7
Net Tons Bug Fix Rates

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.

 

10/15/2019 19.7
EW Date Bug Fix Shipments

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.

 

10/15/2019 19.7
Fleets Name Validation Fleets

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

 

10/15/2019 19.7
Grouped by Bug Fix Reports

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.

 

10/15/2019 19.7
Diversion Page Form Update Diversions A few minor changes have been made to the Diversion pages (New, Edit and View):

  • 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 

 

8/14/2019 19.6
Outage Table Updates Equipment

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 

 

8/14/2019 19.6
 Ship Sales Order “Legend” bug fix Shipments

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.

 

8/14/2019 19.6
ETA Uniformity Enhancement Reports

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

 

8/14/2019 19.6
Rate Freight Terms Enhancement Rates

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.

 

8/14/2019 19.6
Reporting Enhancements Multiple

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.

8/14/2019 19.6
Temp/Customer Car Drop Code Enhancement Equipment

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.

 

8/14/2019 19.6
Batch Update Equipment Bug Fix Equipment Fixed a bug where the “AAR Type Code” field in Equipment pages was not saving data when using the Batch Update Equipment Tool. A checkbox was added to the field to facilitate the saving process properly

  • 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.

 

6/18/2019 19.5
Days En Route Logic Update Reports

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.

 

6/18/2019 19.5
Predictive ETA Logic Update Reports

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.

 

6/18/2019 19.5
Equipment Description Reporting Feature Reports

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.

 

6/18/2019 19.5
Inactive Contact Enhancement Contacts

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.

 

6/18/2019 19.5
Insert Multiple Equipment Enhancement Shipments

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.

 

6/18/2019 19.5
BOL Enhancement 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.

 

5/3/2019 19.4
Accrual w/o Invoice Reporting Feature Reports

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. 

 

5/3/2019 19.4
Empty Dispo Enhancement Shipments

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

 

5/3/2019 19.4
RR Shop Party Feature Patterns

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.

 

5/3/2019 19.4
Idler Rate Accrual Feature Rates Added the ability to create a Separate Idler Car Rate in RSInet and have it be part of the Total Freight Accrual for shipments generated in RSInet.

  • 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.

 

5/3/2019 19.4
Rate Request Email Bug Fix Rates

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

 

5/3/2019 19.4
Volume Value Bug Fix Shipments

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.

 

5/3/2019 19.4
CLM Tab Bug Fix Shipments

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.

 

5/3/2019 19.4
View Maintenance Details Enhancement Maintenance

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.

 

3/15/2019 19.3
DOT Code Enhancement Equipment

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:

“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.

 

3/15/2019 19.3
AAR Code Feature 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 

 

3/15/2019 19.3
Shipment Load Number Feature Shipment / Trace Report

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.

 

3/15/2019 19.3
Shipment Volume Feature Shipment / Trace Report

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.

 

3/15/2019 19.3
Equipment Type Enhancement Equipment

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

 

3/15/2019 19.3
Help Videos Bug Fix Help

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.

 

2/27/2019 19.2
Lease Rider Equipment Sorting Enhancement Equipment Lease Updated the logic for the “Add Equipment” section of the View and Edit Lease Rider action page (View Lease Rider page).

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

 

2/27/2019 19.2
Equipment Reporting Enhancement Equipment Added Fields to the New and Edit Equipment pages for recording “Hatch Type” and “Gate Type”.

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

 

2/27/2019 19.2
CLM Diversion Code Functionality Trace/Dashboard

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)

 

2/27/2019 19.2
Group Trace ‘Grouping’ Enhancement Reports

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

 

1/16/2019 19.1
Report Order Updated Data Visualization

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

 

1/16/2019 19.1
Gasket / O-Ring Field Enhancement Equipment

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.

 

1/16/2019 19.1
Pattern Validation Enhanced Patterns

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.

 

1/16/2019 19.1
CLM Mask Bug Fix Customer SVC

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.

 

1/16/2019 19.1
Shipment Pattern Bug Fix Shipments

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.

 

1/16/2019 19.1
Idler Car Feature Shipments

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.

 

1/16/2019 19.1
Shipment Validation Enhancement Shipments Added Validation to the New Shipment page that will prevent Non-Standard Characters from being submitted.

  • 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:

 

1/16/2019 19.1
Last Sighting Enhancement Equipment Searches

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.

 

10/16/2018 18.4
Attachment Expansion Products

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. 

 

10/16/2018 18.4
Demurrage Report Bug Fix Reports

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

 

10/16/2018 18.4
Pattern Rate Logic Change Rates

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. 

 

10/16/2018 18.4
Output & Filter Expansion Trace Reports

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.

 

10/16/2018 18.4
Rate Contact Management Contacts

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

 

10/16/2018 18.4
OT-5 Management Equipment

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

 

10/16/2018 18.4
Max Gross Weight Validation Multiple

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 ServicedShipping 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

 

10/16/2018 18.4
Transit Report Update Reports

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)

 

10/16/2018 18.4
CLM Mask Enhancement Multiple

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.

 

10/16/2018 18.4
Release Announcements Dashboard/Menu

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)

 

10/16/2018 18.4
Trace Report Outputs Addition Trace Reports

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

 

10/16/2018 18.4
New Filters & Outputs Trace Reports

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.

 

6/21/2018 18.3
Emailed Group Trace Report bug fix Group Trace Report

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.

 

6/21/2018 18.3
Weight Field Limitation Shipments

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.

 

6/21/2018 18.3
Totals missing from Demurrage Report Loaded Demurrage Report

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

 

6/21/2018 18.3
Prevent ETAs with dates in the past Trace Reports

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

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

 

6/21/2018 18.3
“Restrictions” Field, Filter and Output Rate Requests

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.

 

6/21/2018 18.3
“Shipment Creator” Name for Hazmat Cert Contact New Shipment

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. 

 

6/21/2018 18.3
Placement Date Report Reports

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 

 

6/21/2018 18.3
New “Trace Report Summary” report Reports

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:

Trace Report Sum

6/21/2018 18.3
Updated RSInet Look All

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

 

4/27/2018 18.2
New Fields and Filters Lease Riders

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.

 

4/27/2018 18.2
Patterns related to Party Edit Patterns / Shipping Parties New feature when the City, St/Prov or Country of Origin/Destination Shipping Parties is edited in RSInet the system will provide a list of Patterns that are related to the Edited Shipping Party.

  • 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.

 

4/27/2018 18.2
CLM Data Masking Trace Report / Dashboard searches New feature allows for the “Masking” of select CLM Sighting data for a Trip.

  • 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).

 

4/27/2018 18.2
“Load Limit” Output and Filter added View Shipments

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.

 

2/9/2018 18.1
 “Modified” & “Created” Outputs/Filters  View Pattern Rates

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.

 

2/9/2018 18.1
Inactive Contacts Bug Fix Contacts

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

 

2/9/2018 18.1
“Output Type” Bug Fix in Reports  Saved 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”.

 

2/9/2018 18.1
 Enhanced Filtering  All (filter tool)

 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]

 

2/9/2018 18.1
 Implement “Auto-Close” on CS Logs Service Logs

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]

 

2/9/2018 18.1
Time Zones on Shipments  Shipments / Patterns

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

 

2/9/2018 18.1
 Empty Demurrage Report Reports

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

 

2/9/2018 18.1
Fixed bug with “Car In Interchange” CS Log Customer Service Logs

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.

 

8/17/2017 17.6
Automation features for Maintenance Log Details Maintenance Logs Fields and Features:

  • “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.
8/17/2017 17.6
Update Service Logs en masse Customer Service Logs

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
8/17/2017 17.6
Block ETA on Placement Sightings (CLMs) Trace Report This bug fix will prevent erroneous ETAs from showing for equipment that are already “Placed”. An ETA for a equipment that completed its trip (“Placed”) is not accurate, as the equipment has already “Arrived”. 7/7/2017 17.5
Freight Bill Summary (tab) View Shipments / Freight Bills This new feature will display a Summary for a specific shipment that shows the Freight Bills received compared to the Equipment on the shipment, including Freight Accruals. Tab will include very basic Shipment and Freight Bill info. This is accessed via the View or Edit actions on the View Shipments page. 7/7/2017 17.5
“Location Of Occurrence” for Logs View/New Service Logs When a Customer Service Log is created (opened) this new feature will capture the City and State from the last CLM sighting RSI has on file for the equipment and create a “Location of Occurrence” for the Log. This should represent the last known location for the equipment when the Service Log was triggered. An Output and Filter added to the View Service Log page will help filter and report on this data. You can also see the data in the Service Log itself via the Edit or View action on View Service Logs. The Location of Occurrence will be left blank if no sightings exist for the equipment. 7/7/2017 17.5
Use “Estimated” Weight Qualifier on all “Weigh In Route” shipments New Shipment When a shipment is entered with an option of “Weigh In Route”, the weight qualifier will be set to “Estimated” automatically (N704 = “E”). This will help prevent instances where “Weigh In Route” requests were not completed by the carrier because the weight qualifier was set to “Actual” (net) or “Gross”. Per EDI Notes: “The presence of actual net weights or gross weights in N704 (Code values ‘N’ or ‘G’). indicate that the car has been weighed. A weight qualifier indicating estimated weight in N704 (Code value ‘E’) indicates that the car has not been weighed” 7/7/2017 17.5
Fleet Groups Fleets This “Fleet Groups” feature was added to allow clients to group similar Fleets together to enhance reporting services. This enhances the reporting available in Data Visualization features only (no outputs or filters added to RSInet itself). Users can assign a Fleet Group on the Manage Fleets page by selecting the Fleet you want to update then using the “Add/Edit Group” button to set and save.  If you would like to use this feature, please reach out to your Customer Service Representative for assistance in adding your Fleet Groups to the system. 5/19/2017 17.4
Equipment Output/Filter for “Date Inactivated Equipment Added ability to report and filter on the Date that a piece of Equipment was marked as “Inactive” in RSInet. This is available as standard filter and an optional output on the View Equipment page. Field will contain the date the car was last marked inactive only if available (blank if never inactivated). 5/19/2017 17.4
CLM Location Name Manager CLM / Car Sightings (Multiple) This new feature will allow a “Replacement” name to be set in RSInet for a particular Rail Station (City/St) when dealing with the CLM Rail Car sightings and reporting. For Example, if your company likes to use the city name of “East St Louis, IL”  for the Rail Station that is actually called  “Granite City, IL”, then the system can automatically replace Granite City with East St Louis for CLM sightings in RSInet. This will subsequently update any CLM based reporting with that “Replace” name as well. These Replacements are limited on a client by client basis – so you will not see other client’s “Replacements”. If you would like to use this feature, please reach out to your Customer Service Representative for assistance with setting the “Replacement” Station info in RSInet. 5/19/2017 17.4
CLM Tab Bug Fix View/Edit Shipment Actions Fixed a bug where the “CLM” Tab for a shipment was not showing the CLMs related to the referenced shipment. The CLM tab is located via the “View”/”Edit” actions available on the View Shipment page 5/19/2017 17.4
Removed Duplicate “Sub-Lease” Output View Lease Riders Fixed a bug were a duplicate “Sub-Lease” output column was showing as an optional output. 4/14/2017 17.3
Updated Logic on “Constructive Placement” Output View Shipments Fixed a bug where the system was occasionally showing a “Constructive Placement” date that was not within the shipment/trip being referenced. The logic that displays the date in the “Constructive Placement” output column was updated. The “CP” date must now fall between the Ship Date and the Actual Placement date, otherwise the date will be left blank. 4/14/2017 17.3
Party Groups View Shipping Parties This “Party Groups” feature was added to allow clients to group similar parties together to enhance reporting services. This allows a user to filter on a Group rather then having to list out multiple (individual) parties into the RSInet filers. This is very helpful where parties are part of the same parent company, but are separate parties listed in RSInet. Filtering for the Party Group is available on the View Shipping Parties page. This also enhances the reporting available in Data Visualization features. If you would like to use this feature, please reach out to your Customer Service Representative for assistance in adding your Party Groups to the system. 4/14/2017 17.3
Tiered Demurrage Reporting Demurrage

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

Demurrage Image

4/14/2017 17.3
Product Groups Products This “Product Groups” feature was added to allow clients to group similar products together to enhance reporting services. This allows a user to filter on a Group rather then having to list out multiple (individual) products into the RSInet filers. This is very helpful where products are essentially the same, but are separate products listed in RSInet. Filtering for the Product Group is available on the View Product, View Shipments and View Pattern pages. If you would like to use this feature, please reach out to your Customer Service Representative for assistance in adding your Product Groups to the system. 3/24/2017 17.2
Fleet Sizing Model Reports The “Fleet Sizing Model” was developed to help analyze your Rail Fleet allotment and suggest adjustments. This interactive report analyzes historical shipment data for each of your actively used RSInet patterns, based on a user defined date range (preset for current year). You can also filter down further to look at a specific Origin, Destination or specific Fleet using the additional filters on the page. The Fleet Sizing Model will be available in the Report section of RSInet for those clients and users who have access. After setting your filters and running the report you can edit most of the data columns based on known or anticipated changes to volume/Moves, Transit/Turn Times and other numerical fields. Users can also adjust Maintenance, Seasonal and Storage Allowances to better estimate the cars that may be out of service for some time. 3/24/2017 17.2
“Sighting Status” output bug fixed Trace Report (s) Fixed a bug related to the Output “Sighting Status” that caused errors with saved/scheduled reports. Sighting Status output is a quick summary of the status of the shipment based on CLM sightings. You will either see “Placed” (Y or Z sighting code) or “In Transit” (any other sighting code). 2/17/2017 17.1
“Shipment Type” dropdown menu bug fixed Patterns Fixed a bug related to the “Shipment Type” dropdown menu. This error prevented selecting “Please Select One” option after a Shipment Type was set. Users can now de-select any options set in the “Shipment Type” dropdown menu. 2/17/2017 17.1
Future rates now available in “Select a Rate” tool Patterns Users will now see “Future” rates in the “Select a Rate” tool that is used to add rates to patterns. Previously this was limited to “Current” rates only. A “Future” rate is any rate that has an effective date after ‘today’. A “Current” rate is any rate where ‘today’ falls within the Effective and Expiration date range. 2/17/2017 17.1
“Request Type” now a required dropdown menu item Rate Requests The “Request Type” field in Rate Request pages has been updated to a dropdown containing the previous options, Actual & Estimate, along with a new default “Select a Request Type”. A selection of Actual or Estimate is required. This will help ensure that the rate type is correctly defined when Rate Request is submitted. 2/17/2017 17.1
“Ship From” party to “Party at Pick-Up Location” Transition – Final Phase Multiple

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.

2/17/2017 17.1
Filter and Output Additions Multiple New Filter and Outputs have been added to multiple RSInet pages. These are features you can 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 and what pages they have been assigned. filter and output adds 17.1 2/17/2017 17.1
“Dispute” Widget Fix Dashboard A correction to the logic that pulls in Freight Bills into the Dispute Widget on the Dashboard. Will show all Freight Bills in Dispute status that are assigned to your user 12/29/2016 16.8
“Fleet” Filter fix View Service Logs The “Fleet” filter on the View Service Logs page has been updated to add the filtering options for “Equal (with Subfleets)” and “Not Equal (with Subfleets)” 12/29/2016 16.8
Freight Accrual and Freight Paid Reporting Enhancements Reports If RSI manages freight on your behalf, there will be a set of 4 new Accrual and Paid reports that have a multitude of filtering options. See brief description to each of the New Reports below. Contact your Customer Rep if you want more details or would like to schedule report distribution.new-report-summary 12/29/2016 16.8
“Shipment Type” field added to Pattern Pages Patterns / Data Visualization “Shipment Type” dropdown menu has been added to the New/Edit Pattern pages. Users can categorize the “Shipment Type” at the pattern level. Shipments created from these patterns will be set with this “Shipment Type”. Using this feature will provide additional summarizing abilities on Data Visualization reporting tools in RSInet 12/29/2016 16.8
Filter and Output Additions Multiple New Filters and Outputs have been added to multiple RSInet pages. These are features you access by using the filter link (funnel), or when you edit a saved report in RSInet. Please refer to the image below for a list of all new Filters & Outputs and what pages they have been assigned.16-8-filters-and-outputs 12/29/2016 16.8
Filter and Output additions Multiple New filters and outputs have been added to multiple RSInet pages.  These are features you access by sing 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 and outputs and what pages they have been assigned. 16-7-filters-and-outputslarge2 9/16/2016 16.7
“Freight Rate” Report added Reports Report showing Rate Details, Basic Pattern info and number of moves (shipments) for each pattern in RSInet.  Pattern must have rates tied to it and must have had shipments entered using the pattern during the date range set in the report in order for the lane data to display. 9/16/2016 16.7
Edit Maintenance Log Bug Fix Reports Fixed a bug where user was not able to save a maintenance log if the associated equipment was inactive.  Now able to edit and save maintenance logs independent of the status of the equipment. 9/16/2016 16.7
Attachments (“Files”) Functionally Maintenance & Service Logs RSInet users with “Admin” rights for the View Maintenance Logs page and the View Service Logs pages are able to upload/save and download files (attachments) from associated logs. 9/16/2016 16.7
“Car in Interchange” Service Log added Customer SVC The new Customer Service Log type “Car In Interchange” has been added to indicate a service delay while Equipment is being transferred between 2 carriers.  This Auto-Open service log will ope non Equipment that (1) has not moved in 48 hours and (2) has either the Junction Delivery (J) or Junction Received (R) sight codes. 9/16/2016 16.7
“Party at Pick Up Location” added to Reports Multiple Output columns for “Party at Pick Up Location” have been added to the Detention Report & Freight Accrual Report in RSInet.  This is for the upcoming transition from “Ship From” to “Party At Pick Up Location” – see note below**. 9/16/2016 16.7
“Ship From” Party  Qualifier disabled Shipping Parties The “Ship From” check box has been removed from the Qualifier section of Shipping Parties in RSInet.  The “Party at Pick Up Location” Qualifier is to be used in place of “Ship From” for indicating the company that physically handles the shipment at rail origin, when Shipper is not at rail origin.  Does NOT effect Shipping Parties previously set with the “Ship From” Qualifier.  This is for the upcoming transition from “Ship From” to “Party at Pick Up Location” – see note Below**. 9/16/2016 16.7
Party At Pick-Up Location Filter and Output additions Multiple The Filters and Outputs for the shipping party qualifier of “Party at Pick-Up Location” have been added to the View Patterns, View Shipments, View Diversions & Trace Report pages. Users will be able to use these features to find associated shipping parties, similar to the current process for Ship From parties. 8/19/2016 16.6
View Pattern page Filter and Output additions View Patterns

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.

new 16.6 filters and outputs

 

8/19/2016  16.6
Enhanced “EDI Info” Widget Dashboard The “EDI Info” Widget has been enhanced to better clarify the Status of EDI Shipments sent from RSInet – Looking specifically at “Today” and “Yesterday”. The widget will display counts of EDI Shipments: Submitted, Accepted (without errors), Accepted (with error/corrections), Rejected, Unknown Status. Along with showing shipments With and Without waybill #s received from Railroads. See screen shot for details.EDI counter annoucements page 7/22/2016 16.5
More detail added for EDI Acknowledgements View Shipment Acknowledges* Removed the generic “Ack Code” & “Comment” columns and replaced with more specific columns for the different types of Acknowledgements (997 & 824). New Fields: 997 Ack Code, 997 Comment, 824 Ack Code, 824 Comment. *This feature also translates into the EDI History section in the Edit Shipment page/action. 7/22/2016 16.5
Enhanced Shipment Volume Report Reports Added Filters for: L/E Status, Creator, Freight Accrual, Unit Train, Multi-Product and Rate Contract (has data). Also added was the ability to Group on multiple criteria. Also fixed some formatting and column name issues. 7/22/2016 16.5
Suppress (Block) Customer Service Logs Manage Fleets, Service Logs Ability to suppress Auto-Open Customer Service Log from generating for specified fleets and the related equipment. Feature can be toggle on/off at the “Manage Fleet” page by clicking the “View Details” button for the selected fleet, clicking the “Edit” button, then using the “Monitor Fleets”  check box and saving. Checked = Service Logs are Enabled for equipment in this fleet; Unchecked = Service Logs are Suppressed for equipment in this fleet. Newly Created fleets will have the feature enabled by default. Also upon release of this feature, all existing fleets will be enabled.  Users will have to manually toggle the feature. 7/22/2016  16.5
Disclaimer Shipments Disclaimer has been added to all Shipment Submission pages (New Shipment, Ship Sales Order, Preview BOL, etc.). Disclaimer: “By submitting this shipment, I ( [users first & last name] ) declare that the contents of this shipment are fully and accurately described above and are in all respects in proper condition for transport according to applicable governmental regulations. This is in accordance with 49 CFR § 172.201.” 7/22/2016 16.5
Filtering Tool Added to RSInet Pages Patterns and Contracts The filtering tool filter image has been added to the “View Account Codes” & “View Demurrage Contacts” pages in RSInet. This is the same filtering/report creation tool that is available in most other pages in RSInet.  5/13/2016 16.4
New Filters and Outputs View Patterns New Filters and Outputs have been added to the Report Filtering and Page Filtering options available in RSInet. 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, and affected pages. filters and outputs v2 16.4  5/13/2016 16.4
Enhanced Excel Output All Sections The Excel output feature in RSInet has been upgraded to handle filtering and sorting natively –  without the need for reformatting outputting the data. This replaces the previous Excel output in most RSInet pages and RSInet generated reports. There are some limitations of this feature with “Canned” reports generated from SQL (i.e. Transit Report, Shipment Volume) 5/13/2016 16.4
File Attachments Leases The tool to attach files has been added to the Edit Lease pages in RSInet. You can now upload files to the Lease saved to RSInet.  5/13/2016 16.4
STCC in Edit/View Shipment View Shipments The STCC has been added to the Product Information Section of the View/Edit Shipment page (Accessed from: Shipment Tab -> View Shipments Page/Link -> Edit (or View) Shipment Action). STCC-shipment 4/8/2016  16.3
 15 Minute Increments for Reports Saved Reports The Report Scheduler is now available to send reports in 15 minute increments. Previously set in 1 hour increments. (Accessed from: Reports Tab -> Saved Reports Page/Link -> Edit Subscription Info Action) 4/8/2016 16.3
Fixed Sorting for Attachment Dates Multiple Pages Fix was put in place to address an issue with how the ‘Date Created’ & ‘Date Modified’ columns were sorting for File Attachments. This fix is for any page where there is the File Attachment option. 4/8/2016 16.3
Shipment History Tab View Shipments Shipment History Tab added to Edit Shipment Action. This will show the history of Edits, Cancellations and Reinstatements for the shipment. Along with the user who performed them and any reason given. (Accessed from: Shipment Tab -> View Shipments Page/Link -> Edit (or View) Shipment Action). shipment history cancel 16.3 4/8/2016 16.3
New Filters and Outputs Multiple Pages New Filters and Outputs have been added to the Report Filtering and Page Filtering options available in RSInet. 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 list of all of the new Filters, Outputs, and affected pages.  filters and outputs v2 16.3  4/8/2016 16.3
Larger View of “Canned” Reports Reports (non-trace) The display of the “Canned” Reports in RSInet has been enlarged. Pop-up view removed. These are all the reports that appear below the “Saved Reports” link under the Reports tab. Sample of “canned” reports are the ‘Pipeline Report’, Shipment Volume & Detention Report. All reports similar to these will have expanded views in RSInet. 4/8/2016 16.3
STCC in Edit/View Patterns View Patterns The STCC has been added to the Product Information Section of the View/Edit Pattern page (Accessed from: Patterns Tab -> View Patterns Page/Link -> Edit (or View) Pattern Action). STCC pattern information 16.3 4/8/2016 16.3
Set Specific Origin/Destination Patterns Ability to change the Origin City, St, Country and/or Destination City, St, Country at the pattern level, without having to change that info on a party tied to that pattern. All Origin/Destination data was previously driven by the data saved to parties tied to a pattern. Now you can override that Origin/Destination data in the Routing Section of the Edit Pattern page. By default the Origin/Destination data will pull from the Origin/Destination Party info, but that can be overridden by this feature. Userful if the Rail Station City is different from the Physical Location City.  add shipping party information 16.3 4/8/2016 16.3
New Filters and Outputs Multiple Pages New Filters and Outputs have been added to the Report Filtering and Page Filtering options available in RSInet. 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 pdf attachment below for list of all of the new Filters, Outputs, and affected pages.   Added Fields and Filters 16.2  3/4/2016 16.2
Equipment Lease Rider Report Reports A new report that outputs Active Equipment with current Lease Rider Information. This is located in the Reports tab in RSInet. 3/4/2016 16.2
Lading Value Corrections New Shipments Calculation corrections made to this function to properly account for the different units of measure (KG, Lbs., MT). 3/4/2016 16.2
Rate Creation Details Rate Details Added “Created Date” and “Creator Name” to the Rate Details in RSInet. This may not necessarily be the creator of the Rate itself. 3/4/2016 16.2
Attachments Enhancement Multiple Pages Date Created and “Date Modified” details added to the columns displayed for attachments in RSInet. This will display on any page that has an attachment option. Will show when the attachment was added or changed.  2/12/2016 16.1
New Filters and Outputs View Equipment  New Fields added to the New/Edit Equipment pages – see PDF below. Filters and Outputs options have also been added to the View Equipment page for these added fields. view equipment new fields 16.1 2/12/2016 16.1
New Service Log Type Customer Service Logs Customer Service Log type of “Load Shift” has been added to the Auto-Open Customer Service log process. The system will create a more detailed Bad Order (B) log when we receive a CLM that meets the criteria. This will also be available for manual selection in the Customer Service logs. *note that feature availability depends on RSI services provided.  2/12/2016 16.1
‘Run It Now’ Report Option Reports Ability to run a Saved Report on demand from RSInet that will be sent to your email address. The “Run It Now” button will be on the Edit Subscription page for a Saved Report – in the Subscription Schedule section. run it now (2) 16.1  2/12/2016 16.1