Coding Guide
Coding Guide
GENERAL
This Coding Guide is used to interpret and maintain data in the computerized Bridge Inventory, Inspection and Appraisal Files. The interpretation
of this coding guide will apply to both ON- and Off-system bridge data. The Bridge Inspection Database contains a record for each Bridge Class
Structure (See definition of structures, Item 112) and tunnel on public roadways in Texas. Bridge Inventory, Inspection and Appraisal data is also
used to update the National Bridge Inspection File (NBI) in Washington.
DATA QUALITY CANNOT BE OVEREMPHASIZED. The data in the Bridge Inventory, Inspection and Appraisal Files must be kept in as up-
to-date condition as possible. Requirements for Bridge Inventory, Inspection and Appraisal data are that an inspection that reflects changes to
existing structure data must be updated within 90 days of the evaluation or inspection that denotes the change in status. Newly built or
rehabilitation projects are to be reported within 90 days of job completion. Note: (SR) in the right margin means that item number is used in
the Sufficiency Calculation. See the CICS BRISUF calculation in the Appendix for more information.
CODING INSTRUCTIONS
When coding on a disk input or using a coding form, the following rules should apply:
(1) Use one character per space. Complete all data items for each bridge when adding new records. Before loading
transactions, perform a virus scan of any disks received from outside sources.
(2) Use alpha characters only in the fields where specified, and use capital letters.
(3) Complete coding for each item and column entirely; justify right or left. Read and follow coding instruction for the item
number being coded.
(4) To remove data from the file, use uppercase “X,” and it will replace the existing value with “Blank.” Code the complete
data field. Items 6.1, 7, and 9 are text fields and should never be entered as “Blank” or removed. The coding instructions
for each item will explain the values to be used and if a blank is proper in that item.
(5) Code data consistently. If data is coded for a structure in one direction, code only data that is for that direction. If you are
not clear on what is to be coded in a particular field, ask questions; call someone for help with questions. Bridge Division's
(BRG) Bridge Inspection Branch will be glad to answer any coding or engineering and structural questions that you may
have.
(6) Note: Card number and items 2,3, 8 and 5.1 are used as key identification. If these identifiers are coded incorrectly or
missing, they will cause fatal errors; i.e., no action will be taken to update the record or the wrong record will be updated.
(7) Card Number Explanation, 2 Digits: The correct card number must be used on any transaction entered. If the card number is
missing, the transaction will not be entered in the update. If the card number is wrong, the transaction will be entered in the
update and will change data items not intended to be changed.
(8) Uses of update codes in column 19, card 01: The update codes listed below will establish the type of transaction (add record,
delete record, change key identification or change data item) entered in the file or on a bridge record.
Add — Use “A” in column 19 on Card 01 to add a new record to the file. Use only on card 01, and complete coding for all data
items required for that record. Caution: If the record is already on file, this type of transaction will be rejected. ADD
COMPLETE RECORDS ONLY — DO NOT ADD PARTIALLY COMPLETED RECORDS.
Delete —Use “D” in column 19 of Card 01 to remove (delete) a record from the file. Code only items 2, 3, 8.4, 8.5, 8.6, 8.3 and
5.1 to accompany the “D” in Column 19.
Blank —A blank transaction code of blank in column 19 will cause the transaction entered to be handled as a change to existing
records on file. Enter only the card or cards and the Key Identification of the data item that are to be changed.
Change — Use “C” in column 19, Card 12 to change either the Inventory Route Record Identification (Items 8.4, 8.5, 8.6, 8.3 or
5.1) or the Intersecting Route Key Identification (Items 8.4A, 8.5A, 8.6A, 8.3A or 5.1A). This cannot be used to change
On-System records to Off-system or Off-system records to On-system records. If there are data items to be changed
There is an RPF in Roscoe to help build transactions. Type in ‘BRGRPF’ in the command area of any Roscoe region.
Answer ‘Y’ to delete AWS. Go through the screens and enter transactions and save in a Roscoe member at the end. This
RPF places an ‘*’ in position 20 of the transaction to indicate that it was built using the RPF.
Item 4 — City, Town, or Place Code (Census Place Code) Card 01 5 Digits
Cities, towns, townships, villages, and other census-designated places shall be identified using the Federal
Information Processing Standards (FIPS) codes given in the current version of the Census of Population and
Housing — Geographic Identification Code Scheme. If there is no FIPS place code, use City number; if rural,
then code all zeros. For on-system bridges the city number is furnished by program. See the Roadway Information
System (RIS) Manual for the city number list to code city number for off system.
Code Description
1 Route carried “On” the structure
2 Single route goes “Under” the structure
A Thru Z Multiple routes go “Under” the structure
5 Railroad Underpass
6 Pedestrian Underpass
7 Utility Structure Underpass
8 Tunnel
It cannot be overemphasized that all route-oriented data must agree with the coding as to whether the inventory
route is “On” or “Under” the structure.
“On” signifies that the inventory route is carried “On” the structure. All of the Bridge Inventory, Inspection and
Appraisal data items must be coded, unless specifically excepted, with respect to the structure and the inventory
route “On” it.
“Under” signifies that the inventory route goes “Under” the structure. If an inventory route beneath the structure is
on a federal-aid system, is a defense route or is otherwise important, a record must be coded to identify it. The type
of code must be 2 or an alphabetic letter A through Z. Code 2 for a single route “Under,” and code A, B, C, D, etc.,
consecutively for multiple routes “Under” the same structure. Defense routes shall be listed first. If more than one
route is under the structure, Code 2 shall not be used. Instead, use A for the first route, B for the second, and so on
for the consecutive routes.
Tunnels shall be coded only as an “Under” record; that is, they shall not be coded as a structure carrying highway
traffic.
There are situations of a route “Under” a structure, where the structure does not carry a highway, but may carry a
railroad, pedestrian traffic, or even a building. These are coded the same as any other “Under” record and no “On”
record shall be coded.
When a structure is “On” and “Under”, determine the inventory route first. The inventory route is determined by
hierarchy of highway class; i.e., for an Interstate over or under a U.S. Highway, the Interstate will be coded as the
inventory route, and the U.S. Highway will be coded the intersecting route. If two highways are of the same
hierarchy class, the lowest highway number will be the coded inventory route, and the higher numbered route will
be the intersecting route. The record identification to be coded in Item 8 — Structure Number, (8.3 thru 8.6) is now
established along with the other (intersecting route) route Item 8A (8.3A thru 8.6A) record identification.
Example 1: IH 10 over IH 20 – Item 5.1 IH 10 structure function will be coded 1, and the control-section, bridge
number of IH 10 will be coded in Items 8.3 thru 8.6 Structure Number. Item 5.1A, intersecting route structure
function, will be coded 2, and the control-section, bridge number for IH 20 will be coded in Items 8.3A thru 8.6A,
the intersecting route key identification.
Example 2: US Highway under FM Highway – The US Highway Item 5.1 structure function will be coded 2, and
the control-section, bridge number of the US Highway will be coded in Items 8.3 thru 8.6, Structure Number. Item
5.1A, intersecting route structure function will be coded 1, and the control-section, bridge number of the FM will be
entered in Items 8.3A thru 8.6A, intersecting route key identification.
Code Description
11 Interstate Highway
12 US Highway (Spur)
13 State Highway
14 State Loop or Spur
15 Farm or Ranch to Market Road
16 Park Road
17 Recreation Road/Spur
18 Metropolitan Highway (Federal-Aid Urban System Routes that have
been designated part of the State Highway System)
19 Other On-System Route
20 Toll Road
Code Description
21 County Road/Highway
23 Old San Antonio Road
24 NASA 1
25 Business Interstate
26 Business U. S. Highway
27 Business S.H. Highway
28 Business F.M. Highway
29 Principal Arterial Street
31 City Street
41 Federal Lands Road
51 State Lands Road
99 Other
Code Description
0 None of the Below
1 Mainlane (service roads and ramps are NOT to be coded 1)
2 Alternate
3 Bypass
4 Spur
5 Toll Road
6 Business
7 Ramp, Connector, etc.
8 Service and/or Unclassified Frontage Road
9 Truck Route
Item 5.3A — Intersecting Route Designated Level of Service Card 01 1 Digit (SR)
Identify the designated level of service for the intersecting route using one of the following codes:
Code Description
0 None of the Below
1 Mainlane (service roads and ramps are NOT to be coded 1)
2 Alternate
3 Bypass
4 Spur
5 Toll Road
6 Business
7 Ramp, Connector, etc.
8 Service and/or Unclassified Frontage Road
9 Truck Route
Code Description
0040 Interstate 40
0102 State Highway 102
2222 Farm Market Road 2222
0010 Tunnel on Interstate 10
0155 County Road
Code Description
0 Not Applicable
1 North
2 East
3 South
4 West
EXAMPLES:
Record Code
Interstate 35, On 1 111 0035 00 1111003500
Interstate 35E, Under 2 111 0035 20 2111003520
State Highway 104, Spur, Under 2 134 0104 00 2134010400
City Street, On 1 310 0000 00 1310000000
Ramp From IH 35, Under 2 117 0035 00 2117003500
County Highway 173, On 1 211 0173 00 1211017300
Interstate 20, Under 2 111 0020 00 2111002000
Interstate 635, On 1 111 0635 00 1111063500
State Highway 120 (Defense Route), Under A 131 0120 00 A131012000
US 90A, Under B 122 0090 00 B122009000
Business Rt. IH 35, On 1 256 0035 0A 125600350A
When Item 5.1 is coded the route "Under," this item will describe the route or feature under.
The information to be recorded for this item in the first 24 digits shall be the name or names of the features
intersected by the structure. When one of the features intersected is another highway, the signed number or name of
the highway shall appear first (left most) in the field. The names of any other features shall follow, separated by a
semicolon or a comma. Parentheses shall be used to provide a second identification of the same feature (see third
example). Abbreviations may be used where necessary, but an effort shall be made to keep them meaningful. The
data in this segment shall be left justified in the first 24 positions without trailing zeros.
A structure on a designated defense highway considered to be a critical facility (Item 6.2), shall no longer be codedd
by an asterisk in the 25th position. A blank space shall be coded in the 25th position in all cases..
I 35, US 81, Mill Road
CR 72, Colorado R
CR 42 (Pond Road)
Item 10 — Inventory Route, Minimum Vertical Clearance (XX feet XX inches) Card 02 4 Digits
Code the minimum vertical clearance over the inventory route identified in Item 5, whether the route is “On” the
structure or “Under” the structure. The minimum clearance for a 10-foot width of the pavement (or traveled part of
the roadway) where the clearance is the greatest shall be recorded and coded in feet and inches. For structures
having multiple openings, clearances for each opening shall be recorded, but only the greatest of the minimum
clearances for the two or more openings shall be coded regardless of the direction of travel. This would be the
practical maximum clearance. When no restriction exists, code 9999. For bridges that have been restricted on the
roadway approaches, code the vertical restriction over the bridge deck, not the approach restriction. Use District
Use Field (Item 126) to record the approach restriction. Item 10 shall not be coded less than 0900.
Milepoint date will be the date of milepoint in the Road Inventory RI 2 File. This date must be furnished when
adding on-system bridges. The milepoint date can be obtained from the RI 2 listing or TPP will furnish the date.
(Reference: Roadway Information System [RIS] Manual, RI 2 T Log).
When an intersecting route is present, a milepoint date must be furnished for that route. See Item 11.1.
Enter Intersecting Route Reference Marker and Displacement. See instructions in Item 11.1B.
This item is to be coded for all records in the inventory route. The Base Highway Network includes the through lane
(mainline) portions of the NHS, rural/urban principal arterial system and rural minor arterial system. Ramps,
frontage roads and other roadways are not included in the Base Network. For the inventory route identified in Item 5
- Inventory Route, indicate whether the inventory route is on the Base Highway Network or not on that network. Use
one of the following codes:
Code Description
0 Inventory Route is not on the Base Network
This item is to be coded for all records in the intersecting route. The Base Highway Network includes the through
lane (mainline) portions of the NHS, rural/urban principal arterial system and rural minor arterial system. Ramps,
frontage roads and other roadways are not included in the Base Network. For the intersecting route identified in Item
5 - Intersecting Route, indicate whether the intersecting route is on the Base Highway Network or not on that
network. Use one of the following codes:
Code Description
0 Inventory Route is not on the Base Network
If Item 12 - Base Highway Network has been coded 1, the information to be recorded for this item is inventory route
for the State's linear referencing system (LRS). If Item 12 has been coded 0, this entire item should be left blank.
This item is a 12-digit code composed of 2 segments.
The LRS inventory route and subroute numbers to be reported in this item must correspond to the LRS inventory
route and subroute numbers reported by the State for the HPMS. The LRS inventory route number is coded in the
ten positions of segment 13A, right justified and zero filled. The subroute number, if it exists, is coded in the two
positions of segment 13B, right justified and zero filled.
The LRS inventory route number can be alphanumeric, but must not contain blanks. The LRS inventory route
number is not necessarily the same as that posted along the roadway, but is a number used to uniquely identify a
route within at least a county and perhaps throughout the State.
The subroute number is a number that uniquely identifies portions of inventory route sections where duplicate
milepoints occur. These subroute numbers, if they exist. are identified in the State's HPMS-LRS records. If there is
no subroute number, code 00 in this segment.
EXAMPLES: Code
Inventory Route 2775, Subroute Number 0 000000277500
Inventory Route 2775, Subroute Number 3 000000277503
EXAMPLE:
Code
Latitude is 35° 27’ 33.16´ 35273316
EXAMPLE:
Code
Latitude is 35.273 35.27300000
EXAMPLE:
Code
Longitude is 81° 5´ 15.23” 081051523
EXAMPLE:
Code
Longitude is 81.58 08158000000
Item 17.2 — GPS Method Used to Collect Lat. And Long. Card 13 1 Digit
Use one of the codes below to indicate which method was used to determine the Latitude and Longitude in items
16.1 and 17.1 for this structure. Codes 2, 3 and 4 shall only be coded by the Bridge Division. If there is data that
meets the criteria for codes 2 ,3 and 4 please contact the Bridge Division for updating.
Code Description
0 Unknown or other
1 GPS (Not Differentially Corrected)
2 CRI Project (County Road Inventory)
3 GPS (Differentially Corrected)
4 Generated from reference marker data
EXAMPLES:
Description Code
Diamond interchange, structure by-passable 00
Cloverleaf, not by-passable; 8-mile detour 08
Structure over river; 121-mile detour 99
Structure over highway, no interchange, 00
By-passable at ground level
Structure on dead-end road 99
FUNCTIONAL
URBAN CODE SYSTEM RURAL
FUNCTIONAL
URBAN CODE SYSTEM RURAL
Include all lanes carrying highway traffic (i.e., cars, trucks, buses) which are striped or otherwise operated as a full
width traffic lane for the entire length of the structure or under the structure by the owning/maintaining authority.
This shall include any full width merge lanes and ramp lanes, and shall be independent of directionality of usage
(i.e., a 1-lane bridge carrying 2-way directional traffic is still considered to carry only one lane on the structure. Any
bridge with a roadway width of less than 18 feet must be considered one-lane.)
When the inventory route is “Under” the structure, the obstruction over the inventory route may be other than a
highway bridge (railroad, pedestrian, pipeline, etc.). Code 00 for these cases if there are not highway lanes on the
obstructing structure.
EXAMPLES:
Description Code
1 lane on, 0 lanes under 0100
3 lanes on, 1 lane under 0301
Railroad and pedestrian 0004
on, 4 lanes under
Un-stabilized grass or dirt, with no base course, flush with and beside the traffic lane is not to be considered a
shoulder for this item.
For structures with medians of any type, this item should be coded as the sum of the usable roadway widths for the
approach roadways (i.e., all median widths which do not qualify as shoulders should not be included in this
dimension).
When there is a variation between the approaches at either end of the structure, record and code the most restrictive
of the approach conditions.
EXAMPLES:
The last example above represents the code method for a structure in which the most restrictive approach has the
cross-section shown below:
Regardless of whether there are parallel structures or single structures, the data coded must be compatible with the
other related route and bridge data (i.e., if Item 51 — Bridge Roadway Width, Curb-to-Curb is for traffic in one
direction only, then Items 28, 29, 32, etc. must be for traffic in one direction only).
If a ramp is adjacent to the through lanes approaching the structure, it shall be included in the approach roadway
width. The total approach roadway width for the example above is 94 feet (a code of 094).
Code Description
0 No median
1 Open Median
2 Closed Median (No Barrier)
3 Closed Median with Non-Mountable Barriers
The skew angle is the angle between the centerline of a pier and a line normal to the roadway centerline. When
plans are available, the skew angle can be taken directly from the plans. If no plans are available, the angle is to be
field measured if possible. Record the skew angle to the nearest degree. If the skew angle is 0°, it should be so
coded. When the structure is on a curve or if the skew varies for some other reason, the average skew should be
recorded, if reasonable. Otherwise, record 99 to indicate a major variation in skews of substructure units. A 2-digit
number must be coded.
EXAMPLES:
Skew Angle Code
0° 00
10° 10
8° 08
29° 29
1st digit Bridge railings: Some factors that affect the proper functioning of bridge railing are height, material,
strength, and geometric features. Railings must be capable of smoothly redirecting an impacting
vehicle. Bridge railings should be evaluated using the AASHTO Standard Specifications for
Highway Bridges as a guide for establishing a currently acceptable standard.
2nd digit Transitions: The transition from approach guardrail to bridge railing requires that the approach
guardrail be firmly attached to the bridge railing. It also requires that the approach guardrail be
gradually stiffened as it comes closer to the bridge railing. The ends of curbs and safety walks need
to be gradually tapered out or shielded.
3rd digit Approach guardrail: The structural adequacy and compatibility of approach guardrail with transition
designs should be determined. Rarely does the need for a barrier stop at the end of a bridge. Thus,
an approach guardrail with adequate length and structural qualities to shield motorists from the
hazards at the bridge site needs to be installed. In addition to being capable of safely redirecting an
impacting vehicle, the approach guardrail must also facilitate a transition to the bridge railing that
will not cause snagging or pocketing of an impacting vehicle. Acceptable guardrail design
suggestions are contained in the AASHTO Guide for Selecting, Locating, and Designing Traffic
Barriers.
4th digit Approach guardrail ends: As with guardrail ends in general, the ends of approach guardrails to
bridges should be flared, buried, made breakaway, or shielded. Design treatment of guardrail ends is
given in the AASHTO Guide for Selecting, Locating, and Designing Traffic Barriers.
The reporting of these features shall be as follows:
Code Description
Code Description
1 Bridge is on the National Register of Historic Places. (Listing provided by the
Historic Preservation Office).
2 Bridge is eligible for the National Register of Historic Places. (Not used unless
specifically instructed).
3 Bridge is at least 40 years old and meets one or more of the following
qualifications:
Is a pin-connected or otherwise unique truss, a suspension bridge, an arch
bridge, or is made of cast iron.
Demonstrates unique architectural or engineering design, or artistic
embellishment such as cast iron or steel finials and fretwork, or elaborate
concrete form work.
Is a “one of a kind” design.
4 Historical significance is not determinable at this time, but is at least 40 years
old.
5 Bridge is not eligible for the National Register of Historic Places, or is not 40
years old.
Code Description
N Not applicable, no waterway
0 No navigation control on waterway (bridge permit
not required)
1 Navigation control on waterway (bridge permit
required)
EXAMPLES:
EXAMPLES:
Code Description
A Open, no restriction
B Closing or posting recommended, but not legally implemented (all signs not in
place). See Note
D Open, would be posted or closed except for temporary shoring, etc., to allow
for unrestricted traffic
E Open, temporary structure in place to carry legal loads while original structure
is closed and awaiting replacement or rehabilitation.
G New structure not yet open to traffic
K Bridge closed to all traffic
P Posted for load (may include other restrictions)
R Posted for other load-capacity restriction (speed, number of vehicles on bridge,
etc.)
U Under construction or rehabilitation not covered by routine inspection
Note: When the load rating calculation requires a change to a lower posting, use B in this item until the signs are
replaced. Code the new lower loading requirements in Items 41.1 and 41.2 as well.
EXAMPLE:
EXAMPLES:
Code Description
1126 Simple Span Concrete Flat Slab
1363 Warren Pony Truss, Parallel Chord
2112 Continuous Steel Deck Plate Girder, Multiple
6129 Concrete Rigid Frame
5129 Closed Spandrel Concrete Arch
1271 Parker Through Truss
5153 Masonry Arch
1125 Simple Span Concrete Pan Girder
7254 Movable Vertical Lift
8214 Cable Stayed Girder w/Floor System
1261 Pratt Through Truss
Item 47 — Inventory Route, Total Horizontal Clearance (XXX.X feet) Card 05 4 Digits
The total horizontal clearance for the inventory route identified in Item 5 should be measured and recorded. The
clearance should be the available clearance measured between the restrictive features – curbs, rails, walls, or other
structural features limiting the roadway (surface and shoulders). The measurement should be recorded and coded to
the nearest tenth of a foot (with an assumed decimal point).
The purpose of this item is to give the largest available clearance for the movement of wide loads. This clearance
has been identified in 3 ways; use the most applicable:
1. Roadway surface and shoulders.
2. Distance from face of pier (or rail around pier).
3. Include flush or mountable medians, but not raised medians. For a raised or non-mountable median, code the
greater of the restricted widths in either direction, not both directions.
The minimum code is 008.0; the maximum is 999.9.
EXAMPLES:
EXAMPLES:
EXAMPLES:
Left Side Right Side Code
Sidewalk None 8.3' 000083
10.0 4.1' 100041
8.3' None 083000
12.1' 11.5' 121115
None None 000000
0.6' 1.5' 00001
EXAMPLES:
The last example above would be the coded value for the deck section shown below
Functional Class
3 Vertical clearance less than value in rating code of 4 and requiring corrective action.
2 Vertical clearance less than value in rating code of 4 and requiring replacement.
0 Bridge closed.
Using one of the codes below, code in the first position the reference feature from which the clearance measurement
is taken:
Code Description
H Highway beneath structure
R Railroad beneath structure
N Feature not a highway or railroad
In the next 4 positions, code a 4-digit number to represent the minimum vertical clearance from that feature to the
structure. If the feature is not a highway or railroad, code the minimum vertical clearance 0000.
EXAMPLES:
Code
River beneath structure N0000
Description Code
Railroad 31 ft 3 in. beneath structure R3103
Code Description
H Highway beneath structure
R Railroad beneath structure
N Feature not a highway or railroad
In the 55.2 positions, code a 3-digit number to represent the minimum lateral underclearance on the right. The
lateral clearance should be measured from the right edge of the roadway (excluding shoulders) or from the centerline
(between rails) of the right-hand track of a railroad to the nearest substructure unit (pier, abutment, etc.), to a rigid
barrier, or to the toe of slope steeper than 3 to 1. The clearance measurements to be recorded will be the minimum
after measuring the clearance in both directions of travel. In the case of a dual highway this would mean the outside
clearances of both roadways should be measured and the smaller distance recorded and coded.
If two related features are below the bridge, measure both and record the lesser of the two. An explanation should
be written as to what was recorded. If the feature beneath the structure is not a railroad or highway, code 999 to
indicate not applicable.
The presence of ramps is not considered in this item; therefore, the minimum lateral clearance on the right should be
measured from the right edge of the through roadway.
EXAMPLES:
Item 56 — Minimum Lateral Underclearance on Left (XX.X feet) Card 05 3 Digits (SR)
(for divided highway, 1-way streets, and ramps;
not applicable to railroads)
Using a 3-digit number, record and code the minimum lateral underclearance on the left (median side for divided
highways) to the nearest tenth of a foot (with an assumed decimal point). The lateral clearance should be measured
from the left edge of the roadway (excluding shoulders) to the nearest substructure unit, to a rigid barrier, or to the
toe of slop steeper than 3 to 1. Refer to examples under Item 55 — Minimum Lateral Underclearance on Right.
In the case of a dual highway, the median side clearances of both roadways should be measured and the smaller
distance recorded and coded. If there is no obstruction in the median area, a notation of “open” should be recorded
and 999 should be coded. For clearances greater than 99.8 feet, code 998. Code 000 to indicate not applicable.
Code Description
N NOT APPLICABLE
9 EXCELLENT CONDITION
8 VERY GOOD CONDITION — no problems noted.
7 GOOD CONDITION — some minor problems.
6 SATISFACTORY CONDITION — structural elements show some minor deterioration.
5 FAIR CONDITION — all primary structural elements are sound but may have minor
section loss, cracking, spalling or scour.
4 POOR CONDITION — advanced section loss, deterioration, spalling or scour.
3 SERIOUS CONDITION — loss of section, deterioration, spalling or scour have seriously
affected primary structural components. Local failures are possible. Fatigue cracks in steel
or shear cracks in concrete may be present.
2 CRITICAL CONDITION — advanced deterioration of primary structural elements. Fatigue
cracks in steel or shear cracks in concrete may be present or scour may have removed
substructure support. Unless closely monitored it may be necessary to close the bridge until
corrective action is taken.
1 “IMMINENT” FAILURE CONDITION — major deterioration or section loss present in
critical structural components or obvious vertical or horizontal movement affecting structure
stability. Bridge is closed to traffic but corrective action may put back in light service.
0 FAILED CONDITION — out-of-service beyond corrective action.
Code Description
N Not applicable. Use if structure is not a culvert.
9 No deficiencies.
8 No noticeable or noteworthy deficiencies which affect the condition of the culvert.
Insignificant scrape marks caused by drift.
7 Shrinkage cracks, light scaling, and insignificant spalling which does not expose reinforcing
steel. Insignificant damage caused by drift with no misalignment and not requiring
corrective action. Some minor scouring has occurred near curtain walls, wingwalls, or
pipes. Metal culverts have a smooth symmetrical curvature with superficial corrosion and
no pitting.
6 Deterioration or initial disintegration, minor chloride contamination, cracking with some
leaching, or spalls on concrete or masonry walls and slabs. Local minor scouring at curtain
walls, wingwalls, or pipes. Metal culverts have a smooth curvature, asymmetrical shape,
significant corrosion or moderate pitting.
5 Moderate to major deterioration or disintegration, extensive cracking and leaching, or spalls
on concrete or masonry walls and slabs. Minor settlement or misalignment. Noticeable
scouring or erosion at curtain walls, wingwalls, or pipes. Metal culverts have significant
distortion and deflection in one section, significant corrosion or deep pitting.
4 Large spalls, heavy scaling, wide cracks, considerable efflorescence, or opened construction
joints permitting loss of backfill. Considerable settlement or misalignment. Considerable
scouring or erosion at curtain walls, wingwalls or pipes. Metal culverts have significant
distortion and deflection throughout, extensive corrosion or deep pitting.
3 Any condition described in Code 4, but which is excessive in scope. Severe movement or
differential settlement of the segments, or loss of fill. Holes may exist in walls or slabs.
Integral wingwalls nearly severed from culvert. Severe scour or erosion at curtain walls,
wingwalls or pipes. Metal culverts have extreme distortion and deflection in one section,
extensive corrosion, or deep pitting with scattered perforations.
2 Integral wingwalls collapsed, severe settlement of roadway due to loss of fill. Section of
culvert may have failed and can no longer support embankment. Complete undermining at
curtain walls and pipes. Corrective action required to maintain traffic. Metal culverts have
extreme distortion and deflection throughout with extensive perforations due to corrosion.
1 Bridge closed. Corrective action may put back in light service.
0 Bridge closed. Replacement necessary.
Code Description
1 Load Factor (LF)
2 Allowable Stress (AS)
3 Load and Resistance Factor (LRFR)
4 Load Testing
5 No rating analysis performed
This item contains the Operating Rating referred to in Article 4.1 of the AASHTO Manual and discussed elsewhere
in the Bridge Inspection Manual. This Item uses the same codes given in Item 66. The first digit of this item
should be the same as the first digit used for Item 66.
Code Description
1 H Configuration
2 HS Loading
7 Railroad Loading
8 Pedestrian or Special Loading
9 Gross Load Only
The AASHTO Manual for Maintenance Inspection of Bridges permits the calculation of the inventory and
operating ratings by the load factor method.
If the bridge is closed and/or will not carry any live load, the second and third digits shall be coded 00.
The use or presence of a temporary bridge requires special consideration in coding. In such cases, since there is no
permanent bridge, Items 64 and 66 should be coded 900 even though the temporary structure is rated for as much as
full legal load.
A bridge shored up or repaired on a temporary basis is considered a temporary bridge and the inventory and
operating rating should be coded as if the temporary shoring were not in place. See Item 103 — Temporary
Structure Designation for definition of a temporary bridge.
EXAMPLES:
Description Code
HS30 254
Temporary bridge 900
Shored-up bridge 203*
Structure under sufficient fill that live load is insignificant
(according to AASHTO design) 299
*Load capacity without shoring.
For load posting of off-system bridges (county road — city streets), see House Bill 1574, Section 9, Chapter 1, Title
116, Article 66674o-2 for additional guidance.
Article 6674o-2. County and Municipal Bridge Inspection.
(a) If the Texas Department of Transportation determines after an inspection that a bridge under the jurisdiction of a
county or municipality qualifies for a lower load rating under 23 C.F.R. Sections 650.301–650.311 than is currently
permitted, the department shall notify the commissioners court of the county or the governing body of the
municipality.
(b) A commissioner’s court or governing body that receives notice under Subsection (a) of this article shall post
notice on a road or highway approaching the bridge indicating that traffic is restricted consistent with the newer
lower rating. The notice must be placed in a location that enables restricted traffic to avoid crossing the bridge.
Code Description
1 Load Factor (LF)
2 Allowable Stress (AS)
3 Load and Resistance Factor (LRFR)
4 Load Testing
5 No rating analysis performed
This item should be coded 299 for a structure under sufficient fill, such that according to AASHTO design, the live
load is insignificant in the structure load capacity.
Code Description
N Not applicable
9 Superior to present desirable criteria
8 Equal to present desirable criteria
7 Better than present minimum criteria
6 Equal to present minimum criteria
5 Somewhat better than minimum adequacy to tolerate being left in place as is.
4 Meets minimum tolerable limits to be left in place as is
3 Basically intolerable requiring high priority of corrective action
2 Basically intolerable requiring high priority of replacement
0 Bridge closed
Tables are provided to evaluate Item 67, 68, 69 and 71, and shall be used by all evaluators to code these items. They
have been developed to closely match the descriptions for the appraisal evaluation codes of 0 to 9. The tables shall
be used in all instances to evaluate the item based on the designated data in the inventory, even if a table does not
appear to match the descriptive codes. For unusual cases where the site data does not exactly agree with the table
criteria, use the most appropriate table to evaluate the item. Note: To obtain a correct Sufficiency Rating, the
following items (along with the usual items) must be coded accurately and in agreement with the tables:
If these items are not in agreement with the tables for Items 67, 68, and 69, the FHWA Sufficiency Rating
Calculation will furnish a number based on the coding of the record to complete the calculation. That number will be
part of the Record Lister (Program 120179) displayed in parentheses to the left of the coded value. If a discrepancy
occurs between an expected SR and an FHWA SR, check the listed items for errors.
Completed bridges not yet opened to traffic, if rated, shall be appraised as if open to traffic. Design values, for
example, ADT, shall be used for the evaluation. The data provided will include a code of G for Item 41 — Structure
Open, Posted, or Closed to Traffic.
Structural
Evaluation Average Daily Traffic (ADT)
Rating Code
>5000
0-500 501-5000
or I-26 FC = 1, 11 or 12
>236* >236 >236
9
(HS20)** (HS20) (HS20)
236 236 236
8
(HS20) (HS20) (HS20)
231 231 231
7
(HS17) (HS17) (HS17)
223 225 227
6
(HS13) (HS14) (HS15)
218 220 222
5
(HS10) (HS11) (HS12)
212 214 218
4
(HS7) (HS8) (HS10)
Inventory rating less than value in rating code of 4 and
3 requiring corrective action. (I-75A Type of Work
Proposed = 33 thru 38)
Inventory rating less than value in rating code of 4 and
2 requiring replacement. (I-75A Type of Work Proposed =
31 or 32)
TABLE 2A TABLE 2B
Deck
Geometry Item 51 in feet converted from NBI measures in meters Bridge Roadway Width
1 lane, two way traffic
Rating Bridge Roadway Width 2 Lanes, two way traffic
Table 2C
Table 2D
Item 51 in feet converted from NBI measures in meters
Bridge Roadway Width Bridge Roadway Width
2 or More Lanes 1-Way Traffic 1-Way Traffic
Deck Ramps Only
Interstate and Other Divided Other Multi-lane Divided
Geometry Item 5.3 = 7
Freeways & S.Roads Facilities
Rating Code
3 or More 3 or More 2 or More
2 Lanes 2 Lanes 1 Lane
Lanes Lanes Lanes
34.1 11.2N+12.1
4 29.8 11.2N+5.9 18 12.1N+3.9
(28.9)* (11.2N+6.9)*
33.1 11.2N+11.2
3 26.9 11.2N+4.9 16.1 12.1N+2
(27.9)* (11.2N+5.9)*
2 Any width less than required for a rating code of 3 and structure is open.
Functional Class
Deck Geometry
Interstate and Other Freeways
Rating Code
Major and
Other Principal
Minor
All Routes: and Minor
Undesignated Collectors and
Except as Arterials
Route, Urban Locals
Noted for
Areas*
Urban Areas
* Use for routes in highly developed urban areas only when there is an alternative Interstate, freeway, or
expressway facility with a minimum of 16'-0" clearance.
Notes:
1. Use the lower rating code for values between those listed in the table.
Functional Class
Under
Clearance Interstate and Other Freeways
Rating Code
Major and
Other Principal
Minor
All Routes: and Minor Railroad
Undesignated Collectors and
Except as Arterials
Route, Urban Locals
Noted for
Areas*
Urban Areas
Underclearance less than value in rating code of 4 and requiring corrective actions. (I-75A Type
3
of Work Proposed = 33 thru 38)
Underclearance less than value in rating code of 3 and requiring replacement. (I-75A Type of
2
Work Proposed = 31 or 32)
* Used for routes in highly developed urban areas only when there is an alternative interstate, freeway or
expressway facility with a minimum of 16'-0" clearance.
Notes:
1. Use the lower rating code for values between those listed in the tables.
2. The functional classification of the underpassing route shall be used in the evaluation. If an "under" record is
not coded, the underpassing route shall be considered a major or minor collector or a local road.
Functional Class
7 18 21 3 9 21 11.2 17.1
Underclearance less than value in rating code of 4 and requiring corrective actions. (I-75A Type of
3
Work Proposed = 33 thru 38)
Underclearance less than value in rating code of 3 and requiring replacement. (I-75A Type of
2
Work Proposed = 31 or 32)
Notes:
1. Use the lower rating code for values between those listed in the tables.
2. Dimensions are in feet and inches.
3. When acceleration or deceleration lanes or ramps are provided under 2-way traffic, use the value from the right
ramp column to determine code.
4. The functional classification of the underpassing route shall be used in the evaluation. If an "under" record is
not coded, the underpassing route shall be considered a major or minor collector or a local road.
Code Description
0, 1, 2, 3 or 4 Posting required
5 No posting required
The degree that the operating rating stress level is under the maximum legal load stress level may be used to
differentiate between codes. As a guide and for coding purposes only, the following values may be used to code this
item:
Functional Classification
Code
0 0 0 Bridge closed.
Speed Reduction
(MPH) Code
>0 ≤ 8
>0 ≤ 5 7
>5 ≤ 10 6
> 10 ≤ 15 5
> 15 ≤ 20 4
> 20 3 or less
For example, if the highway section requires a substantial speed reduction due to vertical or horizontal alignment,
and the roadway approach to the bridge requires only a very minor additional speed reduction at the bridge, the
appropriate code would be a 6. This concept shall be used at each bridge site.
Speed reductions that are necessary because of structure width, and not alignment, shall not be considered in
evaluating this item.
This item, along with Items 76, 94, 95, 96, and 97, must be coded for a bridge eligible for the Highway Bridge
Replacement and Rehabilitation Program. It may be coded for other bridges at the option of the TxDOT.
If the structure has a sufficiency rating of less than 80 and is structurally deficient or functionally obsolete, a
calculated cost for these items (see above) will be entered by program until the actual cost is determined. Enter
Items 75, 76, 94, 95, 96, and 97 when the actual cost of replacement or rehabilitation is developed by the district.
Use one of the following codes to represent the proposed work type:
Code Description
Blank No proposed improvements.
31 Replacement of bridge or other structure because of substandard load carrying
capacity or substandard bridge roadway geometry.
32 Replacement of bridge or other structure because of relocation of road.
33 Widening of existing bridge or other major structure without deck rehabilitation
or replacement; includes culvert lengthening.
34 Widening of existing bridge with deck rehabilitation or replacement.
35 Bridge rehabilitation because of general structure deterioration or inadequate
strength.
36 Bridge deck rehabilitation with only incidental widening.
37 Bridge deck replacement with only incidental widening.
38 Other structural work.
The third digit shall be coded using one of the following codes to indicate whether the proposed work is to be done
by contract or by force account:
Code Description
Blank No proposed improvements.
1 Work to be done by contract.
2 Work to be done by owner’s forces
.
A deck is to be rehabilitated and the bridge widened to provide a full 12-foot shoulder. 341
The existing shoulder is only 4 feet wide, and an extra line of girders with an extra
line of girders with appropriate substructure widening must be added.
The work will be done by contract.
A bridge superstructure and substructure are to be rehabilitated by state forces to increase 352
The bridge’s load capacity.
A bridge deck is to be rehabilitated by contract and a safety curb to be removed which 361
results in incidental widening of 2 feet.
A bridge deck is to be replaced by contract and the deck cantilever overhang extended 2 371
feet, which is the maximum that can be done without adding another line of stringers
or girders to the superstructure
A bridge that is no longer needed is to be demolished and an at-grade crossing built by 382
state forces. (This code could also be used to designate incidental safety work on a
bridge such as bridge-rail upgrading or replacement.)
EXAMPLES:
Length of Structure
Improvement Code
250 feet 000250
1,200 feet 001200
12,345 feet 012345
No improvement 000000
For substructure or channel work only, code the length of superstructure over, or supported by, the substructure or
channel.
Typically, a replacement bridge is longer than the existing bridge. Nationwide averages for the increase in bridge
length with replacement as a function of the existing length are given in the following figure. The length-expansion
factors represent data for the years 1981 to 1985. Where site-specific data is lacking, these factors are suggested for
estimating the length of replacement bridges. For exceedingly long bridges (i.e., 1000 feet or more) the length-
expansion factor approaches 1.0.
For each of 92.1, 92.2, and 92.3, code the first digit Y for special inspection or emphasis needed and code N for not
needed. The first digit of 92.1, 92.2, and 92.3 must be coded for all structures to designate either a yes or no answer.
In the second and third digits of each segment, code a 2-digit number to indicate the number of months between
inspections only if the first digit is coded Y.
92.1 Fracture Critical Inspection can not exceed 60 months.
92.2 Underwater inspections can not exceed 60 months.
92.3 Special inspections can not exceed 60 months.
If the first digit is coded N, the second and third digits are left blank.
EXAMPLES:
Segment Code
A 2-girder system structure which is being inspected yearly and 92.1 Y12
no other special inspections are required. 92.2 N__
92.3 N__
A structure has been temporarily shored and is being inspected 92.1 N__
on a 06-month interval. Other special inspections are not 92.2 N__
required. 92.3 YO6
For each segment of this item, when applicable, code a 6-digit number to represent the month and year. The number
of the month should be coded in the first 2 digits with leading zeros as required and the last 4 digits of the year
coded as the through sixth digits of the field. If the first digit of any part of Item 92 is coded N, then the
corresponding part of this item shall be blank.
EXAMPLES:
Item Code
A structure has fracture critical members which were last 93.1 031986
inspected in March 1986. It does not require underwater or 93.2 Blank
other special feature inspections. 93.3 Blank
Bridge Improvement
Cost Code
$55,850 000056
$250,000 000250
$7,451,233 007451
No improvement Blank
Nationally, the deck area of replaced bridges is averaging 2.2 times the deck area before replacement. The deck area
of rehabilitated bridges is averaging 1.5 times the deck area before rehabilitation. Widening square foot costs are
typically 1.8 times the square foot cost of new bridges with similar spans. For example, if the average cost of a new
bridge is $50 per square foot, the average cost of the widened area would be $90 per square foot.
Each district is encouraged to use its best available information and established procedures to determine bridge
improvement costs. In the absence of these procedures, the district may wish to use the following procedure as a
guide in preparing bridge improvement cost estimates.
Apply a construction unit cost to the proposed bridge area developed by using (1) current state deck geometry
design standards and (2) proposed bridge length from Item 76 — Length of Structure Improvement.
Code Description
056 Arkansas
226 Louisiana
356 New Mexico
406 Oklahoma
For the special case of a structure on the border with Mexico, code the State code value = MEX. If structure is not
on a border, leave blank.
EXAMPLES:
Description Code
A structure connects your district with 22645
Louisiana and Louisiana is responsible for
funding 45 percent of future
improvement costs.
Code Description
0 The inventory route is not a STRAHNET route.
1 The inventory route is on a Interstate STRAHNET route.
2 The inventory route is on a Non-Interstate STRAHNET route.
3 The inventory route is on a STRAHNET connector route.
Enter the defense highway designation for the intersecting route identified in 5.1A. Indicate defense
highway condition using one of the following codes: Link to STRAHNET maps
Code Description
0 The intersecting route is not a STRAHNET route.
1 The intersecting route is on a Interstate STRAHNET route.
2 The intersecting route is on a Non-Interstate STRAHNET route
3 The intersecting route is on a STRAHNET connector route.
.
Code Description
R The right structure of parallel bridges carrying the roadway in the direction
of the inventory. (For a defense highway, this is west to east and south to
north.)
L The left structure of parallel bridges. This structure carries traffic in the
opposite direction.
N No parallel structure exists or service road structure.
EXAMPLES:
Code
Structure #1 R
Structure #2 L
Code Description
R The right structure of parallel bridges carrying the roadway in the direction of the
inventory. (For a defense highway, this is west to east and south to north.)
L The left structure of parallel bridges. This structure carries traffic in the opposite
direction.
N No parallel structure exists.
Code Description
0 Highway traffic not carried
1 1-way traffic
2 2-way traffic
3 One-lane bridge for 2-way traffic
Code Description
0 Highway traffic not carried.
1 1-way traffic.
2 2-way traffic.
3 One-lane bridge for 2-way traffic.
Code Description
T Temporary structure(s) or conditions exist.
Temporary structure(s) or conditions are those which are required to facilitate traffic flow. This may occur either
before or during the modification or replacement of a structure found to be deficient. Such conditions include the
following:
1. Bridges shored up, including additional temporary supports.
2. Temporary repairs made to keep a bridge open.
3. Temporary structures, temporary runarounds or bypasses.
4. Other temporary measures, such as barricaded traffic lanes, to keep the bridge open.
Any repaired structure or replacement structure which is expected to remain in place without further project activity,
other than maintenance, for a significant period of time shall not be considered temporary. Under such conditions,
that structure, regardless of its type, shall be considered the minimum adequate to remain in place and evaluated
accordingly.
If this item is coded T, then all data recorded for the structure shall be for the condition of the structure without
temporary measures, except for the following items which shall be for the temporary structure:
Enter this item in situations where temporary structures exist on the intersecting route. This item should be left
blank if not applicable. See Item 103 for codes and explanations.
Code Description
0 Inventory Route is not on the NHS
1 Inventory Route is on the NHS
Code Description
0 Intersecting Route is not on the NHS
1 Intersecting Route is on the NHS
EXAMPLE:
Reconstruction completed Code
1970 1970
Code Description
0 No widening or not applicable
1 One side, one widening job
2 One side, two widening jobs
3 One side, three widening jobs
4 One side, four widening jobs
5 Both sides, one widening job
6 Both sides, two widening jobs
7 Both sides, three widening jobs
8 Both sides, four widening jobs
9 Other widening
Code Description
1 Concrete Cast-in-Place
2 Concrete Precast Panels
3 Open Grating
4 Closed Grating
5 Steel plate (includes orthotropic)
6 Corrugated Steel
7 Aluminum
8 Timber
9 Other
N Not Applicable or Non-vehicular Traffic Structures
Code Description
1 Concrete
2 Integral Concrete*
3 Latex Concrete
4 Low Slump Concrete
5 Epoxy Overlay
6 Bituminous
7 Timber
8 Gravel
0 None
9 Other
N Not Applicable (applies only to structures with no deck)
* Separate layer of concrete added, but not latex modified, low slump, etc.
Code Description
1 Built-up
2 Preformed Fabric
3 Epoxy
8 Unknown
9 Other
0 None
N Not Applicable (applies only to structures with no deck)
Code Description
1 Epoxy-Coated Reinforcing
2 Galvanized Reinforcing
3 Other Coated Reinforcing
4 Cathodic Protection
6 Polymer Impregnated
7 Internally Sealed
8 Unknown
9 Other
0 None
N Not Applicable (applies only to structures with no deck)
Item 109 — Average Daily Truck Traffic (XX percent) Card 08 2 Digits
Code a 2-digit percentage that shows the percentage of Item 29 — Average Daily Traffic that is truck traffic. This
information is available for on-system bridges from TPP Traffic Section. Do not include vans, pickup trucks and
other light delivery trucks in this percentage.
If this information is not available, an estimate which represents the average percentage for the category of road
carried by the bridge may be used. Leave blank if Item 29 — Average Daily Traffic is not greater than 100.
EXAMPLES:
Average Daily Traffic Code
7% trucks 07
12% trucks 12
If Item 29A — Intersecting Route Average Daily Traffic is greater than 100, enter the average daily truck traffic in
Item 109A. Leave Item 109A blank if Item 29A is less than 100. See Item 109 for further explanations.
Code Description
0 The inventory route is not part of the national network for trucks. Route has
known limitations: length, width, load restrictions, or posted for no
commercial vehicles.
1 The inventory route is part of the national network for trucks (no known
commercial motor vehicle restrictions).
For the intersecting route identified in Item 5.1A, indicate whether it is part of the national network for trucks (most
of the Interstate System and those portions of the Federal-Aid Primary System identified in the Code of Federal
Regulations, 23 CFR 658).
Description
Code
0 The intersecting route is not part of the national network for trucks. Route
has known limitations: length, width, or load restriction).
1 The intersecting route is part of the national network for trucks (no known
commercial motor vehicle restrictions).
Code Description
Y Yes
N No
EXAMPLES:
Use a single-digit code as indicated below to identify the current status of the bridge regarding its vulnerability to
scour. Evaluations shall be made by hydraulic/geotechnical/structural engineers.Guidance on conducting a scour
evaluation is included in the FHWA Technical Advisory T 5140.23 titled, "Evaluating Scour at Bridges. "1Detailed
engineering guidance is provided in the Hydraulic Engineering Circular 18 titled "Evaluating Scour at Bridges.
"2Whenever a rating factor of 2 or below is determined for this item, the rating factor for Item 60 -- Substructure and
other affected Items (i.e., load ratings, superstructure rating) should be revised to be consistent with the severity of
observed scour and resultant damage to the bridge. A plan of action should be developed for each scour critical
bridge (see FHWA Technical Advisory T 5140.23, HEC 18 and HEC 233). A scour critical bridge is one with
Code Description
U Bridge with "unknown" foundation that has not been evaluated for scour. Until risk can be determined, a
plan of action should be developed and implemented to reduce the risk to users from abridge failure during
and immediately after a flood event (see HEC 23).
T Bridge over "tidal" waters that has not been evaluated for scour, but considered low risk. Bridge will be
monitored with regular inspection cycle and with appropriate underwater inspections until an evaluation is
performed ("Unknown" foundations in "tidal" waters should be coded U.)
9 Bridge foundations (including piles) on dry land well above flood water elevations.
8 Bridge foundations determined to be stable for the assessed or calculated scour condition. Scour is
determined to be above top of footing (Example A) by assessment (i.e., bridge foundations are on rock
formations that have been determined to resist scour within the service life of the bridge4), by calculation or
by installation of properly designed countermeasures (see HEC 23).
7 Countermeasures have been installed to mitigate an existing problem with scour and to reduce the risk of
bridge failure during a flood event. Instructions contained in a plan of action have been implemented to
reduce the risk to users from a bridge failure during or immediately after a flood event.
6 Scour calculation/evaluation has not been made. (Use only to describe case where bridge has not yet been
evaluated for scour potential.)
5 Bridge foundations determined to be stable for assessed or calculated scour condition. Scour is determined to
be within the limits of footing or piles (Example B) by assessment (i.e.,bridge foundations are on rock
formations that have been determined to resist scour within the service life of the bridge), by calculations or
by installation of properly designed countermeasures (see HEC 23).
4 Bridge foundations determined to be stable for assessed or calculated scour conditions; field review indicates
action is required to protect exposed foundations (see HEC 23).
3 Bridge is scour critical; bridge foundations determined to be unstable for assessed or calculated scour
conditions:
- Scour within limits of footing or piles. (Example B)
- Scour below spread-footing base or pile tips. (Example C)
2 Bridge is scour critical; field review indicates that extensive scour has occurred at bridge foundations, which
are determined to be unstable by:
- a comparison of calculated scour and observed scour during the bridge inspection, or
- an engineering evaluation of the observed scour condition reported by the bridge inspector in Item 60.
1 Bridge is scour critical; field review indicates that failure of piers/abutments is imminent. Bridge is closed to
traffic. Failure is imminent based on:
- a comparison of calculated and observed scour during the bridge inspection, or
- an engineering evaluation of the observed scour condition reported by the bridge inspector in Item 60.
1
FHWA Technical Advisory T 5140.23, Evaluating Scour at Bridges, dated October 28, 1991.
2
HEC 18, Evaluating Scour at Bridges, Fourth Edition.
3
HEC 23, Bridge Scour and Stream Instability Countermeasures, Second Edition.
4
FHWA Memorandum "Scourability of Rock Formations," dated July 19, 1991.
Code Description
A Bridge foundation is unknown. Screening indicates low risk of scour. Item 113 coded 5.
B Bridge foundation is unknown. Screening indicates that bridge is scour critical. Item 113 coded 2 or 3. Plan
of Action is in place.
C Bridge foundation is unknown. Screening indicates that bridge is scour critical. Item 113 coded 2 or 3. No
Plan of Action in place.
D Bridge foundation is unknown. Bridge is closed to traffic or has failed. Item 113 coded 0 or 1. Plan of
Action in place.
E Bridge foundation is unknown. Bridge is closed to traffic or has failed. Item 113 coded 0 or 1. No Plan of
Action in place.
Enter the forecasted ADT for the intersecting route. This shall be at least 17 years, but no more than 22 years, from
the year the data is submitted to the NBI. The intent is to provide a basis for a 20-year forecast. This item may be
updated any time, but must be updated when the forecast falls below the 17-year limit. If planning data is not
available, use the best estimate based on site familiarity. Use current ADT if a projected ADT is not available. See
Item 115A for year.
The future ADT must be compatible with other items coded for the bridge; for example, if parallel bridges have the
present ADT coded separately for each bridge, then the future ADT must be coded for each bridge separately, not
the total for the route. Code with the necessary leading or trailing zeros.
EXAMPLES:
Year of
Future ADT Code
2021 2021
Year of Code
Future ADT
2019 2019
This reason for change is required by and furnished to the National Bridge Inspection File (NBI) in Washington. See
also Item 127A (Intersecting Route Reason for Change).
Note: Item 2 — District Number and Item 3 — County Number cannot be changed on Card 12. Please notify BRG
if this type of change is required. Code one of the following in Column 24 of Card 12.
Code Description
(A) Replaced by New Bridge
(B) District Number Changed
(C) County Number Changed
(D) Control Number Changed
(E) Section Number Changed
(F) Bridge Number Changed
(G) Duplicate Route Changed
(H) Structure Function Change
(I) Administrative Change — (changed from city to county or county to city or
control section change)
(J) Hierarchy Change — (Highway Number change or Highway Route change)
(K) Correction of Error (not listed above)
When a change to the Intersecting Route Key Identifier occurs, a reason for change shall be coded.
Key Identification for the Intersecting Route are Items 8.4A, 8.5A, 8.6A, 8.3A or 5.1A. District Item 2 and County
Number, Item 3, are coded on the Inventory Route. If District or County Number are changed on the Inventory
Route, please notify BRG of the intersecting route change, also.
Code one of the following in Column 37, Card 12.
Code Description
(A) Replaced by New Bridge
(B) District Number Changed
(C) County Number Changed
(D) Control Number Changed
(E) Section Number Changed
(F) Bridge Number Changed
(G) Duplicate Route Changed
(H) Structure Function Change
(I) Administrative Change — (changed from city to county or county to city
or control-section structure number change)
(J) Hierarchy Change — (Highway Number change or Highway Route
change)
(K) Correction of Error — (not listed above)
Code Description
N No damage to beam(s) or beam members.
Y Bridge has damage to beam(s) or beam members. Requires in-depth
analysis.
If Y is coded, the following information shall be kept with the current inspection data: measured length and depth of
any patches to concrete or prestressed beam(s) and related members, and the number of severed strands on
prestressed beams should be documented where possible. For steel structures, the straightening or patches to steel
members are to be recorded. Visual quality of repair welding shall be documented. Where possible, photographs
should accompany written documentation. If culvert, leave this field blank.
A district that inspects bridges in another district cannot update those bridges. The county numbers are outside the
established range for that district. The update of these bridge records can be accomplished by using one of the
following procedures:
A. The inspecting district can contact the owning district when the data on a bridge or bridges are entered in a
library member.
1. If the owning district and the inspecting district are within the same regional center, the library
member can be “fetched.”
2. If they are not within the same regional center, you must do a ROSCOE-to-ROSCOE transfer
using RJEJCL (select 40 1) to send the transactions to the owning district.
B. The inspecting district can also have BRG update the records by using a ROSCOE-to-ROSCOE transfer to
send transactions to a BRG library. If you choose this method:
1. The destination computer ID will be “CENTRAL.”
2. The destination ROSCOE key will be “D884522.”
3. The naming convention of the member being sent should be as follows:
a. On-system transactions: DIXXON (where XX is the district number).
b. Off-system transactions: DIXXOFF (where XX is the district number).
NOTE: Transactions can only be sent one time per week or the second transfer will write over the first. Transactions
will be deleted each Friday after being applied to the Thursday night update run.
For reports, each district can use RJEJCL to select one of the following:
A. Select 6 and either 1 or 2 to execute Program 120179 which accesses the Roadway Information System
(RIS) file. This lets you view or print the records which are currently in the file.
B. Select 32 and 22 to execute Data on Terminal (DOTS) programs. Error messages contained on DOTS
reports can be corrected in one of the following ways:
1. The owning district can FAX a copy of the error messages to the inspecting district.
2. If a printer ID is known, the output can be printed locally then sent to the inspecting district’s
printer.
3. You may also contact BRG for a copy of the error report.
All districts involved must communicate with each other and BRG so that all records are updated in a timely
manner.