Provides a view with fields primarily oriented to the Cycle records in RMS. A cycle is a record created by RMS that is derived from the sighting (CLM) records that are imported in RMS. RMS derives these records so that reports based on this type of information will open in a reasonable amount of time (i.e. a few seconds to a few minutes).
List of fields
APDate
Actual placement date - the date when the railcar is placed or spotted at the final destination on the consignee or care of party's property. Source: Cycle. Format: mm/dd/yyyy
APDttm
Actual placement date and time - the date and time when the railcar is placed or spotted at the final destination on the consignee or care of party's property. Source: Cycle. Format: mm/dd/yyyy hh:mm
BOLDate
Date the bill of lading was created (format: mm/dd/yyyy). Source: Shipping Instruction
BOLNum
Bill of lading number assigned to the shipment by the shipper. Source: Shipping Instruction
CareOf
Company name listed as the care of party by the shipper. Source: Shipping Instruction or if a match is made on a Party Alias, Party
Commodity
Description of the commodity carried in the railcar. Source: Shipping Instruction unless it matches an alias of a proprietary Commodity - in that case, it will display the proprietary Commodity Name.
Consignee
Company name listed as the consignee party by the shipper. Source: Shipping Instruction or if a match is made on a Party Alias, Party
ContractNum
Number identifying the contract between the freight payor and the rail carrier. Source: Shipping Instruction
CPDate
Constructive placement date - the date when the railroad tried to place or spot the railcar at the final destination on the consignee or care of party's property, but they couldn't for reasons out of their control. Source: Cycle. Format: mm/dd/yyyy
CPDttm
Constructive placement date and time - the date and time when the railroad tried to place or spot the railcar at the final destination on the consignee or care of party's property, but they couldn't for reasons out of their control. Source: Cycle. Format: mm/dd/yyyy hh:mm
CPVSAP
If a railcar is constructively placed (CP) during a trip cycle and then subsequently actually placed (AP), this is the number of days between the two dates. Source: Calculated by RMS: APDttm minus CPDttm. Format: 00.0
CycleTime
Number of days from the beginning of the cycle (i.e. release date / time) to the end of the cycle (i.e. the next release date / time). Source: Calculated by RMS: RlseEndDttm minus RlseDttm. Format: 00.0
DailyDemCharge
Dollars per day that will be incurred for each day of DemurrageTime. Source: Demurrage - Railroad
DailyLeaseCost
Dollars per day required to lease a particular railcar. Source: Railcar Lease
DemurrageRR
Delivering railroad that will assess the demurrage charges. This is the railroad that constructively placed, actually placed the railcar and received the railcar back after loading or unloading. Source: Cycle
DemurrageTime
Time (in days) of calculated demurrage days based on the Railroad Demurrage criteria. Source: Calculated by RMS based on criteria entered in Demurrage - Railroad
Destination
City / station where the shipment terminated. Source: Cycle or if a match is made on a Station Alias, Station.
DestSPLC
SPLC (standard point location code - a 6 digit number identifying a station) for the destination. Source: Station.
HasBilling
True or False indicating whether the cycle has a shipping instruction related / attached to it. Source: RMS
IsCarInactive
True of False indicating whether the railcar is inactive. Source: Railcar
IsComplete
True or False indicating whether the cycle is complete (i.e. the RlseEndDate is not blank/null). Source: RMS
IsTransitOnTime
True of False indicating wheter the cycle transit time is less than or equal to the Standard Transit (Days) that is entered for the matching stored Origin Destination (OD) Pair record.
IsValid
True or False indicating whether the cycle is valid. RMS considers a cycle valid if its origin and destination matches a stored Origin Desitnation (OD) Pair record in RMS. The location where the railcar is actually placed must also match the location where it is subsequently released.
Label
A one character code indicating that the cycle has been identifyed by a user as:
B - Bad Cannot Repair
S - Special Causes
G - Good (Use is not recommended)
Source: Cycle
LayoverTime
The number of days it takes for the railcar to be unloaded (if this is a load cycle) or loaded (if this is an empty cycle). Source: Calculated by RMS: RlseEndDttm minus APDttm. Format: 00.0
LE
Indicates whether this is a load cycle or an empty cycle. Source: Cycle. Format: L for load and E for empty.
LeaseNum
Railcar lease contract number. Source: Railcar Lease.
LEDesc
Indicates whether this is a load cycle or an empty cycle. Source: Cycle. Format: LOAD for load and EMPTY for empty.
Mileage
Number of miles from the origin to the destination. Source: OD Pair. Format: 00.0
NetWeight
Weight of the lading. Source: Shipping Instruction
OrderInDttm
Date and time that the railcar was ordered in after it was reported as constructively placed. Source: Shipping Instruction
Origin
City / station where the cycle originated. Source: Cycle or if a match is made on a Station Alias, Station
OriginSPLC
SPLC (standard point location code - a 6 digit number identifying a station) for the origin. Source: Station.
Pool
Railcar sub-fleet / pool that the railcar belonged to at the time of this cycle. Source: Railcar Pool
PoolCurrent
Railcar sub-fleet / pool that the railcar belongs to currently (Provided for backward compatibility). Source: Railcar Pool
Railcar
Initial and Number of the equipment used for the shipment (XXXX 123456); there is always one space between the initials and number with no trailing or leading spaces or zeros. Note: This is not a good field to use for sorting. If you wish to sort by the railcar initial and number, it is recommended to use the fields RailcarInitial and RailcarNumber. Source: Cycle
RailcarInitial
Initial of the equipment used for the shipment. Source: Cycle
RailcarNumber
Number of the equipment used for the shipment. Source: Cycle
RlseDate
Date the railcar was released to start the cycle. Source: Cycle. Format: mm/dd/yyyy
RlseDttm
Date and time the railcar was released to start the cycle. Source: Cycle Format: mm/dd/yyyy hh:mm.
RlseEndDate
Date the railcar was released to end the cycle. Source: Cycle. Format: mm/dd/yyyy
RlseEndDttm
Date and time the railcar was released to end the cycle. Source: Cycle Format: mm/dd/yyyy
RlseRR
Railroad to which the railcar was released at the start of the cycle. Source: Cycle
RlseTime
Time the railcar was released to start the cycle. Source: Cycle. Format: hh:mm:ss am/pm
Route
Includes SCAC abbreviations of railroads that are involved in the shipment and Rule 260 junction abbreviations indicating interchange points. Source: Shipping Instruction
RTADttm
Requested date and time of arrival. Source: Shipping Instruction. Format: mm/dd/yyyy hh:mm
Segment
A combination of the origin and destination. Source: Calculated by RMS: Origin + ' to ' + Destination. Format: Anywhere, NS to Somewhere, NA
Shipper
Company name listed as the Shipper party by the shipper. Source: Shipping Instruction or if a match is made on a Party Alias, Party
STCC
A seven digit numeric code representing 38 commodity groupings. Source: Shipping Instruction
STCCDesc
A description related to the seven digit numeric code representing 38 commodity groupings. Source: RMS Commodities
TransitStandard
Number of days used as a basis of comparison. Source: OD Pair. Format: 00.0
TransitTime
Number of days of transit time. Source: Calculated by RMS: APDttm minus RlseDttm. Format: 00.0
WaybillDate
Date the waybill was created. Source: Shipping Instruction
WaybillNum
Waybill number assigned to the shipment by the rail carrier. Source: Shipping Instruction