<rss version="2.0" xmlns:atom="https://www.w3.org/2005/Atom">
  <channel>
    <title>Transport Research International Documentation (TRID)</title>
    <link>https://trid.trb.org/</link>
    <atom:link href="https://trid.trb.org/Record/RSS?s=PHNlYXJjaD48cGFyYW1zPjxwYXJhbSBuYW1lPSJkYXRlaW4iIHZhbHVlPSJhbGwiIC8+PHBhcmFtIG5hbWU9InN1YmplY3Rsb2dpYyIgdmFsdWU9Im9yIiAvPjxwYXJhbSBuYW1lPSJ0ZXJtc2xvZ2ljIiB2YWx1ZT0ib3IiIC8+PHBhcmFtIG5hbWU9ImxvY2F0aW9uIiB2YWx1ZT0iMCIgLz48L3BhcmFtcz48ZmlsdGVycz48ZmlsdGVyIGZpZWxkPSJpbmRleHRlcm1zIiB2YWx1ZT0iJnF1b3Q7Q09CT0wgICggQ29tcHV0ZXIgcHJvZ3JhbSBsYW5ndWFnZSApICZxdW90OyIgb3JpZ2luYWxfdmFsdWU9IiZxdW90O0NPQk9MIChDb21wdXRlciBwcm9ncmFtIGxhbmd1YWdlKSZxdW90OyIgLz48L2ZpbHRlcnM+PHJhbmdlcyAvPjxzb3J0cz48c29ydCBmaWVsZD0icHVibGlzaGVkIiBvcmRlcj0iZGVzYyIgLz48L3NvcnRzPjxwZXJzaXN0cz48cGVyc2lzdCBuYW1lPSJyYW5nZXR5cGUiIHZhbHVlPSJwdWJsaXNoZWRkYXRlIiAvPjwvcGVyc2lzdHM+PC9zZWFyY2g+" rel="self" type="application/rss+xml" />
    <description></description>
    <language>en-us</language>
    <copyright>Copyright © 2026. National Academy of Sciences. All rights reserved.</copyright>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <managingEditor>tris-trb@nas.edu (Bill McLeod)</managingEditor>
    <webMaster>tris-trb@nas.edu (Bill McLeod)</webMaster>
    <image>
      <title>Transport Research International Documentation (TRID)</title>
      <url>https://trid.trb.org/Images/PageHeader-wTitle.jpg</url>
      <link>https://trid.trb.org/</link>
    </image>
    <item>
      <title>Highway Performance Monitoring System: Procedural Manual for Data Submittal</title>
      <link>https://trid.trb.org/View/2121048</link>
      <description><![CDATA[The module of programs supplied for a State to use in preparing their Highway Performance Monitoring System (HPMS) data submittal tape will develop the database from cards or card images, edit the section data, correct errors in the data, and develop mileage, DVMT, and volume group summaries by functional class. The module consists of a main (calling) program, STHPMS, and four subprograms: DEVTAPE, EDITCK, UPDATE and SUMTBLES. (It should be noted that this module of programs has the capability of processing a mixed dataset consisting of both urban and rural section data.) The main program and four subprograms are written in COBOL and were designed and developed on an IBM 360/65 with full operating system (OS).]]></description>
      <pubDate>Mon, 03 Apr 2023 13:57:07 GMT</pubDate>
      <guid>https://trid.trb.org/View/2121048</guid>
    </item>
    <item>
      <title>SIMS IMPLEMENTATION HANDBOOK. SERVICE, INVENTORY AND MAINTENANCE SYSTEM</title>
      <link>https://trid.trb.org/View/29963</link>
      <description><![CDATA[The Service, Inventory, and Maintenance System (SIMS) has been developed to aid urban bus transit properties in managing their servicing and maintenance activities. This automated information system is currently operational and consists of three components: the Service/Unit Change System, Inventory System, and Repair Cost System. General descriptions of the system's data requirements and the reports it produces have been published, and detailed software documentation is available for each of the three components. This handbook furnishes guidance to management in planning the implementation of the SIMS components at individual properties, by outlining such steps as data base generation, training, and acquisition of data processing services.]]></description>
      <pubDate>Wed, 16 Dec 1981 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/29963</guid>
    </item>
    <item>
      <title>USER DOCUMENTATION FOR THE FHWA CARPOOL MATCHING PROGRAM (SECOND EDITION)</title>
      <link>https://trid.trb.org/View/63209</link>
      <description><![CDATA[The full documentation for the computerized FHWA Carpool Matching Program is divided into two reports: user documentation and program documentation. This report only covers the user portion of the documentation and is intended to be used as a guide and set of instructions for operating the program. On October 1, 1974, the Federal Highway Administration released the latest, improved version of the program. This second edition of the user documentation includes a description of all the improvements and additions that have been added to this latest version of the program. The FHWA program is written in American National Standard COBOL and thus should be readily transferable to environments other than the IBM 360/65 (OS) under which it has been developed and tested.]]></description>
      <pubDate>Fri, 16 Jan 1981 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/63209</guid>
    </item>
    <item>
      <title>PROGRAM DOCUMENTATION FOR THE FHWA CARPOOL MATCHING PROGRAM</title>
      <link>https://trid.trb.org/View/63211</link>
      <description><![CDATA[The full documentation for the computerized FHWA Carpool Matching Program is divided into two reports: user documentation and program documentation. This report covers the program portion of the documentation. It is intended for use by those persons who desire to learn the internal operation of the program. The FHWA program is written in American National Standard COBOL and thus should be readily transferable to environments other than the IBM 360/65 (OS) under which it has been developed and tested.]]></description>
      <pubDate>Fri, 16 Jan 1981 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/63211</guid>
    </item>
    <item>
      <title>TRUCK DRIVING PATTERN AND USE SURVEY PHASE II - FINAL REPORT, PART I</title>
      <link>https://trid.trb.org/View/77726</link>
      <description><![CDATA[The report covers activities in Part I of Phase II of the title study, which developed sampling plans and instrumental 50 heavy duty trucks in normal operation in New York City for 172 days, and, similarly, 5 transit buses for 15 days. Operational profile data included: engine speed, engine load factors, vehicle speed, engine temperature, and throttle valve closure. These data, obtained from sensors installed and calibrated with vehicle operating on a chassis dynamometer, were recorded in digital form at 0.863 second intervals on magnetic tape cassettes. Recorded data was edited and certain values translated to engineering terms using calibration data obtained at time of instrumentation installation. The report describes the sampling plan, instrumentation equipment, calibration methods, edit procedures, survey vehicle types, and technical problems encountered and their solutions. A set of 14 raw data and 14 calibrated, machine-compatible tapes were generated which are available separately from sponsor. Operational use profile data thus generated was basic input to generation of driving cycles for emission testing programs in subsequent program phases by EPA. (Portions of this document are not fully legible)]]></description>
      <pubDate>Sat, 29 Dec 1979 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/77726</guid>
    </item>
    <item>
      <title>RSPO SUBSIDY PROGRAM</title>
      <link>https://trid.trb.org/View/71694</link>
      <description><![CDATA[This computer program calculates the Light Density Line subsidy level under the Rail Service Planning Office requirements given alternative service characteristics and traffic/revenue bases.  The program as written by RSPO has been revised and enhanced.]]></description>
      <pubDate>Thu, 18 May 1978 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/71694</guid>
    </item>
    <item>
      <title>FLEET MANAGEMENT SYSTEM</title>
      <link>https://trid.trb.org/View/71700</link>
      <description><![CDATA[The computer program will provide an up-to-date inventory of the company's automotive fleet, as well as a complete history of all expenses.  This information will provide the means by which the operating and maintenance cost can be reduced to a minimum.  The system will pinpoint abuses so corrective action can be taken and will provide a guide for authorizing repairs and vehicle replacement.  All expenses over $50 will require authorization by Fleet Management personnel.]]></description>
      <pubDate>Thu, 18 May 1978 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/71700</guid>
    </item>
    <item>
      <title>LOCOMOTIVE IN-SERVICE FAILURES/DEFECT ANALYSIS</title>
      <link>https://trid.trb.org/View/38457</link>
      <description><![CDATA[File name is LOCOMOTIVE FAILURE/DEFECT FILE, CAR MOVEMENT HISTORY FILE.  Major objective of computer program is to isolate major causes of locomotive in-service failures. Input consists of: 1. Data on the results of a monthly spectrographic analysis of samples of the cooling water, crank case oil, and air compressor oil from each locomotive. 2. Data on in-service failures (motive power failures which result in either reducing the tonnage of a train or in a train delay.) 3. Diesel shop report on in-service failure giving cause, type to defect, data repaired, etc. 4. Reports of locomotive defects (conditions not causing failure). Monthly output reports include: 1. A raw data tabulation of each failure listing all pertinents data and sorted by locomotive model and within model by cause of failure. 2. A summary of locomotive in-service failures by maintenance points, locomotive model, and failing component for both one month and three-month periods giving number of failures and failures per million miles. 3. Summary of locomotive defects by defective component and by the reporting Road Foremen of Engines. 4. A summary of in-service failures by operating division and by type of service (passenger, freight, or switching). 5. Identification of units which have had repetitive duplicate oil lab findings.]]></description>
      <pubDate>Fri, 27 Aug 1976 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/38457</guid>
    </item>
    <item>
      <title>ACTIVE CAR SAMPLE</title>
      <link>https://trid.trb.org/View/38440</link>
      <description><![CDATA[Computer program:  ACTIVE CAR SAMPLE MASTER FILE.  The objective of this program is to provide estimates of car mileage on Southern Railway System for selected groups of cars.  The mileage estimates may be any of the following characteristics or combination of characteristics which are obtained from the Umler File and added to the Active Car Master File (age range, AAR car type, truck tonnage capacity, SRS marketing code, cubic foot capacity, nominal capacity, tare weight, lining, outside length, side door width, clearance, bearing type, draft gear travel, truck center length, fittings, compartments, floor type).  These mileage estimates are used in calculating failure rates for groups of cars.  Examples include studies of (1) derailments by AAR car type and age range, (2) uncouplings by cut-lever type and car cushioning, and (3) broken knuckles and couplers by AAR car type and age range.  The input data (consisting of car number and supplemental information obtained by inspection of the car such as air hose arrangements and/or cut-lever type) is collected at selected hump yards for a sample of cars going over the hump.  The file is of unlimited length.  This method of estimating car population approximates mileage more closely than would ownership figures since cars will be included in the sample in proportion to their movement.  The program produces a microfiche listing of all data in the file by car initial and number.  Other reports are generated by a general purpose picker program (RSVP) which has the capability to select certain records, to sort them in any order, and to print the selected records with summaries on any field.]]></description>
      <pubDate>Fri, 27 Aug 1976 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/38440</guid>
    </item>
    <item>
      <title>UNIVERSAL MACHINE LANGUAGE EQUIPMENT REGISTER PICKER PROGRAM</title>
      <link>https://trid.trb.org/View/38453</link>
      <description><![CDATA[File name is UMLER FILE.  Program allows selection of cars in the Umler file on the basis of ownership code, AAR car type, individual car numbers (maximum of 500 cars), a car series, or car initials.  Output consists of the selected Umler file data with sorting options of car age, AAR car type, capacity, bearing type, draft gear, outside length, tare weight, truck center length, and car identification.  Objective of the program is to classify cars in failure groups or in population samples by the various characteristics described in the Umler file for failure analysis.]]></description>
      <pubDate>Fri, 27 Aug 1976 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/38453</guid>
    </item>
    <item>
      <title>DIESEL RECORDS SYSTEM</title>
      <link>https://trid.trb.org/View/38454</link>
      <description><![CDATA[The file name is DIESEL RECORDS MASTER FILE.  The objectives of this computer program are:  1. To aid in scheduling and verifying completion of locomotive maintenance items. 2. To aid in isolating problems with specific locomotives by providing a history of pertinent information for each unit. Output consists of a semi-monthly printout showing the following information for each unti due maintenance during the next fifteen days: 1. Maintenance items due to be performed including repetitive maintenance items which are done at fixed intervals and special upgrading or correction projects. 2. A history of traction motor failures on each unit by pedestal number. 3. An indication if the traction motor model is not one of the models which is recommended for use on the specific locomotive model. (Recommendation is based on reliability considerations). Other outputs include a current "cab card" and various inventory listings of main components (traction motors, main generators, turbochargers, etc.).  Feedback is provided when maintenance items are completed by having the person who did the work sign the computer report and then keytyping data from the report.  A maintenance item will continue to appear on the report each month until it is reported completed. Input consists of: 1. Oil control lab data, in-service failures, and defects from the Locomotive In-service Failure/Defect Analysis Program. 2. Feedback data from the shops on each maintenance item or project completed. 3. Traction motor applications and removals from the diesel shops. 4. Tables of frequency of repetitive maintenance items. 5. Tables identifying which units are due for special projects.]]></description>
      <pubDate>Fri, 27 Aug 1976 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/38454</guid>
    </item>
    <item>
      <title>TRACTION MOTOR RELIABILITY</title>
      <link>https://trid.trb.org/View/38455</link>
      <description><![CDATA[Computer program: MAIN DIESEL COMPONENT INVENTORY, CAR MOVEMENT HISTORY FILE. Program produces a family of reports giving traction motor reliability data by model.  Reports provide basis for decision rules for vendor selection, and preferred combinations of traction motor model--locomotive model.  Input consists of traction motor application (to locomotive units) and removal records, traction motor disassembly and reassembly records.  Mileage is obtained from the car movement history file. Output consists of the following reports: 1. Traction motor overhaul data by motor serial number.  2. Traction motor overhaul data by armature serial number. 3. Traction motor armature overhaul rates by armature manufacturer for each 100,000 mile increment since manufacture or rewinding. 4. Traction motor model-locomotive model failure rates by combination showing number of motors in class, mileage last 3 months; reason for overhaul and number of overhauls.]]></description>
      <pubDate>Fri, 27 Aug 1976 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/38455</guid>
    </item>
    <item>
      <title>TRACK PROFILES</title>
      <link>https://trid.trb.org/View/38383</link>
      <description><![CDATA[This program permits computer generation of track profiles using a Calcomp plotter.  Accurate milepost location of each track element is required.  Unless existing manual records are both accurate and current, new data from the field is necessary.  This can be accomplished with a track geometry car or any test car where accurate distance measurement is an output.  The program utilizes data in a three-step process.  The first is to input the type and milepost location of each track element in the symbol master.  The output from this step consists of two reports--a symbol listing in milepost order and the distance between each milepost.  Elements include yard track locations, spring switches, railroad crossings, private crossings, three types of public crossings, railroad bridges, rivers, underpasses, overhead bridges, tunnels, hot box detectors, 13 types of train signals.  The second step merges the symbol master data from step 1, grade and curve data from the track characteristics master, and milepost locations from the milepost master.  Output from this step is a printed listing of each track element in milepost order and a plot tape.  The third step uses the plot tape as input to drive a Calcomp plotter and produce the track profile (generally on a paper original).  Plot scale is two inches to the mile (5280 feet).  Height of the profile is 4 1/2 inches and can be of any length.  Plot consists of a milepost line dividing distance between adjacent mileposts into ten equal parts regardless of actual distance, a grade line, a track line showing single track, double track, sidings, spurs, and all track elements and a curve line.]]></description>
      <pubDate>Fri, 27 Aug 1976 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/38383</guid>
    </item>
    <item>
      <title>RAIL FAILURE SYSTEM</title>
      <link>https://trid.trb.org/View/38386</link>
      <description><![CDATA[File name is ENRF. Computer program. The "Rail Failure" application is designed to compile statistics of all types of rail failures.  The system employes two highly regimented input forms entitled "Rail Removal Order" and "Rail Insertion Report" which also serve to cause the appropriate physical action to take place.  The system is modular and as such contains over twenty (20) separate programs re: data validity edits, maintenance and print routines which can provide monthly, year-to-date and yearly statistics, e.g.: (a) "Audigage and Reflectoscope; Detector Car; and Service Rail Failure Statement": a three part statement, i.e., a separate report for each potential input source, giving a complete description by Division and District of type of track, location of rail, position, grade, weight, mill, etc. of all failures reported. (b) "Rail Insertion Report Statement Covering Service and Detected Rail Removal Orders"; this statement lists all rail that has had a defect and that has been replaced by a new rail, angle bar repaired or taken out of service. (c) "Annual Report of Rail Failures, Service and Detected, in Rail of All Ages and Sections".  (d) "Rail Removal Orders not Covered by Insertion Reports on the Eastern, Western and Coast Lines".  Report will flag any removal order over 30 days old for which as insertion report has not been issued.  (e) The "Transverse Fissure Rail Heat Statement": This statement provides listing of all transverse fissure heat failures over the system.  The statement is written out in mill order and year rolled plus pertinent detail data. (f) The "Thermite and Butt Welded Joint Failure Statement"; This statement lists all thermite and butt welded rail failures by division, district, mile post, type track, weight or rail, mill and year rolled.  Each report is year to date.]]></description>
      <pubDate>Fri, 27 Aug 1976 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/38386</guid>
    </item>
    <item>
      <title>RAIL AND TRACK CHARACTERISTICS PICKER PROGRAM</title>
      <link>https://trid.trb.org/View/38390</link>
      <description><![CDATA[File name is Track Characteristics Master, Rail Defect Master, Derailment Master. Computer Program.  The purpose of the rail and track characteristics picker program is to provide the information with which to develop the relationships between various rail and track characteristics and their correlation with rail failures, rail defects, and derailment frequency.  The Track Characteristics Master contains rail type (jointed versus welded, kind of steel) weight, rail rolled and laid dates, history of surfacing dates, rail and track inspection and test data, grades, curves, load limits, and traffic density (tons per year) for all system track.  Locations of rail failures, rail defects, and exceptions to track geometry standards found by testing and inspection are contained in the rail defect master.  The derailment master contains pertinent data on all derailments.  The rail and track characteristics picker program selects and prints out track locations from the track characteristics master with user-defined selection criteria; these can be minimums and/or maximum for any combination of the characteristics listed above.  Up to 50 different combinations, i.e., cells in a matrix can be requested at one time.  For each cell or specific request, the number of miles of track and the number of ton-miles is printed out.  In addition for each cell, the progrm gives the types and numbers of rail defects and derailments reported over a time period selected by the user.  Once relationships have been established, the program can be used for developing rail laying and timbering and surfacing programs, anchor and double spiking programs, problem area identification, budgeting, and other applications.]]></description>
      <pubDate>Fri, 27 Aug 1976 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/38390</guid>
    </item>
  </channel>
</rss>