National Academies Press: OpenBook

Framework for a National Database System for Maintenance Actions on Highway Bridges (2010)

Chapter: Chapter 2 - National Bridge Maintenance Database

« Previous: Chapter 1 - Background on Bridge Maintenance Programs at U.S. Departments of Transportation
Page 22
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 22
Page 23
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 23
Page 24
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 24
Page 25
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 25
Page 26
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 26
Page 27
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 27
Page 28
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 28
Page 29
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 29
Page 30
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 30
Page 31
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 31
Page 32
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 32
Page 33
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 33
Page 34
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 34
Page 35
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 35
Page 36
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 36
Page 37
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 37
Page 38
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 38
Page 39
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 39
Page 40
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 40
Page 41
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 41
Page 42
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 42
Page 43
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 43
Page 44
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 44
Page 45
Suggested Citation:"Chapter 2 - National Bridge Maintenance Database." National Academies of Sciences, Engineering, and Medicine. 2010. Framework for a National Database System for Maintenance Actions on Highway Bridges. Washington, DC: The National Academies Press. doi: 10.17226/14432.
×
Page 45

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

22 The National Bridge Maintenance Database (NBMD) is a collection of self-contained sets of data on bridge inventory, conditions, and maintenance work. Each dataset is established for one state DOT and for a fixed reporting period, usually one year. Data are collected from records of the U.S. NBI, from Pontis bridge databases of state DOTs, from DOT mainte- nance management systems, from maintenance work report- ing systems and from contract reporting systems. NBMD offers a uniform, consistent format and structure for data on bridge maintenance work, on the context of bridge maintenance work, and on the outcomes of bridge maintenance work. The NBMD data system is a set of standard data tables, stan- dard headings for data fields, standard keywords for indexing fields, and standard methods for the creation of unique identi- fiers for bridges, bridge elements, maintenance actions and maintenance resources. NBMD is instantiated as a set of plain text data files, and a set of XML documents each supported by an XML schema. Three concepts are applied to NBMD design. First, bridge maintenance data are collected into self-contained datasets that bundle all related maintenance, condition, and inventory data. Second, data are presented in plain language keywords so that information is easily understood without recourse to coding guides or lookup tables. Data headings, too, are pre- sented in plain language. Third, NBMD datasets are stackable. Unique IDs for bridges, elements, actions, and resources are established for each dataset and remain unique when datasets are merged. Merging allows for aggregations of large num- bers of data records when data analysis and statistical evalua- tions require it. A Database for Bridge Maintenance NBMD is an archive of maintenance events. An event is the execution of one maintenance operation at one bridge at one time. Each record in the database is a single event, and each record contains complete information on the work performed. The data include the following: 1. Structure, 2. Operation, 3. Dates, 4. Resources, and 5. Outcomes. The Structure. NBMD stores selected fields from NBI records and Pontis bridge databases. These include NBI and Pontis condition data together with data on structure type, route, milepost, custodian, structural size, age, construction materials, and administrative authority. The Operation. Maintenance work is identified using NBMD standard keywords for components and operations. The Dates. The date(s) of completion of the maintenance event are recorded. The Resources. Resources include usage of labor, materi- als, and equipment for DOT work, or pay items and quanti- ties for contract maintenance. Specific repair products and manufacturers can be stored. Resource data are used to com- pute total costs and unit costs for actions. The Outcomes. Outcomes include maintenance produc- tion and changes to conditions. Production may be expressed in units for the maintenance action and as the quantity of bridge element that is improved. Conditions are new values of bridge condition ratings achieved as a result of this mainte- nance event. Standard Data for Highway Bridge Maintenance Standard Bridge Components NBMD uses 14 standard bridge components (Table 9). Five components are named in the NBIS (Deck, Superstructure, C H A P T E R 2 National Bridge Maintenance Database

Substructure, Channel, Culvert). Seven more components are used by many DOTs as objects of maintenance actions (Joints, Drains, Railings, Bearings, Approaches, Movable Bridge, Elec- trical & Mechanical Systems). A twelfth component, Bridge, is used when actions are applied to an entire structure, or a specific component is not reported. The thirteenth compo- nent, nonBridge, is used for other assets. Standard Maintenance Operations NBMD uses eight standard maintenance operations: Clean, Reset, Coat, Repair, Replace, Modify, Emergency, and nonMaintenance (Table 10). Note that a Replace operation refers to the replacement of a part or portion of the bridge. Complete replacement of a bridge is not maintenance. In a 23 Component Description Approaches/ Embankments Approach slab and pavement, slopes, slope protection (other than channel banks), embankments. Bearings Bearing devices, both fixed and expansion. Bridge All bridges on the state's list, also a catch-all component for maintenance work not reported under other components. Channel Watercourse, flow restrictors/deflectors, banks, and bank protection. Culvert All types and sizes of culverts maintained by structures maintenance program. Deck The structural deck, wearing surface, waterproofing membrane, if any. Drains Scuppers, grates, pipes, outlets, features for over-the-edge drainage. Joints All joints in the deck, all maintainable (sealable) joints in superstructure and substructure components. Mechanical /Electrical Electrical or mechanical systems on bridges, includes all mechanical and electrical equipment for movable spans, all gates, lights and delineators for traffic. Movable span The operable parts and systems of a movable bridge. Includes deck and superstructure of movable span. nonBridge Other structural assets. Rails/Walks All deck accessories for directing/restricting vehicles and pedestrians. All sidewalks and medians. Substructure Piers, abutments, and their foundations. Wing walls. Superstructure Stringers, floorbeams, girders, truss members, arch members, etc. Table 9. Standard bridge components. Operation Description Clean/clear Sweeping, washing, debris removal, graffiti removal, clearing scuppers, clean-out drain lines. Reset Renew consumable elements such as lights, removable joint seals; Tighten bolts or rods, Lubricate bearings or other moving parts; Minor re-alignment of railings, repositioning of bearings. Coat All surface applications of paint, waterproofing, galvanic coatings, chemical preservatives, crack sealing materials. Repair Restoring damaged or deteriorated elements. Patching, welding, reinforcing, etc. Replace In-kind replacement of damaged or deteriorated elements. Modify Repair or replacement actions that yield changes to elements. These may be improvements to function as when drains are extended, changes in function as when relief joints are installed in rigid pavements, changes to vulnerability as by seismic retrofit, changes to strength by post-tensioning, jacketing, installation of scab plates, changes to clearances as by re-positioning of bracing in truss portals, or installation of a system for corrosion protection when none was present before. Emergency All repairs, replacements, and modifications completed as an immediate response to a sudden condition or event. nonMaintenance Operations, inspections. Table 10. Standard maintenance operations.

