My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Trinity Contractors, Inc 3/1/2017
>
Contracts
>
Capital Contract
>
Trinity Contractors, Inc 3/1/2017
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/11/2018 10:38:25 AM
Creation date
3/10/2017 2:24:32 PM
Metadata
Fields
Template:
Contracts
Contractor's Name
Trininty Contractors, Inc
Approval Date
3/1/2017
Council Approval Date
2/1/2017
Department
Public Works
Department Project Manager
Ryan Sass
Subject / Project Title
Citywide Intersection Signing Project
Public Works WO Number
PW3628
Tracking Number
0000497
Total Compensation
$653,910.20
Contract Type
Capital Contract
Retention Period
10 Years Then Transfer to State Archivist
Document Relationships
Trinity Contractors Inc 4/3/2017 Change Order 1
(Contract)
Path:
\Documents\City Clerk\Contracts\Capital Contract
Trinity Contractors Inc. 5/4/2018 Change Order 2
(Contract)
Path:
\Documents\City Clerk\Contracts\Capital Contract
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
346
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
1 1 <br /> 2 TIP reports shall include: <br /> I 3 <br /> 4 1. A map or plot of the wire/tube location within the shaft and their position <br /> 5 relative to a known and identifiable location, such as North. <br /> I 6 <br /> 7 2. Graphical displays of temperature measurements versus depth of each wire or <br /> 8 tube for the analysis time selected, overall average temperature with depth, <br /> I 9 shaft radius or diameter with depth, concrete cover versus cage position with <br /> 10 depth, and effective radius. <br /> 11 <br /> 12 3. The report shall identify unusual temperatures, particularly significantly cooler <br /> 13 local deviations from the overall average. <br /> 14 <br /> 15 4. The report shall identify the location and extent where satisfactory or <br /> 16 questionable concrete is identified. <br /> 17 <br /> 18 a. Satisfactory (S) - 0 to 6% Effective Radius Reduction and Cover Criteria <br /> 1 19 <br /> 20 Met <br /> 21 b. Questionable (Q) - Effective Local Radius Reduction > 6%, Effective Local <br /> I 22 Average Diameter Reduction > 4%, or Cover Criteria Not Met <br /> 23 <br /> 24 5. Variations in temperature between wire/tubes (at each depth) which in turn <br /> 1 25 correspond to variations in cage alignment. <br /> 26 <br /> 27 6. Where shaft specific construction information is available (e.g. elevations of <br /> I 28 the top of shaft, bottom of casing, bottom of shaft, etc.), these values shall be <br /> 29 noted on all pertinent graphical displays. <br /> 30 <br /> I 31 CSL reports shall include: <br /> 32 <br /> 33 1. A map or plot of the tube location within the shaft and their position relative to <br /> 34 a known and identifiable location, such as North. <br /> 1 35 <br /> 36 2. Graphical displays of CSL Energy versus Depth and CSL signal arrival time <br /> 37 versus depth or velocity versus depth. <br /> I 38 <br /> 39 3. The report shall identify the location and extent where good, questionable, and <br /> 40 poor concrete is identified, where no signal was received, or where water is <br /> I 41 present. <br /> 42 <br /> 43 a. Good (G) - No signal distortion and decrease in signal velocity of 10% or <br /> I 44 less is indicative of good quality concrete. <br /> 45 <br /> 46 b. Questionable (Q) - Minor signal distortion and a lower signal amplitude <br /> 47 with a decrease in signal velocity between 10% and 20%. <br /> I48 <br /> 49 c. Poor (P) - Severe signal distortion and much lower signal amplitude with a <br /> 50 decrease in signal velocity of 20% or more. <br /> I51 <br /> 52 d. No Signal (NS) - No signal was received. <br /> I <br /> I AMENDMENTS TO THE 2016 STANDARD SPECIFICATIONS BOOK <br /> Revised: 8/1/16 <br />
The URL can be used to link to this page
Your browser does not support the video tag.