|
What's New
|
Top Next |
|
|
| Improvements
|
| · | Added compatibility for Norfolk Southern's new FTP server with a more robust implementation that allows the update to be installed before the switch to the new FTP server.
|
| · | Updated report writing component (ActiveReports 2) to the latest version to improve compatibility with Microsoft Windows security updates.
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Client. Will work with 5.11.XX Server. Server 5.11.06 update is highly recommended if you use the Railcar Utilization reports.
|
|
|
| Improvements
|
| · | Added compatibility for Norfolk Southern's new FTP server.
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Client. Will work with 5.11.XX Server. Server 5.11.06 update is highly recommended if you use the Railcar Utilization reports.
|
|
|
| Improvements
|
| · | Several fields were added to the Problem Logs custom report dataset to show the railcar's last reported location, origin, destination, event date/time, load/empty status, and pool.
|
|
|
| Notes
|
| · | Server only update for 5.11.XX Server. Will work with any 5.11.XX Client.
|
|
|
| Bug Fixes
|
| · | Program icons not displaying properly.
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Client. Will work with 5.11.XX Server. Server 5.11.06 update is highly recommended if you use the Railcar Utilization reports.
|
|
|
| Bug Fixes
|
| · | The count of shipments by pool on the Railcar Utilization reports, in some situations, was inaccurate. The reports were counting the number of shipments in a pool based on the number of shipping instruction records that were tagged with the pool. Shipping instructions are tagged with a pool when they are entered manually or imported. Whatever pool the railcar is assigned to at the time the shipping instruction is entered or imported is tagged to the shipping instruction. This usually gave accurate counts. However, sometimes a user may wish to change what pool a railcar was assigned to and they want the effective date to be prior to the current date. There was no way to change the pool on the shipping instruction because the field is locked. The pool field will still be locked on the shipping instruction window, but the shipment counts on the Railcar Utilization reports are no longer tallied from the shipping instruction records. RMS now looks at the Bill of Lading date on each shipping instruction in the date range used for the Railcar Utilization reports and looks to the RMS Event Logs to determine which pool the railcar was assigned to on that date. The RMS Event Logs may be modified if necessary. The pool field will be removed from the Shipping Instruction Add window in a future release.
|
|
|
| Notes
|
| · | Server only update for 5.11.XX Server. Will work with 5.11.XX Client.
|
|
|
| · | Updated component that is used for FTP communication to latest version (Dart FTP for ActiveX version 2.1.0.1). There were no problems with the older version, but we wanted to update to the latest version to be sure that recent FTP problems were not related to a bug in the older version of this component. The problems were actually related to a server firewall.
|
|
|
| Bug Fixes
|
| · | When an FTP error is encountered, RMS logs the FTP conversation. Sometimes when the conversation is longer than 4,000 characters, the end of the conversation is not recorded in the error log. Changed to have RMS log the last 4,000 characters of the FTP conversation to ensure that the part that shows the error is stored to the log.
|
| · | Setting an EDI File Transfer record to Inactive for CLM/sighting imports does not exclude it from the import. This has been fixed.
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Client. Will work with 5.11.XX Server. Server 5.11.06 update is highly recommended if you use the Railcar Utilization reports.
|
|
|
| Bug Fixes
|
| · | Shipping instructions (i.e. waybills) are sometimes received that do not provide a load/empty status. This is a required field in RMS. A modification has been made so that RMS logs a warning and renames the file so that it is not imported in the future.
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Client. Will work with 5.11.XX Server. Server 5.11.05 update is highly recommended.
|
|
|
| · | Modified the Home window so that if a railcar initial/number entered in the Railcar text box is not Active, when the user selects the Inactive option button, the railcar initial/number remains instead of being cleared.
|
| · | Modified the Home window so that after a railcar initial/number is entered in the Railcar text box the user can press the Enter key and RMS will execute the Refresh button to query the database the railcar history.
|
|
|
|
|
| Bug Fixes
|
| · | When the user changes the flat file directory in the Reference Values window form from a non-existing folder to an existing folder, RMS still can't run reports because it tries to move the .rpx files from the non-existing folder to the new folder. It now checks first to see if the original folder existed and if not, it gets the report layout (.rpx) files from the installation FlatFiles folder.
|
| · | RMS' default flat file directory is c:\Program Files\Railcar Tracking Co\RMS\FlatFiles and on a 64 bit computer (Windows 7), it installs to c:\Program Files (X86)\Railcar Tracking Co\RMS\FlatFiles. RMS now checks to see if the c:\Program Files (x86)\Railcar Tracking Co\RMS\FlatFiles is available and if so, it uses that folder.
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Client. Will work with 5.11.XX Server. Server 5.11.05 update is highly recommended.
|
|
|
| · | Selecting a railcar and displaying the history on the Home window had several problems. After clicking on the Tree View control, sometimes the cursor would not activate in the Railcar text box until several tries. Also after a railcar was selected or pasted into the Railcar text box and the Enter key was pressed, the history was not refreshed - instead the cursor would go to the Open button. This has been fixed, but the Enter key must be clicked twice - once to move focus from the Railcar text box to the Refresh button; the second time to click the Refresh button which will refresh the history displayed in the data grids below. The cause of this problem was a 3rd party splitter control that had a bug in it. This control has been removed. Unfortunately the ability to change the size of the tree view control and the other side of Home window is not possible now. However, the tree view control has been widened, so even on a 1020 X 768 display, the names of forms and reports should be completely displayed as well as the data in the data grids (cycle label is the one exception - you will need to use a larger monitor resolution if you need to see that column without using the scroll bar).
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Client. Will work with 5.11.XX Server. Server 5.11.05 update is highly recommended.
|
|
|
| Improvements
|
| · | The error logs that RMS automatically emails to a support technician when errors are encountered during a scheduled activity has been reduced from the current and prior day to the current day only. This was done to reduce the size of the email messages, which for some larger fleets where getting so big that they couldn't be read in our new online support system.
|
|
|
| · | RMS is designed to handle sighting city and destination city locations with single quotes in them (i.e. O'FALLON), but there was a situation where this type of location name was the destination and was causing unexpected issues with the cycle creation process.
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Client. Will work with 5.11.XX Server. Server 5.11.05 update is highly recommended.
|
|
|
| Improvements
|
| · | A particular trading partner was entering the incorrect format for bill of lading time. RMS has been fixed to recognize when a BOL time is not formatted properly and instead of raising an error and stopping the import, it enters 00:00 (12AM) for the time.
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Client. Will work with 5.11.XX Server. Server 5.11.05 update is highly recommended.
|
|
|
| Improvements
|
| · | When RMS is in the middle of a data import and it is interrupted by a computer crash or restart, it is left in a state where manual intervention is required in order to allow future data imports. RMS now stores the date/time that it began an import. If it is interrupted, that date/time is preserved and the next time an import runs, RMS checks the stored start date/time of the last import. If the stored start date/time is 3 (default setting - user configurable) hours or more in the past, RMS assumes that the prior import was interrupted and it allows the current import to proceed. The setting that stores the maximum number of hours before RMS will allow another import may be altered by opening the Help > Diagnostics window and select MaximumHoursForImport.
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Client. Will work with 5.11.XX Server. Server 5.11.05 update is highly recommended.
|
|
|
| Bug Fixes
|
| · | When multiple corrections are made to a shipment (i.e. diversion) within a short period of time (i.e. 1 day), it is posssible for RMS to import only the first correction and ignore the second correction if the two shipping instruction files are imported during the same import process.
|
|
|
| Notes
|
| · | Server only update for 5.11.XX Server. Will work with 5.11.XX Client. Client 5.11.06 update is highly recommended.
|
| Bug Fixes
|
| · | In some situations, Last Sighting reports would show the shipping instruction information (i.e. Destination) from a prior shipment if the current shipping instruction was not available.
|
|
|
| Improvements
|
|
|
| Notes
|
| · | Server only update for 5.11.XX Server. Will work with 5.11.XX Client. Client 5.11.03 update is highly recommended.
|
| Bug Fixes
|
| · | Passive connection mode doesn't work on downloads from RR/VAN sightings (CLM) data sources.
|
|
|
| Improvements
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Clients. Will work with 5.11.XX Server.
|
| Bug Fixes
|
|
|
| Improvements
|
| · | Added the Comments field to the Contract Rates custom report dataset.
|
|
|
| Notes
|
| · | Server only update for 5.11.XX Server. Will work with 5.11.XX Client. Client 5.11.03 update is highly recommended.
|
| Bug Fixes
|
| · | RMS no longer requires Shipper and Consignee entries for Contract Rates records. If a contract rate was missing a Consignee entry, it wouldn't show in the list of contracts to choose from on the Shipping Instruction Add window.
|
| · | Shipping Instructions without a bill of lading number and date/time can't be imported. RMS requires a bill of lading number and date/time, so if this information is not provided, RMS enters "NA" for the bill of lading number and uses the waybill date (and 12:00 PM) for the bill of lading date/time.
|
|
|
| Improvements
|
|
|
| Notes
|
| · | Client only update for 5.11.XX Clients. Will work with 5.11.XX Server. Server 5.11.02 update is highly recommended.
|
| Bug Fixes
|
| · | Adding a sighting to an inactive, temporary, already completed, railcar cycle doesn't work. The sighting gets archived the next time that the Create Cycles process is run.
|
|
|
| Improvements
|
|
|
| Notes
|
| · | Client only update for 5.11.01 Client. Will work with 5.11.01 Server. Server 5.11.02 update is highly recommended.
|
| Bug Fixes
|
| · | When a shipping instruction is imported/added to RMS that has a bill of lading date more than 1 day later than the release date on the trip cycle record for the same shipment, RMS is unable to attach the shipping instruction to the cycle. In some circumstances, it may be possible for the release date to be several days before the bill of lading date that is on the imported shipping instruction. This was found in only a few cases where the railcar was released on a short line, but the shipping instruction was received from the next railroad in the route.
|
|
|
| Improvements
|
|
|
| Notes
|
| · | Server only update for 5.11.01 Server. Will work with 5.11.01 Client. Client 5.11.02 update is highly recommended.
|
| Bug Fixes
|
|
|
| Improvements
|
| · | Added Mileage and AvgTransitTime fields to the Contract Rates custom report dataset
|
| · | Added support for SQL Server 2008 Native Client drivers
|
| · | Automatically labels cycles S - Special Causes when a bad order event is found
|
|
|
| Notes
|
| · | Client and Server update required for those using 4.X, 5.XX, 5.10.XX Client and Server.
|
| Bug Fixes
|
| · | Shipping Instruction Add window has some field text that is not highlighted when the field gets focus
|
| · | Railcars not getting saved as permanent on Shipping Instruction data entry. If a shipping instruction is entered using a railcar that doesn't exist in the fleet as known to RMS (i.e. it hasn't been saved in the system prior to this action), RMS will prompt the user if they want to save it as a Temporary (this is assumed). If the user answers No, the railcars should have been saved as a permanent fleet addition, but the bug was preventing that from happening.
|
|
|
| Improvements
|
| · | Dynamic fleet updating now enables RMS to upload fleet additions and deletions to a remote data source, eliminating the need of manually preparing fleet updates.
|
| · | Removed saved filter on Demurrage - Railroad in Progress report to eliminate confusion and instead added a feature where the filter builder has the most commonly used filter auto-filled
|
| · | Added the ability to highlight and delete multiple sighting records on the Home window
|
| · | Added PO Number field and three generic user fields to the Shipping Instruction window. The generic user fields are available for users to enter shipment-related information, which may then be displayed on custom reports.
|
| · | Enhance Railroad Demurrage reports to be more user friendly.
|
| · | Add Railcar Lease Contract Number (LeaseNum) to Last Sightings and Cycles custom report datasets
|
|
|
| Notes
|
| · | Client and Server update required for those using 4.X and 5.X Client and Server.
|
| Bug Fixes
|
| · | Shipping instructions (waybills) that are imported late cause sightings for system / temporary railcars to be mistakenly archived in some situations. This update also increments the Reference Value - Relate BOL Days to 20. The way that shipping instructions are attached (i.e. related) to cycles has been changed to: The shipping instruction with the bill of lading date that is closest to the cycle release date AND is not more than one day later than the cycle release date and is not more than 20 days (or whatever the Relate BOL Days value is set to) greater than the cycle release date. A larger Relate BOL Days is now OK and is recommended. The Relate BOL Days of 20 setting allows a shipping instruction to be imported up to 20 days late and still be attached to the appropriate cycle.
|
|
|
| Notes
|
| · | Server update only required for those using 5.00.XX Clients. Client 5.00.03 is recommended.
|
| · | For 4.X Client and Server users, upgrade to 5.00.03 Client and 5.00.06 Server.
|
| Bug Fixes
|
| · | The Update Trip Plans process, under certain circumstances, calculates the Days to Destination incorrectly. If you have multiple Trip Plans that have the same Origin, Route, and Load/Empty Status, but have a different destination, these Trip Plans may contain Events with incorrect calculations.
|
|
|
| Notes
|
| · | Client update only required for those using 5.00.XX Clients
|
| · | For 4.X Client and Server users, upgrade to 5.00.03 Client and 5.00.05 Server.
|
| Bug Fixes
|
| · | Inbound empty system car (temporary/railroad owned) that is diverted or rejected is tracked through the following loaded move whether it is with the user's company or another company. RMS will now check for a valid shipping instruction before creating a new load cycle for a system car (temporary/railroad owned).
|
|
|
| Notes
|
| · | Server update only required for those using 5.00.XX Clients. Client 5.00.03 is recommended.
|
| Bug Fixes
|
| · | Removed check constraints for Shipping Instruction table for STCC and BOLDate. They were restricting the import of legitimate records
|
| · | Fixed demurrage days calculation error that occurred for permanent railcars that had been constructively placed, but not actually placed. The number of demurrage days was one day less than the correct calculation..
|
|
|
| Notes
|
| · | Server update only required for those using 5.00.XX Clients
|
| Improvements
|
| · | Added Cycle and Shipping Instruction history grids to the Home window for faster access to a specific railcar shipping information.
|
| · | Added IC System Business System Shipping Instruction import. This is a bridge to a proprietary customer order system that supplies RMS with shipping instruction information for each shipment.
|
| Bug Fixes
|
| · | The filter statement, created from the pop up Filter Builder, was not showing on the report header of reports saved to Excel Native format.
|
| · | Removed unused field on the Inbound Railcars Daily Report. It was causing an error on certain occasions.
|
| · | Fixed a problem where it was possible for Stations that were referenced in Contract Rates to be deleted.
|
| · | Fixed a problem where it was possible for Railcar Pools that were referenced in RMS Event Logs to be deleted.
|
| · | Modified timeout settings for the Create Cycles process to avoid timeout errors on large databases.
|
| · | Modified timeout settings for the Output Batch Report process to avoid timeout errors on large report batches.
|
| · | Fixed a query statement used in the Update Trip Plans process that may have limited the number of events for which RMS could provide accurate ETAs.
|
|
|
| Notes
|
| · | Client and Server updates must be applied
|
| Bug Fixes
|
| · | Made additional changes to overcome a problem where the Update Trip Plans process does not complete.
|
|
|
| Notes
|
| · | Client update only
|
| Improvements
|
| · | New Railroad Demurrage Measurement - allows more accurate and easier measurement of rail assessed demurrage/private storage
|
| · | New Contract Rates Custom Report Dataset - allows building reports to view rail contract rates
|
| · | New Problem Logs Custom Report Dataset - allows building reports to view problem logs
|
| · | New Compressed Report Summary Option - when a user selects to hide the report detail records, they will now have an option to compress the summary results, which provides an easier to read format
|
| · | Redesigned the Update Trip Plans process, which will now complete more quickly especially for larger fleets with several years worth of history
|
| Bug Fixes
|
| · | The filter statement, created from the pop up Filter Builder, was not showing on the report header of reports saved to Excel Native format.
|
| · | Removed unused field on the Inbound Railcars Daily Report. It was causing an error on certain occasions.
|
| · | Fixed a problem where it was possible for Stations that were referenced in Contract Rates to be deleted.
|
| · | Fixed a problem where it was possible for Railcar Pools that were referenced in RMS Event Logs to be deleted.
|
| · | Modified timeout settings for the Create Cycles process to avoid timeout errors on large databases.
|
| · | Modified timeout settings for the Output Batch Report process to avoid timeout errors on large report batches.
|
| · | Fixed a query statement used in the Update Trip Plans process that may have limited the number of events for which RMS could provide accurate ETAs.
|
|
|
| Notes
|
| · | Client and Server updates must be applied
|
| Improvements
|
| Bug Fixes
|
| · | Preview of custom reports based on the Railcar Utilzation dataset takes too long for large railcar fleets. Modified it so that it does not attempt to extract data for the preview.
|
|
|
| Notes
|
| · | Client update only
|
| Improvements
|
| Bug Fixes
|
| · | Waybill imports from BNSF experience error: 425 Can't open data connection. RMS has been modified to mitigate the problems that this causes (i.e. some waybill files may not get downloaded until a subsequent import). We are hoping that BNSF can modify their FTP server to not raise this error. If they can't, RMS will modified further
|
|
|
| Notes
|
| · | Client update only
|
| Improvements
|
| Bug Fixes
|
| · | Timeout errors during imports from Steelroads. Miscellaneous Error 12002. Updated the component that does this process.
|
|
|
| Notes
|
| · | Client update only
|
| Improvements
|
| · | Add option to the Railcars Update window to show a list of railcars that are unassigned to a pool.
|
| · | Add form size memory feature. Most forms will now "remember" how they were re-sized by the user.
|
| · | Add an automatic insertion of an underscore in the Field Alias if a space exists. Spaces are not allowed, so this is a user friendly feature.
|
| · | Add quick search feature to the Railcar Pool dialog box.
|
| Bug Fixes
|
| · | Can't save a new Railcar and assign it to a Lease at the same time.
|
| · | Cannot connect to Secondary Database using Windows Integrated security.
|
| · | Filter Builder for Trip Cycle Segments Detail report doesn't build cycle label filters properly.
|
| · | Manual database backup doesn't report a failure if there is one.
|
| · | Timeout error encountered occasionaly during Create Cycles process. The timeout threshold was increased.
|
|
|
| Notes
|
| · | Client update only
|
| Improvements
|
| · | Build compatibility with CSX waybill delivery methods
|
| Bug Fixes
|
| · | Database backup files not getting deleted after the configurable number of days
|
| Notes
|
| · | Client update only
|
| Improvements
|
| · | Improve handling of inbound temporary empty railcar tracking.
|
| · | Create an alias table for Commodity descriptions.
|
| · | Add IsCarInactive field to the DetentionHistory custom report dataset. This will allow the creation of reports showing Detention in progress (i.e. before the railcar is released back to the railroad) without showing inactive railcars. Add to the filter: IsCarInactive = 'False'.
|
| · | Allow certain historical reports to be run without a date range - a warning is raised instead. This allows for showing Detention in progress style reports.
|
|
|
| Bug Fixes
|
| · | Trip Cycle Actual Placement time may be inaccurate in certain circumstances.
|
| · | Comma delimitted CLM Format D import files not getting parsed properly.
|
|
|
| Notes
|
| · | Client and Server update must be applied
|
| Improvements
|
| · | Increase the timeout setting for the shipping instruction import feature to accommodate larger imports
|
| · | Add AARCarType, OriginCity, OriginState, DestCity, DestState fields to the ShippingInstructions custom report dataset
|
| · | Add feature where a user can take advantage where RMS tracks which shipping instruction records are exported. See Tracking Exported Shipping Instructions topic.
|
| Notes
|
| · | Client and Server update must be applied
|
|
|
| Improvements
|
| · | Added DailyLeaseCost field to the Cycles and RoundTripCycles Custom Report Datasets
|
| · | Add ability to import waybills from another RMS database
|
| · | Add ability to connect to a secondary database
|
| · | Ability to fillter imported shipping instructions based on origin and fleet status
|
| · | Add IsOnTime field to the Cycles and RoundTripCycles Custom Report Datasets
|
| · | Added railcar filter to the RMS Events window to make it easier to find Events for particular railcars and to reduce network traffic.
|
| · | Relabeled the Railcar Pool selector on report Filter Builder forms to make it more clear which type of pool was being selected: the pool to which the railcars are currently assigned or the pool to which the railcars were assigned during the measurement.
|
| · | Added the TareWeight (from the Railcar record) field to the ShippingInstructions Custom Report Dataset.
|
|
|
| Bug Fixes
|
| · | Pool field on various views may not be accurate.
|
| · | Railcar initials and/or numbers for shipping instructions were not getting updated automatically if a railcar is restenciled (i.e. the initials and/or number is changed in the railcar window).
|
| · | When add/delete STCC/Commodity the Shipping Instruction window is not refreshed.
|
| Notes
|
| · | Client and Server update must be applied
|