similar way, Modify operations include minor modifications, and exclude larger projects such as bridge rehabilitation. Maintenance activities are generic methods for maintenance operations. Activities are modifiers to operations, providing more specific reports of maintenance work. Each operation has its own set of activities. Actions are reported in a hierarchy of fields such as the following: Component → Operation → Activity → Mode NBMD employs standard keywords for components and operations and allows descriptive keywords for activities and modes. Actions must be reported by component, should be reported by operation, may be reported by activity, and might be reported by mode. This hierarchy admits both general (component only) and detailed (all four descriptors) report- ing of maintenance actions. Notes on Maintenance Operations Reset versus Repair/Replace. The replacement of con- sumable parts is a Reset operation. Parts such as light bulbs, fan belts, gaskets, and rubber joint elements are replaced as needed or on a set schedule. Repairs are made in response to deterioration or damage and entail parts that are not con- sumable. The designation of these activities as Repair or Replace correctly identifies the significance of the operation within the maintenance program, and correlates with costs since consumable elements are designed for replacement and other parts might not be. Modify versus Repair/Replace. Modify operations are repairs or replacements that change (usually improve) bridges. Improvements may include: greater clearances, greater resis- tance to fatigue, greater safety for traffic, greater resistance to high water flow, etc. Modify operations may be in response to obsolete features, as when railings are upgraded, or in response to damage or deterioration. Maintenance Activities Activities are descriptive keywords for NBMD bridge main- tenance operations. Examples of Activities for maintenance operations are presented in the following sections. Activities for Clean/Clear Operations. The Clean/Clear operation includes washing of structures, and removal of detri- tus, drift, and vegetation. Activities for Clean/Clear operations are described in Table 11. Activities for Reset Operations. The Reset operation provides expected maintenance for consumable parts or parts needing periodic lubrication or adjustment. Activities for reset operations are described in Table 12. Activities for Coat/Paint Operations. The Coat/Paint operation includes all application, maintenance and renewal of surface-applied sealers, paints and chemical treatments. Activities for Coat/Paint operations are described in Table 13. Activities for Repair Operations. The Repair operation restores original condition or functionality of bridge compo- nents after deterioration or damage. Repair does not include substantial replacement of components and does not include improvements to components beyond their original capacity or function. Activities for repair operations are described in Table 14. 24 Activity Description Wash The use of water at moderate pressure to clean bridge components. Zone Wash Washing of selected portions of components, usually those portions exposed to salt water, salt spray, or standing water. These can include parapets facing traffic, gutters in decks, and areas below open joints. Any selective washing of portions of structures. Sweep Dry removal of sand, grit, or other minor detritus on bridge components. Flush The use of water at higher flow rate and/or pressure to clear more substantial size or amounts of detritus on bridge components. Unclog and Cleanouts Maintenance of scuppers, troughs, pipes, and other drainage elements. Methods entail opening grates and cleanouts, removal of waste material, flushing as needed and reassembly of parts. Graffiti Removal or covering (masking) of unauthorized markings on bridges. Vegetation Trimming and/or removal of brush, trees, etc., on slopes, approach embankments, channel banks and within channels. Debris & Drift Removal of (loose) material on substructures, at foundations, on channel banks and within channels. This activity does not include channel dredging. Table 11. Activities for clean/clear operations.

25 Activity Description Consumables Replacing light bulbs, rubber joint elements, pavement reflectors, etc. Tighten Checking and tightening of bolts, anchors, rods and other threaded parts. Tighten also includes replacement of missing fasteners in otherwise complete connections. Caulk Removal and replacement of caulk in railings, fixed joints and construction joints. Lubricate Inspection and lubrication of bearings, expansion joints, railing joints and other moving or sliding parts. Reposition Inspection and re-centering or re-alignment of bearings, joints, and other parts needing periodic adjustment. Gates and Signals Inspection and servicing of traffic control systems, especially for movable bridges. Mechanical Equipment Inspection and servicing of mechanical parts of motion equipment for movable spans. Mechanical Equipment includes consumables (filters, belts, etc), lubrication, and adjustment of machinery. Electrical Equipment Inspection and servicing of electrical parts of motion equipment for movable spans. Electrical Equipment includes consumables (fuses, switches), and adjustment of equipment. Table 12. Activities for reset operations. Activity Description Paint Application of paint on bridge components, usually to an entire component. Spot Paint Application of paint on selected areas of components that may include: areas of deteriorated paint, areas of special exposure (splash zones), damaged areas (as by collision), etc. Seal Surface Application of water-repelling or other surface treatments, usually to concrete or asphalt surfaces. Seal Cracks Use of epoxy, high-weight methyl-methacrylate or other pourable materials to fill existing cracks. Usually applied to concrete surfaces, but can be crack sealing in asphalt surfaces and crack sealing in timber elements. Chemical Treatments Surface application of preservatives for timber components. Surface application of herbicides or pesticides on slopes as part of bridge maintenance. Surface Preparation Preparation of surfaces for coating or painting if separate tracking of preparation cost is desired. Otherwise, surface preparation is part of a coating or painting action. Table 13. Activities for coat/paint operations. Activity Description Patch Repairs to concrete components, concrete surfaces, or asphalt surfaces by filling with cementitious or bituminous material Re-attach/ Re-anchor Work to restore lost or weakened anchors for railings, joints, bearings, or other components. Straighten For metal components, the use of bending or heat to restore proper shape. Jack/Align For pavements or substructures, the use of jacking and filling to mitigate tilting or settlement. Reinforce/Strengthen Application of welds, scab plates, concrete jackets, cables, post-tensioning, etc., to restore strength to weakened structural components. Dredge/Grade Earth moving activities to repair shifted or scoured slopes and banks, or to re- establish channel depth and profile. Table 14. Activities for repair operations.

Activities for Replace Operations. The Replace operation provides in-kind replacement of bridge components in whole or in part. Activities for Replace operations are described in Table 15. Activities for Modify Operations. The Modify operation provides improvements to components. Improvements may mitigate observed problems in performance of components, may reduce vulnerability of components, or may deliver com- pliance with higher or newer standards, especially where stan- dards can be met within a maintenance project rather than a rehabilitation project. Activities for Modify operations are described in Table 16. Activities for Emergency Operations. Emergency activi- ties are performed in response to extreme events and/or sudden damage to structures. Activities for Emergency operations are described in Table 17. Operations, Activities, and Bridge Components Activities, more so than operations, may target specific com- ponents or construction materials. Frequent combinations of activities with bridge components are discussed in this section. Clean/Clear Operations. Among the activities for Clean/ Clear operations: Wash applies to structural elements, but not 26 Activity Description Individual Replacement of an individual unit of a component made up of a collection of units, such as replacement of individual bearings, individual joints, individual beams, individual piers. Section Replacement of a portion of a continuous component, such as a bridge deck, that is not a collection of similar units. Complete Replacement of an entire component. Complete replacement of a collection of elements. Complete replacement of a continuous component. Span Complete replacement of a component within one span of a multispan bridge. Table 15. Activities for replace operations. Activity Description Geometry Modifications to clearances including internal clearances of thru-trusses and thru- arches. Protection Addition of protection system that is new to the component, including corrosionprotection, fenders, channel modifications. Vulnerability Modifications that reduce vulnerability to fatigue, seismic loads, sudden fracture, etc. Strength/Capacity Modifications that increase load rating of bridges, flood/flow capacity of channels, flow capacity of drains, motion capacity of expansion joints or bearings, etc. Function Modifications that alter load paths or expansion regimes. These may be: helper bents, conversion to integral abutments, relief joints in approach pavements, etc. Assembly Modifications that provide a newer device, such as a joint, bearing, or railing in place of an older, obsolete device. Table 16. Activities for modify operations. Activity Description Post Investigations and repairs leading to load restrictions on structures. Shore Installation of temporary supports for decks or superstructures. Construction of “diapers” to catch loose materials. Closure, Partial Activities to exclude traffic from some portion of a structure, such as closures at weakened or blocked traffic lanes. Closure, Full Complete closure of a structure. Detour Activities needed to establish alternate routes around restricted or closed structures. Temporary Bridge Deployment and maintenance of temporary bridges. Table 17. Activities for emergency operations.

earth slopes and banks; Sweep applies to horizontal surfaces, but not vertical ones; Unclog applies to drains but not to open surfaces; Vegetation control applies to earth slopes and banks, but not to structural components. A list of likely applications of Clean/Clear activities to bridge components is shown in Table 18. Reset Operations. Among the activities for Reset opera- tions: Consumables maintenance applies to light bulbs, rub- ber parts of joints, but not other bridge components; Tighten applies to threaded parts; Caulk applies to fixed, closed joints in components, but not other joints; Lubricate applies to moving joints, bearings and rails, but not other parts; Gates/ Signals applies to traffic control on movable bridges, but not other traffic control; Equipment maintenance applies to motion equipment for movable bridges, but not other equipment. A list of likely applications of reset activities with bridge com- ponents is shown in Table 19. Coat/Paint Operations. Among the activities for Coat/ Paint operations: Paint applies to structural components, but not earth slopes and banks; Sealing applies to concrete and bituminous surfaces usually; Chemical Treatments apply to timber elements, and to control of vegetation. A list of likely applications of coat/paint actions with bridge components is shown in Table 20. Repair Operations. Among the activities for Repair oper- ations: Patch applies to concrete structural components and bituminous wearing surfaces; Re-attach applies to anchors for 27 Clean/Clear Bridge Components Wash All except earth slopes and banks. Zone wash All except earth slopes and banks. Sweep Decks, Joints, Approach pavement, Substructures. Flush All except earth slopes and banks. Unclog /cleanouts Drains. Graffiti Superstructure, Substructure, Parapets/Sidewalks, Culverts. Vegetation /trees Earth slopes and banks. Debris /Drift Substructures, Channels, Culverts. Table 18. Clean/clear—frequent uses of activities. Reset Bridge Components Consumables Bridge (lights), Joint seals. Tighten All components having bolts or rods. Caulk All except Embankment, Channel. Lubricate Bearings, Railings (at joints). Reposition Bearings, Railings, Channel (protection), Movable Span. Gates and signals Movable span. Mechanical equipment Movable span. Electrical equipment Movable span. Table 19. Reset—frequent uses of activities. Coat/Paint Bridge Components Paint All except Embankments, Channels. Spot paint All except Embankments, Channels. Seal surface Concrete or Bituminous elements of Deck, Wearing surface, Parapets/Railings/Sidewalks, Superstructure, Substructure, Embankment (protection), Culvert, Movable Span. Seal cracks Concrete or Bituminous elements of Deck, Wearing surface, Parapets/Railings/Sidewalks, Superstructure, Substructure, Embankment (protection), Culvert, Movable Span. Chemical treatment Preservatives for Timber Deck, Railings, Superstructure, Substructure, Culverts and Movable Spans. Herbicides/Pesticides for earth slopes and banks. Surface prep All structural components. Table 20. Coat/paint—frequent uses of activities.

