<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+PHBhcmFtIG5hbWU9ImxvY2F0aW9uIiB2YWx1ZT0iMCIgLz48L3BhcmFtcz48ZmlsdGVycz48ZmlsdGVyIGZpZWxkPSJpbmRleHRlcm1zIiB2YWx1ZT0iJnF1b3Q7TWFpbnRlbmFuY2UgZGF0YSBzeXN0ZW1zJnF1b3Q7IiBvcmlnaW5hbF92YWx1ZT0iJnF1b3Q7TWFpbnRlbmFuY2UgZGF0YSBzeXN0ZW1zJnF1b3Q7IiAvPjwvZmlsdGVycz48cmFuZ2VzIC8+PHNvcnRzPjxzb3J0IGZpZWxkPSJwdWJsaXNoZWQiIG9yZGVyPSJkZXNjIiAvPjwvc29ydHM+PHBlcnNpc3RzPjxwZXJzaXN0IG5hbWU9InJhbmdldHlwZSIgdmFsdWU9InB1Ymxpc2hlZGRhdGUiIC8+PC9wZXJzaXN0cz48L3NlYXJjaD4=" 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>STUDY OF ELECTRICAL EQUIPMENT RELIABILITY USING MAINTENANCE DATA COLLECTION SYSTEM</title>
      <link>https://trid.trb.org/View/1058</link>
      <description><![CDATA[The Maintenance Data Collection System contains maintenance data which, with certain limitations, may be utilized for derivation of the data on electromechanical equipment for reliability evaluation and prediction.  A method of utilizing this system for shipboard reliability purposes is presented, showing how the data was used to obtain the number of failures during the reporting period. In the study the operating hours have been derived from steaming hours of ships with application of the usage factors.]]></description>
      <pubDate>Thu, 30 Oct 2003 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/1058</guid>
    </item>
    <item>
      <title>COATINGS-RELATED COMPUTER PROGRAMS CAN SIMPLIFY THE BUSINESS OF MAINTENANCE</title>
      <link>https://trid.trb.org/View/542553</link>
      <description><![CDATA[Although the use of computers and computer software by members of the coatings industry to track maintenance programs and painting projects is not as widespread as the use of paper-filled file folders, some end users and contractors have seen the benefits of computerization:  minimization of stacks of paper, easily retrievable historical information, simplified maintenance prioritization, streamlined budgeting processes, more accurate project estimation, heightened productivity, and professional-looking reports.  This article takes a look at the types of computer programs that three end users and five contractors are using or considering to make their maintenance programs and projects more efficient.  Many of these programs are not off-the-shelf, coatings-focused programs but rather are databases that, with a little planning and creative thinking, the users structured to suit their particular needs and circumstances.  Sidebars offer a sampling of commercially available software that facilitates maintenance management, coatings selection, specification writing, and project estimation, and provide an outline for a computer maintenance management system for coating maintenance.]]></description>
      <pubDate>Thu, 07 Jan 1999 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/542553</guid>
    </item>
    <item>
      <title>AUTOMATED DAILY ACTIVITY REPORT AND AUTOMATED CONSTRUCTION INSPECTOR'S REPORT - USER MANUAL WITH ANALYSIS</title>
      <link>https://trid.trb.org/View/460898</link>
      <description><![CDATA[ADAR is a user friendly program that is written in Pen Pal (trademark) for automating the Daily Activity Report.  This program is developed to be used with pen based field computers. The paper form of the Daily Activity Report was programmed into the pen based computers.  The electronically filed forms would be transferred to a record computer by disk.  This program is intended for use by the maintenance personnel.  The final link would have been the connection for loading the information to the mainframe.  Mainframe programs could not be changed at this time to facilitate this connection.  The CIR is a window based software for automating part of the construction record keeping process.  This software was put into production and performed successfully.  The project required the automation of the 1257 and 1258 reports.  As requested, automation of the daily diary, time charge, contractor, and material information was provided, to give the user a more worthwhile product.  The software is intended for use by construction inspectors to help keep up with the progress records.  This report has a user's manual for both the ADAR and CIR; also included is some analysis information.]]></description>
      <pubDate>Fri, 13 Sep 1996 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/460898</guid>
    </item>
    <item>
      <title>TRAFFIC SIGN AND SIGNAL INVENTORY AND MANAGEMENT SYSTEMS</title>
      <link>https://trid.trb.org/View/451381</link>
      <description><![CDATA[This Technical Paper describes software developed and now in use to manage traffic engineering assets. The software effectively integrates Geographical Information Systems [GIS] with Relational Database Management Systems [RDBMS]. The software for DOS and Windows enables city, county, and state traffic engineers: (1) to create and maintain inventories of the geographic locations and detailed attributes of traffic signs, traffic signals, and other features; (2) to make inquiries of the database and create tabulations or maps of signs and signals based on any flexible combination of attributes; (3) to print work and maintenance orders for field crews showing the attributes and mapped locations of signs or signals to be replaced or repaired; (4) to automatically update the field inventory when work and maintenance orders have been completed; (5) to maintain a detailed file of all work and maintenance activities associated with each sign or signal; and (6) to create annual programs and budgets for signs and signals to be repaired or replaced.]]></description>
      <pubDate>Fri, 20 Oct 1995 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/451381</guid>
    </item>
    <item>
      <title>RE-ENGINEERING TRACK-INSPECTION REPORTING SYSTEMS</title>
      <link>https://trid.trb.org/View/389898</link>
      <description><![CDATA[The maintenance-of-way industry is moving rapidly to take advantage of advances in computer portability and processing power.  The article describes a sturdy hand-held computer and a new software system that have given the Metropolitan Atlanta Rapid Transit Authority's (MARTA) Track and Structure's Branch better data in a more accessible and usable format.  Specific benefits of the new system include improved data accuracy, improved timeliness of reports and repairs, reduced administrative costs and better communication among teams.  In the future, programs that are currently being developed will fully integrate the inspection database into MARTA's systemwide maintenance management information system network.]]></description>
      <pubDate>Thu, 14 Apr 1994 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/389898</guid>
    </item>
    <item>
      <title>NATIONAL TRANSIT SUMMARIES AND TRENDS FOR THE 1990 SECTION 15 REPORT YEAR</title>
      <link>https://trid.trb.org/View/368953</link>
      <description><![CDATA[This report provides a summary on the state of the national public transit industry by highlighting aggregate financial and operational characteristics and trend information for key statistics and performance indicators.  In prior report years, these data were found in Chapter 2 - Aggregate Transit Statistics of the National Urban Mass Transit Transportation Statistics Section 15 Annual Report.  These data represent a portion of the 1990 Annual Report.  It is the intent of this report to provide a national, policy oriented perspective of the American transit industry through graphics and tabular displays of relevant statistics.  The statistics presented here permit an understanding of the performance and condition of mass transportation in the United States.  This report serves as a reference for policy makers at all levels of government, transit professionals, and researchers at various institutions.  The report provides a picture of the public transit industry in 1990 and its performance covering four Section 15 report years, 1987 through 1990.]]></description>
      <pubDate>Wed, 08 Dec 1993 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/368953</guid>
    </item>
    <item>
      <title>GLOSSARY OF TRANSIT TERMS USED FOR SECTION 15</title>
      <link>https://trid.trb.org/View/380565</link>
      <description><![CDATA[This report provides a comprehensive glossary of terminology used for the Federal Transit Administration's Section 15 Program.  This report is comperable to Appendix D - Glossary contained in the National Urban Mass Transportation Statistics 1989 Section 15 Annual Reportt.  Section 15 of the Federal Transit Act (FT Act), as amended, provides for establishment of a uniform system of transit accounts and records plus a reporting system for the collection and dissemination of public mass transportation financial and operating data by uniform categories.  All applicants and direct beneficiaries of Federal assistance under Section 9 of the FT Act are subject to the reporting system and the uniform system of accounts and records. The purpose of the Section 15 reporting system is to assist in meeting the needs for information on which to base planning for public transportation services and to make public sector investment decisions at all levels of government  The terminology provided in this glossary includes the Section 15 reporting year ending in December 1992.]]></description>
      <pubDate>Thu, 04 Nov 1993 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/380565</guid>
    </item>
    <item>
      <title>TRACK MAINTENANCE TECHNIQUE FOR 300 KM/H CLASS SHINKANSEN</title>
      <link>https://trid.trb.org/View/382869</link>
      <description><![CDATA[Recently, there are remarkable activities in the development of high speed railways all over the world.  Also in Japan, Shinkansen's speedup, by improving the vehicle and the track, is planned.  In this report, we propose a new track maintenance technique matching 300 km/h class Shinkansen operation.  The first step is control of long wave track irregularity.  The second is control of short wave track irregularity.  The third is track inspection system.  And the last step is data analysis system.  Following these steps, commercial service at 300 km/h with good riding comfort will be made feasible.]]></description>
      <pubDate>Sun, 26 Sep 1993 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/382869</guid>
    </item>
    <item>
      <title>COMPUTERIZATION IN MAINTENANCE-OF-WAY</title>
      <link>https://trid.trb.org/View/378266</link>
      <description><![CDATA[This article discusses how computer technology is being used to improve maintenance-of-way, providing the greatest possible accuracy and the highest possible productivity. Microprocessors are ensuring more flexibilty as well, since computer programs can be made to detect potential problems which individual operators might overlook. Also, computers don't get tired, and this is of particular importance when repetitive procedures, such as switch grinding, are required. Computers will not abolish the need for managers to be out on the track, but they will enable managers to to a better job when they are out there.]]></description>
      <pubDate>Mon, 17 May 1993 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/378266</guid>
    </item>
    <item>
      <title>MOCA - A KNOWLEDGE-BASED SYSTEM FOR AIRLINE MAINTENANCE SCHEDULING. IN: INNOVATOVE APPLICATIONS OF ARTIFICIAL INTELLIGENCE 3. PROCEEDINGS OF THE IAAI-91 CONFERENCE</title>
      <link>https://trid.trb.org/View/373415</link>
      <description><![CDATA[American Airlines currently operates in excess of 550 aircraft and flies over 2200 scheduled flights a day to over 160 destinations worldwide.  Maintenance planning in a route network of this magnitude is a complex, decision-intensive task that is managed at the Maintenance Operations Center (MOC) in Tulsa, Oklahoma.  The process of routing aircraft for maintenance has evolved over the years but until recently was a manual process, involving many large paper documents.  This paper describes the automation approach chosen to build an expert system application called the maintenance operations controller adviser (MOCA), a knowledge-based system that automates the previously manual planning and document maintenance tasks.]]></description>
      <pubDate>Sun, 24 Jan 1993 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/373415</guid>
    </item>
    <item>
      <title>SHIP MAINTENANCE: A QUANTITATIVE APPROACH</title>
      <link>https://trid.trb.org/View/151655</link>
      <description><![CDATA[In this new technical book for marine engineers the authors show how preventive ship maintenance can be coupled with modern scientific management.  Covering three progressive stages the book presents maintenance programs to achieve substantial benefits with minimum delay, an integrated total maintenance system incorporating management control techniques, good engineering practice and back-up facilities and scientific analysis of maintenance data for optimum conditions of ship maintenance, management and practice.]]></description>
      <pubDate>Wed, 08 Oct 1980 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/151655</guid>
    </item>
    <item>
      <title>HOW TO MAKE 3-M SYSTEMS WORK FOR YOU</title>
      <link>https://trid.trb.org/View/154047</link>
      <description><![CDATA[The primary objective of the Ships' 3-M Systems is to provide for managing maintenance and maintenance support in a manner which will ensure maximum equipment operational readiness.  This paper describes a simple improvement to the 3-M system to accomplish that objective better.  The improvement makes the system more comprehensible and useful to Work Center maintenance personnel and to ships' officers who manage the maintenance work.  To a system, which utilizes Equipment Identification Codes (EIC) and Work Center (WC) codes to facilitate the summarization and analyses of maintenance information, is added the Ships' Work Breakdown Structure (SWBS) codes which are then entered on individual work requests as they are written.  Two immediate benefits are realized, the first being that work is better categorized and structured in the way in which it will be performed, and secondly, ship management can check a structured list (SWBS) of ship equipment and systems to ensure all discrepancies and needed repairs are documented. Easier submission and processing of work packaging by the ship and repair activity is another advantage.  Advantages and benefits from this improvement are not just proposed in this paper but are actually related to a two year experience in the USS KITTY HAWK (CV-63).  A proposal to make this improvement Navy-wide is presented.]]></description>
      <pubDate>Thu, 26 Jun 1980 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/154047</guid>
    </item>
    <item>
      <title>DESTROYER ENGINEERED OPERATING CYCLE (DDEOC) SYSTEM MAINTENANCE ANALYSIS DDG-37 CLASS MAIN LUBE OIL AND PROPULSION TRANSMISSION SYSTEMS SMA 37-107-240. REVIEW OF EXPERIENCE</title>
      <link>https://trid.trb.org/View/148653</link>
      <description><![CDATA[The Main Lube Oil and Propulsion Transmission Systems ROE includes an analysis of all available maintenance data sources.  The documented maintenance experience of the system was reviewed through analysis of data from the Maintenance Data System (MDS), Casualty Reports (CASREPs), and system overhaul records.  Initial findings from these sources were correlated with Planned Maintenance System (PMS) requirements, system alterations, and system technical manuals to identify maintenance problems.  Ship surveys were conducted and discussions were held with appropriate technical groups to validate identified problem areas, identify undocumented maintenance problems, and determine the status of current and planned actions affecting the Main Lube Oil and Propulsion Transmission Systems.  All findings were evaluated and appropriate conclusions developed. Recommendations were then formulated to implement existing and newly defined corrective actions to minimize the occurrence of identified maintenance problems and their impact on an extended operating cycle.]]></description>
      <pubDate>Mon, 31 Mar 1980 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/148653</guid>
    </item>
    <item>
      <title>ESTABLISHMENT OF RELIABILITY AND MAINTAINABILITY DATA BANK FOR SHIPBOARD MACHINERY. VOL. I</title>
      <link>https://trid.trb.org/View/142996</link>
      <description><![CDATA[In recent years there have been considerable advances in methods for the measurement, prediction, and control of reliability, with the main emphasis placed on electronic systems.  This report discusses the development and improvement of similar techniques for the mechanical systems in U.S. Navy ships.  The procedures and techniques involved are described in this volume.  Volume II gives data sheets for a very large number of specific items fitted in U.S. Navy ships; these list the number of units in service, the failure rates, and the reliability and maintainability indices.  All these terms are defined in Volume I.  Whereas previous studies have usually been concerned with main propulsion machinery, the current work is directed towards auxiliary and deck equipment.]]></description>
      <pubDate>Mon, 11 Feb 1980 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/142996</guid>
    </item>
    <item>
      <title>ALL AT LAND &amp; SEA'S FINGER-TIPS</title>
      <link>https://trid.trb.org/View/91712</link>
      <description><![CDATA[MacGregor operates an international servicing repair and maintenance network under the name Land & Sea (L & S).  It has service stations situated in the world's principal ports (the addresses of which appear on the inside back page of this issue) and that the network is managed and its work coordinated from a headquarters in Paris.  Probably not so well known is the existence, at Land & Sea Worldwide headquarters, of a computer installed in 1978, which is used to classify and record all the relevant information concerning the cargo access equipment installed on thousands of vessels-whether MacGregor-equipped or not.  The computer's data base contains a catalogue of all cargo ships in the world which have been built since 1961.  It records the following information: name of vessel; unique Lloyd's Register number; owner and/or manager; gross tonnage; type of ship; builder and yard number; year of build; and type and make of cargo access equipment.  This latter information is available for 10,750 ships.  A second computer program is concerned with all work carried out by L & S companies on cargo access equipment.  To prepare it, a study carried out by the headquarters company classified 49 separate jobs against which any type of repair can be entered, and from which it was possible to design a form suitable for processing by the computer.  Called the "universal inspection report" the form enables L & S companies worldwide to report in quick and simple fashion on any job performed and it incorporates both technical and commercial information.  On arrival at computer headquarters the data is fed into the machine, ready for instant retrieval whenever required.  Thus at the touch of a button a ship's complete cargo access repair history can be made available. As far as L & S operations are concerned this history goes back to January 1, 1978 and, as time goes by, the stored knowledge will become increasingly more valuable in helping to determine the cause of any operational problem.]]></description>
      <pubDate>Wed, 15 Aug 1979 00:00:00 GMT</pubDate>
      <guid>https://trid.trb.org/View/91712</guid>
    </item>
  </channel>
</rss>