|
|||||||||||
![]() |
|||||||||||
|
Features RAILTRAC® Deployment Staff Requirements Through our experience with previous installations, here is an average estimate of the time required by the client staff for implementation and management of RAILTRAC® Fleet Manager. We have provided this to our clients in order to estimate and budget for staff efforts for implementation and on-going system support. The daily requirements are an average - RAILTRAC® does not require daily attention!
One
Time Implementation Tasks RAILTRAC® has the ability to process keypunched shipment entries as well as process shipment records inserted into a database table called RT_TRIP_IMPORT. This insert routine is programmed by the client by extracting the records or bill of lading system.
More
about Daily Shipment Feed... Historical data structures pertain to shipment and CLM records which provide an historical representation of the movement of the rail fleet and the delivery of product to customers. These two data sets are extracted by the Licensee from archives residing on the current fleet management system and are dumped to flat files. Besides
providing valuable chronicle of past shipments, the shipment history record
provides key information for creation of the new RAILTRAC® route master
and the transit time benchmarks by route leg and segment. Shipments and CLMs
for one year are sufficient to reflect these trends.
More
about Data Conversion... The following recommended specifications can be used for the various fleet sizes listed. If your drive configurations differ from those below, modify these recommended specifications to fit your needs. Regardless
of your drive configuration and capacity, the following theory remains valid
- Attempt to segregate the Data Tablespace, Indexes and Transaction Logs to
maximize performance by minimizing the I/O!
500
- 2000 Railcars
|
|||||||||||
|
|
|||||||||||