joint, bearings, railings, etc.; Straighten applies to metal ele- ments; Jack applies to components that have tilted or settled; strengthen applies to structural components; Dredge/Grade applies to earth slopes, banks, and channels. A list of likely applications of Repair activities with bridge components is shown in Table 21. Replace Operations. Among the activities for Replace operations: Individual applies to items such as joints, bear- ings, railing sections and beams where the component is a collection of similar elements; Section applies to decks, wear- ing surfaces, and other components that are continuous; Complete is full in-kind replacement of a component; span is complete replacement of a component in one span of a multi- span bridge. A list of likely applications of Replace activities with bridge components is shown in Table 22. Modify Operations. Among the activities for Modify operations: Geometry applies to improvements to clearances; protection applies to new protection of structural components against corrosion, or channels against scour; Vulnerability applies to the potential for sudden failure of structural com- ponents; strength applies to increases in load rating for struc- tural components, and increases in motion or flow capacity for joints, drains, bearings and channels; Function applies to changes in load path or movement regime; Assembly applies to upgrades of joints, bearings, railings and other devices. A list of the frequent uses of Modify activities with bridge com- ponents is shown in Table 23. Emergency Operations. Among the activities for Emer- gency operations, Post applies to structural components; Shore applies to any component needing additional support; Clo- sure applies to bridges and culverts; Detour applies to bridges 28 Repair Bridge Components Patch All concrete or bituminous Deck/Wearing course, Parapets/Railings/Sidewalks, Superstructure, Substructure Approach/Embankment (protection), Channel (protection), Culvert, Movable Span. Re-attach/ re-anchor Deck (grate), Joints (armor), Joint (seal), Drains, Parapets/Railings/Sidewalks, Superstructure, Bearings, Substructure, Channel (protection), Culvert (metal), Movable Span. Straighten Parapets/Railings (metal), Superstructure (metal members), Substructure (metal elements), Culvert (metal), Movable Span. Jack/Align Approach slabs (mudjack), Substructures, Culverts. Reinforce/ Strengthen Deck (structural), Parapets/Railings/Sidewalks, Superstructure, Substructure, Culvert, Movable Span. Dredge/ Grade Approach/Embankment, Channel. Table 21. Repair—frequent uses of activities. Replace Bridge Components Individual Unit, all components. Section All components Complete All components Span All components Table 22. Replace—frequent uses of activities. Modify Bridge Components Geometry Bridge, Superstructure, Parapets/Railings/Sidewalks, Culvert, Movable Span. Protection Bridge, Deck, Parapets/Railings/Sidewalks, Superstructure, Substructure, Approach/Embankment, Culvert, Channel, Movable Span. Vulnerability Bridge, Parapets/Railings/Sidewalks, Superstructure, Substructure, Culvert, Channel, Movable Span. Strength/ capacity Bridge, Deck, Parapets/Railings/Sidewalks, Superstructure, Substructure, Culvert, Movable Span. Function Bridge, Deck, Joints, Drains, Parapets/Railings/Sidewalks, Superstructure, Bearings, Substructure, Movable Span. Assembly Bridge, Parapets/Railings/Sidewalks, Movable Span. Table 23. Modify—frequent uses of activities.

and culverts; Temporary applies to bridges and culverts. A list of likely applications of Emergency activities with bridge com- ponents is shown in Table 24. NBMD Database NBMD is a modular self-contained historical record of maintenance work at bridges. NBMD is a ledger of bridges, bridge conditions, work performed, resources expended, and costs. NBMD is a collection of datasets of identical structure (Figure 3). All information on maintenance actions, their costs, the bridges affected, and the outcomes are contained in a data- set. Each dataset contains information from a single DOT and a fixed reporting period. Each NBMD database is a collection of 13 tables (Figure 4). Of these, two tables contain maintenance work data (Pro- duction and Resources), two tables contain inventory data (Structure and Roadway), three tables contain bridge inspec- tion information (Inspection_Cross_Reference, Element_ Inspection, and Inspection_Event), three tables define the correspondences between NBMD data entries and DOT data entries (Activity_Definition, Element_Definition, and Resource_Definition), one table identifies data sources (Con- tact), one table lists element-level unit costs of maintenance (Element_Unit_Cost) and one table provides file size informa- tion used by NBMD software applications (Size). The tables are linked through global identifiers for bridges, mainte- nance events, and definitions for actions, bridge elements, and resources. Maintenance production is recorded as Events. An event is defined as a set of work activities conducted at the same time on a single structure. Each event provides a specific maintenance 29 Emergency Bridge Components Post Bridge, Deck, Superstructure, Substructure, Culvert, Movable Span. Shore Bridge, Deck, Joints, Drains, Parapets/Railings/Sidewalks, Superstructure, Bearings, Substructure, Approach/Embankment, Channel (bank), Culvert, Movable Span. Closure, partial Bridge, Culvert, Movable Span. Closure, full Bridge, Culvert, Movable Span. Detour Bridge, Culvert, Movable Span. Temporary bridge Bridge, Culvert, Movable Span. Table 24. Emergency—frequent uses of activities. Figure 3. National bridge maintenance database.

Operation and one bridge Component. Each event is asso- ciated with bridge inspections before and after the event. Inventory data are recorded for the structure and the road- way. A Resource is a quantity of labor, material, equipment, or contract pay item applied in the accomplishment of an action. NBMD Data Sources NBMD contains data adequate for computation of total costs and unit costs, generation of reports of maintenance accomplishments, creation of performance standards, and evaluations of maintenance actions. NBMD preserves the his- tory of maintenance events so that long-term performance of actions can be examined, life-cycle costs can be computed, and the evolution of maintenance programs can be tracked. Data include the following: • Crew card data in all headings: Work Administration, Work Performed, Location, Labor usage, Equipment Usage, Material Usage, Work Production. • Quantities of affected bridge component or element. • Bridge conditions before and after the maintenance event. • Total cost and unit costs of maintenance. While data from crew cards and contract tabulations are routinely available, other data may not be. The field collec- tion of element-level maintenance quantities is not usual. The immediate or at least near-term re-evaluation of element con- ditions after maintenance is not usual. In response, NBMD identifies and stores bridge condition data from inspections that occur before and after maintenance events. NBMD collects data from existing sources at DOTs includ- ing NBI files, Pontis bridge databases, maintenance manage- ments systems, and reporting systems for labor, materials, and equipment. NBMD identifies appropriate data fields in DOT sources. NBMD moves unmodified DOT data to appropriate storage areas in NBMD data tables and augments DOT data with NBMD keywords. The NBMD keywords provide the uni- form reporting and retrieval features that make any DOT’s data useful to all DOTs. The paths of DOT data into NBMD datasets, and the potential for sharing of NBMD datasets through internet sites is shown in Figure 5. Data Integrity NBMD is a long-term repository of bridge maintenance data. For this reason, datasets are self-contained. Datasets are complete with all bridge inventory and condition data and all maintenance action, accomplishment, resource and cost data. Changes over time to bridges (as by modification or replace- ment), inventory and condition data (by new coding formats), or maintenance data (by introduction of new methods or materials) will not affect the historical record and will not limit the future ability to retrieve and understand the histori- cal record. 30 Figure 4. NBMD dataset organization.

NBMD Tables There are 13 data tables in NBMD datasets. These are listed in Table 25. NBMD datasets are temporal. Each dataset contains com- plete data for bridges and maintenance work for a defined reporting period. Reporting periods can be a calendar year, a fiscal year, an inspection biennium, or other convenient reporting period. NBMD anticipates that one bridge will have one maintenance event of a given work-type within one report- ing period. One bridge may have more than one event, entail- ing different work-types, within one reporting period. 31 Maintenance Crew Cards Bridge Management System NBMD Collection Module NBMD Dataset Host Web Site NBMD User NBMD Public Dataset NBMD XML documents Contracts System Fleet Management Materials Management Existing New In te rn et Figure 5. Path for maintenance data. NBMD Table Description Activity_Definition_Table Mapping of DOT actions to NBMD descriptors. Contact_Table Contact information for agency providing bridge maintenance, condition and inventory data. Element_Definition_Table Mapping of DOT bridge elements to NBMD descriptors. Element_Inspection_Table Element-level condition data adapted from Pontis’ eleminsp table. Element_Unit_Cost_Table Unit costs of maintenance actions generated by NBMD viewer utility. Inspection_Cross_Reference_Table List of NBI and element-level inspections before and after maintenance events. Inspection_Event_Table table or from NBI files. NBI condition and appraisal ratings collected from Pontis’ inspevnt NBMD_Size Line counts for NBMD data tables. Generated by NBMD_Size utility. Production_Table Maintenance work activities, production (accomplishment), and costs. Resource_Definition_Table Mapping of DOT equipment, labor, and material IDs to NBMD descriptors. Resource_Table Equipment, labor and material types, quantities, and costs for maintenance events. Roadway_Table roadway table or from NBI files. Structure_Table bridge table or from NBI files. Route inventory data, mostly NBI fields, collected from Pontis’ Bridge inventory data, mostly NBI fields, collected from Pontis’ Table 25. NBMD data tables.

32 NBMD Identifiers NBMD generates global identifiers for maintenance events, bridges, bridge elements, and maintenance resources (Table 26). Global identifiers link events, bridges, etc., across tables in a dataset, and allow datasets to be merged without loss of identity of events, bridges, etc. Identifiers are built up as combinations of existing IDs that are unique within DOTs’ bridge populations and NBMD dataset labels that tie records to particular DOTs and reporting periods. NBMD Naming Conventions NBMD employs conventions for simple, predictable forma- tion of NBMD identifiers (Table 27). The Dataset identifier is formed with abbreviations for bridge owners plus reporting years. Bridge IDs are formed with Dataset identifiers plus DOTs’ own structure ID. DOT structure IDs can be the NBI structure numbers or Pontis brkeys. Either is unique within one DOT. Combined with the dataset ID, the resulting NBMD bridge ID is unique among all bridge owners and all report- ing periods. By similar steps, identifiers are formed for bridge elements and maintenance resources. Identifiers for maintenance events combine the NBMD bridge ID and abbreviations for mainte- nance components and operations. Since NBMD bridge IDs include dataset identifiers, the resulting event IDs indicate bridge owners, reporting periods, bridges, and maintenance actions. The parts of each identifier are separated by left brackets. This allows parsing of identifiers in software applications. Note that DOTs are identified as state postal codes followed by the string “DOT.” For many states, the NBMD identifier differs from the state’s own abbreviation for their transporta- tion department. COAM String Abbreviations for maintenance Component and Opera- tion are part of maintenance event IDs. The abbreviations are shown in Table 28. Resource IDs for equipment and materials are formed from the dataset identifier, a static string “Res” and DOTs’ identify- ing number. Labor resources are identified as dataset, Res, and abbreviations of labor job titles. Abbreviations for Tennessee DOT job titles are shown in Table 29. NBMD Keywords NBMD employs plain-language keywords to identify main- tenance actions, maintenance resources and bridge elements. This makes NBMD tables readable and allows for the intro- duction of additional keywords as needed without revision of older data records. Additional keywords will likely be needed in the future for new bridge components, new construction materials, new maintenance materials, and new maintenance actions. NBMD keywords are either standard keywords or descrip- tive keywords. Standard keywords are proposed in this proj- ect, and are intended to provide simple, definite description of bridge elements, maintenance actions, and maintenance Data Field Description Dataset DOT{Year Global identifier attached to all records in a set of bridge work, condition, and inventory data. NBMD_Bridge_ID Dataset{Structure_Number Global identifier for each structure. The structure_number is the NBI data, usually, but can be the Pontis bridge key (brkey). The NBMD ID is unique for the structure, the DOT, and the reporting period. NBMD_Event_ID NBMD_Bridge_ID{COAM Global identifier for a maintenance event. COAM is a concatenation of abbreviations for bridge component, operation, activity and mode. NBMD_Elemkey Dataset{Elem{DOT_Elemkey Global identifier for bridge elements. The static string “Elem” marks this as an element ID. NBMD_Inspection_ID NBMD_Bridge_ID{Insp{Inspection_Date Global identifier for a bridge inspection. The static string “Insp” marks this as an inspection ID. Resource_ID Dataset{Res{Cat{DOT_Resource_ID Global identifier for resources used in maintenance events. Cat strings are abbreviations for resource categories. The static string “Res” marks this as a resource ID. Table 26. Global identifiers for NBMD.

33 resources. Standard keywords may evolve over time, but may be regulated by an NBMD users’ group. Descriptive keywords provide additional information on bridge elements, maintenance actions, or maintenance resources. These, too, work best when all users (all DOTs) employ a common set of keywords. But descriptive keywords are not regulated. Descriptive keywords can be specific to indi- vidual DOTs. Descriptive keywords provide positive identifi- cation of specific elements, actions, or materials at a DOT. Standard keywords and descriptive keywords are used in separate data fields in NBMD. Maintenance Actions Bridge maintenance actions are described by four keyword fields. The first two, Component and Operation, are NBMD standard keywords. The second two, Activity and Mode, are descriptive (Table 30). Table 31 lists the standard keywords for Component and Operation. Among the Component keywords, Mech/Elec is for mechanical and electrical systems of movable bridges, and NBMD Identifier Formation Example Note Dataset DOT{Year CaDOT{2006 California data for fiscal year 2006 Action_ID Dataset{Act{DOT_ID CaDOT{2006{Act{H30060 California deck overlay action, 2006 report Bridge_ID Dataset{Bridge_ID MiDOT{2005{82182072000R010 Michigan bridge ID,2005 reporting period Element_ID Dataset{Elem{DOT_ID PaDOT{2008{Elem{48 Pennsylvania concrete slab element in 2008 report Event_ID Bridge_ID{COAM string TnDOT{2007{16I002400141{Drn{Rpr Repairs to drains in 2007 for Tennessee structure Inspection_ID Bridge_ID{Insp{Date OrDOT{2006{S8837A064 01072{Insp{2005/03/07 Oregon inspection in 2005 related to maintenance work in 2006. Resource_ID Dataset{Res{DOT_ID TnDOT{2007{Res{EQA127 Tennessee equipment resource in 2007 report TnDOT{2007{Res{HMW3 Tennessee Highway Maintenance Worker in 2007 report Table 27. NBMD dataset identifier—examples. Components Abbr. Operations Abbr. Approach/Embankment ApEm Clean Cln Bearing Brg Coat Cot Bridge Brd Reset Rst Channel Chn Repair Rpr Culvert Cul Replace Rpl Deck Dk Modify Mod Drain Drn Emergency Emg Joint Jt nonMaintenance nMnt Mech/Elec MeEl MovableSpan Mov nonBridge nBrd Rail/Walk RWk Substructure Sub Superstructure Sup Table 28. NBMD abbreviations for COAM strings. Job Title Abbreviation County Supervisor CySpv Assist County Supervisor AsCySpv Floating Crew Supervisor 2 FlCwSpv2 Floating Crew Supervisor 1 FlCwSpv1 Highway Maintenance Worker 3 HMW3 Highway Maintenance Worker 2 HMW2 Highway Maintenance Worker 1 HMW1 Carpenter 2 Cpt2 Carpenter 1 Cpt1 Other Oth Table 29. Abbreviations for job titles— Tennessee DOT.

nonBridge identifies assets other than bridges and culverts, such as tunnels, retaining walls, sign bridges, and other struc- tural assets that are reported in a DOT’s maintenance data sys- tem. Among Operation keywords, nonMaintenance indicates inspection, operation (of movable spans), complaint investi- gation, and other activities that may be performed by DOT crews and appear in maintenance data systems. Standard keywords are exclusive. No component key- word appears in the operation list, and no operation keyword appears in the component list. Keywords used in activity and mode should also be exclusive; keywords in each field should be used only in that field. NBMD maintenance actions are identified at least by a component keyword, and may be identified by a component plus any among the operation, activity, and mode keywords. Bridge Elements Bridge elements are described with five NBMD keyword fields: Component, Material, Form, Part, and Protection. Component and Material are standard keywords. Part, Form, and Protection are descriptive. Table 32 lists the standard keywords for Component and Material, and the keywords for Part, Form, and Protection that appear in the current NBMD datasets. The Component keywords for bridge ele- ments are identical to the Component keywords for mainte- nance actions. NBMD Resources Resources used in maintenance are described by a standard keyword for resource Category. Standard categories are: Equip- ment, Labor, Material, and Other. Three descriptive key- words may be used. These are resource Group, Keyword_A, and Keyword_B. These keywords describe the type and capac- ity of equipment, the grade and title or labor, and the kind and grade of materials. Two more resources keywords, Manufac- turer and Product, are used only for materials and identify spe- cific products used in maintenance actions. NBMD Tables and Data Fields NBMD tables and data fields are presented in this section. Tables are presented in alphabetical order. Activity_Definition_Table The NBMD Activity_Definition_Table (Table 33) relates the codes and titles for DOT maintenance actions to the NBMD keywords for Component, Operation, Activity, and Mode. DOTs’ units of measurement for actions are reported. The NBMD dataset ID is present, linking each maintenance action to a specific DOT and reporting period. Activity definition tables are formed for each dataset by collecting all unique DOT actions and assigning appropriate NBMD keywords to them. Within a single DOT, the IDs for maintenance actions may persist over many years, and so activity definition tables for different reporting years may have many identical entries. Examples of activity definition tables are provided in Appendix B. Contact_Table The NBMD Contact_Table (Table 34) identifies datasets, their DOT sources, and staff contacts at DOTs. Each NBMD dataset has one or more contacts. These are one or more per- sonnel at a single DOT or other bridge owners’ agency. 34 Keyword Field Type Description Maintenance Actions Component Standard Name of the structural component. Operation The category of maintenance work. Activity Descriptive Type of work within the category. Mode Further description of the work; may identify a material type. Table 30. NBMD descriptors for maintenance actions. Component Keywords Operation Keywords Approach/Embankment Bearing Bridge Channel Culvert Deck Drain Joint Mech/Elec Movable Span nonBridge Rail/Walk Substructure Superstructure Clean Coat Emergency Modify Repair Replace Reset nonMaintenance Table 31. NBMD standard keywords for maintenance actions.

35 Component Material Part Form Protection Approach/Embankment Bearing Bridge Channel Culvert Deck Joint nonBridge Rail/Walk Substructure Superstructure Asphalt Concrete Elastomeric Metal PS Concrete Steel Timber Abandoned Abutment Arch Assembly Beam Cable Cap Column Compression Corrugated Deck Truss Electrical/Mechanical Sys Enclosed Expansion Fender Finger Fixed Flag Flume Footing Footing seal Frame Grid Movable Paint Ped/Bike Pier Pile Pile Cap Pin/Hanger Plate Plug Pourable Private Railing Railing with Sidewalk Railroad Seal Sign Slab Slope Protection Stringer Thru Truss Tunnel Cap/Footing Headwall Sidewalk Trough Bottom Chord Box Concrete- filled Deck Crack Disk Drilled Fatigue Impact Modular Open Pack Rust Pot Scour Section loss Settlement Shell Soffit Strip seal Wall Portal Roadway Wearing Surface Damage Incident Compression AC Overlay AC Overlay - Protected Cathodic Coated Coated Bars Painted Rigid Overlay Thin Overlay Bituminous overlay Bituminous overlay, coated bars Concrete encased Galvanized Bituminous overlay, Membrane, coated bars Rigid overlay, coated bars Table 32. NBMD element standard keywords.

Element_Definition_Table NBMD Element_Definition_Tables relate DOT IDs and titles for bridge elements to NBMD keywords for bridge ele- ments. Element_Definition_Tables list the units of measure- ment for elements. Element_Definition_Tables (Table 35) are developed partly from Pontis elemdefs tables, and partly from element coding guides published by DOTs. Pontis elemdefs tables are collected as Pontis Data Interchange (PDI) files. PDI files are converted to tab-text files with column headings using an application developed in this project (see Appendix E). Similar to DOT maintenance activities and their defini- tions, the set of bridge elements at a DOT continues with few changes from year to year. NBMD datasets from a single DOT will have similar Element_Definition_Tables with many iden- tical records. Element_Inspection_Table NBMD’s Element_Inspection_Tables are adaptations of Pontis eleminsp tables. Element_Inspection_Tables are formed with selected Pontis data fields obtained from PDI files, iden- 36 Data Field Description Dataset Global identifier Action_ID Dataset{Act{DOT_Action_ID DOT’s title for work activity this as an action ID. NBMD identifier for this DOT action and dataset. The static string ‘Act’ marks DOT_Action_ID DOT’s code for maintenance activity DOT_Action_Description DOT_Unit DOT’s reporting unit for this work activity NBMD_Component NBMD standard keyword for bridge component NBMD_Operation NBMD standard keyword for maintenance operation NBMD_Activity Descriptive keyword for maintenance action NBMD_Mode Descriptive keyword for maintenance action NBMD_Unit NBMD unit of measure, if different from DOT unit NBMD_CoamString Standard abbreviations for bridge component and maintenance operation Table 33. NBMD Activity_Definition_Table. Data Field Description Dataset Global identifier Contact_ID DataSet{Con{Seq ID. The Seq (sequence) is 1, 2, 3 … as needed for the contacts contributing to this dataset. Unique identifier for this contact record. The static string ‘Con’ marks this as a contract Type General type of bridge information; one among maintenance, inventory, or condition data. Last_Name Last name of staff contact First_Name First name of staff contact Initial Middle initial(s) of staff contact Agency Name of transportation department, or other bridge owner Office / Branch Office within transportation department Title Address_1 Postal address Staff contact’s job title Address_2 City Staff contact information State Zip telephone cell_phone email website Table 34. NBMD Contact_Table.

tifiers for NBMD bridges, inspections, and elements and aug- mented by elements’ units of measurement (Table 36). Element_Unit_Cost_Table NBMD’s Element_Unit_Cost_Tables are generated from data in Production_Tables and Element_Inspection_Tables. Element_Unit_Cost_Tables are generated after other tables in a dataset have been formed from DOT inputs (Table 37). Element_Unit_Cost_Table reports the costs and improve- ments to one element at one bridge due to one maintenance event, and the median costs for unique pairs of bridge ele- ments and maintenance actions. A single maintenance event may improve several elements. The resulting table will contain as many records as improved elements. A single bridge and element may be improved by different maintenance events (events may differ by maintenance Operation). The resulting table will contain as many records as maintenance events. 37 Data Field Note Dataset Global Identifier NBMD_Elemkey Dataset{Elem{DOT_Elemkey Global identifier for bridge element, tied to dataset DOT_Elemkey From Pontis (usually), the numeric ID for an element elemshort From Pontis, short name for bridge element elemlong From Pontis, long name for bridge element DOT_Unit Unit of measurement for bridge element Statecnt Number of condition states for bridge element Component NBMD keyword for bridge component Material NBMD keyword for element material Part NBMD keyword for specific part of bridge component indicated by this element Form NBMD keyword for form of element (such as open beam versus box beam) Protection NBMD keyword for paint, membrane, coated rebar or other feature offering protection to the bridge element Table 35. Element Definition Table. Data Field Description DataSet Global Identifier NBMD_Bridge_ID Global Identifier NBMD_Inspection_ID NBMD_Bridge_ID{Insp{Inspection_DateGlobal Identifier Structure_Unit From Pontis NBMD_Elemkey Global Identifier DOT_Element_Key From Pontis, numeric ID of bridge element Environment_Key From Pontis Element_Total_Quantity From Pontis Element_Quantity_Unit From NBMD Element_Definition_Table Quantity_State_1 From Pontis, element-level condition report of element quantities. Quantity_State_2 Quantity_State_3 Quantity_State_4 Quantity_State_5 Percentage_State_1 From Pontis, element-level condition report of element percentages. Percentage_State_2 Percentage_State_3 Percentage_State_4 Percentage_State_5 Element_Scale_Factor From Pontis brkey From Pontis inspkey From Pontis Notes From Pontis Table 36. NBMD Element_Inspection_Table.

Element_Unit_Cost_Tables contain the maintenance events that improve element conditions as revealed in element-level inspection reports, provided that event Components agree with element Components. The Cost_Status field indicates whether total costs of one maintenance event are distributed to one bridge element, to multiple elements, or to multiple bridge components. The computation of element-level unit costs is discussed in Chapter 5. Inspection_Cross_Reference_Table NBMD Inspection_Cross_Reference_Tables link each maintenance event to three NBI safety inspections and three element-level inspections (Table 38). These are: inspections nearest in date to maintenance events, inspections one cycle prior to events, and inspections one cycle after. Together, these three inspections can reveal the changes (improve- 38 Data Field Description NBMD_Bridge_ID Global Identifier NBMD_Event_ID Global Identifier NBMD_Inspection_ID Global Identifier Inspection_Type NBMD standard keyword: Element or NBI Inspection_Order NBMD standard keyword. Inspections are Prior, Middle or Post, meaning prior to maintenance, nearest to maintenance, or after maintenance Inspection_Date Date of inspection presented as YYYY/MM/DD brkey From Pontis, key to bridge record inspkey From Pontis, key to inspection record Table 38. NBMD Inspection_Cross_Reference_Table. Data Field Description Dataset NBMD global identifier NBMD_Event_ID NBMD global identifier NBMD_Bridge_ID NBMD global identifier Action_Component Bridge component identified in event record Action_Operation Maintenance operation identified in event record Event_Total_Cost Event total cost allocated to this element NBMD_Prior_Insp Inspection ID, inspection before maintenance event NBMD_Post_Insp Inspection ID, inspection after maintenance event NBMD_Element_ID NBMD global identifier Element_long Long name of element Element_Unit Unit of measurement for element Prior_Total_Quantity Element total quantity prior to maintenance event Post_Total_Quantity Element total quantity after maintenance event Element_Component NBMD keyword for element component Element_Material NBMD keyword for element material Element_Form NBMD keyword for element form Element_Part NBMD keyword for element part Element_Protection NBMD keyword for element protection Improvement_Quantity Quantity of element moved to better condition state Prior_State Element condition before maintenance; best condition state among states that lose quantity after maintenance Post_State Element condition after maintenance; worst condition state among states that gain quantity after maintenance Inventory_Change Change in total quantity of element due to maintenance Cost_Type Cost of single event, or median cost of similar events Element_Unit_Cost Event cost divided by improved quantity of element Element_Unit_Cost_Unit Units of measurement for unit cost Cost_Status One among Single element, Multiple elements, Multiple components Table 37. Element_Unit_Cost_Table.

ments) to bridge element conditions as a result of mainte- nance events. Inspection_Cross_Reference_Tables are generated from Pontis inspevnt tables and NBMD Production_Tables using an NBMD software utility called Inspection Cross (see Appendix E). Inspection_Event_Table NBMD’s Inspection_Event_Tables contain NBI condition and appraisal ratings (Table 39). Inspection_Event_Tables can be generated from Pontis’ inspevnt table or from FHWA files of NBI data. NBMD_Size NBMD’s Size_Tables are used by the NBMD viewer appli- cation to establish the sizes of arrays when data tables are loaded (Table 40). Size_Tables list files included in the dataset and the number of lines in each file. Size_Tables are created 39 Data Field Description DataSet Global Identifier NBMD_Bridge_ID Global Identifier NBMD_Inspection_ID Global Identifier brkey From Pontis, bridge key inspkey From Pontis, inspection key Inspection_Date Date of inspection, YYYY/MM/DD NBI_Done Yes / No indicated as 1/0, from Pontis Element_Level_Done Yes / No indicated as 1/0, from Pontis Element_Inspection_Date Date of inspection presented as YYYY/MM/DD UW_Required 1/0 indicator that underwater inspection is required UW_Done 1/0 indicator that underwater inspection was performed FC_Required 1/0 indicator that fracture critical member inspection is required FC_Done 1/0 indicator that fracture critical member inspection was performed Special_Required 1/0 indicator that special or other inspection is required Special_Done 1/0 indicator that special or other inspection was performed Appraisal_Date Date of NBI appraisals Rail_NBI_36A NBI item 36 for traffic safety features Rail_Transition_NBI_36B Approach_Rail_NBI_36C Approach_Rail_End_NBI_36D Open_Posted_Closed_NBI_41 NBI item 41 for structure open, posted or closed. Deck_Geometry_NBI_68 NBI item 68 Deck geometry Underclearance_NBI_69 NBI item 69 Underclearances Waterway_Adequacy_NBI_71 NBI item 71 Waterway adequacy Pier_Protection_NBI_111 NBI item 111 Pier or abutment protection Scour_Critical_NBI_113 NBI item 113 Scour Critical Bridges Approach_Alignment_NBI_72 NBI item 27 Approach roadway alignment Deck_Rating_NBI_58 NBI item 58 Deck condition rating Superstructure_Rating_NBI_59 NBI item 59 Superstructure condition rating Substructure_Rating_NBI_60 NBI item 60 Substructure condition rating Channel_Rating_NBI_61 NBI item 61 Channel and channel protection Culvert_Rating_NBI_62 NBI item 62 Culvert condition Structural_Evaluation_NBI_67 NBI item 67 Structural evaluation NBI_Status NBI status NBI_Sufficiency_Rating NBI sufficiency rating NBI_Sufficient_Prefix NBI position 428 Notes From Pontis Table 39. NBMD Inspection_Event_Table. Data Field Description File path and name Tab-text file of NBMD data File lines Count of lines in NBMD tab-text file Table 40. NBMD Size_Table.

by a software utility, NBMD_Size, after all other tables in a dataset have been assembled. Size_Tables must be updated by the software application if any tables in a dataset are modified. Production_Table NBMD Production_Tables report the production (accom- plishments) of maintenance actions at bridges (Table 41). Each record identifies a bridge, an NBMD maintenance com- ponent and operation, the unit of measurement, the produc- tion amount, total cost, and unit cost. Records also include DOTs’ identifying codes and titles for actions, DOT reference numbers such as contract number, crew number, work order or other identifying number. NBMD Production_Tables provide total cost for each NBMD action at each bridge. Most production records com- bine multiple work reports of DOTs. Each NBMD production record can be the sum of more than one DOT work order, or DOT maintenance action, if these orders and actions con- tribute to a single NBMD action at a single bridge. As a result, DOT work order numbers may be absent from an NBMD production record, if multiple work orders contribute. DOT action ID may be absent from an NBMD production record, if multiple actions contribute. DOT units of measurement may be absent if the contributing DOT records have differ- ing units. Resource_Definition_Table NBMD Resource_Definition_Tables relate DOT identifiers for equipment, material and labor to NBMD resources cate- gories (Table 42). Categories are standard keywords. Other keywords are descriptive. For materials, the table can track manufacturer and product names. Resource_Table NBMD Resource_Tables identify the resources used in maintenance events, together with resource quantities and costs (Table 43). Records identify maintenance events and resources. Each record may combine several DOT records for resource use. Roadway_Table NBMD Roadway_Tables contains NBI inventory data for routes on and under bridges (Table 44). Roadway_Tables con- tain records needed for the maintenance events in a dataset. 40 Data Field Description Dataset Global identifier NBMD_Bridge_ID Global identifier NBMD_Event_ID Global identifier. Concatenation of NBMD_Bridge_ID and abbreviations for component and operation NBMD_DOT_Event_ID Concatenation of NBMD_Bridge_ID and DOT activity code, if available. DOT_Bridge_ID Structure_Number from NBI records, or bridge key (brkey) from a DOTs’ Pontis bridge database. Start_Date Earliest record for this maintenance event, shown as YYYY/MM/DD End_Date Latest record for this maintenance event, shown as YYYY/MM/DD. DOT_Activity_ID DOTs’ identifying code for maintenance activity DOTs’ reference number such as work order, contract number, crew number or DOT_Activity_Title DOTs’ title for maintenance activity DOT_RefA other identifying code useful for retrieval of internal DOT records DOT_RefB Additional DOT reference number NBMD_Component NBMD standard keyword NBMD_Operation NBMD standard keyword NBMD_Activity NBMD descriptive keyword NBMD_Mode NBMD descriptive keyword NBMD_CoamString Abbreviations for component and operation DOT_Production Quantity of work accomplished DOT_Production_Unit Measurement unit for work DOT_Unit_Cost Total cost divided by work quantity DOT_Unit_Cost_Unit Measurement unit for unit cost DOT_Total_Cost Cost reported by DOT, summed from multiple work records or resource records Cost_Unit Monetary unit for total cost Notes Table 41. NBMD Production_Table.

41 Data Field Description Dataset Global identifier Resource_ID Global identifier DOT_Resource_ID DOT’s identifying code for resource DOT_Resource_Description DOT’s title for resource. DOT_Unit Unit of measurement for use or cost of resource NBMD_Resource_Category NBMD standard keyword (labor, equipment, material, other) NBMD_Resource_Group NBMD descriptive keyword NBMD_Resource_KeywordA NBMD descriptive keyword NBMD_Resource_KeywordB NBMD descriptive keyword NBMD_Resource_Manufacturer Name of manufacturer, for materials NBMD_Resource_Product Name of product, for materials NBMD_Unit Unit of measurement for NBMD NBMD_Unit_Cost Unit cost of resource in DOT units notes Notes on resource record Table 42. NBMD Resource_Definition_Table. Data Field Description Dataset Global identifier Resource_ID Global identifier NBMD_Bridge_ID Global identifier NBMD_Event_ID Global identifier NBMD_DOT_Event_ID Concatenation of NBMD_Bridge_ID and DOT activity code, if available DOT_Bridge_ID Structure_Number from NBI records, or bridge key (brkey) from Pontis bridge database Start_Date Earliest resource record for this maintenance event End_Date Latest resource record for this maintenance event DOT_Activity_ID DOT’s identifying code for maintenance activity DOT’s title for maintenance activity DOT’s reference number such as work order, contract number, crew DOT’s identifying code for resource DOT’s title for resource DOT’s category for resource DOT_Activity_Title DOT_RefA number or other identifying code useful for retrieval of internal DOT records on bridge maintenance work DOT_RefB Additional DOT reference number DOT_Resource_ID DOT_Resource_Description DOT_Resource_Category DOT_Resource_Quantity Use of resource in hours, miles, mass, volume, etc. DOT_Quantity_Unit Unit for measurement of resource use DOT_Unit_Cost Unit cost of resource DOT_Unit_Cost_Unit Units for unit cost DOT_Total_Cost Total cost for this resource in this event DOT_Total_Cost_Unit Units for total cost NBMD_Resource_Category NBMD standard keyword NBMD_Resource_Group NBMD standard keyword NBMD_Resource_Keyworda NBMD descriptive keyword NBMD_Resource_Keywordb NBMD descriptive keyword NBMD_Resource_Manufacturer Name of manufacturer, for materials NBMD_Resource_Product Name of product, for materials NBMD_Unit Unit for NBMD measurement of resource, if different from DOT NBMD_Unit_Cost Unit cost of resource in NBMD units of measurement notes Notes on use of resource Table 43. NBMD Resource_Table.

In any one reporting period, maintenance events affect a sub- set of bridges in a DOT’s network. These bridges are included in Roadway_Tables. Roadway_Tables can be formed from NBI text files or from Pontis roadway tables. Structure_Table NBMD Structure_Tables contain NBI inventory data including bridge owner, year built, design type and material types (Table 45). In a single dataset, Structure_Table con- tain records only for bridges having maintenance events. Structure_Tables can be formed from NBI text files or from the Pontis’ bridge table. File Formats for NBMD Tables NBMD tables are presented as tab-delimited text (tab-text) files and as XML documents. Tab-Text Files Tab-text files are convenient for the assembly of NBMD tables. NBMD collects data from many DOT sources, and must incorporate information from databases, from spread- sheets, and from other text files. In this context, text files are the simplest intermediary files for collection and assembly of NBMD data. Tab-text files of NBMD tables all have similar layout. The first line contains headings for all data fields. The second line and all following lines are data records. All lines contain the same number of columns, set off by tab characters. An example tab-text file, a list of bridge maintenance actions in data collected from Tennessee DOT, is shown in Figure 6. Tab-text files can be opened in MS Excel by “drag-drop” operations. This allows quick views of NBMD data. Tab-text data entries are sometimes altered in Excel (date fields, and any field containing “/” can be misread by Excel). Saving NBMD tables from Excel is not recommended. XML Documents NBMD data tables are presented as XML documents con- forming to XSD schemas prepared in this project. XML docu- ments are self-defining sets of data fields and data values. XML documents offer definite and unaltered input of data tables to applications such as MS Excel and MS Access. Templates can be created to display XML documents in web browsers. A portion of the XML document for Oregon’s Inspection_ Cross_Reference_Table is shown in Figure 7. File structure is repetitive. Each data field is identified by name within “< >” brackets Next the data entry appears. Last, the data field is terminated by </ > brackets. Each complete data record is enclosed by <Inspection_Cross_Reference>. . .</Inspection_ Cross_Reference> tokens. The XML document continues with similar structure for all records in the table. 42 Data Field Description Dataset Global identifier NBMD_Bridge_ID Global identifier NBMD_Road_ID Global identifier Record_Type NBI item 5A Record Type Kind_Highway From Pontis roadway table Level_Service NBI item 5C Designated level of service Route_Prefix NBI item 5B Route signing prefix Route_Number NBI item 5D Route number Direction_Suffix NBI item 5E Directional suffix Roadway_Name From Pontis roadway table Kilometer_Post NBI item 11 Kilometerpoint Lanes_On NBI item 28A Lanes on the structure Lanes_Under NBI item 28B Lanes under the structure Functional_Class NBI item 26 Functional classification of inventory route ADT NBI item 29 Average daily traffic Year_ADT NBI item 30 Year of average daily traffic Direction_Traffic NBI item 102 Direction of traffic ADT_Pct NBI item 109 Average daily truck traffic, percentage Road_Speed From Pontis roadway table Roadway_Width NBI item 51 Bridge roadway width curb-to-curb Approach_Width NBI item 32 Approach roadway width Table 44. NBMD Roadway Table.

43 Data Field Description Dataset_ID Global identifier NBMD_Bridge_ID Global identifier brkey From Pontis, bridge key bridge_id From Pontis, usually a short form of the NBI structure number Structure_Number NBI item 8 Structure number Structure_Name From Pontis Features_Intersected NBI item 6A Features intersected District NBI item 2 Highway agency district County NBI item 3 County (parish) code Facility NBI item 7 Facility carried by structure Location NBI item 9 Location Custodian NBI item 21 Maintenance responsibility Owner NBI item 22 Owner Admin_Area From Pontis State_Code NBI item 1 State code Year_Built NBI item 27 Year built Year_Reconstructed NBI item 106 Year reconstructed Historical_Significance NBI item 37 Historical significance Design_Load NBI item 31 Design load Type_Service_Bridge NBI item 42A Type of service on bridge Type_Service_Under NBI item 42B Type of service under bridge Number_Spans_Main NBI item 45 Number of spans in main unit Number_Approach_Spans NBI item 46 Number of approach spans Length_Maximum_Span NBI item 48 Length of maximum span Structure_Length NBI item 49 Structure length Deck_area From Pontis Bridge_Median NBI item 33 Bridge median Skew NBI item 34 Skew Material_Type_Main NBI item 43A Structure type main, kind of material/design Design_Type_Main NBI item 43B Structure type main, type of design/construction Material_Type_Approach NBI item 44A Structure type approach, kind of material/design Design_Type_Approach NBI item 44B Structure type approach, type of design/construction Deck_Structure_Type NBI item 107 Deck structure type Type_Membrane NBI item 108B Type of membrane Type_Wearing_Surface NBI item 108A Type off wearing surface Deck_Protection NBI item 108C Deck protection Deck_Width NBI item 52 Deck width, out-to-out Left_Walk_Width NBI item 50A Left curb/sidewalk width Right_Walk_Width NBI item 50 Right curb/sidewalk width Notes Table 45. NBMD Structure_Table. XML documents conform to schema defined for each NBMD table, and stored in “XSD” files. Schema files list the data fields that belong in each table together with informa- tion on types of data entries and the number of data entries required and allowed. The XSD file for the Inspection_ Cross_Reference_Table is shown in Figure 8. The full set of XML schema files is available in the xsd directory of the NBMD system distribution.

Dataset Action_ID DOT_Action_ID DOT_Action_Description DOT_Unit NBMD_Component NBMD_Operation NBMD_Activity TnDOT{2007 TnDOT{2007{Act{400 400 SPECIAL PROJECTS each Bridge TnDOT{2007 TnDOT{2007{Act{477 477 TRAFFIC CONTROL each Bridge nonMaintenance TnDOT{2007 TnDOT{2007{Act{450 450 STRUCTURE CLEANING each Bridge Clean TnDOT{2007 TnDOT{2007{Act{454 454 MAJ STRUCTURE REPAIR each Bridge Repair Major TnDOT{2007 TnDOT{2007{Act{402 402 CRACK REPAIR each Bridge Repair Crack TnDOT{2007 TnDOT{2007{Act{451 451 MINOR STRUCTURE REPAIR each Bridge Repair Minor TnDOT{2007 TnDOT{2007{Act{412 412 JOINT REPAIR each Joint Repair TnDOT{2007 TnDOT{2007{Act{433 433 REPAIR DRAIN STRCT - EACH each Drain Repair TnDOT{2007 TnDOT{2007{Act{401 401 MANUAL SPOT PATCHING each Bridge Repair Patch TnDOT{2007 TnDOT{2007{Act{438 438 MANUAL BRUSH CONTROL each Bridge Clean Brush TnDOT{2007 TnDOT{2007{Act{447 447 MANUAL SWEEPING each Bridge Clean Sweep TnDOT{2007 TnDOT{2007{Act{405 405 MILLING each Bridge Repair TnDOT{2007 TnDOT{2007{Act{475 475 GUARDRAIL + BARRIER WALL each Rail/Walk Repair TnDOT{2007 TnDOT{2007{Act{461 461 DE-ICING (SALT) each Bridge nonMaintenance TnDOT{2007 TnDOT{2007{Act{463 463 ANTI-ICING (SALT BRINE) each Bridge nonMaintenance TnDOT{2007 TnDOT{2007{Act{446 446 MECHANICAL SWEEPING each Bridge Clean Sweep TnDOT{2007 TnDOT{2007{Act{442 442 EROSION CONTROL each Bridge Repair Erosion Figure 6. Example of a tab-delimited text file.

<Inspection_Cross_Reference> <DataSet> OrDOT{2006 </DataSet> <NBMD_Bridge_ID> OrDOT{2006{S8837A064 01072 </NBMD_Bridge_ID> <NBMD_Event_ID> OrDOT{2006{S8837A064 01072{nBrd{ </NBMD_Event_ID> <NBMD_Inspection_ID> OrDOT{2006{S8837A064 01072{Insp{0 </NBMD_Inspection_ID> <Inspection_Type> NBI </Inspection_Type> <Inspection_Order> Middle </Inspection_Order> <Inspection_Date> 0 </Inspection_Date> <brkey> S8837A064 01072 </brkey> <inspkey> -1 </inspkey> </Inspection_Cross_Reference> <Inspection_Cross_Reference> <DataSet> OrDOT{2006 </DataSet> <NBMD_Bridge_ID> OrDOT{2006{S8837A064 01072 </NBMD_Bridge_ID> <NBMD_Event_ID> OrDOT{2006{S8837A064 01072{nBrd{ </NBMD_Event_ID> <NBMD_Inspection_ID> OrDOT{2006{S8837A064 01072{Insp{0 </NBMD_Inspection_ID> <Inspection_Type> NBI </Inspection_Type> <Inspection_Order> Post </Inspection_Order> <Inspection_Date> 0 </Inspection_Date> <brkey> S8837A064 01072 </brkey> <inspkey> -1 </inspkey> </Inspection_Cross_Reference> Figure 7. XML document (sample). <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:element name="dataroot"> <xs:complexType> <xs:sequence> <xs:element ref="Inspection_Cross_Reference" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="Inspection_Cross_Reference"> <xs:annotation> <xs:documentation> NCHRP Project 14-15 NBMD Inspection Cross Reference Table 2009 G. Hearn TABLE Inspection_Cross_Reference_Table.xml </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="DataSet" type="xs:string"/> <xs:element name="NBMD_Bridge_ID" type="xs:string"/> <xs:element name="NBMD_Event_ID" type="xs:string"/> <xs:element name="NBMD_Inspection_ID" type="xs:string"/> <xs:element name="Inspection_Type" type="xs:string"/> <xs:element name="Inspection_Order" type="xs:string"/> <xs:element name="Inspection_Date" type="xs:string"/> <xs:element name="brkey" type="xs:string"/> <xs:element name="inspkey" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> Figure 8. XML schema for Inspection_Cross_Reference_Table.

Next: Chapter 3 - NBMD Software Applications »
Framework for a National Database System for Maintenance Actions on Highway Bridges Get This Book
×
MyNAP members save 10% online.
Login or Register to save!
Download Free PDF

TRB’s National Cooperative Highway Research Program (NCHRP) Report 668: Framework for a National Database System for Maintenance Actions on Highway Bridges explores a potential framework that provides a uniform format for collecting, reporting, and storing information on bridge maintenance actions for inclusion in a national bridge maintenance database.

Appendixes A through E to NCHRP Report 668 provide detailed information on the different aspects of the research. Links to the individual appendixes are below.

Appendix A: Information on Bridge Maintenance Programs

Appendix B: National Bridge Maintenance Database Tables

Appendix C: List of Element Level Costs of Maintenance Actions

Appendix D: Examples of National Bridge Maintenance Database Uses

Appendix E: Other National Bridge Maintenance Database Tables

  1. ×

    Welcome to OpenBook!

    You're looking at OpenBook, NAP.edu's online reading room since 1999. Based on feedback from you, our users, we've made some improvements that make it easier than ever to read thousands of publications on our website.

    Do you want to take a quick tour of the OpenBook's features?

    No Thanks Take a Tour »
  2. ×

    Show this book's table of contents, where you can jump to any chapter by name.

    « Back Next »
  3. ×

    ...or use these buttons to go back to the previous chapter or skip to the next one.

    « Back Next »
  4. ×

    Jump up to the previous page or down to the next one. Also, you can type in a page number and press Enter to go directly to that page in the book.

    « Back Next »
  5. ×

    To search the entire text of this book, type in your search term here and press Enter.

    « Back Next »
  6. ×

    Share a link to this book page on your preferred social network or via email.

    « Back Next »
  7. ×

    View our suggested citation for this chapter.

    « Back Next »
  8. ×

    Ready to take your reading offline? Click here to buy this book in print or download it as a free PDF, if available.

    « Back Next »
Stay Connected!